• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Just throwing this out there: Cm13 for g2 mini sources

Test build! http://www.mediafire.com/download/9f9kqnn8k0uqv2g/cm-13.0-20160526-UNOFFICIAL-x5.zip

Everything should now work except for NFC, and the usual green tint camera. NFC seems to be on the cusp of working, it goes through the complete NFC setup but the chip stops responding at some point.

Shouldn't need to do a full wipe if updating from previous CM13 builds either. Just cache and dalvik-cache.

Does this latest test build solve the buggy root problems and sd card full read/write access on the 4-25 version https://www.androidfilehost.com/?fid=24499762636008554 ? Better yet, what was fixed from 4-25 version?
 
Last edited:
Does this latest test build solve the buggy root problems and sd card full read/write access on the 4-25 version https://www.androidfilehost.com/?fid=24499762636008554 ? Better yet, what was fixed from 4-25 version?

Keep in mind that all we're trying to do is configuration. The root issue is going to be with CyanogenMod code itself, and the sd card read/write access is just how things are done on Android now. All I've done is get the key backlight working and figure out what "broke" in whoshotjr2006's later builds.

My build is not intended as a daily driver nor is it recommended as one. NFC is stuck on but non-functional, and your battery will quickly drain as a result. This is put out there for anyone who wants to look at it and come up with ideas on how to fix the configuration issues, namely
  • compass
  • NFC
  • green tint
Outside of those, if it's a kernel bug I can try to fix it, otherwise it's in the court of the CyanogenMod project.
 
Does this latest test build solve the buggy root problems and sd card full read/write access on the 4-25 version https://www.androidfilehost.com/?fid=24499762636008554 ? Better yet, what was fixed from 4-25 version?
Why is everyone seeing vastly different issues with the 4/25 build? I don't seem to have any SD card read/write issues. A1 SD card bench shows around 15mb/s read and around 10-15mb/s write, should it be faster for a class 10 card? About root, never had amy issues either. I turned on developers settings and then enabled the built in CM root. All apps that request root cause a popup in which I can grant or deny root.
EDIT: If some app cannot access the SD card, have you made sure you have given it the proper permissions in settings?
 
Last edited:
Keep in mind that all we're trying to do is configuration. The root issue is going to be with CyanogenMod code itself, and the sd card read/write access is just how things are done on Android now. All I've done is get the key backlight working and figure out what "broke" in whoshotjr2006's later builds.

My build is not intended as a daily driver nor is it recommended as one. NFC is stuck on but non-functional, and your battery will quickly drain as a result. This is put out there for anyone who wants to look at it and come up with ideas on how to fix the configuration issues, namely
  • compass
  • NFC
  • green tint
Outside of those, if it's a kernel bug I can try to fix it, otherwise it's in the court of the CyanogenMod project.

So can't I just uninstall NFC from system using root uninstaller app ? I could care less about NFC never will use it.
 
Why is everyone seeing vastly different issues with the 4/25 build? I don't seem to have any SD card read/write issues. A1 SD card bench shows around 15mb/s read and around 10-15mb/s write, should it be faster for a class 10 card? About root, never had amy issues either. I turned on developers settings and then enabled the built in CM root. All apps that request root cause a popup in which I can grant or deny root.
EDIT: If some app cannot access the SD card, have you made sure you have given it the proper permissions in settings?

Yes some of us have had root and sd card issues, not just me. I'm going to start over this time have sd card formatted using CM13 rom itself. Also I turned on developer root (apps only) first thing maybe I should check both apps and ADB root? I'm going to use this latest build and see what it brings. And as far as permission settings, yes enabled everything but seemed like the PrivacyGuard thing was hindering some of my access to sd card. I wish I could actually turn the whole PrivacyGuard thing off but don't think you can. Or can you ? I do remember being offered the choice to make sd card either external media storage or internal storage I chose the external one because was told Titanium can't backup to sd card when it's set as internal. ???
 
Last edited:
So can't I just uninstall NFC from system using root uninstaller app ? I could care less about NFC never will use it.
I haven't found a combination of files to remove yet that will stop the draining. I'm not interested in NFC either, other than that it needs to work for official CM support. Please let me know if you find a combination, I'll do the same.
 
What about flashing your build ontop of the QuickRemote IR fix?

the whole quickremote debacle is based upon the fact that all the sister msm8226 lg devices are bootloader unlocked. the zip attached will make a boot.img that works no problem. the only problem is bumping it, if you want to crack open the zip and add bump support to the script that replaces things in the ramdisk, you could be able to flash the zip after any cm13 flash and be fine.

basically this means any of the kernel work spock is doing right now with button backlights, nfc and sensors would be voided out by flashing the forirrc.img boot image after flashing his cm13 build. this can be worked around very easily by telling the installer script for quickremote to save the modified boot.img to the sdcard instead of flashing it, then copying it to a computer and bumping it. then flash that boot.img after flashing new updates of cm13 and quickremote zip, modifying the ramdisk would have to be done every time after new changes are made to kernel.
 
I haven't found a combination of files to remove yet that will stop the draining. I'm not interested in NFC either, other than that it needs to work for official CM support. Please let me know if you find a combination, I'll do the same.
I flashed your build on top of the QickRemote flash. As suspected the QuickRemote app disappeared which makes since based on what @whoshotjr2006 said a couple of posts back. It would be nice to have for whenever I might need a IR remote, but I don't use QuickRemote enough for it to be a deal breaker.

