Lollipop lpx13d - Greenify

I'm testing greenify on the new lollipop preview for nexus 5, here's what is working for now and what is not:
- non-root mode works(haven't tried automatic hybernation).
- root mode failes to greenify certain apps(chrome beta, tapatalk).
- I bought the pro key on amazon and transfered it to the play store, and it worked on both my nexus 7 and on my nexus 5(with kitkat). With lollipop if i try to enable system app hybernation the app says that I need to buy the donation package.

Bronto9 said:
I'm testing greenify on the new lollipop preview for nexus 5, here's what is working for now and what is not:
- non-root mode works(haven't tried automatic hybernation).
- root mode fails to greenify certain apps(chrome beta, tapatalk).
- I bought the pro key on amazon and transfered it to the play store, and it worked on both my nexus 7 and on my nexus 5(with kitkat). With lollipop if i try to enable system app hybernation the app says that I need to buy the donation package.
Click to expand...
Click to collapse
i'm on the lpx13d build rooted in this way:https://plus.google.com/113517319477420052449/posts/ZzXaU1W7Uzm
and root mode fails to greenify ALL the apps.
For the Dev -> http://forum.xda-developers.com/showpost.php?p=56128406&postcount=6978

root mode broken by lollypop changes
error when running rooted mode is:
D/AndroidRuntime(30231): Shutting down VM
D/AndroidRuntime(30266):
D/AndroidRuntime(30266): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime(30266): CheckJNI is OFF
D/AndroidRuntime(30266): Calling main entry com.android.commands.am.Am
W/main (30266): type=1400 audit(0.0:7977): avc: denied { call } for scontext=u:r:zygote:s0 tcontext=u:r:servicemanager:s0 tclass=binder
W/main (30266): type=1400 audit(0.0:7978): avc: denied { call } for scontext=u:r:zygote:s0 tcontext=u:r:servicemanager:s0 tclass=binder
E/JavaBinder(30266): !!! FAILED BINDER TRANSACTION !!!
E/ServiceManager(30266): error in getService
E/ServiceManager(30266): android.os.TransactionTooLargeException
E/ServiceManager(30266): at android.os.BinderProxy.transactNative(Native Method)
E/ServiceManager(30266): at android.os.BinderProxy.transact(Binder.java:496)
E/ServiceManager(30266): at android.os.ServiceManagerProxy.getService(ServiceManagerNative.java:123)
E/ServiceManager(30266): at android.os.ServiceManager.getService(ServiceManager.java:55)
E/ServiceManager(30266): at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2342)
E/ServiceManager(30266): at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2340)
E/ServiceManager(30266): at android.util.Singleton.get(Singleton.java:34)
E/ServiceManager(30266): at android.app.ActivityManagerNative.getDefault(ActivityManagerNative.java:82)
E/ServiceManager(30266): at com.android.commands.am.Am.onRun(Am.java:295)
E/ServiceManager(30266): at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
E/ServiceManager(30266): at com.android.commands.am.Am.main(Am.java:99)
E/ServiceManager(30266): at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
E/ServiceManager(30266): at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:249)
I/art (30266): System.exit called, status: 1
I/AndroidRuntime(30266): VM exiting with result code 1.
this repeats constantly in the event log until greenify is force stopped (greenify fails to hibernate any app for me in root mode due to this error)

2.5 beta 1 should have fixed the issue. Please try it out.

Can you please upload it on dropbox with other betas? I'm having problems installing it from the play store

Bronto9 said:
Can you please upload it on dropbox with other betas? I'm having problems installing it from the play store
Click to expand...
Click to collapse
Both beta 1 and beta 2 are uploaded to Dropbox.

oasisfeng said:
Both beta 1 and beta 2 are uploaded to Dropbox.
Click to expand...
Click to collapse
Yup, beta 2 working in root mode now! Nice
One query, I love assigning the nav bar ring targets to "Hibernate & lock" on Lollipop LPX13D. While this works, what method do you use to lock the screen? I only ask because while this feature locks the screen + hibernates, it doesn't allow the 'smart lock' on LPX13D to function. Scenario:
- lock screen with power button, smart lock functions fine
- lock screen + hibernate from nav bar target, and smart lock won't function until the device has been unlocked & re-locked using power button instead of nav bar target.
Hence I'm just wondering if the lock screen is using some sort of bypass of the 'normal' screen lock method? No big deal, just wondering cos smart lock is awesome but won't function if I use 'screen off +hibernate'

Related

[1.117.0306] Latest Gear Fit Manager non-Samsung + Endomondo [4.x/5.x compatible]

