Database Users

[Q] setCPU settings

WM Rom: chuckydroid
radio: 2.12.50
Android Build: hyperdroid 1.1
does anyone know why, when i boot i dont get "setCPU has been granted superuser permissions". I have to load setCPU manually then it says it. And my settings dont get saved, everytime i boot it reverts back to ondemand governor
it works on everything else, "juicedefender has been granted superuser permissions" and autokiller gets it aswell. just not setCPU.
have checked autostarts app and "setCPU (Startup)" is listed there.

longobongo said:
WM Rom: chuckydroid
radio: 2.12.50
Android Build: hyperdroid 1.1
does anyone know why, when i boot i dont get "setCPU has been granted superuser permissions". I have to load setCPU manually then it says it. And my settings dont get saved, everytime i boot it reverts back to ondemand governor
it works on everything else, "juicedefender has been granted superuser permissions" and autokiller gets it aswell. just not setCPU.
have checked autostarts app and "setCPU (Startup)" is listed there.
Click to expand...
Click to collapse
nobody else with this problem? or a solution?

Have you checked set on boot on the main page of the app?
Sent from my HD2 running Darkstone Android

Yes everything is set.
Sent from my HTC HD2 using XDA App

[Q] "Process System is Not Responding"

I just installed the latest version of Apex, did a few customizations, then rebooted because I changed the LCD Density. Now, whenever I boot, it says "Process System is not responding". I can force close it, wait, or access the power menu. But, the screen is black, and I can't do anything. This is after a day full of reflashing and wiping because the damn device couldn't receive text messages.

xzillerationer said:
I just installed the latest version of Apex, did a few customizations, then rebooted because I changed the LCD Density. Now, whenever I boot, it says "Process System is not responding". I can force close it, wait, or access the power menu. But, the screen is black, and I can't do anything. This is after a day full of reflashing and wiping because the damn device couldn't receive text messages.
Click to expand...
Click to collapse
If you have a backup try restoring
Sent from my DROID2

How? I'm trying to follow the guides, but whereever I go, the SBF zip is corrupted.

It appears to be working now. I think I'll hold off tinkering with it for a little while. I still would like to know why it did this, though. For now, I'll just restore my apps, but only the ones I use all the time,

