Develop Bugs

[DEV][WIP][ROM] CM10.2 Development thread - CALLING ALL DEVELOPERS

THIS ISN'T A PUBLIC ROM RELEASE. THIS IS FOR DEVELOPMENT ONLY. THE ROM DOES NOT BOOT. FOR MORE INFO READ THE ENTIRE POST
I've been working on bringing our device onto par with a build of Android 4.3. I've set up a GitHub organization just for our device and it has everything we need to build for the device. Now I've been somewhat quiet with what I've been doing lately and I really don't have time to list everything I've done. @bradthomas127 and I have been communicating back and forth about building. I'd say he's done just about as much work as I've done trying to get 4.3 building. Well now, after some tips from him, I've got it building. It's using, in my opinion, the best up-to-date trees there are for our hardware. I am opening this project up to anyone that can help get it BOOTING. I don't need testers as right now I feel like I myself am the best tester for now because getting adb working on a device that sticks at a blank scree is a pain in the a**. So PLEASE I encourage anyone that knows how to maintain a GitHub and can compile and do a little coding to try to help us. The more people we can get, the faster and better we can get 4.3 actually running on our device.
Here is the GitHub:
https://github.com/Primo-Dev
If you feel you are capable of helping us dev this please PM me and I may add you to the GitHub so you can contribute.
Here is the latest build:
http://d-h.st/JSo
Logcat can be downloaded here:
http://d-h.st/SYz
Now, some basic rules for this forum:
1. DON'T ASK FOR ETA OR UPDATES - This kind of stuff is hard and takes time
2. Don't ask to test - I'll open this up for testing if we ever get it to boot
3. To all other people who aren't devs: Don't post here as this is for development only. I've made this thread in hopes of finding more devs to try to help with this, not open this up as a public ROM.
What needs attention:
I'll post bits and pieces of logcat here that shows things that need to be worked on
Code:
I/auditd ( 99): Starting up
E/auditd ( 99): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 99): Exiting
W/dalvikvm( 161): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument

I did not even notice this till you posted the logcat, libgenlock is not even building.
Code:
E/libEGL ( 1327): load_driver(/system/lib/egl/libEGL_adreno200.so): dlopen failed: could not load library "libgenlock.so" needed by "libEGL_adreno200.so"; caused by library "libgenlock.so" not found

Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.

robaho said:
Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.
Click to expand...
Click to collapse
That's what I've been thinking. All the devices that have been updated to cm10.2 have SELinux. Only problem is I'm not much of a kernel dev, but I can see what I can do. Also, if you take the main hardware libs from RhythmicRom and put them in cm10.2 you can get to the bootanimation.
Sent from my HTC One V using xda app-developers app

I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-

bradthomas127 said:
I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-
Click to expand...
Click to collapse
I'll logcat. I'll also post instructions on how I logcat on 4.2+.
Sent from my HTC One V using xda app-developers app

Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app

reV17 said:
Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks I'll do some research on github later. It has almost the same specs so it will be useful.
BTW: To anyone waiting for logcat instructions I'm trying to find a simplest way to do it with the little time I have between work and football, and school coming up.

Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip

bradthomas127 said:
Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip
Click to expand...
Click to collapse
Hey man I'll post how to when I get home
Sent from my C525c using Tapatalk 4

You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Sent from my One V using xda app-developers app

Lucky CDMA people with half working 4.3 o-o

robaho said:
You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Click to expand...
Click to collapse
I added ro.adb.secure=0 to the default.prop a couple days ago making the ramdisk/default.prop look like this now.
Code:
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
I've also tried moving adbkey.pub to data/misc/adb/pub_keys in TWRP but it gets erased as soon as i boot.

Is the USB driver working, that is, can you.see a USB device using your system devices view - varies by OS
Sent from my One V using xda app-developers app

This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.

awidawad said:
This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.
Click to expand...
Click to collapse
Not working for me, messed with it a couple times.

bradthomas127 said:
Not working for me, messed with it a couple times.
Click to expand...
Click to collapse
Strange... I've used that method multiple times in ubuntu.
Sent from my C525c using Tapatalk 4

awidawad said:
Strange... I've used that method multiple times in ubuntu.
Click to expand...
Click to collapse
Getting boot now, just boot loops every min.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:highfive:

bradthomas127 said:
Getting boot now, just boot loops every min.
:highfive:
Click to expand...
Click to collapse
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app