Hello,
I've patched the current version of the Gear Fit Manager (v. 1.117.0306) built on 2015, March 06 and released at the end of March.
Links updated on 2015, April 19. Calls are fixed. I'm investigating on the issue with Lollipop 5.1 .
Test version for 5.1 : https://mega.co.nz/#!bEdXAQhb!i5hxkgyzEI43fBWa6ThfIiPUI2U2V2gdVeXY5AGWHg8 [Test 1 - try to use the 5.1 API]
https://mega.co.nz/#!GFcHUAhI!snmHX91S4PJwJZlPtCTMDUjOv36EKeaaKrS54UX2PtY [Test 2 - try to bypass one section]
This version is based on the last official Samsung version compatible with Lollipop. I patched the apk to be compatible with non Samsung phones. To install this version you need to install the following packages (I advice you to install in that order).
Gear Fit Manager and requirements
This firmware to update with Odin: R350XXU0BOA2
https://mega.co.nz/#!qUskxIDL!wexEZQTZ6t6wk0jO6dv1JDsdT6oCDYBxlegMb-MS6qc
This apk which is the main application: Gear Fit Manager
https://mega.co.nz/#!nI0UyJJD!zYFvTolgxAgL39ydX9ZgHCson5K2TJxMx9_-BKOa--A
This apk which contains required components: Gear Fit Installer (it's actually embedded into the second apk but it has to be installed manually)
https://mega.co.nz/#!mFknlTZB!iIB7DWPQC5ECiPlNcum0JXpcJRuE4XmI7v6Drchgk3Y
Your build.prop must NOT contain "samsung", just keep the default values for your device.
App Connect Applications :
Endomondo 11.0.3:
https://mega.co.nz/#!Kd82hawL!lGt2pJbBCfvO7bQ52fI4VgtOufMHLQVEozqWt7ziY84
To connect via Facebook you need to delete the app from your profile (https://www.facebook.com/help/170585223002660) if you already used it before, else you will have a login loop. The normal login via mail also works.
Endomondo is not able to use the Heart Rate monitor from the watch, this is normal (https://support.endomondo.com/hc/en-us/articles/201784416-SmartWatches#gear).
Calculator 2.0:
https://mega.co.nz/#!jFNDQDoJ!oIqRjQY_4oBrCMbygSB4HZfsAt7K1AWW2gg7KvTx1UA
I'll try to keep this topic up to date with the last version available on :
http://forum.xda-developers.com/showthread.php?t=2789503
I guarantee that the software is 100% safe. I will detail the reverse engineering done to make the new versions of the manager to work properly on non-Samsung devices.
Working :
Bluetooth connection
Clocks
Notifications
Media control
Custom clocks
Heart Rate
Reject Calls
SMS Quick Reply
Find my phone
Partially working :
App Connect (the manager cannot be signed properly so you will always get the "You should install Gear Fit Manager application first" message. This can be fixed but no so easily (the app have to be patched to not check the signature). If you want an app, post the apk here and I will patch this app.
Not working :
Anything related to SHealth / Weather as it requires Touchwiz (Endomondo is a good SHealth alternative)
Updates
19/04/2015 : Added Endomondo and Calculator apps.
19/04/2015 : Crash when receiving calls fixed.
Thanks for baking this. I can live without the weather, but I miss the caller ID notifications.
This isn't working on my 5.1 Nexus 6. I get a force close upon opening it. Firmware is at BOA2 and I installed the smaller file, then the first. Anything I can do to help troubleshoot this? It was a clean install on this phone.
It should work with 5.0.2 (tested with my OnePlus One with OxygenOS). I never tried with 5.1 yet. Could you send me a logcat please ? If it's a force close on launch I think it should be fixable.
koalala said:
Hello,
I've patched the current version of the Gear Fit Manager (v. 1.117.0306) built on 2015, March 06 and released at the end of March.
This version is based on the last official Samsung version compatible with Lollipop. I patched the apk to be compatible with non Samsung phones. To install this version you need to install :
- This firmware with Odin (R350XXU0BOA2) :
https://mega.co.nz/#!WFF2XaAD!slUq8FE4D3cvTCIMrI4THnOPlR2GBttRLRyOgm379r8
- This apk which contains required components : Gear Fit Installer (it's actually embedded into the second apk but it has to be installed manually)
https://mega.co.nz/#!mFknlTZB!iIB7DWPQC5ECiPlNcum0JXpcJRuE4XmI7v6Drchgk3Y
- This apk which is the main application : Gear Fit Manager
https://mega.co.nz/#!WFF2XaAD!slUq8FE4D3cvTCIMrI4THnOPlR2GBttRLRyOgm379r8
Your build.prop must NOT contain "samsung", just keep the default values for your device.
I'll try to keep this topic up to date with the last version available on :
http://forum.xda-developers.com/showthread.php?t=2789503
I guarantee that the software is 100% safe. I will detail the reverse engineering done to make the new versions of the manager to work properly on non-Samsung devices.
Working :
Bluetooth connection
Clocks
Notifications
Media control
Custom clocks
Heart Rate
Reject Calls
Find my phone
Partially working :
App Connect (the manager cannot be signed properly so you will always get the "You should install Gear Fit Manager application first" message. This can be fixed but no so easily (the app have to be patched to not check the signature). If you want an app, post the apk here and I will patch this app.
Not working :
Anything related to SHealth / Weather as it requires Touchwiz
Click to expand...
Click to collapse
So great. I waiting for a long time
Will re-install Lolipop on my 6653 and feedback to you soon.
Again, thanks you
Update: Could you please update the frimware link? My gear fit running R350XXU0BNG2 and CAN NOT pair with my Sony Z3 D6653
Thank you for the remark I didn't see that the hyperlink was broken. It's corrected now, you can download the last firmware.
works
wish endomondo can be work in this version could u plz patch this app?? ... btw thank you for your big help:good::good::good:~ it works on my android 5.0 phone. i flash my gear firm by odin3.0.9.5 in csc bar
Log Cat from Stock 5.1 Nexus 5
koalala said:
It should work with 5.0.2 (tested with my OnePlus One with OxygenOS). I never tried with 5.1 yet. Could you send me a logcat please ? If it's a force close on launch I think it should be fixable.
Click to expand...
Click to collapse
Code:
D/AndroidRuntime(19780): Shutting down VM
E/AndroidRuntime(19780): FATAL EXCEPTION: main
E/AndroidRuntime(19780): Process: com.samsung.android.wms, PID: 19780
E/AndroidRuntime(19780): java.lang.RuntimeException: Unable to create service com.samsung.android.wms.service.WingtipManagerService: java.lang.ClassCastException: int[] cannot be cast to long[]
E/AndroidRuntime(19780): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2771)
E/AndroidRuntime(19780): at android.app.ActivityThread.access$1800(ActivityThread.java:151)
E/AndroidRuntime(19780): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1386)
E/AndroidRuntime(19780): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(19780): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(19780): at android.app.ActivityThread.main(ActivityThread.java:5254)
E/AndroidRuntime(19780): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(19780): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(19780): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
E/AndroidRuntime(19780): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
E/AndroidRuntime(19780): Caused by: java.lang.ClassCastException: int[] cannot be cast to long[]
E/AndroidRuntime(19780): at com.samsung.android.wms.service.notification.CallAdapterForLollipop.registerPhoneStateListener(CallAdapterForLollipop.java:150)
E/AndroidRuntime(19780): at com.samsung.android.wms.service.notification.CallAdapterForLollipop.onCreate(CallAdapterForLollipop.java:110)
E/AndroidRuntime(19780): at com.samsung.android.wms.service.WingtipManagerService.initAdapters(WingtipManagerService.java:1641)
E/AndroidRuntime(19780): at com.samsung.android.wms.service.WingtipManagerService.onCreate(WingtipManagerService.java:1275)
E/AndroidRuntime(19780): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2761)
E/AndroidRuntime(19780): ... 9 more
W/ActivityManager( 738): Force finishing activity 1 com.samsung.android.wms/.app.base.ContentsActivity
I/WindowManager( 738): Screenshot max retries 4 of Token{26383230 ActivityRecord{b658373 u0 com.samsung.android.wms/.app.base.ContentsActivity t689 f}} appWin=Window{2394e09a u0 com.samsung.android.wms/com.samsung.android.wms.app.base.ContentsActivity} drawState=1
I/OpenGLRenderer( 738): Initialized EGL, version 1.4
W/ActivityManager( 738): Activity pause timeout for ActivityRecord{b658373 u0 com.samsung.android.wms/.app.base.ContentsActivity t689 f}
W/LocationOracleImpl(17839): Best location was null
W/ResourceType( 1111): No package identifier when getting value for resource number 0x00000000
W/PackageManager( 1111): Failure retrieving resources for com.samsung.android.wms: Resource ID #0x0
D/TaskPersister( 738): removeObsoleteFile: deleting file=687_task_thumbnail.png
D/PhoneStatusBar( 1111): disable: < expand ICONS* alerts SYSTEM_INFO* back home recent clock search >
D/NuPlayerDriver( 188): stop(0xb590d8e0)
W/MessageQueue( 1111): Handler (android.media.MediaPlayer$EventHandler) {36f23de2} sending message to a Handler on a dead thread
W/MessageQueue( 1111): java.lang.IllegalStateException: Handler (android.media.MediaPlayer$EventHandler) {36f23de2} sending message to a Handler on a dead thread
W/MessageQueue( 1111): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:325)
W/MessageQueue( 1111): at android.os.Handler.enqueueMessage(Handler.java:631)
W/MessageQueue( 1111): at android.os.Handler.sendMessageAtTime(Handler.java:600)
W/MessageQueue( 1111): at android.os.Handler.sendMessageDelayed(Handler.java:570)
W/MessageQueue( 1111): at android.os.Handler.sendMessage(Handler.java:507)
W/MessageQueue( 1111): at android.media.MediaPlayer.postEventFromNative(MediaPlayer.java:2670)
D/NuPlayerDriver( 188): reset(0xb590d8e0)
D/NuPlayerDriver( 188): notifyResetComplete(0xb590d8e0)
I/ActivityManager( 738): Process com.google.android.apps.docs (pid 17663) has died
D/PhoneStatusBar( 1111): disable: < expand icons* alerts system_info* back home recent clock search >
koalala said:
Hello,
I've patched the current version of the Gear Fit Manager (v. 1.117.0306) built on 2015, March 06 and released at the end of March.
Click to expand...
Click to collapse
Thank you very much. It works on my Nexus 4 with 5.0.1 stock.
I think my logcat is saying the same thing as the previous one.
[Nexus 6 w/ 5.1 ROM]
Code:
[ 04-10 18:34:15.309 4238: 4238 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.samsung.android.wms, PID: 4238
java.lang.RuntimeException: Unable to create service com.samsung.android.wms.service.WingtipManagerService: java.lang.ClassCastException: int[] cannot be cast to long[]
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2771)
at android.app.ActivityThread.access$1800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1386)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: java.lang.ClassCastException: int[] cannot be cast to long[]
at com.samsung.android.wms.service.notification.CallAdapterForLollipop.registerPhoneStateListener(CallAdapterForLollipop.java:150)
at com.samsung.android.wms.service.notification.CallAdapterForLollipop.onCreate(CallAdapterForLollipop.java:110)
at com.samsung.android.wms.service.WingtipManagerService.initAdapters(WingtipManagerService.java:1641)
at com.samsung.android.wms.service.WingtipManagerService.onCreate(WingtipManagerService.java:1275)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2761)
... 9 more
Working on Xperia Z2 android 4.4.2 stock/rooted
This is my first attempt to make the gear fit work on a non-samsung device and it's working as informed. Was hoping to get endomondo working thru appconnect, so I'm also looking forward for that patch. Congratulations koalala on this accomplishment and keep up the good work!
This seems to be working on my Nexus 5. Thanks a bunch!
bugs found
Incoming call notify doesn't work. Gear fit will disconnect when there is incoming call and so as the gear for manager
Hi man! You have my all attention
I have Lenovo A806 with Mediatek and Android 4.4.2. It's not possible to connect. Pairing is ok. Logcat is included and I will help you as much as I can, so don't hesitate contact me.
Logcat from line 2381 I think.
Thank you very much!!
Hi, I´m trying to use the app "gear fit share", but i don´t know how i can signed (it show "the manager is not signed" message).
How can i do it?
Is there any tutorial for this?
Thanks!!!
Search tutorial in thread "gear fit manager on non Samsung devices" on xda
Sent from my nexus 4 using XDA Free mobile app
1.117.030622
I have stock rooted Sprint phone and got the 1.117.030622 update and it won't connect anymore. I tried resetting everything still no luck.
hi
followed instructions and the firmware B02 by odin
installed apks, paired with my phone, but it stays on "connect to the device" when in the app, it cant go to the gear
any idea?
logcat joined if any help?
Incoming call notify doesn't work,nexus 4 aicp 5.0.2
hi, i want to use the app "gear fit launcher" to launch tasker shortcuts.
It was hard to find the apk because it isn't available at the playstore anymore.
sadly if i try to activate the app it says "manager not signed"
is there any way to get around this?
if you need the apk, i can upload it for you
adrian_cwchow said:
Incoming call notify doesn't work. Gear fit will disconnect when there is incoming call and so as the gear for manager
Click to expand...
Click to collapse
I have the same problem with my sony xperia z3 compact with 5.0.2

