Gravity box running on marshmallow 6.0.1 - Nexus 5X Q&A, Help & Troubleshooting

Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?

cescman said:
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
Click to expand...
Click to collapse
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.

C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot

cescman said:
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
Click to expand...
Click to collapse
Then it's strange. There must be something different about our devices and the way they are set up. I haven't come across any of these issues whether on N5X or N5. My setup is:
- stock 6.0.1
- modified boot.img which allows SuperSU to work (found in Rooting guide thread in 5X forum)
- xposed framework v78
- GravityBox 6.0.2 (the only module I have installed)

I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.

cescman said:
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
Click to expand...
Click to collapse
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.

C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
C3C076 said:
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
Click to expand...
Click to collapse
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?

cescman said:
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
Click to expand...
Click to collapse
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs

C3C076 said:
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
Click to expand...
Click to collapse
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.

cescman said:
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
Click to expand...
Click to collapse
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.

C3C076 said:
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
Click to expand...
Click to collapse
No, I didn't click fix permissions in recovery, although, as I now remember, installing xposed wasn't that smooth. After installation, I got some error messages saying some services is forced to stop, and I needed several reboots, and the system needed to optimise apps each time before the phone is boot up normally at the end

deleted

Related

Dpi on lollipop

Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
Seqrch plays tore there is tons of apps
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
If you are rooted use a file manager with an editor that has root capability (like File Manager HD) and go to /system. Make a backup copy of build.prop and then edit it to change the value of ro.sf.lcd_density from 480 to something lower, like 450, 400, or 360. I tried the latter and it worked. However the appearance of some native apps like phone or camera may become funky. IF you want everything to look normal you will have to install Xposed and do some stuff like this: http://forum.xda-developers.com/showthread.php?t=2507369
Be careful not to go too low with this value. People usually don't go below 320 because the phone may not reboot afterwards. Below 360 things are not even visible, at least for me.
najoor said:
If you are rooted use a file manager with an editor that has root capability (like File Manager HD) and go to /system. Make a backup copy of build.prop and then edit it to change the value of ro.sf.lcd_density from 480 to something lower, like 450, 400, or 360. I tried the latter and it worked. However the appearance of some native apps like phone or camera may become funky. IF you want everything to look normal you will have to install Xposed and do some stuff like this: http://forum.xda-developers.com/showthread.php?t=2507369
Be careful not to go too low with this value. People usually don't go below 320 because the phone may not reboot afterwards. Below 360 things are not even visible, at least for me.
Click to expand...
Click to collapse
Ok Thanks
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
Before you attempt to use the guide that najoor suggested, be sure to backup your ENTIRE ROM and not just the build.prop file. Installing Xposed on many Note 3's and any TW devices for that matter, ends in disaster. Many are left in an infinite bootloop, causing you to need to wipe everything and reinstall your ROM.
ludeawakening said:
Before you attempt to use the guide that najoor suggested, be sure to backup your ENTIRE ROM and not just the build.prop file. Installing Xposed on many Note 3's and any TW devices for that matter, ends in disaster. Many are left in an infinite bootloop, causing you to need to wipe everything and reinstall your ROM.
Click to expand...
Click to collapse
I concur. I personally don't like Xposed anymore. It was fun the first few times I used it and then I realized it tends to be chaotic in the way it changes the system. In general any tool/software that changes things in an irreversible way without the user's explicit knowledge is in my opinion poorly written. I remember that when I had an ATT note 3 on Android 4.3 I rooted it and installed Xposed and some of its modules and was very content with myself. But then when the time came to upgrade to 4.4.2 the phone refused to do so because it saw my system as "altered in an unauthorized way". I unrooted it to no avail. I uninstalled Xposed and all its modules, once before and once after unrooting to no avail. Finally I sat down and started looking at the system files and Xposed had changed so many things without my knowledge that tracing all of them and reversing them took me forever. I had the luxury of using Safestrap back then to do trial and error but since there is no such thing for lollipop, if you don't have a custom recovery and you mess up, you will need to flash the ROM from scratch and lose your data in the process.
najoor said:
I concur. I personally don't like Xposed anymore. It was fun the first few times I used it and then I realized it tends to be chaotic in the way it changes the system. In general any tool/software that changes things in an irreversible way without the user's explicit knowledge is in my opinion poorly written. I remember that when I had an ATT note 3 on Android 4.3 I rooted it and installed Xposed and some of its modules and was very content with myself. But then when the time came to upgrade to 4.4.2 the phone refused to do so because it saw my system as "altered in an unauthorized way". I unrooted it to no avail. I uninstalled Xposed and all its modules, once before and once after unrooting to no avail. Finally I sat down and started looking at the system files and Xposed had changes so many things without my knowledge that tracing all of them and reversing them took me forever. I had the luxury of using Safestrap back then to do trial and error but since there is no such thing for lollipop, if you don't have a custom recovery and you mess up, you will need to flash the ROM from scratch and lose your data in the process.
Click to expand...
Click to collapse
I've never used Xposed and I never will, but I also have the resources and the knowledge to just change the stuff in the framework and SystemUI myself.
If I'm helping anyone upgrade their system, the first thing I ask is if they've installed Xposed or running a ROM that has it pre-installed. If they say yes I recommend them just starting over from scratch with OEM firmware, which is easy to do on any brand phone. You have Odin for Samsung, RSD Lite for Motorola, and fastboot for HTC to achieve this.

