I did get 155 to load properly, but I have another question. I tried to use the AOSP lockscreen, and it locked the phone up on reboot. Had to boot to recovery and nandroid back a saved config. Is the AOSP not an option, or is there something I missed?
mgf316 said:
I did get 155 to load properly, but I have another question. I tried to use the AOSP lockscreen, and it locked the phone up on reboot. Had to boot to recovery and nandroid back a saved config. Is the AOSP not an option, or is there something I missed?
Click to expand...
Click to collapse
Reboot into recovery and wipe the cache and Dalvik cache. Only problem is you'll have to do that every time you reboot your phone. No biggie but still an extra couple of steps in case you reboot.
I think a few users have noted that this or something similar happens when the ripple effect, or other TW effects are still enabled when you switch over to AOSP lockscreen. Try turning those off.
Also, r155 is buggy because Esch rushed it for us. He released an improved r169 last night, which has a lot of common r155 bugs fixed. Here's the thread: http://forum.xda-developers.com/showthread.php?t=1792499
Related
I recently rooted my phone, installed CWM and eventually flashed my phone with Audiophile 1.7. After experiencing problems with the TW constantly FC'ing, I wiped everything and flashed back to my original rom. Now when the phone starts, I have the "ANDROID" word that flashes on top of my stock start up logo? Anyone know how to wipe that off or get rid of it?
I was going to re-flash the 1.7, but see a 2.0 is coming out. So, I will wait. I also installed the boot animation found here... http://forum.xda-developers.com/showthread.php?t=1080426 but still have the same issue.
its because you have 2 boot animations running. delete the one in /system/bin
to fix your tw problems, try wiping the cache, dalvik cache and fixing permissions. once you do that, install another launcher, like zeam launcher or launcher pro, and i hear that should make tw work again.
Worked like a charm....thanks!
jager555 said:
to fix your tw problems, try wiping the cache, dalvik cache and fixing permissions. once you do that, install another launcher, like zeam launcher or launcher pro, and i hear that should make tw work again.
Click to expand...
Click to collapse
I tried all of that and then installed a new launcher, after reinstalling 1.7 again. I once again wiped all and fixed permissions, but then the power button, every 9th time I would use it to put my phone to sleep, it would fc and reset the phone without going through the reboot sequence. I have since went back to the original rom and will wait for 2.0.
But once again, thanks!
Hmm. Try to start fresh. Odin to kc1. Format sd card. Flash ext4 converter, flash the rom, and reboot and let it sit for 10 min. Then check it out.
Sent from my SGH-T959V using XDA Premium App
I wanted to post this in the BAKED thread in the developer section but I don't have enough poststo do it there, so hopefully someone here can help.
I just flashed crespo BlackBean 7 (BAKED) ROM (on my Nexus S) and inverted gapps. It seems to have installed properly but whenever I reboot I get a message that several processes have stopped such as YouTube and GMail, and when I go in to system settings -> storage I get a message saying "Unfortunately, Settings has stopped". I get that message every time consistently. I've tried re-flashing the ROM but to no avail. When I installed the ROM I wiped "Dalvik cache", wiped "Battery Stats" and wiped "Cache partition".
It appears I've not done something or done something wrong, so if anyone here can help I'd appreciate it.
Did you full wipe before installing the rom? That means factory reset/data wipe.
polobunny said:
Did you full wipe before installing the rom? That means factory reset/data wipe.
Click to expand...
Click to collapse
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
volan1 said:
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
Click to expand...
Click to collapse
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
volan1 said:
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
Click to expand...
Click to collapse
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
anshumandash said:
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
Click to expand...
Click to collapse
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
volan1 said:
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
Click to expand...
Click to collapse
There isn't any boot issue with the ROM. If you decide to try this ROM again, try to do a clean install.
Boot into recovery, do a factory wipe, go to advanced & wipe dalvik cache, go to mounts & format /systems. Flash ROM & gapps, reboot.
Sent from my Nexus S using xda app-developers app
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
That's pretty much it
Unfortunately that's pretty much it. Your phone information should eventually stick (dunno why, but it does eventually) but if it doesn't then try another clean install. (btw have you made a backup of your imei, that might help a little as well.) I've had this problem many times and these work for me pretty much every time.
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
IamMark70 said:
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
Click to expand...
Click to collapse
ive been having this issue when i tired both roms so i ended up on cleanrom and then went over to beans for now due to it been base off of clean rom and having the asop look and feel of a aosp rom and the features of touchwiz and the stabilizability of it
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
IamMark70 said:
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
Click to expand...
Click to collapse
yep its pretty good rom i like it. im kinda having a issue with my picture messages though but probably had a dirty flash when i chose the aosp mms. if you like touchwiz also check out cleanrom its a great stock rom best stable rom and pretty great battery life as well and beans rom i think is based off clean well your welcome hope you enjoy the beans rom aslo i had issues with the sim card to so your not alone
IamMark70 said:
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
Click to expand...
Click to collapse
I downloaded Liquid Smooth 2.4, and it finally addressed the issue of the activation screen popping up after every reboot. So I'm extremely happy and loving the ROM!
xt926 unlocked 4.4.2 KK Bootloader
I have a problem that i can not figure out myself with MMS send\fail problems.
When i install CM11 or Gummy (both by Dhacker29) everything goes well and works until i reboot the phone. If i goto settings\about phone\status\ my phone number and MIN are displayed. As soon as i reboot the system those settings become unknown. I've tried this without installing GAPPs and pretty much bypassing everything i could to start ruling different things out. I only install with TWRP 2710, always wiping \system\data\cache etc. After the install i wipe dalvic as instructed as well.
The stock KK ROM works fine. Always displays the correct phone number. (And MMS works)
I do not think it is an APN setting because it works on the initial boot, and i doubt something I am doing fiddles with any settings because I've tried rebooting as soon as the ROM fully loads.
Any suggestions or insight is greatly appreciated.
divxdvd said:
xt926 unlocked 4.4.2 KK Bootloader
I have a problem that i can not figure out myself with MMS send\fail problems.
When i install CM11 or Gummy (both by Dhacker29) everything goes well and works until i reboot the phone. If i goto settings\about phone\status\ my phone number and MIN are displayed. As soon as i reboot the system those settings become unknown. I've tried this without installing GAPPs and pretty much bypassing everything i could to start ruling different things out. I only install with TWRP 2710, always wiping \system\data\cache etc. After the install i wipe dalvic as instructed as well.
The stock KK ROM works fine. Always displays the correct phone number. (And MMS works)
I do not think it is an APN setting because it works on the initial boot, and i doubt something I am doing fiddles with any settings because I've tried rebooting as soon as the ROM fully loads.
Any suggestions or insight is greatly appreciated.
Click to expand...
Click to collapse
A solid temp fix seems to be using 8sms, and manually inputting the phone number in in the 8sms settings, however on the 7/01 build I am not having the issue you are, although I had it before.
I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....