[Q] Play store breaks Cyanogenmod? - Defy Q&A, Help & Troubleshooting

Hi everyone,
This morning when wake up I noticed a lot of applications were stopping ("XYZ has stopped") - including Google Keep. Also, many app/system settings were suddenly missing from the phone. I had to go through the whole process of reinstalling CM10, realizing that my Nandroid backup (made with OBackup) was in CWM format, rendering it unusable with TWRP (or this is what I, being pretty much a newb in the ROM world, understand from the situation).
A couple weeks ago something similar happened : my defy would bootloop at the CM logo.
This is starting to be exasperating a bit. But the only thing I can think of is that now I noticed I have Play Store 4.4.21 on the Defy - whereas on my Nexus 7 I have 4.3.11. Hence the version on my Defy seems to be the one that just came out. Could Play Store updating itself be causing the problems I'm having on my Defy? Why do I now have the new version if I just flashed CM10 a couple minutes ago, and why would it be working correctly now?
I already googled everything I could think of relating to this and couldn't come up with an answer. That is to say, I'm pretty much clueless about all this!
Thanks..

tb877 said:
Hi everyone,
This morning when wake up I noticed a lot of applications were stopping ("XYZ has stopped") - including Google Keep. Also, many app/system settings were suddenly missing from the phone. I had to go through the whole process of reinstalling CM10, realizing that my Nandroid backup (made with OBackup) was in CWM format, rendering it unusable with TWRP (or this is what I, being pretty much a newb in the ROM world, understand from the situation).
A couple weeks ago something similar happened : my defy would bootloop at the CM logo.
Thanks..
Click to expand...
Click to collapse
There are 2 possible things going on here:
problems with android's data sync with google's services. (this morning there was a diffused malfunction, at least here in Italy)
the infamous CM10's data corruption bug (see details in the bug list). it especially happens if you let completely discharge your phone. Symptoms match with yours
Since the data corruption bug is still under investigation, the best workaround is to keep a (weekly?) data backup.
After a data corruption, reformat in ext4 through the recovery's data tool and then:
reflash rom and gapps
restore your data

Well both times CM broke my phone's battery wasn't empty at all (the last time it was charging...)
When you refer to the sync problem I experienced it on my N7 yesterday, but it seems nowhere as dangerous as to be able to completely break the OS.
Oh well anyway, seems like CM10 isn't quite ready for being a daily driver.. I'll simply learn how to flash/restore backups correctly and as fast as possible it seems!
Sent from my Nexus 7 using Tapatalk 4

The only thing that really bothers me is that I never thought I'd lose so much time in rooting/modding my old defy.. I've spent countless hours on XDA/other forums, and yesterday I even had to restore the (almost bricked) defy with rsdlite after (incorrectly) trying to put CWM to restore my otherwise unusable backup. Then, when I had succeeded in putting CWM, it would totally refuse to restore, complaining about unmountable /system!
I do understand that its totally my choice to root/mod my devices, but with cell phones becoming more and more essential nowadays in everyday life, it seems to me that everyone almost has to become an android developer to survive!
/whine
Sent from my Nexus 7 using Tapatalk 4

Related

Annoying "Major" Startup FC Errors - Loking for Some Feedback