robaho said:
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Do you mean this one? https://github.com/bradthomas127/an...mmit/9af6efa20ece323155a853ff508563a87670e2f0
Rukin added it 4 months ago.
You did just open my eyes though, i thought i commited the SELinux stuff but just noticed i didn't on this kernel, maybe why i am having reboots and SD card is not mounting (reason for no screen shot). Thanks :good:

Does your phone have iZat?

EDIT: If you're missing iZat (read below to see if you already have it) I may have found a way to install it at http://forum.xda-developers.com/showpost.php?p=54558037&postcount=11, requires root though!
So I heard on reddit about this Qualcomm iZat, which is meant to improve the GPS location your phone gets, seems some people have it and some people don't.. I'm one of the people who don't
It sounds like all the chipsets have it though, just some phones don't have it enabled. My D855 doesn't have it, but on reddit it seems some people with the Sprint model have it and some others with the same model don't.
You can check if you have it by going to Settings -> Location -> Mode and underneath the standard options there'll be an Enhanced Location section where you can enable iZat.
If anyone here has it and wants to help us who don't out, uploading your /system/build.prop would be appreciated (it looks like theres some iZat settings in there)
If you could also check your apps to see if theres a Qualcomm iZat app installed that'd be swell

Nope, i don't have it i think?
Got a D855 (16GB) but no extra option whatsoever

Not seeing it in either of the locations you mentioned. (AT&T D850 here.)

harveydwijs2 said:
Nope, i don't have it i think?
Got a D855 (16GB) but no extra option whatsoever
Click to expand...
Click to collapse
geekaren said:
Not seeing it in either of the locations you mentioned. (AT&T D850 here.)
Click to expand...
Click to collapse
Well that's strange, I wonder why they're only enabling it on certain phones
For reference I found out about it from http://www.reddit.com/r/LGG3/comments/2c3k3s/lg_g3_and_geocaching_how_is_the_gps/cjbm9q0
Sounds like at least 3 people there have it, one on Sprint, one on Verizon and I don't know about the other one. Hopefully someone on XDA has it too and could maybe help us figure out how to get it ourselves.

AT&T G3 here, no iZat that I have found, even looking around rooted.

I'm on Sprint and I have it, I would upload the build.prop for you guys but I believe I need root and Sprint doesn't have root yet.
Sent from my LGLS990 using XDA Premium 4 mobile app

D855 european 3/32GB here, and I don't have it (I'm still on firmware 10a) but GPS works great, is very quick and accurate, no problem.

how to tell if you have one?
i see this line in my build.prop
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
Click to expand...
Click to collapse

deadh0b0 said:
I'm on Sprint and I have it, I would upload the build.prop for you guys but I believe I need root and Sprint doesn't have root yet.
Sent from my LGLS990 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ah well hopefully a root will show up soon, although maybe it's inside your KDZ too, could you maybe go to http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=*********** and change the stars to your IMEI, and copy the sw_url path here so we could take a look into it?
cnn888 said:
how to tell if you have one?
i see this line in my build.prop
Click to expand...
Click to collapse
I have the same lines in my build.prop, I think it means that iZat is disabled, but I'm not 100% sure, if you check the reddit post at http://www.reddit.com/r/LGG3/comments/2c3k3s/lg_g3_and_geocaching_how_is_the_gps/cjbm9q0 it says where you can find the setting for it.

Ah well hopefully a root will show up soon, although maybe it's inside your KDZ too, could you maybe go to http://csmg.lgmobile.com:9002/csmg/b...sn=*********** and change the stars to your IMEI, and copy the sw_url path here so we could take a look into it?
Click to expand...
Click to collapse
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=352596060206415 there it is, not sure if that is what you need, but that is my IMEI in the link.

