Scoop: Catches a stack trace when an app crashes unexpectedly
This module - as the description says - saves the stack trace of a crashing app and displays all crashes in a list so you don't have to look through a long logcat anymore. Additionally you get a notification on every crash (configurable) which already displays the most important information.
This module is based off the module Cracker which sadly isn't being developed anymore so I made an updated version which catches crashes more reliably (supports custom crash handlers set by apps), features material design and contains more functionality such as:
Search in crashed apps
Search in stack trace
Crash preview in notification
Combination of same crashes / apps to avoid long repetetive lists
Crash blacklist
Quick actions to copy / share a stack trace
Download: http://repo.xposed.info/module/tk.wasdennnoch.scoop
Source: https://github.com/wasdennnoch/Scoop
You can help translate this module on GitHub!
Changelog:
1.6.4
Make app search case-insensitive
Use separate view to select text
1.6.3
Add button to toggle selection mode (to avoid a bug where you can't scroll anymore)
1.6.2
Make stack trace selectable
1.6.1
Portugese (BR) and German translation
Option to force English language
1.6.0
Add option to sort crashes by apps
Fix long app names and crash date overlapping
1.5.0
Add option to selectively delete crashes
Add blacklist to filter out crashes from specific apps
Add about screen
1.4.2
Fix nothing working at all. Sorry for the many versions, but I don't have a device to test the Xposed part anymore (I updated to Nougat) and also this is the first time I enabled ProGurad in an Xposed module.
1.4.1
Completely disable module not activated warning as something seems to be broken
1.4.0
Add compatibility with ancient Xposed versions (52)
Add search to overview
Add option to combine same crashes into one item
1.3.2
Fix constant module deactivated warning again
1.3.1
Fix constant module disabled warning
Fix crash when opening detail view
1.3.0
Add option to limit line width
Add search function to detail view
1.2.0
Added Copy/Share buttons to notification (configurable)
Added module not activated "warning"
Improved stack trace preview in notification
Directly open crash details from notification
Minor fixes and improvements (duh)
1.1.0
Fix devious face
Fix self-crash when catching custom throwable subclasses
Minor fixes
1.0.0
Initial release
Click to expand...
Click to collapse
XDA:DevDB Information
Scoop, Xposed for all devices (see above for details)
Contributors
MrWasdennnoch
Source Code: https://github.com/wasdennnoch/Scoop
Xposed Package Name: tk.wasdennnoch.scoop
Version Information
Status: Stable
Current Stable Version: 1.6.4
Stable Release Date: 2017-04-01
Created 2016-12-23
Last Updated 2017-04-01
Amazing, thanks for this Christmas gift
Could you add line break and search in log? Thank you!
KaMyKaSii said:
Could you add line break and search in log? Thank you!
Click to expand...
Click to collapse
Done and available in v1.3.0
(Disabled by default)
MrWasdennnoch said:
Done and available in v1.3.0
(Disabled by default)
Click to expand...
Click to collapse
Thank you. I upgraded from version 1.1.0 to 1.3.0 and now it says I do not have Xposed installed. I've restarted, cleaned up data, reinstalled, same thing. Before clearing the data, by clicking on the crash log of another app, Scoop also crash. Attached are the logs logs
Word wrap is very appreciated!
Version 1.2 and 1.3 does't work on n910f (note 4) running marshmallow 6.0.1
Definitely a good upgrade from the good Cracker.
I have an old S3 on 4.1.2 (that i use for debugging) with xposed version 54, could this beatiful tool work on xposed version lower than 81 like Cracker?
KaMyKaSii said:
Thank you. I upgraded from version 1.1.0 to 1.3.0 and now it says I do not have Xposed installed. I've restarted, cleaned up data, reinstalled, same thing. Before clearing the data, by clicking on the crash log of another app, Scoop also crash. Attached are the logs logs
Click to expand...
Click to collapse
I fixed the warning (yet have to push it), but I need a logcat to resolve the crash. Your one unfortunately didn't contain any crash info. Make sure to capture it during the crash (because the module doesn't always catch itself ).
MrWasdennnoch said:
I fixed the warning (yet have to push it), but I need a logcat to resolve the crash. Your one unfortunately didn't contain any crash info. Make sure to capture it during the crash (because the module doesn't always catch itself ).
Click to expand...
Click to collapse
I took it with the Logcat Extreme app, I hope to be enough. I configured it as verbose, fresh log, main, brief. Let me know if you have any better. You said that Scoop does not log its own crash logs, but actually once here it happened, before clearing Scoop data
KaMyKaSii said:
I took it with the Logcat Extreme app, I hope to be enough. I configured it as verbose, fresh log, main, brief. Let me know if you have any better. You said that Scoop does not log its own crash logs, but actually once here it happened, before clearing Scoop data
Click to expand...
Click to collapse
I said "not always"
I fixed it in v1.3.1. The fault was a misconfigured Proguard which removed more than it should have. I enabled Proguard for debug builds to avoid such issues in the future.
MrWasdennnoch said:
I said "not always"
I fixed it in v1.3.1. The fault was a misconfigured Proguard which removed more than it should have. I enabled Proguard for debug builds to avoid such issues in the future.
Click to expand...
Click to collapse
No more crashes, but the notification that Xposed is not installed persists. I updated the module, cleaned data and rebooted
Edit: Looking at this screenshot I recommend future features like search in the main screen, grouping of same app logs and individual exclusion
KaMyKaSii said:
No more crashes, but the notification that Xposed is not installed persists. I updated the module, cleaned data and rebooted
Looking at this screenshot I recommend future features like search in the main screen, grouping of same app logs and individual exclusion
Click to expand...
Click to collapse
Now it should be fixed. Problem is I can't test it because I updated to N and thus don't have Xposed anymore, so I had to try different ways. And of course it was Proguard again.
I'll add the search soon, I thought of only searching for different apps though and not searchin the short description. Not sure how I should approach the grouping but it's possible too. With exclusion you basically mean blacklisting?
Xposed bridge version
Xposed installer tells me that I need Xposed bridge version 81. There are no updates for the XPosed bridge for me and the current version is 54, so I think that's a bug.
Fabian R�ling said:
Xposed installer tells me that I need Xposed bridge version 81. There are no updates for the XPosed bridge for me and the current version is 54, so I think that's a bug.
Click to expand...
Click to collapse
The newest available version is 87, but I just remembered: 81 isn't available below LP, right? I'll fix that in the next release.
EDIT: Compatibility down to 52 added in v1.4.0
Compatibility down to 52 is very good, thanks.
The problem is in the image below
Only version 1.1 works for me (n910f note 4 running marshmallow 6.0.1)
The bug of not having Xposed installed continues, but the app continues to intercept the crashes normally
MarioUnoDueTre said:
The problem is in the image below
Click to expand...
Click to collapse
KaMyKaSii said:
The bug of not having Xposed installed continues, but the app continues to intercept the crashes normally
Click to expand...
Click to collapse
That's really weird, it hould be working. I completely disabled the warning and will have a look again when Xposed for N is available.
MrWasdennnoch said:
That's really weird, it hould be working. I completely disabled the warning and will have a look again when Xposed for N is available.
Click to expand...
Click to collapse
I reported with version 1.3.2, although you talk about version 1.4.0, it was not available when I opened the Xposed Installer. I will update now
Edit: The new version is not working, no crash is being logged
KaMyKaSii said:
I reported with version 1.3.2, although you talk about version 1.4.0, it was not available when I opened the Xposed Installer. I will update now
Edit: The new version is not working, no crash is being logged
Click to expand...
Click to collapse
1.4.2 should fix it... Really bad that I can't test it myself, it could've avoided many issues. But hey, at least I now know how to configure ProGuard properly. At least I hope so.
MrWasdennnoch said:
1.4.2 should fix it... Really bad that I can't test it myself, it could've avoided many issues. But hey, at least I now know how to configure ProGuard properly. At least I hope so.
Click to expand...
Click to collapse
Thanks, now it's working. Can you explain to me how the grouping that you implemented works? When I suggested, I wanted to say that after clicking on the crash group of the app, a list of all the crashs with information like date and time appears, and that they expand in the full log when they are clicked. And about the deletion, I'm talking about a button to clear any individual log after a long click on it. At this time it is only possible to clear all logs at once
Yes!
1.4.2 is working; good job, thanks a lot.
Related
IMPORTANT ANNOUNCEMENT
Click here
Keepchat
Save your Snapchats and Stories automatically
Credits go to @sturmen who invented this mod and to @stammler for his previous updates and of course to @rovo89 for making the Xposed Framework.
Lastly a special thanks to @jbergler for helping to keep this mod updated.
Note: @stammler transferred the project to me, see the old and initial thread.
This Xposed module saves all images and videos upon opening to the specified folder on your SD card. It uses the Xposed framework to hook into the Snapchat app and do the magic. Because it uses the Xposed framework, it is device and rom independent .
YOU MUST HAVE XPOSED FRAMEWORK INSTALLED FOR THIS TO WORK
If you find any bugs, please report
Confirmed to work with Snapchat 5.0.38.2 (version 5.0.38.1 was not tested.) and above(21/10/2014)
Newer versions may or may not work. Try it.
Features
Recieved Snaps are saved when viewed
Stories are saved when viewed
Sent Snaps are saved automatically
Does not report as Screenshotted
Installation
Install the awesome Xposed framework on your rooted device.
Uninstall any 2.x version of KeepChat.
Install and activate the mod, which you can download from the Xposed Framework App or from here.
Reboot your device to start the mod.
To Do
Give me Ideas
Changelog
3.6.3
- fixed support for snapchat 5.0.38.2
3.6.2
- support for latest snapchat 5.0.38.2
3.6
- bug fix
3.5.9
- added support for the 5.0.34.4
3.5.7
- small bug fix
3.5.5
- updated to support 5.0.32.1 and above
3.5.2
- support for 5.0.27.1 added
3.5
- removed support for older versions
- only works with the current stable ( 5.0.23.0 )
- included google analytics
3.2.3
- added support for the latest beta 4.1.13
3.2.2
- added support for the latest beta 4.1.12 and 4.1.11
3.2
- added support for the latest beta 4.1.11
- made a few changes with how settings work and it should fix the problems people have
3.1.8
- disabled support for saving sent snaps for these three beta (4.1.08, 4.1.09 and 4.1.09) due to major changes in snapchat code
- added new setting to save snaps into sub-folders by user name
3.1.7
- fixed small bug introduced by last version
- also trying a potential fix for the settings not being applied error
3.1.6
- added support for latest snapchat beta 4.1.07 and 4.1.07 Stable
3.1.5
- added support for latest snapchat beta 4.1.06
3.1.4
- added support for 4.1.05 including the beta
3.1.2
- added support for the latest Stable 4.1.03
- fixed a major bug for older versions of snapchat
3.1.1
- added support for the latest beta 4.1.03
3.1
- added support for all snapchat version 4.1.01 Beta and below. (Includes the 4.1.01 stable)
- fixed a bug with settings
- fixed a bug with the dialog boxes
3.0.4 Beta
- hopefully fixed getting reported bug for stories
- works with 4.0.22 Beta now
3.0.2
- fixed bug that caused Errors 1, 2, 3
- added new setting for sorting images into folder
- little changes to make logs better
3.0.1
- Small update to the debugging code (no need to update really unless you want to help debug errors)
3.0 Settings added!
- Initail Release
Here are my sources GitRepo. This software is released under the GNU GPLv3.
Cheers and enjoy!
FAQS
Settings not being applied?
Try these in order after you have set your settings
- Force Close snapchat and try again
- Restart
And lastly if it still doesn't work it means there is something wrong with your phone and the best solution is below.
- Convert snapchat into a system app. Currently the best solution in my opinion.
Have a problem?
Submit a bug report. (see below)
I WILL NOT BE REPLYING TO PRIVATE MESSAGES ABOUT KEEPCHAT. POST HERE IF YOU NEED HELP.
Bugs
- none
BUG REPORTS
Ok there are two things I need if you want me to read it.
1. LOG (see below on how to get it)
2. A description of the problem and how to reproduce it.
Getting log
By default keepchat does not print to the log.
Enable Log
- Open Keepchat settings
- Tick Debug Mode (i.e. turn it on)
Turn off other Mods.
Restart
Open Snapchat
Reproduce the error
Get the log
Upload only the revelant part of the log
- Only upload the part after the ----KEEPCHAT STARTED---- Block
- All of Keepchats logs come in blocks. So remove other entries that are not keepchat related.
So is this new v3.0 basically the same as v2.1-rc5?
NickSaul said:
So is this new v3.0 basically the same as v2.1-rc5?
Click to expand...
Click to collapse
Its basically the same, except for these two main differences.
- Lets you save sent snaps
- Lets you choose the folder where everything is saved
Other than that there are just some small bugs that have been fixed.
(and a settings page )
Woohoo I can resend snaps now lol pretty much the only feature I wanted/needed thanks TheRamis
Sent from my Evo 3D CDMA using Tapatalk 4
TheRamis said:
Its basically the same, except for these two main differences.
- Lets you save sent snaps
- Lets you choose the folder where everything is saved
Other than that there are just some small bugs that have been fixed.
(and a settings page )
Click to expand...
Click to collapse
Sounds great. Thanks!
Fantastic! Sometimes I forget what I've said in previous snaps.
Is there still the issue with stories getting reported?
Sent from my EVO using xda premium
Getting an error on 4.0.21 with the latest (3.0) of Keepchat. In the logs it says the module has loaded and I've uninstalled rc5 (which worked perfectly). Problem is, when I open a snap it says "image cannot be saved. Error 1." or something very close to that in a toast. Looking at the logs nothing is happening after the module loads on boot. No recognizing that Snapchat has launched, no loading my settings, nothing. There is nothing in the log from Keepchat besides the module being loaded like any other.
amf66 said:
Getting an error on 4.0.21 with the latest (3.0) of Keepchat. In the logs it says the module has loaded and I've uninstalled rc5 (which worked perfectly). Problem is, when I open a snap it says "image cannot be saved. Error 1." or something very close to that in a toast. Looking at the logs nothing is happening after the module loads on boot. No recognizing that Snapchat has launched, no loading my settings, nothing. There is nothing in the log from Keepchat besides the module being loaded like any other.
Click to expand...
Click to collapse
Hmm I had that issue. Just delete the keepchat folder. And try again. I disabled all writing to log unless debug is turned on.
Xposed repository is updated, remember to uninstall 2.x manually.
amf66 said:
Getting an error on 4.0.21 with the latest (3.0) of Keepchat. In the logs it says the module has loaded and I've uninstalled rc5 (which worked perfectly). Problem is, when I open a snap it says "image cannot be saved. Error 1." or something very close to that in a toast. Looking at the logs nothing is happening after the module loads on boot. No recognizing that Snapchat has launched, no loading my settings, nothing. There is nothing in the log from Keepchat besides the module being loaded like any other.
Click to expand...
Click to collapse
Haha, reverted back to rc5, rebooted, and you had already replied. I'll try deleting the directory and see what happens.
Edit: made a new empty directory and changed the save location to this folder and it works now. Any insight on why it wouldn't work OK the folder I had been using before?
amf66 said:
Haha, reverted back to rc5, rebooted, and you had already replied. I'll try deleting the directory and see what happens.
Edit: made a new empty directory and changed the save location to this folder and it works now. Any insight on why it wouldn't work OK the folder I had been using before?
Click to expand...
Click to collapse
Nope I wasn't able to reproduce it after the first time I had it. So just assumed it was something random
In response to your reply on other thread, thank you for your reply and take as long as you need to fix the module would just be nice to have the ability again
Sent from my HTC One mini using XDA Premium 4 mobile app
Are stories still getting reported as screenshot?
November13 said:
Are stories still getting reported as screenshot?
Click to expand...
Click to collapse
So far I haven't had any reports of it happening yet again it's still early days
Sent from my HTC One mini using XDA Premium 4 mobile app
November13 said:
Are stories still getting reported as screenshot?
Click to expand...
Click to collapse
I have personally never had problems with stories. But there are a few new hooks that should completely stop that. Of course only time will tell.
Getting errors with v3 saying cannot be saved:error1
Edit: about to flash my phone (not due to this btw) and will retry, will report results
Sent from my HTC One mini using XDA Premium 4 mobile app
CONdemmedNORmal said:
Getting errors with v3 saying cannot be saved:error1
Edit: about to flash my phone (not due to this btw) and will retry, will report results
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Great. Mind doing some debugging for me?
EDIT: could you please use the newer version if you want to help debug? and then once the error occurs please submit a bug report using the instructions in second post
TheRamis said:
Great. Mind doing some debugging for me?
Click to expand...
Click to collapse
Right that's odd, got the errors when rc5 was uninstalled and v3 installed but tried again with rc5 installed again but unselected and it's now working??????
Going to re uninstall rc5 to see what happens
Sent from my HTC One mini using XDA Premium 4 mobile app
For anyone who is an avid user of Handcent, the most recent update introduced ads at the top of the message list, effectively "disguised" as the first message in your inbox.
While Handcent has had ads for quite some time, the placement of this particular ad has caused an uproar in the feedback section of the Play Store, and rightfully so.
As a developer, I understand the need for ads to support development (and as such, do not use ad blockers), but this particular style of ad is a bit distasteful for most, requiring not the purchase of a paid version to remove, but rather, an annual ongoing subscription.
So, I first set out to modify the app directly, to see if I could remove JUST this ad, and once I figured it out, figured it made more sense to create as an Xposed module, so that you can continue to receive app updates should they decide to change things. Again, this leaves any other ads (that were already there) untouched. A general ad blocker may or may not address this, but I am not sure, since, as mentioned, I do not use them.
As with all Xposed modules --> install the linked APK --> make the module active --> reboot --> profit.
Note: This module has no front-end UI, so there is nothing to do but install and make active.
Thanks to Rovo89, et al, for the amazing framework.
Download Link --> Xposed Repository - v1.5.1
EDIT: 01-Apr-2015 --> Original Release (v1.0)
EDIT: 02-Apr-2015 --> Updated version for KitKat compatibility (v1.1)
EDIT: 03-Apr-2015 --> Updated version for compatibility with Handcent 6.5.1 (v1.2)
EDIT: 29-Apr-2015 --> Updated version for compatibility with Handcent 6.5.5 (v1.3)
EDIT: 15-May-2015 --> Updated version for compatibility with Handcent 6.5.7 (v1.4)
EDIT: 27-May-2015 --> Updated version for compatibility with Handcent 6.5.9 (v1.5)
EDIT: 31-May-2015 --> Minor update (v1.5.1)
Great idea but the AD keeps popping back up after awhile. But then handcent did update today. So maybe that's why.
DevXen said:
Great idea but the AD keeps popping back up after awhile. But then handcent did update today. So maybe that's why.
Click to expand...
Click to collapse
Hmm, no, I'm on the latest version (6.5) available to me and all running well for the last 48 hours. What version of Android are you running (I'm on LP 5.0.1).
If after installing and rebooting, check to see the module successfully loaded via the Xposed Logs. If so, then a logcat would help during the opening of Handcent. You can send me a PM if you're interested, and I can provide some debug code to use for more verbose logging / output as well.
I'm on Kitkat 4.4.4 - Note Edge - Sprint.
I'm not sure about getting the logcat as he never done that. But I'd assume that would only be good when it actually shows the ad at the top. Which seems to be at least at this point to be random. It's not always there. But sometimes it is.
DevXen said:
I'm on Kitkat 4.4.4 - Note Edge - Sprint.
I'm not sure about getting the logcat as he never done that. But I'd assume that would only be good when it actually shows the ad at the top. Which seems to be at least at this point to be random. It's not always there. But sometimes it is.
Click to expand...
Click to collapse
A logcat would be useful regardless, as when you launch the app and/or navigate in / out of the inbox, it would show any errors the Xposed module may be having in hooking the correct method that gets called. The behavior you are describing is the default / stock behavior they have implemented, which means the module, for you, is not functioning at all.
I may restore KK to my phone this evening to try and test as well.
Also, if you want to test to compare if the issue is related to Xposed, or the mod itself, while on KK, attached is the original Handcent APK I modified while working to determine how to pull this off.
To test, you would need to uninstall your current version of Handcent, as this will not install over top.
If you no longer see the ad in the inbox stream, it would isolate the issue as being related to Xposed on KK versus LP.
EDIT: APK removed as test confirmed issue was with module.
I'm on 4.4 and having the same issue. I tried your apk and the ad disappeared; I then reinstalled from the market and the ad stayed gone until I force closed it and reopened. I'll try to get a logcat when I have a moment.
Sent from my SCH-I535 using XDA Free mobile app
Demonius_Jackson said:
I'm on 4.4 and having the same issue. I tried your apk and the ad disappeared; I then reinstalled from the market and the ad stayed gone until I force closed it and reopened. I'll try to get a logcat when I have a moment.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Perfect, thanks for checking. So this does confirm the technique is good on KK as well, but the module is, for some reason, not hooking correctly to replicate the direct mod.
Also, even before a logcat, can you post the output of your Xposed log when the phone starts up? This will show if the module is successfully loading in the first place.
Thanks.
I hadn't posted previously, but I'm experiencing the same thing. It worked for a bit, then stopped working.
my xposed log shows the following, but I'm always open to the possibility I'm doing something wrong
Code:
Apr 2, 2015 8:24:45 PM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KTU84P release-keys' with fingerprint 'htc/sprint_wwe/htc_m8whl:4.4.4/KTU84P/393205.2:user/release-keys'
Loading modules from /data/app/ca.pr0ps.xposed.entrustunblocker-1.apk
Loading class ca.pr0ps.xposed.entrustunblocker.Unblocker
Loading modules from /data/app/com.elesbb.snapchatfullcaption-1.apk
Loading class com.elesbb.snapchatfullcaption.Xposed
Loading modules from /data/app/com.logika.noinboxads-1.apk
Loading class com.logika.noinboxads.MainActivity
java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation
at dalvik.system.DexFile.defineClassNative(Native Method)
at dalvik.system.DexFile.defineClass(DexFile.java:222)
at dalvik.system.DexFile.loadClassBinaryName(DexFile.java:215)
at dalvik.system.DexPathList.findClass(DexPathList.java:322)
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:54)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
at de.robv.android.xposed.XposedBridge.loadModule(XposedBridge.java:421)
at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:386)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:120)
at dalvik.system.NativeStart.main(Native Method)
ffttgghh said:
I hadn't posted previously, but I'm experiencing the same thing. It worked for a bit, then stopped working.
Click to expand...
Click to collapse
That's the standard behavior, meaning the module isn't working at all on KK.
ffttgghh said:
my xposed log shows the following, but I'm always open to the possibility I'm doing something wrong
Code:
Apr 2, 2015 8:24:45 PM UTC
Loading Xposed v54 (for Zygote)...
Loading modules from /data/app/com.logika.noinboxads-1.apk
Loading class com.logika.noinboxads.MainActivity
java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation
at dalvik.system.DexFile.defineClassNative(Native Method)
at dalvik.system.DexFile.defineClass(DexFile.java:222)
at dalvik.system.DexFile.loadClassBinaryName(DexFile.java:215)
at dalvik.system.DexPathList.findClass(DexPathList.java:322)
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:54)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
at de.robv.android.xposed.XposedBridge.loadModule(XposedBridge.java:421)
at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:386)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:120)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
That's the error. It is failing to load all together on the KK version of Xposed. Need to investigate further. Thanks for the logs.
KK Test Build
Okay, KK users, please give the attached test build a try and let me know if it works for you (be sure to first uninstall the current xposed module before installing the attached). The issue should hopefully be fixed.
Once confirmed, I will upload a new version compatible with both KK & LP to the Xposed repository for re-download / installation.
Confirmed. Attachment removed, OP updated with link to new version in Xposed repository.
JsChiSurf said:
Okay, KK users, please give the attached test build a try and let me know if it works for you (be sure to first uninstall the current xposed module before installing the attached). The issue should hopefully be fixed.
Once confirmed, I will upload a new version compatible with both KK & LP to the Xposed repository for re-download / installation.
Click to expand...
Click to collapse
tried it, works fine, no ads, no ads after reboot, no errors in xposed log!
ffttgghh said:
tried it, works fine, no ads, no ads after reboot, no errors in xposed log!
Click to expand...
Click to collapse
Great. Link in OP has been updated to point to updated version (v1.1) in Xposed repo.
JsChiSurf said:
Great. Link in OP has been updated to point to updated version (v1.1) in Xposed repo.
Click to expand...
Click to collapse
Working like a champ now, thanks.
Sent from my SCH-I535 using XDA Free mobile app
Demonius_Jackson said:
Working like a champ now, thanks.
Click to expand...
Click to collapse
Great. Thanks for the confirmation.
Fyi... Handcent just updated again in Google Play to 6.5.1 and it appears to break the functionality of the module (perhaps intended). I had to revert to the last version (6.5.0) in order to get the module working again. Just informing...
PerCompLLC said:
Fyi... Handcent just updated again in Google Play to 6.5.1 and it appears to break the functionality of the module (perhaps intended). I had to revert to the last version (6.5.0) in order to get the module working again. Just informing...
Click to expand...
Click to collapse
That was fast. Thanks for the heads up. Just enough changed to affect functionality. OP has been updated with new version for compatibility with v6.5.1.
Note: New version of module will break backwards compatibility, so do not update module unless updating Handcent as well.
JsChiSurf said:
That was fast. Thanks for the heads up. Just enough changed to affect functionality. OP has been updated with new version for compatibility with v6.5.1.
Note: New version of module will break backwards compatibility, so do not update module unless updating Handcent as well.
Click to expand...
Click to collapse
Thank you so much for the quick response and fix! Works perfectly!
I have yet to update Handcent to 6.5.x cause of this new ad placement (Still on v6.4.9). Might have to update and give this a go. Huge thanks for this!
Hippie459MN said:
I have yet to update Handcent to 6.5.x cause of this new ad placement (Still on v6.4.9). Might have to update and give this a go. Huge thanks for this!
Click to expand...
Click to collapse
Be sure to keep a pre-6.5 backup just in case things change in the future that prevent the module from working for some reason, so you can easily revert if necessary.
After doing so, you should be safe to upgrade and install the module.
I just started seeing a problem that I thought had been fixed - and now I can't seem to find a solution myself. I had previously had Greenify working happily with the Xposed Framework, but now it has stopped doing so. Every time I enter the Xposed-based Features menu and try to enable anything, I'm taken to the Xposed Setup Guide screen, with only the "ACTIVATE MODULE, REBOOT" button enabled. This in turn takes me to the Xposed Installer; clicking on "Framework" tells me that Xposed framework version 86 (previously 85 - I tried updating but it didn't make any difference) is already active. No amount of rebooting, cache-clearing, or re-flashing seems to help. The problem appears to have re-appeared within the last week or two (I'm not sure exactly, since the only way to know there's a problem is to go into Greenify settings and check). Here are the details of my setup:
Samsung I9300
Cyanogenmod 6.0.1, 26 August 2016 "nightly" version
Greenify version 2.9 (I signed up for Beta within the last 24 hours - but I don't see any indication that I've received any Beta updates)
Xposed Installer 3.0 Alpha 4
Xposed Framework V86-sdk23-arm
The only thing I see in the Xposed log that seems at all helpful is this:
Loading modules from /data/app/com.oasisfeng.greenify-2/base.apk
File does not exist
Anyone have any ideas about what's going wrong here?
Thanks in advance for any light you can shed!
Don Radlauer said:
I just started seeing a problem that I thought had been fixed - and now I can't seem to find a solution myself. I had previously had Greenify working happily with the Xposed Framework, but now it has stopped doing so. Every time I enter the Xposed-based Features menu and try to enable anything, I'm taken to the Xposed Setup Guide screen, with only the "ACTIVATE MODULE, REBOOT" button enabled. This in turn takes me to the Xposed Installer; clicking on "Framework" tells me that Xposed framework version 86 (previously 85 - I tried updating but it didn't make any difference) is already active. No amount of rebooting, cache-clearing, or re-flashing seems to help. The problem appears to have re-appeared within the last week or two (I'm not sure exactly, since the only way to know there's a problem is to go into Greenify settings and check). Here are the details of my setup:
Samsung I9300
Cyanogenmod 6.0.1, 26 August 2016 "nightly" version
Greenify version 2.9 (I signed up for Beta within the last 24 hours - but I don't see any indication that I've received any Beta updates)
Xposed Installer 3.0 Alpha 4
Xposed Framework V86-sdk23-arm
The only thing I see in the Xposed log that seems at all helpful is this:
Loading modules from /data/app/com.oasisfeng.greenify-2/base.apk
File does not exist
Anyone have any ideas about what's going wrong here?
Thanks in advance for any light you can shed!
Click to expand...
Click to collapse
Though I don't have any solutions for you, I note from Xposed log that for me what is loaded is "/data/app/com.oasisfeng.greenify-1/base.apk". I don't know why it searches for greenify-2 for you whereas it loads greenify-1 for me. There is no reference to greenify-2 in my log. Further, the file in /data/app/ is named com.oasisfeng.greenify-1 for me and it contains the base.apk file.
Does this info help you in any way?
Please avoid greenifying Xposed app, this may lead to the issue above.
Hey buddy, it's just simple.
Follow the steps:
1.Go to xposed framework app.
2. Go to modules. (From menu at right top corner)
3.Then just enable greenify.
Comment me if it solved your problem.
InvictaOS is based on LineageOS with some cool extra features. It can be used without any need to have Google application's installed.
DO NOT FLASH LUCKYPATCHER ON InvictaOS BUILDS. I WILL NOT BE RESPONSIBLE FOR THE OUTCOME IF YOU CHOOSE TO DO SO. YOU HAVE BEEN WARNED.
WARNING! This ROM is for the GT-I9200 and GT-I9205 variant's only! If you choose to flash this on other variant's, you will face issues. You are on your own to fix issues.
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Additional Features
Status Bar date
Network Traffic Indicators
Double Tap to sleep on lockscreen
Ambient display battery indicator
Additional QS Tiles
Superuser indicator toggle
Lockscreen charging information
Bluetooth easy toggle
Wifi easy toggle
Toggle to disable suggestions & tile summaries
Unlink notification volume
Pixel navigation bar and animation
Full Substratum OMS theme support
Alarm blocker
Wakelock blocker
Selinux Switch
and more....
Installation procedure
From stock / other custom roms
Plus users have to be on N modem. For models that can't flash N modem, you will have issues with fingerprint registration.
Copy the ROM zip on your phone
Reboot in TWRP Recovery mode
Backup your phone!
Format/Wipe system, cache, dalvik, data
Flash/Install ROM
Flash Install Gapps (OpenGapps ARM N 7.1 Mini/Nano is recommended. DO NOT FLASH STOCK/FULL GAPPS. YOUR PHONE APP WILL FC!!!)
Reboot
Upgrade from previous build
Download the update via OTA app.
Reboot in TWRP Recovery mode
Format/Wipe only cache, dalvik
Flash/Install ROM
Gapps flash is not required for a dirty flash as the backup script in the rom zip file backs up and restores gapps during ROM flash. You can flash gapps after rom flash if you choose to do so. OpenGapps ARM N 7.1 Mini is recommended.
Reboot
Downloads
ROM : Latest build : here || Older builds : here
TWRP : https://sourceforge.net/projects/invictaos/files/Mega-6.3/TWRP/
GAPPS : OpenGapps ( Make sure you use the one for 7.1 - pico is the safest bet )
Screenshots
Note that the screenshots seen above are not the default look of the ROM. It comes with Pixel UI by default. Screenshots are using Coalfield substratum theme and Retrorika icon pack. They are from my MotoG4 plus. Some features may not work on this device.
Updates
You will be notified via the OTA app when there is an update.
Known issues
You tell me...
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Radio (baseband):
ROM version:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
LOSSettings/Performance settings (other than stock):
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
The team
@Silesh.Nair - Project lead
@1chrome - UI designer
Credits
Team LineageOS
Arne Coucheron aka @arco68. Without him, we would not have got a single custom rom. We have cm11,cm12,cm13 & now cm14 due to his hard work and willingness to help others. A big :good: to you, Sir!!!
A big thanks to all users who have helped to test builds as I do not own the device.
@Gibbon_999 for the logs and screenshots.
Others I might have missed.
All users of my roms.
Kernel Sources
https://gitlab.com/sileshn/android_kernel_samsung_msm8930-common
Donations Received
@r1l_Alex_? ( Multiple times, lost count )
@Mr. Obsolet ( Multiple times, lost count )
@gavron ( Multiple )
@bullfinch110
@strongst
@guenterm800
@Retoki
@alaindupus
@dercircle
@echo92
@Tilagoon
@kiden
@bovineyard
@pastorbob62
@syverman
Kai Min?en ( Don't know your user name on xda )
Philip Wehrheim ( Don't know your user name on xda )
Joao Henrique Queiroz ( Don't know your user name on xda )
Robert Rhumba ( Don't know your user name on xda )
It's fine to just click Thanks! or enjoy my work without saying anything.
A donation is to show appreciation of the work I have done already.
A donation is not by any means in expectation of future work.
A donation doesn't entitle for preferred/private support/requests.
A donation is meant as a gift - always appreciated, never required.
MicroG - Not for those who want the easy way out...
What is microg
Microg is a free re-implementation of Google’s proprietary Android user space apps and libraries. In layman terms, it replaces the need to flash gapps. For more details visit the official site.
Sources
https://github.com/microg
Downloads
https://sourceforge.net/projects/los-oms/files/MicroG/MicroG-032317.zip/download
The zip file contains the following files.
Fdroid
Google playstore
Google contacts & calendar sync apk's
Do not install playstore as a user app. It will not work. Playstore has to be in /system/priv-app for this to work.
How do I install this?
March 23rd build will be the first release with support for microg. Fresh flash is a must. Don't even ask if it will work dirty flashing over a rom with gapps. It won't. If you choose not to use microG, you can dirty flash over the previous build.
First build
Download rom from the link in the OP.
Download microg apps from the link above.
Wipe system/cache/data
Flash rom followed by microg apps
Reboot.
Download and install the following apps from the links below.
microG Services Core : here
microG Services Framework Proxy : here
Apple UnifiedNlp Backend : here
MozillaNlpBackend : here
NominatimNlpBackend : here
The last 3 can also be downloaded using the fdroid app.
Updates
Flash rom followed by microg apps without wipe.
How do I set this up?
Go to Settings->Additional Features->Miscellaneous Settings and activate signature spoofing. See screenshot.
Go to Settings->Apps->(Gear Icon)->App permissions->Spoof package signatures and activate spoofing for microG Services Core. See screenshot.
Go to Setings->Battery->Battery optimization and disable battery optimization for the following seen in the screenshot. microG Services Core and Services Framework Proxy should not be battery optimized. Others are optional.
Goto Settings->Apps->(3 dot menu)->Show system and update permissions for Google contact & calendar sync if not updated by default.
Open microG settings app from app drawer and configure backgrounds under UnifiedNlp Settings. See screenshot.
Enable Google device registration and Google Cloud Messaging under Google Services. See screenshot.
Reboot phone. This is a must.
Once you get back to your home screen, open the microG settings app and click on Self-Check. All options must be switched on. That's it. Open playstore and add your account. Read the official webpage or the xda thread for more information. Have fun!!!
Issues
Afaik, the only app that doesn't work is hangouts. I didn't have any other problems.
You may also face delayed notifications from certain apps or for that matter no notifications. If you face such a situation, don't restore data for that app using tibu. Also don't battery optimize that app. Classic examples include mail, google+, whatsapp, tapatalk.
Omg again silesh. Ty!!
Looking good here on my end! Like stated video record isn't functional... All else seems ok for now... I haven't had a chance to hot test... Will be done by the end of the day!!
Damn near a daily Silesh!! Awesome!!
And we start again!! Here we go!!
Other variants
If there is someone running this on a device other than I9200 or I9205, can you provide me with the build.prop from the stock rom. Also mention your model number.
Test build 4 - Backup before you try this. It may not boot.
https://www.androidfilehost.com/?fid=24686681827315503
md5: 022671029fc45f571e2f303c1f38f59c
I have made some changes for this build. I need the following checked on both I9200 & I9205 devices. Fresh flash required.
Does the model no show GT-I9200 or GT-I9205 correctly under Settings->About phone depending on the device? Provide screenshots.
Is the aosp keyboard the default? Does it work? or you need to manually set it as default under Settings->Languages & Input. Provide screenshots.
Is there a physical keyboard entry named "sii9234" under Settings->Languages & Input? Is it set as the default keyboard? Provide screenshots.
Anything else you want to report as out of the ordinary?
If the device is stable to use, can you use it for a while and test for battery usage, any signs of heating and ghost touches.
Thanks in advance.
@Silesh.Nair
My camera working except for video recording..
Flashed gapps and gets play services stopped working
Silesh.Nair said:
https://www.androidfilehost.com/?fid=24686681827315503
md5: 022671029fc45f571e2f303c1f38f59c
I have made some changes for this build. I need the following checked on both I9200 & I9205 devices. Fresh flash required.
Does the model no show GT-I9200 or GT-I9205 correctly under Settings->About phone depending on the device? Provide screenshots.
Is the aosp keyboard the default? Does it work? or you need to manually set it as default under Settings->Languages & Input. Provide screenshots.
Is there a physical keyboard entry named "sii9234" under Settings->Languages & Input? Is it set as the default keyboard? Provide screenshots.
Anything else you want to report as out of the ordinary?
If the device is stable to use, can you use it for a while and test for battery usage, any signs of heating and ghost touches.
Thanks in advance.
Click to expand...
Click to collapse
About to flash it for testing in a little bit.. I should be free for testing for the next few days so ill make sure to really get to work on it!!
I'll update you here in about a hour or so...
Thank you!!
Silesh.Nair said:
https://www.androidfilehost.com/?fid=24686681827315503
Does the model no show GT-I9200 or GT-I9205 correctly under Settings->About phone depending on the device? Provide screenshots.
Click to expand...
Click to collapse
Yes - GT-I9205
[*]Is the aosp keyboard the default? Does it work? or you need to manually set it as default under Settings->Languages & Input. Provide screenshots.
Click to expand...
Click to collapse
Yes
[*]Is there a physical keyboard entry named "sii9234" under Settings->Languages & Input? Is it set as the default keyboard? Provide screenshots.
Click to expand...
Click to collapse
No
[*]Anything else you want to report as out of the ordinary?
Click to expand...
Click to collapse
Camera isn't working.
EDIT: Camera is working now after a couple of reboots.
If the device is stable to use, can you use it for a while and test for battery usage, any signs of heating and ghost touches.
Click to expand...
Click to collapse
Changes made in Settings -> Display are not being saved.
Silesh.Nair said:
https://www.androidfilehost.com/?fid=24686681827315503
md5: 022671029fc45f571e2f303c1f38f59c
I have made some changes for this build. I need the following checked on both I9200 & I9205 devices. Fresh flash required.
Does the model no show GT-I9200 or GT-I9205 correctly under Settings->About phone depending on the device? Provide screenshots.
Is the aosp keyboard the default? Does it work? or you need to manually set it as default under Settings->Languages & Input. Provide screenshots.
Is there a physical keyboard entry named "sii9234" under Settings->Languages & Input? Is it set as the default keyboard? Provide screenshots.
Anything else you want to report as out of the ordinary?
If the device is stable to use, can you use it for a while and test for battery usage, any signs of heating and ghost touches.
Thanks in advance.
Click to expand...
Click to collapse
@Silesh.Nair
Fresh flash cm14-20160910 , phone is boot.
All works as state on OP. Video recording not working and its known issues.
Default keyboard: Aosp
No physical keyboard entry name 'sii9234'
Gonna use this build for a whole days, because the last build (20160909) has ghost touch. Will report back if any.
Here is some screen.
Sent from my GT-I9205 using Tapatalk
Anyone tried the last build on an I9200?
Sent from my Moto G⁴ Plus using Tapatalk
Doh ! - still getting Ghost Touch with this latest version.
EDIT:
So sitting and watching logcat and the phone at the same time - when the ghost settings menu pops up - this event occurs at about the same time.
Code:
09-11 12:05:44.971 730 730 D KeyguardUpdateMonitor: received broadcast android.intent.action.BATTERY_CHANGED
09-11 12:05:44.978 730 730 D KeyguardUpdateMonitor: handleBatteryUpdate
@Silesh.Nair
I can't access anything on the sd card even i want to install an apk..
I noticed that camera only works with google camera
Saiful98 said:
@Silesh.Nair
I can't access anything on the sd card even i want to install an apk..
I noticed that camera only works with google camera
Click to expand...
Click to collapse
Install another file manager from playstore.
Sent from my GT-I9205 using Tapatalk
neilphetamine said:
Install another file manager from playstore.
Click to expand...
Click to collapse
What type of gapps do you install..
Bc i always get play services stopped working
Saiful98 said:
What type of gapps do you install..
Bc i always get play services stopped working
Click to expand...
Click to collapse
I'm using Pico from OpenGapps.
Sent from my GT-I9205 using Tapatalk
Saiful98 said:
What type of gapps do you install..
Bc i always get play services stopped working
Click to expand...
Click to collapse
neilphetamine said:
I'm using Pico from OpenGapps.
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
Isn't that mentioned very clearly in the OP?
Sent from my Moto G⁴ Plus using Tapatalk
Silesh...
I can't toggle flashlight
Tried to reboot several times but same still
But flash in camera working
Camera is buggy.
Sent from my Moto G⁴ Plus using Tapatalk
Hi. Tried the latest build on GT-i9200
Clean Flash , Opengapps Pico.
Call,Data,Sound,everything works smooth.
Camera works, Video recording does'nt.
Ambient display and other options in Display Setting dosent get apply.
Thanks Sir For Great ROM. :good:
Also ghost touch is present.
File manager works
flashlight toggle works too.
Hi, I'm using the last version of Greenify on stock marshmallow rom and I'm not able to cut off paths anymore for apps that wake up by themselves.
There is no "scissors" icon anymore.
Wake up tracker is enabled in settings but I can't enable "enhanced wake up tracker" (a message appears "not supported by the rom")
I'm in root + boost (xposed) mode and I bought donation package.
No problems with previous versions.
Euphorion said:
Hi, I'm using the last version of Greenify on stock marshmallow rom and I'm not able to cut off paths anymore for apps that wake up by themselves.
There is no "scissors" icon anymore.
Wake up tracker is enabled in settings but I can't enable "enhanced wake up tracker" (a message appears "not supported by the rom")
I'm in root + boost (xposed) mode and I bought donation package.
No problems with previous versions.
Click to expand...
Click to collapse
Also running a near AOSP stock MM ROM with root/Xposed and have access to both features. Suggest uninstalling/reinstalling Greenify with a reboot between.
Davey126 said:
Also running a near AOSP stock MM ROM with root/Xposed and have access to both features. Suggest uninstalling/reinstalling Greenify with a reboot between.
Click to expand...
Click to collapse
Thanks for your answer. I did that and installed the last new version (3.2.1) but no effects... One change : when I try to enable enhanced wake up tracker a pop-up appears for one second ("Applying... ") but it still failed saying it's not supported by the rom.
I come from LineageOS 14.1 and I flashed the whole stock marshmallow firmware. Maybe it has something to do with this...
Weird : I tested adb commands to enable wake up cut off for non-root devices (although i'm rooted+xposed)
adb -d shell pm grant com.oasisfeng.greenify android.permission.READ_LOGS
adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
Click to expand...
Click to collapse
Results : cut off paths are back (with the scissors icon) and I have informations on the opened apps ("UI opened xx seconds ago" "Service started by..."). With my "issue" I didn't have these informations anymore.
The strange thing is that I still can't enable enhanced wake up tracker in settings (same message as mentioned before).
Long story short : Although i'm rooted there is something that may block greenify to read/write settings in order to track apps so I have to manually enable wake up cut off via adb commands.
Euphorion said:
Thanks for your answer. I did that and installed the last new version (3.2.1) but no effects... One change : when I try to enable enhanced wake up tracker a pop-up appears for one second ("Applying... ") but it still failed saying it's not supported by the rom.
I come from LineageOS 14.1 and I flashed the whole stock marshmallow firmware. Maybe it has something to do with this...
Click to expand...
Click to collapse
Euphorion said:
Weird : I tested adb commands to enable wake up cut off for non-root devices (although i'm rooted+xposed)
Results : cut off paths are back (with the scissors icon) and I have informations on the opened apps ("UI opened xx seconds ago" "Service started by..."). With my "issue" I didn't have these informations anymore.
The strange thing is that I still can't enable enhanced wake up tracker in settings (same message as mentioned before).
Long story short : Although i'm rooted there is something that may block greenify to read/write settings in order to track apps so I have to manually enable wake up cut off via adb commands.
Click to expand...
Click to collapse
Interesting. I'm vacillating between a near-stock MM build and LinOS 14.1 on a couple devices and haven't run into this...yet. Obviously reduced Geeenify functionality on Nougat w/o Xposed. Appreciate you sharing findings; should be helpful should this issue arise. Hopefully others can offer insight into lingering wake-up tracker issue.
I'm on LOS 13 Greenify 3.0.5.
I noticed an app still started somehow even after I manually hibernate it. wake-up tracker is enabled, wake-up cut-off is enabled.
I'm facing the same issue on 2 Motorola G 2014 devices and 1 Moto E 2015, all on MM roms, root + xposed.
Same here, LineageOS 13 with root+Xposed and donation package, the feature is enabled and even enhanced tracker is enabled but the scissors never show up
Same problem here with Greenify 3.2.2 paid version!!
Samsung Note 3 Neo (SM-N7505) Lollipop 5.1.1 Root Xposed.
I hope on next version to fix it...