Database Users

[q] cm 7 rc1

Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance

eichl0r said:
Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance
Click to expand...
Click to collapse
Wipe EVERYTING, install CM7 then install HCDR.Kernal 4.1 (4.2 doesn't work as well) then use another overclock program, not setcpu, it doesn't work well with CM7. Hope that helps you!

* First, try flashing Kernel v4.1. CM7 comes with Kernel 4.2 by default, and, because it is clocked at 768 max, it leads to a lot of stability problems for everyone. Look for the HCDR.Kernel Topic in Wildfire Android Development Zone
* After that, you can install SetCPU. The SetCPU Dev has a thread here on XDA where he has posted the APK of SetCPU for download. Just enter SetCPU in the search bar and you should be able to find the thread with no issues. Here, you can set the max (Upto 710 recommended) and min (upto 245 recommended)
This should solve your lag and stability issues. If it still doesn;t, two more apps which can cause lag are (Note: This affects only a small %age of members with CM7)
* SetCPU (Alternative: OverclockWidget)
* ADW.Launcher (Alternative: Any other Launcher)
Oh, and CPU Settings FC's for everyone, from the time it was implemented. Looks like it is not ready yet.
Good Luck

hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great

eichl0r said:
hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great
Click to expand...
Click to collapse
That is rather weird, because, many are keeping it at 710 MHz Max and having no issues. What is your battery temperature when you keep it at 691? (And at idle. It is normal for the phone to get warm when you continuously run a heavy app like a game on it, also, I am sure you know this, but dont measure during charging, it does get pretty warm then )

hmm i played around with the phone a little and then put it in my pants pocket, after wa while when i put it back out it has restarted i guess and i was very warm at the back...hmm ill test it a little perhaps it was a one time thing

Possible bug with smartassV2 and Semaphore kernel 1.9.0

Hello everyone, it turns out that took a few days testing the module in different roms listilloV2 and talondev kernels 5.2.5 and semaphore bigmem bigmem also 1.9.0. Anyway, I've noticed these last few days especially with the kernel semaphore when it is off screen not receive calls as if in deep sleep and not wake up because when I burn to the screen to get the typical message that a number has called me. Also if I try to display on call from another number if it works perfect. Trying another module as ondemand works seamlessly with screen off. Anyone else happened?

Hello again, well just wanted to say that apparently I have been testing the module and is not smartass v2, but the thunderbolt script I had. I have changed to the latest version and so far I have not had any problem receiving calls.

Sorry, but another problem arises I am intentanto googlemaps update from the market and will not let me, reads "The package file is not signed correctly." I've downloaded from a link, I tried to install and tells me that the application is not installed. Any solution? Thank you.

I think its a Market issue. Try again later. A few other people also experienced this.

ok, thanks I'll prove it.

Well continue with my research in particular. I thought it was fixed the issue I receive calls but no, because even if you upgrade to the latest version of thunderbolt is the kernel semaphore v2 smartass had it in September but was still in ondemand CPU with what was normal to receive calls, but if you switched to v2 smartass anymore. At the end change the kernel to Talondev 2.5 and 0.5 .. still doing the same smartass v2. Already that the solution is not to use this governor but was very fluid mobile behavior. Have proven to with OndemandX and InteractiveX and to come I have to put them fluids voltages not so aggressive. Which of the two recomendais? My voltages are:
1000 ---- 50
800 ------ 75
400 ---- 100
200 ---- 125
100 ---- 150
and interactiveX ondemandX or simply have removed 25 at each frequency:
1000 ---- 25
800 ---- 50
400 ----- 75
200 ----- 100
100 ----- 125
Another thing about the market. I think that ultimately goes wrong? I do not let me install the latest version of Googlemaps 6.0, and that that changing the kernel thought that maybe was solved. Today I said I have another update Spy CPU and when I upgrade just to let me open it or uninstall or because there acutalizacion. .... Not that rare.

Another thing, for more information, I have the rom Innovation V14 F1, and so far had not had any problems.

snapx said:
Well continue with my research in particular. I thought it was fixed the issue I receive calls but no, because even if you upgrade to the latest version of thunderbolt is the kernel semaphore v2 smartass had it in September but was still in ondemand CPU with what was normal to receive calls, but if you switched to v2 smartass anymore. At the end change the kernel to Talondev 2.5 and 0.5 .. still doing the same smartass v2. Already that the solution is not to use this governor but was very fluid mobile behavior. Have proven to with OndemandX and InteractiveX and to come I have to put them fluids voltages not so aggressive. Which of the two recomendais? My voltages are:
1000 ---- 50
800 ------ 75
400 ---- 100
200 ---- 125
100 ---- 150
and interactiveX ondemandX or simply have removed 25 at each frequency:
1000 ---- 25
800 ---- 50
400 ----- 75
200 ----- 100
100 ----- 125
Another thing about the market. I think that ultimately goes wrong? I do not let me install the latest version of Googlemaps 6.0, and that that changing the kernel thought that maybe was solved. Today I said I have another update Spy CPU and when I upgrade just to let me open it or uninstall or because there acutalizacion. .... Not that rare.
Click to expand...
Click to collapse
Don't understand your English. Sorry
snapx said:
Another thing, for more information, I have the rom Innovation V14 F1, and so far had not had any problems.
Click to expand...
Click to collapse
F1 includes ThunderBolt!

Sorry for my English, but I use google translator. Well because I think this solved everything. In reviewing the system folder / etc / ini.d faltavan me and S98screenstate_scaling S98system_tweak files. Perhaps without realizing it clear it but everything works normally. Rom that already incorporates thunderbol Innovation F1 but I wanted to update it if it were a problem. So far it seems that everything is resolved. Thanks anyway for everything.

Overclock Cyanogen settings

I have rooted abdroid 2.3.4 with cyanogen 7 and in the settings there is one that i can change the maximum value to cpu...Now is at 998....what value above that is the safest to choose with out the phone have any problem???

depends which rom it is
some can go up to 1.5 and some cant

Can also depend on the phone, I have 2 hd2s, one chuggs along nicely at 1075mhz, the other gives random slowdowns / hangs (4-5 a week,not lots but enough to be a pain) at any setting above 921mhz. Same rom,same installed apps, same data.

Well here are the Phone Info
Model
HTC HD2
Andorid
2.3.4
.......
15.42.50.11U_2.15.50.14
Kernel
2.6.32.15_tytung_r10-gbdfeaac
Mod Version
CyanogenMod 7-05252011-NIGHTLY DESIRE
GRJ22

Anyone?
Sent from my HTC HD2 using XDA App

The best thing to do is scale up gradually, try each step above 998. OC then try it for 24hours, then try a step up and try it for 24 hours and so on. Do not check set at boot though just in case you pick a speed that causes problems.

What can go wrong???How do i see that it cant support a number??We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????

What can go wrong???
It coukd stop booting and require a hard reset/backup restore.
How do i see that it cant support a number??
It will start to give force closes, hang, reboot, feel sluggish..
We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????
Do a cwm backup and just try it, worst case scenario is it doesn't boot and you have to restore.

ntisco said:
What can go wrong???How do i see that it cant support a number??We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????
Click to expand...
Click to collapse
I would guess that the majority of users are overclocked. I, for example, am running my phone smoothly at 1.2 GHz without problems, but to be honest I scarcely notice the difference with overclocking. Dorimanx's kernel with 1.61 GHz overclock didn't really perform any better than Tytung r14 at 1.2 GHz.
Just do as the others said and try it out whilst making sure to uncheck 'set on boot', but I think any speed should really be fine.
I don't know what the general opinion is on this (some devs say it isn't a good app) but use setCPU in order to create profiles if you want, thus being able to reduce your standby battery drain and stuff like that

