Related
Okay i'm running the latest nigthly of CM10.1 and I decided i wanted to try and get CRT animation going by altering framework-res.apk, i've tried the decompiling tool but constantly got the ECHO errors. But I found a way to decompile it, but the "folder" that everyone says to edit "bools.xml" in is not in the framework-res.apk the framework-res.apk/res/values/bools.xml.
So how exactly can I alter my framework-res.apk to enable the animation.
FreakyFreakGA said:
Okay i'm running the latest nigthly of CM10.1 and I decided i wanted to try and get CRT animation going by altering framework-res.apk, i've tried the decompiling tool but constantly got the ECHO errors. But I found a way to decompile it, but the "folder" that everyone says to edit "bools.xml" in is not in the framework-res.apk the framework-res.apk/res/values/bools.xml.
So how exactly can I alter my framework-res.apk to enable the animation.
Click to expand...
Click to collapse
I'd personally forget all that. I just dug around and found this method in the Samsung forums.
Follow the instructions here to install the Xposed Framework 2.1.1, and reboot.
Code:
http://forum.xda-developers.com/showthread.php?t=1574401
Then install the XposedTweakBox module from here. Reboot, presto!
Code:
http://forum.xda-developers.com/showthread.php?t=1629653
Hope this works for you. No decompiling required at all.
There are a couple of people whose navigation bar on their N4 isn't working. I'm talking about this.
Found a github repository which contains the fix (credits to gkraynov) for all stock releases: https://github.com/gkraynov/nexus-4-navfix
I've recently installed this ROM, which has a different build number (LMY48G), so this solution would not work for me, because stock 5.1.1 has LMY47V.
The fix (source): https://android-review.googlesource...droid/systemui/statusbar/policy/DeadZone.java
My steps were:
1.) Decompiled the SystemUI.apk with apktool (to get to the smali file):
Code:
java -jar apktool.jar d SystemUI.apk
Here's the decompiled source in a zip file.
2.) Decompiled the same apk with http://www.decompileandroid.com/ to get the java source
3.) Compared the source of the fix with corresponding smali and java file, like in this image.
4.) Recompiled with:
Code:
java -jar apktool.jar b SystemUI
5.) Pushed the apk back to the phone:
- set root access for adb and apps on phone under developer settings
- adb root
- adb remount
- adb push SystemUI.apk /system/priv-app/SystemUI.apk
After that I rebooted the phone, which didn't display the navbar anymore, so I've must have made a mistake somewhere.
Can someone, please, take a look and tell me, what I did wrong? I have zero experience with this.
You can share files you edit?
You didn't set perms right. Reboot to recovery and fix permissions or just change the permissions to
RW-R--R--
I also want to wear a custom rom , but the nav bar I do not work , if you can help ?
chmod?
Can anyone compile this source with android 6.0 marshmallow
Sent from my Nexus 4 using Tapatalk
I tried, I've tried to edit Deadzon.java but I am confused as to restore the file to dex for compile into apk again
I did the same thing using TMA to decompile and to update and got the same issue.
No more NAVBAR.
Any clue?
It appears that the code edit it`s not correct.
Using another tool http://bytecodeviewer.com/ to reverse engineer it appears wrong.
I am also newbie at this.
Can someone help?
same here
I have encountered the same issue with my N4.
To fix it, I tried a stock reset. Did not work.
Than I granted myself root access, installed CyanogenMod, which then allowed me to use the "pie"-Navigation, which works great.
I also found out, because of the full screen option etc., that the area of the screen of the broken navigation bar should be working, as it appears to work in different apps in landscape-mode.
So... My problem is now that I can't try out the patch you writing about because now I am using CM13, not the Stock Version which the fixes are referring to.
I am really new to all this ROM stuff (all I know about it is from this very day) - So, is there a way of applying this way of fixing the navigation bar to CM13?
Thank you.
Sackhaar said:
I have encountered the same issue with my N4.
To fix it, I tried a stock reset. Did not work.
Than I granted myself root access, installed CyanogenMod, which then allowed me to use the "pie"-Navigation, which works great.
I also found out, because of the full screen option etc., that the area of the screen of the broken navigation bar should be working, as it appears to work in different apps in landscape-mode.
So... My problem is now that I can't try out the patch you writing about because now I am using CM13, not the Stock Version which the fixes are referring to.
I am really new to all this ROM stuff (all I know about it is from this very day) - So, is there a way of applying this way of fixing the navigation bar to CM13?
Thank you.
Click to expand...
Click to collapse
I am facing the same issue.
But I am trying to create the patch for Paranoid Rom. If I suceed I think the same concept can be use for any other rom.
Hi all..
does anyone want to help me to update this patch for Lineage OS??
https://github.com/gkraynov/nexus-4-navfix
I don't understand why this isn't a feature of stock Android. They did it with the notification bar, but why not the navigation bar? The main reason for doing this is to prevent the navigation bar from being burned into your screen. There are Xposed modules for Lollipop/Marshmallow that do this exact same thing, making this mod unnecessary on those versions of Android. Since there's no Xposed for Nougat (or if you don't like using Xposed on Lollipop/Marshmallow), doing this mod will make your navigation bar dynamically change color to match your notification bar.
***Please Note***
This isn't perfect. In applications like Google Messenger the navigation bar doesn't change to match the color of the contact you're texting, but it's better than nothing.
Prerequisites:
- Nexus 6 with USB debugging enabled in developer settings
- TWRP
- ADB fully setup and functional
- Text editor (gedit (Linux), NotePad++ (Windows), or whatever you like to use)
- Archive Manager (Linux) or 7Zip (Windows)
- Apktool 2.2.2 (link at the bottom of this post)
- Apktool Windows wrapper script (Windows only)
Step 1: Boot into TWRP
Step 2: Select mount, then select system
Step 3: Connect your Nexus 6 to your computer and fire up a terminal (Linux) or command prompt (Windows)
Step 4: Navigate to the folder containing ADB (platform-tools).
Step 5: Type "adb pull system/framework/framework-res.apk".
Step 6: Type "apktool if framework-res.apk" This installs the framework
Step 7: Type "apktool d framework-res.apk" This decompiles the apk
Step 8: Navigate to res, values, and open styles.xml with your text editor of choice
Step 9: Search for "navigationBar". There will be three instances of it. You only have to change the last two. Change "@colorBlack" to "?colorPrimaryDark" and save your changes
Step 10: Open colors.xml and search for "input_method_navigation_guard". Change "ff000000" to "00000000" and save the file. If you don't change this, the navigation bar will turn black when you open the keyboard
Step 11: Go back to your terminal window/command prompt and type "apktool b framework-res". This recompiles the apk
IF YOU SKIP THE FOLLOWING STEP YOU WILL END UP IN A BOOTLOOP!!!!!!!!!!
Step 12: Delete META-INF and AndroidManifest.xml from the modified framework-res.apk and copy over the ones from your original framework-res.apk
Step 13: Push the modified framework-res.apk to your device with ADB or by boot into recovery, copy it to your phone, and use the TWRP file manager to move it to /system/framework. If you do the TWRP method, be sure to set the permissions to 0644 or your phone will not boot.
Step 14: Boot up your Nexus 6 and test it out!
Link to Apktool
Nice tutorial. However, the reasons you're having issues "reusing" an existing modified copy of framework-res.apk are twofold.
1. You're re-signing a system app. Unless things have changed in the four years since I last modified framework-res.apk, system apps are not signed.
2. The apk can also be moved into /system/framework using a file explorer on the device. It simply cannot be done in one shot as the permissions need to be changed prior to the final move into /system/framework.
The framework is Android version dependent, so an Android 5.x framework will not work in Android 6.x or 7.x. However, replacing the framework on multiple copies of the same version of Android is certainly possible. I have to head off to work, but when I have a spare moment upon getting home I'll generate a "reusable" framework, and a flashable zip as well.
Strephon Alkhalikoi said:
Nice tutorial. However, the reasons you're having issues "reusing" an existing modified copy of framework-res.apk are twofold.
1. You're re-signing a system app. Unless things have changed in the four years since I last modified framework-res.apk, system apps are not signed.
2. The apk can also be moved into /system/framework using a file explorer on the device. It simply cannot be done in one shot as the permissions need to be changed prior to the final move into /system/framework.
The framework is Android version dependent, so an Android 5.x framework will not work in Android 6.x or 7.x. However, replacing the framework on multiple copies of the same version of Android is certainly possible. I have to head off to work, but when I have a spare moment upon getting home I'll generate a "reusable" framework, and a flashable zip as well.
Click to expand...
Click to collapse
1. The first time I did this I didn't sign the app and ended up in a bootloop. After researching the issue I came across a post that said signing the app was necessary. Signing it fixed my problem, so I've signed it ever since out of habit. Next time I do this I'll skip signing it and see what happens. If I don't get a bootloop I'll remove it from the guide. It's possible I had a permissions error or something.
2. While moving it with a file explorer is possible, I just prefer ADB, so that's why I used it in my guide.
I realize that they're version dependant. I wasn't trying to use a modified framework-res from Marshmallow on Nougat or anything like that. For example, when I tried reusing one from the November factory image on the December security update, or one from the November image on Pure Nexus, I get a bootloops, so that's why I assumed it necessary to create a new one each time. It's not like this mod is hard or takes a large amount of time, so why not redo it each time just for fun?
Face_Plant said:
It's not like this mod is hard or takes a large amount of time, so why not redo it each time just for fun?
Click to expand...
Click to collapse
Not everyone likes playing around with app mods. When I last did it, it was to enable the network location service on a Coby tablet running Android 4.0.3. That was NOT fun as it involved smali editing. At least this is only an XML edit.
Strephon Alkhalikoi said:
Not everyone likes playing around with app mods. When I last did it, it was to enable the network location service on a Coby tablet running Android 4.0.3. That was NOT fun as it involved smali editing. At least this is only an XML edit.
Click to expand...
Click to collapse
I didn't mean for all mods, just this one. Like you said, it's only simple changes to two XML files.
After getting some practice by doing this a couple of times it only takes a few minutes to complete, depending on the speed of your computer. It takes me about 30 minutes since my Ubuntu machine is an old early 2000's PC that takes about 10 minutes to decompile the app, 10 minutes to sign it, and 10 more to recompile it... I'll be able to knock 10 minutes of that time if what you're saying is correct and signing it is unnecessary.
I'll try it again after class today and remove the signing bit if all goes well [emoji106]
Great write-up, worked well OP!
You can after recompile of the framework-res folder, you can delete the AndroidManifest.xml in the new APK, and copy the AndroidManifest.xml and META-INF folder from the original framework-res.apk into the newly built APK...hopefully that makes sense.
No need to sign. That's what I did and it worked just fine, eliminates a step. I use 7zip to do all of that BTW.
RMarkwald said:
No need to sign. That's what I did and it worked just fine, eliminates a step. I use 7zip to do all of that BTW.
Click to expand...
Click to collapse
Good to hear. Those steps have been removed from the guide.
I wonder why signing it fixed my problem when I did this on Marshmallow earlier this year... I guess I screwed up something else and the second time around when I signed it I didn't screw up whatever I did wrong the first time.
Face_Plant said:
Good to hear. Those steps have been removed from the guide.
I wonder why signing it fixed my problem when I did this on Marshmallow earlier this year... I guess I screwed up something else and the second time around when I signed it I didn't screw up whatever I did wrong the first time.
Click to expand...
Click to collapse
Could depend on the app maybe? Not too sure there. I started wanting to learn modding apks (mainly making color changes, etc) by guides similar to this, the whole "I wonder if I can do that?" thing. Hopefully this will encourage those looking to try something like this that isn't too difficult to do to give it a shot and try it, just remember to have a backup of framework-res.apk handy, always can be adb pushed back via recovery if something goes south.
Thanks again for this OP, so far working great!
Awesome write up!
Not trying to hijack the thread, but for those not comfy making mods, there is "an app for that" Navbar Apps
Simple app that will dynamically change your nav bar color as well as other goodies.
recompiling it fails. i get this error on Ubuntu 16.10 I even tried using sudo
I: Using Apktool 2.2.0-dirty
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml
at brut.androlib.Androlib.readMetaFile(Androlib.java:258)
at brut.androlib.Androlib.build(Androlib.java:270)
at brut.androlib.Androlib.build(Androlib.java:263)
at brut.apktool.Main.cmdBuild(Main.java:224)
at brut.apktool.Main.main(Main.java:84)
Caused by: brut.directory.PathNotExist: apktool.yml
at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:105)
at brut.androlib.Androlib.readMetaFile(Androlib.java:254)
... 4 more
how do i deal with this?
i see the yml file right in the folder
kidhudi said:
recompiling it fails. i get this error on Ubuntu 16.10 I even tried using sudo
I: Using Apktool 2.2.0-dirty
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml
at brut.androlib.Androlib.readMetaFile(Androlib.java:258)
at brut.androlib.Androlib.build(Androlib.java:270)
at brut.androlib.Androlib.build(Androlib.java:263)
at brut.apktool.Main.cmdBuild(Main.java:224)
at brut.apktool.Main.main(Main.java:84)
Caused by: brut.directory.PathNotExist: apktool.yml
at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:105)
at brut.androlib.Androlib.readMetaFile(Androlib.java:254)
... 4 more
how do i deal with this?
i see the yml file right in the folder
Click to expand...
Click to collapse
Is Apktool installed correctly? Have you tried using Apktool 2.2.1? Maybe 2.2.0 isn't compatible for some reason? These are obviously just guesses. I'm no master at reading error logs...
ok i figured that out..
will this technique work on nitrogen version 7.1.1 because the nav bar doesnt change but when i pull the framework-res.apk the xml files are in fact altered.
---------- Post added at 09:13 PM ---------- Previous post was at 08:24 PM ----------
Face_Plant said:
Is Apktool installed correctly? Have you tried using Apktool 2.2.1? Maybe 2.2.0 isn't compatible for some reason? These are obviously just guesses. I'm no master at reading error logs...
Click to expand...
Click to collapse
no the command in the tutorial didnt work. because i was compiling a folder named framework-res and not an apk all i did was remove the .apk from the command supplied and it worked finally
also i dont know if it is an error but the push command has an lsystem for the location to be pushed. that wasnt working either.
thanks for the reply bro
Thanks face_plant. It was working the whole time. I thought I would get the pixel icons lol. My bad
Great tut thanks
kidhudi said:
Thanks face_plant. It was working the while time. I thought I would get the pixel icons lol. My bad
Great tut thanks
Click to expand...
Click to collapse
Pixel buttons are from the Substratum theme I'm using. You can get those too by being on a Nougat ROM that supports Substratum and using Pixel UI theme from the Play Store.
Just a heads up, if you're on 7.1.1 the theme won't work. It needs to be updated to support 7.1.1. Haven't tried it on 7.1, so it may or may not work.
I DID NOT CREATE THIS ROM OR THE RECOVERIES OR FLASH TOOLS LINKED, I ONLY MODIFIED THE SYSTEM UI AND SETTINGS AND BUILD PROP ZIPS BELOW.
I am not responsible for any damage (if any) to your device, data, life, job or anything else you'd care to think of.
ANY QUESTIONS, PLEASE ASK IN THE THREAD AS EVERYONE BENEFITS, PM'S WILL MOSTLY BE IGNORED.
IF YOU DON'T HAVE AN UNLOCKED BOOTLOADER YOU MUST FIRST UNLOCK IT.
Download all files you want/need to your PC/External SD before starting...just saying.
[/CENTER]
Step One
Flash stock firmware for your device that the rom is based off. Readily available from Xperifirm (attached to flashtool - Bonus!), or XDA. Flash via Flashtool or Newflasher. Again, there's plenty of guides on using flashtool and newflasher, i'm not covering that here.
Step Two
Once flashing has completed, turn the device on and allow it to fully boot. Complete the setup process, and log in to your google account. Move the ROM file you already (hopefully) downloaded to internal storage (IMPORTANT STEP: I had symlink errors flashing the ROM from the External SD Card). I normally disable auto-updates in the Play Store/Whats New apps and then let it rest for 5 minutes.
Step Three
Turn your device off, boot into FASTBOOT MODE, and flash TWRP (fastboot flash recovery TWRP/ATWRP.img). If you don't know how to fastboot, see above re: XDA/Google. Unplug your device, wait 10 seconds, then boot into recovery (Hold power and volume down together, release both at at the vibration). Tick the checkbox then swipe right, and the first thing you SHOULD do is go to settings and turn the damn vibration off. :laugh:
Step Four
DON'T WIPE ANYTHING!!! You are installing on top of an already clean installation, its pointless. Press Install, select the XPERIA_PIE_XZP_1.0.zip file you downloaded earlier, and swipe right to install that sucker. Don't freak out when it takes 5 to 8 minutes for the recovery screen to change, its doing its thing, trust me. Once you get the all clear and the button down the bottom says reboot, that's pretty much all that's left to do.
Step Five
Once the phone reboots, let it settle again for a while, and deny all the requests the Chinese apps throw at you. After a few minutes, go into the root explorer app, allow root permissions when it requests it, then go to system/priv-app and delete any app starting with TG. Unless you really like Chinese bloat, in that case, proceed to set up your phone as usual.
The ROM is pretty basic at the moment but given time and based off the Oreo series, more System UI mods will become available with later versions.
CREDITS: @machao44 @uditrawat @Myself5 @Androxyde @munjeni @Ticklefish @Pandemic
@fOmey[/SIZE]
DOWNLOAD LINKS
M-ROM P v1: BASED ON 306 FIRMWARE https://drive.google.com/file/d/1eOWzREBPehv8QoCFYQfPdF4yqKH2NdB1/view
M-ROM P v1.1: BASED ON .33 FIRMWARE
https://mega.nz/#F!MNYGhKhR!OtCS6j-YBXaxcDI1sa7FlQ
Thanks to @sam.foro for uploading.
M-ROM P v1.2: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=1ZX...ixVN09Ry_vVhDf
Thanks to @Yanun
https://drive.google.com/file/d/14K-...ew?usp=sharing
Thanks to @karrouma
M-ROM P v1.3: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=10l...uGinaYCEzy-vt_
Thanks to @Yanun
TWRP: https://dl.twrp.me/maple/
Aroma TWRP: https://mega.nz/#!TdxmiaLb!FYBet5eRYHGqiLT0niRH9F90Ts_QeRdfkOfPWOAgQCM
Flashtool: www.flashtool.net/
Newflasher: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
M-Rom P v1.6 - BASED ON 10.28 FIRMWARE - Thanks to @karrouma for uploading and sharing
https://drive.google.com/file/d/1pNsIaGR2_r74INyH8p053bQStiruPEWd/view?usp=sharing
M-Rom v1.6 - English Translated
https://mega.nz/#!6ExSGYQZ!HD0YM_Sypeu5h-6K4vhKT9NkiQn_63PZG0ZPwf_kRmY
M-ROM 1.6 aroma add-on.
M-ROM v1.6 aroma add-on - contains .25 animation mod, font picker and fonts, xperia 10 boot animation, double tap to wake kernel selection (g8141/g8142), and magisk 18.1/19.0 selection.
Enjoy.
https://mega.nz/#!nZpihCqK!TvB0_-w0cdTWFBKylPUk5Da3YdLAJCc_vk5d8XNDySc
Beetle84 said:
ADD-ONS
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch (COMING SOON - UPLOADING) for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch:
Enjoy
Click to expand...
Click to collapse
Thank you my friend
Great job
Nice
Thanks for this
Nice bro
Keep it up ^^
Added Patched Services.jar Magisk Module to Post 3.
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
hasaan6545 said:
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
Click to expand...
Click to collapse
Its not a new upload so I wonder what is happening. It is the same link available from the Oreo M-ROM thread, just copied and pasted.
Are you downloading from your device or from a PC?
Removed
link opened fine. and the file is fine opened normally . no problem
Beetle84 said:
ADD-ONS
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch: https://mega.nz/#!mdhmnKwS!POI9MLzZRH9g4isgy0XCZLIhYmu6pUAnZwlXcgaM2xM
And a Patched Services.jar Magisk Module. Flash in Magisk and reboot.
306 Patched Services.jar.zip: https://mega.nz/#!LYpyHQyD!Ka21OVx-yWIM1WUb-WQLoLoJEGOZItz7V_BQMz6fbsk
Enjoy
Click to expand...
Click to collapse
can you explain the step how to deodex the pie ??
rizky_zulfikar said:
can you explain the step how to deodex the pie ?
Click to expand...
Click to collapse
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Beetle84 said:
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Click to expand...
Click to collapse
i've tried that tool, but my priv-app and framework fail to deodex there still odex and vdex file, only my app ?
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
stipi69 said:
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
Click to expand...
Click to collapse
Its a slightly modified stock rom, based on .306 dual sim Pie firmware. The rom is odexed.
I have it flashed root working, looks nice, refreshing and snappy, i guess xzp does not have hardware side sensors but you can still tap on edge of screen and bring side menu out , nice!!!
I love new camera look, huge icons in pull down menu.... not so much, haha , it is a matter of gettin use to it i guess
Great work, thanks
If you cannot flash 47.2.A.0.306 via flashtool and get same error as i did below download and copy next file:
downloaded "47.2.fsc" file to: username/.flashtool/device/G81XX, delete 47.1.fsc
https://drive.google.com/file/d/1hZR...w?usp=drivesdk (not my work in this link, credits to xda user xrenoix)
Hi, i get error in flashtool, somoene else same error?
28/048/2018 13:48:07 - INFO - Start Flashing
28/048/2018 13:48:07 - INFO - Parsing boot delivery
28/048/2018 13:48:07 - INFO - Found a boot delivery
28/048/2018 13:48:07 - ERROR - No flash script found. Flash script is mandatory
28/048/2018 13:48:08 - INFO - Sending Sync
28/048/2018 13:48:09 - INFO - Sync status : OKAY
28/048/2018 13:48:09 - INFO - Sending powerdown
28/048/2018 13:48:09 - INFO - powerdown status : OKAY
28/048/2018 13:48:11 - INFO - Device disconnected
old .270 rom flashes with no problem
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Indashio said:
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Click to expand...
Click to collapse
Does it work for XZ1?
Thanks
unless we get gravitybox (from xposed) features, like in Resurrection Remix, i'm not moving to Pie.
OP status for the first time
I just found out you can snooze it just before typing this sentence lol. But is there a way to disable the notification permanently without root?
I don't expect it to survive a reboot but if there is a way I would imagine it being achieved via ADB?
Not a big deal anymore since I just found out you can snooze it for 2 hours but hey might as well finish what I started. If you were wondering my concern is burn in but I think the icons on the status bar move? I would rest better knowing it's not there anyway.
Thanks, I appreciate it.
EDIT: Nevermind I think I did it.
System/System app settings
Then disable "Show update notifications"
EDIT 2: It did not work:laugh:
- With root I used this solution:
Edit the file: system/build.prop
copy / paste the line that contains the version number.
Example: ro.build.version.incremental=V14.3.11.0.PFJMIXM
I have put a "#" for memo and changed v10 to v14 :
Code:
# ro.build.version.incremental=V10.3.11.0.PFJMIXM
ro.build.version.incremental=V14.3.11.0.PFJMIXM
- Without root It may also be possible (to check) to modify this file with XiaomiADBFastbootTools (with the small embedded file manager).
Do I need an unlocked bootloader or root access to use XiaomiADBFastbootTools?
The Flasher, Wiper and Camera2 modules require an unlocked bootloader but everything else works without rooting or unlocking.
Click to expand...
Click to collapse