Hi
Sorry cant post in the development thread since i just joined.
Using TS1700-GPUOC-4.1.2-mr1-fr-ALPHA12 with CM10 causes Nexus 7 to Freeze/crash and reboot when you remove a USB pen drive or 2.5 harddrive that is connected with a OTG cable. It happens if you do a dismount from settings/storage or just pull the cable OTG cable out.
Otherwise its a very good kernel for Nexus 7.
/cazrack
cazrack said:
Hi
Sorry cant post in the development thread since i just joined.
Using TS1700-GPUOC-4.1.2-mr1-fr-ALPHA12 with CM10 causes Nexus 7 to Freeze/crash and reboot when you remove a USB pen drive or 2.5 harddrive that is connected with a OTG cable. It happens if you do a dismount from settings/storage or just pull the cable OTG cable out.
Otherwise its a very good kernel for Nexus 7.
/cazrack
Click to expand...
Click to collapse
Finally! I could Kiss you!! I wont don't worry.... at least however a manly high five will do. I am having this issue since using the Trinity Kernel and like an idiot never once though it was the Kernel. Strange how the units will still turn off even if you just plug and unplug in the OTG cable with nothing plugged into the cable itself. So we think it is the Kernel then?
Casanub said:
Finally! I could Kiss you!! I wont don't worry.... at least however a manly high five will do. I am having this issue since using the Trinity Kernel and like an idiot never once though it was the Kernel. Strange how the units will still turn off even if you just plug and unplug in the OTG cable with nothing plugged into the cable itself. So we think it is the Kernel then?
Click to expand...
Click to collapse
Yes, 100% certain its kernel related.
When you run CM10 updater from inside CM10 and a new nightly build gets installed it removes Trinity kernel and install the default CM10 kernel and that makes the problem go away.
After you flash Trinity kernel back you get the freeze and crash/reboot issue again.
If you use this Kernel, please contact morfic. check his site below for email and other contact information.
derkernel.com
(sorry no real link, just joined.)
/cazrack
cazrack said:
Yes, 100% certain its kernel related.
When you run CM10 updater from inside CM10 and a new nightly build gets installed it removes Trinity kernel and install the default CM10 kernel and that makes the problem go away.
After you flash Trinity kernel back you get the freeze and crash/reboot issue again.
If you use this Kernel, please contact morfic. check his site below for email and other contact information.
derkernel.com
(sorry no real link, just joined.)
/cazrack
Click to expand...
Click to collapse
Thank you Cazrack. I will email him now, I can imagine he will be inundated with emails
Another two quick questions "sorry" with Trinity, do you use setcpu to overclock or do you find the kernel gives you all the speed you need? secondly have you had the issue of the unit turning off on an overnight charge? I do not do this normally but I fell asleep with it plugged in and found in the morning it was turned off, when I turned it on it was at 100% so thought is might have turned off as a safety feature but just wondering if you experienced this or heard of it happening?
Thank you again for you help.
The same thing happens to me with the Trinity kernel but it also happens with LeanKernel for 4.2. It did not happen with LeanKernel for 4.1.2, so I don't think it is just a kernel only issue. It doesn't happen on the stock kernel, M-Kernel+, or Franco r30.
O2Blevel said:
The same thing happens to me with the Trinity kernel but it also happens with LeanKernel for 4.2. It did not happen with LeanKernel for 4.1.2, so I don't think it is just a kernel only issue. It doesn't happen on the stock kernel, M-Kernel+, or Franco r30.
Click to expand...
Click to collapse
Cheers for the response, always good to know its not the hardware . Defo a Kernel issue, I have emailed derkernel.com, I am sure we should have a fix soon, otherwise it aint that much of a big issue.
Casanub said:
Thank you Cazrack. I will email him now, I can imagine he will be inundated with emails
Another two quick questions "sorry" with Trinity, do you use setcpu to overclock or do you find the kernel gives you all the speed you need? secondly have you had the issue of the unit turning off on an overnight charge? I do not do this normally but I fell asleep with it plugged in and found in the morning it was turned off, when I turned it on it was at 100% so thought is might have turned off as a safety feature but just wondering if you experienced this or heard of it happening?
Thank you again for you help.
Click to expand...
Click to collapse
I keep the stock clock speed 1.3 ghz but I use setcpu to set certain programs to scale to 1.7 ghz.
For example webbrowsers benefit from 1.7 ghz in faster loading and smoothness.
overclocking for games i prefer to run cpu stock and have my gpu overclocked to 600 mhz.
stock gpu is 416 or 418 mhz.
cant overc to much during long gaming sessions since it get to hot and gpu oc give more than cpu.
when i used franco kernel r25 the power off thing happend to me too.
only 1 night during charging but i flashed a new kernel after that.
/cazrack
cazrack said:
I keep the stock clock speed 1.3 ghz but I use setcpu to set certain programs to scale to 1.7 ghz.
For example webbrowsers benefit from 1.7 ghz in faster loading and smoothness.
overclocking for games i prefer to run cpu stock and have my gpu overclocked to 600 mhz.
stock gpu is 416 or 418 mhz.
cant overc to much during long gaming sessions since it get to hot and gpu oc give more than cpu.
when i used franco kernel r25 the power off thing happend to me too.
only 1 night during charging but i flashed a new kernel after that.
/cazrack
Click to expand...
Click to collapse
Ah I see I have done the same it works very well. However you mentioned overclocking the gpu to 600mhz how is this achieved? its not an option in setcpu, suppose the programe is called setgpu
I think I will stick with the the Trinity as the OTG restart is not that much of a issue really. I am sure derkernel will have an update soon.
Casanub said:
Ah I see I have done the same it works very well. However you mentioned overclocking the gpu to 600mhz how is this achieved? its not an option in setcpu, suppose the programe is called setgpu
I think I will stick with the the Trinity as the OTG restart is not that much of a issue really. I am sure derkernel will have an update soon.
Click to expand...
Click to collapse
yes you can OC the gpu for better gaming fps on some kernels.
for example Trinity kernel and Franco kernel allow this if you use franco.kernel.updater from google play store.
i have tested 700 mhz but but during long gaming sessions with games pushing the gpu hardware like spiderman it just get to hot.
484 and 520 mhz is considerd very safe from the information i gatherd.
600 should work even for longer gaming sessions but the device will be warmer.
650 i will test this but im sceptical about long gaming sessions.
750 some crazy people run this....
at the moment im using cpu gov ondemand in setcpu with value 50 in cpu scaling.
have you tried the elite kernel? 1.8 ghz cpu 650 mhz gpu..
/cazrack
cazrack said:
yes you can OC the gpu for better gaming fps on some kernels.
for example Trinity kernel and Franco kernel allow this if you use franco.kernel.updater from google play store.
i have tested 700 mhz but but during long gaming sessions with games pushing the gpu hardware like spiderman it just get to hot.
484 and 520 mhz is considerd very safe from the information i gatherd.
600 should work even for longer gaming sessions but the device will be warmer.
650 i will test this but im sceptical about long gaming sessions.
750 some crazy people run this....
at the moment im using cpu gov ondemand in setcpu with value 50 in cpu scaling.
have you tried the elite kernel? 1.8 ghz cpu 650 mhz gpu..
/cazrack
Click to expand...
Click to collapse
Okay I see it comes full circle, I will give it a bash.
The elite was going to be my next kernel... only reason for using Trinity was, I was advised to do so as a first try. It might be the next step to get rid of the OTG restart and of course the 650 mhz gpu stock oc. Have you tried it or going to try it?
Casanub said:
Okay I see it comes full circle, I will give it a bash.
The elite was going to be my next kernel... only reason for using Trinity was, I was advised to do so as a first try. It might be the next step to get rid of the OTG restart and of course the 650 mhz gpu stock oc. Have you tried it or going to try it?
Click to expand...
Click to collapse
is it supposed to work with cm10? ive tried to flash it but it didnt seem to flash in good
because trinity animation still showing after flash... but nexus isnt booting up.
no problem just boot into recovery and reflash trinity kernel or a cm10 rom.
any clue?
prehaps reflash elite when you have updated to a 100% cm10 nightly installed.
/cazrack
cazrack said:
is it supposed to work with cm10? ive tried to flash it but it didnt seem to flash in good
because trinity animation still showing after flash... but nexus isnt booting up.
no problem just boot into recovery and reflash trinity kernel or a cm10 rom.
any clue?
prehaps reflash elite when you have updated to a 100% cm10 nightly installed.
/cazrack
Click to expand...
Click to collapse
Sounds strange did you delete the cache? As I had that issue originally? I am just using stock ROM tbh as it seems to be the most responsive at the moment but I have not tried them all obviously
Suppose we best keep on keeping and seeing if the smart devas can release a fix.
Casanub said:
Sounds strange did you delete the cache? As I had that issue originally? I am just using stock ROM tbh as it seems to be the most responsive at the moment but I have not tried them all obviously
Suppose we best keep on keeping and seeing if the smart devas can release a fix.
Click to expand...
Click to collapse
I think i did, but i will try again. Could be that extreme kernel is not compatible with cm10?
I would like to try to OC cpu even more up to 2 ghz would be intresting but i dont think there is such a kernel to download.
Once i reach 10 posts ill post in XDA Trinity developer thread
/cazrack.
Related
Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??
mike21pr said:
Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??
Click to expand...
Click to collapse
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel
Freek91 said:
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel
Click to expand...
Click to collapse
im using faux right now. ill see if i can find another one thats good to try out
thnx
i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board
mike21pr said:
i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board
Click to expand...
Click to collapse
well like im sure you've seen or heard...all hardware is different
so while 1.8ghz maybe slow...going down to 1.5 maybe quick and the opposite maybe true for someone elses phone...they may just totally fly at 1.8 while they grind to a halt at 1.5
so keep messing with it and see what happens...change clock speeds...change up the governors...just dont OC it to 1.8 and think the phone will magicly hit a 4100 quadrant and not have any issues
worse case...flash a different kernel and see how it acts
also on that topic...you said you were running IG...did you run the stock kernel for any length of time? did you try and OC that one?
Hi all,
I tried lots of combinations to OC my i9023, without any results.
I currently have CM10.1 Nighly + Marmite 7.3.1, which actually seems to be the fastest combination for me.
Btw, if I try to OC to 1096 or 1320 it starts rebooting.
Everyone said me to raise voltage.
I'm using NSTools and it appears that Marmite 7.3.1 already has higher voltage for 1096Mhz and 1320Mhz.
Furthermore, there are two settings: ARM Voltage and Interal Voltage. Should I increase both of them?
Are there other people with 9023 which overclocked it succesfully? If yes, with which tool and voltage settings?
Thank you
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
mikekir97 said:
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
Click to expand...
Click to collapse
With that voltage @1500 you will probably burn the cpu fast...i think. Maybe someone with better knowledge can advise you. But i wouldn't keep such a high voltage on my phone
mikekir97 said:
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
Click to expand...
Click to collapse
It really seems too much high...
Btw, which ROM and Kernel are you using?
mikekir97 said:
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
Click to expand...
Click to collapse
Which ROM and Which Kernel?
giaomnitel1 said:
Hi all,
I tried lots of combinations to OC my i9023, without any results.
I currently have CM10.1 Nighly + Marmite 7.3.1, which actually seems to be the fastest combination for me.
Btw, if I try to OC to 1096 or 1320 it starts rebooting.
Everyone said me to raise voltage.
I'm using NSTools and it appears that Marmite 7.3.1 already has higher voltage for 1096Mhz and 1320Mhz.
Furthermore, there are two settings: ARM Voltage and Interal Voltage. Should I increase both of them?
Are there other people with 9023 which overclocked it succesfully? If yes, with which tool and voltage settings?
Thank you
Click to expand...
Click to collapse
On marmite i've never been stable on OCs, even with raised voltages. On matr1x kernel you can do 1320mhz without raising voltages.
sidnoit22 said:
Which ROM and Which Kernel?
Click to expand...
Click to collapse
I am using Hellybean (the latest 26/2/13) and my kernel is Devils's kernel NOT the latest but the 21/12/12 release.. this kernel is my favorite.. try it out.. works on 4.1.x, 4.2.x.
migueldbr said:
With that voltage @1500 you will probably burn the cpu fast...i think. Maybe someone with better knowledge can advise you. But i wouldn't keep such a high voltage on my phone
Click to expand...
Click to collapse
I really don't care about burning my cpu. I have my photos backed up with dropbox.. and I'm on contract with my carrier so I will get it fixed within a week..
Is there an official thread/page for Hellybean and for the kernel?
giaomnitel1 said:
Is there an official thread/page for Hellybean and for the kernel?
Click to expand...
Click to collapse
There is a thread on XDA for the ROM Here.. For the kernel there is also a thread on XDA Here, but I don't think that you will find that specific version, just download it from my attachment above..
mikekir97 said:
There is a thread on XDA for the ROM Here.. For the kernel there is also a thread on XDA Here, but I don't think that you will find that specific version, just download it from my attachment above..
Click to expand...
Click to collapse
I have tried it and set it at 1320 (with LIVE OC 110%) and it seems stable.
Why do you suggest that particular version? Have you tried new versions and they are not stable?
giaomnitel1 said:
I have tried it and set it at 1320 (with LIVE OC 110%) and it seems stable.
Why do you suggest that particular version? Have you tried new versions and they are not stable?
Click to expand...
Click to collapse
I have tried all the new Devil kernels and they are stable for every day use but not as fast and battery save as the older version.. This is my opinion.. I have my nexus clocked at 1400Mhz and then apply 108% LiveOC witch took me to 1512.. Stable..! (at max arm volt 1500 mV)
I am experiencing lag on real racing 3, on high graphics. If I overclock to say 2ghz on cpu, will the tablet be stable enough? Should I undervolt ( and does it actually make any difference on temps)? I want to overclock but not at the cost of huge battery drain, can some1 recommend me a good kernel and some stable oc steps?
Sent from my Nexus 10 using Tapatalk HD
lvnatic said:
I am experiencing lag on real racing 3, on high graphics. If I overclock to say 2ghz on cpu, will the tablet be stable enough? Should I undervolt ( and does it actually make any difference on temps)? I want to overclock but not at the cost of huge battery drain, can some1 recommend me a good kernel and some stable oc steps?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Are you running a custom ROM and kernel? I play RR3 daily and have NO lag. AOKP PUB ROM with ktmanta kernel, at 1.7mhz CPU and GPU OC to 720. Runs great.
Most OC is safe, issues are really with battery and overheating. I've run for long periods at 1900 just fine.
So there's no way the tablet will melt down because of the heat? Does warranty cover that? Assuming they don't know it was overclocked, which they couldn't because the device would be dead, right? I guess they don't bother to repair it and see if it was rooted.
LE: btw did you manage to safely undervolt? Even a -5 gives me reboots on most freqs.
Any time I try to use the app from the store to set the graphics mode it causes problems. Running RR3 without it works fine.
lvnatic said:
So there's no way the tablet will melt down because of the heat? Does warranty cover that? Assuming they don't know it was overclocked, which they couldn't because the device would be dead, right? I guess they don't bother to repair it and see if it was rooted.
LE: btw did you manage to safely undervolt? Even a -5 gives me reboots on most freqs.
Click to expand...
Click to collapse
Take a look at the KTmanta thread. KTmanta is a great option for what you are after, he notes and codes distinctions between clocking and thermal protection, plus unless you lock the settings, they will reset at reboot!
If you tell Google you messed it up from some sort of tinkering, no - they won't help you.
lvnatic said:
So there's no way the tablet will melt down because of the heat? Does warranty cover that? Assuming they don't know it was overclocked, which they couldn't because the device would be dead, right? I guess they don't bother to repair it and see if it was rooted.
LE: btw did you manage to safely undervolt? Even a -5 gives me reboots on most freqs.
Click to expand...
Click to collapse
I am assuming you must be using the KTmanta kernel right? I thought it was the only kernel right now that allows for user control undervolting. Trinity has a static -50mv value set on all frequencies by default. You should be able to undervolt just about everything. Getting lockups at -5mv lets me think there is something you are not doing correctly
EDIT: threw the quote in so its less confusing
EniGmA1987 said:
I am assuming you must be using the KTmanta kernel right? I thought it was the only kernel right now that allows for user control undervolting. Trinity has a static -50mv value set on all frequencies by default. You should be able to undervolt just about everything. Getting lockups at -5mv lets me think there is something you are not doing correctly
Click to expand...
Click to collapse
Yes, the kernel
Edit: oops thought you were asking me, I see now I was confused.
Hi there,
I want to get the most performance out of my old galaxy s but i have a slight problem with 4.4.
I came from Slimbean android 4.3 on 1.2ghz because it worked really slow and gave me alot of problems.
I first flashed (After full wipe) to Mackay 4.4 rom but whatever govenor or sheduler i am using it crashes everytime after a minute or so doing some simple tasks from the slightest overclock (1.1 ghz).
So i flashed to CyanAOSP (full wipe) to see if it would fix the problem but the problem still exist on this rom :c
Is there something wrong with my device?
Greetings,
- Merlin
Taking the phone to pieces and applying thermal compound to the chips gave me another 100Mhz. (rock solid at 1200Mhz when 3D gaming etc). There are 2 chips underneath the motherboard, and if you remove the sim tray from the board there are another few under there. I did them all. Be very careful if you're using Arctic Silver. I would have preferred to use the cheap white stuff but I didn't have any. There is a thread if you search for it with instructions on how to do this if you need it.
And with overclocking there's an element of luck. There are variations in the manufacturing of the chips themselves which can make your particular phone good (or useless) for overclocking.
Sent from my GT-I9000 using Tapatalk
knuckles1978 said:
Taking the phone to pieces and applying thermal compound to the chips gave me another 100Mhz. (rock solid at 1200Mhz when 3D gaming etc). There are 2 chips underneath the motherboard, and if you remove the sim tray from the board there are another few under there. I did them all. Be very careful if you're using Arctic Silver. I would have preferred to use the cheap white stuff but I didn't have any. There is a thread if you search for it with instructions on how to do this if you need it.
And with overclocking there's an element of luck. There are variations in the manufacturing of the chips themselves which can make your particular phone good (or useless) for overclocking.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
But why could it do 1.3 ghz on android 4.3 easily? I think it has nothing to do with heat atm.
Because sometimes i can run antutu for 2 times in a row before it crashes. But sometimes it crashes instantly when i press the start button.
MerlijnD said:
But why could it do 1.3 ghz on android 4.3 easily? I think it has nothing to do with heat atm.
Because sometimes i can run antutu for 2 times in a row before it crashes. But sometimes it crashes instantly when i press the start button.
Click to expand...
Click to collapse
It's kernel related issues. I managed to clock in at 1.6Ghz rock stable on CM 10.2 but likewise, a 1.2Ghz overclock on 4.4 is giving me very rear soft reboots
MrAndroid12 said:
It's kernel related issues. I managed to clock in at 1.6Ghz rock stable on CM 10.2 but likewise, a 1.2Ghz overclock on 4.4 is giving me very rear soft reboots
Click to expand...
Click to collapse
Ah ok now that i know that, its probably going to get fixed sooner or later
Interesting. Mine is stable at 1.2Ghz on 4.4, so I'll be trying to push it a bit more when I get new kernels. I put Arctic Silver on all the chips the other day, even the ones under the sim card tray so hopefully that will help it. It has defo done something because my phone was unstable at 1.2Ghz before I did it.
Sent from my GT-I9000 using Tapatalk
knuckles1978 said:
Interesting. Mine is stable at 1.2Ghz on 4.4, so I'll be trying to push it a bit more when I get new kernels. I put Arctic Silver on all the chips the other day, even the ones under the sim card tray so hopefully that will help it. It has defo done something because my phone was unstable at 1.2Ghz before I did it.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I just flashed to semaphore kernel on mackay rom and it is fully stable on 1.3 ghz atm.
Is there a 4.4 semaphore kernel?
Sent from my GT-I9000 using Tapatalk
Guys , every kernel has its own custom voltages for over clocking . just use an app that controls the voltage (you can find one in play store ) and increase the voltage step by step until your phone is stable. For example : on Mackay I can't over clock not even to 1100 MHz with stock voltages without the phone rebooting after a few seconds but on Semaphore I can oc with stock voltages up to 1200MHz and its stable . on Mackay I messed around with higher voltages until I found the ones that my phone is happy with and I could oc up to 1300 MHz stable after that.
knuckles1978 said:
Is there a 4.4 semaphore kernel?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Yes there is , check the Semaphore thread for 3.4.0
Sent from my GT-I9000 using Tapatalk
I didn't realise that voltages were set in a kernel. Thanks
Do you know what voltages I should be using for a 1300 or 1400 overclock? I'm sitting stable at 1200 at the moment, how much do you think I should raise the voltage to keep it stable with another 100 or 200 MHz increase?
Edit: I'll try the 4.4 semaphore kernel
Sent from my GT-I9000 using Tapatalk
I personally use these settings:
Frequency - CPU - Int
1000MHz - 1225 - 1100
1200MHz - 1300 - 1100
1300MHz - 1350 - 1100
1400MHz - I've never got stable 1400MHz OC :/ (I think 1400 1150 should be right for most devices)
Optional:
1100MHz - 1250 - 1100 (some kernels have this step)
Thanks again, that's me running rock stable even under gaming at 1.3Ghz. Not tried 1.4.......yet lol
Why is there two voltage values you gave for each clock speed though?
I used setcpu, and set the first value. I'm not sure what the other value you gave is? GPU voltage?? Thx
knuckles1978 said:
Thanks again, that's me running rock stable even under gaming at 1.3Ghz. Not tried 1.4.......yet lol
Why is there two voltage values you gave for each clock speed though?
I used setcpu, and set the first value. I'm not sure what the other value you gave is? GPU voltage?? Thx
Click to expand...
Click to collapse
Second value is internal voltage (mostly used with LiveOC to stabilize as it gives voltage to GPU and RAM). With normal OC it should be at stock (1100mV). Some apps, like NSTools gives you opportunity to change those.
Normal OC affects CPU, and liveOC CPU, GPU, RAM, so it's more likely to be unstable. I can't reach 1100 on LiveOC, but on normal I have 1300 easily.
midnight911 said:
Second value is internal voltage (mostly used with LiveOC to stabilize as it gives voltage to GPU and RAM). With normal OC it should be at stock (1100mV). Some apps, like NSTools gives you opportunity to change those.
Normal OC affects CPU, and liveOC CPU, GPU, RAM, so it's more likely to be unstable. I can't reach 1100 on LiveOC, but on normal I have 1300 easily.
Click to expand...
Click to collapse
Ah well i am using stock voltages from semaphore kernel and 130% live oc. It is fully stable atm.
MerlijnD said:
Ah well i am using stock voltages from semaphore kernel and 130% live oc. It is fully stable atm.
Click to expand...
Click to collapse
Heh there are no two same devices. One overclocks better and one at all. There are devices which can't be overclocked. It's just luck you have with your hardware.
I just got my s7e yesterday. Found the guide on here how to root it. I did and it started having overheating issues so I downloaded kernel adiutor and put it on "on demand" as I saw posted somewhere else. This seems to work BETTER but my phone still keeps overheating frequently.
rkrajnov said:
I just got my s7e yesterday. Found the guide on here how to root it. I did and it started having overheating issues so I downloaded kernel adiutor and put it on "on demand" as I saw posted somewhere else. This seems to work BETTER but my phone still keeps overheating frequently.
Click to expand...
Click to collapse
My AT&T one was, too. I went back to stock. Faster and cooler (temp). Just gonna wait for a fix.
Yeah it doesn't matter what you set it too, it will overheat more then the stock.
my phone doesn't overheat at all. stock kernel uses interactive governor not ondemand. and you need to use an app that supports big.little CPU cores like kernel toolkit or ex kernel manager. set your big CPU cores to 2.1GHz and your little cores to 1.6k GHz. if you don't know about all this you guys probably shouldn't be rooting in the first place.
I was overheating also on pb6 firmware. Flashed pb8 and re-rooted, used kernel toolkit to set interactive and cpu cores to there min 300 something and 1500 for small and 2100 for large. Then flashed tekx. All is good now. Battery life is nowhere close to stock still.
xVermicide said:
my phone doesn't overheat at all. stock kernel uses interactive governor not ondemand. and you need to use an app that supports big.little CPU cores like kernel toolkit or ex kernel manager. set your big CPU cores to 2.1GHz and your little cores to 1.6k GHz. if you don't know about all this you guys probably shouldn't be rooting in the first place.
Click to expand...
Click to collapse
MegaNoob said:
I was overheating also on pb6 firmware. Flashed pb8 and re-rooted, used kernel toolkit to set interactive and cpu cores to there min 300 something and 1500 for small and 2100 for large. Then flashed tekx. All is good now. Battery life is nowhere close to stock still.
Click to expand...
Click to collapse
This is with using EX Kernel and big.little set to interactive. There is a problem with WiFi and some gaming that will heat this phone up hotter than hell itself.
CaptainMorgan said:
This is with using EX Kernel and big.little set to interactive. There is a problem with WiFi and some gaming that will heat this phone up hotter than hell itself.
Click to expand...
Click to collapse
And what firmware are you on? Did you also try flashing tekx? My phone doesn't heat up at all and WiFi is fine. Using pd8 and tekx. I had overheating but it's gone after a full wipe and flashing pd8 prior too rooting. It sounds like you just need to try again. I had problems also, it took a few tries.
If you use your phone for gaming you will see how much the phone heats up. If your using it from normal non heavy things it will be fine.
Well after switching to ex kernel, using TekX ROM, greenify, and L Speed, my phone is running almost perfect with great battery life.
rkrajnov said:
Well after switching to ex kernel, using TekX ROM, greenify, and L Speed, my phone is running almost perfect with great battery life.
Click to expand...
Click to collapse
Hello,
What do you mean by ex kernel?
umaro said:
Hello,
What do you mean by ex kernel?
Click to expand...
Click to collapse
He means the app, EX kernel manager.
umaro said:
Hello,
What do you mean by ex kernel?
Click to expand...
Click to collapse
Ex Kernel is an app that you can get from the play store.
https://play.google.com/store/apps/details?id=flar2.exkernelmanager&hl=en
xVermicide said:
my phone doesn't overheat at all. stock kernel uses interactive governor not ondemand. and you need to use an app that supports big.little CPU cores like kernel toolkit or ex kernel manager. set your big CPU cores to 2.1GHz and your little cores to 1.6k GHz. if you don't know about all this you guys probably shouldn't be rooting in the first place.
Click to expand...
Click to collapse
That's a ****ty response........remember when you were a noob? There was a lot you didn't know....don't bash people on the forum for trying or questioning what to do. You're a senior member. You probably should act like it and give the proper advice rather than saying one "shouldn't be rooting in the first place" I need to wear a condom just reading your post because of you being a **** on the thread.
...and there is slight heating, and major overheating when playing heavy games like dead effect 2 when you root. Even after the scripts and kernel tweaks. It's the engboot. Likes to be warm I guess
It's the trade off for now if we want root..
Sent from my SM-G935T using Tapatalk