Screen off animation for HTC M9 and xposed installation

After searching high and low, i've finally found the screen off animation i wanted, this particular mod is not mine i'm just providing a find for anyone who is in the same situation.
Thanks to @zst123 for originally posting this
Requirements:
Root access
Custom recovery
Rom running android 5.0XXX
Also note functional on 5.1.XXX ROMs.
*New section for Marshmallow ROMs.
1. Go here and download this http://forum.xda-developers.com/attachment.php?attachmentid=3292041&d=1430517906
or this one if you're on android 5.1 http://forum.xda-developers.com/attachment.php?attachmentid=3313055&d=1431639027
or this one if you're on android 6.0 http://forum.xda-developers.com/attachment.php?attachmentid=3631566&d=1454436795
2. Download the Alpha build xposed framework from here http://forum.xda-developers.com/attachment.php?attachmentid=3200857&d=1425849071
or this one if you're on android 6.0 http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
3. Reboot to recovery and install the .21 or build or the .22 build if you're on 5.1XXX or the v80 sdk23 build if you're on 6.0.XXXX then reboot *NOTE* boot can take some time, 10 minutes at times
4. Once booted, install the alpha build apk downloaded in step 2 using a file manager.
5. Open Xposed and navigate to download, search for screen off animation and download the module.
6. Navigate to modules and enable them, reboot your device.
7. Open the app and choose a screen off animation.
8. Perform a reboot, Done.
FYI, it has been known that xposed can cause bootloops on the M9 so tread carefully and back up prior to installing it.
I can confirm that this and xposed with this installation method works as expected on Leedroid, other ROM's should work but I haven't tested them.
Can also confirm that for the most part, sense 6 toolbox and XUI Mod work too, and again this is not my software.
PS: Just like to add that the screen off Vertu animation is my personal favourite, it's a classy finish to a phone that deserves it.
------------------THEMING------------------
@ineedone This is his theme.
You need to flash the theme after xposed, clearing cache and dalvic after the initial installation of Chameleon. If you don't then you can (not always) end up in a boot loop, if you didn't wipe the caches then power down and boot back to recovery.
The initial boot after wiping the caches can take a long time, 10 minutes + is not uncommon.
This can also be assumed for any other mods which affect a lot of the ROMs system files.
Confirmed with Newest Leedroid and chameleon.
http://forum.xda-developers.com/showthread.php?t=3082322
@dladz
The third link has a extra http// in it.
Here's the right one
http://forum.xda-developers.com/showthread.php?t=3034811
aooga said:
@dladz
The third link has a extra http// in it.
Here's the right one
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
All sorted, thanks mate, oversight on my part.
Posted in error
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
tango280581 said:
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
Click to expand...
Click to collapse
Aye I've used gravity before but have avoided it as I get everything I need from xui and screen off animation. I don't even use sense toolbox no more. I've read that Xposed works with 5.1 and there is a framework for it but as I haven't tested it on a HTC device I've not added it to the OP that its fully functional.
Gravity needs a big update, there have been quite a few broken bits for a while, also found gravity was always very heavy on the system too, might have just been me.
tango280581 said:
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
Click to expand...
Click to collapse
Does that include stock 5.1?
Sent from my HTC One M9 using Tapatalk
neverborn said:
Does that include stock 5.1?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Stock as in not rooted or stock as in rooted on a stock rom, if it's the latter then it should work. That's probably the best way to use these mods. Unfortunately screen off animation as far as I know does not function as of yet. I'm away for a week now, but will be doing some testing of all the mods on my return.
Stock, rooted. Ive never had this much trouble just to get xposed.
Basically i:
1. Unlocked bl
2. Twrp
3. Backup of system image
4. Root
5. Xposed zip for arm64
6. Installed xposed apk
7. When trying to launch amplify it says xposed isn't running, even if xposed says it's active
Sent from my HTC One M9 using Tapatalk
That is literally what you are meant to do, some modules are functional, some aren't. For me the screen off animation didn't work and so strange as it might sound, I would miss it and as such I have retained 5.0.2, I really do not see any difference between the two, all modules work, nothing appears broken to me and the battery life is as good as I need it to be. To answer your question in short I get the same message with screen off animation, as if it's not installed. It's because it's not been updated. Either wait for it to be updated or downgrade like me
Updated op. Screen off animation working properly on 5.1, been using it for a while now.
neverborn said:
Stock, rooted. Ive never had this much trouble just to get xposed.
Basically i:
1. Unlocked bl
2. Twrp
3. Backup of system image
4. Root
5. Xposed zip for arm64
6. Installed xposed apk
7. When trying to launch amplify it says xposed isn't running, even if xposed says it's active
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Usually says that when either xposed isn't installed properly or the module hasn't been updated and you'll have to wait.
Follow the tutorial to install xposed, you can't miss.
dladz said:
Usually says that when either xposed isn't installed properly or the module hasn't been updated and you'll have to wait.
Follow the tutorial to install xposed, you can't miss.
Click to expand...
Click to collapse
And replace soft reboot with a regular reboot. Also had some bad experiences with particular modules. After a regular reboot they all worked fine
oemfoefoee said:
And replace soft reboot with a regular reboot. Also had some bad experiences with particular modules. After a regular reboot they all worked fine
Click to expand...
Click to collapse
Actually in that part of the tutorial, you only need a soft reboot. Regular if you need it but not necessary.
help!
Is the S-off bootloop bug fixed? M9+/S-off/5.0.1 I really want to install Xposed. Please help! :crying:
Vinncent said:
Is the S-off bootloop bug fixed? M9+/S-off/5.0.1 I really want to install Xposed. Please help! :crying:
Click to expand...
Click to collapse
Boot loops are a risk I've written how I was able to get xposed without boot loops but I've also warned that it can happen. If you follow my instructions you stand a food good chance
working great on the latest ViperOne rom... thanks man...
dladz said:
Boot loops are a risk Ive written how I was able to get xposed without boot loops but Ive also warned that it can happen. If you follow my instructions you stand a food chance
Click to expand...
Click to collapse
Food chances are the best!
Works on my m9:highfive:
Krsmqn said:
Food chances are the best!
Works on my m9:highfive:
Click to expand...
Click to collapse
Haha Bloody Auto correct.. Guess my phone is telling me to be a fatty ..
apaquette420 said:
working great on the latest ViperOne rom... thanks man...
Click to expand...
Click to collapse
No worries

