Solved! Battery Drain On Note 2 after 4.3 update. - Galaxy Note II Q&A, Help & Troubleshooting

Alright folks, I think I have finally managed to solve the battery drain problem after the 4.3 update, thank God!
The bad news is that it cannot be done without your phone being rooted. So root the phone in the following manner: 1) Install "Kingo Android Root" to you PC. It will not root your phone without following the other steps.
2) Install "System App Remover" (the one by Jumobile) from play store. The app will be installed as a different name, as "Uninstall". I tried "All-in-One Toolbox" too but it coudn't find all the files listed below (namely KLMS Agent). So I had to install this one and try again.
2.1) Install "Root Checker Basic" from play store.
3) Go to Menu>Settings>More>App Manager>All and force stop the apps:
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
Security policy updates
KNOX
KNOX -- (Yes we have two of them! One is to install Knox interface other one is the one that is already running without installing the other one.)
Knox Notification Manager
KNOX Store
KLMS Agent
In total we have 8 files (or actually apps) to close. You may have 7 of them if you don't have Security Principle Update.
Some of these will not gonna allow you to force stop, never mind, just close the ones that you can.
4) (Now you have to be quick because somehow these apps restart themselves.) Connect your phone to your PC and run Kingo and click root then follow the instructions on your pc screen. Your note 2 will restart and will be rooted.
5) Disconnect your phone.
6) Run "Root Checker Basic" and click "verify root access" and see if you are rooted now. (You should be rooted.)
7) Install "SuperSU" from play store.
8) Run "uninstall" (which we obtain by installing "System App Remover" (the one by Jumobile)). SuperSU will ask for root permission for uninstall, approve it. Uninstall will provide you a list, choose all the apps listed above and uninstall them. KLMS Agent will not be in the list and you should use the search option of the app. If for any reason you don't see any other app in the list search and uninstall! YOU SHOULD DELETE ALL 8 FILES!
9) Restart your phone.
After you remove all the Knox bloatware and anything else you don't like, install Lucky Patcher.
This is usually used to remove licenses from pirated apps, But it also does something else which we will need to use:
It removes Google ads! And these are that keep our phones awake.
In the faulty 4.3 Samsung update apps with Google Ads always try to connect and sync thus keeping the phone awake.
In Lucky Patcher go into each app individually and choose "Remove Google ads".
Then choose "Patch to remove Google ads" and press "Apply". Rarely will you have 100% success but it doesn't matter.
Then repeat the process and this time press "Disable Ads Activities" and press each activity that is used for advertising (They are usually in orange colour).
One more useful step is to use Greenify to hibernate almost all processes except the ones that need to sync eg Dropbox.
My phone used to have 65-85 % wake time after the update. Now it's only 3% wakelock instead of the 65-85% that was before and the battery only went down to 98% from 100% in 2.5 hours! Battery life is even better than on 4.1.2.
If for some reason after a few days (or even hours) the problem returns, then it could well be an app that causes it, or a combination of apps. In my case it was Automatic Call Recorder by App.liqato (Appstar Solutions). an app that was working fine on 4.1.2 but not on 4.3. It was the last app to be installed, that's why I knew. I uninstalled it and batery life is back to normal after it had gone mad for a couple of hours. Notice that no wakelock app showed it as the culprit. I only knew because after I had done a factory reset I installed all my apps one by one and not from a backup and I forgot this one. I remembered a few days later and when I installed it the drain started.

Related

[Q] Struggling to un-install non-system apps

I first noticed this problem last week - the phone is '3' branded (UK), un-rooted, running the stock firmware.
If I install an app from the Market and then subsequently try to un-install it via any of the usual methods (App settings, drag un-install from the apps screen), the un-install process just sits there showing a progress bar. CPU usage goes up (e.g., 50% on 2 cores) and the phone gets hot. The application, however, does not get removed. If I then try to use ADB to remove the app, the process never returns.
If I reboot the phone and try ADB to un-install again, the app does actually get removed.
Anybody know what's going on here? It's kind of annoying to have to reboot the phone and use ADB whenever I want to remove an app.

[Q] How to delete downloaded system update and prevent future updates/notifications?