In the quandra the info of the phone whrites that the cpu is up to 1190mhz and know is at 998.Is this true?Can it go that much?
If so we can put it at 1113 that its safe?
I know that i ask again and again but i dont want the phone to lose or damage

Youre best bet would be to download setCPU and try different clock speeds . the thing about setCPU though is it has a stress test . So after you set a speed . you can run the stress test to test if its too high a value or if you are safe to run at that speed . just dont tick the box that says "apply at boot"

My phone (currently Dorimanx ROM) is stable at 1536MHz. On Cyanogen it was similar. On 1612 it had freezen for a few times while watching a flash video on youtube. Set it to 1,4GHz, and it should work fine. Phone will not damage, data too. Just as they written above, do not click apply at boot.
And make stress test for more than 10 mins, because I have done it for 10 mins, and as I written, it had freezed during YT watching.

The topest that it has is 1190..that is the last option !!!I put it at 1113 for one day know and i made a profile to go 573 when i close the screen.
Tomorow i try the next option antil 1190 ...and we will see

Tytung r10? Why not upgrade to another Kernel?
I think that's the core issue. Dorimanx kernels i.e. can be clocked solid to 1.2ghz

Oh, I've completly forgotten. I have used Dorimanx kernel with Cyanogen. But it doesn't let you reinstall rom from settings (Factory reset). You need to reinstall rom from zip or restore backup in CWM. On 1190 it will work stable for ever

