Nexus S wont turn on after charging. - Nexus S General

I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?

kalda01 said:
I'm using a 9020A model purchased on Ebay for 2 weeks now.
twice already within a few days the phone will not turn on in the morning after charging it all night (in stand-by).
It will not turn on even into boot-loader.
if I take out the battery it turns on like nothing happened.
Any idea what the problem is ?
Click to expand...
Click to collapse
Thats what you called "SOD" screen of death. Just pull your batery when it happen. Also it might be kernel related try changing kernel
Sent from my Nexus S

I'm running CM7 since day one with whatever kernel it came with.
What other kernel might work with CM7 ?

There are still a couple though i don't think any are in development any more. Since it seems to have only happened once so no need to try out different kernels. I wouldn't worry about it at all unless it becomes a regular occurrence.

This seems to have happened to many others with the stable CM7 rom version.
In another post someone who had the issue reported that switching to Netarchy's kernel addressed the problem for him.
This happened already twice today so looks like I need to find a solution.
How difficult it is to replace just the kernel?

Get ahold of a GB compatible kernel, wipe dalvik cache and flash the kernel .zip file. Do a NANDROID backup beforehand (CWM -> backup) if you don't have a recent one already.

In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?

kalda01 said:
In another post someone suggested the following Kernel:
http://forum.xda-developers.com/showthread.php?t=936219
There are CFS & BFS builds. which one should I use? what is the difference ?
Also the kernels are labeled as "2.3.4+ based roms (Nexus-S AND Sprint Nexus-S 4G Phones)", However the CM7 rom is based on 2.3.7. would that work ?
Click to expand...
Click to collapse
CFS is a fairer CPU allocation scheduler, and generally better for multitasking as well as overall performance. BFS is, in theory, better at doing only the "task at hand", but so far hasn't proven any better than CFS, and is additionally less stable most of the time. tl;dr, get CFS.
Kernel should work fine on 2.3.7, don't stress about it. In the event that something goes wrong, just make sure you have a backup anyway.

netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?

kalda01 said:
netarchy-nexus 1.4.1 CFS Kernel is labeled "experimental" since october 2011. Is it OK to use it anyway ? how exactly is a kernel flashed ? via recovery ?
Click to expand...
Click to collapse
Yup, it's OK to use it anyway. Also kernel is flashed via recovery.
Sent from my Nexus S from Tapatalk

Any need to wipe or reset the phone before flashing a new Kernel ?

kalda01 said:
Any need to wipe or reset the phone before flashing a new Kernel ?
Click to expand...
Click to collapse
No need. Simply flash the kernel, via fastboot

flashed the kernel via recovery. I'll report back if the SOD problem is resolved.

5 days later and not even a single "SOD" freeze. looks like changing the stock kernel
did the trick.

3 weeks after flashing the Kernel and the SOD problem is back. 3 times in last 2 days.
Anything I can tweak to avoid these freezes ?

Related

Sleep of Death (SOD)

