When I plug my phone in to charge it stays at 800mhz instead of throttling down to 100-400mhz like its supposed to. I'm on pinnacle ROM and its taking forever to charge. Anyone else have this issue and maybe have a fix for it? Thanks.
Are you using Tegrak?
Yes, I do have it set to throttle down and using Ondemand scheduler.
Kill it and check if it get fixed. I recommend rebooting it after you change tegrak's settings.
Killing it seemed to have worked for now. How can I fix it so I can still overclock? It hasn't done it all the time, Just recently but I haven't installed any new apps or anything.
Sent from my Cappy using the XDA app.
Try clearing the app's cache. Maybe even Dalvik if you have too? Don't know.
I'll try, thanks man.
Sent from my Cappy using the XDA app.
well, getting rid of tegrak didn't help. Still charges and stays at 800mhz.
Sent from my Cappy using the XDA app.
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
prbassplayer said:
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
Click to expand...
Click to collapse
Tried that and still no difference......can't figure it out.
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
prbassplayer said:
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
Click to expand...
Click to collapse
It might be a problem with something included in Pinnacle but I can't narrow it down.
Ondemand 100min-1200max with stock voltage settings.
Na Fusion VII Beta is doing the same thing. I think its a tweak on the kernel maybe? I've been kinda busy and will be for the next few days, so don't know when I'll mess with different kernels.
I'll try the other kernel option and see what I can find.
Sent from my Cappy using the XDA app.
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
rmntruexjr said:
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
Click to expand...
Click to collapse
Using cpuspy or other monitoring software, what speed is it stuck at when charging? Are you running tegrak as well?
Sent from my Cappy using the XDA app.
Well tried a fresh install of Fusion and it still does it......
Geezer000 said:
Well tried a fresh install of Fusion and it still does it......
Click to expand...
Click to collapse
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
prbassplayer said:
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
Click to expand...
Click to collapse
I have flashed Fasty ki2, Fusion, Pinnacle, Apex and so far they all do it with or wothout tegrak.
Fresh look bump.....
Related
Probably is something on my Nook Color. But since I upgraded yesterday from 41 to 7.0.2 there is noticeable degradation of youtube videos playing on the default browser. Used to be fluid now is very choppy.
About the NC
Stock ROM 1.20 (upgraded yesterday)
CM 7.0.2 (from SD using Verygreen's instructions)
NO other kernel changes
EDIT: I think I confused everyone on my post..
I meant that I kept the NC stock ROM and upgraded to the new one (1.2) released by B&N on 4/25
The NC is running CM 7.0.2 from uSD without kernel changes. CPU settings: Performance. Max: 925Mhz
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
There's a 1.3 kernel??? Dalgrin's? Where?
silentbushido said:
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Click to expand...
Click to collapse
shawn605 said:
There's a 1.3 kernel??? Dalgrin's? Where?
Click to expand...
Click to collapse
Kernel Manager app
Do not set the overclock on boot until you know its stable.
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
LBN1 said:
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
Click to expand...
Click to collapse
The 1.3ghz is ready to release. It is just a matter of whether your Nook can handle the overclock or not. It should boot regardless though. The overclock is not set until after the OS boots to UI.
did you have OC before installing 7.02? installing 7.02 resets your cpu back to 800 MHz, and you need to reinstall OC kernels to get it back to what you had before
lanzagas said:
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
Click to expand...
Click to collapse
Been using the 1.3 oc kernel flashed through kernel manager. Seems to be working fine at 1.3 with oc set in cm settings.
No YouTube issues for me on new cm7.
Loving my week old nook color so far.
Sent from my HTC HD2 using XDA App
I didn't have a OC kernel before nor after.
I was using CM7 CPU settings. Max:925Mhz.
I had the 1.1 stable overclock before and currently am using it again. When I added the 1.3 uimage onto my Nook and tried to reboot, it stopped before the CM7 logos popped up. Blank screen with a "-" cursor and that's about it.
Glad to hear it is almost ready to be released, and will certainly try it again.
Oh, thanks Dalingrin for all your hard work on the kernels!
Hi guys. There is something wrong with my phone and hoping you guys could help me work out what it is.
I'm currently running DlevROM 4.2 with Dark Core 2.9.3 kernel with JV5 modem.
For some odd reason, with 80% of my phone calls, after about 5-10min the other person can't hear me anymore but I can still hear them. I'm sure i haven't accidentally touch the mute button or anything because I take notice of the screen the whole time and it was off.
This same problem also occurred when I was with Apex 8.2 with TalonDEV kernel. And also occurred when I was with JK4 modem.
Any idea what the problem might be guys? Maybe a Gingerbread problem phone?
Have you tried flashing a different modem?
Sent from my blazing fast Captivate running Continuum GB ROM using Tapatalk Pro
Rhiannon224 said:
Have you tried flashing a different modem?
Sent from my blazing fast Captivate running Continuum GB ROM using Tapatalk Pro
Click to expand...
Click to collapse
Yeah from the default Apex 8.2 modem, I flashed JK4 modem. Still occurs
Wasnt sure where to post this...so here. I have a problem where my apps will lag and take forever to load (market, maps, browser etc). But, i will reboot my phone and everything will load super fast. Is this a modem issue?
Sent from my Apex'd JVR Matted Blue Cappy
No, kernel.
would the fact that i'm UV'd casue this?
I'm currently using Talon .4.4.21
talleywhacker said:
would the fact that i'm UV'd casue this?
I'm currently using Talon .4.4.21
Click to expand...
Click to collapse
uhhhh....yeah?
you do know what undervolting does right??
I have galaxy s since last one year and i love it... However my phone has become very slow these days.. I tried several roms and kernels.. Formatted both internal and external SD cards... But still it is very slow... I remember that I dropped it 3-4 times... Is it because of it?
Can someone suggest me please... What should I do...
Sent from my Galaxy S using Tapatalk
Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
309041291a said:
Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
Click to expand...
Click to collapse
Can I do anything related to the hardware? I mean how can i check if it is not giving 100%?
Sent from my Galaxy S using Tapatalk
I'm no expert so I'm not sure. Best bet would be to replace the hardware which Costs a ton of money. Its better to just a get a new phone. Either that or maybe mess around with new ROMs some more. Maybe you are wiping your phone incorrectly or maybe you use it too much
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
my suggest...
1. update your firmware to last version (2.3.6).
2. try to change kernel and custom rom.
3. maybe, with some different kernel and custom rom, you can choice the better option for your device. for example, try using kernel semaphore (gingerbread) and custom rom F1 or other.
I would be very surprised if physical trauma has simply caused a slow-down in speed. It would more likely show itself as random reboots and other more obvious symptoms.
Much like Windows, after a lot of use, it slows down - you have said that you've flashed other roms, maybe you just haven't come across a good one; there are after all a lot of different ones...
I would suggest the deodex-ed / rooted stock rom from RAMAD Gingerbread JVT. As I remember it was always quite stable and fast.
The hardware components inside a modern phone will not wear-out after a year - they are not moving parts! - when ram or a processor wears out it usually results in total system crashing not just a slow down.
Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?
Have you ever tried Advanced task killer? Or even killed tasks?
zadusimple said:
Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?
Click to expand...
Click to collapse
Did you try the ics roms. These r pretty fast..specially team icssgs.
Sent from my GT-I9000 using Tapatalk
Try ICSSGS RC 4.2. I had the same situation as you. It was fine for one year and I was using Darky rom by that time. Suddenly I started feeling that my phone is too slow. Lot of stuck. Sometimes I had to remove battery just to restart.
Now running above ICS rom with Devil 14.2 Kernel its rocking ...
yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom
gezze said:
yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom
Click to expand...
Click to collapse
Yeah, and you can just use the ATK widget when you close out of something press the icon and it kills all the background apps...
I will surely try ATK and ICS roms as per your suggestions...
Sent from my Galaxy Nexus using Tapatalk
keep us updated...
Just get stock jw1, flash with reparation to wipe everything, then do a factory reset via secret dial code. Now install semaphore 2.5.0 kernel. Dl superuser to get root. Now install thunderbolt tweaks the main package and the 60lmk other addon(read thread how to) . This is the best setup i can think of in terms of speed bat life and functionality. Next step look in pikachus Android optimization thread and remove the bloatware listed there, basically remove as much bloat as possible. Enjoy ur fast phone.
Sent from my GT-I9000 using Tapatalk
Perhaps you should try the ICSSGS RC4.2 with Devil 14.2 LED VC Kernel. I'm on it and its awesome, my phone lags no more and I'm using it for my primary phone.
Sent from my Galaxy S using XDA Premium
Hi, I have a Captivate running Jelly Bean 4.2.1 (Slim-4.2.1.Beta.1-OFFICIAL) on a Semaphore kernel. It works perfectly when it's plugged into a computer through USB. Otherwise, it reboots into recovery, every single time it goes into standby, even when it's on a charger. I've tried raising the CPU speed, uninstalling SetCPU, re flashing the ROM, and nothing helps.
Is this a hardware issue, app issues, or does it have to do with the ROM or kernel? I had CyanogenMod 10.0 with a devil kernel running on it previously, and it did the same thing.
majorbozo said:
Hi, I have a Captivate running Jelly Bean 4.2.1 (Slim-4.2.1.Beta.1-OFFICIAL) on a Semaphore kernel. It works perfectly when it's plugged into a computer through USB. Otherwise, it reboots into recovery, every single time it goes into standby, even when it's on a charger. I've tried raising the CPU speed, uninstalling SetCPU, re flashing the ROM, and nothing helps.
Is this a hardware issue, app issues, or does it have to do with the ROM or kernel? I had CyanogenMod 10.0 with a devil kernel running on it previously, and it did the same thing.
Click to expand...
Click to collapse
Have made you many any changes/mods?
Also, did you try going back to stock KK4 and reflashing the rom you want to use?
If it's recurrent on 2 different Roms, then it's most likely something you restore or some mods. Hardware issue is possible if it does it on stock.
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
Have made you many any changes/mods?
Also, did you try going back to stock KK4 and reflashing the rom you want to use?
If it's recurrent on 2 different Roms, then it's most likely something you restore or some mods. Hardware issue is possible if it does it on stock.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
No, I haven't really made any changes. It wasn't doing it on stock a couple days ago, before I flashed the new ROMs. I installed an App (wakelock powermanager) that keeps the cpu running. That fixes the problem but it drains the battery way too fast.
I'm trying to figure out how would be the best way to go back to stock.
Thanks
majorbozo said:
No, I haven't really made any changes. It wasn't doing it on stock a couple days ago, before I flashed the new ROMs. I installed an App (wakelock powermanager) that keeps the cpu running. That fixes the problem but it drains the battery way too fast.
I'm trying to figure out how would be the best way to go back to stock.
Thanks
Click to expand...
Click to collapse
The best way to go back to stock is the one I mentioned, Odin one click KK4 (in the dev section).