deadh0b0 said:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=************** there it is, not sure if that is what you need, but that is my IMEI in the link.
Click to expand...
Click to collapse
Hmm well that's strange, normally it gives a link to the KDZ there, at least it does for me...
Luckily there's another way to check, I used your IMEI at http://csmg.lgmobile.com:9002/csmg/b2c/client/cs_auth_model_check.jsp?esn=************** and it gives a link to http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=PS47109201/LS990ZV4_04.51101.zip, that files not found but googling the name brings up some uploads from other people, time to start digging, thanks for your help :good:
Edit: Looks like we might have already cracked it
Doing searches inside the system.img in that zip for the string "IZat" I found an apk which wasn't on my phone, namely /system/app/xtra_t_app.apk, decompiling this apk showed it as being "com.qualcomm.location.XT". Seeing nothing else related to iZat that my phone didn't already have I took the plunge and installed it, and when I went to Location -> Mode I was greeted with a nice "com.qualcomm.location.XT has had to close" error. Darn! At least the enhanced location section was there, but it had no text under it, just an off/on button.
Determined, I looked into what was happening using adb logcat and it seemed like it was looking for an xt_native library which my phone was missing. I found that at /system/vendor/lib/libxt_native.so in the Sprint image and copied it to my phone, went back to settings and to my surprise the iZat option showed up!
Enabling it brought up some standard privacy policy b/s, and after saying OK to that it seems like it's enabled! Not sure how to check if its working exactly, but seeing as it looked like just this apk and lib file was missing I think it's working
A download for the apk and .so file is at https://mega.co.nz/#!DoQzgSjA!k8OeUr6W6pfhszd-kddVtzXNd7d1voWQsqN-A0D_0J8
To install it you'll need root (although there might be a way to package the .so inside the apk and skip needing it, this is my first time messing with Android since 2010 or so though so I'm a bit rusty with stuff like that)
First mount your system as r/w, running this works for me:
Code:
mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
Copy the libxt_native.so to your /system/vendor/lib/ folder
Run chmod 644 libxt_native.so to set the permissions properly
Install the apk
Restart, go to the location settings and enjoy
The permissions for the apk are pretty crazy and mention some in-call purchasing things, this isn't my doing though. In case you want to verify it you can download the LS990ZV4_04.51101.zip, extract the tot using LGBinExtractor (might need a small mod to support Sprint tots), open the system.img with Ext2explore and compare the hash of the apk I uploaded with the /app/xtra_t_app.apk inside it.
Major thanks to deadh0b0 for helping us find where it was!
Anyway, enjoy
Edit: also, obligatory disclaimer that I'm not responsible for anything that happens by doing this! This is literally just-found-out-about-5-minutes-ago work, so I haven't exactly tested it long, my (3UK D855) phone seems to be working fine though, so hopefully all should be good!
Edit2: I think there might be some more to this, not getting any XT debug messages in logcat besides the settings changes, hmm..

I don't even know how it works but I have it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LGLS990 using Tapatalk

Any way to get it working on other versions than the Sprint G3?
Sent from my LG-D851 using Tapatalk

Out chipsets support it, at least my Snapdragon 801 supports it.
But I don't got the option...
http://www.qualcomm.com/snapdragon/processors/801
Sent from my LG-D852 using Tapatalk

D8855 V20i and iZat
Dear All,
Please note that LG D855 with V20i bumped image does not have by default the xtra_t_app.apk applied. However it has the related .so library. If xtra_t_app.apk is installed, the Enhanced Location Menu appears and it allows to turn it on/off.

http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=354153062849400
This is my D855 and i dont have that option and i'm on 5.0 (20h). Can i install xtra_t_app.apk without the libxt_native.so in to my phone? thanks

saigon66 said:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=354153062849400
This is my D855 and i dont have that option and i'm on 5.0 (20h). Can i install xtra_t_app.apk without the libxt_native.so in to my phone? thanks
Click to expand...
Click to collapse
Check your:- /system/vender/lib/folder for the:- libxt_native.so file, if there go ahead, if not see Post #11......

This screen was taken after i installed the apk file. Did i miss something?

saigon66 said:
This screen was taken after i installed the apk file. Did i miss something?
Click to expand...
Click to collapse
My sister's got same blank menu with on/off slider...

Install Xposed framework on Verizon VS986 G4!

Confirmed working! Follow steps in this thread!
http://forum.xda-developers.com/showthread.php?t=3181593
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my VS986 using Tapatalk

Woah.... Makes me pending switch from note 4 better
Sent from my SM-N910V using Tapatalk

Thanks for the repost. Confirmed working.

Man, did I need this. It will take my mind off our locked bootloaders, for a bit longer. Yesterday, I almost traded my G4 for a 64gb Nexus 6.

This is what I was waiting on! I've been keeping my G3 as I needed Xposed for certain modules. Working great.

