Database Info

OMAP Clock and Overclocking v1240

Been lurking for a while, made one or two posts, trying to learn what I can and avoid asking all the typical n00b questions.
But I've got one.
I'm using a Vodafone v1240 and WM6 English 5.2.1616.18120 Standard v3.4. When I first installed an earlier version (v2.0, I think), when I opened up OMAP Clock, it showed running at 132MHz. I bumped it up to 204, but maybe ten minutes later it was back at 132. I then bumped it up to 180, and it's stayed there since. When I installed v3.4, it was still at 180.
But no matter what I set it to, within a few minutes it switches itself back to 180.
Am I doing something wrong? Or is my phone trying to tell me to stop messing with the clock and it's happy at 180?

From what i remember reading, when your phone goes to sleep (screen goes black) it resets it back to the phones default (which should be 180 as far as i know). i've made myself a shortcut and OC'd it to 252, personaly i've not had any problems, but these results vary.
PS: Mine is originaly a T-Mobile SDA

Thats right after every sleep it goes back to the standard clocking.
I'm using Tornado Power Control for overclocking and my phone works fine with 264 MHz.
Here is the link
http://forum.xda-developers.com/showpost.php?p=1362675&postcount=6
Have fun....

I just found an interesting "bug" with Vox Display Driver and the OmapClock, it's kind of a bug i like actually, since the Vox doesn't update when the phone is in sleep, the OmapClock stays at the designated speed

Yeap, the screen doesn't refresh until you press any button. So if you leave the screen idle at 2pm, it will show that even at 10pm unless u refresh it by pressing any button, same with the clock rate

264 mhz what thats high
KingAxel said:
Thats right after every sleep it goes back to the standard clocking.
I'm using Tornado Power Control for overclocking and my phone works fine with 264 MHz.
Here is the link
http://forum.xda-developers.com/showpost.php?p=1362675&postcount=6
Have fun....
Click to expand...
Click to collapse
are you useing qtek 8310 and if you does it doesent it gett hot or burn the proccesor when you over klock it to 264 mhz

I'm using a xda phone which is the htc tornado without wlan.
And the device is not getting hot or the porcessor burned, the only thing is that the phone can stopp working, so that you have to take the battery of and switch it on again.
Try with omapclock to get the best speed for your phone, before you use Tornado Power Control.
Nice day

has anyone successfully set up the tornado powercontrol with the 'hide' option. every time i start my device, powercontrol comes up. seems that hide does not do anything...
any help?

it works now. you have to make sure, that 'hide' not has a blank at the end like 'hide '. it would not work like that.

[Q] Serendipity7 question

Hello XDA,
I've recently purchased a samsung infuse and there were a few things standing out that i was wondering about. When i bought the phone, it had already been unlocked + rooted + flashed with S7, it should be running on the default kernal that came with S7. Afterwards, i installed dynamicRAM's tweaks in the development section.
1) Lock screen lag.
Wondering if anybody else is having this problem. When i hit the unlock button, theres a small lag time present before the screen activates, subsequently, when swiping my finger across to unlock the screen, theres a lag time before the imagine/slider/what have you responds. At first, i thought this had no functional problem and that it was just a little ugly. Until i received a phone call and in my attempt to answer it, the slider didn't respond. I wonder if this is perhaps a kernal problem?
2) If it is a kernal problem, is it compatible to try flashing the infusion 1.1 kernal overtop the default S7 kernal (Granted that the phone itself is first backed up with tibu and a NANDroid backup performed). Would this help the above problem?
3) The seller had the phone overclocked to 1.6 ghz with setCPU which isn't a large problem as its an ondemand clocking. however, the battery usage seems to be lower than expected? Note that i do not use data plan so thats turned off, wifi is turned off, but i like having the brightness as full (i acknowledge this eats up a lot of the battery).
Leaving the phone on my bedside table for sleep, it depletes 6% over the course of my 6 hour sleep. 1% an hour seems pretty fair. However yesterday, i unplugged from 100% at 2pm and used it till the following day 10 am. During this period, it depleted to 49%. I used aldiko for my book for an hour before bed. Sent a total of 14 texts, received 18. No music player was used, rest of the time the phone was essentially idle. I'm a little surprised at this.
I have yet to calibrate the phone but it is only a month old, granted it was calibrated after flashing S7, could this be the problem? I don't think the phone is undervolted yet, would voltage control from the market help this by lowering it a bit?
4) sometimes my volume slider just dissapears, i don't know why. Using the volume rocker on the homescreen usually has the ringer volume pop up. But once in a while, it stops showing up, the settings still work, but the slider is invisible. It is not restored upon reboot, and it eventually comes back and dissapears again.
5) First phone call has no audio. I believe this is a documented problem with S7, just asking to confirm this.
6) A couple of albums in my music library aren't tagged properly in the player despite being correctly tagged with MP3TAG on my computer. After some research, i think i found this is a GB media scanner problem. Is there a way to correct this? Perhaps take an apk from another ROM and replace it?
Many thanks to anybody who takes the time to read this thread

