So I tried out the CM11 nightlies, and of course to see how it works I tried the WhisperPush out since it is included in noobdev's builds. Now after attempting setup Messaging crashes immediately upon tapping to open. If i switch Hangouts to be in charge of SMS, same thing, crashes if i try to create a text. I tried 2 other SMS apps from the play store, same problem. Reflashing rom has same issues, coming from another rom to it, also same. Any idea what could be causing it, I can run other 4.4 roms without this issues, so definitely something with CM/WhisperPush.
Same Issue here
wafflenator said:
So I tried out the CM11 nightlies, and of course to see how it works I tried the WhisperPush out since it is included in noobdev's builds. Now after attempting setup Messaging crashes immediately upon tapping to open. If i switch Hangouts to be in charge of SMS, same thing, crashes if i try to create a text. I tried 2 other SMS apps from the play store, same problem. Reflashing rom has same issues, coming from another rom to it, also same. Any idea what could be causing it, I can run other 4.4 roms without this issues, so definitely something with CM/WhisperPush.
Click to expand...
Click to collapse
I got the same problem.
Trebuchet crashed constantly, too. Also, saving Trebuchet's options did not work (migrating from CM 10.2 to 11 M3)
Edit: The "Unfortunately, WhiserPush has stopped" message comes right after receiving the verification code and generating the keys.
Edit2: In Trebuchet Settings, I cannot access "Drawer" or "Dock".
Running:
cm-11-20140210-SNAPSHOT-M3-jfltexx.zip
on SGS 9505 without gapps.
Did you wipe data before flashing CM11? Since this is a major Android version change, it could very well be that there's issues from the 4.3 vs 4.4 data.
For Trebuchet Settings not giving access to drawer or dock, it might have been placeholder or there's a bug accessing those.
Related
I've recently installed CM 10.1 nightly build, the most recent, on my Nexus 4. I am experiencing only problems with gmail, when I attempt to open the application, it loads then crashes every time. It is becoming very disturbing and making me not want to use this ROM. If anyone else is experiencing this issue can you tell me below to get this thread popular so someone might find a fix? And if you've fixed it, can you let me know how?
Thanks, Eric.
EDIT: I'm also realizing that almost all of my GAPPS are not functioning whatsoever. I did a restore of my apps and system and shared to get all my apps back, but now half of them are incomplete for some reason (no icon and non functioning) and the rest work fine though.
ericvolp12 said:
I've recently installed CM 10.1 nightly build, the most recent, on my Nexus 4. I am experiencing only problems with gmail, when I attempt to open the application, it loads then crashes every time. It is becoming very disturbing and making me not want to use this ROM. If anyone else is experiencing this issue can you tell me below to get this thread popular so someone might find a fix? And if you've fixed it, can you let me know how?
Thanks, Eric.
EDIT: I'm also realizing that almost all of my GAPPS are not functioning whatsoever. I did a restore of my apps and system and shared to get all my apps back, but now half of them are incomplete for some reason (no icon and non functioning) and the rest work fine though.
Click to expand...
Click to collapse
If this is your first flash of CM 10.1, you also needed to flash the 11/30 gapps that they point you to in their OP
lol dude another "i flashed xyz rom and now everything is broken" thread
Hey everyone learns one way or another here at q&a. Heck, I'm still asking questions myself
If you backed up everything in Stock, then it will be tricky when you try to restore in Cyanogenmod. You can restore downloaded apps and data safely. But you may start running into problems when you begin to restore system apps, system data, and system settings.
I know some people have had issues with Chrome and Chrome Beta on just about any N7.2 ROM; what happens is that while using it, the app crashes. It doesn't force close, it just crashes; it's near impossible to use because it happens every time you try to load any page. Even loading Google.com causes a crash; if you force close the app, then open it back up, it crashes after only a few seconds.
I've heard multiple things: it's the kernel; no wait, it's the GAPPs; just kidding, it's the ROM.
I have no clue what it is. I haven't been able to get Chrome to work on anything.
I've tried CM10.2 nightlies, I've tried this ROM: CM10.2 Kang. I've tried literally every available kernel. I'm currently using Faux's Enhanced Stock kernel (v002). I've tried clearing the data from Chrome, I've done clean wipes (wiped data, system, cache, dalvik cache). Someone said use SlimRoms Gapps. Tried that, still doesn't work.
I would like some help in either resolving this issue, or maybe some help in narrowing down what's causing the issue. I appreciate any and all help.
I saw someone else had this issue in another thread. I personally have never had this issue with Chrome or any other browser. Try running your Nexus 7 in Safe Mode by rebooting and holding down the volume down button until it boots up.
Right now I'm using CM Kangs ROM with PA Gapps and Elementalx kernel, and no crashing. As a matter of fact, I'm writing this using Chrome. Sometimes when I'm flashing ROMs and use titanium back up to restore my apps, Chrome starts crashing, but a reboot always solve it.
NekroWolfen said:
Right now I'm using CM Kangs ROM with PA Gapps and Elementalx kernel, and no crashing. As a matter of fact, I'm writing this using Chrome. Sometimes when I'm flashing ROMs and use titanium back up to restore my apps, Chrome starts crashing, but a reboot always solve it.
Click to expand...
Click to collapse
I'll give PA Gapps a try. Same ROM as you. I'm desperate.
EDIT: I know some people are lucky to NOT have any issues, but I haven't been using my N7 as much because I can't get Chrome working. I do all my browsing there. :|
natezire71 said:
I'll give PA Gapps a try. Same ROM as you. I'm desperate.
EDIT: I know some people are lucky to NOT have any issues, but I haven't been using my N7 as much because I can't get Chrome working. I do all my browsing there. :|
Click to expand...
Click to collapse
Also, if I have a problem with CM Kangs(because I switch from ROM to ROM) I just full wipe everything(dalvik, system, data, cache) and install one of the first versions of it(10.2-20130806) and then install a new version of it by dirty flash. Then install Chrome new from the store, I don't know, it may not work but just trying explain everything I do. I too can't browse without Chrome, there's AOSP but still prefer Chrome. Report if you got it working anyhow please.
I had major issues with Chrome on both my HTC One and my GS4 Active. It would crash and freeze my phone, requiring a reboot. It would even make my phone freeze when not using Chrome. Once I actually removed Chrome from /system, the freezes stopped completely. It took a lot of troubleshooting and headaches to determine that Chrome was the cause of my issues but I am 100% certain that it was the culprit. I was stock rooted on both devices, no custom ROMs. I haven't had any problems on my N7 yet, but I wouldn't be surprised if Chrome started acting up again.
_MetalHead_ said:
I had major issues with Chrome on both my HTC One and my GS4 Active. It would crash and freeze my phone, requiring a reboot. It would even make my phone freeze when not using Chrome. Once I actually removed Chrome from /system, the freezes stopped completely. It took a lot of troubleshooting and headaches to determine that Chrome was the cause of my issues but I am 100% certain that it was the culprit. I was stock rooted on both devices, no custom ROMs. I haven't had any problems on my N7 yet, but I wouldn't be surprised if Chrome started acting up again.
Click to expand...
Click to collapse
It's not a system app for me.
natezire71 said:
It's not a system app for me.
Click to expand...
Click to collapse
That makes it easier. Just delete it and find another browser. I'm using Firefox. I don't like it as much as Chrome, specifically because it lacks the syncing with Chrome on my laptop, but I've learned to live without it. Firefox is a great browser on its own.
Sent from my SAMSUNG-SGH-I537 using xda premium
Turns out it is Xposed Framework that was causing the issue. I'm assuming it's because it installs a modified "app_process" file in "/system/bin/app_process". I uninstalled Xposed and Chrome Beta works again.
I downloaded and flashed 'cm-11-20140922-NIGHTLY-jflte' (which I know is not as stable as a snapshot but the snapshot was stuck in a reboot loop when I installed it so I had to revert to the nightly) onto my previously stock phone and everything is fine, I can't believe I haven't had a custom rom sooner. However, the ONE app I have problems with is Facebook Messenger; it opens, but crashes when it goes to load my details in and force closes from that point on. It wouldn't be such an issue if I could still interact with people through the Facebook app, but you're forced to use the Messenger app, which seriously will not work at all for some reason.
I've tried reflashing the ROM, clearing the data and cache, cloaking the fact that the device is rooted, installing an earlier version of Messenger and just about everything I could think of. I'm at a complete loss, I don't know what's wrong. I thought maybe something to do with it accessing my contacts or something but I'm really not sure.
Any help will be appreciated, it seems stupid but Messenger is an important part of my phone, I use it daily, so if I can't get this figured out I might have to go back to stock. Thanks in advance guys!
Hi all,
Been having some fairly major issues with this tablet recently. Sorry for the back story, but I'm unsure whether it's related or not...
I primarily use the tablet to watch videos on while I'm commuting from an external USB stick. Always used to be 100% fine, running AOKP ROM for around a year. In the last month or so, I would watch a video and it would work for a couple of minutes, then the video would freeze and the audio soon after. To fix it I'd have to close MX Player, and unplug/plug back in the USB stick. Then it would happen again.
I therefore copied files onto the internal storage, and didn't have problems with this (a 4GB video file would copy with no issues). Then watch from internal storage with no issues.
I decided to try a different ROM and see if it helped the USB OTG issues. This is where the real problems started. I changed to a different Android 4.4 ROM (Purity I think?), and had Google Play Store crashing soon after starting, if I tried to download an app. After the initial crash, I would continually get 'Google Play Store has stopped working' messages. Rebooting etc made no difference. I would also get the same issue if I tried downloading an APK through the built in browser (it crashes).
I have since tried about 5 different ROMs (Android 4.2, 4.4 and 5.0 based) flashed through TWRP 2.8.4.0, with different Gapps, each time performing full or partial wipes/factor resets.
I have also tried restoring to stock settings through NTK, flashing factory images of 4.2, 4.4 and 5.0 builds through the 'restore stock and unroot' option (whatever it is called). I have also re-locked and unlocked the bootloader again.
Basically, I don't know what else I can do. Every time I get into a new ROM, I complete the initial setup, I can't go into Google Play store without the app force closing. I can't think of what would be causing this if it's the same between a lot of different ROMs, with the same issue.
Does anyone have any ideas..?
Thanks in advance.
scorpii said:
Hi all,
Been having some fairly major issues with this tablet recently. Sorry for the back story, but I'm unsure whether it's related or not...
I primarily use the tablet to watch videos on while I'm commuting from an external USB stick. Always used to be 100% fine, running AOKP ROM for around a year. In the last month or so, I would watch a video and it would work for a couple of minutes, then the video would freeze and the audio soon after. To fix it I'd have to close MX Player, and unplug/plug back in the USB stick. Then it would happen again.
I therefore copied files onto the internal storage, and didn't have problems with this (a 4GB video file would copy with no issues). Then watch from internal storage with no issues.
I decided to try a different ROM and see if it helped the USB OTG issues. This is where the real problems started. I changed to a different Android 4.4 ROM (Purity I think?), and had Google Play Store crashing soon after starting, if I tried to download an app. After the initial crash, I would continually get 'Google Play Store has stopped working' messages. Rebooting etc made no difference. I would also get the same issue if I tried downloading an APK through the built in browser (it crashes).
I have since tried about 5 different ROMs (Android 4.2, 4.4 and 5.0 based) flashed through TWRP 2.8.4.0, with different Gapps, each time performing full or partial wipes/factor resets.
I have also tried restoring to stock settings through NTK, flashing factory images of 4.2, 4.4 and 5.0 builds through the 'restore stock and unroot' option (whatever it is called). I have also re-locked and unlocked the bootloader again.
Basically, I don't know what else I can do. Every time I get into a new ROM, I complete the initial setup, I can't go into Google Play store without the app force closing. I can't think of what would be causing this if it's the same between a lot of different ROMs, with the same issue.
Does anyone have any ideas..?
Thanks in advance.
Click to expand...
Click to collapse
Are you sure you're using correct gapps versions? They're specific gapps packages for 4.2, 4.4 AND 5.0.
If you're sure of the above, then yes, I suggest you capture `adb logcat` output when Play Store is crashing. Then share the log with us.
Basically some of the components of play store are located in the system partition and most of custom roms don't come with gapps packages you need therefore to flash them after installing a new rom. PA provides very nice and up to date solution. PA gapps on Google.
Sent from my Xiaomi MI2s
Thanks for the suggestions guys. I had flashed correct Gapps packages for each ROM when required, but was still having the issue.
Somehow, after many hours spread over the last week, last night I seem to have fixed it.
I had suspected that it was an issue with a corrupt partition, (or permissions, or something!) on the internal storage, as it was only when I tried to download something that the browser crashed, and Play Store would generally only start crashing after a first time browsing with it. Also sometimes from within Recovery I wouldn't be able to wipe data properly (it would complete almost instantly, sometimes not removing a previous ROM...). Sometimes it did seem to work properly though.
I can't pin down exactly what I did that fixed it though. I tried 2 things at once: I manually wiped each of /system, /cache, etc through fastboot in the bootloader, and I also (from adb in recovery) manually did mkdir /data and mkdir /data/media
I'm not sure which of these worked, but I flashed a ROM and Gapps (AOKP again), and I haven't had any crashing so far...
I'm afraid to flash any other ROMs as it seems to be working now, so I think I'll leave it!
Probably should have looked at the adb logcat output, but didn't think of that while I was still having the issue.
Thanks
Hi,
I have a Note 3 with Lollipop 5.0.
A couple of weeks ago I started to get this annoying message when there's a call coming in. It forces me to reboot, (the popup doesn't go away but I use the split second after clicking ok to restart ...). Calling out is fine.
I've googled this error and the typical solution of clearing cache and data in the phone and SIM apps is not working.
The error doesn't happen in Safe mode so it suggests that is caused by an installed app. I did a backup and removed all apps and sure enough, the error didn't appear.
After many combinations and trial-error days of work I seem to have pinpointed the culprit.
I use Atom launcher and if I remove it and go back to the default 'TouchWiz' the error doesn't happen so it's definitely the custom launcher.
However, this started to happen recently despite having used Atom launcher for months with no issues. I've tried a previous version with the same problem.
Also, I've tried different launchers (nova, CM ...) and they all cause the error so, somehow the system won't accept ANY custom launcher and it causes the phone error .
I'm at a total loss .... any ideas ?
Thanks