[Xposed] Battery Shutdown Manager

Battery Shutdown Manager
Download @ Google Play
​
Do you know that moment when you're on 1% of battery and think "I'll just use my device 20 more seconds then I'll get my charger" - and at exactly that moment it'll switch to 0% and you'll see the threaded "Shutting down" dialog and know it's too late now?
This Xposed module will help by showing you a dialog with a countdown before the actual shutdown, so you'll have time to attach your charger.
The module achieves this by postponing the shutdown for a couple of seconds to give you time to connect the charger.
Please post any kind of feedback or ideas you have regarding this app :fingers-crossed:
I tested the module a lot but can't possibly test it for all those different phones and versions out there.
Thus I will flag it as beta for now so you can provide feedback before I'll release the 1.0 version.
It would be great if some more people could test it. I used the StabilityTest app to quickly drain my battery down to 0%.
Compatibility:
I wrote this module and tested it with AOSP devices as well as on Cyanogenmod.
It should work without any issues on all Nexus and Google Play Edition devices from Android 4.2 to 5.1+.
As almost all Custom ROMs are based on either AOSP or CM they should work without issues, too.
Some vendors might have changed the original code and thus render this module incompatible on their device. Nothing bad will happen when you install it, it just won't work.
Compatible:
Nexus / AOSP / GPE ROMs
Cyanogenmod
Almost all custom ROMs (as they're usually either based on AOSP or CM)
Sony Stock ROMs
Not compatible:
Currently not working for LG Stock ROMs due to internal code changes by LG.
Android devices <4.2. Support for Android 4.0.3+ and 4.1 might be added when I see a greater demand for it.
Installation:
- Download the app
- Activate the module in the Xposed Insaller
- Reboot your device
- Open the app to change it's options to your liking
Bugs/Issues:
If you encounter any bugs just report them here and I'll try to fix them. Always include as much information as possible, including your device model, android version and exact ROM details.
Note that I will most likely need a log to fix the issue, a generic "doesn't work on phone xyz" won't help me fixing the issues.
There are two possibilities to get a log.
Use the Catlog app. In the app press Menu > Record Log before the device shuts down, then attach the logcat to your bugreport.
Alternatively you need to use adb to grab the log.
Unfortunately logging is a bit more complicated for this module as the interesting part happens on shutdown.
The best solution (and what I do personally for debugging this app) is to use ADB over WiFi (e.g. with this app) and grab the log.
Download:
Google Play Store
Xposed Module Repository
Google+:
www.google.com/+thetonyp
Last but not least an obligatory huge thanks to @rovo89 for his amazing Xposed framework!
If you like this module don't forget to press thanks, rate this thread with 5 stars, consider a donation etc. etc.
:fingers-crossed:​

			
				
I love your icon pack!
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Samsung galaxy s3 i9300 4.3 mk6 stock rom, bootloops.
Sent from a stolen phone!
Bootloop on Nexus 4, Stock Android 4.3.3...
EDIT Because OP asked how the bootloop occurs on Nexus 4, Android 4.3.3:
Bootloop occurs after activating module and normal (not soft) reboot.
Before reboot app can be runned and configurated.
I have no log app running, so I'm not able to deliver logs.
Yes, please send me a logcat. Bootloops are great, then you can just get the log after the reboot. I literally can't do anything without a log.
mobihack said:
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Click to expand...
Click to collapse
Thanks for the feedback, then I will add 5.1 to the compatibility at the Play Store.
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
tonyp said:
Thanks for the feedback, then I will add 5.1 to the compatibility at the
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
Click to expand...
Click to collapse
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
bootloops
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
akhilkbaby said:
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
Click to expand...
Click to collapse
I'd like to fix the issue, could you kindly send me a logcat of the bootloop?
Unfortunately there is literally nothing I could possibly do without a log.
mobihack said:
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
Click to expand...
Click to collapse
I'm using the stock dialog which guarantees the highest possible compatibility with other devices.
Regarding the notification, I don't know when the battery will be empty before, so there's no way to display a message one minute before. All I could do is starting the dialog at 1% (which I'm considering for a future version), but that would be quite different.
I like the idea for a shutdown button, an option to include that will be in an upcoming version.
Oh, true, the icon pack is called etched material.
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
HydraS4 said:
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
Click to expand...
Click to collapse
This sounds very strange, the module is only hooking into one class which has nothing to do with receiving messages.
Yes, usually it works to log the freeze, just start logging (best would be with adb logcat) before it happens.
Can not install on 4.1
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
---------- Post added at 02:41 PM ---------- Previous post was at 01:49 PM ----------
Fif_ said:
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
Click to expand...
Click to collapse
There we go, I have it.
This is a logcat of the behavior I was describing earlier: after the countdown, the system performs a soft reboot instead of shutting down.
I have seen this behavior on Nexus 4/5/10 (mako/hammerhead/manta) on CM11 M11.
The logcat below is on a Nexus 4 running CM11 M11 and Battery Shutdown Manager 0.93:
Code:
I/Xposed ( 1726): BatterySM: invokeOriginalMethod. batteryLevel=2, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=false, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: Showing dialog. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: Dismiss dialog
W/InputMethodManagerService( 1726): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
D/AndroidRuntime( 1726): Shutting down VM
W/dalvikvm( 1726): threadid=1: thread exiting with uncaught exception (group=0x415e4ce0)
E/AndroidRuntime( 1726): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 1726): java.lang.NoSuchMethodError: com.android.server.BatteryService#processValuesLocked(java.lang.Boolean)#bestmatch
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:271)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:284)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.callMethod(XposedHelpers.java:947)
E/AndroidRuntime( 1726): at com.thetonyp.batteryshutdownmanager.BatteryDialog$2.onFinish(BatteryDialog.java:258)
E/AndroidRuntime( 1726): at android.os.CountDownTimer$1.handleMessage(CountDownTimer.java:118)
E/AndroidRuntime( 1726): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1726): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(SystemServer.java:1289)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(Native Method)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(SystemServer.java:1386)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
E/AndroidRuntime( 1726): at dalvik.system.NativeStart.main(Native Method)
W/DropBoxManagerService( 1726): Dropping: system_server_crash (1667 > 0 bytes)
I/Process ( 1726): Sending signal. PID: 1726 SIG: 9
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Mubasher96 said:
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
Click to expand...
Click to collapse
The module currently requires Android 4.2 or higher. You can't install the module on CM10 as that is based on Android 4.1.
To support Android 4.0 and 4.1 I need to write some custom code which I need some people to test, so everyone interested in this module on a 4.0 or 4.1 device (including CM9 / CM10 etc of course) please write here or send me a PM and I'll contact you as soon as I have a version ready for testing! Can I count you in?
Fif_ said:
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
...
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Click to expand...
Click to collapse
Thank you very much for the logcat! It contained exactly what I needed!
Thanks to that I identified the issue and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Additionally this version fixes a potential bootloop cause for devices running Jellybean (4.2 / 4.3).
Could the affected people please test this and confirm? Again, if you manage to get me a log it will make it a lot easier for me to fix any issue whatsoever.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Nice! This is so necessary… I'm gonna test it.
tonyp said:
Thank you very much for the logcat! It contained exactly what I needed!
I believe I identified the issue thanks to the log and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Click to expand...
Click to collapse
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Fif_ said:
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
Click to expand...
Click to collapse
No worries, they're using the same codebase so it will work on all devices.
Thanks a lot for buying pro
That purchase should work on all devices of course sometimes it takes a little while to propagate at Google, when you still have the issue after a couple more hours could you please drop me a PM? I did test the IAP purchases with all possible ways Google offers for me, but unfortunately that's something that could be greatly improved on their side.
exodius48 said:
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Click to expand...
Click to collapse
Ah, I didn't know there exists an alternative manager. I'm explicitly checking for the Xposed Installer. You can ignore the warning for now and I will push an update which recognizes the WSM Manager as well
No bootloops on moto g stock 5.0.2

