Hello, I just installed the Paranoid Android 3.60 ROM that I downloaded via this link http://forum.xda-developers.com/showpost.php?p=27465239.
I am using a Sprint Galaxy Nexus.
The problem I am running into is with the "hybrid properties" in the settings. Everything else with the ROM has worked wonderfully, but I believe the Hybrid is the main reason to run this ROM and I cannot access it. Any time i click the Hybrid Properties in settings, I get "Unfortunately, settings has stopped responding." I have reinstalled and wiped factory and dalvik/ caches.
I am at a loss and any help would be appreciated. From the change log it looks like this may have been an old issue and was apparently fixed..
I have searched the forums here as well as Google and all i could come up with was one other person having this problem and it was never resolved.
Anyone else have this or know how to fix it?
Same Issue using 3.65
killkida said:
Hello, I just installed the Paranoid Android 3.60 ROM that I downloaded via this link http://forum.xda-developers.com/showpost.php?p=27465239.
I am using a Sprint Galaxy Nexus.
The problem I am running into is with the "hybrid properties" in the settings. Everything else with the ROM has worked wonderfully, but I believe the Hybrid is the main reason to run this ROM and I cannot access it. Any time i click the Hybrid Properties in settings, I get "Unfortunately, settings has stopped responding." I have reinstalled and wiped factory and dalvik/ caches.
I am at a loss and any help would be appreciated. From the change log it looks like this may have been an old issue and was apparently fixed..
I have searched the forums here as well as Google and all i could come up with was one other person having this problem and it was never resolved.
Anyone else have this or know how to fix it?
Click to expand...
Click to collapse
Having the same issue with a Verizon Galaxy Nexus, just installed PA 3.65 and it's doing the same thing. I'll have to admit to not wiping cache and dalvik cache after updating OS. I've tried reinstalling and wiping, but still no "hybrid properties" without the "Unfortunately, settings has stopped responding." message. Did you wipe caches on first install?
update
netbyter said:
Having the same issue with a Verizon Galaxy Nexus, just installed PA 3.65 and it's doing the same thing. I'll have to admit to not wiping cache and dalvik cache after updating OS. I've tried reinstalling and wiping, but still no "hybrid properties" without the "Unfortunately, settings has stopped responding." message. Did you wipe caches on first install?
Click to expand...
Click to collapse
Noob issue I think. I had installed 3.60 using one thread and 3.65 using another, thinking Paranoid Android is Paranoid Android, probably not wise to mix? Anyway, backed off to the 3.60 version and it is working again.
Related
I'm posting this here because i don't have posting rights in the dev section yet. I installed FXP50 yesterday on my NEO then installed the gapps package. Yet even though the apps appear in Settings-> Application they don't appear on my drawer and so i can't use them. I tried reinstalling the package, wiping data/cache and wiping market data but nothing worked. When i installed CM i was on CM7Xperia edition and not stock though i don't really think this has anything to do with that. Anything else i could try?
I got it fixed. Well i reinstalled the mod twice and the second time i tried setting up a Google account(which failed because of locked Wifi) and then skipping the step. I guess if you skip the step without trying to set up an account it's missing from the app drawer although i didn't try to replicate it.
I need some help!
I tried rebooting and did a hard reset then I wiped the app data and defaults in settings and it still wouldn't work. I've uninstalled and reinstalled twice now. Oddly the music does play if I plug my headphones in and press play on the mic controls and I can use the notifications controls to skip tracks and pause. It plays in the background but when I try to actually open the app it says: "Unfortunately, Poweramp has stopped." and then I have to close it.
I have been on Resurrection Remix 3.0.4/Siyah Kernel 4.1b6 for a while now and Poweramp hasn't given me any trouble until this morning. I'd really like a solution where I wouldn't have to completely wipe my phone if possible.
Thanks!
[Solution]: Uninstall, reboot to CWM, Wipe Cache and Dalvik Cache, Reinstall and Enjoy!
Shiftyshifty said:
I need some help!
I tried rebooting and did a hard reset then I wiped the app data and defaults in settings and it still wouldn't work. I've uninstalled and reinstalled twice now. Oddly the music does play if I plug my headphones in and press play on the mic controls and I can use the notifications controls to skip tracks and pause. It plays in the background but when I try to actually open the app it says: "Unfortunately, Poweramp has stopped." and then I have to close it.
I have been on Resurrection Remix 3.0.4/Siyah Kernel 4.1b6 for a while now and Poweramp hasn't given me any trouble until this morning. I'd really like a solution where I wouldn't have to completely wipe my phone if possible.
Thanks!
Click to expand...
Click to collapse
Do you use lucky patcher?
Swyped from my Galaxy SII
Jokesy said:
Do you use lucky patcher?
Swyped from my Galaxy SII
Click to expand...
Click to collapse
Nope
Shiftyshifty said:
Nope
Click to expand...
Click to collapse
ok.
Try this:
- clear data of PowerAmp
- Uninstall PowerAmp
- reboot to CWM recovery
- wipe cache partition
- wipe dalvik cache
- reboot phone
- reinstall PowerAmp
Swyped from my Galaxy SII
Jokesy said:
ok.
Try this:
- clear data of PowerAmp
- Uninstall PowerAmp
- reboot to CWM recovery
- wipe cache partition
- wipe dalvik cache
- reboot phone
- reinstall PowerAmp
Swyped from my Galaxy SII
Click to expand...
Click to collapse
I just did all of that and now I'm reinstalling.
Update: It worked! Thank you so much! Everything is back to normal
Shiftyshifty said:
I just did all of that and now I'm reinstalling.
Update: It worked! Thank you so much! Everything is back to normal
Click to expand...
Click to collapse
Hi I have the same problem with power amp. I tried the above methods with no avail. I have used lucky patcher in the past for power amp but not anymore. I still have lucky patcher installed for other applications. What could be causing power amp to crash every time I launch it?
PowerAmp Still crashes
Shiftyshifty said:
I just did all of that and now I'm reinstalling.
Update: It worked! Thank you so much! Everything is back to normal
Click to expand...
Click to collapse
Hi, I also have a galaxy sII and I encountered this problem as well (poweramp crashing instantly upon opening). I believe it only started happening after I installed the newest CM 10.1 nightly (20130531). I attempted the solution posted in this thread (first I cleared the app's data, then I uninstalled it (both the app and the unlocker of the purchased version), I then went to CWM recovery and cleared the cache, even formatted the cache partition, and also cleared dalvik cache). I rebooted my phone but the problem remained. I thus uninstalled the program again and went back to CWM and did a complete factory reset, which got rid of all my apps and settings, etc. When i reinstalled poweramp (and most of my other apps).... the problem still was there. I also notice that it seems to be the exact same problem as described in this thread initially since the app will play music fine when I plug my headphones in. But as soon as I click on the app to access it... it crashes. i have posted a video of the problem on youtube, but i'm not allowed to post links yet. however you may access it at /watch?v=DIZGBxej2uU
My best guess is that the problem lies in CM 10.1 20130531 nightly for the SGSII. Any ideas?
caracter2 said:
Hi, I also have a galaxy sII and I encountered this problem as well (poweramp crashing instantly upon opening). I believe it only started happening after I installed the newest CM 10.1 nightly (20130531). I attempted the solution posted in this thread (first I cleared the app's data, then I uninstalled it (both the app and the unlocker of the purchased version), I then went to CWM recovery and cleared the cache, even formatted the cache partition, and also cleared dalvik cache). I rebooted my phone but the problem remained. I thus uninstalled the program again and went back to CWM and did a complete factory reset, which got rid of all my apps and settings, etc. When i reinstalled poweramp (and most of my other apps).... the problem still was there. I also notice that it seems to be the exact same problem as described in this thread initially since the app will play music fine when I plug my headphones in. But as soon as I click on the app to access it... it crashes. i have posted a video of the problem on youtube, but i'm not allowed to post links yet. however you may access it at /watch?v=DIZGBxej2uU
My best guess is that the problem lies in CM 10.1 20130531 nightly for the SGSII. Any ideas?
Click to expand...
Click to collapse
I have the exact same issue after updating to CM 10.1 RC3 for the Galaxy Nexus (toro) on May 30th. I even did a factory reset to no avail.
EDIT: The problem was fixed by updating to CM 10.1 RC4.
I'm having the same issue with cm-10.1-20130530-NIGHTLY-fascinatemtd. PowerAmp worked fine when I was running cm-10.0, but is now crashing on start with 10.1.
I did all of the steps mentioned above. I also cleaned up my sdcard, although since it also crashes without an sdcard installed, I doubt it matters.
Ideas?
Solution
toejam13 said:
I'm having the same issue with cm-10.1-20130530-NIGHTLY-fascinatemtd. PowerAmp worked fine when I was running cm-10.0, but is now crashing on start with 10.1.
I did all of the steps mentioned above. I also cleaned up my sdcard, although since it also crashes without an sdcard installed, I doubt it matters.
Ideas?
Click to expand...
Click to collapse
caracter2 said:
Hi, I also have a galaxy sII and I encountered this problem as well (poweramp crashing instantly upon opening). I believe it only started happening after I installed the newest CM 10.1 nightly (20130531). I attempted the solution posted in this thread (first I cleared the app's data, then I uninstalled it (both the app and the unlocker of the purchased version), I then went to CWM recovery and cleared the cache, even formatted the cache partition, and also cleared dalvik cache). I rebooted my phone but the problem remained. I thus uninstalled the program again and went back to CWM and did a complete factory reset, which got rid of all my apps and settings, etc. When i reinstalled poweramp (and most of my other apps).... the problem still was there. I also notice that it seems to be the exact same problem as described in this thread initially since the app will play music fine when I plug my headphones in. But as soon as I click on the app to access it... it crashes. i have posted a video of the problem on youtube, but i'm not allowed to post links yet. however you may access it at /watch?v=DIZGBxej2uU
My best guess is that the problem lies in CM 10.1 20130531 nightly for the SGSII. Any ideas?
Click to expand...
Click to collapse
You can fix the problem by updating to 10.1 RC4. There was a math calculation bug in RC3 and its nightlies. Look at the cyanogenmod google+ page for more info.
The AOKP build works great except for the constant disappearing keyboard that is about to make me kick puppies. I saw the note to install the wingray google apps to avoid the disappearing keyboard that is synonymous with the recommend gapps to use, but my dumb ass forgot and installed the recommenced apps and I surely do have the constant disappearing keyboard issue. I have flashed the "gapps-jb-20130129-P75xx" zip but still have the issue. Do I have to wipe everything and start over? Does flashing the new gapps zip not overwrite the "gapps-4.2.2-jb-3.4.2013-signed" I originally installed? It seems not to, but wanted confirmation before wiping everything again.
You should wipe everything and start over. IMHO.
Full wipe and used the "gapps-jb-20130129-P75xx". Disappearing keyboard will no longer boil my blood.
For reference, never use the "gapps-4.2.2-jb-3.4.2013-signed".
Glad I stumbled onto this thread. Exactly the problem, keyboard, (well one of them anyway) I am having.
Well for me I can't find anything to fix the disappearing keyboard issue. I tried using the suggestions above. No help. After finding more and more posts in the same subject on different boards it seemed only the Wingray gapps is the one that works properly. Just tried that one and it doesn't seem to fix the issue either. Tried several of the newer nightly ROMs too.
One suggestion was to download the Go keyboard. That didn't help either.
Dang how hard can this be? I have flashed and wiped cache so many times lately. lol
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
DefQoN_BE said:
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
Click to expand...
Click to collapse
Unfortunately that thread content has not helped in my case. I found that thread early on and have tried to follow the directions. So either I'm missing something or not doing something correctly it appears.
Someone in another forum suggested I try the free Jellibean keyboard.
I had this issue too with AOKP 4.2.2. I have not reflashed another new gapps yet, as I found re-installing a third-party keyboard which I liked from previous use solved the problem.
Andre
Well whatever I did I finally fixed it. I ended up simply formatting the internal SD card. Poof, everything gone. Had to restore from backup default ROM. Once the stock firmware was up and running I followed the procedures again. Wiped, cleared cache multiple times and when it was all done installing there is no more keyboard issue as of now.
I loaded the 4/08/2013 nightly ROM and Wingray gapps(which I've already tried multiple times). So all is well in Tablet land again.
First, I apologize for the inevitable incorrect use of terminology - I'm trying my best.
After hours and hours of reading up, I finally attempted to internally install CM10.1 to my Nook Tablet 8GB v 1.4.3. I appreciate all the helpful posts on this forum, and primarily used http://forum.xda-developers.com/showthread.php?t=2037368 and http://forum.xda-developers.com/showthread.php?t=2056626 to go through the steps. I hit a few snags along the way, but in the end I think I was successful.
Now I get an error message every time I boot: "Unfortunately, the process android.process.media has stopped." I click okay, then everything seems to work fine. I have tried some suggestions from here, including clearing caches and stopping google's automatic syncs, but nothing has fixed the problem. As far as I can tell, everything works okay otherwise.
Any ideas on how to fix this message? Could it mean that I did not successfully complete the installation process? (Are there ways to tell if the installation was not successful other than not having a brick?)
Android Version 4.2.2
CyanogenMod Version 10.1-20130421-NIGHTLY-acclaim
Happy to provide any more details that would be helpful. And many thanks in advance.
eyeshaveit said:
Now I get an error message every time I boot: "Unfortunately, the process android.process.media has stopped." I click okay, then everything seems to work fine. I have tried some suggestions from here, including clearing caches and stopping google's automatic syncs, but nothing has fixed the problem. As far as I can tell, everything works okay otherwise.
Any ideas on how to fix this message? Could it mean that I did not successfully complete the installation process? (Are there ways to tell if the installation was not successful other than not having a brick?)
Click to expand...
Click to collapse
This happened to me after I dirty-flashed CM 10.1 over another CM 10-based rom. Let me see if I can remember what I did to make it go away... I think it has something to do with a file or process that Android uses to index/keep track of media files on internal and external sd cards, and deleting or wiping the cache or data on that particular process fixes things. I will do some checking around and post back here if I (re)find more specific info.
EDIT: Found it, I think... Do a force stop, clear data, and clear cache on the "Media Storage" app, then reboot and see if it goes away.
Sooo... did it work?
johnseeking said:
Sooo... did it work?
Click to expand...
Click to collapse
Sorry...long week.
Unfortunately, it didn't work. I had also seen suggestions on the forum of similarly stopping and clearing Google Account Manager, Google Services Framework, and a few others (can remember them all), but those didn't do it either.
I have now also had an error message about Themes not responding - can't remember the exact wording. It's happened 2 or 3 times, doesn't seem to have any other consequences other than requiring me to acknowledge the error.
Could I have strayed somewhere along the installation pathway and inadvertently made this a dirty install?
eyeshaveit said:
Sorry...long week.
Unfortunately, it didn't work. I had also seen suggestions on the forum of similarly stopping and clearing Google Account Manager, Google Services Framework, and a few others (can remember them all), but those didn't do it either.
I have now also had an error message about Themes not responding - can't remember the exact wording. It's happened 2 or 3 times, doesn't seem to have any other consequences other than requiring me to acknowledge the error.
Could I have strayed somewhere along the installation pathway and inadvertently made this a dirty install?
Click to expand...
Click to collapse
You need to load into recovery and do a factory reset/wipe data, clear cache, clear dalvik cache. If you dirty installed (installed over another ROM that's not in the same version) you'll have problems with the ROM. If you're using an older cm7 or cm9 I'll suggest you update to cm10+ succulent.
datallboy said:
You need to load into recovery and do a factory reset/wipe data, clear cache, clear dalvik cache. If you dirty installed (installed over another ROM that's not in the same version) you'll have problems with the ROM. If you're using an older cm7 or cm9 I'll suggest you update to cm10+ succulent.
Click to expand...
Click to collapse
I tried to go back to the beginning to see what I did wrong - hoping to fix the problem but also trying to learn. I'll explain in a bit of detail...
Tried to follow the process outline here: http://forum.xda-developers.com/showthread.php?t=2037368. I was able to access root using NT16or8gbV47SDimagefile.img, but was unable to get any further as it kept saying "No files found" when trying to flash rom and gapps zipped files. After trying multiple reformats, partitions, etc, I abandoned following this process. (Of note, I did make sure that debugging and allowing installation from unknown sources were active - to no avail.)
I then followed this process: http://forum.xda-developers.com/showthread.php?t=2056626. In addition to Step 6 - "Wipe data and factory reset," I also cleared cache and dalvik cache as suggested. Everything else went very smoothly. I've now been running CM 10.1 for a few hours without any error messages. I'll report back anything that pops up over the next few days.
I tried to improvise a bit and flash CWM recovery internally as described here: http://forum.xda-developers.com/showthread.php?t=1640958. I was never succesful using flash_CM9-10_CWM_6.0.2.5_8-16gb_emmc.zip, though I'm not sure it's really necessary. (In trying to do this, I modified step 2.b from Digixmax's guide - rather than using the recovery image from CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, I tried using the flashable emmc.zip noted prior. In the end, I just followed Digimax's steps without modifications.) What do you think? Is there any reason to continue trying to flash CWM internally?
Thanks a million to all.
eyeshaveit said:
...
I tried to improvise a bit and flash CWM recovery internally as described here: http://forum.xda-developers.com/showthread.php?t=1640958. I was never succesful using flash_CM9-10_CWM_6.0.2.5_8-16gb_emmc.zip, though I'm not sure it's really necessary. (In trying to do this, I modified step 2.b from Digixmax's guide - rather than using the recovery image from CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, I tried using the flashable emmc.zip noted prior. In the end, I just followed Digimax's steps without modifications.) What do you think? Is there any reason to continue trying to flash CWM internally?
...
Click to expand...
Click to collapse
As long as you have SDcard-based CWM available for recovery purpose (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31) you don't really need to flash CWM internally. But if you'd like to flash it internally you can grab a flashable CWM zip file from Succulent's repo http://goo.im/devs/succulent/acclaim/recovery and install it using SD-cased CWM (just like you had installed the ROM/gapps zip files except there is no need for wiping cache/data & doing factory reset in this case).
so i installed cwm touch on my device,
factory reset
clear cache
clead dalv cache
format system
install beatstalk and get this error
E: can't copy meta-inf/com/google/android/update-binary
installation aborted
can anyone help me
i've tried from both my internal and external sd card
What version is CWM? You need 6.0.4.3.
Also, try re-downloading the rom and gapps.
Error I717 vs i717
I have installed CWM touch 6, wiped (2x) then goto install and get the error that "This rom is for I717, and your device is i717" I have formatted the sd card and downloaded 2 different versions of the 4.4 and both give the same error. Also when I try to install others roms I get an error about "Bad" file. Any suggestions?
Only bug I see is YouTube does not work. I uninstalled and reinstalled updates and also tried force stopping the app.
It will play the first video I choose but then it won't play anything else.
Otherwise, Great Rom!
ddochi11 said:
What version is CWM? You need 6.0.4.3.
Also, try re-downloading the rom and gapps.
Click to expand...
Click to collapse
cwm touch 6.0.4.3 and standard cwm 6.0.4.3
i've downloaded cm11 and installed beanstalk 4.4 downloaded rom and multiple version of the rom and all the same thing
Maybe try formatting the sd card
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Installed this ROM and GAPPS from the dev thread for t0lte device.
First issue: AOSP keyboard force close. Looked up solution - install Google KB via APK. Ok, managed to do that, then set it to default. The AOSP FC message still appears, although not as frequently as before, and at least Google KB works.
Next issue: No data, no phone network.
Next issue: Went to set up APN, entered information, Menu > Save, APN did not save.
Not sure what the problem(s) is/are. Wanted to try this ROM but maybe I'll wait a while to see if anyone else runs into the same issues and if so, if they get fixed.
Permissions?
Well apparently the APN issues are caused by any 4.4 ROM if it is installed using TWRP.
So I have tried a couple of 4.4 ROMS using CWM and yes, my issues with APN didn't crop up. However, if I used another ROM that wasn't 4.4 (Paranoid) and then restored a backup of a 4.4 ROM, the APN again disappeared and was not modifiable. Anyway it's not the fault of any particular ROM, it appears.
As for the other issues, I have not gone back to Beanstalk since I posted my other message. Mostly because I don't really want to have to start from scratch every time I want to switch to a KitKat ROM (unless coming from another KitKat ROM, I presume - although I haven't ruled out that any recovery from backup wipes out APN).
Hopefully between the ROM developers and the custom recovery makers, this gets resolved and I can get back to feeding my ROM addiction.