• 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

spock1104 said:
I agree, I don't recommend any of my builds for a daily driver, daily use should be on the 4/25 build. That said, it won't get any better without feeding me logs of the issues experienced. The only issues I've personally experienced are
  • stuck nfc battery drain
  • rotation stops working after camera use
  • occasional lock-up using maps
Click to expand...
Would you like for us to post logcats? If so would it be possible to still acquire one, let's say, after the phone froze and shutdown?
 
che_edgar said:
Would you like for us to post logcats? If so would it be possible to still acquire one, let's say, after the phone froze and shutdown?
Click to expand...

It *might* be possible, if conditions are right the OS saves logs to various places when a crash occurs. The below locations might have logs.

/proc/last_kmsg -- This is for system logs when the kernel panics or crashes. This file shows up right after the last kernel panic or crash, such as when your phone unexpectedly shutdown. This can be read by the "editor" in Cyanogenmod file manager or any text editor. Just copy the whole file to your computer and upload it.

/data/dontpanic -- Also contains some kernel and system logs related to kernel panics or crashes.

/data/tombstones -- Also contains some extra logs from application and system crashes.

You can also pull up whatever your device has for logs and crashes if you have ADB. Connect your phone to a comp and run "adb bugreport", this pulls up a HUGE output of all sorts of crash and panic related logs so it might take a minute before you get output. "adb bugreport > some.txt" can dump that to a file.
 
ShapeShifter499 said:
It *might* be possible, if conditions are right the OS saves logs to various places when a crash occurs. The below locations might have logs.

/proc/last_kmsg -- This is for system logs when the kernel panics or crashes. This file shows up right after the last kernel panic or crash, such as when your phone unexpectedly shutdown. This can be read by the "editor" in Cyanogenmod file manager or any text editor. Just copy the whole file to your computer and upload it.

/data/dontpanic -- Also contains some kernel and system logs related to kernel panics or crashes.

/data/tombstones -- Also contains some extra logs from application and system crashes.

You can also pull up whatever your device has for logs and crashes if you have ADB. Connect your phone to a comp and run "adb bugreport", this pulls up a HUGE output of all sorts of crash and panic related logs so it might take a minute before you get output. "adb bugreport > some.txt" can dump that to a file.
Click to expand...

These are exactly what I need when the phone locks or reboots.
 
spock1104 said:
I agree, I don't recommend any of my builds for a daily driver, daily use should be on the 4/25 build. That said, it won't get any better without feeding me logs of the issues experienced. The only issues I've personally experienced are
  • stuck nfc battery drain
  • rotation stops working after camera use
  • occasional lock-up using maps
Click to expand...
Well I've been using the 6-1 for a few days & it's working fine, plus my 4G still works, I'm stoked just because of that! Thank you devs.
 
I am starting to notice on latest build that some of my app notifications don't work when they should because I know they are set up correctly. One is an outage notification from local electric company app and other is cell phone tracker app notifications. Can't remember if they were working on 4/25 version but pretty sure this one has a bug on notifications. Think my missed call audio notification also does not work.
 
ShapeShifter499 said:
@spock1104 and @whoshotjr2006 which manifest and github repos do I use now if I want to try to build off the current fixes? I want to mess around again and maybe try to fix somethings, mainly OTG support.
Click to expand...
Go through normal CM13 setup, then put this file in .repo/local_manifests and do another repo sync
You might have to manually modify stuff in proprietary/vendor/lge, I haven't tested this and it'll replace files.
You also need to copy the new liblights code I posted previously into device/lge/x5/liblight, my files are a mess right now from trying to get NFC working and so I haven't updated github.
 
spock1104 said:
Go through normal CM13 setup, then put this file in .repo/local_manifests and do another repo sync
You might have to manually modify stuff in proprietary/vendor/lge, I haven't tested this and it'll replace files.
You also need to copy the new liblights code I posted previously into device/lge/x5/liblight, my files are a mess right now from trying to get NFC working and so I haven't updated github.
Click to expand...

Downloading and building right now! Once I get a working build I'll move on to searching the net for possible fixes.
 
spock1104 said:
Go through normal CM13 setup, then put this file in .repo/local_manifests and do another repo sync
You might have to manually modify stuff in proprietary/vendor/lge, I haven't tested this and it'll replace files.
You also need to copy the new liblights code I posted previously into device/lge/x5/liblight, my files are a mess right now from trying to get NFC working and so I haven't updated github.
Click to expand...

I'm getting this error https://pastee.org/5qu3v
 
ShapeShifter499 said:
I'm getting this error https://pastee.org/5qu3v
Click to expand...

