Related
Is anyone else having an issue with custom kernels? My Tbolt only seems to run on the stock kernel/voltage. When I flash an oc kernel sometimes it will load and then freeze the system.
Sent from my ADR6400L using XDA App
All phones are NOT created equally. Your phone may just not be able to handle it while others could.
I realize every cpu used is not the same and can't handle being overclocked to the max, but come on, I can't overclock it at all without it freezing shortly after the Rom starting. Don't you think that's a little out of the ordinary?
Sent from my rooted Tbolt.
I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.
Yeah that does sound kinda sketchy. Which kernels have you tried? Have you tried running one that wasn't undervolted? I've heard people having issues with the UV kernels.
Wkd1 said:
I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.
Click to expand...
Click to collapse
I know what you mean. I had the 1.2 GHz uv kernel from adrenalyne and the phone ran like crap. What's the point of over clocking if real world results are worse. Smart-Ass would stutter while it was ramping up and gun bros ran like crap until I reverted back to the stock kernel.
I'm hoping somebody makes an OC kernel that isn't under volted.
Sent from my HTC Thunderbolt using Tapatalk.
I'm running Imoseyon's version 3 of the lean kernal, 1.4 ghz, undervolted. it seems much faster and more responsive, and has yet to cause me any problems. Right now I'm running on 20 hours off the charger with 45% battery life left (extended battery, so assuming stock would last around 9 hours).
The only kernel that works for me is adrenaline's 2.6.32.21 battery is life kernel. I've tried his other kernels, imoseyon's lean kernels, and a few others all with the same result of freezing up the Tbolt.
Sent from my rooted Tbolt.
Have you tried adrenalynes newest kernel? I'm using version 4 right now with no problems.
Yeah, another vote for Adrenalyne's kernels here.
I'm running the version 4c, and it's flawless on my phone. (4b locked up at higher speeds.) But the other tweaks he threw in there kick ass. Louder audio, faster charging and, I think, most significant, a potential fix for the GPS issues a lot of people are experiencing. Granted, mine was not too bad -- I could usually get a lock within a minute or two, but now it's locking in under ten seconds.
Can't quite comment on the battery life yet, but it's probably pretty damn good, especially with a minimal overclock or even staying at 1Ghz.
Running one of Ziggy's...so far so good...
I ran Drod's 1.5 kernel with no problems overclocking. When I switched over to Ziggy's or Adrynalyne's overclock kernels, I am unable to overclock with out my phone freezing and going into constant boot loops. Kinda weird but I have no real need to OC so I just went with Adrynalyne's stock kernel and been fine ever since.
So I was running CM7 RC1 and everything went fine, I was able to OC and UV. Then I flashed TalonACE kernel, and it wouldn't let me OC past 1.1 ghz. If I went any further, the phone would freeze up and I was sol till I did a battery pull. I just flashed MIUI (love it by the way) and I still have the same problem. I tried lordmod's kernel and it wouldn't go past the boot screen. Any help, or did I fry my cpu for good?
Well, if you fried your CPU you would not be using your phone right now. Every phone is different, as is every CPU. If your phone is freezing up then your CPU is overheating. You may have pushed it too hard in the past and now it does not like being overclocked. You can try different kernels to see how it behaves, but if I were you I would take it easy. Remember, phones are not like desktop computers. There is no active cooling. Care has to be taken.
Wolf_2 said:
Well, if you fried your CPU you would not be using your phone right now. Every phone is different, as is every CPU. If your phone is freezing up then your CPU is overheating. You may have pushed it too hard in the past and now it does not like being overclocked. You can try different kernels to see how it behaves, but if I were you I would take it easy. Remember, phones are not like desktop computers. There is no active cooling. Care has to be taken.
Click to expand...
Click to collapse
I pushed it to 2 ghz briefly one time just to check it out, but no overheating occured. Just wanted to make sure I hadn't seriously damaged my phone, it still runs smooth as butter, even if I can't oc
Some phones can run stable at 1.8 and some only at 1.1 GHz. Like I said, yours may not like overclocking. You definitely did not fry it because then you would be getting another phone. If it is running fine then all is good.
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
recDNA said:
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
Click to expand...
Click to collapse
It looks like that most people that end up with this problem (sleep of death, blank screen of death, or whatever you want it to be called) were either underclocking to low or undervolting to low, some governors have also been the culprit on some devices. Not all of our thunderbolts are the same, guess solder joints are weaker or something that makes this such a random problem. Your best solution is to try different kernels, cpu settings, and governors to find out what your phone likes. I personally haven't had this issue with eternity. However, some others have! Good Luck
Yes, what the above poster said. Like for my phone it does not like smartass gov. It will work but the screen will freeze as you have experienced also. Also overclocking, i can overclock to 1.7ghz but will also freeze randomly as you experienced.
Sent from my HTC ThunderBolt using xda premium
I think (but could be mistaken) this is more like the opposite of black screen of death. I believe that is when the phone wont wake from sleep.
My problem occurs only when phone is awake and being used heavily. The screen isn't black nor blank - I see whatever screen I am on when it happens: lock screen, an app, home screen, keyboard, etc. I see all the icons but screen becomes totally unresponsive to touch. Wide awake.screen but no matter how you tap, slide, or use capacitive buttons nothing works.
Only way out is to pull battery or hold down up volume, down volume, and power key simultaneously to force a restart.
There is someone out there who understands this phenomenon better than I and can suggest approaches but I must be clear - this is.not a black or blank screen and doesn't occur when clock speed is low.
I would.guess cpu is operating at full 1 ghz when screen freezes occur in my tbolt. I am not overclocking at the moment but I do believe overclocking makes it worse but not sure.
Mine was doing that at being underclocked too low keep it at say, 368 mine never did it again, also don't undervolt too much it can cause phone to power down. I use ondemand and keep you lowest speed to 368 and you should be fine. Using battery saver mode for kernel in speedtweak may be undervolting your phone to much if you are using that.
Try this kernel working great for me. http://db.tt/QqkRvtjm jdk newest kernel.
Sent from my ADR6400L using XDA App
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That might be the case if we all used the exact same set up. We don't some change fonts, some use different apps, and there are so many variables.
Nothing unusual going on in my tbolt. 1.0.9 cubed with no unusual apps or settings. I seldom add.an app to my bolt unless it has 1000's of downloads in the market with high ratings. I learned that back before I rooted. I bet someone who writes.kernels understands this phenomenon and could point me in the right direction. Imagine if your computer was bonked up and advice was to randomly try changing settings?
recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That sounds more like your phone doesn't like whatever voltage is set for your top end frequencies. Might want to try IncrediControl from the market and increase the vdd levels a little. I think a lot of the kernels floating around are under volted a little. Could be the cause.
Sent from my ADR6400L using Tapatalk
Its worth a try. I never tried that. Thanks.
You say it only happens when using your bolt, maybe the processor is just maxed out. How long do you wait to see if it comes back around?
I have waited as long as 10 minutes but usually ibjust restart within 30 seconds based on experience. Once "frozen" it has never recovered on its own.
What's interesting is the processor is still working whilebthe screen becomes unresponsive. I know this because I was streaming a r radio into a jawbone earpiece and when I switched apps the screen froze yet the radio continued to play. I HAD to restart to stop the music since the screen wouldn't respond to touch.
I flashed Imo's lean Sense Kernel and haven't had a freeze yet. I hope this has solved the problem. There is a little lag now when I hit a widget or app shortcut but no more freeze.
Your lag is prob due to being in safe made, put in normal mode in speed tweak to rid yourself of lag.
Sent from my ADR6400L using XDA App
No, I'm in standard mode. I chose #1 in speedtweak. I varified at 1.4 ghz max/ 254 min
I couldn't figure out how to raise min value in speedtweak so I reinstalled set cpu and set min to 368. Seems to reduce the lag.
Still a slight lag but most importantly no screen freeze since installation.
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
mkitchen said:
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing a stock ruu in fastboot? You may try to go back to completely stock and then go from there. You could try a different rom too and wipe the system partition as well as the usual stuff first.
Sent from my ADR6400L using Tapatalk
I went back to the stock ROM using clockwork mod recovery, and the problem persists. I am wiping system partition now, but I did some of the stuff that has worked for me in the past such as dalvik, user data, and cache.
Wiping system may help but if that doesn't I'm not sure what else for you to try except fastboot flashing an ruu.
Sent from my ADR6400L using Tapatalk
Actually wiping system worked, I may have not done it in the correct order the first time I tried to flash back to stock. I really appreciate the help.
I can't take credit for any of the work here, I just modded the framework-res.apk and twframework.apk so that I could use the standard Gingerbread sliding tab lockscreen on my favorite ROM GingerClone. Thanks goes out to the Platypus Dev Team and everyone else involved in making this. The KJ2 Locks Mod does in fact work on GingerClone AS WELL AS OTHER ROMS, but it replaces a large portion of the theming elements of the UI with the ones from Glorious Overdose. I fixed this by modding the frameworks.
Call me crazy, but I'm a big fan of the standard Gingerbread interface, even on my old phone running CM7, I used the standard theme.
***BUGS***
-- Landscape tabs don't match portrait tabs
The only thing I've noticed so far is that the landscape lockscreen tabs do not match the portrait lockscreen tabs, but since the phone screen needs to be OPEN and locked for you to ever see this screen it shouldn't be a big deal. I've torn through the res files and can't seem to find the landscape lock tabs, so unless they're not images and are actually hard coded, I can't figure out where they're at. Maybe the dev could point me in the right direction?
Once again, I can't take credit for ANY of this. I just modded the work created by other people.
***DOWNLOAD***
https://rapidshare.com/files/2888540474/GingerClone_AOSP_Lockscreen_Mod.zip
***SCREENSHOTS***
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
ENJOY
Thanks man! So I'm assuming we have to flash this? And how are you getting a 2300+ score on quadrant? I tried tegrak and even at 1.1 it was freezing up my phone and doing the 1vib followed by 3vib when it didn't freeze it up.
JonathanBarca10 said:
Thanks man! So I'm assuming we have to flash this? And how are you getting a 2300+ score on quadrant? I tried tegrak and even at 1.1 it was freezing up my phone and doing the 1vib followed by 3vib when it didn't freeze it up.
Click to expand...
Click to collapse
try 1.2, that normally is pretty solid.
See I tried 1.2 but it froze even faster, and that's why I tried to downgrade to the 1.1
My q score suprised me too! First of all, it's the ROM. GingerClone is the only fully de-touchwized ROM available currently and it amazes me how well this device performs on a close to vanilla Android OS (especially for Froyo! I can only imagine that this phone would FLY with Gingerbread or ICS)
I OC'd using Tegrak to 1.125Ghz. Any higher and the system locks up on my phone regardless of ROM or kernel, but if I buy the full version of the app, I'm pretty sure I could get at least 1.4Ghz with overvolt. In the past I've noticed that especially refurbished phones can have issues with overclocking. My first LG Optimus could EASILY overclock up to 800+ Mhz stable, but I bricked it and the replacement they sent me was a refurb that couldn't handle more than 730Mhz and be stable.
But the real magic lies in using the latest version of V6 supercharger. I set mine to Aggressive 2. I had to run Quadrant a couple of times because I thought it was a glitch or a fluke the first time it broke 2000.
JonathanBarca10 said:
Thanks man! So I'm assuming we have to flash this? And how are you getting a 2300+ score on quadrant? I tried tegrak and even at 1.1 it was freezing up my phone and doing the 1vib followed by 3vib when it didn't freeze it up.
Click to expand...
Click to collapse
yeah, I forgot to mention that (figured it was self explanatory). You flash it in recovery.
I just flashed GingerCloneV2, I have not overclocked or supercharged, and my quadrant score was 2025. I ran it twice to be sure it wasnt a fluke. My phone has never even approached 2000 before. The highest score I have gotten prior to GC was 1695. This rom is crazy fast. Never would have imagined a rom based on kd1 could be this fast, considering the fact that supposedly kj2 is the most stable. I just flashed this, so I cant say if this rom is stable or not yet, but I hope it is. If it stays this fast AND its stable, then I wont even worry about overclock or supercharge.
yea same here, ran quadrant on stock gingerclone and got a 1950 and was like "whaaaaaat" its pretty awesome.
have tried supercharging it, with update 9 (and maybe thats where i'm going wrong), and after about an hour it begins to do the 1 buzz followed by 3 quickfire buzzes endlessly, and i'm forced to reinstall Gingerclone. do you guys think its because i should use update 8 for supercharger? its still blindingly fast though
edit: oh and i was wondering if there was some way to take that stupid "update social network" thing from the notification bar with this lockscreen mod? because it takes away the option under the display portion of the settings.
Thanks for the heads up on the lockscreen mod disabling the social status thing. Personally, I always left it on because when you turn it off you lose your power widgets in the drop down too. I know there are widgets that do the same thing, but aside from my launcher and the Google search widget I leave my desktop clean.
I'll have to look into the original framework from gingerclone and merge some of the code with the one from the lockscreen mod. I have some exams to study for this week, but I'll try to get around to it.
yoyowhatup22 said:
try 1.2, that normally is pretty solid.
Click to expand...
Click to collapse
assuming you're running the free version of Tegrak which only changes CPU clock, for the majority of SK4G phones running at 1.2Ghz will actually result in a net loss in performance over 1.1Ghz. Without upping the voltage along with the clock speed, the processor actually begins to encounter errors.
I run into the same thing on my PC. I can safely overclock to 3.0Ghz, and I'm more than capable of overclocking to 3.2, but performance rapidly degrades any higher than 3.01 Ghz without overvolting. At 3.0Ghz, my Geekbench score is around 6500, whereas at 3.02 it falls to under 3000, and at 3.2 it's at about 1200 (if you've never used Geekbench it uses a baseline score of 1000 which is equal to a 2005 PowerMac G5 dual core, and doubling the score means doubling the performance).
If I bump the voltage up from 1.25 to 1.3v, I can overclock even higher than 3.2Ghz, but my computer doesn't have adequate cooling for that and it overheats within about 5 minutes.
So as you can see, faster clock speed doesn't necessarily equate to having a faster phone, the exact opposite can be true. Overvolting would most definitely result in a performance spike, but keep in mind that there IS NO COOLING on a cell phone, not even a heat sink. Excessive heat can very rapidly damage your phone or even break it. Another thing to consider is that not all silicon is created equal especially when you're talking about CPUs.
Look at Intel for example, they sell the EXACT SAME cpu set at different clock speeds as a Celeron, Core2duo and Core2Extreme based on how the individual chip performed on a bench test. This is why overclocking is actually possible. sometimes you get lucky with a well manufactured CPU, and sometimes you end up with a dud that can barely perform at the clock speed it's rated at.
N00b-un-2 said:
Thanks for the heads up on the lockscreen mod disabling the social status thing. Personally, I always left it on because when you turn it off you lose your power widgets in the drop down too. I know there are widgets that do the same thing, but aside from my launcher and the Google search widget I leave my desktop clean.
I'll have to look into the original framework from gingerclone and merge some of the code with the one from the lockscreen mod. I have some exams to study for this week, but I'll try to get around to it.
Click to expand...
Click to collapse
alright, cool. its not a make or break thing for me, i dont mind it that much. but thanks for even saying you'll try!
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
FirePoncho86 said:
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
Click to expand...
Click to collapse
teuv runs at 880mhz.
its possible that an app or a background process is active. try this free app from the market, its called diagnosis https://play.google.com/store/apps/details?id=eu.thedarken.diagnosis&hl=en
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
FirePoncho86 said:
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
Click to expand...
Click to collapse
1096... thats not teuv, that the t11 kernel. heres the latest teuv http://goo.gl/5JwMT im using this one at the moment
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
FirePoncho86 said:
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
Click to expand...
Click to collapse
if you just booted, it should(for about 2-4 minutes) then it should drop. unless you have an active live wallpaper, an app thats not written very well, or a process thats gone wild. try that app i linked, let it run for a few hours, maybe you can find the cause.
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
FirePoncho86 said:
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
Click to expand...
Click to collapse
sounds like a bad download of teuv.
Bad download? I flashed it properly and it booted fine, until after the "optimizing applications" screen
is this the first charge since you flash the kernel? If it is, let the battery run out, charge it full and take a look at it again. I find that ICS really take a full charge to stablize its battery... my first charge after flashing a new kernel has always use a lot more battery than the second charge.
Alright, I'll try that... Also I went back to aosp+ because I really like it.
Also, android system is always using 20% cpu, even on idle..
I remember performing some tests with frequencies and deep idle - I wanted to find out the minimum frequency required to run music player screen-off with few concurrent processes. I remember reading how 400mhz is the optimal frequency for deep idle but cpu spy would always report it cruising at 1ghz and cross referenced with nstools DI stats, it was supposedly in deep idle. With DI off and bumping up the frequency to 800mhz, 1ghz took up the majority of operation time. Long story short, whatever combination I tested did not garner desirable results. That was a couple weeks ago, though. I've since given up on figuring it out.
Wait, are you having the same problem as me?Ive lost 5% battry just by having the screen on for 9 minutes...