Hi xda people!
After I updated my phone to the stock 2.3 rom I've experienced WiFi issues (connection lost, no data transmitted even if the signal is strong and so on) I've then updated from stock to CM7 hoping that this would've solved the problem.
But... it's still there!
Any solution/ideas?
Thank you!
P.S. before updating to stock 2.3 the WiFi used to work like a charm!
Did you tried to wipe the cache when installing?
Yes, I had to, both caches.
Well, actually... did you mean the dalvik (or whatever the name is) and the other one?
Sorry, I'm an uber noob
EclipsedPal said:
Well, actually... did you mean the dalvik (or whatever the name is) and the other one?
Sorry, I'm an uber noob
Click to expand...
Click to collapse
Yep, you need to wipe cache and dalvik. Also, which cm version do you use? Latest nightly or stable? Because you should try a CM KANG instead they're better and might solve your wifi issues. See my sig for the link.
I'm using the stable, I'll give a try to the one you referred!
I just flashed the Android 4.2 Gapps on my GT-P3113 running Paranoid Android 2.51 and all is well.... with the exception of the Camera which I keep getting FC's ("Unfortunately, Gallery has stopped.")
http://forum.xda-developers.com/showthread.php?t=1965895
I just downloaded Camera ICS from the Play store until a fix is made. I'm glad to have the gallery sync back to connect to my Picasa albums though.
Check out the thread and thank garner!
I figured that I'd chime in and say that I'm trying out the new gapps package too.
I'm also getting a FC on the camera, but don't use the tablet for photos anyway (photosphere does sound cool though).
All the other apps seems to work fine though Haven't tested exhaustively though.
lordvader1982 said:
I figured that I'd chime in and say that I'm trying out the new gapps package too.
I'm also getting a FC on the camera, but don't use the tablet for photos anyway (photosphere does sound cool though).
All the other apps seems to work fine though Haven't tested exhaustively though.
Click to expand...
Click to collapse
Try clearing data for gallery and the flash gapps again.
I had same problem with new gapps on Liquid rom on galaxy s3 and that's how I solved it.
Excuse me all, but... Paranoid Android 2.51 and 2.99 are JB 4.1.2, am i right? so, is it correct to try to use 4.2 gapps on 4.1.2 android version?
Yup!
zot71 said:
Excuse me all, but... Paranoid Android 2.51 and 2.99 are JB 4.1.2, am i right? so, is it correct to try to use 4.2 gapps on 4.1.2 android version?
Click to expand...
Click to collapse
Yes buddy, they're two different things, and that's why these releases (and rooting) are so wonderful -- they let you be in the bleeding edge all the time
zot71 said:
Excuse me all, but... Paranoid Android 2.51 and 2.99 are JB 4.1.2, am i right? so, is it correct to try to use 4.2 gapps on 4.1.2 android version?
Click to expand...
Click to collapse
NO, Gapps version needs to match Android version.
DigitalMD said:
NO, Gapps version needs to match Android version.
Click to expand...
Click to collapse
Nope -- I have Synergy ROM on my SGS3 which is based on 4.1.1, and I have GApps 4.2 working just fine.
Sometimes it will work, but you cant just flash any gapps version.
Sent from my GT-P3110 using xda app-developers app
Well what I did was hit the screen to force frist wait till stop then take pic it worked for now untill fix is done .
Sent from my GT-P3113 using XDA Premium HD app
Hi,
I have upgraded from CM 10.1 to CM10.2 and have hit a couple of problems.
Play music keeps on "Stopping" when I try to launch.
The Play store fails whenever I try to update an app or install a new app.
I flashed 4.3 GAPP's and installed SU 1.51 and re-rooted.
Any ideas?
Steve
Rassilon7 said:
Hi,
I have upgraded from CM 10.1 to CM10.2 and have hit a couple of problems.
Play music keeps on "Stopping" when I try to launch.
The Play store fails whenever I try to update an app or install a new app.
I flashed 4.3 GAPP's and installed SU 1.51 and re-rooted.
Any ideas?
Steve
Click to expand...
Click to collapse
Tried clearing play store and play services data?
Happened to me on asylum's with 4.3 gapps as well.. Either stuck at downloading or installing. Clearing data helps but after a while the problem comes back again.
seahorsepip said:
Tried clearing play store and play services data?
Click to expand...
Click to collapse
Hi,
Thanks for getting back to me. I didn't try that, but assumed (incorrectly) that flashing GAPPS would overwrite the cache.
I've rolled back to CM10.1 for a few weeks until there are a few more releases. Loving CM 10 so much, and Focal is pretty cool too.
Steve
yeah i am getting this issue with 10.1 as well except clearing data does not work, also how did you go to 10.2 and re-root i am not sure what to do for that
Rassilon7 said:
Hi,
Thanks for getting back to me. I didn't try that, but assumed (incorrectly) that flashing GAPPS would overwrite the cache.
I've rolled back to CM10.1 for a few weeks until there are a few more releases. Loving CM 10 so much, and Focal is pretty cool too.
Steve
Click to expand...
Click to collapse
Using cm10.1 too on my nexus 7 and xperia z simply because cm10.2 isn't stable enough for me yet
the only thing you need to do now..... is reflash the whole thing.... i was also encountering the same issue..... flashed the boot.img from it and flashed the rom again... no need for flashing the root update and all.....
awesome thing...
seahorsepip said:
Using cm10.1 too on my nexus 7 and xperia z simply because cm10.2 isn't stable enough for me yet
Click to expand...
Click to collapse
I finally went back through the process and this time I cleared out the cache for Play and Music and it all worked perfectly. Seems stable enough too.
Thanks for the suggestions guys.
I upgraded my P1000 from cm-10.1-20131117-NIGHTLY-p1.zip to cm-11-20131210-NIGHTLY-p1.zip
After the update it was kinda working fine. Gapps did not work yet since I did not upgrade that yet, so I installed pa_gapps-full-4.4-20131126-signed.zip.
And rebooted.
That's where the trouble started.
Apps crashed and the P1000 did not startup fine.
I decided to do a full wipe, cleared all caches and re-flashed the P1000.
I does not start anymore (stays on the CM11 boot screen).
What did I miss?
It's not your fault.
It's many different but similar errors in past few days on experimental CM11 builds.
Read http://forum.xda-developers.com/showthread.php?t=2560605 for example.
MarviXDA said:
It's not your fault.
It's many different but similar errors in past few days on experimental CM11 builds.
Read http://forum.xda-developers.com/showthread.php?t=2560605 for example.
Click to expand...
Click to collapse
Thanks,
It seems I updated to CM11 a bit to early, having confidence
If there is someone having a glorious idea...I'm open to those, hehe....
I flashed back to cm10... Maybe it was a bit too early to go to CM11....
This thread can be closed
brenzef said:
I flashed back to cm10... Maybe it was a bit too early to go to CM11....
This thread can be closed
Click to expand...
Click to collapse
Your original problem was using PA GAPPS full. Its to big for the /system partition. You should use one of the BaNkS Gapps versions instead. CM11 runs extremely well on SGT 7, especially after switching to ART.
ulev said:
Your original problem was using PA GAPPS full. Its to big for the /system partition. You should use one of the BaNkS Gapps versions instead. CM11 runs extremely well on SGT 7, especially after switching to ART.
Click to expand...
Click to collapse
That was a very good tip!!!!!
THANKS, upgraded to CM11 with BaNkS Gapps.
+1
brenzef said:
That was a very good tip!!!!!
THANKS, upgraded to CM11 with BaNkS Gapps.
+1
Click to expand...
Click to collapse
Glad I could be of help.
Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:
Fanarkle said:
Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:
Click to expand...
Click to collapse
Nightly builds are just that, builds that are made nightly. They are the most up to date. Snapshots/M(*insert number here*) releases are generally more stable, but we got knocked out of being eligible for them after the release of M8 (thanks kk bootloader). CM has made a msm8960 jb bl section, which you did find. This might get us up and running for a M10 next month if they choose to do that, but then again, msm8960 did not get a M9. Nightly's are for everyone. CM makes a few tweaks to their code and pushes it to each nightly. Some tweaks make it better, some tweaks make it worse. If you are satisfied with the release that you currently are running, you don't need to flash the update if you don't want to. Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Sent from my MB886 using XDA Free mobile app
palmbeach05 said:
Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Click to expand...
Click to collapse
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.
Fanarkle said:
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.
Click to expand...
Click to collapse
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.
Dr. Orange said:
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.
Click to expand...
Click to collapse
When you say "clear cache", do you mean "wipe cache partition," "format /cache," or "wipe delvik cache?" So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.
Yes. Wipe cache. It will format automagically. You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.
Fanarkle said:
So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.
Click to expand...
Click to collapse
Dr. Orange said:
You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.
Click to expand...
Click to collapse
The method of flashing over-top of an existing ROM is referred to as "dirty flashing". The issue isn't so much that it's not recommended or that it develops problems, but it could potentially develop problems, because there's always a chance that the new build relies on some random file that should have been deleted, changed, etc.
So, in summary, it's perfectly fine to dirty flash a CM nightly over your existing version, especially if it works fine for you. HOWEVER, if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."
quasihellfish said:
if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."
Click to expand...
Click to collapse
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?
Fanarkle said:
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?
Click to expand...
Click to collapse
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.
quasihellfish said:
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.
Click to expand...
Click to collapse
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?
Fanarkle said:
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?
Click to expand...
Click to collapse
Well, then I just recommend sticking with XDA. If one of the real CM devs/maintainers then recognizes a bug, someone will report it. Or re-ask this question over there, and they can help you.
Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app
RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Click to expand...
Click to collapse
Did I do something wrong? I am creating a backup and "dirty" flashing the latest nightly right now. I was going to post how it went after I finished just so other people would have the info if they were looking for it.
Success! I rebooted into recovery and, after creating a backup, performed "wipe cache partition" and "wipe delvik cache" before installing cm-11-20140811-NIGHTLY-moto_msm8960_jbbl.zip on top of the build I was running. I rebooted and everything is as it was, except that my custom boot animation was reverted back to CM default (which was expected, no big deal) and the new version I flashed is correctly shown on the "About phone" screen. If I encounter any issues going forward, I will post in the appropriate thread.
Fanarkle said:
Did I do something wrong?
Click to expand...
Click to collapse
No.
RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Why did you post here if you had nothing constructive to say?
I'm glad you got it to work fanarkle[emoji4]