[ROM][8.1][UNOFFICIAL] Android Ice Cold Project v13.1

Removed
moto actions?
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
KamiGooDz said:
moto actions?
Click to expand...
Click to collapse
Yes, it's available
snapchat don't work, how fix?
Update
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
FpX said:
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
Click to expand...
Click to collapse
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
KamiGooDz said:
snapchat don't work, how fix?
Click to expand...
Click to collapse
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
AsD Monio said:
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
Click to expand...
Click to collapse
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
anybody tested nin moto g5S xt1795 indian edition
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:28 AM ---------- Previous post was at 07:26 AM ----------
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
anybody tested in moto g5S xt1795 indian edition ?
FpX said:
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
Click to expand...
Click to collapse
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
AsD Monio said:
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
Click to expand...
Click to collapse
I was using the previous build, now it's working perfectly, thanks!
Update
aicp_montana_o-13.1-UNOFFICIAL-20190121
Changes
Enforcing SELinux
Download: http://www.mediafire.com/file/hquz82ge8werfgf/aicp_montana_o-13.1-UNOFFICIAL-20190121.zip/file
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
newinnov said:
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
Click to expand...
Click to collapse
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
AsD Monio said:
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
Click to expand...
Click to collapse
Yes, It was indeed! Actually I flashed the custom kernel on top of that , somehow that was causing trouble. Thanks again.
Flashed it om my wifes phone yesterday, she's very happy, less battery drain and wifi is better, which was the main reason to try a custom rom.
Thanks guys!
Hi, is Fingerprint, camera photo/video recording, and Moto display notifications working good ?
Thank´s
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
SvenHee said:
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
Click to expand...
Click to collapse
I had that happen to me as well, it's not the ROM's fault. Either fastboot or the stock recovery store some data in the /misc partition. That tells the bootloader/kernel to boot to recovery by default. It's probably meant to ensure that a partially upgraded system does not get booted while flashing a stock ROM. To fix it just wipe the /misc partition, I recommend making a backup first. I used dd in the terminal in TWRP for both operations (adb shell will work as well but it has some problems with displaying some characters in the Windows command prompt). To back up the partition:
Code:
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc.img
^ (replace "external_sd" with "data/media/0" to save it in the internal storage instead of the external microSD card)
To wipe /misc:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
It may also work using fastboot, though I have not tried this way:
Code:
fastboot erase misc
Thanks!
That is slightly intimidating to execute but I'll give it a go!
aicp_montana_o-13.1-UNOFFICIAL-20190116
My device : xt1799-2
64bit os.
VoLte works for my xt1799-2.
Bugs:
1. Can't copy any file from the device to my PC. The same bug in crDroid 8.1.0 rom. And lineageos. This happens in all the third party rom between 8.1.0-9.0. Date at least before 2019-09-23. But can copy the folder from the device. But also can send file to the device, so weird.
________________________________________________
I see the lineageos 15.1 changelog:
2019-09-23:
September security patch
Optimized SEPolicy
Fixed MTP (thanks to @wiktorek140)
We're back to LTE
________________________________________________
But can copy the folder from the device. But also can send file to the device, so weird.
2. Front camera doesn't work.
3. Fingerprint doesn't work.
4. Delay a lot when you scroll the page, or move the app icon. The same bug in crDroid 8.1.0.
5. Call recorder. If you don't open the speaker, the inner voice recorded from the other side is too small, unable to hear it clearly.

