Should i go with stock kernel of RR rom or should i go with a custom kernel i prefer battery life,stability and a little bit of performance
if you can take an honest advice.....dont flash any rom or kernel or even do any update if your phone,s performance,battery and stability are ok!.
my phone worked without issues for 7 months but began showing touch issues just after i began overdoing it with flashing new roms,kernels....etc
now even miui 9 oreo (which had the best battery,stability) is giving me touch issues so am forced to stick to the rom/kernel combination that gives me less touch issues
ron_hyatt said:
if you can take an honest advice.....dont flash any rom or kernel or even do any update if your phone,s performance,battery and stability are ok!.
my phone worked without issues for 7 months but began showing touch issues just after i began overdoing it with flashing new roms,kernels....etc
now even miui 9 oreo (which had the best battery,stability) is giving me touch issues so am forced to stick to the rom/kernel combination that gives me less touch issues
Click to expand...
Click to collapse
its giving me touch issues but im going to adapt all that advice that were being told to me
wecp17 said:
its giving me touch issues but im going to adapt all that advice that were being told to me
Click to expand...
Click to collapse
well,thats a different story.....if you are having touch issues try flashing xiaomi eu 10.3.6.0+malakas oc kernel (5/8/19 version) ......this rom/kernel combo partially fixed my touch issues(i tried many roms and kernels before trying this combo but didnt fix the issue).
try optimus drunk kernel, haven't tried itself but i heard it fixes many touch issues for alot of people, personally tho i use arter97's kernel and there is also no touch issues here (as if i had any in the first place, actually never had any touch issues with my pocophone since day 1, i think it's a 9/2018 NVT-ts or 10/2018 NVT-ts model) also i am on 9.6.27 vendor+firmware.
Related
Good morning everyone
Seems to be that my GSII has serious issues running his stock rom (continuous reboots, not-working 3g etc.). I tried several factory resets, but nothing worked 100% . CM fixes some of my problems, but the only full-working custom rom is MIUI, that seems to be stable and very neat. Despite that I still prefer the custom rom (yes I'm probably insane), or a more traditional one like CM and I really would like to understand what kind of problems can generate such a massive amount of errors and reboots.
Could be a hardware problem? MIUI works fine, I can't explain why I still got problems with other ROMs.
Sorry for my bad English, thanks in advance
Without telling us the version of the stock rom you are using, we can never give you any answers.
I'm currently using
2.6.35.7-I9100XWKDD-CL161513 [email protected] #2 Kernel
Gingerbread.xwkj3 Build
That's not the original stock ROM, just one I found (here on xda I guess...)
Is there some kind of hardware-check I can run by myself, just for exclude manifacturing defects?
if you want to check to exclude hardware defects, u could go to the dialer and press *#0*# .. it will give u a list of tests which allows u to pinpoint any hardware defects ( if it exists) .... but if the problem is with the 3g, you could reflash your modem..
Initial problems were strictly connected with 3g's use, after a few hours of use i've noticed slowdowns using sms, then it started crashing and random rebooting. That's the same reason why I initially switched from original ROM to CM. I mean, I know that Samsung's ROM is not the best one at all, but I can't figure why it's so instable on my device.
fra beone said:
I'm currently using
2.6.35.7-I9100XWKDD-CL161513 [email protected] #2 Kernel
Gingerbread.xwkj3 Build
That's not the original stock ROM, just one I found (here on xda I guess...)
Is there some kind of hardware-check I can run by myself, just for exclude manifacturing defects?
Click to expand...
Click to collapse
As that the oldest stock rom try a newer one .
jje
Updating: now my GSII works with latest stable Cyanogen, except for the 3g that's still not working. Should I reflash modem, as suggested by roophz?
That old kernel is known to cause random reboots.
Update to a newer stock rom.
Sent from my GT-I9100 using Tapatalk
Update 2: I switched from the old stock rom to the latest cyanogen stable version, then to a newer stock rom and then back to MIUI again. Still no life signals from 3g.
How is that possible?
Hi all,
Until recently I have been having very unstable results with my SGS2 (gt-i9100), every time the phone would freeze, overheat, use most of the battery in 2 seconds (figuratively speaking that is) or rebooting itself.
Some people on this forum told me to try a different kernel or roms, something I did and well no real improvement, I tried combinations of ressurection remix, omega and kernels such as siyah and dorimanx (I tried more but these are the ones I still remember by name)
Luckily (or unfortunately) I love my phone and android so I didn't really want to change hardware.
Couple of weeks ago, I figured that maybe I should try yet another rom and... SUCCESS!!
Ever since flashing AOKP milestone 1 everything is the way it should be (well to be honest first thing I always do when getting a new phone is rooting it and getting a new rom, so I am not sure how "normal" out of the box operating of an android is :silly
So basically my question to you is:
does the instability have anything to do with the kernel? currently using 3.0.31-cm-00008 (which incidentally, is that CyanogenMod?)
if it is related to the kernel, anyone has any suggestions to make dorimanx/siyah work (as they seem to be pretty popular here on xda, I'm guessing it has more to do with me)
and less kernel related, if a rom is AOKP based (or CM or whatever), does that mean that this rom has all the bugs from the base + the things the specific rom has?
Thanks!
supermooshman said:
Hi all,
Until recently I have been having very unstable results with my SGS2 (gt-i9100), every time the phone would freeze, overheat, use most of the battery in 2 seconds (figuratively speaking that is) or rebooting itself.
Some people on this forum told me to try a different kernel or roms, something I did and well no real improvement, I tried combinations of ressurection remix, omega and kernels such as siyah and dorimanx (I tried more but these are the ones I still remember by name)
Luckily (or unfortunately) I love my phone and android so I didn't really want to change hardware.
Couple of weeks ago, I figured that maybe I should try yet another rom and... SUCCESS!!
Ever since flashing AOKP milestone 1 everything is the way it should be (well to be honest first thing I always do when getting a new phone is rooting it and getting a new rom, so I am not sure how "normal" out of the box operating of an android is :silly
So basically my question to you is:
does the instability have anything to do with the kernel? currently using 3.0.31-cm-00008 (which incidentally, is that CyanogenMod?)
if it is related to the kernel, anyone has any suggestions to make dorimanx/siyah work (as they seem to be pretty popular here on xda, I'm guessing it has more to do with me)
and less kernel related, if a rom is AOKP based (or CM or whatever), does that mean that this rom has all the bugs from the base + the things the specific rom has?
Thanks!
Click to expand...
Click to collapse
1. May or may not be, usually it's kernel related, yeah that is the usual kernel made for CyanogenMod
2. The latest dorimanx does work fine with xwlsn and so does the latest siyah for xwlss.
3. An AOKP rom has different frameworks and usually is more buggier than stock rom, because of closed source codes (blame Samsung) several features are disabled or improperly functioning.
Sent from my GT-I9100 using xda app-developers app
hello guys, here i have some problem to connect with wifi after flashing a certain new ROM
when i try to connect, it always said, Obtaining IP adress.....authentication.....
this is happen to
- NeatRom (AOSP)
- Slimkat
- (long time ago with Supernexus)
well i dont have a problem connecting to Wifi with
- stock Rom
- temasek
- Archidroid
i have go through all the search topics, flashing WIFI-II9300 fix... do the terminal thing...set wifi region (Singapore, Europe, United Sate), flash boefella kernel.... still cant connect...
i hope all the master developer here can help me, and let me use the above ROM that i want to try....
normeck said:
hello guys, here i have some problem to connect with wifi after flashing a certain new ROM
when i try to connect, it always said, Obtaining IP adress.....authentication.....
this is happen to
- NeatRom (AOSP)
- Slimkat
- (long time ago with Supernexus)
well i dont have a problem connecting to Wifi with
- stock Rom
- temasek
- Archidroid
i have go through all the search topics, flashing WIFI-II9300 fix... do the terminal thing...set wifi region (Singapore, Europe, United Sate), flash boefella kernel.... still cant connect...
i hope all the master developer here can help me, and let me use the above ROM that i want to try....
Click to expand...
Click to collapse
i just want to try that ROM .. are you already reflashing it?
tr4falgar said:
i just want to try that ROM .. are you already reflashing it?
Click to expand...
Click to collapse
yep...now im back to temasek...
normeck said:
yep...now im back to temasek...
Click to expand...
Click to collapse
I had the exact same experience with my wife's phone that I bought of ebay. I even flashed a variety of RIL's (radio interface layers) and different modems. I'd never had the problem with my SGS3 before, and have hundred of different roms on it.
Anyway it seemed to be a kernel issue and after trying ever combination possible I found that wifi would always work perfectly on any stock based rom or any CM based rom (assuming that hey used the CM kernel). It wouldn't even work on a CM rom if I flashed a different kernel such as Yank's, Boeffla or Googy.
Also at the time I trawled the net looking for answers and found one or two others that had the same issue, but could still use stock Sammy or CM. Strange... almost felt like it was an odd batch.
pjcarrmole said:
I had the exact same experience with my wife's phone that I bought of ebay. I even flashed a variety of RIL's (radio interface layers) and different modems. I'd never had the problem with my SGS3 before, and have hundred of different roms on it.
Anyway it seemed to be a kernel issue and after trying ever combination possible I found that wifi would always work perfectly on any stock based rom or any CM based rom (assuming that hey used the CM kernel). It wouldn't even work on a CM rom if I flashed a different kernel such as Yank's, Boeffla or Googy.
Also at the time I trawled the net looking for answers and found one or two others that had the same issue, but could still use stock Sammy or CM. Strange... almost felt like it was an odd batch.
Click to expand...
Click to collapse
ahh... thankz for your feedback... really disappointed when you only can use only certain custom rom.... hope developers can look into this problem....
Hello friends.
I am new to this wonderful community and very happy to be a part of it.
I am facing a very strange problem. I am trying to update my WT9i Live with walkman from Gingerbread to Ice cream sandwich. Problem is .. whenever I flash an ICS rom my touch doesn't work !! Everything else works fine (physical keys / network / audio). Then if I install GB rom again it works flawlessly.
I have unlocked bootloader.
I am using Flashtool to flash stock roms.
* WT19i_4.0.2.A.0.58_(1254-1868).ftf = works
* WT19i_4.0.2.A.0.62_(1254-1889).ftf = works
* WT19i_4.1.B.0.431_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_CUSTOMIZED CE3 WORLD I 1254-1889.ftf = touch doesn't respond
I have no idea what could be the reason. Any GB roms works smoothly. Any ICS roms bricks the touch screen. I have tried custom kernel (mesa .. kappa) and many custom ICS rom .. same problem. But at any moment I flash GB rom .. everything works.
I did all the research I could (for last 4 days) and read many threads .. tried many things. Nothing helped.
Please help me! Please Please Please.
I have seen many threads with problem "touch does't work because of flashing wrong rom or kernel".
I don't think that's my case. Because whenever I flash a stock GB rom .. it works just fine. Problem happens with ICS roms .. custom or stock.
I am going to try some custom GB rom with custom kernel. I'll post if that works.
This thread is most likely my last hope of finding a solution .. please help!
Just out of curiosity downloaded the 587 ICS generic rom from flasstool website then flashes it .. same touch problem.
Now downloading latest Nightly CM10 coconut. I'll try it. CM 9.1 stable did not worked .. same touch problem.
Please Help ! I dont see a clue ! Why ICS roms would freeze my touch when everything else works? I am on the verge of throwing my phone out of window !!!
Latest CM10 Nightly build = same problem .. touch screen is not working.
Flashed Stock GB = everything is fine !
:crying::crying::crying::crying::crying:
Now I am downloading every regional roms of stock ICS .. its all I can think of.
I know its a very old phone and update / development for it completely stopped. Its forgotten. Still I love this little cute handset and I would love to get ICS on it (for app support .. many app do not work on GB .. like google chrome).
So please help !
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Pixelado said:
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Click to expand...
Click to collapse
Hello. Thank you for replying. Its a second hand phone .. my brother purchased it from a friend then gave it to me. So it may have a replaced display or digitizer. I just checked with my brother and he said his friend never repaired the phone.
So GB and ICS use different digitizer drivers? Is it possible to use GB touch drivers with ICS?
No idea. Your problem is truly rare haha.
I'm out of ideas here, most of the time flashing a stock ftf does the trick, but not here.
if I were you, i'd sell that phone to someone who woulndn't care about software updates hehe.
Hello Friends.
I am posting this in case someone else face the same problem and find this thread. In my opinion ..this is a very rare and strange problem.
This problem should never happen with an original handset.
If your touch only works with Gingerbread stock roms and even after complete wipe other stock roms freeze your touch .. then you can be sure that your touch was replaced with a cheap one. Go to a servicing center and replace it with a good touch or sell the phone to someone else who doesn't care about updates.
I went to a servicing center today and replaced my touch. Now it works smoothly with stock ICS rom. I am sure it will work with CM too. It costed me around 25$.
1 tip to recognize low quality touch. Low quality touch will not have transparent bottom-left and bottom-right button. You wont be able to see the key lights through it. Good quality touch will have transparent button. Another warning .. after market touch is most probably not scratch resistant like the original touch .. so you may want to use a good screen protector (plastic film) on it.
This is not only for WT19i. Whenever you buy a secondhand set .. make sure its touch wasn't replaced and best to check if its upgraded and working properly.
Thanks to "Pixelado" for hinting me about the replaced touch issue. Then it made sense to me .. there was no other logical reason for the stock rom not working.
I am very happy with my upgraded ICS But kinda sad about the money loss ! Anyway loss is loss. This is a good handset and I hope it will serve me good. Now looking for a way to root it.
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Pixelado said:
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Click to expand...
Click to collapse
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
I've never tried mesa, so no comment there. Quie frankly, rage 3.2 seemed to be all i ever needed when using a stock rom. I tried lupus, but stopped using it when they switched from CWM to TWRP.
Angelina7 said:
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
Click to expand...
Click to collapse
i have same problem too
can u solve this problem?
I in the past did not have the issue where the camera keeps making sound and can't focus at all, I've seen that devs have made special kernel for such users, is this issue permanent for all roms that I install henceforth or just on the current rom, if I flash a focus Fix kernel will its effect be on my current rom only or on all the roms I install after that? does focus Fix kernel restore it back to original state or you still have slight issue and hardware clicks? I'd appreciate answers!
kewlest22 said:
I in the past did not have the issue where the camera keeps making sound and can't focus at all, I've seen that devs have made special kernel for such users, is this issue permanent for all roms that I install henceforth or just on the current rom, if I flash a focus Fix kernel will its effect be on my current rom only or on all the roms I install after that? does focus Fix kernel restore it back to original state or you still have slight issue and hardware clicks? I'd appreciate answers!
Click to expand...
Click to collapse
Hi
Just like you I didn't have focuse issue but after I flashed a ROM with the fix now i have clicking sound and refocusing in videos. And I have this problem now in every ROM even the ROMs without the fix.
Now I'm trying to solve this problem, I hope rolling back to the official stock ROM will help me.
I don't recommend to install a ROM with the fix!
Xlipton said:
Hi
Just like you I didn't have focuse issue but after I flashed a ROM with the fix now i have clicking sound and refocusing in videos. And I have this problem now in every ROM even the ROMs without the fix.
Now I'm trying to solve this problem, I hope rolling back to the official stock ROM will help me.
I don't recommend to install a ROM with the fix!
Click to expand...
Click to collapse
install pixel experience++ unofficial rom, you won't have the focus issue on that, it has no bugs except for the fact that volte doesn't work on it after reboot yet.
Xlipton said:
Hi
Just like you I didn't have focuse issue but after I flashed a ROM with the fix now i have clicking sound and refocusing in videos. And I have this problem now in every ROM even the ROMs without the fix.
Now I'm trying to solve this problem, I hope rolling back to the official stock ROM will help me.
I don't recommend to install a ROM with the fix!
Click to expand...
Click to collapse
install pixel experience++ unofficial rom it won't have focus issue, you won't have volte on that after reboot though. it doesn't have any other bug that I know of
Does the Focus Issue problem work with Pixel Experience++ ?
Because i have the problem since i flashed a rom and the problem is still alive
i have tested many different camera apps but none fix the blurry pictures.
the focus works on a very low distance, but when you go outside and want to take a picture, they are always blurry..
I had the focus issue (blocked at 20 cm) and installing Resurrection Remix (RR-N-v5.8.5-20171006-x2-Final.zip), worked for me