xzillerationer said:
It appears to be working now. I think I'll hold off tinkering with it for a little while. I still would like to know why it did this, though. For now, I'll just restore my apps, but only the ones I use all the time,
Click to expand...
Click to collapse
Did you happen to delete any system apps when you were customizing? You might have deleted an app that settings was dependent on by accident, which could cause something like that.
ALWAYS do a nandroid backup before you start tinkering with the phone, it will save a lot of trouble.
Heres how to do it:
1. Boot into clockworkmod recovery using Koush's Bootstrap Recovery
2. Select Mounts and Storage, and mount /system and /data
3. Return to the main menu and select Backup and Restore
4. Select backup and let it work.
5. When its done, return to main menu, and choose to reboot.
Now you can tinker however you want. If you happen to mess something up, return to clockworkmod recovery (hint: if you can't get the phone to boot properly, boot the phone, and pull the battery when you see the M logo. Replace the battery and it should take you to clockworkmod)
1. Boot into recovery
2. Mount your /system and /data again
3. Go back and select Backup and Restore
4. Select restore, and select you restore file (should be the only one if you've only done 1 backup)
5. Let it work, then reboot the phone, and your phone will be in the exact same state as it was when you did the backup.
If you can't get into clockwork, you'll need to SBF.
SBF guide:
http://forum.xda-developers.com/showthread.php?t=770224
SBF Download (download in guide doesn't work):
hxxp://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html (replace xx with tt)
Hope this helps!

Thanks, that'll really come in useful. The reason I couldn't fix it before is because Moto sucks, and encrypted the bootloader, so I was having a problem getting back into Clockwork. Did I say thanks? Oh well. Thanks.
Sent from my DROID2 using XDA Premium App

Yeah moto does suck for that. They are giving options on future devices to lock and unlock the bootloader though (like the xoom) so at least they are making progress. Doesn't help us though...

xzillerationer said:
I just installed the latest version of Apex, did a few customizations, then rebooted because I changed the LCD Density. Now, whenever I boot, it says "Process System is not responding". [... ]
Click to expand...
Click to collapse
Are you using Droid 2 Overclock? I'm asking because it allows setting screen density. I found that the new startup scripts added to Apex 1.4.1 don't play well with OC settings that were fine on Apex 1.3. The scripts add sysctl and CPU tweaks.
I set my OC settings to more conservative settings, and it has been far more stable. This isn't a knock against either product. Both work fine together with a bit of work.
Fab did release a test release (1.4.2 seems to be the informal name) that doesn't launch his new startup scripts automatically, and that's what I'm currently running.
- Bob

bobstro said:
Are you using Droid 2 Overclock? I'm asking because it allows setting screen density. I found that the new startup scripts added to Apex 1.4.1 don't play well with OC settings that were fine on Apex 1.3. The scripts add sysctl and CPU tweaks.
I set my OC settings to more conservative settings, and it has been far more stable. This isn't a knock against either product. Both work fine together with a bit of work.
Fab did release a test release (1.4.2 seems to be the informal name) that doesn't launch his new startup scripts automatically, and that's what I'm currently running.
- Bob
Click to expand...
Click to collapse
Aye, I am. It seems fine most of the time for me. However, I've only been running for a few days, and have barely rebooted.
Sent from my DROID2 using XDA Premium App

I am had luck with 1.4.2 by setting my OC values to defaults before doing my pre-flash backup with Titanium Backup. After flashing, I was able to restore everything, including OC (default) values.
I also disabled the CPU tweaks Apex puts in /etc/init.d scripts, and and re-run QuickClock Advanced to recalculate my clock and voltage settings and imported those into Droid 2 Overclock.
So far (5 hours), it's been solid. If you don't want these issues, stick to Apex 1.4.0 for now. It was very stable.
- Bob

A few questions

what's the consensus about stability, supprot development and battery life? It seems like CM7 offers the most battery life, CM10 is still unstable and CM9 has hardware acceleration but battery drain. I am on CM9 and wondering whether I should move forward to CM10 or just keep waiting for Qarx to release better releases?
Also is there a way, on my phone, to be notified of build releases?
What is the difference (I have a Bravo) between Kobe and Qarx builds? I have been using Kobe can I just flash to Qarx?
Also if I'm upgrading from CM9 to CM10 is there a way to keep my settings, files, homscreen icons and simply flash to CM10?
I am on the KOBE build, and wanted to know will I have things like HWA with the generic CM9 build...is there any advantage of the generic CM9 builds? Also will I be able to go to settings->:system updates and update using CM9's update service?
My battery life stinks on CM9!

zetsui said:
what's the consensus about stability, supprot development and battery life? It seems like CM7 offers the most battery life, CM10 is still unstable and CM9 has hardware acceleration but battery drain. I am on CM9 and wondering whether I should move forward to CM10 or just keep waiting for Qarx to release better releases?
Also is there a way, on my phone, to be notified of build releases?
What is the difference (I have a Bravo) between Kobe and Qarx builds? I have been using Kobe can I just flash to Qarx?
Also if I'm upgrading from CM9 to CM10 is there a way to keep my settings, files, homscreen icons and simply flash to CM10?
I am on the KOBE build, and wanted to know will I have things like HWA with the generic CM9 build...is there any advantage of the generic CM9 builds? Also will I be able to go to settings->:system updates and update using CM9's update service?
My battery life stinks on CM9!
Click to expand...
Click to collapse
Cm9 was alredy left in the past, there will be no more changes to fix battery drain, you should move alredy to cm10, the problem is present but it still has support from devs.
In the lastest build from quarx for bravo, bravo rom updater is working, but the app says defy rom updater and you just need to change some things inside config to make it work

josuearisty said:
Cm9 was alredy left in the past, there will be no more changes to fix battery drain, you should move alredy to cm10, the problem is present but it still has support from devs.
In the lastest build from quarx for bravo, bravo rom updater is working, but the app says defy rom updater and you just need to change some things inside config to make it work
Click to expand...
Click to collapse
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Also no way to set the number of homescreens on cm10? Any other big changes they are looking forward to? That already seemed to slow down my bravo more than cm9.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too

zetsui said:
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Also no way to set the number of homescreens on cm10? Any other big changes they are looking forward to? That already seemed to slow down my bravo more than cm9.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
Click to expand...
Click to collapse
The easiest way to check for updates is to check up on the forums where updates/changelogs are being posted.
For homescreens in cm10, I don't use trebuchet. Alternatively, apex launcher and nova allow you to change the number of homescreens.
Personally, I wipe cache/dalvik and wipe data each time I flash roms. It just seems safer that way, even though it's a pain to restore. Can you explain the app id problem you're talking about?
Governors are found in the development section of bravo forums, posted by skeevy420.

Dr. Orange said:
The easiest way to check for updates is to check up on the forums where updates/changelogs are being posted.
For homescreens in cm10, I don't use trebuchet. Alternatively, apex launcher and nova allow you to change the number of homescreens.
Personally, I wipe cache/dalvik and wipe data each time I flash roms. It just seems safer that way, even though it's a pain to restore. Can you explain the app id problem you're talking about?
Governors are found in the development section of bravo forums, posted by skeevy420.
Click to expand...
Click to collapse
So I remember from stock->cm9 when I tried to restore my apps via titanium backup (and maybe in retrospect I erred when I tried to restore google store) there was some difference in the google store id off my old phone and my new phone's google store account on cm9...the difference in the store ids between my old apps and my new apps wouldn't allow me to authenticate all my applications. That and a lot of apps failed on startup because of it. Basically I dont think there is an easy way around reinstalling everything between cm9 and cm10

zetsui said:
So I remember from stock->cm9 when I tried to restore my apps via titanium backup (and maybe in retrospect I erred when I tried to restore google store) there was some difference in the google store id off my old phone and my new phone's google store account on cm9...the difference in the store ids between my old apps and my new apps wouldn't allow me to authenticate all my applications. That and a lot of apps failed on startup because of it. Basically I dont think there is an easy way around reinstalling everything between cm9 and cm10
Click to expand...
Click to collapse
Hmmm. The only issue I've had is trying to restore system apps/data between android 2.3.x and 4.0.x/4.1.x. Never had problems with restoring various other apps. That being said, you shouldn't have an issue restoring any apps from ics to jb.
Don't restore the google play store. That's a system app and I think that's why you've had problems. Just flash gapps when you flash roms. You can then do batch restore in titanium and it will restore your missing apps/data. I think that should fix the problems you've been having.

zetsui said:
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
Click to expand...
Click to collapse
Always factory reset when switching the rom base; eg. CM7 to CM9 or CM10. The reason is that the apps use the same filenames for sqlite databases, which don't have the same values from CM7\Miui\9\10\stock\MS2. That's where all the bugs come from when you don't wipe data\factory reset.
Google "fixed" Play to make it like that. If I remember correctly, there's an option in TB Pro that allows you to change the market id to your current rom's id. Under Batch\Market, if memory serves me well.
SmartassV2 is in the DX Gov pack. A trick is to just push it to /system/lib/modules/cpufreq_smartass.ko and overwrite the default smartass module with V2, since they use the same values to be tweaked you'll be able to configure V2 this way. This trick doesn't work with boostedass to overwrite boosted; only smartassV2 over smartass works.
Smartass sucks and is bugged by not using the 2nd vsel profile. Use SmartassV2 or Boosted. Oddly enough, I've found that if I use boosted\smartassV2 in combination with the vsel settings of [email protected]\[email protected]\[email protected] I get better battery life than when using [email protected]\[email protected]\[email protected] since 700mhz can handle more crap than 600 and doesn't need to jump up to vsel3 for greater processing power. Hell, I get 24 hrs easily like that and I use a Live Wallpaper (Galaxy Pack, its awesome so go buy it; Have Planet Pack from the same dev and its awesome as well).
You can speed up the startup by disabling the boot animation, removing unused system apps, using V6 properly, using F The Logs mod. Set the Governor to Ondemand\Performance\UserSpace (performance\userspace force it to use vsel3 exclusively) in the bootmenu for booting up and use something like NoFrills\CM Performance Menu\SetCpu to change to boosted\smartassV2 once you're fully booted and in the system. Another good tweak is to modify the sio scheduler scripts. I've done plenty of posts on how I mod bootmenu scripts to fix sio and to make it work better. The sio fix will give you much faster read times for the system memory (twice as fast for some apps, literally twice).
You can use the /system/bootmenu/scripts/overclock.sh and /system/bootmenu/config/overclock.conf from my latest CM7 Kang to apply the sio tweak. Just replace them before you flash the rom or adb push with 0777 permissions.

skeevy420 said:
Always factory reset when switching the rom base; eg. CM7 to CM9 or CM10. The reason is that the apps use the same filenames for sqlite databases, which don't have the same values from CM7\Miui\9\10\stock\MS2. That's where all the bugs come from when you don't wipe data\factory reset.
Google "fixed" Play to make it like that. If I remember correctly, there's an option in TB Pro that allows you to change the market id to your current rom's id. Under Batch\Market, if memory serves me well.
SmartassV2 is in the DX Gov pack. A trick is to just push it to /system/lib/modules/cpufreq_smartass.ko and overwrite the default smartass module with V2, since they use the same values to be tweaked you'll be able to configure V2 this way. This trick doesn't work with boostedass to overwrite boosted; only smartassV2 over smartass works.
Smartass sucks and is bugged by not using the 2nd vsel profile. Use SmartassV2 or Boosted. Oddly enough, I've found that if I use boosted\smartassV2 in combination with the vsel settings of [email protected]\[email protected]\[email protected] I get better battery life than when using [email protected]\[email protected]\[email protected] since 700mhz can handle more crap than 600 and doesn't need to jump up to vsel3 for greater processing power. Hell, I get 24 hrs easily like that and I use a Live Wallpaper (Galaxy Pack, its awesome so go buy it; Have Planet Pack from the same dev and its awesome as well).
You can speed up the startup by disabling the boot animation, removing unused system apps, using V6 properly, using F The Logs mod. Set the Governor to Ondemand\Performance\UserSpace (performance\userspace force it to use vsel3 exclusively) in the bootmenu for booting up and use something like NoFrills\CM Performance Menu\SetCpu to change to boosted\smartassV2 once you're fully booted and in the system. Another good tweak is to modify the sio scheduler scripts. I've done plenty of posts on how I mod bootmenu scripts to fix sio and to make it work better. The sio fix will give you much faster read times for the system memory (twice as fast for some apps, literally twice).
You can use the /system/bootmenu/scripts/overclock.sh and /system/bootmenu/config/overclock.conf from my latest CM7 Kang to apply the sio tweak. Just replace them before you flash the rom or adb push with 0777 permissions.
Click to expand...
Click to collapse
WOW That is amazing! Do you think that range between VSEL 2 and VSEL 3 with smartass is going to be consistent across different devices?

zetsui said:
WOW That is amazing! Do you think that range between VSEL 2 and VSEL 3 with smartass is going to be consistent across different devices?
Click to expand...
Click to collapse
Most devices have 4+ vsel slots. Moto phones are screwed by the bootloader\limited Moto Kernel features.
It should be. The thing with the bravo (when tweaking governors) is trying to find the magic values that use vsel2 more than vsel3 and still provide a smooth ui. The reason that a 700mhz vsel2 works good is that the Bravo comes with a stock vsel3 of 800mhz. CM7\9 work\use resources much better than our stock Froyo making that 700mhz perform like 800mhz on a stock rom.

[Q] Problem with FauxClock

Hello,
I have a problem with the Fauxclock app on my Nexus 4.
ROM is CM10.1 official nightly with faux kernel 002b5.
Everytime I reboot the phone all my settings are gone. The governor is set to ondemand and max clock speed.
I selected intellidemand and some other modifications. The "set on boot" tabs are all set inside the app.
It also takes a long time to start the app. It is recquiring root and always setting the proper permissions.
Can anybody help me solving this problem?
Thanks in advance.

Sorry I can't help with your settings not sticking. Maybe ask in his thread. One thing that I have seen mentioned in his thread is that he recommends using the supersu app as opposed to the superuser app that I believe is included in cm10.1. The app may not be getting proper root permissions.
The slow startup with setting permissions and such is normal from my experience.

http://forum.xda-developers.com/showthread.php?t=2008222

Uninstalled and reinstalled xposed to be able to login to snapchat, broken ex kernel

Ok well, I had xposed framework installed on my 6P. I also have ElementalX kernel installed. To login to snapchat I had to uninstall xposed, login to snapchat and then re-install xposed. After doing this the EX Kernel Manager app would not let me change a lot of settings. Cluster 2 governor would also be N/A and I couldn't change the Max CPU freq for both clusters. Also I couldn't disable/enable hexacore mode. Any help would be greatly appreciated.
Thanks.

Um, What exactly are you asking for help for?

HesThatGuy said:
Um, What exactly are you asking for help for?
Click to expand...
Click to collapse
Oh how I can fix the problem, it's stopping me from changing settings. Also something more to add, it'll automatically changed the Max CPU frequency, also it freely allows me change the min freq but not max.

The problems you have described relating to ElementalX & EX kernel manager aren't because of Xposed.
Regarding cluster 2(big cores) you weren't allowed to change the settings for those because of thermal throttling. So make sure your is phone is cool when trying to change the settings for the cores.
Side note: Also make sure that you touch the icon next to the setting so that it turns blue and will apply the setting on boot.

HesThatGuy said:
The problems you have described relating to ElementalX & EX kernel manager aren't because of Xposed.
Regarding cluster 2(big cores) you weren't allowed to change the settings for those because of thermal throttling. So make sure your is phone is cool when trying to change the settings for the cores.
Side note: Also make sure that you touch the icon next to the setting so that it turns blue and will apply the setting on boot.
Click to expand...
Click to collapse
I'm pretty sure it's not because of thermal throtlling, because I'm only at around 40C. It seems a little suspect that just after I uninstalled and re-installed xposed that it stopped functioning as it did before I did that.

Well, with a case like yours I would advise 2 things.
1.) Try to cool the phone down, change the settings, and see if they stick.
2.) Reflash the rom, login to your apps, then install xposed.
You could also try to clear all data from the ex kernel manager app, restart the phone and then try to apply your settings.

Should I restore to backup that I have? It's after I install xposed but before I root and install elementalx.
Sent from my Nexus 6P using XDA-Developers mobile app

You can try that, but I would suggest that you start completely over and clean flash.

Ok so, I flashed stock again, installed xposed, rooted and then installed elementalx, it is still being "buggy". Doesn't let me really set the max freq. Automatically changes it all of the time on both clusters too.
Sent from my Nexus 6P using XDA-Developers mobile app

Hmm, I don't understand how you could have this problem going on considering that I'm running xposed and elementalx on my phone and my settings stick. Is it possible that you aren't touching the icon so that it applies the settings on boot?

What do you mean?
Sent from my Nexus 6P using XDA-Developers mobile app