Database Info

[PORT] LG QuickRemote for AOSP MM

Hello, i bring to you the QuickRemote app for your AOSP Marshmallow rom, CM13 or any rom based on CM13 (Resurrection Remix, Bliss, AICP), you may ask, "Why would i want QuickRemote on my AOSP rom if MM has native IR support and Peel or Anymote works without all this mambo jambo?
Well, even though what i just said is true, no remote controller app has the learning method enabled, even on a stock rom, only QuickRemote can enable the IR receiver to learn a controller that does not appear on the device/manufacturers list.
So, that's the reason we want QuickRemote to work on our AOSP rom.
So, before anything, i would like to thank @hikarisei23 because in a comment of his post HERE i found the files for QuickRemote to work on MM wich leads to the second person i want to thank wich is @syndre who on said comment, posted the files that worked on MM, also @KronicSkillz who helped a lot to troubleshoot and also confirmed that the method i'm posting here works.
Well, this is it, after personally testing with: Resurrection Remix, AICP and Bliss, all of them MM amd CM13 based, all of them with the stock kernel and Lambda Kernel i'm confident enough to post it here, days of testing and troubleshooting and 3 different roms later.
So first, the mandatory disclaimer, im not responsible for any problem that may result from using my method and the files i'm providing you, either with your phone or your self-esteem, it's your responsibility to read, re-read and only do what you are comfortable with.
What you will need:​
1. - The phone, this only has been tested with Lg G2 and Lg G3, this may or may not work on another LG phone with IR, you can try, but at your own risk.
2. - The Rom, this only have been tested with AOSP roms either CM13 or CM13 based roms, again, you can try in another rom but at your own risk.
3. - Obviously a Custom Recovery (twrp, cwm, philz)
4. - The three zips im leaving at the end of the post, QRemote_AOSP_MM.zip Fix_Part1.zip and Fix_Part2.zip.
5. - Maybe necessary or not, depending on your rom, Universal init.d from Playstore HERE and Selinux Mode Changer from HERE.
6. - Root Access.
Ok, once you checked and have everything needed, we have to make a little prep on your Rom before starting to flash the zips.
Rom Preparation 100% Needed
You need to set Selinux to permissive, here is where you may or may not need Selinux Mode Changer, First go into "About Device" on your phone settings and in the bottom you will find an indicator for Selinux state, if its "Permissive" you are good to go, some Roms and Kernels have this set to Permissive by default, if it's Enforcing, search in your Rom or Kernel settings, some of them have an option to set it to Permissive, if your rom does not have any option to change it, you will need Selinux Mode Changer, you install it and set Selinux to permissive, after reboot you can check in About Device again to see if it succeded, if it does not work, try again and check the original post, most of the answers are there, i cant give support for this app, also, this app needs root rights, and preferably two reboots after setting Selinux to Permissive.
Next you need to have init.d support, again, some roms have it, but at least for the test that me and the other users did, even though you are pretty sure init.d is enabled it's better to just install Universal init.d from the Play Store and enable init.d manually after doing so, reboot the system at least two times and grant Root access.
Installation!
Now we are ready to start flashing, reboot into recovery and RECOMMENDED, do a Nandroid Backup just in case, but at the moment no boot loops or any other problems had raised from flashing this, but again, just in case. After that, flash the first file: QRemote_AOSP_MM.zip, reboot your system and let it settle for a bit, 1 minute at least.
Now is the part where almost everyone has problems, you have to check in your Sdcard root for a log file named Qremote.log, if the file is there, it means init.d is enabled and in the file it will say if Selinux is Ok, if you don't have the file, check back the first two prep steps and try again.
Now if everything is going ok, is time for the second file, Fix_Part1.zip, reboot and let the system settle again, you may have some force close errors from QuickRemote or QuicksetSDK, its ok, you can try and check if QuickRemote is working, in allmost every case it will not work just yet, but you may have some luck.
Now, is the time to flash the third file, Fix_Part2.zip, again, reboot and let the system settle, now, you should have a working QuickRemote app on you AOSP MM Rom.
This are the steps, if you need more information about what all of this is doing and why you need Selinux and init.d, also why you need to flash 3 files, you can read the troubleshooting section where i explain what i understand about it.
TROUBLESHOOTING
Well, if you are here, it means that this didn't work as planned, so lets make this like a FAQ so you just search your problem and get the answer for it.
P.- I can't see QuickRemote on my app drawer. A: be sure that QuickRemote.apk is not showing as "com.lge...." and has the default green Android icon on your app drawer, sometimes and for reasons unknown to me, this happens for the first day or so, it will automatically change to QuickRemote and it will have the correct icon at least 5 hours after you installed it, it can take more time. A2: Maybe the flashing proccess was not successful, re-flash the file, it will automatically delete previously flashed files and install a new copy of them.
P. - I get force close messages for QuickRemote or QuicksetSDK after completing the proccess. A: try to run QuickRemote after the system settled, most of the times is 1 minute, in some roms and for reasons unknown to me, this messages will appear at boot but after the system settled, you will be able to run QuickRemote without any problem.
P. - QuickRemote opens up but no manufacturers are showing and it also gets really slow. A: this problem shows when either QuicksetSDK is not correctly installed or Selinux is not set to permissive, the solution for the first problem is in my 2 part fix, the version of Selinux included in the first zip, works great with MM but for some reason it will not work out of the box, i dont know if it's missing some files but it may or may not even show under system apps list on your settings menu, what my 2 part fix does is that, deletes the version of QuicksetSDK that the first flash installs and installs a temporary copy of QuicksetSDK wich i believe, writes information needed for QuicksetSDK to work properly, but this newer temporary QuicksetSDK apk, will allmost never work on MM, you can try but allmost every time it will not work, it will constantly force close, so the second fix zip, will delete this temporary QuicksetSDK and the folder it creates in your Sdcard root and install the previous version of QuicksetSDK again, and now, if everything went well, it will work as it's supposed to, i really dont know why exactly, but it works.
A2: the first thing you will notice when you switch to MM is that allmost every app will ask for permission to your Sdcard or camera or microphone wich in LP was not doing, since 4.3 Google is taking extra steps to ensure that you and your information are better protected one of this steps is Selinux (Security Enhanced Linux) wich, for putting it in simple terms, is like a sandbox for your system, only some trust-signed apps can get out of that sandbox and copy files etc... Into your system, those not-so privileged apps cant output anything outside the sanbox and thats why you need to disable or "set to permissive" Selinux, so QuicksetSDK can make the changes necessary for QuickRemote to do its work, it's true that now your system is in a degree "more vulnerable" but if you are a user of this forum, the odds to install something that will damage your system or jeopardize your information are minimal, you need to be really silly to fall for those "your system has problems" or "your battery is gonna explode if you don't install this app" ads that appear on your phone on the daily basis, so, dont worry, but at the same time, just be carefull and have some common sense, if there is a way for this to work with Selinux set to Enforcing, i will update it in the same second.
P. - QuickRemote force closes whenever i try to open it. A: this is caused by either a bad zip flash, or problems with Selinux or init.d, follow the previous answer and the first installation steps again.
P. - I can see QuickRemote and QuicksetSDK on my apps list, no force closes but still no manufacturers. A: Be sure init.d is enabled, i had problems with Roms that had "native init.d support" and emulated init.d will not work, the only way i got no problems with this was with Universal init.d, install that even though you are "pretty sure" your rom supports init.d, the 10QuickRemote.sh script on your init.d tries to get your country to see if you will use the app in, either Korean or any other supported language, it will also give some permissions to a file and it will check if Selinux is Permissive and finally, it will log this to a file called Qremote.log on the root of your Sd, if you have problems and you cant see the file, the problem is 99% most of the time, init.d.
P.- I don't want to flash three files, isn't there a simpler way? A: Unfortunately no, at this moment and after A LOT of testing etc... This is the only effective way i found.
P. - I'm afraid to set Selinux to permissive and leave the door open for all kind of bad ju ju and stuff to invade my sacred Android system, what can i do? A: Skip this hole thing, at the moment, the only way to make this work on AOSP MM is by doing the previous, just be careful, get some common sense and everything will be just fine.
Well, thats all i can think of right now, if you have suggestions, problems or a better way to make this work, please tell me in the comments or PM me, i'm glad to help as far as i can, i hope this helps, i leave you with the needed files and proof that it works.
QRemote_AOSP_MM.zip - MEGA - DRIVE