Alright I've searched through XDA, and I'm sure this has been covered before but I couldn't find it.
Problem:
Booted up my phone (i9000T) up this morning and it started vibrating (the FC vibrating type feedback), and I was getting all these .com.Android errors (from the keyboard, to internal Android errors, to Pandora, to the keyboard again ETC). Eventually it kicked me back to the initial setup screen and all those errors kept popping up. (The last apps that I installed were 2 days ago, Shazam and Soundhound from the market)
Finally I said "Screw it", reflashed my phone in Odin, repartitioned, and reinstalled everything (since I decided to format my SD in the Recovery Menu too which I forgot that my TiBu backup was on)
Is my phone/SD Card dying, or WTF is going on? & How common does this BS happen to you guys?
A little background:
I had 2 different i9000m (bell) phones that died from the internal SD errors. When they were dying they went through this same startup BS as what happened to my i9000T. Eventually on the next reboot they would go through the "boot loop of death".
So I decided to go the "i9000T" route because I got really tired of my i9000m phones dying. So of course I'm very concerned about WTF is going on with my i9000T (since that phone isn't supposed to have the SD issues like the Bell)
My current Setup:
i9000T
Running one of the stock Froyo Euro Roms (I9000XXJPU) for a couple of weeks now
Added the I9000B_JPA_JP3_JPA_JPA_modem_850.zip modem to get 3G
Rooted with CF
Apps I have apx 60 or so (all from the Android Market) mainly general BS stuff like Launcher Pro, Smart Keyboard Pro, TV Guide ETC...
I mean I really LOVE the Galaxy S phones, but none of this stuff crapping out ever happened when I owned a Milestone, Desire, or even my Atrix.
My first 2 i9000M phones lasted a month, and now this goofy error happened right around the month mark for my i9000T too, but haven't received the "boot loop of death yet?"
Right now things "appear" to be fine after I reinstalled all my apps and settings again from scratch.
So as my bold question above states:
Any ideas what could be going on with my phone, and is this that common of an issue for the Galaxy S users?...
So how often does a stock ROM crap out for no reason for you guys?...
Sent from my GT-I9000 using xda premium
I once had an error like that, which I thought was probably due to me messing up flashing in Odin. However, it hasn't recurred in a couple of months now, although I'm using the international I9000 and not the I9000T. Also, I've stopped formatting the internal SD during flash to increase its longevity, given I don't flash too often.
do you have a lot of apps installed ?
if yes check if datadata is full or not..
Chief_Death said:
do you have a lot of apps installed ?
if yes check if datadata is full or not..
Click to expand...
Click to collapse
I have exactly 60, with plenty of space available.
None of these errors are making any sense to me...
Sent from my GT-I9000 using xda premium
Clicking repartition doesn't do a factory reset and doesn't clean the cache data.. You need to do that in the 3 button recovery mode (Factory reset / Wipe cache data) in the On-Sound "-" and Home menu.

Strange "black" Reboots

