Related
You're busy and don't have time to wait, which is why you need to stop reading this thread and get back to organizing your Pogs. Rate this thread to express how the OnePlus 3 performs when multitasking. A higher rating indicates that the OnePlus 3 keeps many apps in memory so that they don't need to reload, and that when moving between apps, transitions are smooth and performance is excellent.
Then, drop a comment if you have anything to add!
Incredible after applaying the memory fix by settig the app limit to 42
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
Any idea on how this affects battery life?
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
So I also switched my background processes to 42, and I ended up dialing it back to 32, because I do think it affects battery life a bit. To be honest, at 42, I was using 5GB of RAM at a time, which was amazing (SO MANY apps in RAM), but honestly, while it's fun, it's not really helpful in day to day use. But the default setting of 20 is too low.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
Batterylife might be effected, but its perfectly fine for me. Im getting around 4h of SOT with brightness at 100% (adaptive) Wifi and Bluetooth turned on, connectet to my huawei watch and using it quite a lot. And there was literally no app cleared from ram. I will test it again with the value set to 36 though!
Its such a great experience to have a phone which doesn't have to start up an App twice.
Sounds great... but for me stock settings only end up getting about 2h of SOT wich seems to be not that much... Seems like Android System drains a lot...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
By default limit is low but i think for day to day usage it is fine
I able to use only 3 to 4 apps daily for multi tasking and it is fine and giving me good battery experience.
Sent from my ONEPLUS A3003 using Tapatalk
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
By stating a memory fix you are referring to rooting the phone prior to adjusting the value, correct?
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
Go on Youtube and search vor "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions.
In the video description you will also find all the downloads you will need!
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
The simplest way to apply the memory fix is the following:
-Go on Youtube. Search for "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions. Its really easy, you will find all the downloads in the videos description.
-then download the build prop editor app from the play store and look for the right value (ro.sys.fw.gb_apps_limit=20) and change it.
Julius1993 said:
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
Click to expand...
Click to collapse
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
harharryhar said:
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
Click to expand...
Click to collapse
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I believe there is a utility that does this all for you as well. I don't have my OP3 yet but I have used utilities with my Moto G3 and it simplified the process a lot.
There is no Utility for the op3. And it already is very simple
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
--
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I'm just an "interloper" curious about this new phone and noticed this while browsing the forum, and I've modified / files without root being "installed" on many phones before as long as someone had already created a custom recovery for it that worked (and supported adb when booted to custom recovery)::
Should be something like :
Code:
Boot to custom recovery ::
open shell and adb shell,
su // this should just work since recovery's are by definition already rooted and you're booted into it.
Make sure system is mounted (mount -o remount,rw /system) (or whichever switches it requires)
modify your file using the terminal mode or editor provided by TWRP/{other} and save
remount as read (mount -o remount, ro /system)
reboot.
I hope that helps, if not, I will shut up in this forum. I'm assuming TWRP for this device is about the same as for nearly every other one. Sorry if not,.
Cheers.
That's actully true! Haven't thought about that. You can Mount/remount by using a custom Recovery. But still I would recommend rooting, since it doesn't even Void your warranty
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Dunno guys,i just got my phone yesterday,barely installed anything,like 3 apps running in the background and my Nonstop Knight game reloads in 7/10 tries.
With OOS 3.2 the RAM can (well, could) be used to its fullest. I simply could not throw enough at it to fill up. Five big, full 3D games, 20+ Chrome tabs, all my apps (30ish) open and still 1Gb remaining whilst load-less app-switching
The multitasking on this device is awesome! Good job OnePlus
If this phone had 4GB of RAM, I think it wouldn't have changed anything.
I just got my Z2 Force for Christmas (AT&T of course) and am wondering if there is a root method that doesn't involve unlocking. I love the almost stock feel of the Moto Android skin and don't plan on flashing or stuff like that. All I really want to do is get rid of what little bloat there is and runs Ad-away, stuff like that. I don't need TWRP as I plan on keeping the stock ROM. I did a search but didn't find what I'm looking for so I apologize if it's already been discussed.
Thanks and Happy New Year
Happy New Year!
As of writing the AT&T and Big Red variants of the Z2F aren't eligible for bootloader unlock codes. People were apparently working on a brute force method, but that effort fell flat. The most you can do is update using a flashall kit, if I'm not mistaken.
theandies said:
I just got my Z2 Force for Christmas (AT&T of course) and am wondering if there is a root method that doesn't involve unlocking. I love the almost stock feel of the Moto Android skin and don't plan on flashing or stuff like that. All I really want to do is get rid of what little bloat there is and runs Ad-away, stuff like that. I don't need TWRP as I plan on keeping the stock ROM. I did a search but didn't find what I'm looking for so I apologize if it's already been discussed.
Thanks and Happy New Year
Click to expand...
Click to collapse
I'm in the same boat as you; I like everything about it, just want the bloat gone. The adb method worked like a charm for me. You can check out the XDA guide here: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Thanks Chicago , I'll give that a try and report back.
Reading further into doing this I don't think this actually uninstalls the package
From the instruction Chicago posted:
This is a good thing, however, as it means that these applications truly aren’t being uninstalled from the device, they are just being uninstalled for the current user (user 0 is the default/main user of the phone). That’s why, if you omit the “–user 0” and “-k” part of the command, the command won’t work. These two commands respectively specify that the system app will only be uninstalled for the current user (and not all users, which is something that requires root access) and that the cache/data of the system application will be preserved (which can’t be removed without root access). Therefore, even if you “uninstall” a system application using this method, you can still receive official OTA updates from your carrier or OEM.
Click to expand...
Click to collapse
It appears that this just disables the app as you can do through app manager. I'm going to try it and keep an eye on my storage size. If I gain more storage after doing this then it is deleting it off the phone. If the storage stays the same then it's just disabling the app. I just want the few gig's back. Not that I'm running out of storage I just want it for me and not AT&T
theandies said:
Reading further into doing this I don't think this actually uninstalls the package
From the instruction Chicago posted:
It appears that this just disables the app as you can do through app manager. I'm going to try it and keep an eye on my storage size. If I gain more storage after doing this then it is deleting it off the phone. If the storage stays the same then it's just disabling the app. I just want the few gig's back. Not that I'm running out of storage I just want it for me and not AT&T
Click to expand...
Click to collapse
OEM apps (carrier apps) are saved on the /OEM partition. No data in /data or /system is used up for these apps unless you open them and it creates a file in /data. Disabling would prevent the apps from writing user data.
And not all apps can be disabled/uninstalled this way. T-Mobile prevents uninstalling it's native app
Let me correct myself. These commands will disable annoying TMO software:
adb shell pm disable-user com.tmobile.pr.adapt
adb shell pm disable-user com.tmobile.pr.mytmobile
adb shell pm disable-user com.tmobile.services.nameid
adb shell pm disable-user com.tmobile.simlock
Same principle with AT&T.
There are of course some generic guides like
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
https://source.android.com/setup/build/gsi#flashing-gsis
and in this G6 Play subforum there is this guide for things such as root, twrp, decrypt, magisk
https://forum.xda-developers.com/showthread.php?t=3929928
But I do not want to root/decrypt my device unless needed and I ESPECIALLY don't want to install sketchy unofficial software from untrusted sources.
It seems TWRP does not officially support the Moto G6 Play, and it seems you can install without it.
So I have a few questions:
Do I need Dm-Verity & ForceEncrypt Disabler?
Do I need Magisk?
Do I need to disable verify boot (AVB) by flashing vbmeta.img?
How can I backup my phone without TWRP?
Any other particularities besides the generic GSI guide?
How badly can I mess up?
I've written Android apps, so I know my way around adb, but this is my first time flashing GSI.
pepijndevos said:
There are of course some generic guides like
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
https://source.android.com/setup/build/gsi#flashing-gsis
and in this G6 Play subforum there is this guide for things such as root, twrp, decrypt, magisk
https://forum.xda-developers.com/showthread.php?t=3929928
But I do not want to root/decrypt my device unless needed and I ESPECIALLY don't want to install sketchy unofficial software from untrusted sources.
It seems TWRP does not officially support the Moto G6 Play, and it seems you can install without it.
So I have a few questions:
Do I need Dm-Verity & ForceEncrypt Disabler?
Do I need Magisk?
Do I need to disable verify boot (AVB) by flashing vbmeta.img?
How can I backup my phone without TWRP?
Any other particularities besides the generic GSI guide?
How badly can I mess up?
I've written Android apps, so I know my way around adb, but this is my first time flashing GSI.
Click to expand...
Click to collapse
Do I need Dm-Verity & ForceEncrypt Disabler?
Yes, but you need to install twrp first in order to flash it, or it won't work properly. GSIs like to bootloop if you don't disable them.
Do I need Magisk?
Nope. I'd still recommend it though, because I'm not sure if the disabler removes AVB, and having it enabled can cause bootloops.
Do I need to disable verify boot (AVB) by flashing vbmeta.img?
Nope. This doesn't apply to us. We don't have "system as root". AVB is in the boot.img.
How can I backup my phone without TWRP?
You pretty much can't. Some partitions can be backed up with dd commands, but most of them can't be restored like this. You also need root to use them.
Any other particularities besides the generic GSI guide?
You'll need to manually replace the apn if you use Virgin/Sprint/Boost. You'll also need an overlay to enable auto brightness, and another one to fix the rounded screen corners.
How badly can I mess up?
Worst case scenario, you might encounter a bootloop. There isn't much you could do, that flashing stock firmware couldn't fix.
Thanks for the info.
Between the post and your reply I just figured I'd attempt the generic guide.
I guess I'm lucky that I did not encounter a boot loop.
All is working great now.
I should look into adding this overlay maybe...
pepijndevos said:
Thanks for the info.
Between the post and your reply I just figured I'd attempt the generic guide.
I guess I'm lucky that I did not encounter a boot loop.
All is working great now.
I should look into adding this overlay maybe...
Click to expand...
Click to collapse
I have copies for our phone. Check the attachments. Here's all the steps.
1. Install your GSI.
2. Using twrp's file manager, a root browser, or ADB... copy the 2 apks below to /vendor/overlay and set permissions on them to 0644 or rw-r--r-- and reboot.
3. Using ADB or a terminal emulator, run the following commands.
adb shell or su from a terminal emulator.
Code:
[B]chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/Autobright.apk[/B]
Code:
[B]chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/Curves.apk[/B]
And reboot.
4. Open up adb or a terminal emulator once more. Enter these commands.
adb shell or su
cmd overlay list
cmd overlay enable android.auto_generated_rro__
cmd overlay enable com.android.systemui.Curve
*** You should see the changes immediately after this. You may need to reboot one more time to get auto brightness' options to show up in your settings.
So this phone is used by my close relative and I usually update their phone for them. It worked great, no complaints.
Just today I wanted to do something in Magisk, but I didn't have the bottom options like I didn't have root.
Interesting. I thought something broke it, so I decided to update to latest OS and then try again.
Since the phone was running a few months old update, I thought I'd update + root to make sure everything works.
I used flash-all.bat to update, it flashed fine, the phone loaded fine, it shows September security update.
so I went ahead and tried to root like I always did.
got the latest image, updated via flash-all.bat (without -w switch), then copied over the boot.IMG, patched it on phone, copied back to my PC from /sdcard/Downloads, then used "fastboot boot magisk...img" to boot the patched img.
now, this is how I rooted my 9R and this 3a XL a dozen times. but not now.
I open Magisk once it boots up and it just shows me the same Install option.
It same as nothing happened.
like root just doesn't exist. wtf?
did Google mess remotely with Pixels? or what's going on?
ps.: I even tried to "flash" the img into the active slot, both slots, nothing.
like the .img itself is not getting patched.
using Magisk stable, 23.0.
update 1: Interestingly enough, Root Checker says I have root. But Magisk only has Patch File option, no Direct Install. Tried Canary too, nothing. Reinstalled Magisk app, nothing. So weird... like Magisk lost root access? But why? How do I fix that? So weird...
You can open a terminal app and type 'su' to see if it prompts you for root access. If not you can try uninstalling magisk, then rename the magisk.apk to .zip and sideload from recovery.
SOLVED!
Sorry for not updating my thread, it was pretty late when I cracked this.
Here is how I fixed it. (I'll format it a bit later.)
I went Termux, root with su.
went into /data/adb/ and there is a magisk.db file.
I copied that to /sdcard/ and then to PC (you can do this on phone too using SQLite editor apps but whatever. On PC it's easier, more screen estate, etc.)
I used SQLite Browser (free) to open the file, then Browse Data and Policies
here I saw all the apps that had root granted...
So I added a new line.
I used adb shell on PC to find out the data I needed.
first, pm list packages | grep magisk to find magisk's name (it's "com.topjohnwu.magisk")
then, dumpsys package com.topjohnwu.magisk | grep userId to find out the user ID (uid) for it.
I added these into the database, it looked like this in the end:
uid package_name policy until logging notification
10386 com.topjohnwu.magisk 2 0 1 1
(^ your userId will NOT be the same!
and the first line is the column names)
saved the file, copied it back to my phone in Windows, then used Termux to copy the file from /sdcard/magisk.db to /data/adb/magisk.db
then I shut down the phone, used "fastboot boot magisk_.. patched.img" so I'd have a rooted boot image loaded up.
and boom, Magisk app works again.....
how to tell if Magisk app loses root?
well, for me the screen went dark briefly for like 2 times when I opened the app on clean boot.
and of course, Direct Install was missing.
to verify root in this case - you can only use apps that are present in the .db file.
ie.: apps that you granted beforehand.
so I'd really recommend opening Termux then doing a "su" at least after a root.
Why does it happen?!?!
I THINK this happens when you repackage Magisk. So I'd recommend changing it back before doing a system update. Because after the system update, you most often need to reinstall the .APK and then its under the original package + app name. Thus, it's not in the Policy file -> ie.: the Magisk app will not have root.
So I stumbled upon this thread: https://forum.xda-developers.com/t/guide-remove-unlocked-bootloader-warning.4069207/
The flash script reads:
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_a");
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_b");
On my root explorer, I am able to see both these files by navigating to /dev/block/bootdevice/by-name/
So my question is, how do we edit abl_a and abl_b for our phones, to remove the warning screen?
Interesting. If these files/partitions serve the same purpose on the Pixel as they do on Xiaomi, then there's hope. I'd find it amazing if this was possible on the Pixel that no one would have found this yet - unless the solution just wouldn't work on the Pixel. I have no idea if you can safely replace those files on the Pixel with the same example that is included in the flashable zip with ADB either with the system booted or in recovery mode.
I found the files to be actually inside:
Code:
/dev/block/platform/14700000.ufs/by-name/
through X-Plore File Manager, but the "/dev/block/bootdevice/" does exist and redirects to "/dev/block/platform/14700000.ufs/".
roirraW edor ehT said:
Interesting. If these files/partitions serve the same purpose on the Pixel as they do on Xiaomi, then there's hope. I'd find it amazing if this was possible on the Pixel that no one would have found this yet - unless the solution just wouldn't work on the Pixel. I have no idea if you can safely replace those files on the Pixel with the same example that is included in the flashable zip with ADB either with the system booted or in recovery mode.
I found the files to be actually inside:
Code:
/dev/block/platform/14700000.ufs/by-name/
through X-Plore File Manager, but the "/dev/block/bootdevice/" does exist and redirects to "/dev/block/platform/14700000.ufs/".
Click to expand...
Click to collapse
/Tad off topic: I am using Material Files (found on F-Droid - free and open source). Material Files has true root file explorer, unlike many file explorers and comes ad-free and fully functional!
I would strongly recommend against this unless you know EXACTLY what you are doing. You can render your device permanently hard bricked if you effort the bootloader even slightly wrong.
I agree with @dragynbane222. Unless you're prepared to RMA your device, I wouldn't attempt it.
dragynbane222 said:
I would strongly recommend against this unless you know EXACTLY what you are doing. You can render your device permanently hard bricked if you effort the bootloader even slightly wrong.
Click to expand...
Click to collapse
This is exactly why I have not even attempted to research this any further. I was simply asking the dev community for their input.
mkhcb said:
So I stumbled upon this thread: https://forum.xda-developers.com/t/guide-remove-unlocked-bootloader-warning.4069207/
The flash script reads:
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_a");
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_b");
On my root explorer, I am able to see both these files by navigating to /dev/block/bootdevice/by-name/
So my question is, how do we edit abl_a and abl_b for our phones, to remove the warning screen?
Click to expand...
Click to collapse
As other people have mentioned, it is theoretically possible, but you can easily hardbrick your device.
On many Android versions, it was possible to adjust this warning via setting certain permissions manually (I haven't seen an attempt with A12 yet). Oddly enough, some people have reported (over the years) that such a module/mod worked without problem, whilst other had "random" hardbricks, even though they - as far as I recall - claimed that they did not deviate from instructions, and had the same devices with stock firmware. Meaning even if someone would provide you with such a file that you could add via terminal (su) or other means, and even if a dozen people here would claim it works on their end, it could still easily brick your device for reasons we do not understand. So I'd just step away from that thought and even if someone would provide a solution, to not use it. I've never seen any explanation as to why some devices bricked, and some did not, so that's danger-danger.