Zygote64 asking root permission. - Nexus 5X Q&A, Help & Troubleshooting

So today some process called zygote64 tried to access root and SuperSU prompted to allow or deny the request. This is the first time I've seen this process ever in my life.
Anyone have clue as to if it's safe or what it represents?
Google search showed some vanuralibilities regarding zygote64 but it really didn't have alot of coverage.

I got this today on my OnePlus 3 don't know what it is
---------- Post added at 02:46 PM ---------- Previous post was at 02:14 PM ----------
Accidentally granted it permission after it appeared on the initial reboot after a TWRP backup. Went back and re-restored the same backup but it didn't appear this time. Would love to find out what the heck it is.

reiichiroh said:
I got this today on my OnePlus 3 don't know what it is
Accidentally granted it permission after it appeared on the initial reboot after a TWRP backup. Went back and re-restored the same backup but it didn't appear this time. Would love to find out what the heck it is.
Click to expand...
Click to collapse
I think it must be one of the ROOT apps that we are using. See if you have any apps in common with mine.
Nova Launcher
Automate
FKUpdater ( franco kernel updater)

Tried restoring it 5 plus times and didn't see it again. I even reviewed the SuperSU logs.
Here are my root apps:
YouTube adaway
System app mover
Greenify
Amplify
Better battery stats
Ex kernel manager
Busy box pro
SuperSU pro
Flux
TWRP manager
Adaway
Root cloak
Xposed installer 3.1
Paragon NTFS HFS
Notification Slider
Sent from my ONEPLUS A3000 using Tapatalk

Did you guys manage to find out what it is?
I got this on my OP3 today.

Zygote is the display server of android. (Think X11/Xorg on Linux)
No idea why it would require root rights. (It should have the required rights by default because its a system component).
Malware infected it maybe?

tauio111 said:
Zygote is the display server of android. (Think X11/Xorg on Linux)
No idea why it would require root rights. (It should have the required rights by default because its a system component).
Malware infected it maybe?
Click to expand...
Click to collapse
Zygote is the Init process on Android, it doesnt need root to do anything... it sounds like some malware is called like that.

Update: Android 7.1.1 stock rooted. I was still asked for zygote for root permission. this time instead of it being zygote64 it was zygote. Still haven't found a solution to this. if anyone can shine a light into this.

in doubt i say Malware !!!

Yeah, I just got it today on CM14 for Find 7a December 18th build. I wasn't sure what it was so I just denied it permissions. After a quick Google search, it seems sketchy that a component of the system wouldn't already have root permission.
I also just checked SuperSU and didn't see any app that had root access denied to it, so I wonder what's actually going on here.

I ended up purging my phone and reinstalling everything.
Haven't been asked for that in 14.1. Wiped everything and flashed everything again.

one things i figured out is zygote is coming with whatsapp as since i refused whatsapp su permission by than zygote is asking for su permission .. zygote is a project is being used by whatsapp for stopping the mod or to retrive the logs to block them

I got this request on my Nexus 5x for zygote64 once the day before yesterday when I tried to switch from wifi to mobile data with a self-designed toogle from "Power Toogles", which needs root rights to do that. I did nothing and let the SuperSU message dissappear. Wifi were successfully disabled but mobile data didn't get enabled, even not after several tries. I use this buttons every day and it was never a problem to enable/disable mobile data with it.
There was no entry regarding this root request in the SuperSU logs! So I checked what happens when the root request is ignored like I did it with the zygote64 request. I removed "PowerToogles" from the allowed-list in SuperSU and tried to enable mobile data via the toogle. The SuperSU request came up (now for "PowerToolges" not for "zygote64"), I ignored it and after that I checked the SuperSU logs. There was a "Deny" entry for this request. Why is there no deny entry for the zygote64 request?
The phone is nearly new (Christmas present), and were updated to the newest Stock Android 7.1.1 one and a half week ago. I use only the Google Store to download and install apps, and the phone contains nearly the same apps which I used on my previous phone, where I never had this problem.
I'm a bit confused where this request comes from, but I don't think that it is from a adware app or something like this. I could imagine that it has to do with SuperSU and it's harmless. But I'm not an Android expert.

Yeah,
I literally just got this right now through an su prompt while listening to Spotify. At first I granted permission for it, but later went to the Su app I disabled it and found this post. Regarding its connections to WhatsApp, I recently opened up the app after a long period of time, if that has an effect, even though it's a non root app. Keep in mind I just restored yesterday's nandroid backup coming from the Nexus 5X Lineage OS 14.1 nightly build. I don't know if that has anything to do with it as well as me changing my ElementalX kernel profile to Ghost pepper. That's all lol I'm not trying to get hacked.

