Phone slow to wake up when receiving a call - Thunderbolt General

I tried tinkering with the cpu settings but I still have a problem. Is anyone else's phone slow to wake up when receiving a call? My phone will ring for a good second or 2 before you watch it wake up and load the call screen to answer. Any input is appreciated.
bamf 1.0.9
Adrnalyne's Kernal 1.4ghz/245mhz

All had this issue when I put the profile 'Screen off' to 245-245 (And lower)

Shawn haz root said:
I tried tinkering with the cpu settings but I still have a problem. Is anyone else's phone slow to wake up when receiving a call? My phone will ring for a good second or 2 before you watch it wake up and load the call screen to answer. Any input is appreciated.
bamf 1.0.9
Adrnalyne's Kernal 1.4ghz/245mhz
Click to expand...
Click to collapse
Move you lower mhz to 368 or higher. I gave up on low clock speeds I hate lag I have mine set to 1113/806 interactiveX no screen lag from coming off lock, and no lag anywhere else and still getting good battery life. I find that if you mess with speeds or governs its best to recalibrate battery.
Sent from my ADR6400L using XDA App

Grnlantern79 said:
Move you lower mhz to 368 or higher. I gave up on low clock speeds I hate lag I have mine set to 1113/806 interactiveX no screen lag from coming off lock, and no lag anywhere else and still getting good battery life. I find that if you mess with speeds or governs its best to recalibrate battery.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
This! I was having the same issue. But I gave up and have mine running at 1.8 constant... LoL

Related

Fresh Toast 2.1 - OC Widget vs. SetCPU

Could anyone help me out with this? I was using SetCPU, but I had heard about its constant processor use and "instability" (jumping down to 19MHz?). So I switched to OC Widget, but I'm having some issues with battery life. I had it set to 767MHz max/min when the screen was on and 245? max/min when the screen was off (I always had SetCPU on "performance"). However, I seem to lose battery like crazy with this for some reason! I switched to 245min/767max with the screen on, and I seem to lose battery much slower, but I will get a bit of lag sometimes (especially when typing something). Any assistance?
TheBiles said:
Could anyone help me out with this? I was using SetCPU, but I had heard about its constant processor use and "instability" (jumping down to 19MHz?). So I switched to OC Widget, but I'm having some issues with battery life. I had it set to 767MHz max/min when the screen was on and 245? max/min when the screen was off (I always had SetCPU on "performance"). However, I seem to lose battery like crazy with this for some reason! I switched to 245min/767max with the screen on, and I seem to lose battery much slower, but I will get a bit of lag sometimes (especially when typing something). Any assistance?
Click to expand...
Click to collapse
Via Flipz's website:
Overclock Widget vs SetCPU: Up until now toast and I have been pushing SetCPU because it allows us to create a custom file that tells it what clock speeds the rom is capable of running at which makes things nice and easy. However a couple of bugs have come up lately. First off is that it is constantly using 10-15% of the processor when it shouldn’t even be doing anything. That doesn’t sound like a lot but that’s pretty extreme. The second issue is that it doesn’t seem to be honoring the settings you pick. I could tell it that I want the minimum to be 245mhz but I would catch it at 19mhz. Or vice-versa I tell it that I want the max to be 650mhz and I catch it at 767mhz. With that said, toast took the time to program settings in to the kernel that will now allow you to pick “automatic” off of the device selection rather than custom. This may resolve the issue, so just keep an eye out for it if you use SetCPU. In OC Widget just go in to settings and click “Detect frequencies” to have it read them. If you have no preference then I’m personally saying to use Overclock Widget. It isn’t quite as user friendly as SetCPU, but it gets the job done right. Additionally as a 3rd reminder: make sure if you are running Fresh Toast that you DO use one of these applications, and if you are running Fresh Rom that DO NOT run one of these. Doing so can cause slowdowns.
Click to expand...
Click to collapse
drummingfool said:
Via Flipz's website:
Click to expand...
Click to collapse
Yes, I read that. That is where I got the information about SetCPU being funky.
I wish I could help, but I'm in a "noob-state-of-mind" right now...how the hell do I find OC Widget? I see it no where!
Thanks,
Tee Jay
I wish I could help, but I'm in a "noob-state-of-mind" right now...how the hell do I find OC Widget? I see it no where!
Thanks,
Tee Jay
Click to expand...
Click to collapse
"Overclock widget" in the Market.
-------------------------------------
Sent via the XDA Tapatalk App
Thank you, I might take a look!
I don't know how much you use your phone, but to say I use mine heavily is like calling Rosie a bit chunky. The settings I use are min:652.8 max:767 while on
min:19.2 max:247 while sleeping. I get roughly 6 hours batter life. But I literally use my internet for around 6 hours every day, plus calling, texting, email etc.
I'd imagine, if you use it less, you'd get much better battery life.
Edit: Oh! And I run MUCH more stably with OC widget than setcpu.

