Random reboot. Help appreciated! - Samsung Galaxy Nexus

Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.

Petrovski80 said:
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.
Click to expand...
Click to collapse
For some reason, when I cleared the cache and dalvik, It doesn't seem to reboot anymore. But if it ever happens again, I'll do what you told me
Thanks!

Hi, this happened again today, but I noticed that it isn't a full reboot. (no Google splash screen)
Any ideas?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Related

Which kernel should I have if I just want OC?

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.

Data Disconnects after sleep?

I have an issue with any custom ROM's I've tried, when the phone sleeps my cell radio turns off and I cant receive phone calls, sms's and the like.. The service comes back after a minute of having the screen on, but its a real hassle. I dont have this issue with either of the stock roms, both 4.0.1 and 4.0.2 but anything custom causes me issues.. I wipe data, cache and dalvik and take care not to install any apps and the issue still arises.. I noticed there are a few other people having similar issues, but unlike them I do not have to reboot to get my cell radio working and its not just data, I have also tried the gamut of radio's but I am hesitant to flash radios constantly since my understanding is flashing them has a greater risk to brick your phone should something happen. Does anyone know anything I could try? I dont understand how custom roms all do this but a stock one wont..
set minimum CPU frequency to 700 mhz.
also try other radios (UGLA4 works very well)... flashing a radio won't brick your phone as long as its for your phone.. which in this case, just dont flash I515 radios (verizon)
what rom? kernel?
yannisthegreek has a thread about this; not uncommon by the sounds of it.
Purely conjecture on my part, but I think it's a power issue, i.e. your phone isn't supplying the radio with enough power to kick start it from sleep. Basing this on the fact that a particular kernel (Fugo IIRC?) or upping your min freq to 700 seems to fix the issue. I've yet to experience this however.
I'm going to try setting it to 700mhz right now, I've flashed CM9, Modaco, Codename Android, Revolution, used the Kernel that was provided with those ROMS and Franco's and Trinity, I have also tried every radio as well with the same results.. it does make sense the way mudferret explained it and also explains why it will start up after my phones out of sleep mode and running faster, the weird thing is that this just happened one day, my phone was fine running a custom rom and Franco's kernel and then one day I notice that I had calls going right to voice mail..
So glad I found this thread. I've been dealing with the same issue. People tell me when they try to call they get a fast busy signal. If I wake my phone for about a minute everything works again. I am going to try Fugo IIRC? kernel and see what that does.
Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..
flindil said:
Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..
Click to expand...
Click to collapse
Glad to see it up and running. I never had this problem but I always had my minimum frequency set to 700 MHz because I think I heard franco say something about it helps battery blah blah blah... it was a while back but I don't remember the full details
Yeah, I read that he said the difference on battery use was negligible.. that could have been why custom ROMS and kernels were working for me previously.
Sent from my Galaxy Nexus using xda premium
I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...
bk201doesntexist said:
I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...
Click to expand...
Click to collapse
What's the voltage differential between the 350 and 700 slots, if any?
Edit: I ask because I can't see my voltages on my current kernel
Have same problem post 4.0.4 update
I started seeing this too after a manual 4.0.4 update to my GSM Nexus. The phone is still stock (and was prior to the flash) with ClockWorkMod the only thing added. Still troubleshooting.
----------------------------------------------------
UPDATE: Noticed that this does not happen while phone is being charged. I've tried playing around with a CPU speed program, but I haven't yet figured out if the settings are taking properly.

Nexus reverts to 700 mhz max CPU speed.

Ok so for the past 2 AOKP builds (the latest nightly and M1 both Jellybean) i have had this weird issue where upon boot, the CPU would be capped at 700Mhz. so i went into ROM control, set it to 1200 and made sure "set on boot" was on.
eventually, even without a reboot, it woud revert back to 700 MHZ. so i checked my other apps that can controll OC/UC. Franko kernal app, and ROM toolbox were both set at 1200 and not set on boot. so ROM control was in charge of the CPU.
yet, no matter what i do, after about 4 hours on use it reverts back to 700 mhz.
this happened on the included Faux kernel and Franko's latest milestone kernel.
anyone else experiencing this? know what causes it?
On CNA and get the same thing. It's horrible because it will lock up my phone.
Bumping Cuz it happened again. This is the most annoying thing I have come across.
Some of these phones are really picky. Try another rom and see if the problem persists.
tgyberg said:
Some of these phones are really picky. Try another rom and see if the problem persists.
Click to expand...
Click to collapse
*whimpering* b...b....but... I.. like this rom...
BTW, I am on CNA with popcorn kernel which is different than the op so I feel like it's a deeper issue.
CNA kangs literally everything from everyone (not saying that in a derogatory sense).
AOKP has this bug as well, and I'm sure it's being worked on on their side...which CNA will then cherry pick.
I had this before,Download nofrills cpu from play store and set the desired freq,your problem will
Be solved.
Sent from my Galaxy Nexus using Tapatalk 2
I've been using CNA 3.5 and had no problem with the max CPU setting to 700Mhz until i started playing around with all of the settings in the start-up tweaks, Kernel controls, color hack presets, and color gamma tuning. I changed all of the settings back to default and have not had the issue since then (18 hours). I have slowly started enabling all of the tweaks one at a time to see what was causing the max CPU to set at 700MHz.
max boot speed to 700mhz is defined in init.tuna.rc, if i recall it correctly.
Sent from my i9250
tried changing the kernel !
I used CNA 3.5 and 3.6.6 Still the same issue.
Tried Trinity Kernel too it did help for sometime but still it reverts back to 700mhz..
Is there any fix yet.... I really Love CNA so i prefer to stay on this rom.
My friend using PARANOID ANDROID has never experienced such an issue.
Hope it is fixed soon
Thanks
I'm having the same issue on CNA 3.6.6. Even when I set it back to 1200mhz it still never goes above 700 mhz.
I'm having the same problem. On CNA 3.8 right now, but have had the same problem on other custom rooted ROMs based off of cm. I finally figured out that it reverts back to 700 MHz during phone calls--or maybe not every phone call, not sure on that part. All my calls recently have bumped it down. At least now I know when it's switching. Just installed the no frills cpu--hopefully that'll help until this bug gets fixed.