[MAGISK] OnePlus 5 Google Dialer + Contacts - Fully working!

All the methods of installing the Google Dialer on the OP5 kinda worked but would not allow the user to answer/decline calls from the notification popup. Well, did some digging on this and found a solution. This is a Magisk Module, so for those that use Magisk, simple flash and restart. Be sure you select the new Phone app as default for calls. Also, need to go in and manually set the permissions for the app.
This can be done by going to "app info" for default OnePlus phone app and disabling, then by going to Google Phone "app info" and clicking on Phone App, then on the "Configure apps screen, changing the default Phone App to the only option you should have (after disabling the default one) which is the Google "Phone". Then make sure your new Phone app has all it's permissions.
Enjoy!
Update: TWRP install method added for those not using Magisk. Just flash the zip and good to go.
Magisk Module v2.1a: Update Sep 5, 2017
https://www.androidfilehost.com/?fid=817550096634797320
TWRP Install:
https://www.androidfilehost.com/?fid=889764386195918352
Thanks intall working
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Sent from my OnePlus5 using XDA Labs
Great Tweak mate! Thank you so much
I'm expecting an important call today, but will test thoroughly later.
ilia1985 said:
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
badcrow35 said:
Thanks intall working
Click to expand...
Click to collapse
I don't own a OnePlus 5, I have a 3 but I saw a Turkish text and decided to write. How did you get access to OnePlus 5? Have you imported it from abroad or are you living in abroad?
Brought with my friend from abroad UK
ilia1985 said:
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Click to expand...
Click to collapse
dustintinsley said:
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
Click to expand...
Click to collapse
Can anyone confirm if the zip works?
dustintinsley said:
All the methods of installing the Google Dialer on the OP5 kinda worked but would not allow the user to answer/decline calls from the notification popup. Well, did some digging on this and found a solution. This is a Magisk Module, so for those that use Magisk, simple flash and restart. Be sure you select the new Phone app as default for calls. Also, need to go in and manually set the permissions for the app.
This can be done by going to "app info" for default OnePlus phone app and disabling, then by going to Google Phone "app info" and clicking on Phone App, then on the "Configure apps screen, changing the default Phone App to the only option you should have (after disabling the default one) which is the Google "Phone". Then make sure your new Phone app has all it's permissions.
Enjoy!
https://www.androidfilehost.com/?fid=889764386195917884
Click to expand...
Click to collapse
Work like a charm wish everything went this easy
Awesome, works just fine. This has been driving me bonkers lol.
Working great! I use xxx rom with latest Magisk. Thx! :highfive:
dreams.sri said:
Can anyone confirm if the zip works?
Click to expand...
Click to collapse
I have not tested it as I use Magisk, but it should work. Worse case is that it will still not answer from notification. Should not cause any boot loop or anything like that. Have you tried the zip? There should be no issues with it, if you have issues please let me know so I can fix it...
Binary Assault said:
Awesome, works just fine. This has been driving me bonkers lol.
Click to expand...
Click to collapse
Same here man. It was driving me nuts. I'm kinda OCD so I had to figure it out. Glad others find it useful...
But OnePlus Dialer Is Better Than Google One ?
Krsambhav16 said:
But OnePlus Dialer Is Better Than Google One ?
Click to expand...
Click to collapse
Not sure that I agree, but to each his own...
Can someone explain how to flash the magisk module? Flash it via TWRP or via Magisk?
Donald Nice said:
Can someone explain how to flash the magisk module? Flash it via TWRP or via Magisk?
Click to expand...
Click to collapse
You can do it either way. I prefer doing it via Magisk, but either should work.
does it vibrate when the call connects?
dustintinsley said:
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
Click to expand...
Click to collapse
Thanks for taking time to make it. Just tried and TWRP throws error 6.

