So after going through ton of different roms/kernels to fix the lag issue that makes my S3 slower than S2, I've finally figured out what is causing it. I can make the phone run smooth if I bump up the minimum freq to above 1ghz. At the moment I'm running 4.3 custom rom/kernel w/o KNOX so the max is at 1.5ghz. I played around with governor and they don't make much difference as long as the minimum has been bumped up. I've seen this happen on stock Note 2 when power saver mode is turned on even with battery on full. What can I do to fix this? I don't want my phone to be in idle at 1ghz for no reason. I will never be able to use the phone for more than 5hrs. Can someone tell me what I can do to make the governor to work as it should?
I've been thinking maybe flashing too many times with different ports could be the cause so I want to flash the stock using Kies but I want stock 4.2.1, not 4.3 with KNOX. How can I achieve this?
Related
Okay, so my question is basically how stable is overclocking your g2? I typically keep it at 800 when I use my phone normally, than 1.5ghz for games. I wante d to keep my g2 at 1.5ghz forever.. is that bad?
My battery obviously increases in temp..
I just use 1GH. It's enough for all game now. and didn't see any bad to battery or phone
I've had my DZ for about three weeks now and all this time I've had it consistently overclocked to 1843MHz. At that high of a speed, I had to let the phone cool down after 20 minutes of use.
Just today I flashed pershoot's 1516MHz kernel and noticed no heat issues after ~45 minutes of consistent use (temps < 40C).
I have had my g2 for.... However long they been out. I have always been overclock to at least 1.5 with zero heat issues. I ran 1.8 and even 1.9 for a good long time as well. Those speeds have heat issues ones that required a battery pull a few times because it started heating up faster then i could shut down the phone. If your going to OC at those speeds makes sure you set temp profiles with alarms.
Sent from my HTC Vision using XDA App
ARM processors, like our snapdragons, are a lot more forgiving on the overclocking front than what you might find in your desktop, for instance.
I still treat overclocking on my phone like I do my computers, though... setcpu has a stress test built in that you can use if you're curious how "stable" your overclock is. but in my experience, I've found that you can get away with just playing around with it and using the phone normally and seeing how it reacts to different clockspeeds.
right now, I run it at 1.1ghz (24/7). I have run it at 1.5ghz (24/7) in the past for PSX/N64 emulators, but I've found with my new setup (pretty light; no widgets, very few things going on in the background, stripped as many unnecessary apps as possible, and not using any animations or fancy bits) that 1.1ghz is more than enough to be able to play the games I play on any emulator smoothly.
you should be fine at any speed that is currently available in the overclocking kernels we have with the exception of flippy's 1.9ghz kernel, which does require some monitoring to keep things cool and stable. but it still does vary from phone to phone. if you're running at 1.5ghz and the phone isn't doing anything wonky, then you shouldn't worry about it. if you're running it at 1.5ghz and you're experiencing stability issues, random force closes that aren't fixable through conventional methods, or heat issues, you should probably back off a bit.
some people have problems at 1.2ghz, some people are running at 1.9ghz all the time and never have problems... just find what works best for normal usage with your device and go with it.. it's not like we keep these things for more than a couple of years anyway, and the processor will be capable of handling the [stable] overclock for that period of time.
im always at 1.2ghz. 768 as min, interactive gov (when i use CM7) and battery has been fine, havent noticed any major issues. hard to tell if it was the rom bugs or OC being the issue but from what i read all my issues others have at various speeds so im guessing it was rom related
i think it depends on the rom.
when i use the Pyromod rom i dont need overclock but for other roms like sense roms those I require OC. I always keep it at 1400 when needed.
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
NissanNick said:
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
Are these freezes ONLY happening when running o/c? If so, then your hardware might not like o/c speeds. Please clarify that it is not an o/c issue due to the information you provided above.
If you're stable and having no locking issues on stock, then flash ROMS/kernels and of the bat start boosting to o/c speeds then seeing instability, how/why are you ruling out it's not a o/c or hardware limitation?
NissanNick said:
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
I don't think sprint will swap your phone out just because you can't manage stable o/c speeds on your phone. LOL
Sounds like you need to do the classic Wipe 3X before flashing.
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
NissanNick said:
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
Click to expand...
Click to collapse
It's not the overclocking that causes your phone to go into sleep of death, it is the low end. 100 Mhz causes sleep of death on a lot of phones on a custom ROM. Set your minimum frequency to 200 Mhz and you will be fine. Don't change any of the stoick voltages.
Try using stock speeds (400-1000). Then work your way incrementally in both directions to see which frequency(ies) cause your issues. Each phone is unique, so find the sweet spot.
I get the black screen of death about twice a month running twilight 1.1.1. My phone runs 200-1000 with no undervolting and set on conservative. I'm just too lazy to bother playing with settings since I'm holding out for SRF 1.3 to release.
hey guys, so im trying to figure out if theres something wrong with my gnex possible the hardware. ive been using antutu to benchmark it over the past month and at first i was getting scores of 6900 on aokp and francos kernel, but in the past couple of week ive been getting things like this http://imgur.com/ybWRK
the two numbers that are taking the biggest hit are the cpu and ram. is there any way that flashing roms are kernels could have damaged any physical part of the phone? its also been acting a little sluggish so i know its not all the benchmark. any ideas or advice?
which versions of aokp and franco are you using?
b25 for aokp and 18.2 for franco. im wondering if i might have overheated something? is there an app or some other way to see if the hardware is all running the way it should?
i regularly see temperatures from 120-140 without having anything open and not charging, should i return it and try another one or is this normal? from what ive read this is kind of hot.
jinni10 said:
b25 for aokp and 18.2 for franco. im wondering if i might have overheated something? is there an app or some other way to see if the hardware is all running the way it should?
i regularly see temperatures from 120-140 without having anything open and not charging, should i return it and try another one or is this normal? from what ive read this is kind of hot.
Click to expand...
Click to collapse
I see exactly what the problem is, and it's very common.
Your CPU speed is at 1500 MHz -- obviously overclocked.
What can often happen is the OC creates more heat. This causes thermal CPU throttling, which actually will slow the CPU to below-stock speed.
I reckon that if you were to turn your max CPU speed back to 1350 or 1200 you would probably get higher benchmarks even though the CPU speed is slower.
I haven't seen anyone post about this yet, so I am going to take the plunge. I have a finicky device. Regardless of what kernel I put on, if I overclock at all, I will eventually get an SOD. I have tried Perseus and Core, all flavors, and started various times all the way from clean, Triangle-Away'd stock via Odin...same thing. It is really frustrating. The best results I get seem to be when I don't mess with the voltages at all, but eventually, SOD strikes. Sometimes I can go days. Today, I tried overclocking the new Perseus to 1.8 with stock voltage (after running it vanilla for 2 days with no issues), and within 2 hours, I had an SOD. I am currently on Clean 4.5, but have had the issue in every ROM.
Anyone else have a super-sensitive Note II with kernel overclocking? Anyone else seen SODs at all, under any other conditions?
What are you max screen-off and phone-on speeds clocked to? That could easily be the issue--I leave mine at 500MHz.
T.J. Bender said:
What are you max screen-off and phone-on speeds clocked to? That could easily be the issue--I leave mine at 500MHz.
Click to expand...
Click to collapse
Oh man, I am embarrassed to say I don't know...I am using STweaks currently with Perseus, and don't see where to set these values. I know that I was able to use profiles in SetCPU...
Where can I check these values? Appreciate your help!
I switched to SetCPU for now and created a couple of profiles. We'll see what happens.
Sent from my CLEANed Note II
Can't say that I get the SOD, but if the weather gets TOO cold (which it has for the last few weeks), my phone would reset itself and will be stuck at the "Samsung Galaxy Note II" screen until I pull the battery. Unlike your situation, I'm an extreme underclocker so it's easy to fix my issue (just give it a bit more juice!).
meatlocker said:
I haven't seen anyone post about this yet, so I am going to take the plunge. I have a finicky device. Regardless of what kernel I put on, if I overclock at all, I will eventually get an SOD. I have tried Perseus and Core, all flavors, and started various times all the way from clean, Triangle-Away'd stock via Odin...same thing. It is really frustrating. The best results I get seem to be when I don't mess with the voltages at all, but eventually, SOD strikes. Sometimes I can go days. Today, I tried overclocking the new Perseus to 1.8 with stock voltage (after running it vanilla for 2 days with no issues), and within 2 hours, I had an SOD. I am currently on Clean 4.5, but have had the issue in every ROM.
Anyone else have a super-sensitive Note II with kernel overclocking? Anyone else seen SODs at all, under any other conditions?
Click to expand...
Click to collapse
Coming from the Galaxy Nexus (and yes, I did my share of undervolting and overclocking with it) I know some of the dice used in making the cpu/gpu are not the same for every Galaxy Note 2. For example, where you got SOD problems used Perseus and Core, I could flash Perseus and Core on mine and not have the same problems at all. Best thing to do is try a different kernel till you find one that does not give you the SOD. Also, it is better to not flash a different kernel when you flash a new ROM as the kernel that is in the ROM usually works the best with it.
yes sod
I get the sod periodically irritating at times
I kept the phone unrooted and stock for 6 weeks or more, and i got the sod even then
I''ve rooted and have been using scottsroms for several weeks now, and get the sod about the same
I'm now wondering if it is a defective unit?
Anyone getting the sod probably has a bad phone. I would return it to be fixed. I personally never had the sod on any rom I have been on.
Sent from the TermiNOTEr 2!
hello. I have a galaxys s2 hercules t989 known as tmobile. the problem is that the cell overheats me much when I use it and when charging too. the same load power cycled only takes 2 days to load. heats up like an oven. someone will know the problem this past me and I can help?
I'm having the same problem, it's not as bad on stock roms as on custom roms not sure why.
I have the original jelly bean I 4.1 and I've put several original and custom rom and is still overheating. I think it is problem of romsfirst
You guys need to check CPU usage
Install CPU usage app and load the timeline (also press the second button to see system apps). You can see which which one is using the most CPU power and terminate it. If that fixes it, you can uninstall or disable that particular app.
ok. result will do that and post them. thanks
JoeGrimm said:
I'm having the same problem, it's not as bad on stock roms as on custom roms not sure why.
Click to expand...
Click to collapse
Custom ROMS + kernels may have overclocked GPU and CPU for a performance increase. This will cause your phone to get hot. Hot Hot...If you're stock, there is something running in the background as others have suggested. If it's a custom ROM, install something like Trickerster MOD and check to see what your CPU and GPU are set at...Anything over 1512 (CPU) and 266 (GPU) will cause increase in heat due to the processors running past their stock settings.
Governor
If your capable of changing the governor like CM or other Roms with custom Kernal's, find a setting that doesn't use a lot of juice all the time. I keep mine on Smartass or conservative if i'm not using it or charging it. I had the same issue before because I had it set to ondemand or performance. Hope that Helps
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
NOPE
I have the same problem but it isnt the battery thats heating up, if you take the back cover off, and feel the battery, it is not heating up. I did get this problem when i installed a custom rom, i had issues with that one including the battery life so i switched back to official jellybean 4.1.2 or whatever, and the battery is fine, does still get hot though but not as much, or maybe were all huluscinating
--- ALIENS