Ha! I thought of you when I saw this.
Don't get the nexus 6. If anything wait for the next incarnation. The camera actually is pretty bad.
Was this easy to do and are there plenty of modules that work?
thanks
spotmark said:
Man, did I need this. It will take my mind off our locked bootloaders, for a bit longer. Yesterday, I almost traded my G4 for a 64gb Nexus 6.
Click to expand...
Click to collapse

bkrickles said:
Ha! I thought of you when I saw this.
Don't get the nexus 6. If anything wait for the next incarnation. The camera actually is pretty bad.
Was this easy to do and are there plenty of modules that work?
thanks
Click to expand...
Click to collapse
Yeah, it's a simple install. So far I have Xblast, Gravitybox, Holo Themer, and Greenify, up and running.

Absolutely wonderful!
I miss the Per App DPI, why is there not a standalone app for this!!!
Nevermind, I have Xposed now, all is well.
It was a lengthy install (23-27 minutes) but I think it was worth it

Is anyone else getting the "updating apps" dialogue after each reboot?

b3y0ndd34th said:
Absolutely wonderful!
I miss the Per App DPI, why is there not a standalone app for this!!!
Nevermind, I have Xposed now, all is well.
It was a lengthy install (23-27 minutes) but I think it was worth it
Click to expand...
Click to collapse
What did you use to change the DPI?

corywf said:
What did you use to change the DPI?
Click to expand...
Click to collapse
The xposed AppSettings module.
You have to reboot to see changes. Probably because of how lollipop handles apps.
What I meant was I wish there were a standalone app that didn't require xposed that allowed us to change the dpi per app. It's really the only draw I feel towards xposed. The other modules are nice and beneficial, but the large DPI on my phone ruins the UI experience IMHO. If apps like camera, settings, and the block screen worked better on a modified DPI everything would work with a global change to the build.prop

b3y0ndd34th said:
The xposed AppSettings module.
You have to reboot to see changes. Probably because of how lollipop handles apps.
What I meant was I wish there were a standalone app that didn't require xposed that allowed us to change the dpi per app. It's really the only draw I feel towards xposed. The other modules are nice and beneficial, but the large DPI on my phone ruins the UI experience IMHO. If apps like camera, settings, and the block screen worked better on a modified DPI everything would work with a global change to the build.prop
Click to expand...
Click to collapse
Not sure if this will help you but it's what I ended up doing. All the apps work. I don't use the stock lock screen though so I'm not sure about that one.
http://forum.xda-developers.com/g4/general/problem-g4-dpi-t3126972/page2

corywf said:
Not sure if this will help you but it's what I ended up doing. All the apps work. I don't use the stock lock screen though so I'm not sure about that one.
http://forum.xda-developers.com/g4/general/problem-g4-dpi-t3126972/page2
Click to expand...
Click to collapse
I'm alright with the stock DPI, I only adjust the apps that drive me nuts, thanks for the link though.
Thanks for the recommendation, I re read that thread and saw where someone deleted the icons from their lock screen before changing their DPI. That seemed to do the trick!

b3y0ndd34th said:
I'm alright with the stock DPI, I only adjust the apps that drive me nuts, thanks for the link though.
Click to expand...
Click to collapse
For me it's the opposite, it's the UI in general that IMO needs to be smaller and display more data, with the exception being a few apps. I hate only seeing 3-4 notifications since the status bar icons take up so much space.

geoff5093 said:
For me it's the opposite, it's the UI in general that IMO needs to be smaller and display more data, with the exception being a few apps. I hate only seeing 3-4 notifications since the status bar icons take up so much space.
Click to expand...
Click to collapse
Good point on the status bar lol!
I went back and re read the thread I missed the post that said he removed the icons from the lock screen before changing the DPI. I gave that a shot and my lock screen looks perfect now. 540 seems to be an acceptable DPI!

Would it be worthwhile to start up a carrier specific thread that addresses which modules are safe to use for the respective device?

SpinningHook said:
Would it be worthwhile to start up a carrier specific thread that addresses which modules are safe to use for the respective device?
Click to expand...
Click to collapse
Yes it would be.

This is excellent news