Hi!
I'm suffering from reboots on my Note (also on my S2...). I call them "black" reboots because the screen becomes black, there's no start-up animation , I only hear the sound, and the home screen don't comes up, or it do it after a long delay. So, the screen is mostly black. Until 2-3 minutes pass, and reboot again.
-Sometimes occurs simply starting up the phone in the morning. I'm advised of a slow launcher load (Go Launcher, but it can occurs on TW).
If I go to System Monitor (System Panel app), I see the 2 cores working hard, toghether or alternating. The "System" app goes mad. The battery drain becomes quick, and the phone back around the camera begins to warming...
After 2-3 minutes with this behaviour, the "black" reboot comes up. Often, after rebooting, the message "Unable to run System process"- Force Close-Wait (or so) appears in the black...etc
If I force shut-off, then I wait and then shut-on again, all things seem normal, until...reboot
-Factory reset (through Recovery, of course) seems arrange all things, until I load again the apps. I've unistalled all "tweaking" apps for overclocking, Ram managing, etc. I only have Root explorer and Speed Boost as Root operating things...
- My Rom is an odex Pre-rooted XXLC1, Modem XXLB2, but the multiCSC is not from it.
How the phone can become so unstable with only the half memory app capacity occuped? (800 Mb or so of 2GB)?
And how can it often occurs on updating apps from damned Google Play Store?
Is worth to flash another Rom (not ICS...), or re-flash same with its CSC included?
Sorry if I've been too long. In my searchs I only see things about bricks or another type of reboots.
Thanks for read me!
i get these once every two weeks or so.
I also get these type of reboots, I get them on RocketROM and on previous roms I've had installed the only way I've found to get out of them is to boot into recovery and wipe the caches. Before I was rooted I removed some of the apps I'd moved to the SD Card and that sometimes stopped the boot loop. I now only update apps one by one someone suggested it was to do with the amount of apps moved to the sd card and the multiple updating of them. I'm still not sure of the cause I know its the only flaw on my Note that I'm fed up with.
Im running stock ics rom straight from samsung only with root and getting the same behaviour as yourself. About 2 to 3 times a week...
Sent from my GT-N7000
Ive posted a poll as i also experience this issue. Can you vote on the poll here please with how many reboots you are getting etc - http://forum.xda-developers.com/showthread.php?t=1706343
tallen3 said:
I also get these type of reboots, I get them on RocketROM and on previous roms I've had installed the only way I've found to get out of them is to boot into recovery and wipe the caches. Before I was rooted I removed some of the apps I'd moved to the SD Card and that sometimes stopped the boot loop. I now only update apps one by one someone suggested it was to do with the amount of apps moved to the sd card and the multiple updating of them. I'm still not sure of the cause I know its the only flaw on my Note that I'm fed up with.
Click to expand...
Click to collapse
gnikolakis said:
Im running stock ics rom straight from samsung only with root and getting the same behaviour as yourself. About 2 to 3 times a week...
Sent from my GT-N7000
Click to expand...
Click to collapse
Guys, i don't know if I'm going to cry of pain or to laugh of huge joy, after seeing this is almost ..."normal"
We have a beautiful 500€ plastic and metal block which is unable to perform the half of things it's supposed to do! And we don't know exactly why...
Sure I do wipes, but most of times this fixes nothing, and the reboot returns.
If I re-install with Titanium, I am very careful unsellecting into the batch which things can cause problems, installing only a few apps.
After some days, I go on installing manually some others.
The Play updates are critical, as I see... Why? How it's possible that this "beasts" with so much RAM and so much App Memory (2 GB on S2 and Note!) fail down handling its management, with their super 2 core CPU's?
It's too serious. How we can live with a 500€ phone rebooting bad 2 times a week?
Can you imagine that on your computer, forcing you to re-install OS and apps once or twice a week? It's crazy. Is Android going crazy?
Maybe Samsung don't like Root users? Have HTC same problem?
There's someone with a non rooted phone with same problem?
Are you guys running stock? Had custom rom installed or still have?
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Are you guys running stock? Had custom rom installed or still have?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I have this Rom, based on strict stock, but rooted: http://forum.xda-developers.com/showpost.php?p=24690725&postcount=154
Mine is the XXLC1
No tweaks, no overclocking, no CWM...
I had the same problem when my GN was on rooted LC1. I disappeared after I made a factory reset and let my apps reinstall by Play Store.
Yes me too got out of this strange reboot by a factory reset today morning.
Something is messed up .....
Very difficult to find that something ...
better idea would be a factory reset .....
I think the problem is with the Stock Samsung Rom, it doesnt happen in CM9 Roms. I had this problems wen on ROcket rom, but vanished when on Asylum Rom.
go wild...
"I had the same problem when my GN was on rooted LC1. It disappeared after I made a factory reset and let my apps reinstall by Play Store"
Thanks, milesabords, I'll try that the...(glappps) next time.
.
prabhu1980 said:
Yes me too got out of this strange reboot by a factory reset today morning.
Something is messed up .....
Very difficult to find that something ...
better idea would be a factory reset .....
Click to expand...
Click to collapse
Yesss, very difficult. I'm not on advanced technical stuff, but my intuition says that is something deep inside the Rom, something that is related to CPU-Memory management.
By the way, do you have/had many apps (250+)? Have you made recently massive update and/or installing apps, or massive "App to SD" moves?
bhasg1007 said:
I think the problem is with the Stock Samsung Rom, it doesnt happen in CM9 Roms. I had this problems wen on ROcket rom, but vanished when on Asylum Rom.
Click to expand...
Click to collapse
You are pushing me a little step more to the wild side of Android.... Here I'll go!
It seems to me that the Note is a strangely different phone of, say, S2. Some apparently "simple" apps that I carry on from 2 years ago don't run right.
And the little lags that sometimes appear on touching icons, never, never appear on the fast S2.
Lol be carefully factory on ICS resetting...
Try and official rom, haven't seen it myself
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Lol be carefully factory on ICS resetting...
Try and official rom, haven't seen it myself
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Don't worry, baz77, I don't touch ICS by now even with gloves & calipers...

Bizarre FCs