Odd ARHD Issue (All 4.1.xx versions) - Requires Removing Battery.

So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?

Does it seem to happen at a certain time? After opening a certain app?
Does sound odd though.

The only certainty I can say is that it happens when no applications are open and the screen goes into lock mode. It also happens regardless of the launcher being used (I use FX, my brother uses HTC Rosie, the other uses Go).

gotpriest said:
So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?
Click to expand...
Click to collapse
+1 I have this issue too...I lowered my overclock and it's been working fine since
Sent From My HTC Sensation 4G

I assume that is performed through SetCPU? Or Daemon.
In Daemon, there's only four options, Sleep and Wake Max, Sleep and Wake Min - how did you fix yours?

Anyone offer a tip on this?
I don't have SetCPU on my phone (looks like it was replaced?)
Don't want to bork my phone, just wondering how to dial down the overclock slightly to prevent this hard crash.
Thanks

ARHD has Daemon Tools I think, with this you can reduce your overclock.
However my suggestion would be to increase the Maximum sleep CPU speed. [Sleep Max]
I can't remember but I think be default it is at ~440MHz, increase it by around 600MHz and see if that fixes the problem. If so you can reduce it gradually to save battery, stopping if the problem redevelops.

Thankee very much!

I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?

tk_xda said:
I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?
Click to expand...
Click to collapse
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.

Grandelama said:
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.
Click to expand...
Click to collapse
Does this particular known issue apply if the screen turns off on its own due to inactivity time? What about if camera app is in background?
Does faux kernal need a camera fix similar to the one for bricked?

[Q] Want to undervolt CM10. KT747 kernel not working?

