Related
Hi Everyone,
So recently YouTube updated to version 2.4.4, and apparently, videos launch with considerable lag that locks up the device. I've tried every rom with every kernel and they all behave the same. Maybe Titanium Backup? But it worked before...
1. Anybody else getting this?
2. Any solutions?
Wait I just installed RolleTube (version 2.1.6) and it still lags. Now I'm seriously wondering what's wrong.
something is wrong on a system level. try a fix permissions in cwm
icenight89 said:
something is wrong on a system level. try a fix permissions in cwm
Click to expand...
Click to collapse
Well, the even weirder thing is that when I just install a ROM, TiBu, and run youtube, there's no lags. Then when I reboot (because of battery or something), the lag reappears. Fix Permissions seems to be locking up in the middle of the process, and I have to hard shutoff to get the device back working. Funny thing is that youtube worked fine like a month ago...
eliwu26 said:
Well, the even weirder thing is that when I just install a ROM, TiBu, and run youtube, there's no lags. Then when I reboot (because of battery or something), the lag reappears. Fix Permissions seems to be locking up in the middle of the process, and I have to hard shutoff to get the device back working. Funny thing is that youtube worked fine like a month ago...
Click to expand...
Click to collapse
I would wipe everything and start fresh
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
xcrazydx said:
I would wipe everything and start fresh
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
Click to expand...
Click to collapse
Did that already... Even wiped my internal 16gb. Darkside wipe, fix permission, etc. etc. didn't work - still there.
Also: it seems Go Launcher also has some problems with YouTube's lag... the widget on Go Launcher lags to launch the video on the widget, while twlauncher doesn't have that (as much). Still has crazy device-locking lags though.
EDIT: Oh wow... it seems when I connect my phone to my PC it shows up as a corrupted disk... Windows is asking me if I want to fix the disk. Would that be the problem? And if it is, can I let Windows fix the disk?
I don't think I would let windows do that. It says corrupted or needs formatted?
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
Ok. Boot into odin and reflash cwm 5.0.2.6. Boot into cwm and format system, then data, the cache and dalvik cache. Repeat 3x. Flash stock through odin. Reboot, twice. Now reflash cwm and then flaah a rom and configure. I don't care what your problem is, that method is a guarantee fix lol
icenight89 said:
Ok. Boot into odin and reflash cwm 5.0.2.6. Boot into cwm and format system, then data, the cache and dalvik cache. Repeat 3x. Flash stock through odin. Reboot, twice. Now reflash cwm and then flaah a rom and configure. I don't care what your problem is, that method is a guarantee fix lol
Click to expand...
Click to collapse
I did this, and I still had lag after restoring TiBu. Lol the look on my face when it happened
But turns out, the TiBu backup of Go Launcher was actually screwing many apps up (including YouTube)... dunno if it was a system issue, but it was the problem. Transitioned to ADW after a full wipe again (without ever launching go launcher) and all was good. Thanks guys.
eliwu26 said:
I did this, and I still had lag after restoring TiBu. Lol the look on my face when it happened
But turns out, the TiBu backup of Go Launcher was actually screwing many apps up (including YouTube)... dunno if it was a system issue, but it was the problem. Transitioned to ADW after a full wipe again (without ever launching go launcher) and all was good. Thanks guys.
Click to expand...
Click to collapse
Don't restore stuff across roms with TiBu. I only use it as a reference of the apps I had. So I always have a clean slate
xcrazydx said:
Don't restore stuff across roms with TiBu. I only use it as a reference of the apps I had. So I always have a clean slate
Click to expand...
Click to collapse
glad u got it sorted. And while I agree with xcrazydx thay starting clean is best, I have too many apps and not enough time, so thag metgod is impractical. I've never had this ssort of problem though to be honest
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset. Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
I suggest do a full wipe, if you want to keep your app, "tibu" titanium backup is great and well worth app, buy it...I did and worth every dime. IMHO Tibu will and can backup your apps and restore them.
So I suggest get tibu, backup your apps, do a full wipe install Leg3 go back to Gplay download/install tibu back on, then use the program to restore your apps only in this case.
Plus tibu can do a full backup of your data & apps, say you find your DD but want to test other ROMs, use tibu to backup data & apps, go test the another ROM, and want to come back to your DD ROM, you can then do a full data & app restore...plus there are lots of YouTube vid on Titanium Backup app.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
You can do the update and keep your files, which is the reason for the update. Though, like Bigjoe says, a full wipe is always prefered, but not necessary.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
The reason why everyone suggests a full wipe is so that you dont potentially run into any problems after the flash. ie flash not working, or camera wont load... little things like that that make it hard to narrow down problems. One of the main things people are going to ask is did you wipe before you installed? It helps to eliminate and remnants of left over roms so that you dont have any issues with the new rom. Its called a Bad flash.
I hope i answered your question!
Thanks for all the replies! So whether it is the full wipe ROM or the update ROM, both go through the same procedure of booting into CWM first? I will try Tibu for app backup! :good:
Stuck at blue loading loop
Hey, I am new so bare with me, I just flashed this rom onto my Infuse 4g and it seems to be restarting itself and looping to the Blue Android/Dust loading screen. It seems to fix with a fresh install of the rom, but shortly starts after everything seems fine. Please help!
araidis said:
Hey, I am new so bare with me, I just flashed this rom onto my Infuse 4g and it seems to be restarting itself and looping to the Blue Android/Dust loading screen. It seems to fix with a fresh install of the rom, but shortly starts after everything seems fine. Please help!
Click to expand...
Click to collapse
Try doing an odin or hemdall back to stock with partitioning, then flash the full wipe rom.
http://forum.xda-developers.com/showthread.php?t=1524081
http://forum.xda-developers.com/showthread.php?t=1705260
So I've been using your latest release (full wipe Legend v3) and I did factory reset, clear cache and dalvik cache, fixed permissions, etc. The phone is occasionally laggy now, usually when I open web browser it would stay on the white screen a several seconds. Sometimes, when I open my phone, it would stay on the black screen even though I never turned it off and it still has battery. So I had to long-press the button to restart. I've already rebooted and shut down numerous times but these problems still persist.
Also, bluetooth doesn't work for me. When I enable it from settings, the "Turn bluetooth on" checkbox stays unchecked and does nothing.
Should I reflash again? I did to a Titanium Backup to restore apps and settings... Any help is appreciated! Thanks.
turkish ?
i wonder if turkish is included or not ?
turnazurna said:
i wonder if turkish is included or not ?
Click to expand...
Click to collapse
With any rom, you should be able to install More Locale 2 from the Play Store to get support for Turkish (and many other languages).
Yakusoya said:
So I've been using your latest release (full wipe Legend v3) and I did factory reset, clear cache and dalvik cache, fixed permissions, etc. The phone is occasionally laggy now, usually when I open web browser it would stay on the white screen a several seconds. Sometimes, when I open my phone, it would stay on the black screen even though I never turned it off and it still has battery. So I had to long-press the button to restart. I've already rebooted and shut down numerous times but these problems still persist.
Also, bluetooth doesn't work for me. When I enable it from settings, the "Turn bluetooth on" checkbox stays unchecked and does nothing.
Should I reflash again? I did to a Titanium Backup to restore apps and settings... Any help is appreciated! Thanks.
Click to expand...
Click to collapse
My bet is the tibu restore of your settings is what is causing the issues, I've had problems and have known others that had problems when restoring system settings with tibu, especially if the tibu backups were done on another rom.
crt60 said:
My bet is the tibu restore of your settings is what is causing the issues, I've had problems and have known others that had problems when restoring system settings with tibu, especially if the tibu backups were done on another rom.
Click to expand...
Click to collapse
I only started using tibu when I had Legend ICS v2 and then I immediately upgraded to v3 using the full wipe ROM. And then I restored all apps and settings. I'll try wipe and re-flash without restoring any settings in tibu. But honestly, I only wanted to backup my widget and screen settings (such as app shortcuts on home screens) but tibu didn't back that up.
Yakusoya said:
I only started using tibu when I had Legend ICS v2 and then I immediately upgraded to v3 using the full wipe ROM. And then I restored all apps and settings. I'll try wipe and re-flash without restoring any settings in tibu. But honestly, I only wanted to backup my widget and screen settings (such as app shortcuts on home screens) but tibu didn't back that up.
Click to expand...
Click to collapse
I would try reflashing to stock, then reflashing the rom again, are you converting to ext4 at all or just using rfs?
crt60 said:
I would try reflashing to stock, then reflashing the rom again, are you converting to ext4 at all or just using rfs?
Click to expand...
Click to collapse
I'm a noob so I don't know what those are. :laugh: But I've only flashed ZEUS final and then Legend ICS v2 and v3. Full wiped and cleared cache on all those flashes.
I've reflashed to stock and then back to Legend 3 without restoring anything. It is all better now, very snappy. The bluetooth can be turned on now but for some reason, it doesn't detect my Jabra headset no matter how many times I scan. But it detects my Macbook Pro...
I'm not a dev, but it's obvious to me something is wrong.
I re-flashed the eaglesblood ICS rom using clockworkmod recovery v.5.8.1.3 (touch version)
everything seemed okay.
until i started putting apps back on my phone with app backup and restore.
I was getting "process syystem has stopped responding" all over the place.
Then the phone crashed.
it keeps booting, only three apps seem to be running that show themselves in the taskbar, Groove IP, GV SMS integration, and Battery Notifier (Big Text)
It sits there, one one of the home screens, LW animating slowly as it will.. then the phone reboots for no reason.
I installed 4 or 5 different logcat apps but i can't make heads or tails of them
and adb logcat > logcat.txt just spits out this :
/sbin/sh: exec: line 1: logcat: not found
dmesg spits out the log i'm attaching.
Can anyone help me? If i can save the log from one of the logcat apps, will that help?
I'd rather not have to reflash and re-install apps AGAIN.
Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app
Barracuda1101 said:
Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.
Eve_brea said:
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.
Click to expand...
Click to collapse
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..
Eve_brea said:
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..
Click to expand...
Click to collapse
*grumble* damn sun-downer phone. SO all night it was crashing.. So i finally got irritated when i went to bed, yanked the battery out and plopped it on my night-stand by my fan.
This morning i put the battery in, turn it on, and it seems stable.
What the heck?!
logs.
So... between all the log apps i've played with i have a bunch of logs.. if anyone could look them over and tell me if they see a problem, i'd appreciate it.
Re-download Rom+Gapps
Place on SD card
Re-nvflash cwm recovery 5.0.2.0
Wipe data/cache/davlk/battstats/format system
Install rom+gapps
Wipe cache/davlk/battstats
Fix permissions
Reboot
Using touch is sometimes buggy, 5.0.2.0 is most stable. Restoring apps/data is sometimes a messes things up.
Sent from my LG-P999 using xda app-developers 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