Database Users

[Q] No install after defrosting

I froze a bunch of crapware on my Atrix. Later I was looking for the sound recorder but it was nowhere. TB couldn't find it either. Then I noticed a few of the apps I had frozen were no longer available to TB. Now I did a factory reset in between.
Could that screw up that apps that are "frozen"? What does TB do when freezing the apps? Is it easy to revert that process manually? I am kind of hosed here.

Yea... when skmmething goes wrong you shouldn't just blindly factory reset man, you're going to screw yourself over.
The files were changed when you froze them, making them invisible to the system (er launcher for that matter).
When you reset, I'm assuming TB was removed, and the files are still gone; the system checks for those files and since it can't find them, it is having problems.
I would say to flash back to the stock ROM and start over.
Sent from my Nexus One using XDA Premium App

I had to reset the phone because it lost my google login info and i couldn't see contacts. I couldn't add contacts either.
TB and its data were stored on the SD so when I reinstalled TB from market it could see the backed up stuff, etc.. Seems like it forgot what it had frozen.
Can one manually unfreeze?
And where can I find the stock ROM to reflash?

Yea you can unfreeze by going back into the application and just hitting unfreeze rather than freezing like before.
Now I don't know where you could get a stock ROM; check around on the Android Dev forum and see what you can find.
Sent from my Nexus One using XDA Premium App

they're not in the defrost list

gdanko said:
they're not in the defrost list
Click to expand...
Click to collapse
did you make sure to have cleared the filters D: .. maybe your filters had it set to hide frozen apps.. D:

Sadly not. In fact, to test something I did the following...
[localhost app]# ls -l vlingo-1.9.5-release-moto.apk
-rw-r--r-- 1 root root 3575093 Feb 5 01:21 vlingo-1.9.5-release-moto.apk
[localhost app]# md5sum vlingo-1.9.5-release-moto.apk
620e8e5df056507a038da706adfc92ca vlingo-1.9.5-release-moto.apk
Freeze Vlingo via TB
[localhost app]# ls -l vlingo-1.9.5-release-moto.apk
-rw-r--r-- 1 root root 3575093 Feb 5 01:21 vlingo-1.9.5-release-moto.apk
[localhost app]# md5sum vlingo-1.9.5-release-moto.apk
620e8e5df056507a038da706adfc92ca vlingo-1.9.5-release-moto.apk
[localhost app]#
The apk has not changed at all. What does Titanium Backup do when "freezing"? I verified Vlingo is now hidden.

hmmm .. have you tried checking out the TiBu website for assistance X-x?
http://matrixrewriter.com/android/
This was for people who had issues freezing an app.. but maybe it can help you D:
Open Titanium, then Preferences. Scroll down to App processing mode, and check the second radio button "AUTO, Indirect"

Well the FAQ says frozen apps will be defrosted on factory reset.

you know.. i don't think i ever had a sound recorder app .. but TiBu recognizes it.. though ther's no app for it..

darkamikaze said:
hmmm .. have you tried checking out the TiBu website for assistance X-x?
http://matrixrewriter.com/android/
This was for people who had issues freezing an app.. but maybe it can help you D:
Open Titanium, then Preferences. Scroll down to App processing mode, and check the second radio button "AUTO, Indirect"
Click to expand...
Click to collapse
Well I tried the AUTO, Indirect but that did not help restore the problem apps. Someone hinted TiBu merely renames the apk to something like apk.bak but that isn't the case, either.
I ran a test; checked md5sum for an app before and after a freeze/reboot. The md5sum was the same. The file is not modified in any way. So the question remains, what does TiBu do to "freeze" an item?

This is what logcat shows when I freeze something:
03-22 06:25:13.529 1502 1508 I ActivityManager: Force stopping package com.amazon.mShop.android uid=10129
03-22 06:25:13.549 4975 4975 D HomeLoaders: application intent received: android.intent.action.PACKAGE_CHANGED, replacing=false
03-22 06:25:13.549 4975 4975 D HomeLoaders: --> package:com.amazon.mShop.android
03-22 06:25:13.549 4975 4975 D HomeLoaders: --> sync package com.amazon.mShop.android
03-22 06:25:13.589 3355 3355 I class com.keramidas.TitaniumBackup.c.k: App enable/disable activity has finished ! (resultCode = 0)
03-22 06:25:13.599 4818 4818 D AndroidRuntime: Shutting down VM
03-22 06:25:13.609 3355 3355 D com.keramidas.TitaniumBackup.j.d: onStop()
03-22 06:25:13.609 1502 2279 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
03-22 06:25:13.629 4818 4828 D jdwp : adbd disconnected
03-22 06:25:13.679 3355 3355 I [email protected]: List refreshed