Hello All,
Here's my 2 cents on SODs and killing of it (even if only temporary)
I am currently on @Anti's Asylum ROM. Previous to that, I was on CM9 ver 7.
Had been plagues by SODs and had almost given up and was about to flash Samsung Stock ROM.
I was on Stunner previous to CM9. Once I was on CM9 and loving it, I came across this nasty looking creature called SOD for the first time in my life.
Threads suggested I should flash GB ROM back and do a clean install. @AndroidIndian was kind enough to walk me through all the steps and I did everything I had to. Then flashed CM9 back. Guess what, those SODDIN SODs were still there.
So, apologetically, I posted that I had to betray my brethren here and go back to Samsung Stock.
Then, @Tremorone PMed me to try @Anti's asylum, built on CM9 code. He said since I was trying to hold on to an AOSP thing, I should try it at leas once. In one last ditch effort, I did the right thing - flashed Asylum ROM over the CM9 ver 7.
Now, the interesting bit:
Initially, I was on XXLPT Modem (the latest one). Overnight, there was no SOD and I was a happy bunny. Next morning I got a long call (about 20 mins). Once the call was over, SOD !!!! Figured it HAD to be a modem.
So, I did the following:
1) I flashed LP5 Modem through Mobile Odin. SODs were less but the lockscreen froze up once.
2) Being the impatient prick that I am, after a while I flashed LB2 Modem via CWM Recovery.
SODs has drastically gone down on that. No SODs in the last 7 hours as a matter of fact.
I don't know if it's the ROM, LB2 via CWM or the combination of Steps 1 and 2 above, but seems like it has more or less solved the problem. Of course, it is still early days and I need to observe for a couple days more.
To everyone suffering at the hands of the SOD demon, I would suggest why not try Step 1, let the ROM settle, and then proceed with Step 2 (as above).
There's no harm in trying, right? And if it solves it, nothing more beautiful than it. Then you can go CM flash happy as soon as new builds start being avaialble.
Thanks to @Abhisahara for helping me keep the faith.
All the best SODding off the SOD.
Cheers.
Well, I think I'm a lucky guy. I had never one SOD since I own a note. I have nearly the same flashing history like you. Flashed also many modems . I can't imagine why the devices are so different. The same thing I noticed with my old HD2. I hope you will find the reason/way to solve this f******* SOD issue
Gesendet von meinem GT-N7000 mit Tapatalk 2
I'm the same after flashing cm9 I had one screen of death on the lb2 modem.. I flashed lp6 just because.. After that I used cm9 for a week with not one sod before flashing ics official
Sent from my superior Nokia 3210 using XDA Premium Plus Legacy Edition
My SODs stopped after I flashed .19 Stunner with LP5 kernel and LP6 modem. I haven't had one since then (**knock on wood**). I am on stock ICS now with the new modem, not CF-root kernel though. Strange how variables are always so different though.
Hmm,
I've flashed several modems since being plagued by the SODs. I'm on CM9 nightlies and am using LP6 from LB2. The SODs have gone down with the newer modem since I was getting 5 or 6 a day! But, I still get at least one or two a day now. I'll try with the latest LPT or LR1 and see if these make any improvements.
They are a bit of a mystery though since there never seems to be any consistency to what is actually causing the sleeps.
I always flashed modems through Mobile Odin and flashed every single modem available for note, but still had SODs.
So I wiped everything and reinstalled the ROM and did not restore data and I did not have SOD.
I have data backed up on Google, it restored my apps (through play store), contacts and wifi access points, so I was kind of OK, since I did not lose out much. But thats just me!
I tried LB2 ,LA4 ,LPY Modems ,and had one SOD in two weeks time while on CM9 build#3 and LA4 modem.
LB2 modem iks very good and I'm using it right now with the latest nightly with no SODs what so ever.
I've flashed modems using CWM and still get the SODs. I'm beginning to think these are not directly related to the modem. I did a clean install of GB from Imilka's CM9 (Chinese leak) then Chainfire's rooted kernal and then on to the CM9 nightly. I didn't copy any system data but I did use TB to resinstall my apps (against advice I know). I had no SODs on Imilka's rom but they appeared following install of CM9 nightly.
I guess I'll try a clean install again but I hate having reconfig my phone everytime since I change so many things via Apex, Minimalistic Text and Folder Organiser apps.
I'm hoping though that we'll get to a nice update on CM9 that will resolve the problem eventually.
I think SOD is WIFI related (not just modem). Since upgrading to ICS, different ROMs, I had many of them on all ROMs and modems, until I set my WIFI to never sleep and disabled any battery saver trying to make it sleep when screen off. That solved it for me. Then started testing battery savers, most of them brought SOD again, until I tried battery defender, which seem to work without SODs.
Had lots of SODs in the past on CM9, none for 3 days since I installed nightly 20120515 and LPT modem. Fingers crossed

[Q] Rooting a U8800 that's currently on 2.2...