I'm sort of interested in NFC, I brought a bunch of "NFC Stickers" that cotain the coil and chip sandwiched between two layers for when NFC started working. But your build does not keep NFC turned on. On first flash it was on but after a reboot it shows its off in settings and I don't see any noticeable battery drain yet. Nevermind.

Why is NFC a requirement for official Cyanogenmod support? Not every phone has NFC.
 
Last edited:
I flashed your build on top of the QickRemote flash. As suspected the QuickRemote app disappeared which makes since based on what @whoshotjr2006 said a couple of posts back. It would be nice to have for whenever I might need a IR remote, but I don't use QuickRemote enough for it to be a deal breaker.

I'm sort of interested in NFC, I brought a bunch of "NFC Stickers" that cotain the coil and chip sandwiched between two layers for when NFC started working. But your build does not keep NFC turned on. On first flash it was on but after a reboot it shows its off in settings and I don't see any noticeable battery drain yet. Nevermind.

Why is NFC a requirement for official Cyanogenmod support? Not every phone has NFC.
Official Cyanogenmod support is contingent upon a 100% working device. They'll take non-100% on a case-by-case basis. So essentially, if we can we should get this stuff working on our own. We might be able to squeak by if we just have green tint, but my gut tells me that if we show up with three issues we'll be told to come back later.
 
Test build! http://www.mediafire.com/download/9f9kqnn8k0uqv2g/cm-13.0-20160526-UNOFFICIAL-x5.zip

Everything should now work except for NFC, and the usual green tint camera. NFC seems to be on the cusp of working, it goes through the complete NFC setup but the chip stops responding at some point.

Shouldn't need to do a full wipe if updating from previous CM13 builds either. Just cache and dalvik-cache.


Got a few hard shutdown crashes with this build where the device just died with plenty of battery life left and never turned on by itself. I had to force it back on by holding the power button a long time to get it to boot. Attached is a /proc/last_kmsg I was able to snag once the device booted back up. I had to install the 4/25 build again since that works the best for me so far.

Also I have a idea about the green tint, not sure if it's been discussed before but has anyone noticed that if you search "LG Volt" at the LG Open Source web site you get multiple different LG Volt devices? These devices don't appear to be any LG Volt 2 either, the list includes LGLS740, LGLS740P, LGLS740PZ, and LGLS740Z. See those extra three devices? I cannot seem to find these for sale anywhere, maybe the source code online has clues for what settings LG used for the green tint affected cameras? Dunno just a thought.
 

Attachments

Last edited:
Latest kernel source is up so others can take advantage of the long weekend. Attached is the new liblight.

Got a few hard shutdown crashes with this build where the device just died with plenty of battery life left and never turned on by itself. I had to force it back on by holding the power button a long time to get it to boot. Attached is a /proc/last_kmsg I was able to snag once the device booted back up. I had to install the 4/25 build again since that works the best for me so far.

Also I have a idea about the green tint, not sure if it's been discussed before but has anyone noticed that if you search "LG Volt" at the LG Open Source web site you get multiple different LG Volt devices? These devices don't appear to be any LG Volt 2 either, the list includes LGLS740, LGLS740P, LGLS740PZ, and LGLS740Z. See those extra three devices? I cannot seem to find these for sale anywhere, maybe the source code online has clues for what settings LG used for the green tint affected cameras? Dunno just a thought.

Looks like a bug in the wifi driver.
 

Attachments

Last edited:
Got a few hard shutdown crashes with this build where the device just died with plenty of battery life left and never turned on by itself. I had to force it back on by holding the power button a long time to get it to boot. Attached is a /proc/last_kmsg I was able to snag once the device booted back up. I had to install the 4/25 build again since that works the best for me so far.

Also I have a idea about the green tint, not sure if it's been discussed before but has anyone noticed that if you search "LG Volt" at the LG Open Source web site you get multiple different LG Volt devices? These devices don't appear to be any LG Volt 2 either, the list includes LGLS740, LGLS740P, LGLS740PZ, and LGLS740Z. See those extra three devices? I cannot seem to find these for sale anywhere, maybe the source code online has clues for what settings LG used for the green tint affected cameras? Dunno just a thought.

Bug seems to be the same as https://jira.cyanogenmod.org/browse/BACON-213 but it hasn't been resolved yet.
 
Doesn't look like whatever is going on with the compass is kernel related. It looks like we have the bosch bmc050, and there's absolutely nothing in the kernel source about it.
 
So far so good running this latest build. Just wish there was some way to get full read write access to the sd card. I looked into trying Folder Mount app but even the beta one needs SuperSu running so no luck there. Was thinking could link internal folder to external folder as a work around. So for now having to save Titanium backups to internal then upload to google cloud for real backup.
 
On this recent build, did dev take out LiveDisplay? Can't see it on Display & Lights settings page. It was on there previous version back in april. Hmmmmmm.
 
On this recent build, did dev take out LiveDisplay? Can't see it on Display & Lights settings page. It was on there previous version back in april. Hmmmmmm.
Not on purpose, didn't touch anything that would have affected that other than syncing with CM.
 
Back
Top Bottom