nice you started a new thread!
Ive been messing around with this a lot the last few days and I have been seeing the same fix you were talking about by swapping the quickset apks back and forth. Ive put together a zip for flashing that I think would make things as easy as possible for people to get the list to show up.
The script in this one sets the correct permissions for everything on flash. It will instal;l the L version of Quickset, which doesnt show the manufactures list. The M quickset apk also gets flashed but i just put it in /system, so its there and can be moved easily. When you boot the first time after flashing, the the ROM uses the L version. All you should have to do then is use a file manager app to move the QuicksetSDK.apk from /system to /system/app/QuicksertAPK/ replacing the one thats there already. Set perms to 644 if necessary. Now wipe tjhe app data for quickset app, forcing the new one to restart, you dont even have to reboot.
Last thing is you have to delete the Quickset Settings folder made by the lollipop quickset. The Marshmallow version will make a working folder of its own the first time you start Quick Remote.
I like your idea to make fixes in separate flashes, that is probably easier
link to my 01262016.AOSP-6.x.x-M_LGQuickRemote_v4.50.19.zip on MEGA

it's working great!
tnx!

i just ran a nightly update on mokee6 which is cm13 similar and i had to reflash the fixes to get it working again and strange thing is i noticed lib folder is gone from quickset sdk folder but it's working
another thing i noticed is quickset sdk is not in my apps list so don't use that as a way to test if it's working either see if manufactures show up after waiting a bit or try the learning feature to test app functionality
im using d852 with stock mokee6 kernel btw of anyone's wondering and yes i have all apps selected