Good evening all,
Basically I'm looking to root my girlfriends fathers U8800, it's currently running android 2.2. He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
I've read there are 3 different types of models for this handset. How do I know which one we've got? If that's relevant?
I've found this thread that seems dead easy to follow, http://forum.xda-developers.com/showthread.php?t=1420728 , am I ok to proceed?
When I've rooted it, do I just flash a rom via CWM like I would with my galaxy s? And will I be caught out with bootloader issues or little things like that?
Thanks in advance.
If the device is the U8800 regular model(not pro or plus) you can follow the guides of the link.
And yes, you can flash a rom from cwm recovery.
Only one suggestion. If you flash the latest stock gingerbread rom(I think is the 522), search for a thread called "get your pink screen back" on developing section. The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Thanks for that, I'll get on it tomorrow with an operational head. I'll do the pre root checks and make sure I have everything I need in place before I get going.
dancer_69 said:
If you flash the latest stock gingerbread rom(I think is the 522)
Click to expand...
Click to collapse
It's 528
dancer_69 said:
The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Click to expand...
Click to collapse
*locked pink screen.
Sent from my GT-P1000 using Tapatalk 2
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Dave759 said:
He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
Click to expand...
Click to collapse
Did you look to see what is causing the battery drain? I have a friend with a stock GT540 that had serious battery drain. Turns out it was the GoSMS program. Deleted the app and now his phone lasts 5 days between charges. Switching a rom won't help if the problem is an app.
1) Get cpu spy and see if it is going to deep sleep
2) If not sleeping, turn off running applications one by one and test via cpu spy to find out which one is causing it not to sleep.
3) Either remove the offending app or use Autorun Manager to modify the receivers (if rooted)
You can fix his problem without changing his rom. If he wants root, superoneclick can root 2.2, I just used it the other day. Also make sure he is on the latest 2.2: b138sp04 or b163. I prefer b163, even though it is the China rom, because I like the Huawei launcher better that stock.
A.C.A.B. said:
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Click to expand...
Click to collapse
That's not true... official 2.2 is the slowest thing in existence. If he just needs stability then Ezets CM7 is the answer. There are no bugs with it (except wifi tethering) and it's much much faster than stock...
Also he can undervoltage it to preserve battery life more than stock ROM.
Sent from my U8800
You want the best 2.2 you try Void Eridanus. Everything works.
Want the speed, OEX rom it's a Ferrari. Everything works less the mms with data off.
You can also keep the stock Rom, root it and just apply a ffranco kernel. This way you gain the speed.
3 good solutions here.
I'm don't revert to stock Rom for 2 reasons, cam quality and battery life, otherwise i would use stock Rom without a shadow of a doubt.
In terms of stability and all working it's stock 2.2 Rom and this is unquestionable!!!
I have been trying ALL roms and ALL respective versions since July 2011 therefore I do speak by personal extended experience
I repeat once again, in the conditions you mention leave the phone as it is. If you want to do something just root it and that's it.
as a matter of facts i had my phone with so many rooms that i can even say how many but if u want stability i recomend oxygen... if u want stability and good looks use miui 32...
last .32 miui that i used was from miui portugal in english and nothing to say about that...
battery for 2 days and all smoth...
but my phone is weird... he can take almost every rom and be usable...
The issue with miui pt versions it's the cam quality that is horrible. It's just this detail that it's not very good. The rest it's perfect.
Sent from Odin's device!
Hey everyone, back for an update and some other steps. basically, he got frustrated with how the battery so he went out today and bought the newer huawei. Reading eveyones comments here i think its due to the ammount of apps and being on froyo hasn't helped any thing, but anyways its now my new toy to play with. So far, followed the link i posted in the first thread, rooted and installed the latest CWM (v5). I'm now a little confused when it comes to the get the pink screen back, should i follow this thread http://forum.xda-developers.com/showthread.php?t=1457490 now before flashing a new rom or afterwards?
Again thanks for all the help, I'm almost done bothering you all for now
Edit: Reading on some ROM's and the comments above, i should install B518 stock ROM then flash the bootloader fix from the thread posted above then i can install other ROM's? If so where can i get the stock B518 ROM and how do i know which version I'm using? Sorry and thanks again.
First, which rom you have now?
You can find the version from settings -> about phone.
If you have a newer than 518 version you need to change the bootloader with the one from 518. If you have 518 you don't.
Also check which version of kernel you have(is on about phone also)
If you have a 2.6.32 version(which mean that you have froyo rom), you can flash only roms with this kernel version. If you have a 2.6.35 version, you can flash roms with 2.6.35 kernel or 3.0.8(as aurora ICS).
Basically its a stock froyo rom, im looking to get to gingerbread by the end of tonight but currently im stuck on the huawei splash screen after i did a data reset in CWM. Can still get to CWM though.
What rom you want to flash now?
A custom gingerbread based of froyo's kernel 2.6.32 like CM7.2, oxygen or miui, or the official gingerbread?
Im not particularly bothered, something that won't brick the phone and is stable. I'm more worried as to why it wont boot now after a data reset.. any suggestions for that?
You can use adb and logcat function to see where the problem is. Usually when some errors prevent device to complete the boot proccess, this piece of code loops. You need to have some knowledge of programming though, but maybe is something easy.
and now i have blue screen.. what can i do? or have i bricked it?
Where you have blue screen and what you did?
Usually blue screen instead of recovery mode, means that the recovery.img is deleted from .cust_backup/Image folder
basically, i formatted something, reboot and soon as the huawei logo appear a blue scrren rolls down. when i plug the phone into the pc it detects a folder but its empty, the phone is detected as qualcomm now..
Yes, seems that you formated the partition which has the Image folder with all system images. So, now you need to flash an official rom. You can either flash a froyo or a gingerbread rom. You can avoid this only if you previous had take a backup of this folder. In this case just put all files in (empty now) image folder.