I have this one too on xiaomi's miui 7.1.19 and no WhatsApp at all.
C:\Windows\System32>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ ps | grep zygote
root 453 1 6528 1288 __skb_recv 0000000000 S zygote
root 665 1 2143808 60040 poll_sched 0000000000 S zygote64
root 672 1 1579612 32724 poll_sched 0000000000 S zygote
root 2872 672 36072 2364 futex_wait 0000000000 S xposed_zygote_service
[email protected]:/ $
Click to expand...
Click to collapse
Does dirty flash of the ROM replaces the zygote files (and I remove xposed beforehand, then reinstall expose later on)
---------- Post added at 12:30 PM ---------- Previous post was at 12:10 PM ----------
I restarted the phone and zygote64 no longer appears in supersu's log...

I've been seeing this over the last couple days, and never approving it. It seems "spontaneous" in that it's not related to UI-driven activity.
(I'm running OmniROM 7.1.1 with very heavily trimmed GApps, no XPosed framework in place)
I only see "zygote64" in the SuperSU apps, and nothing in the SuperSU logs.
The hints I have so far are:
Code:
bullhead:/ # ps | fgrep 64
[...]
root 491 1 2140052 26968 poll_sched 786e1c9cc8 S zygote64
[...]
u0_a64 1364 491 1578476 38536 SyS_epoll_ 786e1c9ba8 S com.teslacoilsw.notifier
[...]
Given the number of process with ppid of 491, and that pid 492 is "zygote", I've got to think that "zygote64" is the 64-bit parent process for apps.

Just got this too (zygote64). Running 6.0.1 cause I love xposed. So this shouldn't be related to the OS.
Recently started getting same requests from com.android.settings which is my settings app. Been on the sand Rom without updates or dirty flashes since November (Running buttery-smooth with N-ify and other modules.) And this is the first time I get this request.
Thus, I can safely make the assumption that we got a potential virus...
Edit: I'm on a 6P and when I denied access to both settings and zegote64, I had no differences in phone operation. No "failed to switch from Wi-Fi to Data" like oth3rd are claiming. So I'm just going to keep rejecting until we get a firm details on what that thing is
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
Gonna run a log cat until I get home, where I'll look more into it...

jeffsf said:
I've been seeing this over the last couple days, and never approving it. It seems "spontaneous" in that it's not related to UI-driven activity.
(I'm running OmniROM 7.1.1 with very heavily trimmed GApps, no XPosed framework in place)
I only see "zygote64" in the SuperSU apps, and nothing in the SuperSU logs.
The hints I have so far are:
Code:
bullhead:/ # ps | fgrep 64
[...]
root 491 1 2140052 26968 poll_sched 786e1c9cc8 S zygote64
[...]
u0_a64 1364 491 1578476 38536 SyS_epoll_ 786e1c9ba8 S com.teslacoilsw.notifier
[...]
Given the number of process with ppid of 491, and that pid 492 is "zygote", I've got to think that "zygote64" is the 64-bit parent process for apps.
Click to expand...
Click to collapse
It's highly unlikely that you will see whatever is asking for in the process list as it may quit once it gets access denied.
Extending the prompt time may give you a chance to connect the device to your PC and use adb shell to look for it, but seeing as it occurs spontaneously I doubt you will catch it on time.
The only thing you may look for elsewhere is a app_process32 or app_process64 file, which is the actual name of the zygote binary (zygote is the service's name)
Also, per init.zygote64_32.rc, both versions of the service should already run as root, and unless this is a bug; which could be possible if somehow app_process32 or app_process64 do not recognize their parent (the one started by init) and tries to restart as the new parent.

I just saw this popping up on my phone and started scouring the net which brought me here. Anyone yet know exactly what this is?
---------- Post added at 08:46 AM ---------- Previous post was at 08:14 AM ----------
I denied it super user permissions though, and nothing seems to be broken. I just remembered I updated whatsapp and gbwhatsapp few hours ago.

Hi, I have the same thing going on on my phone. And I can tell so far that it has absolutely nothing to do with WhatsApp as I never ever had WhatsApp or any Facebook related app installed on my phone. I even hadn't installed any app for a longer time before the first appearance. Maybe there is another way of infection (if it is a malware).

Related

Root 4.6.3...

Kingroot 4.5 form here works perfectly on fire os 4.6.3 (and it's in English now). If you think knigroot permission manager is annoying, you can replace it with SuperSu following the instructions here.
Just out of curiosity, Does anyone know what exploit kingroot uses to gain root on fire phone? I know they use several exploits from here and there, but I'm not sure which one.
I keep getting a failure. Even restored settings and still fails... bummer. 4.6.3 auto installed and removed my root, etc...
---------- Post added at 11:27 PM ---------- Previous post was at 11:01 PM ----------
Took a few tries, but think I got the trick.
1. Restore to 4.6.3
2. Enable usb debugging from Settings
3. IMMEDIATELY load ES File Explorer (and register your Phone through the normal process, don't skip and then do it from the App Store app)
4. Load KingRoot to the Downloads folder
5. enable 3rd party application installs in preferences
6. Install kingroot
7. Reboot
8. Run Kingroot
Worked for me.
Well, I never registered with amazon, Just sideloaded Google play and installed everything trough there. Anyway, Kingroot worked every time I tried. Maybe some problem with your internet connection?
I updated mine from 3.5.1 to 4.6.3, rooted with KingRoot 4.5 and then installed Super-Sume, didn't even reboot after KingRoot....but it seems to be working....now just gotta get Google Play installed
This also worked great on 4.6.4!!!!!!!!!!!!!!!!!!!!!!!!! THANK YOU!!!!!!!!!!!!!
Where?
plympton said:
I keep getting a failure. Even restored settings and still fails... bummer. 4.6.3 auto installed and removed my root, etc...
---------- Post added at 11:27 PM ---------- Previous post was at 11:01 PM ----------
Took a few tries, but think I got the trick.
1. Restore to 4.6.3
2. Enable usb debugging from Settings
3. IMMEDIATELY load ES File Explorer (and register your Phone through the normal process, don't skip and then do it from the App Store app)
4. Load KingRoot to the Downloads folder
5. enable 3rd party application installs in preferences
6. Install kingroot
7. Reboot
8. Run Kingroot
Worked for me.
Click to expand...
Click to collapse
Where in Settings do I find Enable USB Debugging?
jude525 said:
Where in Settings do I find Enable USB Debugging?
Click to expand...
Click to collapse
About device. Press any of those option 5-10 times until dev options shows up.
absolutely working fine, no need to do any steps, i just install the app n run and with in 22% it says root status accomplish
Thank u for the info
Which apps can I remove and how can imake sure that my Google services always work and no headaches

Tips, Tricks, and the Root!

Please Read: I am making this post to help my fellow hd 8 & hd 10 kindle users out with things I have found working and useful to me that I got working with my kindle. Please remember that doing this stuff can be dangerous unless you know what you're doing. Enjoy my findings!
Ready to ROOT your device?!
Follow these step's and I'll try making this as simple as possible.
Step 1. First we're going to install adb and get shell command working. This youtube video is probably the best visual way of getting it done. Only watch 3 minutes and 37 seconds of it, Skip the rest of the video. Click HERE. (give him a thumbs up for making the video).
Now open up Command prompt and type
Code:
adb devices
It should show a 16 digit serial key with "device" to the right. SUCCESS!
Step 2. Now let's run RootJunky's script. Download and extract the files, Click HERE. Run "1-Install-Play-Store.bat" file and let it load. It should list your device serial key and load up to the main menu page. Follow the order on the menu from 1 to 4. Now this was made for the fire hd 7" tablets but some of it works and some might not, I had a problem with ads loading up on lockscreen but found another way to disable them which is under "Disabling Amazon Services" down below.
Step 3. Let's get ROOT! We are going to install KingRoot and run it, kingroot will also install purify which is a nice handy program but you can remove it if you want later on. Now once you run KingRoot its going to search for the best possible method to root your device, it may or may not find a way but there should be a second option to install root. Do it. Some people have found that you may have to try multiple times to root to get a success or try updating the google framework through the play store. (My google framework is V4.4.4-1227136)
I have attached the kingroot apk down below or you can download kingroot from there website. Click HERE. (If you have any problems please post it and we may be able to help.)
Now let's disable some thing's we may find useless..
Disable the lockscreen
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
Code:
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
Code:
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
Disable Amazon's FireLauncher and replace it with Google Now Launcher
Note:
Load up ES Explorer, make sure it has root enabled in settings.
Before you run this command please download a new launcher and either install it normally or you can copy the apk file into the "system/app" folder and chmod the app to "-rw -r -r" in properties. Once the apk file is in the "system/app" folder, you can either install it from that location or disable Fire Launcher, reboot, and the app should auto install and load.
*Installing Google Now Launcher requires Google app from marketplace(Link below). Now Launcher allows you to use widgets. If you use Google now launcher please keep a back up launcher like nova launcher just in case until you get now launcher working. Google now launcher is tricky.
Open Command Prompt.
Type in "adb shell". Then type in "su".
Then type into command prompt,
Code:
pm disable com.amazon.firelauncher

After reboot if you get no launcher don't worry. Just enable firelauncher and install a new launcher(IE nova launcher) and then disable firelauncher. (Try updating the google framework.)
*To Re-enable, replace disable with enable.
*Don't forget to type in "exit" into command prompt twice when you are done and or before unplugging your usb.
Disable Amazon's OTA(over the air) updates
Go in to ES Explorer(set root access).
Now in ES Explorer go to system/etc/security
locate "otacerts.zip" and I made a copy of it and renamed it to "otacerts.zip.backup" just in case i needed it.
AND..
Now in Command Prompt, type "adb shell", type "su".
Then type into command prompt,
Code:
Pm disable com.amazon.device.software.ota
Pm disable com.amazon.settings.systemupdates
Hopefully this disables all the updates! Enjoy!
Google Play Store not working?
Solution 1. (¿GotJazz?)
Open up Kingroot's Purify app.
Try putting Google Account Manager and Google Services Framework on the Purify Whitelist.
Solution 2.
Load up Command Prompt.
Then type in "adb shell". Then "su".
Code:
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
You will not get a notification that it worked but it does.
Open Google Play or Reboot device. If that doesn't work, read on..
Solution 3.
Re-install Google applications
Go into system settings >> apps & games >> manage all applications
I then went into every google application(this will help remove any settings saved and email addresses) and cleared the data and cache of each app.
After that was done, I then uninstalled each of these apps,
"Google Account Manager, Google Play Services, Google Play Store, and Google Services Framework".
After uninstalling those, run the rootjunky's script(link located below) and install the play store which is option 2 I believe.
Also remember to turn off google play store auto updates!
Disabling Amazon Services
Start up Command Prompt.
Type in "adb shell". Then "su".
Then type into command prompt.
Code:
pm disable (app name(IE. com.amazon.ags.app))
*To Re-enable, replace disable with enable.
List of Amazon apps that are okay to remove.
Code:
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.geo.mapsv2.services
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.parentalcontrols
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedshare.actionchooser
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.amazon.webview
com.amazon.windowshop
com.amazon.pm
com.amazon.recess
com.amazon.socialplatform
com.amazon.zico
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Optional
Don't have prime? Please continue + more.
Code:
com.amazon.mp3 -amazon music player
com.amazon.mw -removes the firefly cam app
com.amazon.mw.sdk -part of the firefly app?
com.amazon.avod -amazon video app, i don't have prime, useless to me..
com.amazon.kindle.personal_video -the amazon/system video app, I replaced this with mx player.
com.amazon.csapp -amazon help app
com.amazon.application.compatibility.enforcer -not sure what this does
com.amazon.android.marketplace -amazon marketplace
com.amazon.camera -stock camera app, install a new one from play store
com.amazon.dynamicupdationservice -not sure what this is or if this is part of amazon updates
com.amazon.platform.fdrw -part of amazon app & services?
com.android.contacts -remove, no reason for contacts, up to you
com.android.calendar -android calender
com.android.deskclock -remove if you don't need alarms/clocks/timers/etc
com.kingsoft.office.amz -not sure what this is yet but im sure its useless
com.nuance.swype.input -yup, unless you like swype
jp.co.omronsoft.iwnnime.mlaz -not sure what this does?
*Don't forget to type in "exit" into command prompt twice when you are done and or before unplugging your usb.
Links:
Changing the DPI(HERE).
Google App v5.9.27.19.arm(300600996)(HERE).
Replace KingRoot with SuperSU(HERE).
Rootjunky's install play store script(HERE).
Contributors:
madsc13n41s4, sd_shadow, Selexo
Downloaded kingroot apk, installed, tried root twice, confirmed via superuser from chainsDD, backed up special offers from titanium backup, uninstalled special offers, great fully rid of ads on my lockscreen.
madsc13n41s4 said:
Downloaded kingroot apk, installed, tried root twice, confirmed via superuser from chainsDD, backed up special offers from titanium backup, uninstalled special offers, great fully rid of ads on my lockscreen.
Click to expand...
Click to collapse
Does your wallpaper on the lockscreen change? I have yet to look into getting it changed, about to look in to a new lock screen as well. Also don't forget to stop ota updates from amazon.
EDITED MAIN POST. Will add more soon.
kanderson88 said:
Does your wallpaper on the lockscreen change? I have yet to look into getting it changed, about to look in to a new lock screen as well. Also don't forget to stop ota updates from amazon.
Click to expand...
Click to collapse
Yeah, its not the default wallpaper, and changes on its own with generic backgrounds. Did forget about ota, powering off until I have the time, I'm elbows deep in a Ford Probe project for the time being. Thanks so much for finding this, hopefully I get time to really contribute soon. Glad to confirm
madsc13n41s4 said:
Yeah, its not the default wallpaper, and changes on its own with generic backgrounds. Did forget about ota, powering off until I have the time, I'm elbows deep in a Ford Probe project for the time being. Thanks so much for finding this, hopefully I get time to really contribute soon. Glad to confirm
Click to expand...
Click to collapse
You're very welcome sir. So happy I found out that kingroot worked. I am currently looking into getting a new lock screen and once I post my findings I'll let y'all see as well as changing the lock screen wallpaper. As well for the fixing google play store I am still currently having problems after that adb command, it worked for a good minute longer than usual.
kanderson88 said:
You're very welcome sir. So happy I found out that kingroot worked(credit). Anyways I am currently looking into getting a new lock screen and once I post my findings I'll let y'all see as well as changing the lock screen wallpaper. As well for the fixing google play store I am still currently having problems after that adb command, it worked for a good minute longer than usual.
Click to expand...
Click to collapse
I would install an opengapps.org package with FlashFire (Arm, 5.1.1, nano or pico)
Flashfire will install Google framework and extra support files, that should allow playstore to work better.
should work fine, but no guarantees
How to Use FlashFire App
Sent from my KFFOWI using XDA Labs
sd_shadow said:
I would install an opengapps.org package with FlashFire (Arm, 5.1.1, nano or pico)
Flashfire will install Google framework and extra support files, that should allow playstore to work better.
should work fine, but no guarantees
How to Use FlashFire App
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yeh I need to look into flashfire, I used rootjunky's script to install it. Thanks for the idea, I'm gonna check it out.
I don't think I am going to use flashfire. Seems really risky of bricking me device. I'm going to try installing the apps manually or through adb. I'll keep doing some research on flashfire though. Thanks
kanderson88 said:
You're very welcome sir. So happy I found out that kingroot worked(credit). Anyways I am currently looking into getting a new lock screen and once I post my findings I'll let y'all see as well as changing the lock screen wallpaper. As well for the fixing google play store I am still currently having problems after that adb command, it worked for a good minute longer than usual.
Click to expand...
Click to collapse
Yeah, I had to cobble together my own Play Store solution. The differences in the versions of the apks used together really matters it seems. Luckily, I haven't had any issues since I got it running. I would highly recommend turning off Play Store automatic updates as App Store versions of certain apps are intentionally out of date as per compatibility. Eg, Facebook.
Holy crap opening up TB I can not wait until someone comes up with a list of **** thats safe to freeze/remove, so much amazon crap on this thing!
madsc13n41s4 said:
Yeah, I had to cobble together my own Play Store solution. The differences in the versions of the apks used together really matters it seems. Luckily, I haven't had any issues since I got it running. I would highly recommend turning off Play Store automatic updates as App Store versions of certain apps are intentionally out of date as per compatibility. Eg, Facebook.
Click to expand...
Click to collapse
Thanks didnt think about stopping the auto updates.
Smart move. Thanks.
mikek9 said:
Holy crap opening up TB I can not wait until someone comes up with a list of **** thats safe to freeze/remove, so much amazon crap on this thing!
Click to expand...
Click to collapse
What a great Idea, I will make a list of some things. Give me a day. Bed time.:crying:
mikek9 said:
Holy crap opening up TB I can not wait until someone comes up with a list of **** thats safe to freeze/remove, so much amazon crap on this thing!
Click to expand...
Click to collapse
This is what I've safely removed so far, leaving Prime included services.
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.android.contacts
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Google Now Launcher doesn't start with Fire Launcher enabled/installed, but takes right over when disabled/uninstalled.
madsc13n41s4 said:
This is what I've safely removed so far, leaving Prime included services.
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.android.contacts
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Google Now Launcher doesn't start with Fire Launcher enabled/installed, but takes right over when disabled/uninstalled.
Click to expand...
Click to collapse
Thanks for this. I'll consider when and if i make a cleaned up ROM/Bin
Yeah you must hide fire launcher through adb in order to use any launcher. Thanks for the list. I've been trying to figure out how to disable the lock screen all day and it seems impossible. Idk but maybe someone someday will provide a modified settings app. Idk.
madsc13n41s4 said:
This is what I've safely removed so far, leaving Prime included services.
com.amazon.ags.app
com.amazon.cloud9
com.amazon.cloud9.kids
com.amazon.dp.contacts
com.amazon.dp.fbcontacts
com.amazon.firelauncher
com.amazon.geo.client.maps
com.amazon.geo.mapsv2
com.amazon.kcp.tutorial
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kor.demo
com.amazon.photos
com.amazon.photos.importer
com.amazon.tahoe
com.amazon.unifiedsharefacebook
com.amazon.unifiedsharegoodreads
com.amazon.unifiedsharesinaweibo
com.amazon.unifiedsharetwitter
com.amazon.webapp
com.android.contacts
com.audible.application.kindle
com.audible.application.store
com.goodreads.kindle
Google Now Launcher doesn't start with Fire Launcher enabled/installed, but takes right over when disabled/uninstalled.
Click to expand...
Click to collapse
Did this show any improvements on the operating system? IE faster loading, battery power, etc etc..
What I'd like is as near as pure android as possible. So the more input the better.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Try freezing apps like those listed. Report back
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
None of those apps look crucial to me. Get rid of them, let me know here.
technope said:
What I'd like is as near as pure android as possible. So the more input the better.
Click to expand...
Click to collapse
I agree, I don't know if i want to completely get rid of the fire os just in case and possibility of bricking when booting up a new rom and plus no boot image yet.
None of those apps look crucial to me. Get rid of them, let me know here.
Click to expand...
Click to collapse
Will do
Don't forget
"com.amazon.mp3" and replace with different music app
"com.amazon.mw" removes the firefly cam app.
"com.amazon.avod" -amazon video app, i don't have prime, useless to me..
"com.amazon.kindle.personal_video" the amazon video app, i replaced this with mx player.
"com.amazon.csapp" amazon help app
I disabled them all, ill keep you updated if i see a performance boost or battery boost.
Freshened up the main post! Hope its more readable.
Also note, multiple user profiles seem to break with the disabled apps in my list, personally believe it to be Fire Launcher's fault, probably responsible for handling the switch over, but I don't know too much about 5.1.1
madsc13n41s4 said:
Also note, multiple user profiles seem to break with the disabled apps in my list, personally believe it to be Fire Launcher's fault, probably responsible for handling the switch over, but I don't know too much about 5.1.1
Click to expand...
Click to collapse
can you try disabling all those but leaving firelauncher enabled? lets see if it gives you error's, if it doesnt, instead of disabling firelauncher, use the hide command instead of disable and see if that works. I would like to know what app is in charge of multiprofiles..
Please look at section for disabling amazons ota updates, added more to it! Thanks.

Regretting my purchase

Okay Sso I've just ordered the lenovo p2. I was looking for a mid-range/budget phone under the £200 price mark and found this and several others. After checking and comparing the phones in this range, I decided to buy this (even though the camera is pretty rubbish). Now upon further investigation, I've noticed that this phone isn't as polished in terms of glitches. There's a lip sync issue and notification issues that keeps on coming up wherever I look as well as several other issues. Most of the fixes for these issues are pretty much either work or don't so I don't want to end up with a phone that has glitches. Could someone list their experience with this phone and any pros and cons.
TwilightLoz said:
Okay Sso I've just ordered the lenovo p2. I was looking for a mid-range/budget phone under the £200 price mark and found this and several others. After checking and comparing the phones in this range, I decided to buy this (even though the camera is pretty rubbish). Now upon further investigation, I've noticed that this phone isn't as polished in terms of glitches. There's a lip sync issue and notification issues that keeps on coming up wherever I look as well as several other issues. Most of the fixes for these issues are pretty much either work or don't so I don't want to end up with a phone that has glitches. Could someone list their experience with this phone and any pros and cons.
Click to expand...
Click to collapse
Update to nougat bro and issue will be fixed
reality1234 said:
Update to nougat bro and issue will be fixed
Click to expand...
Click to collapse
Im in the UK and not sure if we have received the update over here yet.
Yes just update to nougat and enjoy.
I haven't regretted buying this phone one single bit.
It's a great phone and amazing phone once you factor in the price!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
There is an official update but they pulled it for the time being (there are still a couple of issues). It's still better than MM and you can download and put the update.zip on the SD card to update it manually.
philje123 said:
Yes just update to nougat and enjoy.
I haven't regretted buying this phone one single bit.
It's a great phone and amazing phone once you factor in the price!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
There is an official update but they pulled it for the time being (there are still a couple of issues). It's still better than MM and you can download and put the update.zip on the SD card to update it manually.
Click to expand...
Click to collapse
MM?
Do I have to root the phone just to update it manually?
No, you don't have to root to update it.
The lip sync issue can be fixed by updating to Nougat and resetting the phone to factory defaults after updating it.
The notification "lag" issue can be fixed by executing a adb dumpsys command to disable doze.
MrColdbird said:
The notification "lag" issue can be fixed by executing a adb dumpsys command to disable doze.
Click to expand...
Click to collapse
And how would I do that?
No problems here... Probably some mistake from your side... The sync issue was resolved in nougat AFAIK.
TwilightLoz said:
And how would I do that?
Click to expand...
Click to collapse
adb shell dumpsys deviceidle disable
yes i have also purchased from 3 UK and all issues are resolved with Nougat update which you can do manually. It also enables Volte so it works properly. Just follow the manual update for Nougat thread.
So the notification lag isn't really the Lenovo P2's problem?
edit: perhaps it really isn't https://www.reddit.com/r/Nexus6P/comments/3qsgue/yes_doze_will_delay_your_social_media/
Doze is a disease, but yes, it's not the P2's fault.
Bigger shot smartphones like the OnePlus 3 also suffer from this "bug".
Doze is worthless it doesn't even save battery for the most part. It just delays notifications. Yes that's what it does. It's a plague on many phones.
how to disable it?
No issues here.
MrColdbird said:
The notification "lag" issue can be fixed by executing a adb dumpsys command to disable doze.
Click to expand...
Click to collapse
What is this "lag" you speak of?
Is this the lag like -
When Im playing spotify and stopped and cleared it from recents I'll have some notification in the status bar
like the first song i played then after display. Notification is gone. is that it??
sam00561 said:
how to disable it?
Click to expand...
Click to collapse
adb shell dumpsys deviceidle disable
Needs to be done after every reboot as it doesn't stick.
Also needs to be noted that this command can be made to auto execute when the hosting app is given android.permission.DUMP rights via adb, or if the executing app has root rights.
I coded myself a minimalistic app, requested and granted it android.permission.DUMP and auto start rights and let it handle the command execution for me, essentially disabling doze permanently on my P2.
Things have been a breeze since then.
MrColdbird said:
Also needs to be noted that this command can be made to auto execute when the hosting app is given android.permission.DUMP rights via adb, or if the executing app has root rights.
I coded myself a minimalistic app, requested and granted it android.permission.DUMP and auto start rights and let it handle the command execution for me, essentially disabling doze permanently on my P2.
Things have been a breeze since then.
Click to expand...
Click to collapse
Care to share in PM?
Skickat från min iPhone med Tapatalk
I think the following helps. Credit goes to JasonMR and [MENTION=487946]manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxDMCRH9QxV7aUQyalpZQ2JudGc/view?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0BxDMCRH9QxV7YVA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to [MENTION=487946]manototh for putting this together originally.

Galaxy Note 10.1 (2014 Edition) P-605 Official LineageOS

I downloaded and installed official LineageOS to my Galaxy Note 10.1 (2014 Edition) P-605 from
https://download.lineageos.org/lt03lte
Install TWRP Recovery
Install latest downloaded file from the link given above
Install open gapps (mini)
Everything working fine except
Usb MTP connection is not working
On boot Setting app closes
Less battry life than the stock rom
MTP connection issue is a huge problem for me. Do anyone know a fix? I searched everywhere and couldn't find anything
I confirm all the above issues with the nightly build 2018-02-22.
Let me add another (serious) one: if you encrypt the storage, every time you reboot a bunch of applications go in restart loop, until eventually the device restart. This is basically a bootloop. I will try to wipe cache and dalvik and restart to see if the problem persists.
I'm not used to rant just for the sake of, also considered the amazing work devs do, but this time I'm a bit pissed. I bought this tablet specifically because it is listed in the "Lineage OS supported devices" list. It would be nice to put a big disclaimer if the current build has so many crippling issues.
---------- Post added at 10:39 AM ---------- Previous post was at 10:16 AM ----------
That's annoying... TWRP does not manage to decrypt the storage partition... So I'm pretty much screwed.
I will try to format the storage to remove the encryption, and then re-install the latest Lineage nightly using either adb sideload or a micro-USB pendrive.
OK, kind of works. I started TWRP recovery and formatted all the device (removing encryption), then copied back the lineageOS (I used the last nightly, 2018-02-22) and addonsu zip files using a microUSB stick. Reinstalled everything. It works, the only annoying thing is that by formatting the sdcard I lost the backup I had previously done with TWRP of the original firmware, but that's fine, I was not planning of using it anyway.
- enabled USB debugging, root apps+ADB, enable third-party apps
- added F-Droid repo
- downloaded CryptFS from F-Droid
- Settings -> Security -> set up a temporary password for screen unlock
- Plugged in tablet, Settings -> Security -> encrypt device (using the temporary password above)
- reboot, this time seems to work (modulo the usual annoying "settings app has stopped working" one-time popup)
- changed encryption password with CryptFS (requires root of course)
- Settings -> Security -> changed screen unlock to a normal PIN
Everything seems to work so far: the device asks for the long decryption password at boot but only short PIN to unlock screen.
Planning to install WrongPINshutdown now, to complete anti-theft security setup.
So far so good, except ADB still doesn't work. Keeping a close eye on battery usage.
Coming next:
- testing whether TWRP can decrypt storage
- making sure at least LineageOS can mount USB drives... since MTP doesn't work it would be annoying having to use network or ADB to transfer large files...
---------- Post added at 01:17 PM ---------- Previous post was at 12:59 PM ----------
Babality!
- TWRP still cannot decrypt storage, does not even ask for the passphrase, just does not see the partition
- after trying the above, somehow the encrypted partition header got screwed: if I start Lineage OS, when I'm prompted for the passphrase. I always got "wrong password". Either using the "right" password, or using the old temporary password I used before, or the current device PIN, nothing: everything is "wrong password".
I'm reinstalling everything again and do a couple of final tests before giving up and forgetting about encryption.
I suspect this might be an issue of TWRP. I'm using version 3.0.2-0. I'm installing now the latest version (3.1.1-0) and see if things change.
Also, coming next MTP test.
---------- Post added at 01:37 PM ---------- Previous post was at 01:17 PM ----------
TWRP 3.1.1-0 bootloops tablet... I have to start from Odin again.
F**k all this s**t, my next device's gonna be an Apple :angryface:
I managed to make the double-encryption work: now when I boot the tablet it requests the passphrase, but to unlock the screen just a PIN (however, Wrong PIN Shutdown powers off the tablet after a few wrong PIN trials).
I'm not entirely sure how I did it to be honest, but I suspect the reason is the following: the encryption of the tablet can only be done by setting up a password for screen unlock at first.
Then you use Cryptfs to change the encryption password.
Then you change the screen protection option to "PIN" instead of password. If you are running one of the latest Lineage OS builds, when you are asked "do you want to require a PIN also at boot?", counterintuitively, answer "yes".
THEN you must run Cryptfs again and re-set the storage encryption password. This way it works.
I did not dare starting TWRP again in recovery mode , I'm afraid it would mess up with the encryption.
Keeping an eye on the battery: it's pretty bad to be honest. I was used to my beloved Lenovo tablet, I was using it only as a PDF reader (flight mode, uninstalled all the crap etc) and, with the stock firmware, it had pretty much the same battery life of a real Ebook reader, I could easily leave it in the closet for weeks and find it still charged when I needed it. This Galaxy Note 10.1 is not even close with Lineage 14.1, now I killed all the unnecessary processes and set battery mode to maximum span, let's see if it gets better.
After a few days of test I can confirm poor battery life. Less than two days in complete standby, flight mode, energy saving mode. That really sucks.
I have to add: SIM card not recognized, only WiFi works.
TL;DR: do not install this ROM.
Did anybody test the official LineageOS build for the SM-P605 (lt03lte) ?
Is it working by now?
Has anybody an old (Octobre or Septembre) version of the official LinageOS for SM-P605 (lte03lte)? Unfortunately after the decision to no longer maintain that ROM all older downloads have been deleted and I have some problems with the december version

app settings delete when lineageos reboots

I'm not 100% certain it only happens when I reboot, but that's one method of repeating the bug. I know it's not the only way, but it's one repeatable way that I know.
So, after I reboot all the settings of most every app that I have is deleted. For instance, in the newpipe download section there is nothing, but when I open my file explorer the videos I downloaded still exist. Fito Track records my workouts fine ,but then upon reboot the entire apps settings need to be reinstated. I have to reset my login information into K-9 Mail app. F-Droid keeps needing to update repositories everytime I open it. Nearly every app I have installed has this issue, except KurobaEx.
/storage/emulated/0/Android/data is not accessible. No idea if that's relevant or not, as it was accessible when I had AndroidOne installed.
Also, notifications keeps mentioning SELinux is not enforcing your security has been weakened. I don't know if this has anything to do with the problem, but just pointing it just in case.
Nokia 7 Plus with LineageOS 19.0
Edit:
I tried:
Code:
chown -R <user>:everybody /storage/emulated/0/*
As root, but nothing happened. Permissions stayed the same.
Also, my sdcard does not show in the file manager. When I first installed lineageOS I accidentally cancelled the formatting process.

Categories

Resources