Ok, if anyone can help me out on this, I'd be really grateful.
So, it started something like a couple months ago.
I was on Cyber.GR and Matr1x kernel, all was fine, when suddenly the phone stopped being usable: everything FC'd at boot and rebooting was of no use. I was pissed off but luckily I had a NANDROID from a couple days before.
I restored it and all was fine again.
One week passes and BAM everything FCs again.
I tried to switch kernels, but nothing.
I decided to wipe everything and flash AOKP (faster updates and Cyber.GR dev was going in service) and AIR Kernel.
I restored my apps using Titanium and everything was fine again.
One month passes and all of a sudden, a friday night, FCs again.
I was in panic, tried reflashing kernel, fixing permissions, wiping cache and dalvik, no use.
So I googled a little bit and found out that reflashing the ROM usually fixed the problem.
I reflashed ROM and gapps and, as google said, everything was back to normal.
Except that once again, nothing's fixed.
The phone stays stable for a couple of weeks circa, then it starts again to force close everything.
Reflashing ROM and gapps seems to fix this, but as you can see it isn't a permanent solution.
I post a logcat I took when the FCs started, so it's like 2 months old.
If anyone knows the reason of all of this, I will gladly pay you a couple beers: this ****'s driving me nuts.
Here's the logcat: http://pastebin.com/C6hr0sDT
tl;dr: phone randomly start force closing everything at boot on different combos of kernels and ROMs. no ****ing idea. paying money for solution.
Have you tried using another ROM? Seems like the easiest route to take.
Sent by pocket technology
After you flash the rom when you install your apps again do you just install the app or do you install with data? Its better to install apps fresh cuz if the data's corrupted then your going to get FC! Try installing the CM9 Skank Rom & don't flash another kernel leave it as is then install all your apps fresh no data & run it for weeks or months see if your still having fc the CM9 skank kang Rom are really great & stable try it out here you go! :thumbup:
http://forum.xda-developers.com/showthread.php?t=1386869
°N€×U$ $⁴G°
Make sure not to include system apps when restoring backups using tb. That might be the issue
Sent from my Nexus S®
That as well. I saw you did use AOKP also. Hmmmm. In my personal experience, my phone likes stockish kernels. Matrix always froze up on me after 100+ hours of up time with the stock nexus voltages applied. Air Kernel always gave me FCs. My phone is picky. No idea why. Maybe try using another kernel, stockish this time and see what happens? I haven't had any lock ups using thalamus', Pete's or, Simple Kernel.
Sent by pocket technology
Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think
Thanks for the replies, guys!
Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.<br />
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).<br />
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think <br />
Thanks for the replies, guys!
Click to expand...
Click to collapse
Yeah starting from scratch will not hurt too much ;-)
Sent from my Nexus S®

[Q] phone reboots during titanium backup

Hi,
my i9305 behaves a bit strange recently, and I wonder if it's a hardware flaw or a software porblem
As you can see in my sig I'm up to date with OmniROM nightlies, and as my phone refuses to charge the battery properly (a problem with the usb jack I'd say) I think it may be both
Now, here's my problem: I'm trying to back up all my apps in order to move most of the stuff to my new mobile, but during backup it happens to reboot after a while.
I tried to make a logcat (attached), but honestly speaking I don't have a clue what to look for, as I'm no coder.
Can anyone take a look and maybe hint me to what may be the problem? I'm totally lost
husky69 said:
Hi,
my i9305 behaves a bit strange recently, and I wonder if it's a hardware flaw or a software porblem
As you can see in my sig I'm up to date with OmniROM nightlies, and as my phone refuses to charge the battery properly (a problem with the usb jack I'd say) I think it may be both
Now, here's my problem: I'm trying to back up all my apps in order to move most of the stuff to my new mobile, but during backup it happens to reboot after a while.
I tried to make a logcat (attached), but honestly speaking I don't have a clue what to look for, as I'm no coder.
Can anyone take a look and maybe hint me to what may be the problem? I'm totally lost
Click to expand...
Click to collapse
soft reboot (bootanimation) or hard reboot (back to bootloader)?
Since you're running a modified configuration (changed kernel) - no clue what's going on. I'm going to assume the problem is the modified kernel until you're actually running Omni as opposed to modified pseudo-Omni.

[Q] Investigating really slow Nexus 7 2012