Unlocked Bootloader v8 / ICS - SoDs

I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
droidroidz said:
I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
Click to expand...
Click to collapse
Had sod on any rom (and stock) with changed bootloader (and other problems). Went back to ota stock without root. No problems
I have SoD since going from thors rom back to taboonay and then to V8 bootloader, still trying to solve the issue but no luck. I can't even connect to pc to root it again as I've lost that too
Any of you running a 501?
If so, it's an issue with the kernel.
MD
a500 here
Moscow Desire said:
Any of you running a 501?
If so, it's an issue with the kernel.
MD
Click to expand...
Click to collapse
Using A500
I see so many others with success which is why its killing me that this is not more common issue. There must be something we are doing slightly wrong or forgot to do causing this.
Ok, here is the real deal.
1. ICS Bootloader. Mandatory. Check it when you boot, it should say in the left corner.
2. Recovery version has no effect on SOD. However, you should have the correct one for ICS. Currently I use 1.7.3.
3. The kernel. Now, most of the ICS Roms in the forum for the 500 have a "tweaked kernel". These are the ones you want to use. MAKE SURE the rom you are using is for the patched ICS Bootloader. This includes EZTerry's and Civatos. You have to pay attention with Civ's as he may still have some designed for HC bootloader. YOU DO NOT WANT THESE. I believe Smaury's and Vache's are ok also, but check first.
4. This is probably where the problem is. Wipes and Formats. Sometimes, leftover code from a previous kernel or modules could still possibly be in the tab. This can cause strange issues.
Wipe
Data/factory reset
Cache
Dalvik Cache
(depending on recovery version)
Format System
Format Flexrom
Do this 2 or 3 times, then install the rom.
I use CWM 1.7.3 recovery (too lazy now to change but will in the future)
Also, if you have any doubt which bootloader you currently have, download AcerRecoveryInstaller and it should tell you. After OTA in the Dev forum will also tell you. You don't have to do anything with the app, just start it to get information.
This should get you going.
MD
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Moscow Desire said:
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Click to expand...
Click to collapse
This is an interesting theory and makes sense. In my case with CM9 and Ezterry's rom I have tried the stock kernel for each and ezterry's OC kernel on both...and still SoDs although ezterrys rom/kernel seems to be far less frequest SoDs. We don't have much options for kernels around here.
Progress?
Has anyone made any progress with figuring this out?
My tablet was running fine on a stock, rooted ICS. Then I installed custom recovery, different kernel, and bootloader when I tried JellyBean (ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]) from the Developers forum on here. I started getting SoDs and some of my games weren't running, so I went back to the ICS rom, but the SoDs are still happening. At that point, I was pretty sure it was related to the kernel or the bootloader.
On the "ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]" thread in the developers section they are questioning if the SoD is related to CyanogenMod (which I don't believe it is). I wanted to post there about what this thread is hypothesizing, but am unable to post to that thread (too new to XDA).
Update
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Waleslie said:
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Click to expand...
Click to collapse
Venturing out to JB land is a choice.
Although CM does a pretty good job of doing things, I always have to remember, they lean toward mainstream devices.
We 50x owners, have some pretty good guys. But, we only have a few, compared to the mainstream devices, which have a whole lot more. Welcome to the tablet world.
If it were a samsung or Asus, would probably have a ton more.
But, my ICS on my 501 runs pretty darn good. And I'm thankful to each and every dev and cook who strive to make it better. It's a pity there are not more for our device.
SOD will always plague us it seems. A lot seems to depend on the revision hardware. Seems the earlier versions don't get it much.
MD
droidroidz said:
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
Click to expand...
Click to collapse
same problem as you and 8/10/2011 is when I got mine. I have had some version of hc to work with no sod, but tried everthing and every combination out there (with the mod bootloader) and still have sod, so just went back to stock.

When waking up device, gets black screen, hangs for few secs, then reboots

When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?
its because of the kernal, mine does this aswell..
kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!
Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.
It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.
Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.
i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..

WiFi with ktoonz kernel

Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
TweeXta said:
Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
Click to expand...
Click to collapse
I make the same mistake
Originally Posted by monkteo View Post
Hi,I just install the (I9505 XXUEMKE JB 4.3 Pre-Rooted STOCK ROM's) great rom and I thanks you for bring it here.
Question; after installed I try to flash a custom kernel (AOSP/TW/GE - 4.2/4.3 KT-SGS4 - MFD - KTweaker) and everything started to work wrong (no wifi,net fc,and many others)please tel my what kernel it's perfect for your rom and also if it's realy ned to flash a custom kernel ?
10X
A custom kernel is not required for these ROMs as they include the stock Samsung TouchWiz kernel which I'd say is probably the best kernel for the stock ROMs.
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
TweeXta said:
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
Click to expand...
Click to collapse
WiFi-fix
Regards
Got the same issue with 4.4.2 and newest kernel version...
Tried changing build.prop line but with no success.
Is there any kind of help or a adequate wifi fix for kitkat?
Solved: wiped cache and dalvik and fixed permissions couple of times. Now it works
Sent from my GT-I9505 using xda app-developers app
I'm using GT-I9505 "international" with Paranoid Android 4.45 and successfully installed Ktoonsez kernel (3.4.94) with flashify app using Philztouch cwm recovery.
No problems at all, everything works, not tweaking by KTweaker, just raised 2.2GHz from PA's processor settings, ondemand as processor governor and Noop on i/o scheduler.
Tried few KTweaker profiles first but didn't find any good what understands to drop processor on deep sleep mode, almost all keeps it running all the time, PA's own handling with freshly installed KT-SGS4 kernel did best job for me.
Testing with profiles was frustrating thing, there wasn't way back to same situation what I got on fresh install.. few PA flashes later stand on "default".
Props to KToonsez (kernel), Christian Göllner (Flashify) and Paranoid Android.

Categories

Resources