[Q] Trinity Kernel settings

I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
I had similar issues. Not flowing very well , reboots and crashes. Also even though I bought the trinity app changing the clock speeds made the phone very very unresponsive. Tried many times to install it but no luck. Swapped back to Franco / glados (tried air kernel which was nice for battery but a bit laggy)
Franco also has trinity settings you can play with
J
Sent from my Galaxy Nexus using xda app-developers app
Me personally had a better experience than Franco. But all the phone are different and some might like trinity and some might like Franco. Seems like yours like Franco more
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
Personally I've had ridiculously good results with Trinity - with 384 GPU, not 512 (1536-384-Stable35). Absolute butter even when I have very resource heavy, multiple, tasks running - and havn't had a forced reboot, freeze or anything of the sort even once. Interactive/SIO, min 307, max 1190. Everything else on default (except screen colours/gamma which I changed to my liking).
That said, if the 384 GPU is also not working for you I suppose you can give Franco or the other kernels a try, every phone set probably responds a little differently to each kernel.
cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
What trinity kernel are you using? I am on trinity 384 Alpha 56 and it is butter smooth... even get great deep sleep with it.
Sent from my Galaxy Nexus using xda app-developers app
cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
I have good flow with trinity kernels. No lag or unresponsivness
*Who needs a gs3 when you have a NEXUS*
simms22 said:
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
Click to expand...
Click to collapse
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i like ondemand/deadline. overheating.. whats your cpu temperature? most think that their devices are overheating when it falls in the normal range. tkt comes with widgets(in the app drawer widget menu), put the no background cpu temp widget on your homescreen and youll also get a cpu temperature reading in your status bar. at 100C the thermal throttle will kick in to lower your cpu speed and cool down your device. the safety shutdown temperature is 110C, your cpu will automatically shut down at that point. 110C is only reachable if you turn off the thermal throttle in the tkt app and you are benching your phone at a high oc. otherwise, i wouldnt worry about overheating.
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
cmstlist said:
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
Click to expand...
Click to collapse
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Despite the fact that I disabled "Set On Boot" in Trinity Kernel Toolbox, it does seem I'm still set to interactive/sio on boot. And check out the logcat I captured over USB when I was doing a reboot and it locked up:
http://pastebin.com/sSe9eFXT
In particular to trim out just the TKT lines and the last few lines before lockup:
Code:
D/TKTBootHelper( 1853): TKT: Boot Completed
D/TKTBootHelper( 1853): TKT: Set file permissions.
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
D/TKTBootHelper( 1853): Current Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): Previous Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): TKT: Versions match, let's restore settings.
E/vpnapi ( 1672): Function: Connect File: AndroidIPCSocket.cpp Line: 172 failed
to connect fd=38: Connection refused
E/vpnapi ( 1672): Function: Run File: LocaleChangeMonitor.cpp Line: 140 Invoked
Function: AndroidIPCSocket::Connect Return Code: -26476533 (0xFE6C000B) Descrip
tion: ANDROIDIPCSOCKET_ERROR_CONNECT_FAILED
So it would seem that right after TKT says "let's restore settings" it locks up, if the screen is off, when set to interactive/sio. Huh?
simms22 said:
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Click to expand...
Click to collapse
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
cmstlist said:
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
Click to expand...
Click to collapse
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
simms22 said:
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
Click to expand...
Click to collapse
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
does your rom have its own cpu settings? maybe theres something enabled in there?
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
smart reflex is a built into stock, it controls your voltages. the thing about it is that it doesnt know overclock or undervolting, so if you overclock or undervolt, it restores voltages for stock cpu speeds. which causes freezes if youre trying to overclock by setting the voltages too low.
simms22 said:
does your rom have its own cpu settings? maybe theres something enabled in there?
Click to expand...
Click to collapse
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
simms22 said:
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
Click to expand...
Click to collapse
No I do not. I will try reinstalling now since I uninstalled it completely.
morfic said:
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Again, pure stock flashed straight from Google, except for Trinity.

[Q] Random Reboots driving me crazy

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.

Categories

Resources