I wanted to undervolt my CPU a bit to hopefully get a better battery life. Especially now that I've gotten a tablet (Nexus 7, so nothing to sneeze at) I'm using my phone as a Android device a little less and most of my gaming on it allows for some very low CPU speeds anyway. So to that end, if I can squeeze a little more out of it, it seems like a good idea. I've already taken a LOT of other steps, including minimizing the number of things running all the time (it's actually a little annoying how often things stay running in the background that I just don't need, so Android Assistant is now one of my favorite tools, though I wish its "quick boost" widget and the automatic selections in the process list could stop more apps) and I've even removed a lot of the built in things that run all the time that I don't want like live wallpapers (I really don't understand why it likes to run even if you're not actually using a live wallpaper) and DSP Manager (I want the sound to be unmodifed anyway) among many others. I use SetCPU to set the CPU lower under normal operation with the conservative governor and to even set it extremely low when the screen is off with the powersave governor. WiFi and mobile data stay off when I'm at work and often even at home. Overall battery life is generally quite good, but sometimes it's still going down faster than it really should even just idle with the screen off. If I could just squeeze a little bit more out of it I'd be a lot happier. Plus it also can get fairly hot despite the underclocking on those occasions I do play a game thanks in no small part to the fact that I'm having to use an Otterbox on it (which means not one, not two, but THREE layers of insulation on the back side when Samsung pretty much designed it with one in mind. More heat escapes through the glass at the front than the rear and that's saying something given that glass is a pretty strong insulator... Otterbox truly needs to design these with some sort of thermally conductive material or something.) I don't know that undervolting would help a lot with either since I probably can't go down by much, but it most certainly can't hurt...
Ok, so I grabbed the KT747 kernel for the Verizon SGS3 from here (I got the AOSP Jellybean version, not Touchwiz) and tried to install it using the update function in ClockworkMod then cleared the cache partition and Dalvik cache both immediately after. The moment I hit reboot, the phone got stuck on a black screen or shut off (I couldn't exactly tell which.) I didn't find a convenient CM10 kernel alone, so had to basically just put the full CM10 update which of course was a bit inconvenient since I had to redo a lot of stuff. Is that the incorrect way to install it? So far everywhere I've looked everyone just skips over the part about the actual install process -- they just say to install it. Given that it's distributed as a ZIP complete with the normal stuff one would see in a recovery update ZIP I assumed that was the appropriate way (and it did say it was successful and all.) Well, I've read in that thread and others that sometimes it just doesn't work with some phones, so my assumption is that was the case here, but just in case if I've installed it wrong it would help to try doing it right, lol.
Is there any other kernel I should try with CM10? I don't need any special features (definitely no Voodoo sound or whatever -- again, I like the sound being unmodified anyway) beyond the normal stuff other than the ability to undervolt the CPU by a bit. I'd like to do the undervolting with SetCPU if I could as it overall suits me best of the tools I've tried and even has a "safe mode" ZIP file that can be installed as if it were an update in the recovery menu that would stop it from doing its thing if something goes wrong, thus making it safe even to use the set on boot option (though I suspect that with my current underclocking the CPU will remain stable until I push it at any reasonable undervolt level.) Or am I maybe even missing something and CM10 actually has the ability built in that I just haven't found anywhere? I see options to set the CPU min/max, governor and I/O, but nothing about things like voltage (or overclocking for that matter, where I assume such settings would probably lie.) From my understanding, the fact that SetCPU lacks even a tab for voltage control on here means that it thinks the kernel doesn't support it though.
EDIT: Oops, forgot to mention, but I did do "fix permissions" after clearing both types of cache. Also, the system is definitely on when it just goes black. When I press the power button I get the power LED on green indicating that the battery is nearly full and the hardware button backlights come on.

You're correct on assuming that since SetCPU doesn't have the tab the kernel doesn't support it. Try leankernel. It's what I always run. I don't have the URL handy but it's on rootzwiki. It has a TW and AOSP version so obviously make sure you grab the right one.

Ok, something's odd here. I tried the LeanKernel for Verizon (lk_aosp_jb_vzw-v1.9.zip from http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v19-111012/ -- or, more accurately, from what I believe is his official page at http://imoseyon.host4droid.com/s3/#!/view=details/lang=en/sort=na) and again the same thing. Just a black screen. I can get the lights to come on behind the bottom hardware buttons, but it's not working right. It seems it DOES boot up enough to where I can connect with adb thank goodness (I had to pull the battery twice before I thought to see what would happen) and get a shell, so I tried running lkconfig and setting it to not undervolt by default (I don't really understand why so many kernels under/overvolt/clock by default when you can so easily mess with those things via software after it's actually up and running) but even after another reboot or two it still didn't work. Again, I cleared BOTH caches and ran fix permissions after installing the kernel from the zip file. Also, I'm trying TWRP now instead of ClockworkMod as it seems to be quite a lot better (touch interface in the free version, ability to choose WHAT to backup so I don't have to backup data every time -- which is really handy since I lack the free space to backup data and always have to wait for CWM to error out -- and a bunch of other nice little things) and I'm getting the same problem with it.
I even tried waiting a while in case it was doing the "Android is upgrading" thing where I guess it's basically just rebuilding the Dalvik cache, but the screen still wouldn't come on at any point after that even after another reboot. It's worth noting that the adb shell it gave me went straight to root (eg a # sign on the prompt) whereas under a normal bootup it should be at user level first requiring me to run su to get root. Am I just missing something or what?

Screen wake issue - battery pull

Hi guys
I know this issue has been mention a bit, and I've searched through countless threads but I find the search system on the site a little counter intuitive, like forum searches will only bring up the thread, not the actual key word references and I have to search again within the threads to yield results, but I'd like to clarify a few things.
I'm running Cm11 nightlies on the phantom kernel and I have the screen wake issue. It takes multiple attempts to wake up the screen. OK.
I understand this is a problem with Kitkat roms for our device. However, my case is that there is a 50-50 chance that the screen doesn't wake up at all and I have to pull the battery. This makes any rom almost unusable for me as 1 out of 2 times I have to pull the battery to access the phone, Music continues to play, and I can skip tracks or play or pause, and even take photos, which means that the phone unlocks only the screen doesn't light up. If I hold down the power button, I can feel the phone vibrate to indicate the shutdown menu and sometimes I can blindly reboot or turn off the phone by tapping the screen roughly where the menus would be, so the touch is working.
Roms have been reinstalled and dalvik wiped etc but no improvement
I'd like to know if there's something I've done wrong to have so much poor luck. I don;t mind waiting for the screen to light up, or even a few tries, I'm aware of the unstable nature of nightly roms, and I am happy to use it and contribute usage stats to help further development, but not being able to get the phone on is a massive problem, especially when receiving a call
If anyone has any tips, I;d love them to let me know so I can add here as a one stop thread to general KK problems and work-arounds.
Pr m,aybe it's just my phone
Current mods
Xposed framework modules
greenify
kk bugs fixer (currently disable as seems to make no change)
minminguard
no lock home
Xposed gel settings.
No crazy overclocks or aggressive governers (tested with ondemand, intelliactive no difference, but great battery)
General rom experience apart from this - Excellent battery and very snappy, only a little skipping with audio (even with cache increased to 4010)
Cheers people!

try another kk rom
i did not use cm11 b,coz i had problems with the low reciever volume
tryout carbon rom or vanir aosp
they are too good

SOLVED
OK, thanks for the suggestions, actually I had the same issue on all roms that I tried.
The fix was the following, I disabled the NO LOCK HOME Xposed module and now all is back to normal.
i think there was an issue with it auto unlocking the screen on wifi or cel tower that caused the lockscreen to crash from time to time or get stuck. All is working like a dream now.
It~s a shame really, here in Brazilo with the rise of the Iphone and the high robbery rate, it´s quite common now for thieves to stick their gun in your face and demand your password or for you to unlock;disable the password during the robbery so that they can reset the apple acount or phone for resale. With nolock home I could save the cel towers near my home and work (for my walks to and from the subway) so that in case of a robbery, the phone just opens up and shows its unlocked, and then I can remotely wipe it later without giving up account details. Anyway, anybody else with this problem, thats the source of the Issue