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 use titanium to backup stock email (both app and Exchange service) and uninstall it.
I restore it later. But unfortunately, I cannot open the Email app.
Here is the exception:
E/AndroidRuntime( 6369): java.lang.RuntimeException: Unable to create application com.android.email.Email: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.android.email.EXCHANGE_INTENT }
Can someone provide those two apk?
Thanks
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.
I have a rooted Nexus 6p, and also installed xposed framework. I did some tweaks and not much.
Now I get a randomly reboot (2-5 times a day) and every time it reboots, ~5% battery is lost...
I have located the exact moment and the logs, but don't have much clue.
HTML:
AndroidRuntime: ****FATAL EXCEPTION IN SYSTEM PROCESS: main
java.lang.NoSuchMethodError: No interface method broadcastIntend(Landroid/app/IapplicationThread; Landroid/content/Intent:Ljava/lang/String:IZZI)I in class Landroid/app/IActivityManager;or its super classes (declaration of 'android.app.IActivityManager' appreas in /system/framwork/framwork.jar)
at ccv.a(SourceFile:64)
at cdk.a(sourceFile:127)
at cdn.run(SourceFile:99)
at android.os.Handler.handleCallback(Hand***
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at com.android.server.SystemServer.run(SystemServer.java.283)
at com.android.server.Systemserver.main(SystemServer.java:168)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.intrenal.os.ZygoteInit.main(ZygoteInit.java:616)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:114)
P.S.I typo all above, forgive if any nonsense errors...
Is that the problem with Xposed?
Do you have Greenify? If so, it's probably the "Use GCM Push for Greenified Apps" option (your logcat looks similar to what my phone showed)
(to clarify, I had to grab a logcat via adb to really see where Greenify was mentioned - maybe I didn't use catlog or syslog correctly at first)
Sent from my Nexus 6P using Tapatalk
Xposed is fine. I get no random reboots. Check which modules ypu are running. Turn them on one at a time.
Sent from my Nexus 6P using Tapatalk
Android 9 pie stock
A2n kernel
Samsung s8 Plus G955FD
Rooted magisk
Everything was fine.
When i downloaded Instagram mod2 , YouTube vanced and spotify "premium" ....
I receive some times in my screen this message:
Error: java.lang.nullpointerException:
Attempt to invoke virtual method 'int java.io.inputStream.read(bytes[])' on a null object reference
Well, this error is from one of that apps
But, all apps Works fine.
Have i any option to disable this error message?
Found the problem:
The App Instagram mod 2 , version april 10th has a bug.