The mult-zip installation also worked out here on BrokenOS. Remote is working fine.
Originally I used "init.d scripts support" app to handle the init.d file. Worked just fine, BTW. Reason for that is I wasn't sure what would happen if I used Universal Init.d with Broken as it has a directory full of tweaks.
On later examination I see that each script needs to be enabled before it will run (via Settings. True/false values are then looked up in a cfg file).
So I reckon I can safely use Universal Init.d.
LG G3 D851, BrokenOS MM ROM, Tapatalk 4.9.5

can i delete universal init.d after enabling it?

@syndre well yes, i think that flashing zip it's pretty straight forward, your new method is simpler but i think that just flashing and not having to deal with system folders and permissions is better for the less tech savvy, but a little more hideous because of the various reboots

smolchy said:
it's working great!
tnx!
Click to expand...
Click to collapse
You're welcome

@marcdw yes, the thing with Universal init.d is that it really enables init.d at boot, Resurrection Remix and AICP also have their individual init.d scripts and they run, i don't know why the QuickRemote script does not run, and Universal init.d does not mess with the existing scripts, so it's not harmful for the system and runs the script at boot and thats what we want

@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback

Roi007leaf said:
can i delete universal init.d after enabling it?
Click to expand...
Click to collapse
I think you can i but i have not tested that, if you do, tell me what that did to update the post, i keep Universal init.d for other scripts that i have installed so i need it, if you only use it for QuickRemote i dont think you'll have a problem

ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?

Roi007leaf said:
ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?
Click to expand...
Click to collapse
What variant/rom you have?

