Related
I've been a Nexus S owner for about a month now and it's the best Android phone I've owned so far. If it had an LED notification light and better build quality it would probably be perfect in my book. Anyways, the phone has been extremely fast for me. This is also the first Android phone I've had no interest in rooting because everything works as I want it to stock.
I'm just wondering, is it worth it to root and overclock this phone? Does overclocking really improve the speed that much? Also does Voodoo really give noticeable improvements to the sound and screen?
Arcadia310 said:
I've been a Nexus S owner for about a month now and it's the best Android phone I've owned so far. If it had an LED notification light and better build quality it would probably be perfect in my book. Anyways, the phone has been extremely fast for me. This is also the first Android phone I've had no interest in rooting because everything works as I want it to stock.
I'm just wondering, is it worth it to root and overclock this phone? Does overclocking really improve the speed that much? Also does Voodoo really give noticeable improvements to the sound and screen?
Click to expand...
Click to collapse
yes, yes, and a huge yes to voodoo sound
For me personally, my NS goes up to 1,4Ghz flawlessly and stable and in my (probably subjective) opinion, it did speed up the flicking through my large app drawer list, for example.
Basic things like browsing, texting, opening e-mails etc are pretty much the same, it's barely noticable. Probably because the stock NS is so fast and smooth, the few percents of added speed you gain by overclocking aren't really noticable.
The main thing is the battery life though, it'll drain the battery significantly and so it's up to you whether or not you want to have your phone running a tad faster but not make it through the day, or have it go normal and last the day.
I would always root your phone.
Since you mention the missing backlight notification, if you flash your kernel to say, for example, Netarchy 1.3.12, you can install a small app that's called "BLN". It turns the 4 buttons into a notification light by blinking them on notifications, works perfect.
Also, many people prefer CM7 over the stock Android because of the added functionalities; one more reason to root your phone
I haven't noticed anything about the voodoo sound/display, maybe someone else can pick in here.
Greetz
Trust me in that you will love your phone more if you do. I don't notice the change in speed but voodoo control is a must. You'll be able to adjust the colours on your screen to make your phone POP!
The badass thing about rooting it is that it fixes the notification light problem. All you have to do is flash a kernel with BLN compatibility (Nearly all of them have it) and download the BLN app from the market.
Every time you get a new notification the bottom four buttons flash on and off
Also like Simms said, you also get Voodoo colors which make the screen colors much much better then stock.
I personally don't overclock because like you said the phone is already so damn fast =)
Sent from my Nexus S
I do not overclock my CPU. I don't get any noticeable benefit from it (other than increased Quadrant scores). I tend the opposite way.... I'd rather reduce power for longer battery life, so I undervolt.
Voodoo is worth flashing a custom kernel for, in my opinion. Keep in mind you do not have to root to flash a custom kernel. You only have to unlock the bootloader with one simple command.
I know what you mean about not wanting to even root. I only rooted so I could take screenshots with Shoot Me app. But I use the stock Rom and probably always will
matt2053 said:
I do not overclock my CPU. I don't get any noticeable benefit from it (other than increased Quadrant scores). I tend the opposite way.... I'd rather reduce power for longer battery life, so I undervolt.
Voodoo is worth flashing a custom kernel for, in my opinion. Keep in mind you do not have to root to flash a custom kernel. You only have to unlock the bootloader with one simple command.
Click to expand...
Click to collapse
well, since the bootloader is unlocked, why doesn't root?! =oP
in my opinion, the bad thing in flashing things is because it is addictive, you can't stop anymore. I lived fine with stock for two months, and now i can't stay a week without flash something.
as a matter of fact, you can have voodoo sound in stock kernel, just use the pay app, and if you own a slcd version (like me), you won't need voodoo colors. So the missing and must have is BLN and that was the first reason i root this thing! =o)
and btw, for me, the device is fast enought and i really like to finish the day with my phone still alive, so i don't oc it! =o)
I have noticed that everyone seems to talk about bln but does no one like the no led app? It does well for me...just wondering because I'm new to the S but not android
alnova1 said:
I have noticed that everyone seems to talk about bln but does no one like the no led app? It does well for me...just wondering because I'm new to the S but not android
Click to expand...
Click to collapse
bln is universal (works in scld and samoled screens) and uses A LOT less battery than no led...
frutelaken said:
For me personally, my NS goes up to 1,4Ghz flawlessly and stable and in my (probably subjective) opinion, it did speed up the flicking through my large app drawer list, for example.
Basic things like browsing, texting, opening e-mails etc are pretty much the same, it's barely noticable. Probably because the stock NS is so fast and smooth, the few percents of added speed you gain by overclocking aren't really noticable.
The main thing is the battery life though, it'll drain the battery significantly and so it's up to you whether or not you want to have your phone running a tad faster but not make it through the day, or have it go normal and last the day.
I would always root your phone.
Since you mention the missing backlight notification, if you flash your kernel to say, for example, Netarchy 1.3.12, you can install a small app that's called "BLN". It turns the 4 buttons into a notification light by blinking them on notifications, works perfect.
Also, many people prefer CM7 over the stock Android because of the added functionalities; one more reason to root your phone
I haven't noticed anything about the voodoo sound/display, maybe someone else can pick in here.
Greetz
Click to expand...
Click to collapse
what is your setup to OC to 1.4? Currently I am running the I9020A at 1200 mhz on stock 2.3.4 with netarchy kernel, latest stable version. slightly over volted. however, it still freezes when i play videos with moboplayer. I havent been able to find a stable OC @ 1.4. It will reset and freeze overnight when idle
anyone else's input is welcome
thiagodark said:
bln is universal (works in scld and samoled screens) and uses A LOT less battery than no led...
Click to expand...
Click to collapse
This is truth. No LED does drain the battery quite a bit if you aren't able to dismiss a notification right away. That really hurt me a few times which is why after a few weeks I switched to BLN and haven't looked back.
Mudblood69 said:
what is your setup to OC to 1.4? Currently I am running the I9020A at 1200 mhz on stock 2.3.4 with netarchy kernel, latest stable version. slightly over volted. however, it still freezes when i play videos with moboplayer. I havent been able to find a stable OC @ 1.4. It will reset and freeze overnight when idle
anyone else's input is welcome
Click to expand...
Click to collapse
For my Phone i've never been able to handle 1.4 ever. I run mine at 1.3 and have no issues. Going to 1.4 makes my phone lock up. Every phone is different it seems.
For the record I'm running CM7 7.0.3 and Netarchy BFS 1.3.4.
Sent from my Nexus S using XDA Premium App
I was running Netarchy 1.3.0.2 BFS a few weeks ago. Without doing anything fancy, I could overclock to 1,4 using setCPU and it ran smoothly. I9023, GRI40 and CM7.
But, that kernel version doesn't support BLN so I had to upgrade and I chose the Netarchy 1.3.0.12 CFS and I have to admit (I just tested), I get lock-ups and reboots using 1,4 now.
Many people say it's device related, but I'm convinced the kernel has a lot to do with it as well. I don't know if BFS is the reason or not, it never ran stable on my device (even on stock speeds) and I'm much more satisfied with CFS's stability, but I think that's personal as well
Greetz
1.4 my phone just locks up.
1.2 and 1.3 are about the same for me: random reboots several times a day, with minimal if any noticeable improvement in performance in day to day activities.
Sent from my Nexus S using XDA App
I recently tried overclocking. I found that my phone can barely handle 1.2Ghz. Forget 1.4Ghz. I tried 1.1Ghz and it seemed stable enough but I didn't see any real world benefit from it. Right now I've settled on netarchy 1.3.4 bfs and cyanogen nightlies running at stock clock 1Ghz. Phone is stable, responsive, battery life seems good and voodoo sound is great.
Sent from my Nexus S using XDA Premium App
Trying overclocking now. Phone seems to handle even 1.4 pretty decently. Not noticing any problems. 3393 on Quadrant, nice and peppy. I don't know if the draw on batter life is really worth it. I'll probably drop back down to 1.2 max 400 min. That seems to be a sweet spot.
Running OpenSoju 0.2.6 with the included netarchy kernel.
Has everybody encountered after doing some intensive stuff like doing AnTuTu benchmark, the phone abruptly slows down to a crawl where animations slow down like rotation being damn slow, swiping through screens also is slow, and games being damn slow. For instance, I ran AnTuTu benchmark and it won't go higher than 30FPS. where usually it's 40 - 60 FPS.
This is not the typical lag I encounter.
The only way to solve this is to restart the phone. Sometimes restarting the phone once is not enough.
This sounds fishy. Never happened to me before. Although will try again once I download Antutu.
Edit: Just checked... Ran Antutu. Got a score of 6474. Everything seems fine. After quitting Antutu, scrolled through the homescreens. Everything was smooth as before.
Edit2: Ran Antutu again & got a score of 6502. Tried playing ShadowGun immediately afterwards. It ran without any hiccups...
Currently on KL8.
Livewings said:
Has everybody encountered after doing some intensive stuff like doing AnTuTu benchmark, the phone abruptly slows down to a crawl where animations slow down like rotation being damn slow, swiping through screens also is slow, and games being damn slow. For instance, I ran AnTuTu benchmark and it won't go higher than 30FPS. where usually it's 40 - 60 FPS.
This is not the typical lag I encounter.
The only way to solve this is to restart the phone. Sometimes restarting the phone once is not enough.
Click to expand...
Click to collapse
Turn off the power saving mode and you should notice a big improvement in lag.
I get around 56fps running AnTuTu with system power saving off.With power saving on,I only get 27fps.A big difference.
Could this be an overheating issue? Your cpu might be throttling coz of high temps.
Sent from my GT-N7000 using XDA App
Raghav1980 said:
This sounds fishy. Never happened to me before. Although will try again once I download Antutu.
Click to expand...
Click to collapse
This is not only because of AnTuTu, this only happens when I'm running an intensive app, where suddenly after exiting it will slow down to a crawl.
The most annoying part is the rotation animation. It is devastating slow.
noteworthy said:
Turn off the power saving mode and you should notice a big improvement in lag.
I get around 56fps running AnTuTu with system power saving off.With power saving on,I only get 27fps.A big difference.
Click to expand...
Click to collapse
Power saving mode was never turned on at the first place.
pandey18 said:
Could this be an overheating issue? Your cpu might be throttling coz of high temps.
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
I'm not sure because the phone also isn't hot at that time.
I haven't seen this issue either with benchmark apps or with intensive games. Might be an issue specific to your device. What rom is it running?
speedofheat said:
I haven't seen this issue either with benchmark apps or with intensive games. Might be an issue specific to your device. What rom is it running?
Click to expand...
Click to collapse
I'm currently on ROMOW 5.1, previously using ROCKET ROM since V9.
I never had this issue on Stock ROM's.
Both custom ROM's I used had this issue.
Livewings said:
This is not only because of AnTuTu, this only happens when I'm running an intensive app, where suddenly after exiting it will slow down to a crawl.
Click to expand...
Click to collapse
What sort of "intensive app"? Is it still running in the background?
If you have an app that uses a lot of memory, and then immediately try to use another memory intensive app, you may the OS begins to run low on memory as the garbage collector may not have run yet.
Regards,
Dave
foxmeister said:
What sort of "intensive app"? Is it still running in the background?
If you have an app that uses a lot of memory, and then immediately try to use another memory intensive app, you may the OS begins to run low on memory as the garbage collector may not have run yet.
Regards,
Dave
Click to expand...
Click to collapse
After playing GTA 3, Modern Combat 3, Asphalt 6, I will have this issue.
Killing the tasks on task manager won't help, neither cleaning memory.
Same problem
I have exactly same problem, my phone starts to lag randomly example in browser.
First its super smooth and then suddenly it kind of turns off gpu acceleration and starts to lag.
Even cm9 alpha doesnt have this problem so it's wery strange issue. And its there on every phone my friend also noticed it.
this is an issue with mali driver on note.
the gpu clock have two clockspeed that is 160mhz and 267mhz.
during that time when u run the benchmark the gpu clock to 160 and only utilise half of the mali power.
this had been explained by tegrak, creator of tegrak app.
the only solution is reboot and rerun the test or flash fm 2.0 that is clock min to 200mhz or flash tegrak kernel (can find at tegrak 2nd core in android dev forum) and use tegrak overclock app to lock the gpu to 267mhz.
Livewings said:
I'm currently on ROMOW 5.1, previously using ROCKET ROM since V9.
I never had this issue on Stock ROM's.
Both custom ROM's I used had this issue.
Click to expand...
Click to collapse
This is exactly I don't use ROMs other than CM. Eagerly waiting for CM9. Until then, I am happy with Stock.
deli_gt said:
I have exactlh same problem, my phone starts to lag randomly examble in browser.
First its super smoothand then suddenly it kind of turns off gpu acceleration and starts to lag.
Even cm9 alpha doesnt have this problem so it's wery strange issue. And its there on every phone my friend also noticed it.
Click to expand...
Click to collapse
We don't have the same problem. The browser thing I think everyone has that problem. Mine is a rare issue where it affects the entire OS.
nameejokerx said:
this is an issue with mali driver on note.
the gpu clock have two clockspeed that is 160mhz and 267mhz.
during that time when u run the benchmark the gpu clock to 160 and only utilise half of the mali power.
this had been explained by tegrak, creator of tegrak app.
the only solution is reboot and rerun the test or flash fm 2.0 that is clock min to 200mhz or flash tegrak kernel (can find at tegrak 2nd core in android dev forum) and use tegrak overclock app to lock the gpu to 267mhz.
Click to expand...
Click to collapse
Thank you, I believe you might be right. I'll try and report back.
Raghav1980 said:
This is exactly I don't use ROMs other than CM. Eagerly waiting for CM9. Until then, I am happy with Stock.
Click to expand...
Click to collapse
CM9 is awesome, but I can't live without the video player.
It is same problem i have exactly same impact, everything becomes lagyer. Same thing with every note.
The browser was only sample where you can notice it.
I can hereby confirm that Tegrak Kernel Build 31 is able to resolve the issue after setting the minimum GPU clock to 267mhz on Overclock Ultimate.
FM Kernel 2.0 doesn't solve the issue.
Is the phone hot after running this intensive app? The Note will guard itself against high temps.
zlagger said:
Is the phone hot after running this intensive app? The Note will guard itself against high temps.
Click to expand...
Click to collapse
One of my favorite things about the Note: No hotness!!! I had this issue all the time with the SGSII to the point that I couldn't hold it to me ear. My Note doesn't even get warm! So happy.
i am on a stock phone and seen enough force closures in the last week and more than enough in the last 48h. i was just showing my daughter the live wallpapers, so was just flipping through various ones, after flipping through them quickly and setting it, the phone froze, was not able to do anything for about half and hour as phone was booting and rebooting with me unable to even switch off the phone. luckily, at one point i just was able to change wall paper to the black wall paper available on the market and it sorted itself out. it has done this twice whle flipping through live wall papers quickly. the wll papers i was flipping through were flames, weather windmills, aquariium, 3d wall paper, most came with the phone with the exception of flames and black wallpaper.
the phone is fine now but OTG function is flaky, dont know if it is the connector, so have ordered a samsung otg from amazon now and will find out whether it is the phone or the cable.
the built in file manager has serious lag issues as it keeps 'processing' after changing every folder and have stopped using that now and use other free ad supported versions instead which have no problems. same with stock video player which keeps force closing often, so use mxplayer or dice player without issues.
an expensive phone like this should work stock apps fine and not require third party apps for video playing and file browsing etc. was on the verge of returning it when it froze but seems ok now.
After the release of Clemsyn's 1.6 GHz Kernel for CM7 based ROMs last night, I immediately switched to it just to see.
But before that I was running Faux123 1.3 GHz.
I'm keeping the Clemsyn kernel for now, simply because I can. My phone can run it with little difficulty thus far and I have a profile to lower the max freq when the CPU gets to a certain temperature. I think I went with about 65 Celsisus.
Before I switched back to CM7 (or rather Neutrino) I was using Wet Dream. I OCed to 1.45 then in attempt to compensate for only half decent webtop performance.
But now I really only do it because I can. Whenever possible, my phone is on the lapdock since I like to HDMI mirror. Battery is not a concern since the lapdock charges the phone and I pretty much always keep the lapdock charger on hand in my bag.
I just thought it would be an interesting subject for the community to discuss as I'm sure it's something that a number of us haven't even thought of and I bet a good number of us fall into the because I can or bragging rights category.
Specific instances of problems OCing helped with in x app or y app might make someone else want to OC whereas someone who doesn't OC might persuade a user like myself to drop it for amazing battery ETC.
Sent from my MB860 using Tapatalk
Why I DO OC.
Right now I have my Atrix OC'ed at 1.45. I'm currently running Alien ROM Build #4.
The CPU has never gotten past ~55º C.
I also have 2 profiles set
1 for Screen off - 800 MHz max.
1 for Battery< 10% -216 MHz max.
This paired with Alien ROM and LP has left me with a buttery smooth experience.
Is the 1.6 OC kernel worth giving a shot? Or does it make the CPU run excessively hot?
EDIT: I didn't really address battery life. I don't notice a huge decrease in battery life, I'm a pretty heavy user- SMS, Web, Video streaming, Facebook, Twitter. Over all OC'ing is definitely worth it to me.
I like to keep mine overclocked because it seems snapier. I use faux 1.45 and its great. Ive noticed clem's likes to make my phone very hot when running video or games and has actually shut my phone down due to heat. If I run clems I like to drop the overclock with setcpu to around 1.3 so it doesnt shut down but seems to get way hotter than faux's. Anything over 1.5 is just going to cause damage to peoples phones and IMO it should not be used so lightly.
I'm OC'd to 1.45ghz I do it for performance and those random times I need to benchmark I want to try 1.5-6 but I can't seem to get them to boot with the ICS mod2 cm7 so till cm9 or neutrino ill just float about with what I have
Sent from my Atrix-4G, stock 2.3.4 (rooted)
No need for 1.6 IMO.
1.3 is plenty for the Atrix. Even Faux 1.0 is fine. Its a phone, not a PC.
Sent from my HTC Inspire 4G using XDA App
I dunno...my webtop configuration may want to take exception to that statement
troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
+ 1
Sent from my Atrix 4G using Tapatalk
i honestly haven't been able to really tell a difference between 1.0 and 1.3GHz in most of my applications. it definitely doesn't help with system slowdown due to live wallpapers, which is a disappointment.
troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
Haha, I was in that boat before I switched to HDMI mirroring coupled with VNC or Splashtop (when applicable) from experience, I can tell why Webtop users want OC. You can turn your phone into such a useful computer, and then it falls flat on its face because the inner-workings aren't streamlined. The extra power DOES help in that situation.
But in my actual experience, I haven't seen many realworld benefits past 1.2.
Especially since 1.6 kept eventually shutting down on me after about an hour (assuming there is the same issue as in Clemsyn 1.5, setting your max to a lower frequency than 1.6 won't stick so my temperature profile wouldn't actually work)
My "because I can" mindset is going to leave me stuck on 1.45 though most likely. I keep it maxed at 1.2(or is it 1.1? I'm not using the kernel right now) and then have a profile to ramp it up to 1.45 when it's on the charger (aka my lapdock)
I don't think it is quite the same for Blur based ROMs, but on CM7 1.0 seems perfectly adequate for the Atrix. Even at it's stock speed, it is snappy.
Sent from my MB860 using Tapatalk
I dont overclock. I used to be at 1.3ghz, but I didnt see a big enough difference to keep it. At least on CM7, the Atrix is plenty fast on stock speed.
I overclock, but I wait for thoroughly tested kernels before doing so. Right now I'm with faux's v023r @ 1.3 Ghz. I'll try Clemsyn's after its second or third "redesign" or bugfix.
I stick to optimal battery life kernels rather than performance (faux 123 0.2.3 being the one I'm currently on and most likely will be for the foreseeable future)
Also I can't imagine performance possibly getting any quicker or running programs any faster than they already are on the atrix.
Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.
Atrix_Owner said:
Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.
Click to expand...
Click to collapse
Quote for truth
The Atrix is plenty fast already. I can understand if you OC a HTC Magic, or a Hero; but there's no real need to do so on the Atrix.
Idk I see a difference on any launcher when I flip through pages and through apps. 1.3 or 1.45. But I def notice the difference in snappyness.
Sent from my MB860 using xda premium
95% of the time I overclock I do it for getting awesome benchmark scores that I can admire. 5% of the time I do it when playing 3D games like Fruit Ninja, It seems a lot smoother to me. But I hardly ever do it because it sucks the battery down so fast, so usually I'm at 1ghz. Also it's just kind of cool to see the the potential the phone has when overclocking.
i used faux's kernel to overclock to 1.3 for a few months but i didnt really see any difference except when i run quadrant or how my phone got hotter than stock when under load. another thing that annoyed me with faux's kernel was constantly losing widgets on reboot. i use two batteries so i reboot pretty often.
I used faux 23r 1.4GHz with setCPU profiles.
Profiles clamped speed to 1ghz at cpu temp of 50degc and 800mhz at 60degc.
Most noticeable difference was in k9 mail, indexing and searching were slightly improved.
I ran it so I would get a short boost if the cpu was cold.
Matthew
Sent from my MB860 using XDA App
Hey
On my old and feeble Hero I had to OC, if I wanted it to run fine, however I never felt the need to OC my Atrix. it has so much juice in it without OC, making it useless to squeeze the battery for the extra 0.2-0.5 GHz. Moreover, since we have no real ICS, our CPU runs freely and waste energy for nothing, so OC it will just make it run ever faster for nothing (In Hebrew there is a saying- running full throttle on neutral ).
I used to run Faux123 1.0Ghz kernel just to UV the device, but since I flashed weekly 6 I use the stock kernel, and it runs great, no overheating, and extremely stable (What cannot be said on UV kernels...)
The only time i oc is when using webtop, that extra speed makes a difference. The rest of the its running at 1ghz and seems plenty
Sent from my MB860 using xda premium
I'm not sure if anyone else is having my problems. I'm running stock 4.1.1 with this Kernel http://forum.xda-developers.com/showthread.php?t=1831780 (I'm not even sure if that matters). My nexus 7 isn't nearly as fast as when I first had it. Its gotten slower. I'm having issues with multiple games randomly freezing my entire Nexus 7. Sometimes I have to hold down the power button for 20 seconds because it won't respond at all. Also, whenever I reboot it says "Android is upgrading..." then at the bottom it says "Starting apps" for a few seconds. I've had this problem for awhile now. I've tried clearing the Dalvik Cache, removing memory/storage, defragmentation, etc. I'm not sure why it is acting like this. Please help. Thank you!
Sent from my Nexus 7 using XDA Premium HD app
Lol you don't know if it matters that you're using the elite kernel? Maybe you shouldn't be flashing kernels quite yet bud. Go back to stock kernel.
OK ill see if that helps, although I think the issues were happening even before I flashed it. How do I go about returning the the stock kernel?
Sent from my Nexus 7 using XDA Premium HD app
backup all your stuff to your PC, and load the factory rom and it will wipe everything clean including your SD. After trying a few roms I noticed there are some hidden craps that can't be seen by any file explorer and the only way to clear them off is flashing back to stock.
Hi,
Elite Kernel works pretty good. But maybe it has too much overclocked GPU for your device, yeah some device can't hold as much performance then others. Try flashing back the stock rom and see if it works
Sent from my Nexus 7 using Tapatalk
You really shouldn't game on 1.8ghz the elite offers unless you are using ice under your N7. The elite is not really for daily use just benching and seeing how far one can go. Imo pull the core speed down to 1.5 / 1.3ghz to see if your games become stable. Also try the motley kernel build 218 with the 520 gpu for everyday use. Cache whipping should only be done if your installing different roms and completely different kernels. the elite kernel is a motley build so no wipe is needed.
Cheers
Sent from my Nexus 7 using Tapatalk 2
t_007_v2 said:
You really shouldn't game on 1.8ghz the elite offers unless you are using ice under your N7. The elite is not really for daily use just benching and seeing how far one can go. Imo pull the core speed down to 1.5 / 1.3ghz to see if your games become stable. Also try the motley kernel build 218 with the 520 gpu for everyday use. Cache whipping should only be done if your installing different roms and completely different kernels. the elite kernel is a motley build so no wipe is needed.
Cheers
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I think you guys are confused as to which one I'm running. I'm using the one on the second post where the max speed is 1.5GHz.
The 1.5 extreme under volt? Actually that kernel flat out boot looped my N7 and the only way to get out of it was connecting the N7 to the pc. Ditch that kernel. Use the 1.8 / 650gpu pinkfix that kernel is stable at all core speeds for me. Imo just set the clock speed to 1.3 to reduce heat. The 650gpu setting at 1.3 / interactive / cfq will still give you 66fps on nena2. My best score is 71 at 1.8. I the heat build up for gaming is just to much.
Always clear data on setcpu and sys tuner pro when jumping kernels.
Concerning lag does power off then back on fix it for a short time? If so you might want to return it. Asus really dropped the ball on the early N7 runs. I love "Googles" N7 but I'll never buy another Asus product. Hopefully Google picks a better Manufacturer next time.
Sent from my Nexus 7 using Tapatalk 2
Ok. Do I flash this one: https://rapidshare.com/files/1034477848/Clemsyn1.8GPU650.zip or the pinkfix: https://rapidshare.com/files/223841402/Clemsyn1.8GPU650Pinkfix.zip?
Pinkfix. Run your games at 1.3 to see if their stable. Gameloft works best at 1.4 / 1.5 just watch the heat to hot and it will start to lag. THD games 1.3 TOPS their optimized and don't need the oc. Once your done messing with the elite motley build 218 520 gpu is a better everyday kernel for gaming. Have fun and always have a few different kernels in your download folder in case something goes wrong and you need to use recovery from the pc.
Cheers
Sent from my Nexus 7 using Tapatalk 2
Dillon610 said:
I'm not sure if anyone else is having my problems. I'm running stock 4.1.1 with this Kernel http://forum.xda-developers.com/showthread.php?t=1831780 (I'm not even sure if that matters). My nexus 7 isn't nearly as fast as when I first had it. Its gotten slower. I'm having issues with multiple games randomly freezing my entire Nexus 7. Sometimes I have to hold down the power button for 20 seconds because it won't respond at all. Also, whenever I reboot it says "Android is upgrading..." then at the bottom it says "Starting apps" for a few seconds. I've had this problem for awhile now. I've tried clearing the Dalvik Cache, removing memory/storage, defragmentation, etc. I'm not sure why it is acting like this. Please help. Thank you!
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
How much free space do you have on your device? It's been found that the Nexus 7 lags pretty bad when you're running extremely low on space. Try freeing up a couple gigs and see if that improves things.
Also, following Jay's Recipe for Buttery Goodness will help greatly speed up your device.
Do you have your dalvik cache integrated into the ROM with Titanium Backup? That's one way to cause the "Android is upgrading..." to appear on every boot.
I'm using the newest flash kernel and elementalex kernel manager. Its been happening more and more. This time its stuck at max frequency on the big cluster. Everything else I can change like normal. What is causing this? I'm about to lose my mind with this crap. Its happened in several roms too. Right now I'm on screwd android nougat.
Woodrow256 said:
I'm using the newest flash kernel and elementalex kernel manager. Its been happening more and more. This time its stuck at max frequency on the big cluster. Everything else I can change like normal. What is causing this? I'm about to lose my mind with this crap. Its happened in several roms too. Right now I'm on screwd android nougat.
Click to expand...
Click to collapse
Do you have Facebook or Facebook Messenger installed? The latter app especially has been known to cause Max frequency problems for some people.
I do have those apps. But this is when im first setting up a new rom so they are not installed yet. It is also stuck overclocked when it happens. It finally let me change it this time. I have no clue as to why it does eventually let me but not at first. It didn't used to do this on previous version of flash kernel. I also tried changing it with another kernel app and it let me, no problem. Its something about exkm.
Woodrow256 said:
I do have those apps. But this is when im first setting up a new rom so they are not installed yet. It is also stuck overclocked when it happens. It finally let me change it this time. I have no clue as to why it does eventually let me but not at first. It didn't used to do this on previous version of flash kernel. I also tried changing it with another kernel app and it let me, no problem. Its something about exkm.
Click to expand...
Click to collapse
After rebooting or flashing files, the phone runs warm which means you cannot tweak CPU functions due to thermal throttling. The phone throttles when hot (worse if you live in a warm environment) or have low battery. That's a side effect of the Snapdragon 810.
If these issues persist half an hour or more after boot, then there is an app keeping your CPUs clocked high, like mentioned before.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
After rebooting or flashing files, the phone runs warm which means you cannot tweak CPU functions due to thermal throttling. The phone throttles when hot (worse if you live in a warm environment) or have low battery. That's a side effect of the Snapdragon 810.
If these issues persist half an hour or more after boot, then there is an app keeping your CPUs clocked high, like mentioned before.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
That cant be it. I can close exkm and open other cpu tuner app and immediately change the max frequency.
Woodrow256 said:
That cant be it. I can close exkm and open other cpu tuner app and immediately change the max frequency.
Click to expand...
Click to collapse
Keep it simple then. Uninstall then install EXKM from the Play Store and reboot. Open the app after two minutes then grant root access and modify kernel settings. Big cluster may still be offline due to rebooting.
Alternatively, clear data for EXKM and reboot then wait until it's been granted root permissions to modify kernel settings.
Sent from my Nexus 5X using Tapatalk
Woodrow256 said:
That cant be it. I can close exkm and open other cpu tuner app and immediately change the max frequency.
Click to expand...
Click to collapse
For solving your issue, use Kernel Adiutor, go into thermal on the side menu, and disable throttling. - this worked for me
Secondly, I do not recommend Screw'd, it left me well screwed.
- Home screen locking up, only being functional after rebooting
- VERY bad CPU over heating - I'm taking about 180°F - 82°C -while running social media and scrolling. And actually having to physically put the phone on ice to cool it down while I pulled files when I switched off of the ROM
- Random systemui crashes, kind of like CM all over again
I don't know if you get these issues, but I would recommend using a different ROM from my experience.
TL;DR : Screw'd causes CPU over heating and frequency troubles, also use Kernel Adiutor in thermal section to "unlock" or make it easier to tweak frequencies. Good luck!
TnT_ said:
For solving your issue, use Kernel Adiutor, go into thermal on the side menu, and disable throttling. - this worked for me
Secondly, I do not recommend Screw'd, it left me well screwed.
- Home screen locking up, only being functional after rebooting
- VERY bad CPU over heating - I'm taking about 180°F - 82°C -while running social media and scrolling. And actually having to physically put the phone on ice to cool it down while I pulled files when I switched off of the ROM
- Random systemui crashes, kind of like CM all over again
I don't know if you get these issues, but I would recommend using a different ROM from my experience.
TL;DR : Screw'd causes CPU over heating and frequency troubles, also use Kernel Adiutor in thermal section to "unlock" or make it easier to tweak frequencies. Good luck!
Click to expand...
Click to collapse
Wow, i cant believe screwd gives you such problems. Its has been my favorite nougat rom since last months beta. My phone never overheats. Ive only felt it get warm to the touch a few times since i got it last march. As far as throttling goes, if it does i never notice so it must not be too bad.