Related
Hi,
i have an Italian version of i9000 with jf5 firmware.
I have upgraded whit samsung kies my firmware.
now i have
pda xwjm3
phone xxjm2
csc itvjm1
now sometime my phone goes off
anyone have the same problem?
i read that this is a bug......
You read its a bug? Of course it's a bug.
It's either a bug with the firmware or with an application. I had the same problem when using SetCPU.
Sent from my GT-I9000
i have setcpu me too.
so the problem is this app?
just uninstall it?
I experienced it (no response completely unless I reinsert the battery) when with lag fix and GPS on, regardless eclair or froyo ROM.
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
I have a feeling that the problem was due to GPS or due to the 0513 pit, but I'm not sure - so far it's been okay so I bother not to break it for tests.
SetCPU shuts my device down... out of nothing...
i uninstalled setcpu and never happened again
mystaka said:
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
Click to expand...
Click to collapse
Slightly off-topic but... That'd actually be an overclock if I'm reading those numbers correctly. The default frequency is 1000/100mhz with a conservative setting, meaning it'll try to be as low as possible more or less. What you've done is set min-frequency to 400mhz, which in my book is an overclock from the stock 100mhz.
Back to semi on topic... SetCPU is known to cause problems on Galaxy S, and likely other devices aswell. Most problems has been more specifically caused by using ondemand setting when setting up profiles - for some reason the phone doesn't handle this setting well when it wakes from sleep.
I'm pretty sure I managed to get it working more or less flawlessly with an screen off profile at 400/100 with Conservative setting, though I reflashed shortly after those settings so never got to test it properly. Regardless, they might work if you want to mess about with it.
I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.
gettons said:
I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.
Click to expand...
Click to collapse
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100
insty said:
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100
Click to expand...
Click to collapse
Great!This work
Thank you
I don't use setcpu but I have this problem in my two SGS. Using m5 and m6..
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Only thing anyone can probably suggest is turning up your min clock speed. What are your profiles set to?
My screen off is 245/368 just to give it that bit extra to guarantee no wakeup issues, not that I had any to begin with, better safe than wanting to throw her up the wall (I get annoyed easy).
bahmanxda said:
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Click to expand...
Click to collapse
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Possible explination posted here by rmk40:
http://forum.xda-developers.com/showthread.php?t=884237
dhkr123 said:
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Click to expand...
Click to collapse
Thanks
no i didnt make any customization its just CM6.1 although my max clock speed is at 1497 mhz
setCPU
Screen off max 368
min 245
and profiles for temp and battery as well
the wierd thing is it doesnt happen at all when im just waking the phone up it only happens when its ringing i am thinking its my CPU issue ,i dont think it handles overclocking well ,i couldnt go over 1.1ghz (it would freeze instantly) with virouos that was the main reason i switched im gonna play with with cpu profiles for a while and see if i can get it fixed.
btw i have never flashed any radio so im guessing its the stock one
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
bahmanxda said:
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
Click to expand...
Click to collapse
With my experience I've noticed the phone runs better, and lasts longer on a single charge WITHOUT setCPU profiles. Just my opinion
bahmanxda said:
although my max clock speed is at 1497 mhz
setCPU
Click to expand...
Click to collapse
And there you have it. Overclocking can do weird things.
dhkr123 said:
And there you have it. Overclocking can do weird things.
Click to expand...
Click to collapse
Fair enough
Sent from my HTC Vision using XDA App
Hi All,
After being a long time iPhone user i recently purchased htc one x, as a result my android skills are almost non-existent; so please bear with me.
I managed to flash clockworkmod recovery and rooted with SuperSU with no issues.
Purchased setCPU after reading the reviews and enabled. However the phone would reboot randomly a few times a day. Ususally when the screen was off.
After disabling setCPU there was no rebooting issue.
Has anyone got this app to work on the OneX, and if so which settings did you use?
Also has it been confirmed to work with all 4 cores?
FYI I had the following profiles setup.
Screen Off
Freq:640Mhz-51Mhz
Gov: conservative
Temp > 44.5
Freq:880Mhz-51Mhz
Gov: conservative
Battery < 30%
Freq:1000Mhz-51Mhz
Gov: powersave
Charging Any
Freq:1500Mhz-51Mhz
Gov: ondemand
Please note these profiles are based on no evidence, just on what I estimated to be about right...
Cheers
I did not start using SetCPU on my phone yet because it's not rooted, but first I would check if SetCPU doesn't require some kernel support? and if that's implemented in the custom ROM you're using? (if it's needed, I'm not sure).
Or maybe SetCPU needs an update to properly support our phones?
That Temp > 44.5 Profile, wouldn't that interfere with gaming? I have never used Temp profiles before (is it really needed?), only the other ones, like battery and screen-off and charging.
my one x has unlocked bootloader, recovery and root. I was running into some serious intermittent lagging issues, the phone in any app would just stall for 5+ seconds. after hours restoring after failure , it came down to the problem that using ANY cpu controll app, messed my phone up... BADLY! it seems at the moment (im assuming) apps like setcpu and cpu master are not quad core ready...
thanks for the responses guys.
I guess ill just wait until one of the devs can confirm this as working...
The reason is simple. We don't have rooted kernels yet. Until then stay away from messing with CPU speeds or under volting. Etc.
Sent from my HTC One X using xda premium
skywalker1970 said:
The reason is simple. We don't have rooted kernels yet. Until then stay away from messing with CPU speeds or under volting. Etc.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
+1
DO NOT mess with your CPU speeds yet. Undervoltage is causing reboots!
the software is not up to the hardware capability, i dont think the cpu control apps can handle quad core yet. and there is a lot of apps (esp. games) that lag a lot, and amazingly the cores are too lazy to work... im hoping for a better kernel that will address this issues.
If you want to at least see what's going on with the cores, I can confirm that Tablet CPU Usage Monitor works on HTC One X
It shows 2 icons in notification bar, each icon showing usage of 2 cores. Not sure how accurate it is, but so far had no problems with it and it seems to be reporting correctly. Developer is working on single icon with all 4cores in it, to save space.
I had the same problem, but if you delete your profiles you won't get reboots.
I'm just running default profile Max: 1500, Min: 760 Ondemand gov. and it has been a straight line for 6 hours when I was sleeping and no reboots.
jakejay said:
Hi All,
After being a long time iPhone user i recently purchased htc one x, as a result my android skills are almost non-existent; so please bear with me.
I managed to flash clockworkmod recovery and rooted with SuperSU with no issues.
Purchased setCPU after reading the reviews and enabled. However the phone would reboot randomly a few times a day. Ususally when the screen was off.
After disabling setCPU there was no rebooting issue.
Has anyone got this app to work on the OneX, and if so which settings did you use?
Also has it been confirmed to work with all 4 cores?
FYI I had the following profiles setup.
Screen Off
Freq:640Mhz-51Mhz
Gov: conservative
Temp > 44.5
Freq:880Mhz-51Mhz
Gov: conservative
Battery < 30%
Freq:1000Mhz-51Mhz
Gov: powersave
Charging Any
Freq:1500Mhz-51Mhz
Gov: ondemand
Please note these profiles are based on no evidence, just on what I estimated to be about right...
Cheers
Click to expand...
Click to collapse
I was having that problem too... In my opinion, I don't think that the phone can handle the Conservative governor setting. I set my governor to Interactive (On Demand works too)
Right now, I have my profile set to 1000mhz max and 475mhz min, with screen off profiles set to 475mhz max and min. I have not had any problems with the phone rebooting at all since setting those freqs. (And I don't want to quite go any lower yet). And I have it Set on Boot.
im now using rooted HTC One X(HOX) and installed RD-MIUI ROM quite sometimes. my kernel is still in stock. Im using setcpu and NO random reboot happen like what you have said. Yet, i am still confuse whether setcpu is good for my phone. based on my review, in the leading rom developer thread they not mention setcpu for their choice. they play alot with kernels to govern their hox cpu-s. could anyone do some comment.
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Did you try wiping everything on the phone and starting fresh. Go in the Android Revolution thread and run the superwipe script and wipe again then reinstall everything see if that helps.
I didn't look at the logcats, too tedious.
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
clarkey1269 said:
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Click to expand...
Click to collapse
Does this happen on stock. This logcat is using franco's kernel, are you UV'ing? OC'ing? Smartreflex? I don't know if actually Francisco is using official stock voltages today, or is already uv'ing a little from source.
And I just finished going through your log, there's nothing useful there; you should be getting it while it happens, or better yet would be /proc/last_kmsg immediately after the reboot; Grab it like this, for example:
Code:
adb shell cat /proc/last_kmsg > last_kmsg_on_my_pc
Also, what you're experiencing is called Sleep of Death.
chopper the dog said:
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
Click to expand...
Click to collapse
also happens on ICS not just JB
full wipe is taken out with every flash or nightly update without fail.
even did a fresh start with locking and relocking the bootloader with no effect i still get the annoying wake
Are you using any app to control your min CPU voltage? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU voltage is too low...
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
bk201doesntexist said:
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
Click to expand...
Click to collapse
Sorry I meant to say voltage
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
cayte2 said:
Sorry I meant to say voltage
Click to expand...
Click to collapse
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
bk201doesntexist said:
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
Click to expand...
Click to collapse
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
clarkey1269 said:
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
Click to expand...
Click to collapse
Does it happen when using google's factory image?
Do you have Eugene cpu sleeper installed? I was having that happen to mine and I just uninstalled, wiped caches, fixed permissions and I haven't had a problem since.
Sent from my Galaxy Nexus using xda premium
bk201doesntexist said:
Does it happen when using google's factory image?
Click to expand...
Click to collapse
fresh instal of googles stock image and il report back
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.