[MOD][ROOT] Remove notch and rounded corner overlays for different resolutions - Realme X2 Pro Themes, Apps, and Mods

Disclaimer:
If you flash the attached file, you accept the risk that it may create serious issues (very unlikely, but hey, I warned you!). I am not responsible for any soft bricks, boot-loops etc. because of this file. IT DOESN'T WORK IN REALME UI!
Background:
Some games and apps aren't fully compatible with ultrawide screen resolutions (e.g. 2400x1080 like our phone) and demand for 1920x1080 resolution.
When you apply this resolution using adb/root (see below code for Realme X2 Pro), there is an ugly overlay with rounded corners and notch area in Color OS. This is annoying.
If you want to see an example the ugly overlay that I am removing with this mod, you can type the following command in adb and do some gaming or web browsing etc.
Code:
adb shell wm overscan 0,240,0,240
To revert back to original resolution, type the following:
Code:
adb shell wm overscan 0,0,0,0
I spent hefty time to find responsible files and patched them. So that the screen is no more rounded and notch is gone on different resolutions.
This mod will remove the notch and rounded corner overlays by modding overlay images in framework-res.apk. It requires root!
You will not see any change unless you change the resolution of the screen to 1920x1080 or any other custom resolution or by using adb shell wm overscan command (see above).
It uses Magisk and doesn't actually modify the system but creates an overlay. It is based on EvilTheme Patcher
How to use:
1. Create a TWRP backup of system if you want to be definitely safe.
2. Download attached file and flash with TWRP.
3. Done. Enjoy.
Restore:
If you want to revert, simply remove the "Tulsadiver Mods" Module from Magisk manager. Or flash the ozop_restore.zip file created in sdcard/ozop directory via TWRP. If still doesn't work, restore your system backup you created in step 1 using TWRP.
Hope you find it useful. If so, please hit the thanks button.

thank you friend

how to implement this for other phones like OP or xiaomi?

Could this be done, but only in one application?
For example, instagram is super poorly optimized in stories for this type of screen; the other day he optimized himself to be able to take photos in 1920x1080, but from one day to the next he returned to full screen, this way one does not know what the other people will see and what if; So my question, could you just put the instagram app in this mode?

maruf8 said:
how to implement this for other phones like OP or xiaomi?
Click to expand...
Click to collapse
each manifacturer have their own implementation. So there isn't a simple way to make it applicable for all. OnePlus for example has this option already in Oxygen OS. Not sure about Xiaomi.

xxxcazador said:
Could this be done, but only in one application?
For example, instagram is super poorly optimized in stories for this type of screen; the other day he optimized himself to be able to take photos in 1920x1080, but from one day to the next he returned to full screen, this way one does not know what the other people will see and what if; So my question, could you just put the instagram app in this mode?
Click to expand...
Click to collapse
You can use tasker so that each time you start instagram it runs the resolution command. Use Google to learn how to use it. But warn you, its very advanced.

There is no shell such as wm overscan on my phone. Is that exclusive?

this worked perfectly for me! thank you very much! Do you have any idea how to port this over to RUI 2 or LineageOS 19?

Related

[APP] SGS Tools