[ROM][Pie][OFFICIAL] COSP [9.0.0][harpia]

COSP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
Welcome to COSP, your new future Android Operating System.
Our goal is to have an Pixel-like android ROM that isn't spying on you and uses as few system space as possible. Also, we provide the option to go completely without GApps using MicroG support.
Why us?
We are focusing on stability and performance, having an debloated ROM is essential for that. Also, we want Users to decide what kind of Store they want to use, either F-Droid or the Play Store.
Also, we take User requests serious. To suggest something, contact us on telegram.
Features:
1) All systemUI tuning elements
2) An handy Network indicator
3) Charging Information
4) Lawnchair and Quickstep as default
5) Quick Settings mods
6) Signature spoofing
7) OP gestures
8) Navbar tuner
9) Rootless Substratum (with fixes to theme system correctly)
10) Screenshot/screenrecord tile
11) Advanced power menu
12) Double tap to sleep on statusbar
13) Option to disable quick settings/power menu on secure lockscreen
OTA Updating for official devices enables Users to get the newest version with ease.
DOWNLOADS:
COSP-190207-OFFICIAL-harpia.zip
MD5SUM: 5b906e96dd6de389838f86954894f0c3
Sources:
ROM Source: https://github.com/cosp-project/
Kernel Source code: https://github.com/Harpia-development/kernel_motorola_msm8916 (on branch pie_upstream_cust)
Device tree: harpia (on branch cosp_9) and common (on branch 9), using the following manifest.
facuarmo said:
COSP
Code:
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
Welcome to COSP, your new future Android Operating System.
Our goal is to have an Pixel-like android ROM that isn't spying on you and uses as few system space as possible. Also, we provide the option to go completely without GApps using MicroG support.
Why us?
We are focusing on stability and performance, having an debloated ROM is essential for that. Also, we want Users to decide what kind of Store they want to use, either F-Droid or the Play Store.
Also, we take User requests serious. To suggest something, contact us on telegram.
Features:
1) All systemUI tuning elements
2) An handy Network indicator
3) Charging Information
4) Lawnchair and Quickstep as default
5) Quick Settings mods
6) Signature spoofing
7) OP gestures
8) Navbar tuner
9) Rootless Substratum (with fixes to theme system correctly)
10) Screenshot/screenrecord tile
11) Advanced power menu
12) Double tap to sleep on statusbar
13) Option to disable quick settings/power menu on secure lockscreen
OTA Updating for official devices enables Users to get the newest version with ease.
DOWNLOADS:
COSP-190207-OFFICIAL-harpia.zip
MD5SUM: 5b906e96dd6de389838f86954894f0c3
Sources:
ROM Source: https://github.com/cosp-project/
Kernel Source code: https://github.com/Harpia-development/kernel_motorola_msm8916 (on branch pie_upstream_cust)
Device tree: harpia (on branch cosp_9) and common (on branch 9), using the following manifest.
Click to expand...
Click to collapse
What Is working? Bugs?
Volte Is working?
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Moto_g4_play said:
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Click to expand...
Click to collapse
Install it once, reboot to system and after booting to system reboot again, it should appear.
Sent from my Redmi Note 5 using Tapatalk
Sakul1994 said:
What Is working? Bugs?
Volte Is working?
Click to expand...
Click to collapse
Everything is working. VoLTE isn't supported yet for this device on none of the ROMs because of source changes introduced in Pie that broke it. Some devs are working on it, while I can't, just because of the fact that my carrier hasn't implemented it yet.
Moto_g4_play said:
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Click to expand...
Click to collapse
I'm glad you like this ROM, although you might want to thank @edi194 a bit more about this since he's the owner of the project lol. I'm just a maintainer.
About rooting, that's a bug in Magisk. Simply unpack the Magisk zip and manually install magisk.apk from the common folder.
Moto_g4_play said:
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Click to expand...
Click to collapse
Install apk for that coz sometimes it shows bt if not try to install apk n download it from google
Thank you EDI194 and facuarmo for this ROM development and maintenance, thanks look.akash18 for the help.
Hi, after following the standard procedure to install this rom (wipe cache, system, dalvik, data), I found that the initial setup is broken if no gapps are installed, the Pixel setup crashes as soon as I hit Continue, I re-downloaded the rome to check if maybe my download was corrupt, had no luck, also checked with md5sum and the file was fine
Re-installing the rom and installing gapps before the first boot allows me to complete the initial setup
---------- Post added at 03:17 PM ---------- Previous post was at 03:00 PM ----------
Hi, I have encountered another *minor* bug, enabling triple tap zoom on accessibility settings disables any kind of input on the device, the power button still works, although the only thing that can be done is forcing the device to restart long-pressing the power button
I can confirm the device does not completely hangs, as animations going on in the screen are still displaying, and plugging an external mouse thru OTG moves the cursor (but clicking and pressing keys don't do anything)
steps to reproduce:
-Install rom with nano gapps package (from OpenGapps)
-finish initial setup
-enable triple tap zoom
-enjoy (??)
EDIT: I should clarify that only *enabling* triple tap zoom hangs the phone, after forcing the device to reboot, it works normally (and even triple tap zoom works)
---------- Post added at 04:13 PM ---------- Previous post was at 03:17 PM ----------
2ND UPDATE:
Well, seems like everything hangs, the rom is actually pretty cool and "smooth", but I've reinstalled it 3 times, only on the last try I was able to finish the initial setup, then it was all downhill, launching certain settings for the first time hang the phone for about 1 minute (example: opening mobile data settings, app permissions), trying to uninstall an app didn't work, and trying to force the uninstall thru adb froze the phone completely, although after a (forced) reboot, uninstalling apps seems to work correctly, it seems that doing *anything* for the first time hangs the phone, after trying to do something for the first time and rebooting (or letting the phone un-freeze itself, although that could take some serious time)
I'm (almost) pretty sure that this is not a problem with just my device/phone, as everything worked perfectly on past roms.
However, I'll continue to use this rom to see if it stops hanging, after the last forced reboot (after trying to uninstall an app), everything seems to be working perfectly
AngeelGod said:
Hi, after following the standard procedure to install this rom (wipe cache, system, dalvik, data), I found that the initial setup is broken if no gapps are installed, the Pixel setup crashes as soon as I hit Continue
Click to expand...
Click to collapse
That's something really strange, because rom doesn't have any "SetupWizard" or "Initial setup" included, if gapps not installed then you just boot up to home screen
Sent from my Redmi Note 5 using Tapatalk
It's awesome that my device can now run Android 9!
What works
Camera, including video recording
Phone calls
Mobile data (LTE), after adding my carrier's APN
SafetyNet passes out of the box
Bugs/issues I've faced (device-specific)
Updater crashes with
Code:
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.updates.models.Update.getDownload()' on a null object reference
at com.updates.fragments.OTAFragment$2.onResponse(OTAFragment.java:105)
at retrofit2.ExecutorCallAdapterFactory$ExecutorCallbackCall$1$1.run(ExecutorCallAdapterFactory.java:71)
Google's Sounds app crashes so I can't change ringtone or message tone (If you install Gapps don't install this!). It seems to be a graphics issue:
Relevant (think so) logcat output:
Code:
03-04 18:26:40.466 5081 5105 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 17:57:45.158 31215 32483 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
03-04 18:26:40.486 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.492 5081 5114 I chatty : uid=10080(com.google.android.soundpicker) GLThread 1090 identical 44 lines
03-04 18:26:40.492 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.492 5081 5114 W GL2JNIView: creating OpenGL ES 2.0 context
03-04 18:26:40.492 5081 5114 E GL2JNIView: Before eglCreateContext 2: EGL error: 0x3004
03-04 18:26:40.501 5081 5114 W GL2JNIView: Returning a GLES 2 context
03-04 18:26:40.502 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.505 5081 5114 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
03-04 18:26:40.517 5081 5114 I GL2 : all initialized 2
03-04 18:26:40.518 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.518 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.534 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version number unsupported
03-04 18:26:40.538 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version is followed by spurious tokens
03-04 18:26:40.542 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version number unsupported
03-04 18:26:40.542 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version is followed by spurious tokens
03-04 18:26:40.560 5081 5114 E AndroidRuntime: FATAL EXCEPTION: GLThread 1090
03-04 17:57:45.231 31215 32483 E AndroidRuntime: Process: com.google.android.soundpicker, PID: 31215
03-04 17:57:45.231 31215 32483 E AndroidRuntime: java.lang.RuntimeException: Vertex shader
03-04 17:57:45.231 31215 32483 E AndroidRuntime: OpenGL ES #version <number> is not supported.
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 0:1: '' : GLSL compile error: #version number unsupported
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 0:1: '' : GLSL compile error: #version is followed by spurious tokens
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 0:3: 'in' : Syntax error: syntax error
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 3 compilation errors. No code generated.
// ...
03-04 17:57:45.231 31215 32483 E AndroidRuntime: at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1555)
03-04 17:57:45.231 31215 32483 E AndroidRuntime: at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1270)
Sometimes my screen turns black (I'll update this when I'm able to reproduce it again when logging)
More bugs and feature requests (ROM-specific)
Icons on the notification shade are gray, they have no colors
There's no option to make the phone rotate too when it's upside down (this is included in LineageOS, not sure if the Pie one includes it)
There are no shortcuts in the lock screen to access Phone and Camera (this could be a device or Gapps bug)
Volume buttons adjust media volume all the time (Pie issue, an option to change this would be nice)
Updated ROM DL Link
Well I tried to post the updated ROM link since the first one is no longer active, but I'm a FNG, so...
Also, flashed most recent version along with 9.0 micro GAPPS. Phone kept restarting getting a little further each time. Now she's stuck on loading.
And now we're bootlooping again. Did the same with Pixel Experience 9.0. Seems I can only get Oreo to run.
Cookster128 said:
Well I tried to post the updated ROM link since the first one is no longer active, but I'm a FNG, so...
Also, flashed most recent version along with 9.0 micro GAPPS. Phone kept restarting getting a little further each time. Now she's stuck on loading.
And now we're bootlooping again. Did the same with Pixel Experience 9.0. Seems I can only get Oreo to run.
Click to expand...
Click to collapse
Same problem here
xMotoDA said:
[*] Sometimes my screen turns black (I'll update this when I'm able to reproduce it again when logging)
Click to expand...
Click to collapse
I've ran logcat just after the freeze with black screen (pressing Power doesn't turn on the screen):
https://ghostbin.com/paste/3etfc
https://ghostbin.com/paste/h6k3x
Another bug in this ROM is that every 2-4 boots Wi-Fi and mobile data don't work, and the phone gets stuck showing "Android is starting" after unlocking.
Any update on volte ?
Linus2 said:
Any update on volte ?
Click to expand...
Click to collapse
Apparently, the developer hasn't posted in a while
Still, can't you make calls without VoLTE (either using regular calls or your carrier's app)?
xMotoDA said:
Apparently, the developer hasn't posted in a while
Still, can't you make calls without VoLTE (either using regular calls or your carrier's app)?
Click to expand...
Click to collapse
NO unfortunately our carrier dosenot support calls without VoLTES CALLS are muted .
New update for harpia pushed
https://mirror.codebucket.de/cosp/harpia/COSP-190406-OFFICIAL-harpia.zip
https://mirror.codebucket.de/cosp/harpia/Changelog.txt
Hi! Obs.: I'm new in the forum, só, if i err something obvious, please, say it ,-,...
I've tested the ROM published and i loved how it's fast in boot. The problem related with boot and wifi looks not appearing more. This ROM was some personals and best performance. The camera isn't work. I rebooted 3 times and nothing. That's the unique error that i found.
I've switched so many ROM's, searching to find a ROM like these features.
The ROM is so much fluid and faster.
Good work!
w.rony said:
Hi! Obs.: I'm new in the forum, só, if i err something obvious, please, say it ,-,...
I've tested the ROM published and i loved how it's fast in boot. The problem related with boot and wifi looks not appearing more. This ROM was some personals and best performance. The camera isn't work. I rebooted 3 times and nothing. That's the unique error that i found.
I've switched so many ROM's, searching to find a ROM like these features.
The ROM is so much fluid and faster.
Good work!
Click to expand...
Click to collapse
Hi! I'm glad you liked the ROM, and yeah, the camera issues are really frequent on this device. I can't promise anything but I'll be taking a look at what's wrong and try to fix it by the late night of today (UTC -03:00).
For me, it worked, then it wasn't working, rebooted, working again.