Im still on KitKat and want to stay that way, but my N7 has automatically downloaded Lollipop and has the notification to install. How can I remove this notification, delete this update to free up space, and prevent it from happening again?
I know this must have been covered someplace else, but Ive spent the last 20 minutes searching and havent found a definitive answer....
Thanks!
I got this from some thread here.
Depends if you are rooted or not.
If rooted, you need to disable 3 receivers. To do so use one of the apps:
Autorun Manager, or
Autostarts (free in F-Droid).
The 3 receivers to disable :
service:com.google.android.gms.update.SystemUpdateService$Receiver
(this will run on boot competed).
com.google.android.gms.update.SystemUpdateService$ActiveReceiver-
(this will check for OTA on connectivity change).
com.google.android.gms.update.SystemUpdateService$SecretCodeReceiver
(this will check for OTA when your phone "handles" the secret code).
.........
If not rooted, I "think" you can go to
Settings / apps
Go to All tab
Select "Google Play Services" and unselect "show notifications".
This second method has some disadvantages but I don't remember what they are.
Hope this helps.
I'm in autostarts and seemingly have all of these disabled (I am rooted) as seen in the screenshot, but still getting the update notification (as also seen in the screenshot).
Thoughts?
https://www.dropbox.com/s/d25qshnu8w4hb6d/Screenshot_2015-01-21-16-05-18.png?dl=0
Bump for an answer. Would like to know this too
I found this yesterday:
Download System Tuner, free from google play (https://play.google.com/store/apps/details?id=ccc71.pmw&hl=en)
Open App
Click Startups
Navigate to Google Play Services - If you do not see this in the list, press add in the bottom right hand quarter and navigate to it
press and hold over Google Play Services
Press Open
Press Details
Press Activities
Navigate to update.SystemUpdateActivity and uncheck it
restart phone
This did the trick for me. I am unsure whether this also removes other notifications from google, but it certainly got rid of the annoying "system update downloaded" notification.
Or better still if you are using xposed framework download the NotifyClean module. Let the Update System notification appear after a reboot and then select it in NotifyClean to get rid of it. Brilliant!
m+a+r+k said:
Or better still if you are using xposed framework download the NotifyClean module. Let the Update System notification appear after a reboot and then select it in NotifyClean to get rid of it. Brilliant!
Click to expand...
Click to collapse
Unless I'm mistaken, all this is doing is hiding the notification. While that's great, the notification currently says "System update downloaded", so my assumption is space is being taken up by this download which I'd really like to clear up.
With the issues many have reported running Lollipop on the N7, I'm really surprised there isnt a common, well known process for this.
Then try my message #5 above.
m+a+r+k said:
Then try my message #5 above.
Click to expand...
Click to collapse
That's more or less the same thing... just disabling the notification. Also interested I'm how to delete the existing download.
timofcourse said:
That's more or less the same thing... just disabling the notification. Also interested I'm how to delete the existing download.
Click to expand...
Click to collapse
The download is in /cache.
_MetalHead_ said:
The download is in /cache.
Click to expand...
Click to collapse
Perfect. Just the info I was looking for.
Thanks.

[GUIDE] New Fire Phone with FireOS and Google Apps - A Start-to-Finish Walkthrough

I just got a Fire Phone via the Ebay sale, and like many others, I wanted to set it up with Google Apps. I also wanted to keep the working camera and NFC, so I decided to stick with FireOS. Doing that took a lot of searching, and flipping through multiple threads. It can get a little confusing. So I've collected all the steps here to help others (and myself, in case I need to do this again in the future, when I inevitably break something while tinkering). I've written this from the perspective of someone who has purchased a brand new Fire Phone from a third-party seller.
PLEASE NOTE: Much of this is the work/discoveries of other forum members. I'll link out to the original posts whenever possible. Please thank those people accordingly!
1. When you first start up your phone, connect to WiFi, and let it go through the upgrade process to 4.6.4. Now is the time to register your phone with Amazon (by signing in with your Amazon account). You want that year of Prime, don't you?
2. SIM Unlock the phone (if you aren't using AT&T). It's easy!
a. Use a paperclip to pop out the SIM tray
b. Insert a non-AT&T nano-sized SIM card. (Mine came with an AT&T SIM in it. You can't use this card to SIM unlock)
c. A window should pop up, prompting you to enter the code that is on your box. Enter it.
d. Done!​
3. Open Settings>Applications & Parental Controls>Prevent non-Amazon app installation. Turn App Installation to ON
4. Make sure ADB is set up on your computer. (this is an easy guide to follow if you don't already have it: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 )
5. Download the following file to your desktop computer:
GSM Unlocked Firmware (this is a 1.2gb file) (http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2). Rename this update.bin, and put it into the folder where ADB is installed.​Now we get our hands dirty:
6. If you are using Windows (I'm not), follow the directions that @Bingo Bronson posted here: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2. @DePingus also has an illustrated guide for ADB on Windows here: http://forum.xda-developers.com/showpost.php?p=62844581&postcount=14
6a. If you aren't using Windows, you can follow my steps (the same, just without all the Android SDK stuff, assuming you installed ADB in step #4)
a. Connect your phone to your PC & boot into recovery: When the phone is off, hold PWR + VOL. UP until the recovery screen appears
b. From the list, choose "Apply update from ADB"
c. In the command prompt, enter the following:
Code:
adb sideload path/to/update.bin
d. It should take a few minutes. When it's done, reboot your phone​
NOTE: If for some reason this isn't working for you, @jack9955 has posted steps on how to downgrade via Safestrap here.
7. Open Settings>Device>Get Info About Your Fire Phone. Your current version will be listed under Software Version, and it should now be 4.6.3
At this point, you may need to repeat step 3. I didn't, but it's worth checking.
8. Open the Amazon app store (one last time) and download ES File Explorer.
9. In the Silk Browser, open up the following links and download the files:
KingRoot (http://forum.xda-developers.com/fire-phone/help/root-4-6-3-t3173322)
Updated Google Play Store files: (http://forum.xda-developers.com/fire-phone/general/google-play-store-4-6-1-version-4-apks-t3098592)​
10. Open ES File Explorer, navigate to Download, and install KingRoot. Follow the directions to achieve root.
11a. At this point, some people like to remove KingRoot (out of security concerns) and replace it with SuperSu. I haven't done that yet, but you can follow the directions from @najoor here: http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
12. Open ES File Explorer, navigate to Download, and unzip play.zip. Be sure to install the apks contained in the play.zip folder in the proper order (Thanks to @escape75 for these files)
1) Google Account Manager 4.4.2 (940549)
2) Google Services Framework 4.4.2 (940549)
3) Google Play Services 7.8.99 (2134222-036) - Updated
4) Google Play Store 5.8.8 - Updated​
13. After installing, I rebooted into recovery again, and wiped the cache partition. I don't know if you need to, but engaging in good housekeeping is never bad.
14. You should have a Play Store icon in your app drawer now. Click it to open, and holy crap!! It works. Plug in your google account details.
Now it's time to keep Amazon from wrecking all your hard work. Steps 15 or 15a will block OTA updates of the OS.
15. Go to Settings>Applications & Parental Controls>Manage Applications. Click Filter By and select All. Find each of the files listed below, click it, and then click the "Disable" button on the next screen. Repeat for the other three files. (thanks @Bingo Bronson)
Amazon Device Client
DCP Platform Contracts
System Update
System Update (yes, there are two different files named system update. Freeze/Disable both)​
15a. If you'd rather, you can do like I did, and use Titanium Backup Pro to freeze the above files.
16. Don't like the Launcher? Neither do I. I followed these directions to change out my launcher: http://spinyourfire.com/fire-phone-tips-and-tricks/fire-phone-launcher/ I use Home Switch from the Play Store. It will allow you to set your new launcher.
If you decide to use a new launcher, here's some info (courtesy @Bingo Bronson) which may help:
1. Settings>Display>Show Status Bar allows you to turn on the Status Bar at the top of the screen. This will help some launchers display properly.
2. Miss your NavBar / want some way other than Amazon gestures to navigate your phone? Try installing Ultimate Dynamic NavBar or Pie Controls.​
NOTE: The new launcher will disable Tilt Left/Right on your home screen. In Amazon apps, the gesture will still work.
17. To sync your contacts/calendars/etc, go to Settings>My Accounts>Manage Email Accounts and add your Google account info.
a. Select that account, check sync calendar and sync contacts.
b. Set Inbox Check Frequency to manual.
c. In Email Settings, set everything to off, then click email notification settings, and set all of those to off.​
BEWARE: HERE BE DRAGONS
Hi. Are you new to phone hacking? Then you should probably stop reading here. Following any of the links or info could (pretty easily) lead to bricking your phone. I won't even mess with most of this stuff, I'm just providing links for intrepid explorers who know what they are getting into, and are willing to risk it. SERIOUSLY, TURN AROUND HERE!
Seriously, you did all that work, and now you want to risk breaking it? Well yeah, me too. So let's cover our asses.
Backing Up with SafeStrap
First, let's back up what you've done. @ggow (to whom we all owe a debt of gratitude) has gifted us with SafeStrap, which allows us to boot into a version of TWRP recovery. From there, you can install his CM11 or SlimKat Roms, or use the backup feature, which is what we are about to do.
1. Install Safestrap from here http://forum.xda-developers.com/fire-phone/development/recovery-safestrap-v4-0-1-t3149888. In ggow's directions, it talks about 4.6.1, but I can confirm it works properly on 4.6.3.
2. Once you have booted into Safestrap, Click Backup and then back it up! (it took about ten minutes for me)
3. Of course, a backup won't do you any good if you don't have multiple redundancies. So plug your phone into your computer, open up a terminal/CMD prompt, and enter the following:
Code:
adb start-server
then
Code:
adb pull /sdcard/TWRP/ /path/to/your/backup/folder
after that runs for a while, you should see a message that says something along the lines of "12 files pulled. 0 files skipped"​
Good! Now we are backed up, and we can start breaking stuff.
Turn on USB Debugging
1. Go to Settings>Device>Get info about your Fire
2. Tap "Model Number" seven or eight times, until the "Developer Options" button appears at the bottom of the list
3. Tap "Developer Options" and enable USB debugging​Installing Xposed Framework
Xposed Framework allows you to install different modules that can change the look, feel and operation of your phone. Xposed works best on Vanilla Android, but we can definitely put it to good use here. Lifehacker has a great overview on Xposed. I'll just give you the basics here.
What you'll need: Root
1. On your phone, visit http://repo.xposed.info/module/de.robv.android.xposed.installer. Scroll down to the bottom of the page and click Show Older versions. You want the APK for version 2.6.1 (the most recent stable version)
2. After downloading, navigate to your Downloads folder and install the Xposed Apk.
3. Open Xposed and click Framework. It will show you that Xposed is currently inactive. Tap the install/update button.
4. Once installed, you must reboot your phone for Xposed to work.​Congrats! Now with Xposed, you can really start customizing your phone. Check the forums...there is tons to discover and lots of people who know far more than I about how to use it. Just remember that a lot of the cosmetic stuff might not work on a Fire Phone. The modules I use are: ACDisplay, Amplify (paid version), AppOppsXposed, GravityBox, Greenify (paid version), PowerNap.
Installing a custom Lock Screen
Many of us on Android are used to custom lock screens, and haven't been thrilled with the Amazon Lock Screen. Through some trial and error, I've discovered how to swap out the Amazon Lock Screen for my lock screen of choice, ACDisplay. I haven't tried this with other 3rd party lock screens. Try following (and contributing to) this lockscreen thread to see any developments on other lock screens.
What you need: Xposed, Root, ES File Explorer (or another file explorer with root access)
1. Install ACDisplay (I sideloaded the APK, but it seems to work from the Play Store)
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk (com.achep.acdisplay-1.apk) in /data/app
4. rename it LockScreen.apk and move it to /system/priv-app/
5. Reboot
6. Open up AC Display and grant it access to Accessibility Settings and Notifications
7. In ACDisplay>Settings>Lockscreen move the slider to On and make sure that "Enable when no notifications" is ticked
8. Open Xposed and activate the ACDisplay module.
9. Reboot
10. I don't know if you need to, but I went to Settings>Lock Screen> Turn on Notifications... and made sure that notifications were off.​
The Xposed integration seems to be the key. Now, when I reboot my phone, I'll get the original Amazon Lock Screen once (sometimes) and then ACDisplay pops up from that point on. Apparently, if you want a pin/password on the lock screen, you can still use the security features of the OS lockscreen.
Launchers with Widgets
One of the problems with custom launchers is that widgets don't seem to work on the Fire Phone. But @hmoobguy and @DePingus have figured out how to beat that in this thread. Just like with the lock screen, you'll have to move some files.
What you need: Root, ES File Explorer (or another file explorer with root access)
1. Install your launcher from the Play Store.
1a. If you haven't already, visit the Play Store on your desktop, look at the page for the launcher you just installed, and take note of what comes after 'id=' in the URL. That's the file name you'll search for.
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk for your launcher of choice in /data/app by searching for what came after 'id=' in step 1a.
4. move it to /system/priv-app/
5. Reboot​
Note: you can also use Titanium to convert your launcher of choice into a system app.
Other Stuff
@Bingo Bronson has a ridiculously extensive list of Fire OS apps that can be disabled/frozen or deleted. Use at your own risk: http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008
Hopefully this is helpful to others. I can add information as I go if new info (and new annoyances) come to light. Please let me know if there is anything I missed!
Thanks man! That's a good list there!
I gathered much of the information you have posted there last night and I have it at 4.6.3 with Google Play and a custom launcher.
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Cheers!
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Natet2003 said:
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Click to expand...
Click to collapse
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Natet2003 said:
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Click to expand...
Click to collapse
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
I was having issues with the alarm clock and then I screwed up all the lockscreens. I gave up trying to fix my mess and just took the opportunity to install 4.6.3. That fixed all my issues and put me back to the stock crappy lockscreen, which I'm still running.
munkymack said:
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Click to expand...
Click to collapse
I think I found what it was. I had "C Launcher" installed. It does an iPhone styled sliding lock screen that even when I swapped to another Launcher the lock screen kept activating. (So I had two screens to bypass) When I had experimented with GO Locker it added yet another screen to those so 3 screens!
So once I've removed CLauncher and GO Locker I've not just have a single screen, which is FireOS default lock screen.
Great instructions, well consolidated--thanks!!
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!. Hopefully my perception is wrong and I can proceed with your consolidated instructions. Can you please post updates as the days go by on how its all working. Thanks.
dannyol said:
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!
Click to expand...
Click to collapse
I went to 4.6.4 simply because my phone automatically updated from 3.5.0>4.6.1>4.6.4 when I connected it to wifi, and the directions I'd found showed how to downgrade from 4.6.4 (which is AT&T specific) to 4.6.3 (gsm unlocked).
The reason I chose to downgrade is because Play store doesn't work on 4.6.4...it keeps breaking. On 4.6.3, that's not the case (so far); Play Store (and even more important, Play Services, which is necessary for most Google apps) is working exactly like it should be. Might it break in the future? Yeah, probably. But if / when it does, I'll try and update the post (assuming that a fix gets found).
DePingus said:
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
Click to expand...
Click to collapse
Just a heads up, DePingus and I have been discussing this on the linked thread, and the above instructions DO NOT work. LockScreen.apk does not exist in /system/priv-app/ on 4.6.3. At this point in time, there is not a way to completely replace the Amazon lock screen with a custom lock screen.
This is a good guide.
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Is it safe to update the play store when it asks?
MrPaulAR said:
Is it safe to update the play store when it asks?
Click to expand...
Click to collapse
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
New fire phone with version 3.5-rooted and now at a stand-still
Bingo Bronson said:
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
Click to expand...
Click to collapse
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
dannyol said:
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
Click to expand...
Click to collapse
I did the same thing when I first got mine, so I understand where you are coming from. After reading around on the forum, I saw that 4.6.3 could work with Play Store / Services, so I just did a straight up OS update. I didn't unroot or anything, and suffered no problems. My phone updated from 3.5 to 4.6.1, and then to 4.6.4. From that point, I downgraded to 4.6.3 and then proceeded with the steps in the guide.
As far as I can tell, you WILL lose root in the update, but you can use Kingroot to re-apply root.
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
jimbobalu said:
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
Click to expand...
Click to collapse
I have absolutely no idea. If it does work, let me know. I've got one of the new $50 fire tablets coming at the end of the month.
DePingus said:
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Click to expand...
Click to collapse
That's a good point. I've been doing this long enough that rooting is something I do without a second thought, but for beginners, it opens up the door to a host of problems. I'll do a reorganization next time it's slow around the office.
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
And apparently because I'm a new user, I can't post URL's, so here's the closest I can get you
seo-michael.co.uk/how-to-setup-adb-on-os-x
This phone is dirty cheap now.
i might grab one of these . here in Europe
cheers
Be sure and check the LTE bands before you do. You may not be able use high speed data there.
EDIT: I looked at the work in your signature. I'm pretty sure you know exactly what you are doing / getting yourself into if you do pick one up. I'm just trying to be super newbie friendly over here, hence my response.
Osufever said:
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
Click to expand...
Click to collapse
Yeah, ADB is different on every system, and can be a pain in the ass to set up. The Lifehacker article I linked should cover everything, but if Mac users want to delve a little deeper, then the link you followed is a good way to go. I'm glad you were able to get things working!

Is there a List of Background Processes to Kill to Extend Battery?

Does anyone here know of a list of background processes or apps to kill to ensure longer battery?
.
I've this a bit of a battle with this phone, especially with "Phone Services", which from what I understand is mainly other Apps making calls to it.
But I've made some progress, to be honest, the issue is Android is far to liberal with access it gives applications. But if they don't run or cannot access the internet, then they can't drain the battery. Here is what I did:
1) Stop Apps from auto-starting, or being started via other Apps. via Apps -> App Launch. When you disable "Auto Manage", it pops up and asks if the app should Autostart, Run in Background, Secondary Launch
2) Disable background Network access for ALL applications (search settings for Networks Access, then select "Advanced"), including system apps such as chrome.. Only re-enable for apps that do NEED it (i.e. such as Gmail)
3) Disable all unnecessary permissions, via Apps -> Permissions, especially thing such as Location. At minimum, set them to "Allowed only while in use"
Finally, the problem with Android permissions, is Google are self-motivated, I found several apps that I couldn't do this for (including Chrome, which was particularly battery hungry). In addition there are dozens of "permissions" that they don't want you to access. But if you're willing to get your hands dirty, then look into using and Ice Box with Shizuku (it's fairly easy) you can.. In addition, you can use ADB to uninstall all the bloated Apps.
App Ops - To get access to all those "inaccessible" permissions. I used this to change all the backgrounds permissions, and remove Apps abilities that prevent the phone from "Sleeping"
Ice Box - To freeze all Unecessary Apps
Note, both the above use a secondary App called Shizuku, all can be installed from the Play Store. But to allow Shizuku to get the system-level access it needs, it must be started using ADB.. The App runs you through it.
Whilst I've uninstalled quite a few apps using ADB, this can cause problems if you're not careful, so I came to the conclusion its best to freeze them with Ice Box. This is what I've frozen so far:
package:com.andoid.apps.tag
package:com.andoid.bookmakpovide
package:com.andoid.calenda
package:com.andoid.deams.phototable
package:com.andoid.email
package:com.andoid.htmlviewe
package:com.andoid.huawei.HiMediaEngine
package:com.andoid.hwmio
package:com.andoid.keyguad
package:com.andoid.mediacente
package:com.andoid.patnebowsecustomizations.tmobile
package:com.andoid.povides.patnebookmaks
package:com.andoid.statementsevice
package:com.example.andoid.notepad
package:com.google.a.coe
package:com.google.andoid.apps.tachyon
package:com.google.andoid.apps.wok.oobconfig
package:com.google.andoid.feedback
package:com.google.andoid.music
package:com.google.andoid.pintsevice.ecommendation
package:com.google.andoid.pojection.geahead
package:com.google.andoid.youtube
package:com.hicloud.andoid.clone
package:com.huawei.KoBackup
package:com.huawei.aengine.sevice
package:com.huawei.andoid.ch
package:com.huawei.andoid.instantshae
package:com.huawei.andoid.kaaoke
package:com.huawei.andoid.mioshae
package:com.huawei.andoid.thememanage
package:com.huawei.andoid.tips
package:com.huawei.andoid.totemweathe
package:com.huawei.andoid.wfdft
package:com.huawei.appmaket
package:com.huawei.autoinstallapkfommcc
package:com.huawei.bowse
package:com.huawei.contacts.sync
package:com.huawei.contactscamcad
package:com.huawei.fastapp
package:com.huawei.featuelaye.featuefamewok
package:com.huawei.featuelaye.shaedfeatue.map
package:com.huawei.gameassistant
package:com.huawei.health
package:com.huawei.hff
package:com.huawei.hiaction
package:com.huawei.hicad
package:com.huawei.hidisk
package:com.huawei.hifolde
package:com.huawei.himovie.oveseas
package:com.huawei.hitouch
package:com.huawei.hwdetectepai
package:com.huawei.hwid
package:com.huawei.hwstatupguide
package:com.huawei.languagedownloade
package:com.huawei.lbs
package:com.huawei.livewallpape.matetwenty
package:com.huawei.neaby
package:com.huawei.paentcontol
package:com.huawei.pcassistant
package:com.huawei.sceenecode
package:com.huawei.seach
package:com.huawei.tips
Hi evil,
Appreciate the much needed reply. I assume app ops, ice box and Shizuku can be run withourt root since I'm on emui 10 and the bootloader is locked. Got a few questons for you...
1) I can't find ice box in the playstore. The closest I saw was an app called app freezer by mobizsystems. Could this possibly be it and was renamed? If not please post a link to it.
2) Just to be sure, once i install Shizuku, it'll run me through what to do like a tutorial?
3) For the long list of apps you provided that you froze, could you also list what each of these apps are for?
.
1) I can't find ice box in the playstore. The closest I saw was an app called app freezer by mobizsystems. Could this possibly be it and was renamed? If not please post a link to it.
This is the App: https://play.google.com/store/apps/details?id=com.catchingnow.icebox&hl=en_GB
2) Just to be sure, once i install Shizuku, it'll run me through what to do like a tutorial?
So Shizuku provides the API that Icebox and App Ops use for controlling the phone... It can work without root, but it requires a little tinkering. Follow the step Shizuku tells you, but in a nushell:
1 - First enable the Developer Options Menu (Google how to do it), then in the Developer options enable USB Debug
2 - Installl ADB on your laptop or Mac (https://developer.android.com/studio/releases/platform-tools)
3 - Plug your phone into the laptop / Mac
4 - Run the ADB command you laptop/mac that Shizuku tells you, this will start the Shizuku service on your phone
5 - You then use App Ops to control permissions, or Ice Box to freeze apps
3) For the long list of apps you provided that you froze, could you also list what each of these apps are for?
See the spreadsheet linked in this thread: https://forum.xda-developers.com/mate-20-x/how-to/guide-remove-apps-adb-t3870727
EViL3666 said:
1) I can't find ice box in the playstore. The closest I saw was an app called app freezer by mobizsystems. Could this possibly be it and was renamed? If not please post a link to it.
This is the App: https://play.google.com/store/apps/details?id=com.catchingnow.icebox&hl=en_GB
2) Just to be sure, once i install Shizuku, it'll run me through what to do like a tutorial?
So Shizuku provides the API that Icebox and App Ops use for controlling the phone... It can work without root, but it requires a little tinkering. Follow the step Shizuku tells you, but in a nushell:
1 - First enable the Developer Options Menu (Google how to do it), then in the Developer options enable USB Debug
2 - Installl ADB on your laptop or Mac (https://developer.android.com/studio/releases/platform-tools)
3 - Plug your phone into the laptop / Mac
4 - Run the ADB command you laptop/mac that Shizuku tells you, this will start the Shizuku service on your phone
5 - You then use App Ops to control permissions, or Ice Box to freeze apps
3) For the long list of apps you provided that you froze, could you also list what each of these apps are for?
See the spreadsheet linked in this thread: https://forum.xda-developers.com/mate-20-x/how-to/guide-remove-apps-adb-t3870727
Click to expand...
Click to collapse
Hi evil,
Wow.. thank you so much for this info. I'll get started on this tomorrow. Thank you again for this valuable info.
.