Updated:(3/6/2011) Lets Solve G2x Freezing Issue (Solved:Random Freezing in standby)

I know there are countless threads related to G2x Problems but none of the threads are focusing on isolating the reasons of Freezing Issue. I have recently upgraded my phone from Galaxy S Vibrant to G2x and i have to say i love the hardware and performance. Only Issue for me is random freezing.
After using the phone for 2 weeks and trying 3 roms
1. Stock
2. EB 1.04
3. Dark Sinister 1.1
I have come to a conclusion that kernel and rom is not the solution. At least not for me.
So i will try to solve the problem using hardware testing.
From my past 2 weeks experience.
1. Phone Freezes at night during charging
2. Phone Freezes when ever i turn off/on wifi and bluetooth and gps and Data (4g/3g) (Still have to figure out which of them is the cause. Cause i usually turn all off when i need to save battery).
Test Day 1
For Reason 1
I am using SetCpu and have changed Min from 216 to 312Mhz. I am trying this because i think very low cpu usage in standby for a very long period causes the phone to freeze. Its a Hunch i am not sure.
For Reason 2
I will keep wifi, Bluetooth and GPS off.
I will keep 4g/3g Data On all the time.
To My Surprise its been 16 hours no freeze. It includes charging at night. Lets see how long i can go without a freeze. Upon freezing i will make some changes.
Update 31/5/2011 (Test Day 2)
Ok its been more than 40 hours and not a single crash...
I removed the following possibilities as well....
It wont crash upon excessive usage.
Also Normal Heat up does not cause the crash.
As i have been playing Samurai II Vengeance all day long... Until I ended it. Several times charging along playing. I even played it on TV using HDMI. Not a single crash. I used to have around 3 crashes a day on stock rom when i unboxed my new G2x.
I also started using GPS from today. So lets see how it goes. I will update it every 24 hour.
Update 3/6/2011 (Test Day 5)
Ok i am considering Random Freezing On standby as solved because i havent had a single freeze at night after setting CPU Clock at 312 MHz using SetCPU. There are also other comments that back up my solution. I am considering this the solution of one problem.
2nd Issue of freezing while using cell phone apps is because of certain applications that are either buggy or not compatible with tegra Platform. For that i will start another thread with individual application testing for all apps that can cause the system to freeze or crash.
Please Discuss apps System Bloat-ware/User Apps that cause your G2x to Crash or Freeze in the following thread i created:
http://forum.xda-developers.com/showthread.php?p=14399089
Thanks for all the feedback.
Luckily I dont get that issue, buy I think this is a good test :u
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
garrychau said:
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
Click to expand...
Click to collapse
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
mobilehavoc said:
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Do you or @kangxi remember what Apps gave you issues?
it has to be a driver issue, its virtually the only explanation for why devs have not hammered it out yet or even CM7 team for that matter... it has problems on pure AOSP which leaves drivers or overheating (unlikely)... LG has to come up with the fix because they know their drivers and hardware better than everyone else...
Well the obvious problem I see is that they are all based on the stock rom. Try using one build from AOSP or a CM variety.
I didn't stay stock long but I did have reboot using the leaked Gingerbread (which is what EB is built from). I don't follow it but one is based off the stock 2.2.2 rom and the other is based off the leaked 2.3.3 rom.
I had nothing but problems with the stock roms. Thus your problem I think. Move over to Bionic, CM7, Gigglebread, or something.
I tested my phone and I didn't have a reset in like 5 days (which then my battery died overnight because I forgot to plug it in). I usually crackflash the CM nightlies and haven't had any problems with reboots or any issues requiring a reboot (aside from the flashlight killing audio, but just don't use it).
There are definitely two problems - software and the battery. I used to way more problems until I exchanged the battery for a new one and that solved most of my issues. The issues that remain are definitely software based.
tackleberry said:
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
Click to expand...
Click to collapse
Thanks for this information/ Changing the minimum speed didnt affect the battery life but it has survived two nights without crashing. So i am planning to keep it at 312Mhz min.
kangxi said:
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I Completely Agree with you. Some Applications do cause system crashes. But I have removed all the t-mobile bloatware and i only have few games and GPS apps. All games are from tegra zone. So I am sure they are supported.
For GPS App i am using Copilot and it didnt crash on me once.
I just installed setcpu and set minimum to 312. I'm keeping everything else the same to see if this change has any difference. Will report back.
Sent from my LG-P999 using XDA App
Looks like you are gaining progress. Sounds like keeping the processor revved up a little more does the trick.
It would be a simple fix for people to try that have reboot issues. I can't get mine to reboot, so unfortunately I cannot help you. My contribution was to resist from flashing for as long as possible to test how long I could get my "uptime" to. I got up to 127 hours when I passed out without charging it.
I'm running 20 hours now because I forgot to charge it again (seems to be my only problem, lol).
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
jrwingate6 said:
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
Click to expand...
Click to collapse
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
mobilehavoc said:
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
Click to expand...
Click to collapse
Have you noticed any changes in battery usage? I haven't really played around with SETCPU much but can the clock speed be set lower and if it can, have you tried slightly lower settings than 312mhz?
y are u guys using setcpu? and its def cuz the min is too low faux has his at 400 and no problems morfic also has his a little higher then what is it i think 216?? thats too low thats y setcpu isnt supported yet.....pimp my cpu
Someone asked me a question earlier. Only app I had issues with was fring. Soon as I opened it and started playing around with it, phone rebooted.
I uninstalled and it never happened again.
Sent from my LG-P999 using XDA App
mobilehavoc said:
No clue what you're trying to say but setCPU works fine. At startup for first time I selected Tegra2 and it works great. I have max set to 1000 and min to 312mhz (default was min to 216mhz). I'm running stock ROM but with root. that's all.
Click to expand...
Click to collapse
well thats y it works for u, u cant overclock over a thousand mhz so in ur situation ur ok i guess it only applies for people running a custom kernel then setcpu doesnt work, then u would need pimp my cpu

Undervolting

Does anyone know the ideal settings for undervolting the sensation without causing any problems?
StuartTheFish said:
Does anyone know the ideal settings for undervolting the sensation without causing any problems?
Click to expand...
Click to collapse
Not really. As faux say not all chips are created equal. I've seen up to an amazing -150 but my phone can only handle -50 stable and -75 sometimes with a reboot or two.
Sent from my HTC Sensation 4g using xda premium
Mine handles -100 just fine, but yeah,others can only go -50. Just use system tuner and hit the -12.5 till your phone freezes, then when it restarts go one less and see if it's stable. That's what I did.
Sent from my HTC Sensation 4G using XDA App
I'd also suggest keeping the Max Clock at a consistent value while you play. E.g. UV -100mV might work well at one Mhz then fail at a higher value.
Mine seemed to work consistently at about -100mV, then again I tend to UC unless I'm running CF-Bench or something
Should I only need to concentrate on the lowest and highest clock speeds it's been set to use? Or will I have to undervolt all other frequencies between the two? Not sure if it increments on usage, or simply toggles between the min and max.
If it does increment, how can I test it's stability on the other frequencies if I can't tell what frequency it was using at the time?
Just tapped the -12.5 button a few times, and it reduced all of the sliders. It's -100 now with no apparent issues as of yet.
May I ask the reason for undervolting?
masonic1032 said:
May I ask the reason for undervolting?
Click to expand...
Click to collapse
Mainly to save battery. Altho I have found that it is quite negligible. It may also help with phone heat
masondoctorjt said:
Mine handles -100 just fine, but yeah,others can only go -50. Just use system tuner and hit the -12.5 till your phone freezes, then when it restarts go one less and see if it's stable. That's what I did.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
I run faux latest version 2.7 beta and I see his scripts to undervolt and the lowest I see it too go is -75 how are you able to go lower to -100.... ???
I think it varies from phone to phone, mine too seems happy enough -100.
StuartTheFish said:
I think it varies from phone to phone, mine too seems happy enough -100.
Click to expand...
Click to collapse
Soooooo how do I undervolt below -75 that's where I am. Now
rawdawgroy said:
Soooooo how do I undervolt below -75 that's where I am. Now
Click to expand...
Click to collapse
If the phone hangs/boots below that level then with the Phone/Kernel/... that's the limit.
I created a GScript script (well a sh script) to U/V after a reboot. I didn't want it to do it automatically as you'd end up in a boot loop. Just hassle to fix. The reason for the GScript was to remove it from the various CPU controllers I'd tried, I ended up just using the CM7 one to control the CPU.
Faux has the command to do it globally (across all frequencies) or individual frequencies. TBH I never bothered with individual ones.
The bottom line is, do what you and your phone are happy with.
EDIT: meant to add you can check the actual value manually. I know the Faux one (same post as the scripts above) but if you are using a different kernel it might be in a different place.

[INFO] Achieving good battery life!!

I want to share my setup with you guys for getting good battery life which lasts the day without making you compromise on the features. The primary things I've seen on the forums so far has a lot of involved setup and frankly by the time you get it perfect, you will flash a new ROM and have to re-do a lot of it and so on, overall it's not the worth the hassle.
This is usually what my days look like and I manage to last the entire day:
I keep wifi and GPS on always, regardless of whether I'm using it or not.
Get a fair bit of calls because I live away from family so they all call a lot (I have a massive family, so we are talking about 5-6 hrs of talking everyday).
I like to read news from news republic and I'm subscribed to a lot of stuff there so I go through like 2000+ articles in a given day.
XDA like every few hrs (damn ICS!).
Text messages are also flowing throughout the day with the woman being on the other side of the country and all (100+ a day?).
I have facebook on push (not an addict but active enough to mention)
My gmail, school and exchange are all on push for email so they I see a fair bit there
The setup is VERY easy to setup and replicate. It doesn't require you to lose out on features or use your phone at an anorexic level either. You don't need a task manager or watch your processor non-stop either.
So without further delay, here we go:
Pick a ROM
I'm using Seanster_GBaxe EX v1.5.1 from the T-Mobile section, you can find it here.
Get faux's kernel
The reason for this particular one is because it's given the best results when it comes to undervolting and overclocking without SOD. You can find the kernel here.
Get System Tuner
This is available on market. There are alternatives but for this post, I will be making all the references from this app.
Get the AGPS patch from crypted
This isn't for battery directly but it does get locks VERY fast and you waste less clock cycles getting the signal. Less clock cycles wasted, more battery saved. The patch is available here.
I personally use the v3.0 Google CWM Build (scroll down his post and you will see it)
Get the V6 SUPERCHARGER from zeppelinrox
This is available here. Why the beta one? It works fine.
Okay, at this point you can pretty much store these things together in a neat little folder on your SD card because it makes a perfect library. So let's get started, I'll assume that we are starting from scratch. The order for everything will be as follows:
Get into recovery and install your ROM
This I shouldn't have to explain, the instructions you can find on the ROM thread.
Install the kernel
Same with this, read the kernel thread.
Install the GPS patch
Same with this as well
Boot into ROM
Hmm.... hopefully you can manage this
Restore all your backups and apps, accounts and whatever else
Using titanium here is always good
Install System Tuner
Okay, let's get started. Although faux has done an amazing job with the kernel, there's always the personal bias that goes into making things so his balanced settings might not reflect yours (nor mine but you will be tweak even those soon).
Inside System Tuner, go to CPU:
The first you thing you should choose is whether you want to keep the 1.72 GHz OC or not. I kept it but if you want to get even more you can lower to stock 1.56 GHz or go even lower, your choice. Once you set the max, set the min to 384 MHz. Set it once and you don't need to do it again after. Leave the governer to ONDEMAND.
Now go to the Voltage tab:
Be careful here, this can crash you if you go too far. What we do here is globally undervolt, you can do that by hitting the -12.5 mV button over and over. I use -75 mV (press the button 6 times, for those bad at math). Keep in mind that all chips are NOT THE SAME!!! -75 mV might be too much for you or you might even be able to get to -100 mV, find out by doing it.
Now go back to the CPU tab and hit Boot Settings:
Hit Screen-off behavior:
Governor - No changes
Max frequency - 384 MHz (push doesn't lag at all still so don't worry about notifications)
Max frequency/in call - 384 MHz (yes, calls don't require full blast, they work fine even under 500 MHz)
Now go back
Hit Governors behavior:
Sampling rate - Unchanged (faux has it done perfect)
Up-threshold - 75 (what's this? This means that the CPU will scale to higher frequencies when the load is above 75%)
Power-save Bias - 70 (what's this? This means that the CPU will be "biased" towards lower frequencies when load is below 70%)
Setting the Power-save Bias higher than the Up-threshold is obviously stupid so make sure you did it right.
Now go back
At the bottom, there is a whole bunch of tweaks:
Hit Re-apply CPU settings, choose init.d script (you can choose boot too but init.d works 100% of the time)
Hit Boost app loading, choose init.d
Hit Clear cache, choose init.d
Now go back
Find the Startups section and disable whatever you don't want running at boot (this is purely a personal thing).
Install V6 script
His instructions are very good so I'll assume that you have gotten it installed. Once you have it running, choose option 9, the 1000 HP one. Reboot. Run script again, make sure you've got it at 100% supercharged. Done. Reboot just to be sure again.
All done! Now, I know that was lengthy but here's the awesome part. Make a titanium full backup of System Tuner and you NEVER have to do that again for ANY ROM as long as you use the same kernel!! The script is unfortunately the only thing you have to re-apply, probably that has a quick setup too but I'm new to it so I can't give you shortcuts on it.
Hope you have luck with this and it works for you. I promise nothing and if you break your phone please don't come crying to me because you chose to do this yourself. It works for me so I shared it!! Any suggestions are welcome of course.
Note: NO task manager required!! I will modify this for cm7 if needed.
nice job. thanks a lot!
You're using the rc6.1 correct?
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks for the detailed write-up.
Are you in an LTE market? A full day on LTE would be pretty awesome.
For the screen-off behavior, do you think one can get away with using the smartass governor instead?
I'm using the RC6, tad older I guess.
Sent from my SGH-T989 using Tapatalk
jedah said:
Thanks for the detailed write-up.
Are you in an LTE market? A full day on LTE would be pretty awesome.
For the screen-off behavior, do you think one can get away with using the smartass governor instead?
Click to expand...
Click to collapse
I'm not in LTE area :-(... Would be nice because that's why I got the phone but then I had to move so can't say anything about LTE.
As for smartass, what kernel are you using? Smartass works very similar to the modified ondemand settings that I set up so it wouldn't make a difference as far as I forsee.
Sent from my SGH-T989 using Tapatalk
I tried this, will post results later. Thanks for the great tutorial
If you could post screen shots of your CPU Spy that would be helpful! How well does your phone do on going into deep sleep? On average from what to what time does yours last you? I'm just skeptical about setting the screen off behavior cause that usually prevents the phone from going to Deep Sleep.
Sent from my SAMSUNG-SGH-I727 using xda premium
DANIEL133337 said:
If you could post screen shots of your CPU Spy that would be helpful! How well does your phone do on going into deep sleep? On average from what to what time does yours last you? I'm just skeptical about setting the screen off behavior cause that usually prevents the phone from going to Deep Sleep.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
You're right about the deep sleep, don't let it go into deep sleep. It lasts me 12 hours normally. I'll get you screenshots when I get a chance.
Sent from my SGH-T989 using Tapatalk
Mine goes into deep sleep with screen off behavior setup.
Sent from my SGH-T989 using XDA App
kr3w1337 said:
You're right about the deep sleep, don't let it go into deep sleep. It lasts me 12 hours normally. I'll get you screenshots when I get a chance.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Dont you think the phone waste alot more battery though when it doesn't go into deep sleep? I've also found that WiFi tends to create a nasty wake lock. My set up is Sky ICS Speed with Faux Clock 1.296 ghz max -384 mhz min. -37.5 u/v LTE on all day, extremely heavy usage. 12 hour battery life on average.
Sent from my SAMSUNG-SGH-I727 using xda premium
InstigatorX said:
Mine goes into deep sleep with screen off behavior setup.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Which kernel are you using?
kr3w1337 said:
Which kernel are you using?
Click to expand...
Click to collapse
Using faux kernel with foxstar rom.
Sent from my SGH-I727 using XDA App
DANIEL133337 said:
Dont you think the phone waste alot more battery though when it doesn't go into deep sleep? I've also found that WiFi tends to create a nasty wake lock. My set up is Sky ICS Speed with Faux Clock 1.296 ghz max -384 mhz min. -37.5 u/v LTE on all day, extremely heavy usage. 12 hour battery life on average.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
From what I've noticed with the faux kernel, it goes into deep sleep after some time on it's own, regardless of the screen-off behavior. I haven't opened up the source to check it out for a better explanation but that's something I doubt is worth exploring since the performance doesn't take any hit.
I haven't chosen to underclock to 1.2 but it should do better than the 12 hrs I get now if I did do that. I have a tendency to start GTA 3 and start playing whenever I get bored so that's why I went OC rather than under. For others looking strictly to use the phone with minimal gaming, this would be a good option. LTE isn't available in my area so I can't test with it but the WiFi radio uses just as much battery as the LTE, if not more I have a feeling.
Trying eugene's kernel from today to see if the lionheart governor does better than the current setup. I will know in a couple of days because every ROM flash needs a couple of charge cycles before it accurately shows battery status.
InstigatorX said:
Using faux kernel with foxstar rom.
Sent from my SGH-I727 using XDA App
Click to expand...
Click to collapse
Do you get any SOD? Everything working okay? Is the setup different than what I've got up there? Would like to know and try it out, can update the OP accordingly.
Just finished with eugene's kernel and the results were pretty disappointing. Looks like the second core is always kept on regardless, faux's kernel turns the second core offline until usage demands need it.
If anyone knows how to tweak eugene's to stop that from happening, do share.
kr3w1337 said:
Just finished with eugene's kernel and the results were pretty disappointing. Looks like the second core is always kept on regardless, faux's kernel turns the second core offline until usage demands need it.
If anyone knows how to tweak eugene's to stop that from happening, do share.
Click to expand...
Click to collapse
Can you clue me location of his latest ROM? Or is it somewhere in the Macnut thread on TMO side of the fence?
InstigatorX said:
Can you clue me location of his latest ROM? Or is it somewhere in the Macnut thread on TMO side of the fence?
Click to expand...
Click to collapse
Using darkside ROM at the moment with the faux kernel, had the Eugene kernel but I noticed that the second core is kept alive regardless of usage and that wasn't helping so I changed back to faux.
Sent from my SGH-T989 using Tapatalk
thanks for the awesome write up!
Did it last night, and lasted the day without a sweat! However, my min frequency wont stick? I have it set to stock frequency 1.5, using faux kernal, and my voltages arent as low as yours (im not a crazy user like you.. maybe an hour of talking a day, lots of texts and emails tho), but i cannot get my min frequency of 3xx to stay. Suggestions?
Thanks!
edit- running stockMod v1.0
im sorry, i have a hard time believing you talk for 6 hours and scroll thry 2000 pages of web and get a day of use. I myself could get about 1.5 days on battery strictly by staying home, connected to wifi all day and barely talking on the phone. i would like to see a screenshot of battery usage at the end of your day

Kernels not sticking to settings

Hi I had this problem with one kernel and put it down to that. The same thing however has happened with others.
Has anyone else had this problem? I've used Trickster mod donate to try setting the frequency. Even with the frequency lock on they jump. They seem to jump to random frequencies, but 1.7 is the most common.
Can someone recommend one that does not do this and is good on battery?
Sent by mobile telephone.
howard bamber said:
Hi I had this problem with one kernel and put it down to that. The same thing however has happened with others.
Has anyone else had this problem? I've used Trickster mod donate to try setting the frequency. Even with the frequency lock on they jump. They seem to jump to random frequencies, but 1.7 is the most common.
Can someone recommend one that does not do this and is good on battery?
Sent by mobile telephone.
Click to expand...
Click to collapse
What do you mean exactly? Do you mean the minimum frequency jumps up? If so, yes this is called mpdecision and is present in stock based kernels, unless they explicitly give you a way around it.
It's not that. The kernel I'm using has a scaling range of 300- 2265. I'll set these as it's limits but both ends will move, sometimes to the same freq. 1728 is what they jumped to when I set them just now.
I'm not talking about where the scheduler moves to but the upper and lower limits it has to move about in are what won't stay.
Sent by mobile telephone.
Trinity doesn't seem to do this on my phone so I'll go back to that, but Ive never had this problem
Sent by mobile telephone.
Downloaded cpu tweaks and it shows what I set, but Trickster mod does not so I'm dumping trixtermod as it's showing stuff that is not set, or appears to as cpu tweaks is showing in real time data I expect to see
Sent by mobile telephone.

Categories

Resources