Update Xposed from v71 to v72 for Verizon LG G4
Verizon LG G4 VS986 confirmed working with xposed-v72-sdk22-arm64.zip upgrade(Ram is better,battery drain is less)
1)Wipe cache on start
2)Start OS
3)If Flashfire doesn't open,change date in the phone settings to earlier than 8.30.15
4)Follow instructions for v71 installation,but instead of v71.zip use uninstaller for Xposed (xposed-uninstaller-20150831-arm64).Do not uninstall previous version of Xposed which was installed from xposed-v71-sdk22-arm64-by-romracer-20150816 with regular phone means.
5)do not check auto-mount,touch upper right sign and the main page of Flashfire opens
6)Flash (at the very bottom of the screen) uninstaller (all necessary files should be placed on the root of Internal Storage) and wait 10 minutes +,Loading lines appear then another 10 minutes,the phone reboots itself.
7)repeat procedure with FlashFire with zip file xposed-v72-sdk22-arm64
8)Long story now,approximately half an hour of dark screen(do not touch the phone and patiently wait)
9)phone reboots itself,wait and don't worry it'll work with updated Xposed Framework v72,all modules,that have been there before the upgrade,will be there working and activated,no need to reset XposedInstaller_3.0_alpha4.apk
P.S. Make sure the phone has enough charge and not connected to the computer and I assume that you alredy installed this: xposed-v71-sdk22-arm64-by-romracer-20150816.If not,then follow all the instructions from Romracer for v71 file,but
1)use v72 instead
2)Flashfire will not work unless you change the date in the phone settings(you'll correct this easily later)
3)And you will have to wait longer this time(remember,approximately half an hour of dark screen with the impression that the phone is dead,but no worry,just wait and do nothing,cause that's the way it's resetting).Good luck!
Update: the same is confirmed working for new Xposed SDK file: xposed-v73-sdk22-arm64.zip for Verizon LG G4

tulio25 said:
Verizon LG G4 VS986 confirmed working with xposed-v72-sdk22-arm64.zip upgrade(Ram is better,battery drain is less)
1)Wipe cache on start
2)Start OS
3)If Flashfire doesn't open,change date in the phone settings to earlier than 8.30.15
4)Follow instructions for v71 installation,but instead of v71.zip use uninstaller for Xposed (xposed-uninstaller-20150831-arm64).Do not uninstall previous version of Xposed which was installed from xposed-v71-sdk22-arm64-by-romracer-20150816 with regular phone means.
5)do not check auto-mount,touch upper right sign and the main page of Flashfire opens
6)Flash (at the very bottom of the screen) uninstaller (all necessary files should be placed on the root of Internal Storage) and wait 10 minutes +,Loading lines appear then another 10 minutes,the phone reboots itself.
7)repeat procedure with FlashFire with zip file xposed-v72-sdk22-arm64
8)Long story now,approximately half an hour of dark screen(do not touch the phone and patiently wait)
9)phone reboots itself,wait and don't worry it'll work with updated Xposed Framework v72,all modules,that have been there before the upgrade,will be there working and activated,no need to reset XposedInstaller_3.0_alpha4.apk
P.S. Make sure the phone has enough charge and not connected to the computer and I assume that you alredy installed this: xposed-v71-sdk22-arm64-by-romracer-20150816.If not,then follow all the instructions from Romracer for v71 file,but
1)use v72 instead
2)Flashfire will not work unless you change the date in the phone settings(you'll correct this easily later)
3)And you will have to wait longer this time(remember,approximately half an hour of dark screen with the impression that the phone is dead,but no worry,just wait and do nothing,cause that's the way it's resetting).Good luck!
Update: the same is confirmed working for new Xposed SDK file: xposed-v73-sdk22-arm64.zip for Verizon LG G4
Click to expand...
Click to collapse
So you can't just flash the new version over it? You need to uninstall it first?

[ROM][All Quarks][7.1.x][LOS 14.1 Unofficial][2018-06-12]