FIXED! With the help of #cyanogenmod-dev on freenode, it looked like I had to change the manifests file you gave me. Below is the current file with fixes.

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
  <project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-13.0" />
  <project name="spock1104/android_kernel_lge_msm8226" path="kernel/lge/msm8226" remote="github" revision="cm-13.0" />
  <project name="spock1104/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
  <project name="touchpro/android_device_lge_msm8226-common" path="device/lge/msm8226-common" remote="github" revision="cm-13.0" />
  <project name="touchpro/android_device_lge_x5" path="device/lge/x5" remote="github" revision="master" />
  <project name="touchpro/vendor_lge_x5" path="vendor/lge/x5" remote="github" revision="cm-13.0" />
</manifest>
 
New build. Changes are sync with CM source (latest android security updates come with that) and the phone no longer suffers from amnesia, it now correctly identifies itself.

http://www.mediafire.com/download/5v5z6qkh7dm3f9o/cm-13.0-20160711-UNOFFICIAL-x5.zip

I also found that putting the phone into airplane mode, even briefly, kills off the NFC battery drain.

Reminder: If an app has an issue I need a logcat. If the phone locks or reboots I need a /proc/last_kmsg. NFC is still wonky and needs people willing to toy with build.prop, libnfc-bcrm.conf, and libnfc-nxp.conf.
 
spock1104 said:
New build. Changes are sync with CM source (latest android security updates come with that) and the phone no longer suffers from amnesia, it now correctly identifies itself.

http://www.mediafire.com/download/5v5z6qkh7dm3f9o/cm-13.0-20160711-UNOFFICIAL-x5.zip

I also found that putting the phone into airplane mode, even briefly, kills off the NFC battery drain.

Reminder: If an app has an issue I need a logcat. If the phone locks or reboots I need a /proc/last_kmsg. NFC is still wonky and needs people willing to toy with build.prop, libnfc-bcrm.conf, and libnfc-nxp.conf.
Click to expand...

Has the updated code for this been uploaded somewhere?
 
spock1104 said:
New build. Changes are sync with CM source (latest android security updates come with that) and the phone no longer suffers from amnesia, it now correctly identifies itself.

http://www.mediafire.com/download/5v5z6qkh7dm3f9o/cm-13.0-20160711-UNOFFICIAL-x5.zip

I also found that putting the phone into airplane mode, even briefly, kills off the NFC battery drain.

Reminder: If an app has an issue I need a logcat. If the phone locks or reboots I need a /proc/last_kmsg. NFC is still wonky and needs people willing to toy with build.prop, libnfc-bcrm.conf, and libnfc-nxp.conf.
Click to expand...
Testing. Thanks dev. [emoji4]
 
spock1104 said:
New build. Changes are sync with CM source (latest android security updates come with that) and the phone no longer suffers from amnesia, it now correctly identifies itself.

http://www.mediafire.com/download/5v5z6qkh7dm3f9o/cm-13.0-20160711-UNOFFICIAL-x5.zip

I also found that putting the phone into airplane mode, even briefly, kills off the NFC battery drain.

Reminder: If an app has an issue I need a logcat. If the phone locks or reboots I need a /proc/last_kmsg. NFC is still wonky and needs people willing to toy with build.prop, libnfc-bcrm.conf, and libnfc-nxp.conf.
Click to expand...

Wait if I read correctly, you didn't actually change anything. Just having updated the code from CM fixed some issues.
 
ShapeShifter499 said:
I did

croot
breakfast cm_x5-userdebug
brunch cm_x5-userdebug

I got a build just a few moments ago, why shouldn't I have done breakfast?
Click to expand...
breakfast tries to download source from known cyanogenmod sources. We don't have known cyanogenmod sources. not yet at least.

I can hope :(
 
spock1104 said:
New build. Changes are sync with CM source (latest android security updates come with that) and the phone no longer suffers from amnesia, it now correctly identifies itself.

http://www.mediafire.com/download/5v5z6qkh7dm3f9o/cm-13.0-20160711-UNOFFICIAL-x5.zip

I also found that putting the phone into airplane mode, even briefly, kills off the NFC battery drain.

Reminder: If an app has an issue I need a logcat. If the phone locks or reboots I need a /proc/last_kmsg. NFC is still wonky and needs people willing to toy with build.prop, libnfc-bcrm.conf, and libnfc-nxp.conf.
Click to expand...
Thanks again for the new build! So far so good! No issues to report just smooth sailing!
 
spock1104 said:
I'll be hesitant to say daily driver until we fix NFC.
Click to expand...

I always uninstall NFC app anyway dont want it. So guess Im asking is this then a good daily driver to replace the 4-25 one ? I tried one of the recent ones and could not get skype to install so went back to 4-25. ??
 
kwiknuts said:
I always uninstall NFC app anyway dont want it. So guess Im asking is this then a good daily driver to replace the 4-25 one ? I tried one of the recent ones and could not get skype to install so went back to 4-25. ??
Click to expand...

I don't use Skype, wouldn't know
 
Ok if anyone is running this latest July 11 version could you install Skype from google play store and see if it opens or crashes then just uninstall it. Would take 2-3 mins. Sure would like to know and would save me a ton of effort and time. thanks
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom