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.
I have a Chinese version of the ThinkPad Tablet (A310). I was able to root the device and get the CWR (as ROW) on it, but the only problem remains: Google Apps. Since most of the Chinese tablets and phones come without the Google Apps, I have installed these from Cyanogen website. Talk and Maps work, but Gmail does not and crashes with the message:
E/AndroidRuntime( 729): FATAL EXCEPTION: main
E/AndroidRuntime( 729): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gm/com.google.android.gm.ConversationListActivity}: java.lang.IllegalStateException: missing setting: clientId
Anyone have an idea?
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
During my time while hangouts was working, I tried to use the Xposed SMS mod that added a "quick reply' menu for replying. While attempting to get it to work, I pressed "Uninstall updates" with hangouts and managed to break the online portion of hangouts, preventing me from signing in with it. Specifically after a short period of "signing in", it would flash a "Couldn't sign in because we couldn't reach Google. Try Again." on the 2.1 APK version. For the material-styled v2.3 version that just released it's just stuck in a infinite loop for "Signing In". While trying to debug the issue I came across this ADB error printed that says "V/GCM﹕ not posting request to register com.google.android.talk because of backoff period." Fiddling with the "clear cache/data" option reposts that log. I already reflashed Gapps, turned on/off exposed, and reset as much data pertaining to the other gapps(gmail, gplay etc. work fine), and tried diffrent version of the app out. No solution currently works. I'm currently on the Alliance Rom, with root & xposed(currently disabled).
another log entry:
"[avd][avd] Permission for com.google.android.talk to access oauth2:https://www.googleapis.com/auth/chat https://www.googleapis.com/auth/plus.me https://www.googleapis.com/auth/hangouts https://www.googleapis.com/auth/chat.native will be managed locally."
consistenly afterwards I also noticed a "GCM registration failed" notice.
specific order:
1"register - retrying gcm registration:Redacted-21"
2"Implicit intents with startService are not safe: Intent { act=com.google.android.c2dm.intent.REGISTER (has extras) } android.content.ContextWrapper.startService:506 com.google.android.apps.babel.realtimechat.GcmIntentService.xS:295 com.google.android.apps.babel.realtimechat.x.ya:401"
3."I/GCM﹕GCM config loaded"
4."V/GCM﹕not posting request to register com.google.android.talk because of backoff period"
5."I/Babel: [GcmIntentService] gcm error: SERVICE_NOT_AVAILABLE"
6. "E/Babel﹕ Gcm registration failed"
7."D/CMASMessage﹕ [update] mShowingCMASText is false" *repeats multiple times*
Did you fixed it? Im also stuck at signing in in my s4 running Dan's cm11 m9 stock kernel.
Nope.not seems to be related to GCM which handles communications. Flashing a new GAPPS package may fix it if your try that.
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.