Hi,
Defy Plus, running the 20150103 nigthly from Quarx. After one night of charging I found the phone asking for the sim PIN as if it has rebooted. I found out that the following were lost:
-all or almost all settings
-most (but not all) of the programs installed with GooglePlay
-GooglePlay itself.
I tried the following:
-reinstalled GApps
-installed a newer CM nightly: 20150117.
Other details
-contacts list (unsynchronised) and call history are OK
-sdcard seems to be OK, filemanager and gallery can access it
-messaging and some other programs crash on start-up
What could be the problem?
Additional details:
- Crashing messaging app says:
01-17 13:59:30.949: E/AndroidRuntime(3196): java.lang.RuntimeException: Unable to instantiate application com.android.mms.MmsApp: java.lang.ClassNotFoundException: Didn't find class "com.android.mms.MmsApp" on path: DexPathList[[zip file "/system/priv-app/Mms.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
-I can also provide an strace; I didn't find anything useful inside (though I'm not an strace expert).
- Looks similar to:
http://forum.xda-developers.com/showthread.php?t=706773
Probably solved
Messaging was solved by deleting the cache.
GoogleApps and stuff was solved by repeatedly installing different GApps from the internet. pa_gapps-modular-mini-4.4.4-20150117-signed.zip was the last one that finally gave back all functionality.
Related
I don't like the HTC Messaging app much because there are too many bugs with it. I don't like Handcent SMS either (the option list is a mile long). I wanted to switch to the stock Android Messaging App.
So what I've tried thus far was to install the stock one, but that obviously didn't work because it tries to override Mms.apk (the HTC one) and since I don't have root, it can't write to /system. So I found that someone on XDA ran into a similar problem and found a way to rename the stock Android Mms package to Mmz and install it without root. Here's the thread: hxxp://forum.xda-developers.com/showthread.php?t=675914 (replace hxxp with http)
I was able to install it but when launching the app, I get a Force Close dialog. I looked up the error log and the error is:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.mmz/com.android.mmz.ui.ConversationList}:
java.lang.RuntimeException: Binary XML file line #4: You must supply a layout_width attribute at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2649)
...
Anyone have any ideas? I would really like to get the stock Messaging on here.
Hello,
Quick inquiry with regards to a minor complication when attempting to flash a custom theme to a Sony Xperia X10.
The device has been rooted successfully and is currently running Wolfbreaks CM 6.1.3 v053.
I have attempted to flash a custom theme titled "Galaxy S for CyanogenMod 6.1.1 Stable". Everything functions perfectly thus far. Other then the fact that upon reboot an error messages specifies that Gmail has ceased unexpectedly.
The exact message displayed is quoted as "The application Gmail (process com.google.android.gm) has stopped unexpectedly. Please try again." Although this message displays consistently upon each attempt to restart the program. Also automatically once the device initializes from a reboot or shutdown. The theme was flashed via xrecovery as custom zip. As per instructions "cmparts_ui.xml" was transferred to /sdcard/CMTheme and selected from the Tweaks menu.
(Thread referenced: http://forum.xda-developers.com/showthread.php?t=876600)
This problem did not occur originally when CM 6.1.3 was flashed. Would resolution be a matter of reflashing Cyanogenmod? or as simple as updating the application itself within the market? I can not locate any original files to flash back to the provided theme packaged with the most recent 6.1.3 mod and I can only surmise that doing so would resolve this issue.
Final note would be the process one would take to uninstall such custom themes. I've noticed deleting the .xml file from the sd card does remove it from the tweaks menu. However does this procedure ensure deletion of all associated files? Or is there a proper method to ensure complete removal is successfully accomplished?
Any feedback with respect to this particular theme including whether or not it would be necessarily recommended is much appreciated. This wouldn't be my first flash/root/modification or customization of a device. However this is my first Xperia X10. So I do want to make sure I am being as accurate as possible to avoid any future complications.
Thanks for everyones time and attention.
*Although on the plus side I'm able to transfer my contacts from a SIM card directly to the device with this current version of firmware. Such feature was greyed out in the menu initially
the theme probably has a custom gmail apk in it. which is either broken or incompatible with 6.1.3.
try opening wb's 6.1.3 with 7zip and pull the gmail.apk from that rom. copy it to your sd card, then use root explorer to copy it to /system/app. give it the correct permissions and reboot. problem should be fixed.
hello
thanks for your reply. your instructions sounded quite logical and i assumed id have no complications. i copied the app as per your instructions. overwrote the existing entry when prompted. however upon reboot gmail has been removed off the home screen.
attempting a manual install either within the system/app directory or through the sd card returns an unable to install error message.
ive gone ahead and downloaded the gmail app from the market. which thankfully does install. it is functioning and installs successfully to the device.
presumably anyone experiencing this same issue should download the app from the market very strange occurrence indeed.
my only other issue currently is the GPS functionality. switching on the gps displays no indicator within the toolbar. location based services seem not to pick up a location what so ever.
im hopeful this isnt a result of flashing this particular theme. any suggestions?
If you have flashed a framework etc for that theme (using xrec) it won't reverse if you delete that xml file in the sd card.
If you want to go back to original make a copy of that theme xrec and replace its apks with the apks from the ROMs xrec zip. Then flash it.
And if you want to use the theme and also the gmail apk look and feel (theme). Try replacing original gmail apks .png images, which are in drawable-hdpi etc. folders, with the themes gmail apk images.
thesoundofsilence said:
hello
thanks for your reply. your instructions sounded quite logical and i assumed id have no complications. i copied the app as per your instructions. overwrote the existing entry when prompted. however upon reboot gmail has been removed off the home screen.
attempting a manual install either within the system/app directory or through the sd card returns an unable to install error message.
ive gone ahead and downloaded the gmail app from the market. which thankfully does install. it is functioning and installs successfully to the device.
presumably anyone experiencing this same issue should download the app from the market very strange occurrence indeed.
my only other issue currently is the GPS functionality. switching on the gps displays no indicator within the toolbar. location based services seem not to pick up a location what so ever.
im hopeful this isnt a result of flashing this particular theme. any suggestions?
Click to expand...
Click to collapse
after you copied to /system/app, did you change permissions?
the theme may not have a status_gps.png icon or, it's the same color as your status bar.
the app never requested a permission change. upon trying to start originally would just return error.
this was resolved by downloading directly from the market. my only issue now is what to do with the gps connectivity? as it does not seem to be returning a location. the only other thing ive noticed is the default camera app does not zoom.
im trying to assess whether any of this is a result of having changed the theme to the galaxy s cm 6.1 mentioned in the initial post, and how to go about fixing these issues to avoid having to flash back to the original cm6 stock theme.
** GPS has been fixed and is fully functional. Single issue remains with regards to camera not zooming what so ever. Although now attempting an upgrade to CM7. Thanks everyone
Hardware & software
Rooted stock AT&T GS4 (JB 4.2.2).
I have the Xposed framework installed with Wanam and Greenify modules. I recently uninstalled the Nottach module (as the latest Wanam update made Nottach all but redundant IMHO).
I use Apex Launcher.
Things I did prior to having the issue
Updated Wanam module
Updated Apex launcher
Ran an Xposed framework update check (I don't think this did anything)
Changed settings and uninstalled Nottach Xposed
I get a java.OutofMemory bitmap error when attempting to type a message in Hangouts. Video chat and scrolling through contacts works just fine.
Rom Toolbox by JRummy also FCed with this error, but I wasn't using it much so I just uninstalled it.
Apex Launcher seemed to be taking up quite a bit of memory so I unchecked the 'keep in memory box.' That helped a little bit with mem usage, but still getting FCs in Hangouts. The Apex Launcher does not redraw/flicker at all since the last update, but I have noticed a slight lag when opening up drawers. This usually occurs after unlocking the phone and immediately opening up the drawers. It goes away once the drawers get loaded into memory.
Is anyone else experiencing this issue, Hangouts or otherwise?
I assume I will have to wait for a Hangouts update in order to see if the problem is fixed, but I was hoping someone with more knowledge about the force crashing due to out of memory/bitmap error could enlighten me about what causes this problem.
I would go into settings, apps and clear the cache in hangouts and see if that helps.
jd1639 said:
I would go into settings, apps and clear the cache in hangouts and see if that helps.
Click to expand...
Click to collapse
No dice.
I even took the extra step of uninstalling/reinstalling and it still crashes when bringing up the keyboard to type a message.
Here's a snippet from the crash report:
Exception class name: java.lang.OutOfMemoryError
Source file: BitmapFactory.java
Source fileandroid.graphics.BitmapFactory
Source method: nativeDecodeAssist
Line number: -2
Apex crashed on me recently as well but I didn't grab the crash report. I will try to post it if it FCs again.
Google hangouts crashing fix
ashaney said:
Hardware & software
Rooted stock AT&T GS4 (JB 4.2.2).
I have the Xposed framework installed with Wanam and Greenify modules. I recently uninstalled the Nottach module (as the latest Wanam update made Nottach all but redundant IMHO).
I use Apex Launcher.
Things I did prior to having the issue
Updated Wanam module
Updated Apex launcher
Ran an Xposed framework update check (I don't think this did anything)
Changed settings and uninstalled Nottach Xposed
I get a java.OutofMemory bitmap error when attempting to type a message in Hangouts. Video chat and scrolling through contacts works just fine.
Rom Toolbox by JRummy also FCed with this error, but I wasn't using it much so I just uninstalled it.
Apex Launcher seemed to be taking up quite a bit of memory so I unchecked the 'keep in memory box.' That helped a little bit with mem usage, but still getting FCs in Hangouts. The Apex Launcher does not redraw/flicker at all since the last update, but I have noticed a slight lag when opening up drawers. This usually occurs after unlocking the phone and immediately opening up the drawers. It goes away once the drawers get loaded into memory.
Is anyone else experiencing this issue, Hangouts or otherwise?
I assume I will have to wait for a Hangouts update in order to see if the problem is fixed, but I was hoping someone with more knowledge about the force crashing due to out of memory/bitmap error could enlighten me about what causes this problem.
Click to expand...
Click to collapse
What I recommend you is the following...
Part 1
Head over to application manager
Clear cache and data for Google hangouts
Part 2
Use a file explorer and go into your Android folder
Search for any folder that contains anything related to Google Hangouts and delete that or those folders
Part 3
Head over to Google Play store and install Google Hangouts
Part 4
Profit
If you have any other questions regarding this topic, feel free to send me a PM.
:good:
I appreciate the instructions... but that didn't seem to help either. Fwiw, it also crashes with the same error when using root explorer.
Very puzzled atm...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Problem solved! I was afraid something had gotten gunked up and I'd have to factory reset. Luckily that wasn't the case.
I went through and tried enabling/disabling things one by one.
Wanam Xposed was the culprit. I think it causes memory leaks in certain apps. This has been confirmed (by me) with Hangouts, Root Explorer, and Rom Toolbox.
I guess the next step is to email/message the developer. Thanks to all that replied and tried to help.
ashaney said:
Problem solved! I was afraid something had gotten gunked up and I'd have to factory reset. Luckily that wasn't the case.
I went through and tried enabling/disabling things one by one.
Wanam Xposed was the culprit. I think it causes memory leaks in certain apps. This has been confirmed (by me) with Hangouts, Root Explorer, and Rom Toolbox.
I guess the next step is to email/message the developer. Thanks to all that replied and tried to help.
Click to expand...
Click to collapse
Can you reproduce it and post your logcat?
Hangouts crash
I'm having crash problems with my Nexus 4 and Hangouts too, does anybody know what this is? Here the logcat:
09-09 23:19:37.101 I/ActivityManager(1082): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.talk/.SigningInActivity bnds=[368,593][516,757]} from pid 1447
09-09 23:19:37.271 I/ActivityManager(1082): Start proc com.google.android.talk for activity com.google.android.talk/.SigningInActivity: pid=5093 uid=10017 gids={50017, 3003, 1015, 3002, 1028}
09-09 23:19:38.653 I/ActivityManager(1082): Displayed com.google.android.talk/.SigningInActivity: +1s382ms
09-09 23:19:49.113 F/libc (5093): Fatal signal 11 (SIGSEGV) at 0x3f800000 (code=1), thread 5093 (le.android.talk)
09-09 23:19:49.183 I/ActivityManager(1082): Process com.google.android.talk (pid 5093) has died.
09-09 23:19:49.183 I/WindowState(1082): WIN DEATH: Window{41b132f8 u0 com.google.android.talk/com.google.android.talk.SigningInActivity}
09-09 23:19:49.183 W/ActivityManager(1082): Scheduling restart of crashed service com.google.android.talk/com.google.android.apps.babel.realtimechat.RequestWriter in 5000ms
09-09 23:19:49.183 W/ActivityManager(1082): Force removing ActivityRecord{419b3b18 u0 com.google.android.talk/.SigningInActivity}: app died, no saved state
09-09 23:19:55.029 I/Icing.InternalIcingCorporaProvider(2953): Updating corpora: A: com.google.android.talk, C: MAYBE
09-09 23:26:58.778 I/ActivityManager(573): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.talk/.SigningInActivity bnds=[368,593][516,757]} from pid 914
09-09 23:26:58.949 I/ActivityManager(573): Start proc com.google.android.talk for activity com.google.android.talk/.SigningInActivity: pid=4823 uid=10017 gids={50017, 3003, 1015, 3002, 1028}
09-09 23:27:00.290 I/ActivityManager(573): Displayed com.google.android.talk/.SigningInActivity: +1s350ms
09-09 23:27:10.880 I/Icing.InternalIcingCorporaProvider(2989): Updating corpora: A: com.google.android.talk, C: MAYBE
09-09 23:27:13.022 F/libc (4823): Fatal signal 4 (SIGILL) at 0x40479cc4 (code=1), thread 4823 (le.android.talk)
09-09 23:27:13.092 I/ActivityManager(573): Process com.google.android.talk (pid 4823) has died.
09-09 23:27:13.092 I/WindowState(573): WIN DEATH: Window{41f1b6c8 u0 com.google.android.talk/com.google.android.talk.SigningInActivity}
09-09 23:27:13.092 W/ActivityManager(573): Scheduling restart of crashed service com.google.android.talk/com.google.android.apps.babel.realtimechat.RequestWriter in 5000ms
09-09 23:27:13.102 W/ActivityManager(573): Force removing ActivityRecord{41eaec80 u0 com.google.android.talk/.SigningInActivity}: app died, no saved state
I have never had any stable success with CM13 M6.0 ROMs, I always end up with 'System UI Has Stopped' issue which seems to be triggered when installing apps. The error disables the phone, requiring reset or factory reset. Ultimately I really wish someone could explain a fix for this..
For anyone else getting this error;
- Note the app(s) that was just installed
- Reboot to Recovery
- Go to Advanced > File Manager: data/app
- select and delete the app and its sub folders. (can also sort date to see the latest installed)
- reboot and you may be back in action
Hello, I'm having a problem I could not solve even after searching in many forums and video tutorials.
My situation is as follows. Due to technical problems in my Galaxy Y GTS-5310 (it suffered some sort of electric pane that disabled the camera and the input of the headset), I decided to buy a GTS-5360.
The GTS-5310 device was ok to run all applications I used normally, with 4.1.2 Jellyfish. Whenever any updated version of any app was not available on Google Play for some reason (with some exceptions here and there), I've always been able to install it directly through the SD Card.
As I imagined, this new device (with old 2.6.1 Gingerbread) did not recognize the installation of most apps I used (such as Whatsapp, Waze or Instagram). I have managed to install only few of them, like Facebook Lite or Root Browser, and only through the SD Card.
On this new phone, the Google Play Store always shows me a message of incompatible versions (either with Error 492 or simply not making the download button available). Whenever I try to install any of these through SD Card (by downloading the .apk file directly to my computer, be it in Google Chrome or Firefox), then Parse Error appears ("There is a problem parsing this package").
So my first attempt was to use Google Market Helper to change the ROM record as it is viewed by Google Play. However, even changing the version registration of the device to a more upgraded one, this did not work.
The next step was to actually install a new ROM. I have since tried Hyperion 9.0 (2.6), then I try upgrading to Lollipop (4.4), which runs ok, except for installing these apps. As far as I know, the latter should accept the download and installation of most of the apps mentioned above. But whatever I tried, I kept getting the same error messages (Error 492 via Google Market, Parse Error via SD Card).
Since then, some of the suggestions I've followed have not worked either. These include deleting the .android_secure folder from the SD Card, then clearing the cache of processes such as the Google Play Store and Google Framework, as well as clearing the dalvik cache through CWM and rebooting. I did this more than once, but the problem persisted.
I wonder now whether even upgrading the Galaxy Y GTS-5360 to a compatible ROM such as Lollipop is enough for being able to run these applications due to hardware issues.
Thanks in advance for any help!
Hi, galaxy y s5360 just support gingerbread is the reason of pars error when you install higher android apps.
About 492, any notification( log in error or gtalk...)?
Did you tried:
- Turn off device, Delete that folder on computer, then flash the rom again
- log in new gg acc