Related
Just rooted my Defy with Superoneclick and downloaded Setvsel. My problem is that the oc-program won't start. The screen just goes black and after i while i have to force it to shutdown. Anyone knows why it does this?
Do you have 2nd Init instaled? If so, there's an option to enable oc and after that setvsel will work. Another option is install Droidoverclock(if a remember well), and enable oc, then setvsel works too.
No i dont have "2nd Init" installed, didn't know that it was required to run Setvsel.
It's not a pre requisite, but it enable oc feature in android. Install Milestone Overclock from market. Milestone OC will enable the same feature, and after that setvsel will work.
insomaniac.droid said:
It's not a pre requisite, but it enable oc feature in android. Install Milestone Overclock from market. Milestone OC will enable the same feature, and after that setvsel will work.
Click to expand...
Click to collapse
I've just installed Milestone Overclock and when i start it comes to a screen where i have two options: "Load module" and "Refresh". Under these options is a slider that says "Selected frequency: 550MHz 56 vsel (Default)". And under the slider is an box greyed out due to the fact that i don't have my sd-card installed (took it out when i rooted the phone). Sadly none of the options, "Load module" and "Refresh" that is, seems to work. What am i doing wrong? I thought it was as simple as rooting the phone and then play around with Setvsel.
Izak80 said:
I've just installed Milestone Overclock and when i start it comes to a screen where i have two options: "Load module" and "Refresh". Under these options is a slider that says "Selected frequency: 550MHz 56 vsel (Default)". And under the slider is an box greyed out due to the fact that i don't have my sd-card installed (took it out when i rooted the phone). Sadly none of the options, "Load module" and "Refresh" that is, seems to work. What am i doing wrong? I thought it was as simple as rooting the phone and then play around with Setvsel, sadly not.
Click to expand...
Click to collapse
Which version of android you're running?
I'm running leaked 2.3.3-112, with enabled oc in 2nd init.
When Milestone OC starts on my phone, the first button is "Unload module", because the oc is already enabled, and in your case, you have to click on "Load Module", but if is not working, i don't know why. This module is used for setvsel.
I'm running Android 2.2 (Froyo). But during all this time i have had the usb-cable connected to my computer and USB debugging enabled, But that shouldn't matter should it?
install milestone overclock...click on load module..dont care wat it does or wat it doesnt..now open setvsel..it should be working by now..
if it is still not working then uninstall and then reinstall milestone overclock after a reboot
hope it helps
So this is excatly what i did yesterday, i describe it thoroughly so someone with more knowledge maybe can spot what i did wrong.
1. Downloaded The newest version of Superoneclick
2. Downloaded the newest drivers for my Defy from the Motorola website, named "Download Motorola 5.0 Driver with MotoHelper", and installed them.
3. Dismounted the sd-card
4. Turned on USB-debugging in the settings-menu.
5. Connected my Defy to my computer and rooted it (since i'm not on Vista or Win7 i just doubleclicked on the program and pushed the root button). Everything worked fine so far and the "superuser" icon apperad shorlty after.
6. Now i downloaded Setvsel and tried to start it up. I was treated to a black screen but i kept on waiting for something to happen. After about 30s i got a message that the program can't launch and internetaddress.
7. After the advice that i should download "2nd Ini" i did so but that program wouldn't launch either. Then i tried with Milestone Overclock but only got to the screen where the "load module" option is and after having pushed that button the program just hangs and i have to push tha backbutton repeatedly to force the program to shutdown.
So i don't understand what's wrong i thought it was as simple as rooting my phone and then install Setvsel and play around with it? Never heard that Setvsel requires 2nd Init or Milestone to work.
yup.it will hang...let it hang...did u see whether setvsel was working after tat?it should work
arpith.fbi said:
yup.it will hang...let it hang...did u see whether setvsel was working after tat?it should work
Click to expand...
Click to collapse
No, i uninstalled it after Milestone OC just hang. I reckoned i must get into Milestone first to make SetVsel work. Don't understand why SetVsel won't work after i rooted it and why i must install another program to make it start. No one mentioned this to me, all i heard was "root your phone, install SetVsel and give it a go".
same thing used to happened to me too..milestone OC used to hang when load module was pressed...but after tat setvsel used to work...
do this..uninstall both and reinstall both..dont run setvsel...first run milestone OC..and click on load module..now open setvsel...this should work..it always works..
arpith.fbi said:
same thing used to happened to me too..milestone OC used to hang when load module was pressed...but after tat setvsel used to work...
do this..uninstall both and reinstall both..dont run setvsel...first run milestone OC..and click on load module..now open setvsel...this should work..it always works..
Click to expand...
Click to collapse
Ok. I'm just so fed up with the whole business right now, but i'll try later this evening maybe. I just want to understand why SetVsel won't start the easy way (without involving Milestone). For alot of people it does, maybe i'm doing something wrong that will brick my phone somehow?
nope this wont brick ur phone.even i was fed up of this setvsel problem in the beginning..i rerooted 5 times to make it work...atlast i thought to use milestone oc instead of setvsel..but later i noticed tat setvsel was working...after few hrs i installed new rom..followed same process..and it was working..make sure u have latest version of setvsel...
arpith.fbi said:
nope this wont brick ur phone.even i was fed up of this setvsel problem in the beginning..i rerooted 5 times to make it work...atlast i thought to use milestone oc instead of setvsel..but later i noticed tat setvsel was working...after few hrs i installed new rom..followed same process..and it was working..make sure u have latest version of setvsel...
Click to expand...
Click to collapse
But didn't Milestone OC hang for you aswell? So what you suggest is. Install Milestone and SetVSel. Start Milestone and push "load module" and then when it hangs, what should i do? Force it to shutdown by pushing the back-button and then try to start SetVsel?
it shouldnt hang...and even if it hangs then close it and open setvsel...see if its working or not...hope for the best
arpith.fbi said:
it shouldnt hang...and even if it hangs then close it and open setvsel...see if its working or not...hope for the best
Click to expand...
Click to collapse
Yeah will do so. It's just frustrating that SetVsel won't work from the beginning the way i've read it does for alot of people. Maybe there's a OC-program that works right from the start on my phone. Will post on other forums an see what they have to say about it. I'm a curious person and it's in my nature to want to understand the reasons when i encounter a problem rather than go around it without understanding what i'm doing. I've overclocked alot ot computers and now my way around a BIOS, but on my phone i can't even get in at the moment
After install setvsel, run it. Superuser permission will pop out, then allow it. After you allow it, it should run ok. If nothing pop out, setvsel cannot run and will hang. Try reset factory first then re install
Sent from my MB525 using XDA App
salingpusa said:
After install setvsel, run it. Superuser permission will pop out, then allow it. After you allow it, it should run ok. If nothing pop out, setvsel cannot run and will hang. Try reset factory first then re install
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
No "superuser permission box" popped up when i first started SetVsel. Strange since i can see the superuser icon clearly among the apps meaning that i rooted it correctly. Am thinking of trying to install CM7 instead. Have read how to do it and sadly it seems as a rather lenthy process. I fear that since the simple process of rooting and running SetVsel didn't work ,installing CM7 will be impossible
Going to cm7 will be a good choice. Read cm7 faq before proceeding
Still haven't figure out how to build a kernel from source for the Continuum, but I can still hack the stock kernel to add some functionality to it. Since this stock, you can't expect to much, but I did what I could. I made a few memory management changes to try and get the phone to run a little better. Added a root script that will auto-root the phone on boot, you'll still need the Superuser app if you don't already have it (find it in the market). Also added init.d support for those that have busybox and cleaned up the ramdisk and such a lot. Also, this should enable custom boot animations. Put a bootanimation.zip file in /system/media/ or /data/local/ and it should display when your phone boots up. I had one person test it, and they say it works for them, so I'm hoping it works for everyone else here. Download and flash in CWM.
Download - Custom boot animations and memory management settings
Download - Custom boot animations and stock memory management settings
Download - Stock boot animations and custom memory management settings
Download - Stock boot animations and memory management settings
Sweet. Thank you
Sent from my SCH-I400 using Tapatalk
Just installed. Flawless, so far
Sent from my SCH-I400 using Tapatalk
ChainsDD updated Superuser and the su binary tonight (of course) so I updated it in the kernel. No need to re-download unless you really want to, you can update the su binary via the Superuser app. Download link remains the same, so anyone that hasn't yet downloaded will get the updated version.
So youre saying you have source but dont know how to do it?
sent from my XDA phone - its more than a continuum
nodixe said:
So youre saying you have source but dont know how to do it?
sent from my XDA phone - its more than a continuum
Click to expand...
Click to collapse
The source that "we" have is from the Fascinate/Mesmerize. It has the stuff in there for the Continuum, but the times I have tried to build off of it, the resulting kernel doesn't boot. Not sure if what is there is just incomplete, or if the config is off. Feel free to try and get it working. Use the garnett_03_defconfig (or similar) as the base.
imnuts said:
ChainsDD updated Superuser and the su binary tonight (of course) so I updated it in the kernel. No need to re-download unless you really want to, you can update the su binary via the Superuser app. Download link remains the same, so anyone that hasn't yet downloaded will get the updated version.
Click to expand...
Click to collapse
Since i already had root, bb 1.84 and su installed, i should be good. I'll run su and update the binaries to be safe, though. Thanks for the heads up
Sent from my SCH-I400 using Tapatalk
Uh is there a reason my phone hangs at the Samsung logo after installing this?
EDIT: ...Forget I said that...
yea it will probably take a minute for the first boot since ite rewriting most of the system but after the first one u should be good.
imnuts thank u so much for this u have no idea how bad ive been wanting to get rid of the verizon boot lol
imnuts! thanks allot! You rock! testing now.
Animation works! so far all running good! gonna get some scripts in and let it run!
After installing my phone seems to stall a little on some apps. Like I was listening to music using UberMusic and it would skip kind of like an old CD player. And while I was listening to music I tried to open the XDA app and my phone completely froze. I couldn't open the task manager or anything. Had to pull the battery. With every reboot it seems to get worse
Try setting your cpu min above 400
Sent from my SCH-I400 using XDA App
I had my first ever auto-reboot on the Continuum just a few minutes ago. Brought me back to my days of toying with my Hero. And things do seem laggy since the install.
Guess I'll need to install the old kernel back, if'n it's a separate installable download. Can't remember.
Sent from my SCH-I400 using XDA App
If more people start having issues with it lagging or rebooting, I can undo the changes to the memory management and create a second version then. I used the same settings that I had setup on the Charge, and small hardware differences could make the settings not work properly.
Bierce22 said:
Try setting your cpu min above 400
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
I shouldn't have to
imnuts said:
If more people start having issues with it lagging or rebooting, I can undo the changes to the memory management and create a second version then. I used the same settings that I had setup on the Charge, and small hardware differences could make the settings not work properly.
Click to expand...
Click to collapse
That would be nice
imnuts said:
If more people start having issues with it lagging or rebooting, I can undo the changes to the memory management and create a second version then. I used the same settings that I had setup on the Charge, and small hardware differences could make the settings not work properly.
Click to expand...
Click to collapse
Isn't there a fundamental flaw with memory management in the Froyo builds for our Continuums? I have programs running that load from scratch when I switch back to them all the time. There are games on my phone that I lose all my progress if I switch from the game to anything else. I had the Fascinate and pushed it hard and never observed any of these issues, and I was using a Froyo build on there. As I understand it, the Fascinate and Continuum have basically the same hardware.
Granted, I hadn't had any auto-reboots until this last kernel, but I've had memory issues ever since putting any Froyo build on this Continuum.
I've just held out hope that someone will either release a new rom or find out how to make these Froyo builds run as efficiently as the ones for the Fascinate.
Either way, my Continuum is a more enjoyable phone today than it has ever been before!
I've had two auto reboots since I installed the new kernel and it never happened before
Itvhas to be the changes he made last night. My phone is running fine. Not much snapper, but no issues either
Sent from my SCH-I400 using Tapatalk
Here's the link to the old kernel if you want to revert back
http://dl.dropbox.com/u/20459391/ec07.tar
Ok, I've updated the OP with new download links. The original one is the first download, custom boot animations and custom memory management settings. The second download has the custom memory management removed. The third download has the custom memory management, but retains the stock boot animation, and the last download is stock boot animations and stock memory management.
As for why people may have issues with memory on the Continuum and not the Fascinate, which is the same basic hardware. My guess is that it's due to the ticker. The fascinate doesn't need to have softkey images loaded into memory, or any of the ticker functions/images/services/etc. It may not seem like much, but a few added MBs of memory usage could make the difference people are seeing. I did have a few games on my Fascinate, and now my Charge, that would re-load if I went back to the home screen (Angry Birds and Plants v. Zombies). Hopefully the stock memory settings clear up the issues folks have had. I may also be able to add a few items back in as I suspect the major culprit was the low memory killer settings.
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
swindelljd said:
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
Click to expand...
Click to collapse
with any OTA its recommended to do a factory reset. did you do this? its a pain to loss all your data but it might fix your problems.
sorry i didnt have my morning coffee yet.... If you wiped dalvik then that means you have root. your phone is not shutting down. something is killing rosie (the sense launcher.) and that why the white HTC splash screen comes up again. What rom are you runing? i know its the OTA but is it the RUU or one of the devs roms based off RUU??
swindelljd said:
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
Click to expand...
Click to collapse
If you read his entire post you would know he did a factory reset.
My best guess is to go back to stock sense before the last ota (by rooting and flashing or whatever way you wish..sbf or whatever) then download the ota on your computer and try manually updating your phone..if that doesn't work then I don't know
/Droid3
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That worked for me.
synisterwolf said:
... i know its the OTA but is it the RUU or one of the devs roms based off RUU??
Click to expand...
Click to collapse
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Click to expand...
Click to collapse
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
swindelljd said:
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
There's no risk of brick with v6. It just tweaked a couple parts of the kernel.
Sent from my ADR6300 using Tapatalk
swindelljd said:
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
RMarkwald said:
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
Click to expand...
Click to collapse
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
swindelljd said:
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
Click to expand...
Click to collapse
Yes, that's the app.
Download this app as well: Busybox Installer
It'll tell you what version you have (if you have it), then you can select what version you want to install. No need to adjust where it installs, just leave that at the default, just select version 1.18.2, then hit Install.
I read through the script just to get a sense (no pun intended) of what it was doing and then installed Busybox 1.18.2 and applied setting 11 "Hard to kill launcher" from the script. I've done a bunch of browsing to sites that normally caused Sense to get shut down and so far so good.
I initially installed busybox with symlinks and it the script threw a ton of errors so I reinstalled with symlinks to fix that.
Thanks for all the help. For completeness, here is a link to V6 Supercharger so all the links are in this one thread http://forum.xda-developers.com/showthread.php?t=991276 .
One thing I did have to change because I am running Sense and not a stock android launcher is the name of the launcher process itself.
On line 64, I changed this "pidof com.android.launcher" to this "pidof com.htc.launcher"
will the V6 script it just tells the android memory system to not reclaim memory from the launcher app so it stays on no matter what happens. only way to kill it is to go to settings and FC the launcher. also with the script you cant brick the phone because its not ran till after the phone boots. The term brick means : that the phone will not boot at all. you just have a phone that does nothing at all not even turn on. You can soft brick the phone meaning the software will not boot. all you need to do is make a backup before installing the script and you will always have a way back if anything happens.
for me i run the beta V6 script option under -=*512HP*=- which is more of a balanced one with bullet prof launcher and its is wonderful. but each phone is different so just try them out and see what works for you.
synisterwolf said:
... You can soft brick the phone meaning the software will not boot. ...
Click to expand...
Click to collapse
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
Yeah, you kinda need that one there!
Good job getting it replaced using adb and all, good to hear you figured it out!
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
yes that will do it. lol i did that a long time ago when i wanted to edit it my fat finger deleted it. now as good practice i always make a copy of it but add .bak at the end of it so if i do delete it i can just replace it before reboot.
I've been using options 1, 8, and 12 in the V6 Supercharger and my phone has been running great. What options did everyone else choose?
I've finally upgraded my phone to CM7 (Cyanogenmod). I went from Eclair to Froyo to CM7 within one evening.
I did a backup of all my apps and data etc before I upgraded.
All the Apps and Data still seems to be on the phones memory after upgrading so does that just mean I need to reinstall the applications because its essentially a new O/S?
Or would restoring the Titanium backup be the best option?
When I first got into the new CM7 I put in my google account details but chose not to sync until I had wifi back up and running. How do I now get that option back so I can sync and get all my contact details back etc?
Final question, how do I overclock the CM7 install to 1.1ghz for the cpu?
Cheers,
John
To turn on your sync settings go into settings and select accounts & sync. Click your Google account and in next screen check the boxes next to what you want sync'd.
For CPU setting select cyanogen settings and then performance. Click ok to the little warning and there you will be able to change CPU settings carefully!
Sent from my LG-VM670 using XDA App
Hello.
I did the sync thing but it didn't bring any contacts back unfortunately so I think unless part of the backup I did using titanium has got than info off the sdcard before I upgraded to CM7 I may have lost all my contacts?
In the Cyanogen Settings and Performance it doesn't allow me to select a higher cpu speed than 1000mhz? I wanted to take it to around 1100mhz.
I also wasn't sure how to change the cpu core speed in the boot menu?
Are there any good (and free) apps that could do this instead?
Thanks,
John
What phone do you have? The kernel your phone is using may not support overclocking over the stock speed.
Spoke too soon!
Two steps forward and one step back! Story of my life.
Tried doing the titanium back up of all my old apps from Eclair. Big Mistake.
First it didn't show any of these apps but for some reason they then all appeared in titanium.
I think the mistake was restoring the data as well as the actual apps, and I should have been selective.
It put the phone into what I can only describe as a unstable login crash loop where it kept requesting my pin to unlock sim over and over.
Had to wipe it and start again so now I am back on Froyo having flashed back to it. Needed to do this with RSD Lite becase recovery was not possible from the boot menu.
Now to go back to CM7 again and start the process over!
This time I know to just try restore on app at a time without the data to go with it. I will do one app, test, then "may" try the data for that app as well. I don't know for certain that it was the data but that is my best guess. It could have been the app in which case the titanium backup may not be as useful as first though at least going to CM7 because if you can't restore your apps and have to download them all again from market and reinstall on the new CM7 o/s what's th point of it? That's why I suspect its the data?
Will see.
Juanito216 said:
What phone do you have? The kernel your phone is using may not support overclocking over the stock speed.
Click to expand...
Click to collapse
I have the Defy. I am pretty sure it can get to 1.2ghz but at that speed its not stable. I have read replies saying that it is stable at a tiny fraction over 1.1 so I was going to try that speed.
Unfortunately using the cyanogenmod settings it wont allow you to take it higher than 1000mhz in there and An Tu Tu app I tried also doesn't allow it to go higher than 1000mhz, but it should be possible as other people have done it. I'm just not sure how or what app they used to go higher?
Hi guys, recently ive been playing about with roms and i decided to use the aurora play rom for a bit. I had lupusv12 kernel installed at this time with profiles installed. I flashed lupusv12.5 over v12 since they had the same partitions. I also installed auroraplay rom, it came built in with no frills cpu which i didnt like. The reason for that was because it kept inter-fearing with my profiles from setcpu (not letting em work). So i decided to use a file explorer and delete the no frills cpu app built into the rom. After that set cpu's profiles still were not working. So i changed back to stock, still with the lupusv12.5 kernel, and now the profiles (eg opening gta vice city OC to 1.6ghz) still wernt working, and when i went back to setcpu it would take a while to load then crash then i would have to reopen it again for it to work. Profiles still not working, what in the world is going on? The overclocks like moving the slider to 1.6ghz still overclocks but the profiles wont do it, Its annoying to have to keep opening setcpu then open the game, then close the game then open set cpu to return to normal, really annoying, can anyone help?
SetCPU issue.
Mushtaqs said:
Hi guys, recently ive been playing about with roms and i decided to use the aurora play rom for a bit. I had lupusv12 kernel installed at this time with profiles installed. I flashed lupusv12.5 over v12 since they had the same partitions. I also installed auroraplay rom, it came built in with no frills cpu which i didnt like. The reason for that was because it kept inter-fearing with my profiles from setcpu (not letting em work). So i decided to use a file explorer and delete the no frills cpu app built into the rom. After that set cpu's profiles still were not working. So i changed back to stock, still with the lupusv12.5 kernel, and now the profiles (eg opening gta vice city OC to 1.6ghz) still wernt working, and when i went back to setcpu it would take a while to load then crash then i would have to reopen it again for it to work. Profiles still not working, what in the world is going on? The overclocks like moving the slider to 1.6ghz still overclocks but the profiles wont do it, Its annoying to have to keep opening setcpu then open the game, then close the game then open set cpu to return to normal, really annoying, can anyone help?
Click to expand...
Click to collapse
Have you already tried uninstalling the nofrills CPU app?
Deleting it on the system/app folder may affect some code that is causing an issue on your Setcpu app.
Removing the app on the root folder might not be enough to remove all the code link on the rom.
I suggest using titanium backup or any app that can uninstall a system app.
bLoodYHandZ04 said:
Have you already tried uninstalling the nofrills CPU app?
Deleting it on the system/app folder may affect some code that is causing an issue on your Setcpu app.
Removing the app on the root folder might not be enough to remove all the code link on the rom.
I suggest using titanium backup or any app that can uninstall a system app.
Click to expand...
Click to collapse
i should have said somthing sooner but i already fixed the problem, and i tried uninstalling it, and it failed, so thats why i deleted it. I fixed my issue by erasing the system/data then reflashing the stock rom and everything worked again, cheers for trying to help though. :good:
Mushtaqs said:
i should have said somthing sooner but i already fixed the problem, and i tried uninstalling it, and it failed, so thats why i deleted it. I fixed my issue by erasing the system/data then reflashing the stock rom and everything worked again, cheers for trying to help though. :good:
Click to expand...
Click to collapse
what version of setcpu are you using? because i heard issues with versions above ver 3.0.9 are having issues with profiles
xdarkmario said:
what version of setcpu are you using? because i heard issues with versions above ver 3.0.9 are having issues with profiles
Click to expand...
Click to collapse
im using the latest version 3.1.2 , somthing like that i know its higher than 3.0.9
xdarkmario said:
what version of setcpu are you using? because i heard issues with versions above ver 3.0.9 are having issues with profiles
Click to expand...
Click to collapse
im using the latest version 3.1.2 , somthing like that i know its higher than 3.0.9