Question Security message when running an app

Hello
I installed the Marriott app this morning, and when I go to run it, i get that security message along the bottom third of the screen, and the app shuts down.
What is causing that?
It is detecting root/magisk.
Add Marriott to Zygisk hide list, then clear Marriott storage&cache, force close and reopen.
I downloaded the app and installed it to test. If you don't clear the app cache (and only force close and reopen) it will not work. You must clear that before opening again
Thank you App
I followed your instructions, but I still get that message.
Should I have rebooted after adding to the list??
nabril15 said:
Thank you App
I followed your instructions, but I still get that message.
Should I have rebooted after adding to the list??
Click to expand...
Click to collapse
No. That's not necessary. The following 3 steps is all you need
I cleared storage, force closed, and run it.
I get that initial welcome screen of the app, and before I can press on the SIGN IN button, it closes forcefully.
This happens no matter how many times I repeat the steps.
nabril15 said:
I cleared storage, force closed, and run it.
I get that initial welcome screen of the app, and before I can press on the SIGN IN button, it closes forcefully.
This happens no matter how many times I repeat the steps.
Click to expand...
Click to collapse
What magisk version and modules are you using?
Also, what Android/oos version are you using?
Do you have device certification in play store? Or what's your YASNAC result?
nabril15 said:
I cleared storage, force closed, and run it.
I get that initial welcome screen of the app, and before I can press on the SIGN IN button, it closes forcefully.
This happens no matter how many times I repeat the steps.
Click to expand...
Click to collapse
After some more poking around, that app detects everything. I attempted to monitor the https traffic to see what contacts are made at app-boot. It detects that I'm monitoring traffic. I attempted to use frida to bypass the ssl pinning so I can monitor traffic. It detects that I'm using frida. All of those cause a close condition.
This could mean, if it detects anything abnormal, you're gonna get force closed. The whole toast not showing up is annoying. You might be able to adjust your font/text size for the system in Accessibility, to see the full text.
If you have busybox or anything else you can think of that might be detected, try disabling them or any questionable modules like lsposed, restart, then see if you can open the app.
I looked inside the app and don't see some of the stuff as strings, and existing strings are already using some reflected values in another index. It appears to use some kind of library that is checking for root, certification, ssl certificate pins, frida, probably xposed and so on. Then retrieving the response from an api.
My thought was to repackage the apk without root checks for you but if they're doing that much for security, there's almost no chance I will be able to launch the app with self signing for the apk.
Having the full toast response would be helpful here
Wow App.. How detailed, you are.
Here are my modules plus Universal Safetynet fix. I'm running a13 f.17 build.
I'm not sure how to proceed. I installed it on my wife's phone and used it..
Here's a reddit thread with someone else fighting with the Marriott Bonvoy app.
old.reddit.com/r/Magisk/comments/yf8gyu/help_hotel_app_detecting_root/
Its quite ridiculous that a Hotel app is so restrictive and difficult.
I just (briefly) tried running the app inside Island, but still got the toast nags / close.
Interestingly I get one of two nags "you're on an unsecure network" or "we've detected magisk, etc)
I wish that I had twrp to blame, but I don't have it installed.
Hey there,
I did some looking at older versions of the app (apkpure has them). On my phone (Android 9, Magisk 23) the last version that will run (using MagiskHide with all the 3 boxes ticked for the marriott app), is 10.4.0.
Marriott Bonvoy™ 10.4.0 (Android 9.0+) APK Download by Marriott International - APKMirror
Marriott Bonvoy™ 10.4.0 (Android 9.0+) APK Download by Marriott International - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Version 10.5.0 starts giving me nags.
(Sometimes it is just easier to use an older version of an app, than fighting to get the very latest to work!)
Mine is 10.13.1. not sure what got updated. I usually don't want to get stuck with old version, so I'll just use the website to make reservation and redemption. Yikes
I heard Magisk Delta by HuskyG could hide it from detection. Has anyone been brave enough to try? Well, I tried and it didn't work. I tried the whitelist mode by leaving Marriott out of the SuList and many other banking apps too. But it still detects root. Marriott app version 10.13.1. Older version say 10.12.0 and below should survive.

Categories

Resources