Jc_master said:
What variant/rom you have?
Click to expand...
Click to collapse
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1

Roi007leaf said:
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1
Click to expand...
Click to collapse
Try force closing QuicksetSDK and delete its data, re-flash the fix part 2 and see in that helps, also i think that you need Universal init.d again, the Qremote.log updates at every boot and it wont update if Universal init.d is not installed

Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/

hikarisei23 said:
Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/
Click to expand...
Click to collapse
I hop they do, and thank you for your work also

No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?

Roi007leaf said:
No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?
Click to expand...
Click to collapse
Did you flash both fix zips? The need for those 2 fix zips is because the QuicksetSDK that comes in the Qremote_AOSP_MM.zip works with Marshmallow but by itself it will not create some required files in the system and it will most likely not show in the apps list, the QuicksetSDK that comes in fix part1 most of the times wont work on Marshmallow but it will create some necessary files on the system it will show in the apps list but it force closes, and the QuicksetSDK in the fix part 2 is the same as in Qremote_AOSP_MM.zip but this time it has everything needed to work properly and it now should show in apps list allmost every time, so you need to follow the steps again closely and i recommend that before you flash the fix part 2, you go into your apps list and force close QuicksetSDK and delete its data, also report if you get Qremote.log on the root of your Sd and what this shows if its there

Jc_master said:
@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback
Click to expand...
Click to collapse
ya i was using quickset sdk check (apps list) to see if it was working too until i realized it's working without showing up this time

[ROM] iPioneer Slim 10c v0.1 for LGV521 - Rooted, busybox, init.d, debloated, etc...

