I rooted and upgraded my rom to Eos 1.0.0 several months ago. Ever since then ive been having issues with my bluetooth devices staying connected and working property. Also, lately my browser has been closing randomly and will get worse unless I reboot.
I absolutely love the team Eos build and hope they can help me find a solution. I am wondering if anybody else has had the same issues or know of anything that can help me?
Would upgrading to their new rom build help you think?
Upgrade to EOS 2.0.0
Can you go into recovery and wipe cache, and davlik? and check again.
And, if you decided to upgrade to EOS2.0, don't forget to wipe cache, dalvik and battery stats thru recovery.
Related
Hey guys,
I've got a Wind G2X which I've recently installed the new 2012 baseband on using LG's tool and the local webserver trick (I believe this technically rebrands the phone to T-Mobile). I then installed some not-latest Eaglesblood AOSP and had it for a while -- everything was pretty solid.
Then I decided to upgrade to the latest, since I like to stay up to date. During this upgrade, I've also tried to "Fix Permissions" (in CWM, after a data wipe) to make sure the permissions are correct just in case -- this operation makes no sense if it relies on there being data (I suspect it does, because I was able to successfully Fix Permissions after flashing the ROM). While "fixing permissions", I've had the phone freeze up, so I pulled the battery, tried again, same thing. Ever since, I've tried installing the latest EGB AOSP and kept finding my phone either dead due to emptied battery (way too quickly) or dead WITH battery charge, every day.
Just recently, I flashed HellFire Sandwich (tried 1.7 and now 1.9), both of which greeted me with "Process stopped.. something something.media". Now in 1.9, when I went to the Play Store for the first time, it hung. I had to pull the battery. 2nd run worked fine.
So I have the following questions:
1. What could be wrong? I doubt it's just bad luck with the ROMs -- surely they would notice such significant problems.
2. When I flash a new ROM, I do the "wipe data/factory reset" and "Wipe Dalvik cache" (should I do the 2nd step? if not, can it cause problems?) followed by flashing the ROM and then GApps. When I do this, can there be some remains from the previous ROM (or some system components) causing the stability issues, or is it a perfectly clean installation with the exception of the recovery partition?
3. Is there anything I can do to truly restore/wipe the phone to prepare it for flashing some ROM and guarantee that there isn't some residual software that can cause problems?
I'll see how stable HellFire Sandwich 1.9 will be on this phone, but the .media crash and Play Store hang may be indicators of more to come.
Thanks!
:/
All ICS roms for g2x have issues with the stability , you should wait the new SU660 Kernel source for a super stable and fully working ICS ROMS
always make wipe factory reset, wipe dalvik and go to advanced and select format /system , before flash any roms, there is no bug froms previous software if you follow these steps (sorry for the english lol ) e_e/
I recomend you any cyanogen based rom (GB 2.3.7) with camera port for cyanogen in the lg optimus 2x thread
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Meshelton said:
Hi all,
My front facing phone speaker seems to be permanently muted. Whenever I get or make a phone call no sounds come from the speaker on the top front of the phone. When I switch to speaker mode everything works fine. Also the phone randomly disconnects from the phone network then reconnects. I was originally running Cyanogenmod 10.0.0 during which everything was working fine. I then upgraded to a nightly using the built in cyanogen upgrader. For a time after this everything continued to work. Eventually these problems began. I again upgraded, using the built in upgrader to 10.1.0 RC1 then 10.1.0 RC2 which didn't seem to change anything. Finally I used recovery to wipe the cache and factory reset and flash 10.1.0 RC2 and the latest gapps package. This didn't help either. I then repeated that process except with the version 10.0.0 of cyanogenmod which also did not fix the problem. I'm not sure if these problems are actually related but they seemed to start at around the same time. I've never knowingly flashed a radio on this thing, I'm not sure if the in app upgrader does this or not. I was wondering if anyone had a good idea on what my next course of action should be or if they have had similar issues and have found a solution.
Thanks.
Click to expand...
Click to collapse
If you were happy with everything working WHY in the world did you upgrade to a Nightly? Nightly by definition is only for people who know what they're doing and are not afraid of the Night.
Anyway, there are like 6.0221413e+23 changes from cm 10.0.0 to 10.1 RC2. What can I say you did a dirty flash (upgrade!), and probably didn't back up.
So the first thing you should do is back up. NOW (go to CMW recovery and back up)
Download a better behaving nightly like the one JD1639 uploaded. get it from http://forum.xda-developers.com/showthread.php?t=2272261
Download the UCMC1 radio (assuming you're on at&t)
Download the gapps 20130301
Put them all on in one folder for easy access
goto the CWM recovery and get to work:
1-backup
2-cleanup: go to mounts and format data, cache, system (don't format the sdcard!!!) and don't reboot until everything is finished
3-clean dalvik cache from advanced
4-install in this order: RADIO file.zip (UCMC1)
5-CM ROM
6-gapps
7-go to Advanced Restore option, find you back up and restore the "DATA" portion ONLY
This should save you ... good luck,
Commodore 64
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Meshelton said:
Thanks for the reply.
That seemed to fix the connectivity issue but not the sound issue. I guess that could just be a hardware thing. If it were a software issue is there anything else I should try?
Click to expand...
Click to collapse
You know I don't think it is a hardware issue since it started after one of your updates. If you were on a ROM for while, and one morning you wokeup and the sound didn't work ... maybe. But i'm not convinced since also I remember around Feb-March there were some complains on sound not working after flashing to 4.2.2 version of the cm. Try flashing back to the stock UCMC1 ROM (absolute stock flashed with Odin not CMW) and then do a factory reset.
Hi everybody,
I decided to go back to Cyanogenmod, because i had some issues with the ROM I used before. First I flashed the CM 10.1.3 stable, everything worked fine, but I couldn't connect to any WiFi. So i tried flashing the nightly 10.2 10.2 2013111 over the Updates in the preferences. Still, i couldn't connect to any WiFi. I tried it two more times with full wipes and flashing the nightly over my Recovery, but couldn't make it work.
All these times i flashed the boot.img after flashing the nightly. I don't really know what to do anymore and thought anyone might have an idea for me?!
I didn't have any major issues until today, so i don't know what Information you might need to help me, so please tell me if I should say something more about the system or how I flashed it etc.
Thanks in Advance!
Edit: Same Problem with CM11...
Edit 2: Tried to flash the Bubba Kernel, because i read something about it...now i can't even turn the wifi on. -.-
I've been trying most of the currently available roms for my huawei ascend mate. With all of them I have trouble with wifi.
I started with stock B221 (4.2.1), then upgraded to B907 (4.2.2). Also tried hydrom52, cyanogenmod and Pac man rom.
With all of them I had trouble with wifi and I feel too frustrated to just keep it as it is.
I have read that newer stock roms are getting better. I tried B930 which is a China release but that still had wifi issues.
Every now and then the connection is dropped and I have to disconnect and reconnect to get it workin.
Can it be that I did not wipe propperly before/during/after installing the rom?
The official ones were installed as update, through the huawei system which does not ask for wipes. The custom ones were wiped as recommended by each dev. But that info is often not that rich for me as a noob.
How should I go about making the cleanest install possible?
SvenHee said:
I've been trying most of the currently available roms for my huawei ascend mate. With all of them I have trouble with wifi.
I started with stock B221 (4.2.1), then upgraded to B907 (4.2.2). Also tried hydrom52, cyanogenmod and Pac man rom.
With all of them I had trouble with wifi and I feel too frustrated to just keep it as it is.
I have read that newer stock roms are getting better. I tried B930 which is a China release but that still had wifi issues.
Every now and then the connection is dropped and I have to disconnect and reconnect to get it workin.
Can it be that I did not wipe propperly before/during/after installing the rom?
The official ones were installed as update, through the huawei system which does not ask for wipes. The custom ones were wiped as recommended by each dev. But that info is often not that rich for me as a noob.
How should I go about making the cleanest install possible?
Click to expand...
Click to collapse
On my Moto G (I know it's not the same phone but the idea may be the same) when I installed custom ROMs without wiping the /System partition I always had issues. Try wiping cache/dalvik, factory reset and formating system before install.
Ah, ok, thanks.
That gives me a bit of confidence to try one of the roms again. I think I only wiped cache/Dalvik with most installs.
Does it need to be in the sequence you mention?
Hello all, I have some problems I hope you guys can help with.
My phone is a Samsung Galaxt S3 i-747, the att version, running CWM 6.0.4.7.
I am having an issue with every rom I have installed thus far. My battery level registers at anywhere between 14-51 percent and discharges rapidly from there. I have reinstalled each one at least 3 times. Before installing, I made sure to format /system, wipe cache partition and wipe dalvik cache. I ahve even tried such apps as Battery Calibration.
The roms I have used are as follows, and the problem persists with each one.
- Carbon Rom
-Gummy Rom
-LiquidSmooth
-SlimKat(would not go past the Sliktkat logo)
-Dirty Unicorn(would not go past the Unicorn Logo)
-Stock Rom with Root
-Have tried LeanKernel, Archie Kernel and the stock kernel.
Each one has these problems, and two won't even boot. I'm at my wits end and I'm about to repurpose this phone for target practice. Hopefully one of you can help me out.
n3onxhaze said:
Hello all, I have some problems I hope you guys can help with.
My phone is a Samsung Galaxt S3 i-747, the att version, running CWM 6.0.4.7.
I am having an issue with every rom I have installed thus far. My battery level registers at anywhere between 14-51 percent and discharges rapidly from there. I have reinstalled each one at least 3 times. Before installing, I made sure to format /system, wipe cache partition and wipe dalvik cache. I ahve even tried such apps as Battery Calibration.
The roms I have used are as follows, and the problem persists with each one.
- Carbon Rom
-Gummy Rom
-LiquidSmooth
-SlimKat(would not go past the Sliktkat logo)
-Dirty Unicorn(would not go past the Unicorn Logo)
-Stock Rom with Root
-Have tried LeanKernel, Archie Kernel and the stock kernel.
Each one has these problems, and two won't even boot. I'm at my wits end and I'm about to repurpose this phone for target practice. Hopefully one of you can help me out.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
I think this is a battery issue, so in my opinion you should first try with a different battery to see if the issue persists.
But for any other questions you can always ask here: Galaxy S III Q&A, Help & Troubleshooting
Good luck!