View the sourcecode on google Code!
Don't let the app die, develop for it/include its features in another app.
Latest version (4.1.9) can be found on page #37
Hi,
I have written an app, which contains useful functions specially for the Galaxy S imho.
It can do the following things:
-Secret codes list (contains at the moment 31 codes)
(Don't worry clicking around, there will appear a popup if you have selected factory/hard reset )
-System clean up: this means you can delete all system apps you don't like with 1 click. It will remove the .apk, the .odex and the data directory.
It won't let you delete apps that will "brick" your phone, so very useful for android beginners.
-MarketFix: This sets the Fingerprint in the build.prop to JF3 (2.1) and cleares the market cache. After a day you should see 120 hits when searching for "documents".
Useful if you are using a test Firmware and don't see copy protected apps in market.
-Homescreen Settings: In this Menu you can set the default screen (press the home button when you are already on the home screen) and the screen count.
Only works with some Firmwares! Works for example with JM5, JM7.
-Move SGS Tools to System: This will save the app on the device if you do a factory/hard reset. You can also undo this.
-Run a script.
This menu can run scripts, which are written as .txt files.
Simply write every command in a new line and put the script.txt to /sdcard/sgstools.
It checks the inputstream of the process, for example if you want to notify the user about progress with "echo /sdcard/test removed", this will appear in the progressdialog. It also checks the errorstream and will display, if for example a command could not be found.
- Enable/Disable boot/shutdown sound or place custom sounds
-Last but not least, you can add shortcuts to homescreen, which let you run commands. Useful for example as shutdown, reboot recovery, reboot, etc.
There's a bug in 2.2 Firmwares, which won't let you pick custom icons for shortcuts! (I tested it on 2.2 Emulator and also anycut won't set an icon on 2.2 Firmwares..)
That's it. Hope you like it.
(Sorry, it's not on the market - I don't have a market account yet )
PS: Press Menu Button to access further menus.
PPS: It uses a custom menu
PPPS: Rotate the device, and you will see in some menus a rotation animation!
PPPPS: German users can also look in this http://www.android-hilfe.de/samsung-galaxy-s/33978-sgs-tools-app-zum-schnellen-bearbeiten.html.
Ver 3.0: - now translated into english
Ver 3.0.1 - Bugfix: added permission to install shortcuts
Ver 3.1
- Activity handling improved
-new tool for setting boot sound / shutdown sound
Ver 3.1.1:
-MarketFix improved: now show better warnings, for example if busybox is not installed.
-Now a .nomedia file is created in the sgstools folder.
Ver 3.2
-Bugfixes
Ver 3.2.1
-Bugfixes: -Warning when removing system apps now in english
-Standard icons fixed for creating shortcut. (sry, but the broken icons will be only fixed if you deinstall the old version before)
Ver 3.3
-When removing system apps, the .apk and the .odex will be backuped in /sdcard/sgstools
Ver 3.4:
changes
edit: I forgot, please deinstall the old version, so you can read the disclaimer
Ver 3.5.1:
.prop editor bugfix
added 2 small scripts: mount /system ro/rw
command shortcuts now with basic commands (shutdown, reboot, mount..)
Ver 3.6
- script modul update, can now execute .txt scripts wrapped in a .zip
Ver 3.6.1
- script modul can now handle .zips with several scripts in it
Problems with busybox should be fixed now!
Ver 3.8.3
-some useful scripts
-backup & restore your homescreen
Newest version is 4.1.0
-added some tw launcher mods
-modded contacts.apk
-modded browser
-hacked camera.apk
-reverse scripts
If you want to donate something for this free app (Paypal) you can use the following link:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XEMXTUYAZVUGY
I guess it requires root access? Haven't tried yet but the description looks great.
Very nice app.. Good Work..
ssj4Gogeta1 said:
I guess it requires root access? Haven't tried yet but the description looks great.
Click to expand...
Click to collapse
Yeah requieres root, but not for the secret codes.
Nice one!
You could also add a option to change system sounds, bootscreens etc. (very SGS specific)
Fr4gg0r said:
Yeah requieres root, but not for the secret codes.
Click to expand...
Click to collapse
Very nice app I have just one remark about secret codes, it seems that the secret codes executes directly which is very handy but in a case of "HARD RESET", Factory data reset" I think the user should been warned about danger this commands can do before one pinch those links
Can you implement that in your app ?
Wow! Looks amazing. Is the rotation animation just in that application or across the whole device?
lajson said:
Very nice app I have just one remark about secret codes, it seems that the secret codes executes directly which is very handy but in a case of "HARD RESET", Factory data reset" I think the user should been warned about danger this commands can do before one pinch those links
Can you implement that in your app ?
Click to expand...
Click to collapse
When users execute the Factory data reset code they come in a window in which they explicitely have to agree by clicking a button (same window btw when you trigger factory data reset from the settings->security menu... which also don't present a warning btw)
Hard reset is tricky on the other hand. You never wanna trigger that one
lajson said:
Very nice app I have just one remark about secret codes, it seems that the secret codes executes directly which is very handy but in a case of "HARD RESET", Factory data reset" I think the user should been warned about danger this commands can do before one pinch those links
Can you implement that in your app ?
Click to expand...
Click to collapse
Already implemented, look at attached picture. Or did u meant a second warning?
@Hard Reset:
I needed that 2 days ago, in order to use the lagfix. I had not enough space on data and only a hard reset (or manually removing much files) could solve that.
LevitateJay said:
Wow! Looks amazing. Is the rotation animation just in that application or across the whole device?
Click to expand...
Click to collapse
Rotation is only in that application, sry. For whole device you would have to modify the Framework, which isn't possible because it's not open source.
You would have to build a rom from aosp to implement that.
appelflap said:
Nice one!
You could also add a option to change system sounds, bootscreens etc. (very SGS specific)
Click to expand...
Click to collapse
Bootscreens is a very nice idea.
I will look if I can implement that feature.
Fr4gg0r said:
Already implemented, look at attached picture. Or did u meant a second warning?
@Hard Reset:
I needed that 2 days ago, in order to use the lagfix. I had not enough space on data and only a hard reset (or manually removing much files) could solve that.
Click to expand...
Click to collapse
OK, I was just testing some secret codes in your app and saw that they were executed directly and then I hadn't guts to pinch the hard reset and factory reset links and hence was my question to you.
But now I know better and can bee shore that they can't do some major damage if I stupidly do a mistake and pinch those links
BTW a very nice touch the sliding menu
As a suggestion you could maybe implement APN backup as well
5 stars Fr4gg0r, so useful. Many thanks!
Custom Bootanimation seems not to be possible at the moment..
But I will add enable/disable Bootsound later this day.
Fr4gg0r said:
Rotation is only in that application, sry. For whole device you would have to modify the Framework, which isn't possible because it's not open source.
You would have to build a rom from aosp to implement that.
Click to expand...
Click to collapse
So because Samsung's version of Android is closed source we can't implement it but say in Cyanogen Mod it would be possible? This is one of the major features I want to see in Android, adds a nice visual touch.
I think it should be possible in a Cynogen Mod.
But it's not said, that the system is powerful enough to handle that with heavy views..
okay, for the noobs here (meaning me), can someone do a quick "how to" install instuction
tks - and i am rooted
'Homescreen Settings' doesn't work for me
I set 'default: 2' and 'amount of screens: 5'. After press apply and reboot, no results. If I press home key, always show me the first one (0)
rafalense said:
'Homescreen Settings' doesn't work for me
I set 'default: 2' and 'amount of screens: 5'. After press apply and reboot, no results. If I press home key, always show me the first one (0)
Click to expand...
Click to collapse
I have already heard this by other people.. the problem is, for me it always worked.
Are you really using JM5 or JM7?
To exclude misunderstanding:
If you press the home button from anywhere, you will always taken to first screen. This cannot be changed.
But if you already are on homescreen and then press the home button, it should take you to the screen you have set in my app.
@larryccf
Simply copy the apk to sdcard.
Then launch the stock myfiles app, or whatever file explorer, and click on the .apk.
The file explorer should initiate the installing then.
Update to Version 3.1:
-now you can de or activate the boot / shutdown sound and also replace them with custom sounds.
-I rewrote the Activity handling, which had been very bad! Now you won't have the press several times the back key.
The new .apk can be found in the first post.
I'll attach 2 example bootsounds..
Thanks very useful app.

[GUIDE] Getting some old features back in Virtuous Sense ROMS

GUIDE: Getting some old features back
INTRO: For those who dislike some of the changes/features made to roms as they are developed and are asking how to get them back, here is a how to. It is usually a simple matter of pushing the old files from previous builds into your current rom. Keep in mind that the devs are building a rom as they see fit. As with any rom that you don't build yourself, there will always be things you want to change.
-If there is a bug, post it in the thread.
-If there is a change that you personally want, then do it yourself. Don't expect the dev, and everyone else who uses the rom, to accommodate your specific needs/wants. You may not have noticed, but you aren't the only one using the rom!
NOTE: This guide and code are meant for the virtuous sense rom, but the concept is universal. For example, if you are using some rom and the new version is posted with, say the amazon mp3 apk removed, and you want it back, refrain from cluttering up the dev's thread with a request to have it back. This is both selfish and a waste of posting space. If you are to the point of installing custom roms, you should first be able to type basic adb/terminal emulator commands to copy/delete files. In this case you would extract the amazon mp3 apk from an old .zip and push/install it into your current one. Now wasn't that easier than waiting and hoping that someone will do it for you?
NOW TO THE GUIDE:
Auto brightness mod - To revert from the auto brightness 'mod', which is far too sensitive, to the original, simply pull the services.jar and framework-res.apk from a rom before the patch, and push them to your framework folder. I've attached them to the second post for ease.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/framework/services.jar
adb shell rm /system/framework/framework-res.apk
adb push [directory of saved file]\services.jar /system/framework
adb push [directory of saved file]\framework-res.apk /system/framework
Reboot
-------------------
Keyboard mapping - The www/com key has been changed to a tab, which is good, as it was non-functional before. However the user keys have been changed too. I've modified a file which keeps the www/com key as TAB but also keeps the user keys as user assignable keys. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [directory of saved file]\vision-keypad.kl /system/usr/keylayout
Reboot
-------------------
Rosie auto-rotate - If you want to keep it so that rosie will only be in portrait mode with the keyboard closed, but dont want to turn off auto-rotate throughout all apps, just push the old rosie. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/app/com.htc.launcher.apk
adb push [directory of saved file]\com.htc.launcher.apk /system/app
Reboot
Attachments:
You need to rename "services.jar.zip" back to "services.jar" and "vision-keypad.kl.zip" back to "vision-keypad.kl". This is because the forum wont let you upload .kl and .jar extensions as attachments.
Thanks so much for this. I'll definitely be pushing the auto-brightness mod back, and I may do the keyboard, too (might let others do that one first, or see if rmk40/eViL release an update with that first).
Thanks for this!
Sent from my HTC Vision using Tapatalk
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
android602 said:
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
Click to expand...
Click to collapse
What version of virtuous are you running? Did you rename it and remove the .zip from the end?
I'm using that exact file w/ no issues
calendar/lockscreen
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
Lockscreen - no.
Calendar - maybe, haven't tried. However I did find these 2 threads by typing in the words "htc calendar" in the search box (which means you didn't search very hard )
http://forum.xda-developers.com/showthread.php?t=795222
http://forum.xda-developers.com/showthread.php?t=723761]
They may help you.
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
fox-orian said:
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
Click to expand...
Click to collapse
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Can this be modified to restore ".com/www" to G2's?
the1wingedangel said:
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Click to expand...
Click to collapse
Yup, and I have "always show extension" enabled in folder options, so I definitely got rid of the .zip.
Maybe I'll fiddle with it a little more, see if I missed something.
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
fox-orian said:
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Click to expand...
Click to collapse
Weird, I have no idea why that won't work for you. Anyway, there is another way around it. Just open up your patch.zip (from 0.7.0 to 0.7.4), go to the framework folder, and remove the services.jar and framework-res.apk from it. Then go about the wipe/install of both zips like normal. That way the patch zip will no longer replace those two files. Anything that you don't want changed in a patch zip can just removed from it.
Snap Jackel Pop said:
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
Click to expand...
Click to collapse
Sorry cant help on that one, I haven't run a CM rom since like 1 or 2.0 haha. You may try to see if others are having that problem, or if it is a known issue with the 6.1 and streaming videos. Is it only that site? Maybe a flash player version problem?
rmk40 said:
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Click to expand...
Click to collapse
Yea, I assumed it would be out-dated soon anyway, as changes are made to your roms. I'll adjust it to keep up if the need is there though. It was just a couple of the more simple alterations that I made, and after seeing so many people cluttering up your thread with posts about them, I decided to post this.
Mostly, though, I just wanted to remind people that many simple issues/personal needs (like an app being removed from a rom, or a small change to one or two apps) can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
the1wingedangel said:
many simple issues/personal needs can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
Click to expand...
Click to collapse
I really cant emphasise this enough!
Sent from my sweet G2
Do you know if there is anyone to return the power down message. I remember before there being and option to restart the phone, hibernate, power off, or reboot into recovery. I liked having that. Is there anyway to return this feature?
Sent from my sweet G2
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
ddotpatel said:
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
by chance, did anyone try this? if not, I will try it in a few...

Multitasking/RAM

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.

[ROOT HD 10] Enable advanced power menu (global actions) + my other framework mods!

*****ONLY WORKS FOR FIREOS 5.6.2.0 OR LOWER*****
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0 or 5.6.2.0****
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
P.S. This framework also contains all previous modifications. References:
How to guide: Enable 'ok Google' to work from ANY screen
[ROOT] [HD 10 2017] FireTabletSettings.apk Rewritten [August 22, 2018]
[FIRMWARE] [STOCK] Pre-rooted, optimized, stock firmware for HD 10 Suez [APRIL 2019]
[Root] [HD 10 Suez] Remove parental control applications/restrictions [May 2019]
[TEST] [Flash Zip] [HD 10] [ROOT] All-in-1: The ultimate hacks, tricks & mods zip
[Root] [App] [All tablets] Disable & replace lock screen - set custom wallpaper
NO ROOT REQUIRED: Working Screen Mirroring
UPDATE (for 5.6.1.0):
June 1, 2019
- Increased default system volumes from -6 db to 8
- Set preference for 5ghz wifi to false. Setting this to true only allows 5ghz connections. 2ghz are ignored if set to true.
- Fixed typo in time server I found in the system logs.
- Extend network attributes (I don't know if these actually work but doesn't hurt either way)
- Wpa_supplicant_scan_interval by default is set to 15000.... milliseconds. Raised value to 150000000. This may have been the cause of disconnects on a constant level.
- preferences prefer dual pane set to true
- Bar separating notifications from system messages was narrow (set to true). Set it to false.
- Low battery warning is now 10% instead of 25%. Extreme low battery warning (almost dead battery) set at 5%
DragonFire1024 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
Click to expand...
Click to collapse
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?
sga999 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?
Click to expand...
Click to collapse
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x
DragonFire1024 said:
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x
Click to expand...
Click to collapse
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?
sga999 said:
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?
Click to expand...
Click to collapse
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.
DragonFire1024 said:
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.
Click to expand...
Click to collapse
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.
sga999 said:
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.
Click to expand...
Click to collapse
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.
@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.
DragonFire1024 said:
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.
Click to expand...
Click to collapse
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
sga999 said:
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>
Click to expand...
Click to collapse
Correct. First config set to 1 and leave the others as is, unless you want to test them out.
Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
I have not. I rarely touch that at least not Amazon smali. It doesn't translate well at all. And haven't really had to so far. And the framework is odexed...well the .jar in system/framework is, so they don't have smalis.
bibikalka said:
@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.
Click to expand...
Click to collapse
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.
DragonFire1024 said:
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.
Click to expand...
Click to collapse
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.
bibikalka said:
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.
Click to expand...
Click to collapse
Install framework in OP then you need to enable the advanced power menu in gravitybox, power tweaks. Then long press power button, tap restart, then you get your options for reboot.
Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
Also for the most part Amazon just moved configurations around maybe changed a few characters or couple of words. But for the most part a significant portion if not almost all of the Android source for this version was left inside these files. There are very few things I actually had to rebuild. The battery stats is one of those things. Other things are more difficult and require other pieces of software, for example specific apks. That took quite a lot of time to hunt down working versions of certain apks. Remember we are working with what is considered a stone age OS version. So we have to literally search for needles and haystacks just to find the one tiny thing that makes it all work... Well at least some of it
Gosh, I tried for a long time to decompile/recompile framework-res.apk (5.6.3.0)...no luck! I'm using your instructions in post 2 in the 7 wallpaper thread as a guideline. I can decompile successfully. Then, even without making any changes at all, recompile does not work. I won't bother to put the error display here unless you're interested. (systemui.apk fails on the recompile also, but in a different way). A "regular application" will decompile and recompile just fine.
So I have no idea what's wrong. I do have xposed/gravitybox installed, and I wonder if that causes the problem (but it sounds like have those also?). Or some change to 5.6.3.0 that you did not encounter with prior releases. I'm wondering if you can upload your framework-res.apk somewhere so that I can try that. At least that would narrow it down to the new release or my error.
There are lots of posts about this kind of problem, but they mostly talk about wrong paths, etc. That is definitely not my issue.
I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tried to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!
sga999 said:
I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tired to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!
Click to expand...
Click to collapse
Lol it's going to take a bit to get used to everything. I actually had messed around with apktool when I first started all this and got so frustrated I just stopped trying. 6 months after that I tried again and it took me a week or so before I successfully compiled and installed a system apk. My initial goal was to use this method to try and trick a non rooted tablet into thinking it was installing an update to a system app. Though it worked on rooted devices, I could never get it to work for non rooted ones. Don't give up,keep trying and re check everything, especially make sure your PATH to the proper tools is correct. I'll look at the latest fireOS framework tomorrow.
P.S. without any further modifications, I tested APM+ Xposed module and it works too. You can add and remove all the optioions plus add different ones depending on the module. No further tweaking needed on my end.
Okay, when dragging and dropping res, it does finally ask if I really want to copy AFTER it takes quite a while "extracting". I was confusing extracting with unzipping or unpacking...or some other term that would imply it was changing the format. I'm still not sure if it's doing it properly, but I'll keep trying. And I'd still like to know how to make these combined posts cause a notification, and if not, how can I force it to.

How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root-Update

Ready to Unlock, Root, and Update factory images on your Pixel 6 Pro?
There are some really good guides by V0latyle here, and by roirraW "edor" ehT here which are great for veteran/regular users who are really familiar with adb/fastboot and the commands, steps used in the unlocking, rooting environment.
This step by step is for people like ME who are not adb/fastboot gurus, who need every step spelled out so we don't brick our over-priced flagship devices
* * *P L E A S E READ THIS FIRST B E F O R E UPGRADING TO ANDROID 13* * *
What You Need On Your PC:
Factory Image
MAGISK - Canary 24310
SDK Platform Tools & USB Drivers (first time installation)
(additional files I use: optional)
Working SafetyNet @Pekempy
Kirisakura Kernel @Freak07
*** MAKE SURE YOU EXTRACT THE CORRECT BOOT.IMG FILE TO PATCH IN MAGISK ***
-download latest factory image, unzip the MAIN image.zip, then unzip the SECONDARY image.zip , copy the contents of the SECOND image.zip into the same platform tools folder that has the fastboot application in it, then open the image.zip you just copied into the fastboot folder and copy the boot.img and paste it somewhere on your PC.
Device Setup PRIOR To Starting Fastboot:
Settings>About phone>Build Number (click build number until you see YOU ARE NOW A DEVELOPER)
Settings>System>Advanced>Developer Options
Enable OEM Unlocking & USB Debugging & USB Configuration> enable FILE TRANSFER
Unlock the Bootloader, Update Factory Image, and Get Root:
1- Boot your device into bootloader/fastboot (hold power / vol down)
2- Connect USB cable to device and PC ( have diff USB cables available for troubleshooting)
3- From address bar in the platform tools folder where the fastboot application is located on your PC, type CMD to open command prompt window
4- Type FASTBOOT DEVICES, if you see a serial number(s) you are ready, if you don't, verify you've properly set up platform tools folder, change cable, check command, try again)
5- TO UNLOCK BOOTLOADER- type fastboot reboot bootloader (***YOUR DATA WILL BE WIPED***)
6- Type fastboot flashing unlock
7- Type fastboot reboot bootloader
IF UPDATING TO ANDROID 13 FOR THE FIRST TIME IT IS HIGHLY RECOMMENDED YOU FLASH THE 13 BOOTLOADER TO BOTH SLOTS BEFORE UPDATE (read warning at top of page) Follow step 7a to accomplish updating both slots to the Android 13 bootloader:
7a. Type fastboot flash bootloader --slot=all <bootloader image in platform tools>
PRIOR TO FLASHING THE FACTORY IMAGE:
-if you want a clean install, WIPING ALL DATA, skip to step #8
-if you want to SAVE data, edit the FLASH ALL.bat file, REMOVING the -w (leaving just ONE space between the remaining text) and SAVE the file (reopen file to verify -w is removed)
Disabling Verity and Verification isn't required except for use with some custom kernels, but just rooting those custom kernels with the latest Magisk Stable v24.1 or higher should make them not require disabled Verity and Verification anymore. click HERE for more
8- Flash the factory image by typing FLASH-ALL
9- After the install, it will reboot into system, let everything settle, skip start up options and get to where you can download the latest MAGISK apk on your device (downloads folder)
***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***
10- Connect your device and PC and put the extracted BOOT.img file (from the CURRENT factory image you are flashing FOUND IN THE SECOND ZIP FOLDER) that you placed on your PC, put it on your mobile device where you can easily find it (I created a folder FILES TO FLASH)
11- Install Magisk (use Canary 24310 linked above), follow instructions to allow files like this to be installed) ***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***
12- Open Magisk and choose SELECT AND PATCH FILE (select the BOOT.img you just put on your device
13- Copy the new PATCHED BOOT.img from your download folder back into your PLATFORM TOOLS folder where the fastboot application is located on your PC
14- Boot device into fastboot/bootloader, connect device and PC
15- Type CMD in address bar and verify fastboot connection (step 4)
16- Type fastboot reboot bootloader
17- Type fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img)
18- Reboot into System
UPDATE Factory Image WITHOUT Wiping Data:
1- Within the Platform Tools folder, find the FLASH-ALL (.bat) file
2- Open it with text editor and remove the -w (keep ONE space between remaining text, SAVE file, reopen to verify -w is removed)
3- Verify FASTBOOT DEVICES by typing CMD in the address bar of the same platform tools folder
4- Type FLASH-ALL
5- Let it boot into system and settle for a minute
6- Patch the boot image (follow steps 10, 12 -18 above)
*** Thanks to V0latyle, roirraW "edor" ehT, and Lughnasadh for the foundations of these instructions! ***
Please let me know if any part of this process is incorrect, has been updated, or is no longer necessary
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
+1
Your guide is exactly what I have been summarizing in one of the threads already.
They keypoint now is on how to apply monthly updates without wiping the phone all the time while also still getting root
Az Biker FTW! Good to see you here buddy! (I remember you from the Pixel 2/4 XL forums)
Thanks @Az Biker! I'll update the OP of my thread to link to this thread just as soon as I can find the time.
dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
I've never done the OTA method, so I don't have a step by step for that. Sorry.
How can I re-lock the bootloader?
I'm getting a "command error" with fastboot flashing lock
dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
You can find the OTA sideload method here...
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Maybe it makes more sense to combine and improve upon existing tutorials, instead of creating a load of new ones. It's getting a bit confusing here, ESPECIALLY since we don't have any sub-threads/forums.
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Morgrain said:
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Click to expand...
Click to collapse
Did you see the responses about this subject starting here?
Personally, I haven't had a problem with the way they're doing the forums now. The Quick Filters at the top have been good enough for me when I want to concentrate on one of those particular types of posts.
FYI, although I'm a proponent of the new way, I'm not particularly against the old way. That's what I got used to, too, but things change.
roirraW edor ehT said:
Did you see the responses about this subject starting here?
Personally, I haven't had a problem with the way they're doing the forums now. The Quick Filters at the top have been good enough for me when I want to concentrate on one of those particular types of posts.
FYI, although I'm a proponent of the new way, I'm not particularly against the old way. That's what I got used to, too, but things change.
Click to expand...
Click to collapse
Good to know. Nope, I did not notice that. And I don't really like the filters. I'm used to , uhm, use XDA on my PC with multiple monitors, and the old style forums allowed me to just middle mouse button Press every sub forum, enabling me to open all of them in separate browser threads in the course of a second, which made quickly tabbing / shifting through sections /threads extremely quickly / efficient, at least for someone used to that kind of usage. Now I'm stuck with the heck load of filters and that just slows down the way I browse by factor three, if not more.
This new system is also quite confusing. Back in the days whenever you open a sub forum, you had an easily distinguishable sort of sticky threads. Now it just feels all cluttered together. It made browsing XDA less fun and it just feels tedious.
vibrantliker said:
How can I re-lock the bootloader?
I'm getting a "command error" with fastboot flashing lock
Click to expand...
Click to collapse
Check to be sure you only have one space between each word, and no typos.
I believe fastboot oem lock will work as well.
Make SURE you are running a stock, factory image before doing this (just in case you weren't aware).
Morgrain said:
...use XDA on my PC with multiple monitors, and the old Style forums allowed me to just middle mouse button Press every sub form to me to open all of them in separate browser threads, which made quickly tabbing / shifting through sections /threads extremely quickly, at least for someone used to that kind of usage.
Click to expand...
Click to collapse
Ha! Now that you've reminded me, I used to do the exact same thing here (I too middle mouse button, in general, a lot). Maybe it's been beneficial to me that I've barely had any activity on XDA for the last five years, and especially the last three years.
Thank you, however readability is very bad on a light background. Please change font color.
Tomatot- said:
Thank you, however readability is very bad on a light background. Please change font color.
Click to expand...
Click to collapse
Changed the font to "brown", let me know if that helps with the light theme.
I'm on Xda-dark and hadn't thought about the readability using light theme, thanks!
Az Biker said:
Changed the font to "brown", let me know if that helps with the light theme.
I'm on Xda-dark and hadn't thought about the readability using light theme, thanks!
Click to expand...
Click to collapse
I thought of that, that's why I dared to mention it.
It's better indeed!
Morgrain said:
Maybe it makes more sense to combine and improve upon existing tutorials, instead of creating a load of new ones. It's getting a bit confusing here, ESPECIALLY since we don't have any sub-threads/forums.
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Click to expand...
Click to collapse
Sorry for the late response.
FILTER TABS (new way) vs Sub Forums (old way):
Look at it this way:
You're grocery shopping online, and you want to browse the candy bar selection. The store has candy bars in several areas, not just in one place, so now you have to look through pages and pages of all the available product.
Rather than try to scroll through everything in the store to just find the candy bars, you click the CANDY BAR filter tab, and ONLY the candy bars are visible now.
So even though they aren't technically in one single area of the store, you can only see the candy bar selection on your page.
That's how the new forum works. Want to only see Development threads? Click the DEVELOPMENT tab at the top of the device forum.
@Az Biker
could you please make the guide for update factory image with out wiping. and keep root. please please please.
Lw00d said:
@Az Biker
could you please make the guide for update factory image with out wiping. and keep root. please please please.
Click to expand...
Click to collapse
That would be awesome. Just looking around for that as well.
Is it possible to get root without wiping? Currently I only have the bootloader unlocked and I'm on .036

Categories

Resources