Fixing permissions, zipaligning, and bug report

Tried fixing permissions using jrummy busy box installer and it just keeps running. Waited 10min and it was still going. What are you guys doing to fix permissions? Also tried running the zipalign script and get an error for missing binary? Any idea about this? Last.....kept seeing this bug report thing fly up every now and then. Finally found where the .txt reports were being saved and they were all the same error, system/bin/stagefright? Bug report attached, any help is greatly appreciated. Been running faux123 008 test kernel, stock rooted ROM.

Missing stagefright
gokart2 said:
Tried fixing permissions using jrummy busy box installer and it just keeps running. Waited 10min and it was still going. What are you guys doing to fix permissions? Also tried running the zipalign script and get an error for missing binary? Any idea about this? Last.....kept seeing this bug report thing fly up every now and then. Finally found where the .txt reports were being saved and they were all the same error, system/bin/stagefright? Bug report attached, any help is greatly appreciated. Been running faux123 008 test kernel, stock rooted ROM.
Click to expand...
Click to collapse
I started seeing these bugreports when I "upgraded" to 4.2.2 on my stock rooted N7. From what I can tell stagefright is some kind of audio/video/picture rendering engine. I became aware of the reports when I started getting random popups for "complete action using...". I finally selected the gmail app and saw that the bugreport as well as a screen shot were attached to the email. I actually got a copy of stagefright from a friend that had it on a different device and installed it. The bugreports kept happening only this time I was getting this error:
NvAvpOpen: Error opening nvavp device (Permission denied)
I've hit a brick wall with this error. Did you ever get anywhere with the stagefright error?

I have figured out a few more things... If you have developer options (and maybe USB debugging) turned on, pressing power/volume up/volume down will generate a bugreport via /system/bin/bugmailer.sh. Bugmailer then calls /system/bin/dumpstate which in turn calls stagefright to play a sound. So the invocation of stagefright didn't cause the bugreport, it is a result of the report. So if you want to stop this whole nonsense, just edit bugmailer.sh and add "exit 0" as the second line.
Sent from my Nexus 7 using xda app-developers app

[Q] Problems with Google Hangouts - Force Crashes

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

[Stock] MIUI 10.2.2 - Help needed with *alarm* WAKE_LOCK

I have a Redmi 3s Prime (32GB / 3GB RAM) device with stock MIUI 10.2.2 Global version. The device was working smooth, but recently started to fully drain battery within ~24 hours. Managed to find out the CPU is not going to deep_sleep at all, because there is a WAKE_LOCK is held.
Since the device wasn't rooted, I couldn't investigate the problem deeply, so I did:
Unlocked bootloader
Flashed TWRP
Flashed Magisk 20.1
Using Termux shell, the
Code:
dumpsys power
shows the *alarm* PARTIAL_WAKE_LOCK is held by the system_server. I did the following to try to fix the issue:
Rebooted the device several times
Cleared cache via recovery
Cleared dalvik-cache
Cleared data of andorid.apk (I belive its the system_server)
Tried denying the WAKE_LOCK permission via appops command
Tried revoking WAKE_LOCK permission via pm command
Tried force-killing the system_server process
Tried enabling power_saving_mode
Tried removing all bloatwares from /system and /data
Other behaviours I have observed:
The *alarm* WAKE_LOCK only held only after few hours of system boot
wifi or data connection states doesn't affects the WAKE_LOCK problem
Once the WAKE_LOCK is held, it won't get releaded until reboot or killing system_server process
If I revoke/deny WAKE_LOCK permission, it gets restored automatically after few minutes
I know, a full wipe will definitely fix the issue. But, I need your help to fix the issue.

UPDATE 1#: I have read somewhere that the location polling may keep a wake_lock via system_server process (UID 1000). I have tried disabling the location access and rebooted. But the wake_lock is still persists.

[ERROR] java.lang.nullpointerException

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.