smart lock trusted face not working

hi there, i have a redmi note 7 (global), running RR 7.0.2 on android 9. I have magisk installed and was playing around with it, adding modules that seemed interesting. Then i found this zip online for the smart lock trusted face feature so i installed it, thinking face unlocking is cool, since stock MIUI has it. After i installed it i searched around in settings to find smart lock but to no avail, so i dug up some more info and found out that smart lock had to be enabled under "trust agents". It showed up in security, but the trusted face feature keeps crashing right before the face capture screen. I've tried reflashing gapps using aroma package since i could choose what to install and that seemed cool. Didn't work, tried removing smart lock from trust agents, restarting, then enabling it again. Here's the crash report:
time: 1566930758519
msg: java.lang.UnsatisfiedLinkError: dlopen failed: library "/system/app/FaceLock/lib/arm64/libfacenet.so" needed or dlopened by "/system/lib64/libnativeloader.so" is not accessible for the namespace "classloader-namespace"
stacktrace: java.lang.UnsatisfiedLinkError: dlopen failed: library "/system/app/FaceLock/lib/arm64/libfacenet.so" needed or dlopened by "/system/lib64/libnativeloader.so" is not accessible for the namespace "classloader-namespace"
at java.lang.Runtime.loadLibrary0(Runtime.java:1016)
at java.lang.System.loadLibrary(System.java:1669)
at com.google.android.libraries.vision.facenet.FaceNet.<clinit>(FaceNet.java:67)
at com.google.android.libraries.vision.facenet.FaceNet.createFromAssets(FaceNet.java:118)
at com.android.facelock.FaceLockUtil.initialize(FaceLockUtil.java:148)
at com.android.facelock.SetupEnrollmentScreen.onCreate(SetupEnrollmentScreen.java:517)
at android.app.Activity.performCreate(Activity.java:7144)
at android.app.Activity.performCreate(Activity.java:7135)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2932)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3087)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1817)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6724)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Click to expand...
Click to collapse
I fear that it may not work for my device specifically so if anyone knows if there are alternatives to trusted face please list them.
Thank you.
Edit: And I have the solution. It seems as though trusted face is not working with magisk root installed, strange. Just did a clean flash of RR 7.0.2 and gapps and trusted face worked. But just when I installed magisk it started crashing again. Any ideas?

Categories

Resources