Related
So I'm running baked snack here and really beginning to enjoy it and this whole root thing. I've installed setcpu but every time I back out of the interface it goes down to 691 no matter how high I set it or on any profile. Does this not work with baked snack? Am I overlooking something or did I set it up wrong(I used auto detect when I started)?
Did you flash a different kernal?
Sent from my PC36100 using XDA App
Nope I flashed kernel 3 I think or what ever came included in the baked snack.
should I DL that kernel by itself and then flash over the Baked snack with it? and whats the difference between flash over and flash ontop of?
Damn the stupidity of it all... lol. I set my profile to 691 if my battery was under 40% which it was... but now when I plug my phone in the cpu goes up to 1ghz which I have it set to but my battery keeps going down. Now this is a problem here if I'm not able to charge my phone while the setcpu is running it will get really annoying really fast. Considering the app manager that I have refuses to close it so I have to manually go to settings > applications > manage applications then go to setcup and force close it to charge my phone it seems. Do you guys think its a problem with my cpu being set to high while charging should I drop it down a whole bunch for the charge process too? That doesn't seem like a very needed thing to do I would assume it would be able to charge just fine without that. Looks like I got a lot to learn about this whole rooted phone thing.
Check your profiles in setcpu and make sure you don't have one that's at that speed with the highest priority. If that all checks out fine I would flash kernal 2 (my favorite) don't wipe just flash. And as for your question over or on top they mean the same thing and that's flashing the kernal without wiping.
Sent from my PC36100 using XDA App
Also do you have overclock widget running as well? If so they might be fighting eachother
Sent from my PC36100 using XDA App
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
crimeslunk said:
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
Click to expand...
Click to collapse
Overclock widget is just another widget you can download that runs seperatly from SetCPU. You should have a SetCPU widget though. I would try reinstalling SetCPU also
This is stock ROM.
Every time I flash bacon bits to overclock my phone I always noticed that my screen flickers when I turn off the phone's screen or press the button to wake up.
Sometimes it just gets stuck and it stats flickering like crazy and I can't unlock my phone because of it.
This only happens when I OC my phone. When I wipe the phone it works fine but no OC which is what I want.
Any way to fix this issue?
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
dustrho said:
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
Click to expand...
Click to collapse
Actually I OC my phone, but it's still set on 806MHz so even at lower clockspeed it still flickers. It's bugging the hell out of me.
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
captainreynolds said:
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
Click to expand...
Click to collapse
Yeah, I have flashed all the kernels even pershoot's and it still flickers. I'm using the original ROM that came with the phone not the original one posted on the forums. Maybe if I use the one posted on the forums that will work?
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
captainreynolds said:
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Well you know what I flashed an older version of pershoot mayeb I should try the newer one. I'll let you know what happens...
I had trouble flashing it with ROM Manager. Clockworkmod it. Here's the link to pershoots blog with the latest update links: http://droidbasement.com/db-blog/
Good luck!
Sent from my T-Mobile G2 using XDA Premium App
Just tried it and nope... it's still doing it maybe it's just my phone.
Bring it up in this thread:
http://forum.xda-developers.com/showthread.php?t=847672&page=103
Pershoot is always monitoring it along with a bunch of other smart devs. Maybe they'll have a better idea - don't give up hope!
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
pmcqueen said:
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
Click to expand...
Click to collapse
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
jjuice525 said:
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
Click to expand...
Click to collapse
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
pmcqueen said:
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
Click to expand...
Click to collapse
Actually, after installing Pershoot's most recent kernel, I have no problems. Maybe I just got lucky here.
When I first got my phone I looked up some info on rooting. It seemed at the time that Wifi wouldn't work properly. I have spotty 3g coverage so I need Wifi to work properly.
Are there currently any issues to rooting and/or installing custom roms on the ET4G?
Been rooted since I bought it. No issues. Everything works beautifully. Currently running Cauklin's 2.01 EK02 based ROM and loving it.
Once you have been immersed in the "root & overclock" you will find that it provides more gain than headache. I have problems everytime I try something new untilled I learn some quirks and how to overcome the new problem. If you do root & oc first and foremost create a Complete Backup of all the stock data from your phone onto a computer that is untampered with so if all else fails you can flash back to right after gaining root. In which case you can UnRoot your phone and then perform a factory flash.
Just a few things that make it worthwhile...
BATT LIFE went from one day with my normal usage of web, calls, games,extra... I had to topoff in the car midday. Rooted, I use an app that has a "NITROUS" setting which when I hit the lil button my phone clock ramps up to the Max... but for doing my regular activities I actuly have my phone down clocked alot and do not see any performance issues with anything.
Also when my phone is in my pocket it downclocks even further for standby. 1200 is stock.
1600-max overclock for dl
(I do not use 1200 i have mine set on 800)
800-daily activities
200-screenoff
( I Max it out for streaming movies or dl of big files)
Not to mention all of the customization for you with roms and being able to remove stock apps ect...
Here is a good starting point.... root phone create a backup... flash a new kernel that allows over and underclocking set up a screen on off profile with oc app. Remove any stock apps you don't want and see from a "stock os" with the phone if you notice a difference. If you don't unroot and rock it stock.
Staying active in forums and never try a rom or kernel that is labled beta.
Sent from my SPH-D710 (nothing stock about it) using xda premium
On a side note I am below 15% batt life for about 8hrs now and still using normally just not using my nitrous setting.
Sent from my SPH-D710 using xda premium
How do I overclock my phone. I am running the caukulin 2.0.1 rom with the rogue kernel. i tried everything but the max i can go is 1.2ghz which is stock i want to go to 1.6ghz what am i not doing.
Downside to rooting phone....being addicted to said rooted phone.
Sent from my SPH-D710 using XDA App
Grub4dos said:
Once you have been immersed in the "root & overclock" you will find that it provides more gain than headache. I have problems everytime I try something new untilled I learn some quirks and how to overcome the new problem. If you do root & oc first and foremost create a Complete Backup of all the stock data from your phone onto a computer that is untampered with so if all else fails you can flash back to right after gaining root. In which case you can UnRoot your phone and then perform a factory flash.
Just a few things that make it worthwhile...
BATT LIFE went from one day with my normal usage of web, calls, games,extra... I had to topoff in the car midday. Rooted, I use an app that has a "NITROUS" setting which when I hit the lil button my phone clock ramps up to the Max... but for doing my regular activities I actuly have my phone down clocked alot and do not see any performance issues with anything.
Also when my phone is in my pocket it downclocks even further for standby. 1200 is stock.
1600-max overclock for dl
(I do not use 1200 i have mine set on 800)
800-daily activities
200-screenoff
( I Max it out for streaming movies or dl of big files)
Not to mention all of the customization for you with roms and being able to remove stock apps ect...
Here is a good starting point.... root phone create a backup... flash a new kernel that allows over and underclocking set up a screen on off profile with oc app. Remove any stock apps you don't want and see from a "stock os" with the phone if you notice a difference. If you don't unroot and rock it stock.
Staying active in forums and never try a rom or kernel that is labled beta.
Sent from my SPH-D710 (nothing stock about it) using xda premium
Click to expand...
Click to collapse
I am curious ...what app are you referring to? Thanks
Sent from my SPH-D710 using xda premium
I personally like rooting and messing with my phone, it's fun.
My wife hates it because she doesn't care about custom this and that.
Root = fun
Unroot = your phone as intended
Are you a phone junky, then root for sure with caution.
Are you not, then stick with stock, your phone horse power has enough to keep you going.
Note: For me, everything working great. I've had some problem but nothing I couldn't fix within a day here on XDA Forum. Btw, I'm a noob compared to most here on xda.
Well JC I personally like a totally blank canvas to work with... here are some things I just do not use
Google anything be it Maps, Navigation, Books, gmail, Latitude, ect ...
Sprint TV, Radio, ect...
Calander
YouTube
Voice anything
Most all of the apps I just use the internet and save my webpages...
Yahoo mail, Gmail, Facebook, ect...
So with a Stock Phone what ill do is root, create my "Stock Backup" and save that zip on my phone AND my PC. Then al of the ROMs I am untreated in I will load to my PC and push the zip to my phone one at a time. Try them out to find the one I like the most. Once I find a winner I will add back the things I do use the most if the rom doesn't have them alrdy.
To me my camera is a good check of a rom... most of the time if the camera works fine then the rest usually is good. After camera I try to send a pic via text msg. Both working then I explore the rom for any other instabilities I might have read about in the post of said rom.
In theroy the more free space on a phone means it will run processes faster in theroy.
Apps I do use:
Quadrent Standard
Linepack
Speed Test
For my OC I like CPU Benchmark by unstable apps & CPU Boost by conap
Jrummy has a onestop toolbox I also recommend.
Just a last thought... dl different Free overclock apps to find one you like then purchase the one that works for you.
Sent from my SPH-D710 using xda premium
Grub4dos said:
Well JC I personally like a totally blank canvas to work with... here are some things I just do not use
Google anything be it Maps, Navigation, Books, gmail, Latitude, ect ...
Sprint TV, Radio, ect...
Calander
YouTube
Voice anything
Most all of the apps I just use the internet and save my webpages...
Yahoo mail, Gmail, Facebook, ect...
So with a Stock Phone what ill do is root, create my "Stock Backup" and save that zip on my phone AND my PC. Then al of the ROMs I am untreated in I will load to my PC and push the zip to my phone one at a time. Try them out to find the one I like the most. Once I find a winner I will add back the things I do use the most if the rom doesn't have them alrdy.
To me my camera is a good check of a rom... most of the time if the camera works fine then the rest usually is good. After camera I try to send a pic via text msg. Both working then I explore the rom for any other instabilities I might have read about in the post of said rom.
In theroy the more free space on a phone means it will run processes faster in theroy.
Apps I do use:
Quadrent Standard
Linepack
Speed Test
For my OC I like CPU Benchmark by unstable apps & CPU Boost by conap
Jrummy has a onestop toolbox I also recommend.
Just a last thought... dl different Free overclock apps to find one you like then purchase the one that works for you.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I was referring to the app with "Nitrous" boost. TIA
Sent from my SPH-D710 using xda premium
So the app I use for my overclock is named CPU BOOSTPRO in the market... in the settings is where I set up my oc and down clock. The rom & kernel screen shots also.
Sent from my SPH-D710 using xda premium
So this has the nitrous widget in the top right and just the CPU boost pro widget in the top left. The android is my task killer widget.
Sent from my SPH-D710 using xda premium
And I hit that quadrent score at 1400 clock. I personally do not like how hot (heat wise) my phone gets at a 1600 oc.
Sent from my SPH-D710 using xda premium
I've been rooted for some time. Some kernels do have big LoS issues with this phone. My current combo is working VERY well, though. LoStKernelExp+ & viperROM. Fast and dependable.
Hatchett said:
I've been rooted for some time. Some kernels do have big LoS issues with this phone. My current combo is working VERY well, though. LoStKernelExp+ & viperROM. Fast and dependable.
Click to expand...
Click to collapse
^5
Yes something you have to do is get around the los by trying a few different sets ie... same rom different kernel.
Sent from my SPH-D710 using xda premium
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah I read your post earlier in that thread and was using your settings. I've come across a newer problem, my phone randomly reboots. I don't know what was causing this so I restored default settings.
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
DarthDerron said:
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
Click to expand...
Click to collapse
I doubt locking the frequencies has anything to do with your reboot problems, this simply dissallows any apps that are capable to override the voltage settings for any particular frequency step. In fact, unchecking this may actually give you a false positive of it 'fixing' the problem when it is actually just using the default (or higher) voltages, burning up more battery in the process. As mentioned by jethro and liltitiz its more likely your UV settings, keep playing with them until you find the happy spot (works on other things too....:silly.
jethro650 said:
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
Click to expand...
Click to collapse
Or just move the ktweaker apk from the /system/app directory from a recovery based file manager. This will keep it from launching on startup and then can either be moved back or ran to reinstall. This way you dont have to cleark the dalvik cache, which should be done any time a kernel is installed, eliminating the extra long boot time when this is done. Either the built in TWRP explorer or the Aroma File Manager which can be 'flashed' in recovery. It doesn't actually flash anything, just unpacks, runs, and then is dumped from memory on reboot...very handy if you dont have TWRP or can't get into android.
liltitiz said:
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I was wondering what was going on. I restored stock Voltage and realized that it was the problem.
Alright, its a long shot but here goes,
Ive been really into this Family Guy Quest For Stuff game, for those who havent played it I recommend you do!
Anyway it really seems to hate custom roms, It lags unbelievably and becomes unplayable, Yet when im on stock it is smooth, fluent and works flawlessly.
Ive been into the game for a few months now and have progressed well and would like to keep playing it, However I dont wanna be on stock to be able to do this. Are there any other Family Guy players around here with the same problems?
For what its worth all other games work as they should, this is the only game in my collection that has this issue.
Cheers people!
? "Family Guy" and "Big Fish Casino" are the only 2 games I play on Android.
? I solved the lag issues by installing the games on my Tablet instead! (Bigger screen & more processing power).
Sent from my SM-T310 using Tapatalk
That doesn't help me identify the cause though, the issue doesn't lie with the devices processing power because on a stock rom it is fine.
I want to figure out what is different between stock and custom that could have an effect on this particular game.
The game is server based. Could there be something limiting my connection to the server? Could it be that there is different gpu configuration between stock and custom? I really don't know much about how things work but there must be someone who does around here
Sent from my Moto G using XDA Free mobile app
I think you already answered to your own question, when you mentioned "different gpu configuration"...
Try using some game booster app?!
Here some examples:
"clean master" for example, has a game boosting option.
Or maybe a more specialist app like (Android Tuner) that will help you to fully control how your device operates.
? I hope this can be of any help to you,
Good luck!
Sent from my SM-T310 using Tapatalk
Well I've been boosting the game through clean master and it has no effect. I've used an entropy generator to try and reduce lag. Still no difference. I've overclocked the cpu and fiddled with the governors too.
I will give the Android tuner a go and see how I get on with that.
Thanks.
Sent from my Moto G using XDA Free mobile app
Okay so I have optimised my device to the extreme for playing games. Boosted through clean master, had Android Tuner highly configurated and had the cpu overclocked to the maximum possible as well as kernel tweaks and gpu tweaks.
This issue is 100‰ not related to the devices specifications.
The conclusion I have come to is that the game isn't compatible with 4.4.4 as when I was stock I was on 4.4.2 it worked as it should. Can someone shed some light on this?
Also, what could possibly change from 4.4.2 to 4.4.4 that could influence the way this game works?
I know it's no big deal it's just a game. But it's the principle now, it's got me intrigued as to what is happening behind the scenes.
Cheers.
Sent from my Moto G using XDA Free mobile app