• 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:
Considering the number of issues 2.8.7.0 is causing, I'm going to put this out there for expert users. It has an issue where it WILL lock up once booted. I can't get a kmsg/dmesg/last_kmsg out of it and so can't troubleshoot, but if by some miracle someone can get me a log then I can get a newer TWRP fully running.

http://www.mediafire.com/file/e11vc2drd1kae7o/twrp_302-2_volt.img

Again, don't flash expecting this to work. It won't.
Click to expand...


@spock1104 So I found out that TWRP dumps it logs (sometimes) to /cache/recovery/last_log. SO I have a log for you from the above TWRP build that seems to suggest some simple errors with the fstab. https://gist.github.com/ShapeShifter499/b48016421dc3d6d7a4b6e9ab56b383d3


EDIT: Removed attached file and uploaded to gist.github.com due to fact previous files uploaded to Android Forums have been corrupted.
 
Last edited:
@spock1104 New log, I was able to send a photo twice from the LG Volt to the Moto X Pure. However I was still unable to send anything from the Moto X Pure to the LG Volt. But hey PROGRESS!
https://gist.github.com/ShapeShifter499/d9c14ea42ebee6969c2c0c0a719d5252

I was unable to get the LG Volt to see any of the NFC tags I have. I have two kinds, a 'Samsung TecTile' pack of five and one knockoff, all brought on eBay. All of these tags do work and have been tested on my other phone, the Moto X Pure.
 
ShapeShifter499 said:
@spock1104 something seems wrong, must be the accelerometer. If I hold my phone upright in portrait it rotates as if I'm holding my phone landscape and if I hold my phone in landscape it will rotate to portrait, seems inverted.
Click to expand...

Yeah this is the issue I was talking about that supposedly can be fixed by editing sensord_config_axis. Been looking at it for two months and haven't figured it out yet.
 
@spock1104 Did you configure the system as BMC150? I see hints in the stock files that suggest we are using that. i.e. sensor_def_qcomdev.conf

Also I get the below line looking into my logcat.
Code: 
11-16 12:52:10.762   634   987 D EventHub: No input device configuration file found for device 'bmm050'.
 
ShapeShifter499 said:
Do you have any idea how rotation worked in earlier builds?
Click to expand...
spock1104 said:
OK guys, I'm going to call this a preview build. As I've been saying, vm03 pushed new drivers for the sensors and I've been trying to get it fully working. I haven't had much time or motivation to work on finishing it though. The compass now works, but the orientation is wrong. The proximity sensor isn't working at the moment.
Click to expand...

The older builds were using the stock LG sensor libraries. I switched to using the open source kernel drivers and libraries. There's nothing wrong with the driver, just the orientation. Yes, I enabled BMC150. I also enabled BMM050 in case we had a combination device that maybe LG left the driver out for originally.

I think I know how to get the proximity sensor working, but I've been focused on the orientation, and even that I haven't had much time for.
 
ShapeShifter499 said:
@spock1104 So I found out that TWRP dumps it logs (sometimes) to /cache/recovery/last_log. SO I have a log for you from the above TWRP build that seems to suggest some simple errors with the fstab. https://gist.github.com/ShapeShifter499/b48016421dc3d6d7a4b6e9ab56b383d3


EDIT: Removed attached file and uploaded to gist.github.com due to fact previous files uploaded to Android Forums have been corrupted.
Click to expand...

Tried whoshotjr2006's fstab (mine definitely had a few errors in comparison) but still crashes. Maybe it'll at least log better.

http://www.mediafire.com/file/gpqeapw3408a09z/twrp_302-3_volt.img

0D59E8E377D0F7B7F2B7840A3C5F4846
 
Not gonna lie, I've finally stopped being lazy and flashed the 8-19 build. I dont know if im just crazy but it seems like the battery is draining kind of faster than it did on CM11. Could it possibly have to do with NFC or should I just not worry.
 
DeltaXzombies said:
Not gonna lie, I've finally stopped being lazy and flashed the 8-19 build. I dont know if im just crazy but it seems like the battery is draining kind of faster than it did on CM11. Could it possibly have to do with NFC or should I just not worry.
Click to expand...
I would give it a few days to settle down. Are you using the same apps?
 
DeltaXzombies said:
Not gonna lie, I've finally stopped being lazy and flashed the 8-19 build. I dont know if im just crazy but it seems like the battery is draining kind of faster than it did on CM11. Could it possibly have to do with NFC or should I just not worry.
Click to expand...

NFC will definitely play into it. I was using Amaze File Manager to delete the NFC service. Pretty much killed off the drain. With my light use I could get 2.5 days out of a charge.
 
I got it working with folder mount from the play store (I got folder mount working by changing selinux to permissive with the SELinuxModeChanger app from xda).
 
spock1104 said:
The older builds were using the stock LG sensor libraries. I switched to using the open source kernel drivers and libraries. There's nothing wrong with the driver, just the orientation. Yes, I enabled BMC150. I also enabled BMM050 in case we had a combination device that maybe LG left the driver out for originally.

I think I know how to get the proximity sensor working, but I've been focused on the orientation, and even that I haven't had much time for.
Click to expand...
Browsing through the I2C interface I can see that we have BMM050 and BMA2X2
 
andMego said:
I got it working with folder mount from the play store (I got folder mount working by changing selinux to permissive with the SELinuxModeChanger app from xda).
Click to expand...
That sounds like overkill. I admittedly haven't used TitaniumBackup to access a nandroid, but you should be able to use the DocumentProvider to select the external SD card. This is how I access the external for Titanium Backup data.
 
So thoughts on this? Unplugged at 5:30 am, mid-heavy use. YouTube for about 3-4 combined hours, Google Play music, WiFi on most of the time, and I have Greenify and Amplify installed. Also I deleted NFC like Spock said. I got pretty much the same results on CM11 but didn't have any battery savers installed.
 

Attachments

  • Screenshot_20161121-200131.png
    Screenshot_20161121-200131.png
    42.4 KB · Views: 134
Youtube would especially kill it, and maybe Google Play music as well. If your phone isn't asleep it's sucking down power. Best you could do is turn down the screen brightness. Give it a few days, maybe you had a bad charge. If it continues, consider using Better Battery Stats to hunt it down.
 
spock1104 said:
NFC will definitely play into it. I was using Amaze File Manager to delete the NFC service. Pretty much killed off the drain. With my light use I could get 2.5 days out of a charge.
Click to expand...

Is there still a bug somewhere that causes battery drain when you disable NFC as opposed to deleting the NFC service?
 
You must log in or register to reply here.
Back
Top Bottom