Hi,
My Nexus 7 2012 (very first batch) is quite often behaving really slowly. It is common for the settings screen to take 15-20 seconds to open. From the homescreen. With no running app.
Here is a video after I've reset everything to factory defaults, let it run and index things on its own for an hour and then manually upgrade a small app:
At other times, the speed is pretty decent for such a tablet. I just can't figure out why this difference. I've tried to check for wakelocks, tried a logcat and many other things. I can't make any sense from it.
Rebooting the tablet seems to have 50% chance of fixing the problem. So it's probably not a memory leak.
The tablet is rooted, on the latest build and I noticed that App Ops X survived the reset but no funky software is installed and the behaviour predates the installation of App Ops X. The network is not a problem here. The 2013 Nexus 7 of my wife works just fine and so does the Nexus 5 taking the above video.
How can I investigate this ? Is there an app that can run various reliable diagnostics to find out what kind of activity is causing trouble ? I tried to use logcat but the result is quite verbose and nothing rings a bell. I would really like to understand rather than just return it and wait or, worse, buy a new device.
Thanks.
Let me know if you find a solution my Nexus 7 has been really slow, Im rooted with CM11 M6 & KK GAPPS, TWRP 2.7.0.0 I dont know what happened to this tablet.
edarchis said:
Hi,
My Nexus 7 2012 (very first batch) is quite often behaving really slowly. It is common for the settings screen to take 15-20 seconds to open. From the homescreen. With no running app.
At other times, the speed is pretty decent for such a tablet. I just can't figure out why this difference. I've tried to check for wakelocks, tried a logcat and many other things. I can't make any sense from it.
Rebooting the tablet seems to have 50% chance of fixing the problem. So it's probably not a memory leak.
The tablet is rooted, on the latest build and I noticed that App Ops X survived the reset but no funky software is installed and the behaviour predates the installation of App Ops X. The network is not a problem here. The 2013 Nexus 7 of my wife works just fine and so does the Nexus 5 taking the above video.
How can I investigate this ? Is there an app that can run various reliable diagnostics to find out what kind of activity is causing trouble ? I tried to use logcat but the result is quite verbose and nothing rings a bell. I would really like to understand rather than just return it and wait or, worse, buy a new device.
Thanks.
Click to expand...
Click to collapse
droid4lif3 said:
Let me know if you find a solution my Nexus 7 has been really slow, Im rooted with CM11 M6 & KK GAPPS, TWRP 2.7.0.0 I dont know what happened to this tablet.
Click to expand...
Click to collapse
Mine too. Nexus 7 2012 16GB running PA 3.99 (JB4.3). PA Kernel and GAPPS, PA launcher or whatever one came with stock PA.
It takes upwards of 10 seconds to unlock frequently, even from a fresh boot, and without any security just a simple swipe unlock.
App drawer can take 10-15 seconds to open.
If I touch too much during these lag times I will often get a launcher not responding error.
I've about given up myself and am looking at other ROMs. Before I reflash though I may try a different kernel.
I'm downloading a few right now and I'll hopefully remember to report back my results.
Mine is suddenly unbearably slow too. It's a 2012 edition and I'm not rooted, running the stock software. I've tried clearing caches (app and system), doing a factory reset, flashing the factory image, but it just runs like a dog. When I switch it on it takes a few minutes to become responsive, and apps regularly say they will take upwards of 20 minutes to download updates - small apps too, about 3MB. The download issues are nothing to do with my wifi as the tablet is slow wherever I use it, and my Nexus 5 downloads the same things in a matter of seconds. Would love to know what I could do to fix my N7. I don't want to root it or flash a custom ROM - don't want to go down that route - I just want the great performance that I had from it before.
I was having the same issues described here as well after owning the tablet for awhile, and tried every custom ROM, kernel, and android version I could find for our device along the way, in the hopes of finding a solution.
The one thing that finally helped for me, was formatting the device to use F2FS file system format on all partitions. The initial setup is a bit tedious, as you will lose ALL data on the device, so first must back up everything, then restore it all once the device has been reformatted. But the payoff has been huge for both me and my wife.
Making this switch has made both of our tablets usable again, even enjoyable! It's well worth the effort put in to make the switch.
See this thread here http://forum.xda-developers.com/showthread.php?t=2678140, which has the modified recovery, files, and instructions needed to convert. It also helps to first make sure you can successfully use fastboot/ADB commands from your PC to the device, in case you get into any trouble along the way.
There's also an app now available for converting any rom to all-f2fs (prior to flashing), it's cheap and well worth the cost (about the price of a cup of coffee) https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs&hl=en.

Categories

Resources