Questions about running stock rooted ROM / XPosed (Gravity Box) / Substratum

Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Ghisy said:
Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Click to expand...
Click to collapse
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
rickysidhu_ said:
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Click to expand...
Click to collapse
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Ghisy said:
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Click to expand...
Click to collapse
Unlocker is to support dev as well as it unlocks the ultimate notification controls which has a trial period
Ota are fine but we all prefer to flash the whole image because it is recommended and hardly comes up with errors
If you install magisk module for xposed then you would only need to re install magisk zip and your previous modules would be still installed
For substratum you need to disable overlays before updating and just re enable them after updating to latest update
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
Click to expand...
Click to collapse
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Ghisy said:
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Click to expand...
Click to collapse
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
Click to expand...
Click to collapse
Ditto.
rickysidhu_ said:
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
Click to expand...
Click to collapse
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Ghisy said:
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Click to expand...
Click to collapse
Glad you got it working.
I downloaded the Xposed APK in the Magisk thread and installed Xposed within the app; after reboot everything seems to work normally for me.
The way you did it is also fine though:good:

[ROM][FIREOS 5.6.4.0 FOR HD10][Magisk][Gapps][busybox]

Here we are folks latest fireos release for the HD10(Suez) (actual 5.6.4.0) MAY 2019
Deodexed
Removed Kindle special offers aka lock screen ad's
pre-rooted with Magisk 19.1
Disabled OTA
Busybox
changelog V2 5/16/19
fix some wonky dhcp related permissions because amazon doesn't know what the fk they are doing
recommend you guys update asap to avoid wonky wifi
/System increased to 1.6GB to accommodate Gapps
there should be no issue upgrading from previous versions but I have not extensively tested that so if you encounter issues do a factory reset
*Gapps Please do not use hacky tools like fire toolbox. Instead, Install Gapps via TWRP as it is the 'right' way to install Gapps (something reinvent wheel.... )
https://opengapps.org/ 5.1 ARM nano package has been tested and confirmed working **
*it may crash once or twice during account setup but it works just fine once you get logged in
please note that play store version of Amazon apps are NOT Compatible with fireOS exercise caution when allowing apps to update it is highly
recommended you turn auto update OFF, or flash a market detatch script failure todo so will result in you losing amazon stock apps!
if you encounter issues with flashing/updating magisk or do not want root flash the stockboot zip there seems to be a wee bit of jank when flashing over an unclean boot image (an example is if you are updating and already have magisk installed)
the same warning as other stock roms apply do not update magisk from magisk manager use TWRP, flashing modules should be fine
DL:
Rom V2: https://www.androidfilehost.com/?fid=1395089523397966787
Magisk https://github.com/topjohnwu/Magisk/releases/download/v19.1/Magisk-v19.1.zip
Gapps: https://androidfilehost.com/?fid=1395089523397966611
stock boot https://www.androidfilehost.com/?fid=1395089523397965517
Tested this and It's working !
Just a correction your GAPPS link is to an ARM64 package that is not compatible with this tablet. Thankfully the ARM ones work just fine. Thanks for making this great ROM! Running great on my Fire 10 right now!
AngryManMLS said:
Just a correction your GAPPS link is to an ARM64 package that is not compatible with this tablet. Thankfully the ARM ones work just fine. Thanks for making this great ROM! Running great on my Fire 10 right now!
Click to expand...
Click to collapse
this is what I get for uploading at 3am
should be fixed momentarily
edit: link corrected
Just curious, what's the benefit of flashing GAPPS vs other install methods?
Also what's the benefit of having them as system apps? Thanks.
Kctucka said:
Just curious, what's the benefit of flashing GAPPS vs other install methods?
Also what's the benefit of having them as system apps? Thanks.
Click to expand...
Click to collapse
because play services are meant to be installed as a /system app
it will also survive a factory reset
sideloading the apk's can also lead to weird bugs
WiFi? How did you avoid dhcp errors?
DragonFire1024 said:
WiFi? How did you avoid dhcp errors?
Click to expand...
Click to collapse
that was _fixed_ in like 5.6.3 ?
edit apparently it was not fixed
but even this still doesn't like my deco mesh wifi I need to static it to get it through setup and it still randomly disconnects sigh ...
I guess it better look into seeing why its doing that
edit fixed rom updated
Legitsu said:
that was _fixed_ in like 5.6.3 ?
but even this still doesn't like my deco mesh wifi I need to static it to get it through setup
you can also just chmod 755 the configs
i may experiment with replacing the dhcp binaries with ones built from source at a later date
Click to expand...
Click to collapse
I'll have to make a test build and seeif that's what the case was. If so I could kick myself repeatedly. I have a 64 bit build built for this thing, built from AOSP. I have yet to test it. But if you need any of the bins for it, I have them.
deleted see next post for fix to all wifi problems
attached is example updater script
ok so mystery solved once again permission errors
****ing A amazon get it right
@DragonFire1024
boot to recovery
mount system
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
enjoy no more wifi problems
probly could update the updater-script to set_perm and fix it
logcat and grep are your friends use them
you see things *****ing about permission denied its a dead give away
Legitsu said:
ok so mystery solved once again permission errors
****ing A amazon get it right
@DragonFire1024
boot to recovery
mount system
chmod 555 /system/etc/dhcpcd-run-hooks
enjoy no more wifi problems
probly could update the updater-script to set_perm and fix it
logcat and grep are your friends use them
you see things *****ing about permission denied its a dead give away
Click to expand...
Click to collapse
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
DragonFire1024 said:
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
Click to expand...
Click to collapse
fixxed a typeo lol woops
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
and
chmod 555 /system/etc/wifi_log_levels.sh
I am updating the installer script todo this for you reuploading rom gimme a few
Legitsu said:
fixxed a typeo lol woops
chmod 555 /system/etc/dhcpcd/dhcpcd-run-hooks
I am updating the installer script todo this for you reuploading rom gimme a few
Click to expand...
Click to collapse
I think it's time we checked the permissions in other files this might be worth a shot at fixing the rest of the problems these things have with Wi-Fi.
Edit: has anyone uninstalled the wifi locker app yet? The only thing it has permissions to do is upload and store credentials or something to that nature but I don't think it has anything to do with storing Android credentials.
DragonFire1024 said:
I don't have a firmware available to test this and I'm at work for several more hours. So if someone can test this out that is or was on my firmware that would be awesome.
Click to expand...
Click to collapse
you can confirm its the issue with
logcat | grep dhcp
and
locat | grep wifi
look for the permission errors
some of these daemons are executed under a different group which leads to issues
this occurs even on a virgin untouched tablet
I should have posted this a long time ago I have known about it for a year just have not had time lol
Legitsu said:
you can confirm its the issue with
logcat | grep dhcp
and
locat | grep wifi
look for the permission errors
Click to expand...
Click to collapse
I don't doubt you for a second because I figured the Wi-Fi log levels script was causing the issues and though it didn't fix it it seems to have stopped a lot of the reconnect disconnect issues the things seem to have with jumping back and forth to different Wi-Fi networks so I deleted it, at least on other builds but none that I put out to you guys. So it does make a lot of sense however I still kick myself in the ass for not checking permissions first.
DragonFire1024 said:
I don't doubt you for a second because I figured the Wi-Fi log levels script was causing the issues and though it didn't fix it it seems to have stopped a lot of the reconnect disconnect issues the things seem to have with jumping back and forth to different Wi-Fi networks so I deleted it, at least on other builds but none that I put out to you guys. So it does make a lot of sense however I still kick myself in the ass for not checking permissions first.
Click to expand...
Click to collapse
the major problem was the dhcp hooks without that dhcp does not work properly
it also for whatever reason needs to be 555 775/660 will not do it don't ask me why I tried it both ways it only works 0 2000 0555
I blame amazon
rom updated op updated
amazon made aware of the problem hopefully will get fixed so you don't need to root your device to have wifi that works
Legitsu said:
the major problem was the dhcp hooks without that dhcp does not work properly
it also for whatever reason needs to be 555 775/660 will not do it don't ask me why I tried it both ways it only works 0 2000 0555
I blame amazon
Click to expand...
Click to collapse
It would make sense if they wanted to throw off whoever could successfully pull off deodexing. It wasn't easy pre twrp. I had to do it piece by piece, and only some of the manually replaced ones worked. But you are right I've never seen those files with 555 before.
Sent from my Droid Razr M using XDA Labs
DragonFire1024 said:
It would make sense if they wanted to throw off whoever could successfully pull off deodexing.
Click to expand...
Click to collapse
Lol. Do you seriously think some engineer at Amazon (or whomever they contract with) is charged with scheming up bizarre ways to throw off the miniscule community of deodexers? Too much daytime TV.

Categories

Resources