ROM Ipioneer Slim 10c v0.1
A light, clean & faster rom!!!
Disclaimer:
/***
* Your warranty is now void (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
iPioneer Slim 10c v0.1 is a light, clean and fast custom rom designed for the Lg G Pad X 8.0 (T-Mobile variant only) and it's aim is to become a replacement for the default system of this device.
iPioneer Slim 10c v0.1 it is light because it only takes 519.8Mb of disk space which is a big difference when you compare the 1.2Gb of a stock rom, it is clean because it only contains the essential apps to make it work properly and it is faster because the whole system have been 100% optimized.
iPioneer it have been designed with the User Freedom in mind, it only provides you with the basic OS so you can do what you need to do on top of that.
Features:
Based on stock (10c)
Rooted
Busyboxed
Init.d Support
Extremely debloated (very serious)
Deodexed
Zipaligned
Nova as default launcher
Installation instructions:
Download the rom to your desire location (link to download to the end of this post).
Boot into Twrp recovery and do a standard wipe (factory reset).
Install the downloaded rom .zip.
Reboot the device.
Be patient, is going to take more time than a regular stock rom to boot into the system, at first is going to be stuck at T-Mobile logo but after few seconds is going to enter into App Optimization mode and after that you will be able to setup your system.
Enjoy it.
First things to do after you install this rom:
Add your google account (if you didn't complete that step at the first setup).
Download your favorite app manager (Rom Toolbox, Titanium, etc.).
Freeze the application called App Updates in order to stop the system update beacon for OTA. I removed 3 core apps in order to stop OTAs but it seems to be very integrated with the system, there is no way I can remove it from the rom without breaking the system. This is the most practical way to my knowledge right now.
Optionals things to do after you install this rom:
You can uninstall Nova Launcher if you want as is not part of the system apps, but before you need to install your favorite launcher. If you don't install another launcher and remove Nova you will have a broken system and most likely you'll have to re-flash the rom.
On purpose bugs and missing options:
On purpose bugs are bugs that comes when you remove a functionality from the system but it can not be removed from a third party component, example: LG VPN app it has been removed but the options remains in the Settings of the device and when you tap that option you will provoke a crash event, the way to resolve this is to decode the third party component (very difficult) or reinstall the missing part (in this case the LG VPN app).
iPioneer Slim 0.1 it comes without some apps that can not be removed from the system setting options, this is like that because I believe that these apps are not necessary for all people, if someone need them they can be downloaded/replaced from the Play Store or I will provide a flashable file with these apps so you can install them.
On Purpose bugs (located at settings):
From the Share & Connect menu:
File Sharing that contains BLE and Android Beam doesn't work, package SmartShare it has been removed.
Media Server (DLNA) doesn't work, package SmartShare that also contains SmartShare.MediaServer it has been removed.
Lg Airdrive doesn't work, package LGAirDrive & LGAirDriveSettings were removed.
From More>VPN menu:
LG VPN doesn't work, package VpnClient_LG it has been removed. Basic VPN it works.
From Display menu:
Home screen doesn't work, packages LGHome, HomeSelector, LGHome_Theme_Optimus, com.lge.launcher3, com.lge.launcher2.theme.optimus were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.​
Missing options (located at settings):
Smart Cleaning not present, package LGSpringCleaning it has been removed.
Cloud (cloud integration in settings) not present, package CloudHub (maybe dependant on SmartShare package) it has been removed, please also note that this cloud integration it was integrated on the stock File Manager, so... if you want a full integration of the Cloud service on settings maybe you will have to install the stock File Manager provided by LGFileManager package.
From Backup & reset menu:
LG Backup is not present, packages LGBackupLauncher and LGBackup were removed.
From About tablet menu:
Update Center and its content (App updates & System updates) is not present, packages com.lge.appbox.client (app updates), com.lge.updatecenter & LGUpdateCenter (main menu for updates) were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.​Flashable zip with system apps:
Coming soon when I have a free time.
What to do if you get the OTA notification:
Freeze the app called App Updates with your favorite app manager.
With your favorite file manager go to /cache and delete the update.zip (the downloaded ota).
Tap on Restart & Install button on OTA pop-up, the pop-up it will start counting to 0 in order to restart but your device won't restart because there are 3 core apps removed from this rom plus 1 app that you just disabled (all these 4 app controls the OTA), the notification is just gonna disappear, push recent button and clear the ota pop-up window.
Bugs Report:
If you find a bug in this rom just notify me about that in this thread, please, just use the title as "Bug Report" so I can pay close attention to that, my time is very limited. Thank you.
Feature Request:
If you want a feature to be added into future revisions of this rom just notify me about that in this thread, please, just use the title as "Feature Request" so I can pay close attention to that, my time is very limited. Thank you.
More info:
-------------------------------------
Device: Lg G Pad X 8.0
Model: LGV521
Code Name: b3
Carrier: T-Mobile
Android version: 6.0.1
Security patch level: 2016-07-01
Software version: V52110c
Link: https://www.androidfilehost.com/?fid=385035244224403624

Screenshots:
Default View: (sorry guys, I was not able fix Nova in order to show an organized and clean layout by default).
Default App Drawer: remember this is an extremely debloated rom, only the most basic core apps remains.
Settings view, yes some options are not present, read above about this.
Software info.

Reserved 2...

For some reason this post doesn't show up on ET page: lg-g-padx
Too bad, a lot of people won't be able to see this rom, but I can do nothing.
If someone knows an admin who can fix this issue please make mention of this post to him. I would do it but I don't have the time to.
Thank you.

Some screenshots added on post #2...

How fast does it run compared to the stock rom?

Munns86 said:
How fast does it run compared to the stock rom?
Click to expand...
Click to collapse
How fast it can go is a subjective matter:
It will depend on hardware lifetime span (how you use it and how other people use this tablet).
It will depend how much apps and content you put in it (the more things you download the more slow android is gonna be, this is kind a Swap area).
I did not do a benchmark, when I declared that is faster than a stock rom is because that speed response enhacement it comes based on the Deodex and Zipalign process. It can be or maybe not noticeable to your eyes but based on deodex and zipalign process is for sure that is faster than an odex and not-zipaligned rom.
The best answer is that you need to try it on your own and see the difference.
Sent from my LG-H918 using Tapatalk

Poll added at the beginning (not visible in tapatalk or xda app).
Please only select the apps that you really need or you really think that should comes with the next revision of iPioneer Slim rom.
This will help me to build a better version with features that users needs.

C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!

xtremelora said:
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
Click to expand...
Click to collapse
The reason is that the xda app can't see the vote going on.
Personally, I will be excited to see a cm/aosp custom build, which will sure draw much more attention.

googlephone said:
The reason is that the xda app can't see the vote going on.
Click to expand...
Click to collapse
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...

xtremelora said:
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
Click to expand...
Click to collapse
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.

googlephone said:
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
Click to expand...
Click to collapse
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.

xtremelora said:
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
Click to expand...
Click to collapse
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.

Munns86 said:
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Click to expand...
Click to collapse
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.

xtremelora said:
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
Click to expand...
Click to collapse
There is already a TWRP recovery for v521. Why you need to compile cm recovery?

googlephone said:
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
Click to expand...
Click to collapse
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk

xtremelora said:
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.

shabbypenguin said:
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
Click to expand...
Click to collapse
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.

xtremelora said:
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
Click to expand...
Click to collapse
i built it from scratch, id be careful looking too much at the v500, it's a snapdragon 600 SOC which is very old and is a quad core. the 615 in the g pad x is octacore and much newer. even the ramdisk is going to have big differences in how its handled.

SRGX2 Rom for the Life One X2 Mini

SRGX2 for Life One X2 Mini​This Rom Is a Stripped down modified version of the Life One X2 Mini stock Rom.
NOTE: After installation give Launcer 3 notification permission and update Google Play Services (click on the notification).
(Please remember I do this in my free time and with my own money. If you like it please hit the thanks button)
Mods:
Malware removed
Build.prop Tweaks
Oreo Launcher
Camera app replaced by OpenCamera
File manager replaced by MiXplorer
To do list:
Build wifi drivers into the Kernel
Strip down rc scripts
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Camera
Flash
Fingerprint
Not Working Yet:
(You tell me)
Downloads:
Current Build: https://www.androidfilehost.com/?fid=673956719939824825
Builds: https://www.androidfilehost.com/?w=files&flid=239712
Patches: https://www.androidfilehost.com/?w=files&flid=254440
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel: https://github.com/vampirefo/android_kernel_blu_kernel_x2 (Special thanks to @vampirefo for the kernel source)

Screenshots: comming soon

Changelog
Version: Testing
Build: 01072018211020
Initial release
Version: rc1
Build: 01142018205847
switched to stock theme
Version: 1.1.0
Build: 02182018215948
rebuild off of the 01/04/2018 update
Version: 1.1.1
Build: 02242018165134
fixed mobile data bug
Version: 1.1.2
Build: 03032018224915
changed DPI to 441
added stock calendar app
added stock calculator app
add stock clock app

Troubleshooting

reserved

Does quick charge work?

Been running for a couple of days now without issue.

cyrusharding said:
Does quick charge work?
Click to expand...
Click to collapse
Yes it works, I've beeen using 2 QC3 chargers with no problems at all.

Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!

enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.

cyrusharding said:
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
Click to expand...
Click to collapse
Interesting, didn't know that exists. I currently just download off of http://download.spotify.com/android/SpotifyAndroid.apk

enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy

srgrusso said:
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
Click to expand...
Click to collapse
This is awesome thanks so much!! I use Windows on a daily basis but I do have a pretty good knowledge about Linux and have set up a build environment in for Android. These links should help me understand what I am missing. I am also happy to continue testing and give you feedback on this ROM as it is currently my daily driver.

New Rom out. It has the stock theme, other than that it is the same.. I haven't decided if I'm going to build two Roms or have the theme be a patch. Maintaining all the different variants of the Rom are getting to be very time and space consuming.
https://www.androidfilehost.com/?fid=889964283620778170

Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?

Requia77 said:
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Click to expand...
Click to collapse
Is this without root? I don't know if my rom will fix that, I never used the Paypal app. Your welcome to try and let me know. Also there is LineageOS 13 for the mini which has been built from source.
https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814

New rom rebuilt from the 01/04/2018 update.
v 1.1.0

There is a problem with the latest version of SRGX2. Mobile data doesn't work. I work on it this weekend and keep everyone updated.

Here is the fixed rom.
https://www.androidfilehost.com/?fid=818070582850494825

Good news I was able to get Android File Host to make the Life One X2 an official device. I have made a request for the Mini too. For now all the files will be under the Life One X2 device.
Updated rom: https://www.androidfilehost.com/?fid=673956719939824825
It includes the stock Calendar, Clock and Calculator apps. I changed the DPI to 441. Let me know if anyone has any problems with the Playstore. I know that there has been some requests for the stock Camera and file Manager apps. It's hard to please everybody so I added a patch section which may please some.

Root on fire HD 10 - but no custom recovery or ROMs?

Can someone help me understand how we can have root methods for the HD 10, but no custom recovery or ROMs?
Any news or updates on the effort here? I'm willing to pay or donate to get it done!
I REALLY want to turn my tablet into an Android tablet... Not a fire tablet with an almost Android experience.

If we can get some one to create safestrap probably we can have a custom Rom !ade

There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.

DragonFire1024 said:
There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.
Click to expand...
Click to collapse
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!

Supersonic27543 said:
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!
Click to expand...
Click to collapse
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.

DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!

Supersonic27543 said:
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!
Click to expand...
Click to collapse
That's one of my projects

DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Could be that I don't know how to solve the problems I have, but for me not all the Google play applications I want (for my kid) work. Issues vary from validating my authorized purchase to core functionality of applications not working. Some of the applications refer to Android os content and services that either aren't in fire os, are named differently, or have different functionality.
Not to mention that I dislike my son's user experience... He's only 3, quite smart but I've not been able to strike a good balance of protecting him and allowing him to actually use his tablet without learning wierd tricks to access Google play apps.
I'm ok if I have to stay on Fire Os if I can have complete control over profiles, launchers and have a genuine experience using my Google Play applications. Some of the FreeTime stuff is ok... My son might like some of it. But more importantly I want him to have the far superior applications on Google Play which are not currently available on Fire.

I'm willing to contribute to get a custom rom on the fire 10.

I really want to compile one, my skills are getting blunt without some compiling, but it turns out that I only have a HD 8.

Can someone please educate me on getting the GPS to work with google maps, like my phone? My HD 10 7th gen is rooted w/supersu. I have xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.

kferling said:
Can someone please educate me on getting the GPS to work with google maps, naively like my phone? My HD 10 7th gen is rooted w/supersu. I have Xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.
Click to expand...
Click to collapse
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Click to expand...
Click to collapse
Thanks, although I did not get location prompts at the end. :/
Data was wiped for all 4, and uninstalled. rebooted and verified no data with ES.
Installed google apks in the exact order, waited 2 minutes, rebooted, then logged into playstore.
Went to home screen, saw apps flash after waiting. Went to location services (was off) turned on and no prompts
Turned off, waited 30 secs, turned back on, still no prompts.
Is this any different from your guide here?
Step 6. states "Once all the APKs are installed, open the Play Store and sign into your account and IMMEDIATELY go to settings and TURN OFF auto-updates. "
Perhaps that's what I need to do?

Just ordered an HD10, will this tutorial still work? https://forum.xda-developers.com/hd...7-root-box-t3726443/post75187398#post75187398
Will that debloat Fire OS also?

So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.

Have a new 2015 HD 10. Will definitely be following your progress

FuNKSioN said:
Have a new 2015 HD 10. Will definitely be following your progress
Click to expand...
Click to collapse
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.

TechNash said:
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.
Click to expand...
Click to collapse
Not sure about the encryption. It has to be a script problem, or the system partition won't accept zips and that's the barrier. However if I just flash the system directory instead, everything works fine. I can flash stuff into it just fine that way, but seems any time I go the way of the partition, I can't win. Flashing your own system image works too. However I haven't been able to get one to flash if I modify it. So I can decompile a system.img add to it, remove items and recompile it and it won't flash.
I am using flash fire to flash zips. We still have a locked bootloader so twrp isn't a likely option.
Sent from my Galaxy S4 using XDA Labs

DragonFire1024 said:
So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.
Click to expand...
Click to collapse
I mean, if PC performance is an issue I can give you access to a brand new xeon if it means there will be a custom ROM out.
Been thinking about buying the Fire HD 10 this black Friday and flash the Amazon garbage out, and was amazed to see none exist even though it has been a year since they figured out the rooting.
This will be an outstanding value if it was possible...

[Guide] Enable VoWiFi on custom ROMs

First attempt at making a guide for this, so please feel free to make suggestions on how to clean it up (I feel like it doesn't lend itself well to step-by-step but you're welcome to try).
Great news everyone! (well, all three of us with T-Mobile/MetroPCS in the USA...)
I got VoWiFi to work last night on a couple custom ROMs and successfully made wifi calls. It doesn't require many pieces, but it can be complicated (not just a step-by-step) to get the required pieces into the right places.
- You need a copy of /system/priv-app/CNEService/CNEService.apk from a stock OOS install (I did it with the one from 9.0.3).
To get that, you might be looking at booting into TWRP with the other slot active or temporarily using something like @mauronofrio's fastboot install ROM from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and just flashing the system image to one slot to grab the file before restoring back to the one you had. Anyway, use caution, be sure of which slot you're on and what you're flashing to, and copy the apk from /system/system/priv-app (the path when you're booted from TWRP instead of inside the active system slot). You'll probably have to use ADB commands to push/pull the file directly to/from a computer if you already have a custom rom installed on one slot with screen lock set up, since /data will likely be encrypted and unavailable when you're booted up in TWRP with the other stock slot active.
- You need to be able to install a rando apk as a privileged system app to get this apk back into /system/priv-app/ correctly on your custom ROM.
There are ways to do this manually that involve lots of permissions and editing XML files for privileged app permissions in a couple places, but realistically you're using a custom ROM so you probably have Magisk (otherwise what the hell are you doing with custom ROMs?) so you should just use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 and pick option 3 to install it. You'll need Magisk, a terminal emulator, and some ability to type a file path to use this module.
- You'll need to make sure that your /system/build.prop file contains the line "persist.vendor.cne.feature=1" (AEX doesn't at first, XenonHD does, not sure about others).
We've got the requisite stuff in /vendor already, this just enables the ability to use it. You'll need to have root access and a file manager/text editor (Amaze is FOSS and available through F-Droid, MixPlorer through XDA Labs is also nice, or use TWRP and a text editor that knows unix line endings on your computer to copy things back & forth via MTP and remember to set permissions after, I think it's chmod 644).
Reboot, unlock, and try to make a test call. Successfully got it to work on AEX & XenonHD last night, I suspect it works for Omni and others as well.
Try some more ROMs out and report back below if it works for you too!

Now if only you could fix the Android Auto bug.
I'm totally kidding. This is awesome. Thank you!

Tested Omni and it works too; just needed the APK added/systemized, already has the correct entry in build.prop.

hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??

Any chance someone could upload and share the CNEService.apk? Would make life a lot easier...

brmbjn said:
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Click to expand...
Click to collapse
If it's not working in OOS, I don't know what to tell you. Might just be that the connection isn't reliable enough for it to decide to enable... but I never used OB10; I switched back to stable 9.0.3 after OB9.

Great work!