[Guide][Theory] Samsung Galaxy Note ICS Build SOD Fix!

I have found the fix for SOD's on ICS builds (based on i9220 leak kernel)!!
THIS YOU DO BY YOUR SELF! I TAKE NO PART IF YOU HAVENT READ THIS THRU AT LEAST 2 TIMES BEFORE DOING THESE STEPS!
First of I had a theory of the i9220 kernel and its CWM that in one way it does not represent our hardware right. It has its differences and they are more on a file level then anything. This can be shown easy by trying to format /system. By doing so you will get in to a world of trouble (so don't try it, just trust me)
So my first thing as I have never had a SOD was try to RECREATE a SOD. So my theory is/was that the kernel provided for the i9220 is the real culprit in this scenario and that by flashing RADIOS with its built in CWM is a MISTAKE!
And boy was I right! I installed a random N7000 radio .zip thru CWM (Now when I say CWM I do NOT mean some crappy .apk or app that does it FOR you. I mean the CWM you enter by starting the phone with Power + volume up + home button) and rebooted the phone.
I played around with it and let it rest for 30min. When I was going to wake it up again... SOD!!
Mission Accomplished!! Recreated Error!
So now ... how to fix it...
First off wee need to learn how Mobile Odin works and why this method works to fix it. When Mobile Odin is instructed to flash a ROM or anything else (like a radio) it boots to ITS OWN KERNEL! That is the file that Mobile Odin downloads on first run!
Now IF you are going to use Mobile Odin while on any ICS build (except the original i9220leak! Important! Mobile Odin will NOT work on stock i9220 leak!) you have to be 100% sure that you are PROPERLY ROOTED!
So Steps...
Step1: Get ZCLP1.zip Radio from the Radio Thread and extract the modem.bin file.
Step2: Get Mobile Odin and just flash modem, nothing else. The modem.bin you just extracted.
Step3: It should reboot and enter the Blue Odin Droid Kernel and flash radio.
When its done it will reboot again. And you will probably be SOD Free!
Hit the thanks button if this worked for you guys. Thanks for reading.

Oh btw I don't think that it is locked to use only that modem. I had la3 radio before and I didn't suffer any sods so don't get to blind on just the Chinese radio...
| GalaxyNote ICS | Tapatalk |

im on midnight 2.0 ics.i done what u said in the post.i just had a sod.
here is how it happened.i pressed wifi in pull down notification.it was stuck ..wifi would not turn on after the screen turned off and try to awake by using power button.it was dead.it would not do anything.had to hold power button for couple of min to restart.

Im currently on gb, used ics for a couple of weeks since chinese leak. Im not a 100% sure, but i really think it has something to do with wifi. I never really tested but I always had the most sod at home while connected. Rarely had sod at work, which was cellular data H+.

There is another method and that is to increase min CPU speed from 200 to 500mhz. Has worked for some...
| GalaxyNote ICS | Tapatalk |

Thanks mate, i'm gonna try some of that.
These SOD are making me crazy :/ Some day i can have 0 SOD and the day after 1 per hour...

You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA

super_sonic said:
You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA
Click to expand...
Click to collapse
But wouldn't that drain the battery faster?
Sent from my GT-N7000

I only get sods when wifi doesn't activate too. If it doesn't switch on immediately then the phone won't come out of sleep. I just restart manually when this happens instead of letting it sleep.
Sent from my GT-N7000 using XDA

I get SOD with or without wifi completely randomly. I'm going to try increase CPU see if that works.

excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx

It's not specific to the radio. I've done Mobile Odin Pro to try many different radios. Each time, I'd get an SOD.
Folks have also reported getting an SOD WHILE in Airplane mode. This completely puts the baseband issue out of the picture together.
If it's in airplane mode, it can't be a WIFI issue too.
The kernel itself is just bad and it has its quirks.
Due to the inability to get a logcat when it is in a SOD state, it makes it very hard to pinpoint what is causing the SOD.

MaZaGnGy said:
excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx
Click to expand...
Click to collapse
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!

robmeik said:
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!
Click to expand...
Click to collapse
Nope, it's Sleep Of Death. The rest is correct
Sent from my GT-N7000 using XDA

We need a SOD-off app

Look for wake lock power manager in play store. It creates a wake lock, preventing deep sleep, and consequently a SOD. For the price of a low battery autonomy.

I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.

masiullah said:
I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.
Click to expand...
Click to collapse
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.

Akiainavas said:
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.
Click to expand...
Click to collapse
Is there any way or app which stops using certain frequencies.

[Q] (Q) overclocking on cm10

hi i have successfully flashed cm10 and it has been running without problems but i tried overclocking using the bootloader but then i got stuck in a bootloop. this are the values 1200/58 900/44 600/31 300/21
If any one can help me it would be greatly appreciated, i am using the kernel is the installation guide on tezets cm10 post btw.THANKS
edit: i have solve the bootloop but my main question is how to overclock. thanks

I use the following values for over clock on CM10 (well on almost all ROMs that I use on MS2)
300 - 30, 600 - 45, 900 - 57, 1200 - 65
I do know that the vsel values are high and there are lower vsel overclock values out there but with these values I noticed that the CPU uses the 900 frequency more often than it does in lower vsel values settings.
I use these values from the bootmenu -> CPU settings
Load all modules -> Enabled
Status -> Enabled
Exit with save once you make changes to cpu values in the bootmenu.

haha ok thanks but i noticed that my phone heats up very quickly whenever i am using 3g any solutions or reasons behind this??

worldwork said:
haha ok thanks but i noticed that my phone heats up very quickly whenever i am using 3g any solutions or reasons behind this??
Click to expand...
Click to collapse
My phone has ALWAYS done this. Once i left 3g on all night and i could barely touch it in the morning
I think i just got a bad device

worldwork said:
haha ok thanks but i noticed that my phone heats up very quickly whenever i am using 3g any solutions or reasons behind this??
Click to expand...
Click to collapse
scottyn said:
My phone has ALWAYS done this. Once i left 3g on all night and i could barely touch it in the morning
I think i just got a bad device
Click to expand...
Click to collapse
It's a trait of the Milestone 2 to overheat a lot. In the stock battery cover for the Milestone 2, there is a 2-inch square amount of thermal paste under a plastic film. I believe this is to dissipate heat away from the battery, because of the overheating nature of the Milestone 2s. Furthmore from my own experience, when I use 3G or HSDPA my device overheats a lot as well. But, as turning cellular data boosts my battery by over 200% (I don't exaggerate - I have measured this) I keep it off unless I am out of range of a wifi network, where I have a small on/off widget to toggle it..

sahilarora911 said:
I use the following values for over clock on CM10 (well on almost all ROMs that I use on MS2)
300 - 30, 600 - 45, 900 - 57, 1200 - 65
I do know that the vsel values are high and there are lower vsel overclock values out there but with these values I noticed that the CPU uses the 900 frequency more often than it does in lower vsel values settings.
I use these values from the bootmenu -> CPU settings
Load all modules -> Enabled
Status -> Enabled
Exit with save once you make changes to cpu values in the bootmenu.
Click to expand...
Click to collapse
just asking how is ur battery life with this settings?

worldwork said:
just asking how is ur battery life with this settings?
Click to expand...
Click to collapse
Well I would say it is not too different from the other lower vsel values I have tried. The thing that I noticed is that with these settings, the phone tends to stay a lot even in 900 MHz zone which it does not do if vsel are low.
If vsel are too low, then the phone mostly stays in 1200 (when in use) n 300 (when idle). U can try n see for urself. This is just what I personally feel.