Related
My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?
legato89 said:
My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?
Click to expand...
Click to collapse
Baconbits, to my knowledge, is the only OCd kernel available for the stock ROM. Your screen issue might actually be caused by underclocking though, do you have a screen off profile or a minimum set?
Sent from my T-Mobile G2 using XDA App
I just have it set to 368-1497. Should I up the minimum?
legato89 said:
I just have it set to 368-1497. Should I up the minimum?
Click to expand...
Click to collapse
Give the overclock widget a try. Its available free on the market. In the advanced setting, set your screen off profile to 245 min and 806 max. Scroll down and hit "save" before you exit settings. That will keep your phone running at stock speeds while the screen is off and should stop the wake issue you're having. When you're using the phone you'll be at the higher speeds.
I already had the widget. Did what you said but it still occurs.
legato89 said:
I already had the widget. Did what you said but it still occurs.
Click to expand...
Click to collapse
245 is *way* too low, especially if you have things running in the background ... just start raising the lower end up until it stops happening.
Sent from my T-Mobile G2 using XDA App
Setting it to stay at 800 while the screen is off seemed to fix it. Any ideas about wifi calling bugging out? It usually doesn't happen very often, I think when my phone has been on for a while without a restart.
overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.
dietotherhythm said:
overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.
Click to expand...
Click to collapse
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App
EdKeys said:
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
set the off screen profile to the lowest speed 200/200mhz and 100% priority and he wont have anymore wake issues, don't know what I was reading hahaha
The screen on issue doesn't happen anymore but I'm not satisfied with my battery life. In the past something was causing my battery to drain insanely fast so I un installed a bunch of unused apps and started checking background tasks but when browsing the internet for 20 minutes on my way home I use 30% of the battery, bluetooth on.
Sent from my T-Mobile G2 using XDA App
Anyone know if it is possible to run Pershoot's kernel on the stock rom that comes with the device? Any side effects?
I don't know enough to say 100% one way or the other, but I read in a post I can't find right now that only BaconBits is made to work with the stock rom.
FWIW, I tried to flash the 1.8 GHz kernal on my stock G2 this morning, and got stuck in a boot loop.
On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.
legato89 said:
On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.
Click to expand...
Click to collapse
NO. The first thing you need to do is flash clockworkmod 3.0.0.5, which is totally different than ROM Manager. As of right now the latest clockworkmod available through ROM Manager is 2.5.1.3. If you haven't flashed that yet (2.5.1.3) do that first through ROM Manager. The best way to flash 3.0.0.5 is to find the .img file, place it on your sd card and run the commands from terminal emulator. After that just wipe data/factory reset, wipe davlik cache and flash the latest nightly .zip, reboot, then the latest gapps .zip. Go to the development forum and the first post in the nightly vendor vision thread has all the links you'll need.
Hey guys, I constantly have random hot reboots. No pattern or anything, it just happens. I have asked a few guys in Calkulin's forum... everyone offered help... but no one actually helped me fix the issue.
Basically, I am on Calk's 2.0. Only other thing I flashed was Overstew's ICS theme (I used themeporter). No, my issue isn't the theme. I have had these issues since Calk's 1.5. Theme or no theme.
Here's my routine of setting roms up:
Manually wipe everything -sd card.
Use Calk's Format All.
Flash Calk's 2.0 and Overstew's theme.
Reboot.
Install Titanium, but only restore apps (41 apps), no data.
Set LauncherPro as my default launcher.
Setup my settings.
Just using Calk's stock battery saver script. No overclocking or undervolting.
I have tried wiping and new downloads several times. I wiped my external sd card. I even removed it, for a while.
Any ideas? I had a logcat during the hot reboot too. It had some errors around GPS right before it rebooted.
Thanks
P.S. I also had the same issue on my old Evo 3d. I just thought it was my hardware...
Undervolting is what Calk himself recommends to fix hot reboots. It's in the OP on his ROM threads. Also different kernels. Tried any of that?
wolfkstaag said:
Undervolting is what Calk himself recommends to fix hot reboots. It's in the OP on his ROM threads. Also different kernels. Tried any of that?
Click to expand...
Click to collapse
Actually, he recommends restoring the Stock Voltages to remove the default undervolting.
"Having random reboots or freezes?
Try flashing the Calkulin's_Undervolt_Stock_mV_Settings_for_E4GT zip attached or flash a different kernel
first thing that comes to mind is the viper los script
I don't have the Viper LOS. I have tried different kernels. Plus, isn't 2.0 using Rogue's stock anyway?
I'm not undervolted. 2.0 can't be undervolted without using tegrak :/ all great suggestions... it's driving me insane that I can't figure this out.
Sent from my SPH-D710 using XDA App
I am on Calks 1.5 rom and do not have any reboot issues. The first thing I do when I flash any new Rom is put back the stock pulled kernel and I believe this is the most stable of them all and I also have never seen an LOS on it.
Do you have any battery saving apps or task manager apps running? I know these have caused issues like this as well...
No. Nothing! I had stock pulled kernel before. Maybe I will try it again. But isn't it the same as Rogue stock + boot animation and init.d?
Sent from my SPH-D710 using XDA App
I used to have random reboots with different lockscreens from the AIO mod. Had no lockscreen and had no reboots.
Definately recommend stock kernel and restoring stock volt settings. As for Los, ek02 fixes it
If I was helpful, give thanks
Sent from my Epic 4g Touch
Hey I remember chatting with you in the Calk rom thread. "OP"
As a update to my situation. I was also having random hot reboots on EVERY rom I was on UNTILL my latest combination of Kernal / Rom.
My current setup is Kernal: EK02 and my rom is Calk v2.0 which is built on the EK02 stock build.
I have yet to have any hot reboots. My current Up Time is 38:58 which means I have not did a battery pull or reboot in 38 hours.
I also use Titanium Backup to restore about 30 apps + data on my end, and MyBackup Pro to restore bookmarks / texts
For the first time it looks like my hot reboots are currently fixed. I dont use any undervoltages and no SetCPU no custom launcher and no custom lockscreen. Everything Stock and all 7 home screens nearly filled with icons and picture frames ect...
I was using Rogue's kernel and was going to switch to stock today, as that was the only thing I didn't do... but I was in the middle of calibrating my battery this morning and I was getting great battery life. Well, 15 hours later, not one hot reboot, light usage (lots of texts through google voice and xda, and a little browsing) with a screen on time of 1:45 and I'm at 54%. Has my issue been fixed? I have no idea. Am I happy at the moment? F*ck yeah.
hypersonicx said:
Hey I remember chatting with you in the Calk rom thread. "OP"
As a update to my situation. I was also having random hot reboots on EVERY rom I was on UNTILL my latest combination of Kernal / Rom.
My current setup is Kernal: EK02 and my rom is Calk v2.0 which is built on the EK02 stock build.
I have yet to have any hot reboots. My current Up Time is 38:58 which means I have not did a battery pull or reboot in 38 hours.
I also use Titanium Backup to restore about 30 apps + data on my end, and MyBackup Pro to restore bookmarks / texts
For the first time it looks like my hot reboots are currently fixed. I dont use any undervoltages and no SetCPU no custom launcher and no custom lockscreen. Everything Stock and all 7 home screens nearly filled with icons and picture frames ect...
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App
Moose8106 said:
I was using Rogue's kernel and was going to switch to stock today, as that was the only thing I didn't do... but I was in the middle of calibrating my battery this morning and I was getting great battery life. Well, 15 hours later, not one hot reboot, light usage (lots of texts through google voice and xda, and a little browsing) with a screen on time of 1:45 and I'm at 54%. Has my issue been fixed? I have no idea. Am I happy at the moment? F*ck yeah.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
After jumping to the EK02 Rom and Kernal Im also a happy camper now.
No reboots / No los / No lag / No dieing battery.
Now if only Sprint could fix there slow 3G that be great.
On the topic of battery, I never calibrated or did anything special but I noticed my phone can last 12hours + without charge if I turn off 3G when Im not using it. For example I work in a warehouse where I get good signal for calls and texts but 3G is mad slow, so I turn 3G off but am still able to recieve texts and calls and my battery life doubles in that period of time. Soon as I turn 3G back on, battery starts to die faster.
I don't know if this possible but I really like to find out if there is something causing the SOD that we can actually do something about(as in it isn't hardware causing it). I get SOD's on some repack kernels but not on others. When I get it has quite frequently. I am not running setcpu nor do I have any other software controlling the cpu. I have however been using juice defender. I like the product. I am going to remove it and flash a repack kernel that I know gives me SOD's and see if something in the power saving on the JD might be contributing to it. I would like to hear from others that have this issue and see if you are running anything like setcpu or JD.
I've been thinking of something. I don't have sod at all. For those that do have sod how good is your phone at overclocking? Meaning can it run stable at like 1.6 or where does it freeze at?
I'm wondering if its something to do with the difference of processors.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
I dont really overclock anymore but when i used to, my phone froze at 1.6. This was back when i was on calk eg30 rom. Idk what would now if i tried again
Sent from my SPH-D710 using xda premium
I haven't oc'd mine so I am not sure what it is capable of. Tomorrow I will disable the JD and flash a repack and see if that has any effect. It is frustrating because I love the repack rom's. For now I use mobile odin to flash a repack and boot to recovery if I want to nandroid then flash the stock kernel back again.
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
badname said:
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was just curious because on the original epic I had sod on some kernels and that phones processor was terrible. It froze when I tried to overclock it. The next one I got I wad able to overclock and I never had sod. Just seeing if phones with not being able to overclock might have an issue right now.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
Are you using SetCPU? If so, don't fix screen off at 200-500.
Yeah we really meed to figure out what the heck is going on. For the last few days i've been trying to figure out why i've been having SoD. Im on blazer ROM and ive found out that if I don't flash a new kernel i'm fine. But as soon as I flash rouge 1.4.1 or 1.4.0 I get an onslaught of SoD. Things ive tries to fix it are:
-Installing set CPU and raising the voltage and changing gov. to on demand.
-taking all the init.d scripts out of the blazer ROM zip before flashing.
-I find that when the phone is on the charger it never gets SoD
That last point leads me to believe that it has something to do with deep sleep. Because when the phone Is plugged in it isnt allowed into deep sleep mode and idles at 200Mhz. Ill be looking into this more tonight. If anyone would like to work with me i'm always in the e4gt ics dev channel on freenode.
Sent from my SPH-D710 using XDA
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
ElAguila said:
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
Click to expand...
Click to collapse
you know....oddly enough I did install juice defender a few days ago....then flashed the 1.4.0 kernel and thats when everything started.....BUT ive since reflashed the rom a million times without re installing JD and i still get SoD with the 1.4.0 kernel
If you continue to not get Sleep of deaths...will you try flashing 1.4.1 or 1.4.0?
Just to clarify, does the SOD issue include texts/calls not going thru whatsoever while phone sleeping on or off charger for more than ten minutes? I get this with any ICS up to 06, when people call me it goes to VM directly, texts go to sprint limbo. Or, do these leaks just horribly handle low signal areas? I was on stock 85 prl, and signal was about 0-1 bar sprint and force roamed on 1xrtt for 2-3 bars... since this screwed me on a couple important calls I reverted to EL29 and flashed 111115 PRL... anyone have these issues with ICS, or is it just my **** reception and network issues?
Oh, and I SWEAR... no conspiracy theory... but anyone notice pretty much all samsung leaks have issues that are magically fixed for final release? Epic froyo, GB, now ICS on the Epic Touch... just sayin... its like they dont want us daily driving these... just use em enough to beta test (really this site should be renamed XDA Beta Testers)?
The issue you are talking about sounds more like the loss of service bug that has plagued some of these phones. the sleep of death is when the screen turns off and then you can't get the phone to come back on with out holding the power button for 10 seconds or pulling the battery. I am still doing fine. I enabled juice defender but selected advanced settings and disabled jd from controlling the auto sync. I set the controls options to default. So far I haven't had an sod. I will see if I can flash those repacks but I am not sure if it will work right since I am on an ICS rom.
SoD almost certainly involves the cpu going into deep sleep and not coming out. I have never experienced this issue on the E4gT on any rom/kernel combo, but I dealt with the issue extensively on the nook color it it's early days. I can definitively say that because a large number of users are using the repacked kernels and are not having SoD issues, then it is 100% NOT repacked kernel related. SoD is caused by voltage issues or cpu step switching problems. The repacked kernels are identical in these regards across all users, therefore the repacked kernels are not causing the SoD issues.
I've had the SoD a few times on FC05 and FC06 - I'm in the process of downloading FC07 right now. It doesn't happen often (3, maybe 4 times in a few days) and I cannot pinpoint any actions preceding it. I no longer have Juice Defender installed. It's odd though, I've also had problems receiving Kik messages after a reboot. My girlfriend sent me a few messages 6 hours ago that I didn't get until I opened the app, then it's back to normal. This is a pretty regular problem. It's like I have to kick start the app before it starts. But over that 6 hours I streamed Pandora just fine and Gmail has been syncing as normal.
It is a puzzling issue. I also don't think the repack kernels acutally cause it to happen but there is something about the issue that causes it to happen frequently when using a repack. I can go back to any of the stock kernels and it works fine even with juice defender running. That is why I thought perhaps it was some app like juice defender that was causing it but people still have the issue without juice defender. Fortunately for me it seems the fix was to disable juice defender. Unfortunately for my battery though.
Well so far it seems that ive found my solution. All i did was grab the 1 click Odin to Stock Rooted EL29 and wiped everything. I wiped internal storage and flashed back to rooted stock with odin. Then i Odin'd a kernel and flashed back to blazer rom and then had to re odin the rouge kernel that was originally giving me issues. So far all is well. I suggest giving it a shot
My phone locks up 2-3 times a day when sleeping. When it locks up, the "SAMSUNG" splash screen briefly flashes, and the phone vibrates. If left alone, it gets warm. I have to hold the power button or pull the battery to restart it. I have been unable to adb into the phone to get logcat or dmesg after it locks up. Also, this never occurs while the phone is plugged in. I have tried Darkside v8 with both Venom and Faux 008 kernels, as well as Jedi Mind Trick 8/18 with Faux 009. With Darkside, I tried changing the screen-off governor with System Tuner to ondemand as mentioned at http://forum.xda-developers.com/showpost.php?p=29559002&postcount=8633, but it didn't help. Is there anything I may have done wrong, or any way to fix this? Thanks!
What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.
MadMax3947 said:
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.
Click to expand...
Click to collapse
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.
MadMax3947 said:
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.
Click to expand...
Click to collapse
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.
I tried flashing Gideon's stock OC/UV script (http://forum.xda-developers.com/showpost.php?p=20946429&postcount=574), thinking that my phone may just be unable to handle the default UV with Venom and Faux, but this caused it to SOD (without the SAMSUNG splash) almost immediately. I went back to my Nandroid of Darkside v8 (since Mind Trick didn't help things), and flashed Faux 009 with the undervolt set with System Tuner to -12.5mv below stock for all stock frequencies. If this doesn't help, is there a possibility that my phone is faulty? I have had it since December. Also, could this be related to the GPU or L2 overclocks in Venom and Faux (but if so, why wouldn't it crash when the phone is awake)? Thank you for your time.
If it still crashes, I have a flashable zip of the stock ICS kernel and its modules that I can try, or if extremely necessary I can ODIN back to stock.
EDIT: manual Faux UV did not help, just flashed stock.
EDIT2: It just crashed with stock kernel as well (still using Darkside v8 ROM). Since it doesn't seem to be ROM or kernel related, I'm worried it may be the phone (perhaps whatever passes for a PSU in a smartphone? It'd explain why it doesn't crash on battery power). I'll probably try flashing AOKP ICS next in case it's a TouchWiz problem. Is there anything I'm missing here, or should I ask for a warranty exchange if AOKP or stock ODIN still crashes?
EDIT3: Uninstalled System Tuner to be completely sure nothing's affecting the governor/voltage/clock/etc. (still Darkside v8 ROM, stock UVLE1 kernel), crashed within 15 minutes of restart.
MadMax3947 said:
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.
Click to expand...
Click to collapse
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I was worried about this. I will ODIN back to stock tonight, but I won't be able to take it to a t-mobile store for a couple of days. Thank you for your help.
EDIT: I have been running stock UVLE1 (kernel and ROM) without root for almost a day now, and it has not locked up. According to CPU spy, the phone is able to enter deep sleep. Could there be something in the custom boot scripts used by Darkside and Mind Trick that my phone doesn't like? It's about the only thing I could think of that would not be fixed by the stock kernel. I might try re-rooting and/or flashing AOKP ICS in a few days if my phone holds up.
I've had this E4gt for a few days now. First thing I did was root it with the FI27 Odin one click method, then install Agats source 6.5 kernel. Had some random reboots that I shrugged off as my phone not liking any undervolting. But it still does it, even under _dan's lightweight v0.2 rom
It isn't completely random though. Most of the reboots are when I'm trying to wake up the phone after letting it sit idle. Other times it'll reboot while it's sleeping idle. it has NEVER rebooted during use (I ran pandora/poweramp for 8 hours no problem)
It also occurs under most governor settings.
It almost seems that for whatever reason, idling at 200mv is causing the phone to crash and reboot.
the only overclock utility I use is System Tuner Pro, however I don't know if this could be the cause.
Only other option I can see is unroot/flash stock FI27 and see what happens, but I really don't want to go through the hassle, especially having to get another effing phone (since assurion can't be bothered to ever send a proper working phone)
bit of info on my phone I guess
Rooted it from bone stock factory FI27 using Odin FI27 One click rooting (success on first try)
Agats source 6.5 kernel
_dan's Lightweight v0.2 rom
Ktoonservative kernel (however it seems every kernel does this)
Scheduler set to noop
no oc/uv settings currently
I use System Tuner Pro to adjust clocks/governor settings, etc however, I haven't done many tweaks besides my OOM settings.
Stock rooted with Agat's source 6.5 was causing reboots as well, under the same conditions (deep sleep reboots, and waking from deep sleep)
m4xwellmurd3r said:
I've had this E4gt for a few days now. First thing I did was root it with the FI27 Odin one click method, then install Agats source 6.5 kernel. Had some random reboots that I shrugged off as my phone not liking any undervolting. But it still does it, even under _dan's lightweight v0.2 rom
It isn't completely random though. Most of the reboots are when I'm trying to wake up the phone after letting it sit idle. Other times it'll reboot while it's sleeping idle. it has NEVER rebooted during use (I ran pandora/poweramp for 8 hours no problem)
It also occurs under most governor settings.
It almost seems that for whatever reason, idling at 200mv is causing the phone to crash and reboot.
the only overclock utility I use is System Tuner Pro, however I don't know if this could be the cause.
Only other option I can see is unroot/flash stock FI27 and see what happens, but I really don't want to go through the hassle, especially having to get another effing phone (since assurion can't be bothered to ever send a proper working phone)
bit of info on my phone I guess
Rooted it from bone stock factory FI27 using Odin FI27 One click rooting (success on first try)
Agats source 6.5 kernel
_dan's Lightweight v0.2 rom
Ktoonservative kernel (however it seems every kernel does this)
Scheduler set to noop
no oc/uv settings currently
I use System Tuner Pro to adjust clocks/governor settings, etc however, I haven't done many tweaks besides my OOM settings.
Stock rooted with Agat's source 6.5 was causing reboots as well, under the same conditions (deep sleep reboots, and waking from deep sleep)
Click to expand...
Click to collapse
Is the phone new or did you acquire it used? I had random reboot issues...tried numerous software fixes (new ROM, new kernel, uninstalling apps). Finally found the problem...a faulty power button. The solution for me was to replace the phone under warranty.
Its an assurion refer. According to the phones lifetime stats however it wasnt used for more than a week or so in august.
Also its not the power button. I watched it lock up and reboot earlier today
I'm almost thinking I should call asurion and tell them they sent me another effed uup phone and demand a nib phone. But that means unrooting this one and I'm not sure how big of a pain that will be
Sent from my SPH-D710 using xda premium
Ktoon... gov gave me some odd results too, try pegasusq and don't under volt until you have established a stable setup.
Honestly though try a different rom, FI27 seemed buggy to me but FI03 was alright. If you want to try Jellybean then give Codename a try. Its been rock solid.
someguyatx said:
Ktoon... gov gave me some odd results too, try pegasusq and don't under volt until you have established a stable setup.
Honestly though try a different rom, FI27 seemed buggy to me but FI03 was alright. If you want to try Jellybean then give Codename a try. Its been rock solid.
Click to expand...
Click to collapse
Interesting that you would mention ktoonservitive!
My setup has been always dead stable. But....
I've had a few random reboots when on calls lately and have been running that (ktoon..) for a little while now.
I'll have to switch that out and see what happens.
Well im currebtly running the latest version of recaulk so ill report back with my results if i gwt any reboots.
Sent from my SPH-D710 using xda premium
m4xwellmurd3r said:
Well im currebtly running the latest version of recaulk so ill report back with my results if i gwt any reboots.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
After running Re-Caulk all night, I've come to the conclusion that FI27 was the culprit.
Ktoon probably wasn't helping, as I was running it quite often.
I'm using whatever kernel comes with re-caulk, min at 100mhz, max at 1400mhz, -25mv. Battery life is better than before (though, with my 3800mah battery, its already insane)
buttery smooth goodness too
Bit of an update since I made this thread.
Running smartbench 2011 I was getting abysmall productivity scores, and it seemed overall my scores were AWFUL no matter what in any benchmark (overclocking to 1.5 would barely get the almost to baseline numbers)
I called asurion and told them I was having reboot issues with the phone etc, they sent me another refurb today.
Scores are exactly as they should be now. Productivity scores in smartbench 2011 went from 2500-2800 to 4000+
I think the CPU on my first e4gt had a problem with the processor, which is why deep sleeping was crashing it.
I do realize benchmark scores mean nothing in terms of real world performance, but when there's a known baseline number for a particular phone, and your phone is struggling to even get close to that baseline (even with a maximum overclock) there is clearly something wrong with it.