Latest update: 2018-06-12 To view a changelog, you can visit https://review.lineageos.org/#/q/status:merged+branch:cm-14.1 for a rough idea up to the build date.
Hi all. I was able to compile this stock build of LOS 14.1 thanks to the efforts/hard works of Skrilax_CZ, bhb27, the folks who created RR, and those over at Lineage OS/CyanogenMod. It takes some minor features from RR (i.e. notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps). It is otherwise stock LOS 14.1 and I use this daily. The other authors/devs and I assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
In order to make my calling work for Verizon, I had to go under Settings -> More -> Cellular networks -> Preferred network type, and select LTE/CDMA (not LTE/GSM/UMTS). I assume GSM users should be fine with the defaults.
Also if on Verizon, you should most likely select VZWINTERNET as your APN under Settings -> More -> Cellular networks -> Access Point Names (might not show up at first, but eventually loads)
My recommendations to install:
Install TWRP if you haven't already
3.1.1 - https://www.androidfilehost.com/?w=files&flid=39562 (forum:http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308)
Perform a backup of your current system/ROM (if coming from another ROM).
Perform a factory reset/wipe (if coming from another ROM).
Install the .zip
Install the appropriate google apps.
http://opengapps.org/. I would think nano or micro is best, ARM, and 7.1
Wipe dalvik/art cache if you install another kernel. I highly recommend BHB27 kernel
https://www.androidfilehost.com/?w=files&flid=135512
Reboot and enjoy
Here is the link to the latest ROM on the hosting website:
[2018-06-12]https://androidfilehost.com/?fid=746163614322270411
Previous Builds:
https://www.androidfilehost.com/?w=files&flid=128790
Optional Components:
Remove SU/Root: https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip (Lineage OS extras:https://download.lineageos.org/extras)
BHB27 Kernel: https://www.androidfilehost.com/?w=files&flid=135512 (forum:http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526)
BHB27 Kernel Adiutor: https://www.androidfilehost.com/?w=files&flid=48767
iSU: https://www.androidfilehost.com/?w=files&flid=120360 (forum:http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348)
TurboToast: https://play.google.com/store/apps/details?id=com.bhb27.turbotoast
I'll be back to post updates fairly regularly (~ every few weeks), but I also work full time in addition to being a dad (those of you who are know how that is ) and won't really be able to respond to PMs very well. The sources I used can be found under the post on XDA here at http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109 (device, vendor, and kernel trees). Thanks and God bless.

Nice, downloading... made changes in the kernel?
Thanks developer @calsurferpunk

hpbrasil said:
Nice, downloading... made changes in the kernel?
Thanks developer @calsurferpunk
Click to expand...
Click to collapse
Thanks. No I didn't change anything about the kernel. There isn't a good alternative (that I know of yet) so I just used it straight from bhb for now.

How do I disable the capacitive buttons and use on screen nav bar instead?
Sent from my DROID Turbo using Tapatalk

My device is showing no root on this ROM and if I install super su it gains root but shows no sim card available. Fixed by enabling root permission in development settings.

The rom is almost 100%, the battery is well lasting me .... 1 screen time every 10% quietly, the only problem I really noticed was sending images on whatsapp that is not 100%, you send catch screen and photos taken by whatsapp ... now send images from the gallery do not know why, it just outside joys and once again thank you for your development. @calsurferpunk

eddiemc12 said:
My device is showing no root on this ROM and if I install super su it gains root but shows no sim card available. Fixed by enabling root permission in development settings.
Click to expand...
Click to collapse
It's not fixing it for me. I enabled root in developer options.
What can be the issue here @calsurferpunk
Sent from my DROID Turbo using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Root ok

muhammadtalha-13 said:
It's not fixing it for me. I enabled root in developer options.
What can be the issue here @calsurferpunk
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
I'm not sure what could be going on. I haven't flashed su and just use the stock CM root manager. Enabling root for apps only in developer options makes everything work for me when an app requests it. I did notice that I had to make sure that iSu was setting the policy as permissive (causes FC when set as enforcing).

If not bother you wanted to report a small simple mistake that can not encomodar only to warn even ... In Menu> Settings> Developer Options> animator duration scale, the second option is 0.5x and there is 5x....When I click on the Home screen and select background he simply FC, that's Gallery problem equal to whatsapp that has pictures not ...
The maintainer of CrDroid said I do not know how to use the Android and it really is a problem of rom and he would not listen to me and said she did not like my attitude. @calsurferpunk

calsurferpunk said:
I'm not sure what could be going on. I haven't flashed su and just use the stock CM root manager. Enabling root for apps only in developer options makes everything work for me when an app requests it. I did notice that I had to make sure that iSu was setting the policy as permissive (causes FC when set as enforcing).
Click to expand...
Click to collapse
So if I flash ROM and iSu says no root, then I just have to enable root in developer options without flashing SuperSU? I actually tried developer option after flashing SuperSU. Maybe that's why it didn't work. Let me know if I am right then I'll try the correct procedure.
Sent from my Pixel XL using Tapatalk

muhammadtalha-13 said:
So if I flash ROM and iSu says no root, then I just have to enable root in developer options without flashing SuperSU?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
That's all that I did and I haven't had any issue yet. I didn't have to change anything with iSu either (even if I did mess with it later just to see what it does).

Just as a quick update, next time I post an updated build I believe I know how to skip including iSu and kernel auditor by default. I'll make sure to include a way to download them and include them separately if this is successful. The goal of this is to keep it as close to stock CM 14.1 and still be functional so that anything you want to add can be done by your own free will .

calsurferpunk said:
That's all that I did and I haven't had any issue yet. I didn't have to change anything with iSu either (even if I did mess with it later just to see what it does).
Click to expand...
Click to collapse
Okay got it now. I'll try again later tonight and will confirm here.
Sent from my Pixel XL using Tapatalk

no super su, i enabled root in developer setting and it works fine.

太棒了

Hey @calsurferpunk, very good job. But I have to tell u about a bug I notice. When you'll transfer a music from pc to the phone, the music player says "That's impossible to play (Name of the Music)" and in the Google Play Music the music it's with 0 seconds. The music only goes if you put in recovery mode and transfer the mp3 archive while you're at TWRP.

Hlcpereira said:
Hey @calsurferpunk, very good job. But I have to tell u about a bug I notice. When you'll transfer a music from pc to the phone, the music player says "That's impossible to play (Name of the Music)" and in the Google Play Music the music it's with 0 seconds. The music only goes if you put in recovery mode and transfer the mp3 archive while you're at TWRP.
Click to expand...
Click to collapse
It might be a bug with Play Music. I have transferred music normally and Poweramp plays it without any problems.

Shooting Star Max said:
It might be a bug with Play Music. I have transferred music normally and Poweramp plays it without any problems.
Click to expand...
Click to collapse
No man, the problem still at the music player which goes installed in the ROM.

[ROOT] [HD 10] Restore stock battery stats (power usage summary)

I have a surprise for everyone Well if you are on 5.6.1.0 anyways (Support for 5.6.2.0 coming soon). Want to know what application or system function is draining your battery...without installing ANOTHER application to give you those statistics? Well too bad. Amazon said you couldn't have it. They made sure of it too...at least until I came along Without getting fancy, and to make a long story short, Amazon removed a bunch of stuff from the power_profile.xml in the framework-res.apk (/system/framework/framework-res.apk). One of the things they removed was the battery statistics. Not just some, but ALL of them. They also deleted some CPU stats and all the WiFi batched scanning support configurations.
Here you go. You can have all of them back. How? There are many apps that clock your CPU so I logged it for a bit and found the highest and lowest speed values. Since Google has the raw file, with comments on what that should mean on their website, this got pretty easy really fast. For this to start working properly you need to follow the instructions below.
Requirements:
1. ADB/platform-tools
2. ADBD insecure (located here)
3. Rooted Fire 10
4. The 2 APKs located at the bottom of this thread.
5. Activity Launcher
Installation:
1. Download framework-res.apk and FireTabletSettings.apk at the bottom of this posting, and put them in your ADB/platform-tools folder.
1. Install ADBD Insecure, open the app and make ADB insecure.
2. Open an ADB window, making sure debugging is enabled on your tablet, plug it into your PC and type this command to make the system r/w:
Code:
adb remount
3. Now type these two commands to push the files to your tablet. ADB will set the proper permissions:
Code:
adb push framework-res.apk /system/framework/framework-res.apk
adb push FireTabletSettings.apk /system/priv-app/FireTabletSettings
4. Now reboot:
Code:
adb reboot
5. Install and open activity launcher and scroll to settings and tap it. Then scroll to the first battery setting and tap it. Battery stats! If you don't see any user apps or system apps appear, download appops from the play store and make sure to grant the permissions to the apps that ask for usage access.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BONUS!!!
The framework-res APK and the FireTabletSettings.apk both contain ALL of my latest hacks or mods and optimizations. If you want the Daydream Screensaver though, you have to make your way over to this thread and just download and install the Basic Dreams APK into /system/app.

Hell yeah dude, what a nice surprise! Congrats on figuring that all out man, you truly are the savior of these tablets helping to make them so much better than they are.
I think this will be my rainy day project for today, that is unless it rains too much and I have to deal with keeping my garage from flooding out [emoji1787]
Once again, thanks bro and keep up the killer work!
Sent from my SM-G935V using Tapatalk

tylerhole said:
Hell yeah dude, what a nice surprise! Congrats on figuring that all out man, you truly are the savior of these tablets helping to make them so much better than they are.
I think this will be my rainy day project for today, that is unless it rains too much and I have to deal with keeping my garage from flooding out [emoji1787]
Once again, thanks bro and keep up the killer work!
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Anytime

Just showing it's working

Can't wait for 5.6.2.0 version!
Sent from my LGM-V300K using Tapatalk

KIMmunity said:
Can't wait for 5.6.2.0 version!
Click to expand...
Click to collapse
I'll try and work on it today.
Sent from my Amazon KFSUWI using XDA Labs

I went ahead and gave this a run on 5.6.2.0, everything works as described with no obvious issues. Thanks again for all of your work dude.

If you have Nova Launcher installed, you don't need Activity Launcher installed.
Simply, go to 'Widgets'(pinch with two fingers on desktop screen for Widgets menu icon), select 'Activities' from the list of Nova Launcher widgets, drag & drop on the desktop, scroll down to 'Settings', and select 'Battery'(.settings$PowerUsageSummaryActivity - the first on the list).
Thanks @DragonFire1024 for always introducing great features. I also confirm that the two apk files run on 5.6.2.0.

Confirmed working on 5.3.6.4.
Some issues accessing Google account and SuperSU. Confirmation pending.

Any confirmation on weather this works on 5.3.6.4 yet ??
UPDATE: Ok I just found out 5.3.6.4 is 5.6.2.0 just labeled wrong by Amazon ( idiots ) .... So Yes it will work.

remount
adb remount fails.
Command and output:
remount of system failed: Permission denied
remount failed

jhford said:
adb remount fails.
Command and output:
remount of system failed: Permission denied
remount failed
Click to expand...
Click to collapse
You have to have adbd insecure installed to push the file across ADB.

Are the WiFi tweaks included in this APK?

Wall.swe said:
Are the WiFi tweaks included in this APK?
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy S4 using XDA Labs

Im having issues with Bluetooth turning on after doing this. Any ideas?

JohnnyX74 said:
Im having issues with Bluetooth turning on after doing this. Any ideas?
Click to expand...
Click to collapse
No idea. I've not made any modifications to the hardware or any Bluetooth related changes to the framework. The battery stats just show statistics based on power usage and the values there just state the minimum level to record the stats. Did you wipe cache and dalvik after installing?
Edit: i have had my Bluetooth on now with Pandora streaming for 3 hours so far, with the same framework. So far no one else has reported any hardware issues. Since I don't know what could be the cause, you may want to go back to the original framework and settings you had before.

DragonFire1024 said:
No idea. I've not made any modifications to the hardware or any Bluetooth related changes to the framework. The battery stats just show statistics based on power usage and the values there just state the minimum level to record the stats. Did you wipe cache and dalvik after installing?
Edit: i have had my Bluetooth on now with Pandora streaming for 3 hours so far, with the same framework. So far no one else has reported any hardware issues. Since I don't know what could be the cause, you may want to go back to the original framework and settings you had before.
Click to expand...
Click to collapse
How do you do the davlik and cache since we don't have an official recovery like TWRP? PS has anyone noticed there Google and Gmail app crashing? Mine just started. Idk what's going on.

JohnnyX74 said:
How do you do the davlik and cache since we don't have an official recovery like TWRP? PS has anyone noticed there Google and Gmail app crashing? Mine just started. Idk what's going on.
Click to expand...
Click to collapse
Gmail is give or take. Works for some and not for others. That's across all amazon tablets. Google has really screwed up the last update at least for pur device. The last known stable version was any of the 8.33 versions. You can wipe dalvik and cache through flashfire.

DragonFire1024 said:
Gmail is give or take. Works for some and not for others. That's across all amazon tablets. Google has really screwed up the last update at least for pur device. The last known stable version was any of the 8.33 versions. You can wipe dalvik and cache through flashfire.
Click to expand...
Click to collapse
Somehow I found my system app folder was deleted I extracted the apps from the bin then dat files but is there a quick way to put them back? Like without doing it all by hand in Root Explorer?

JohnnyX74 said:
Somehow I found my system app folder was deleted I extracted the apps from the bin then dat files but is there a quick way to put them back? Like without doing it all by hand in Root Explorer?
Click to expand...
Click to collapse
You can flash back to stock. Otherwise you'll have to wait until I get home and have more time to explain another way unless someone else does first.