• 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

fido14dido said:
What is the recommended recovery to be used with the 08/19/16 build of this ROM? I've installed the ROM with TWRP 2.8.7 and am having issues booting into recovery. On one phone (VM version), it gets stuck on the TeamWin screen. Not looping, just stuck there. I've tried the recovery boot loop fix with FastADB and no luck. On another phone, (Boost), the phone freezes up what I quit recovery. Both phones booted and exited fine from recovery prior to this ROM. TIA for any advice.
Click to expand...

My issue was solved when I removed the microSD cards from the phone. Both phones booted into recovery fine. They (32gb/16gb) were set up as internal storage. They also booted up fine when I used an unrelated 2gb microSD.
 
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.
 
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...

Well I flashed this and moments after this TWRP build booted the screen went dark. I cannot get a log it seems. However even though the screen is dark and unresponsive it opened a bunch of devices on my Linux system. Seems I can access all the partitions on the LG Volt over USB, did you mess up the TWRP USB configuration?
 
I have gotten logs, not quite sure if they are the correct ones. They appear inside of what seems to be a "944 MB" USB mount that appears right after the LG Volt screen goes dark on loading of TWRP. I believe this mount is the recovery partition which TWRP is giving me access to via USB for whatever reason. I'll upload the contents of two 'log' files I can access, I don't see anything useful inside based off what I googled from warning and error messages but maybe you'll see something else @spock1104.

Both log files seem to be the same but I uploaded them anyways, they are both at the following gist link
https://gist.github.com/ShapeShifter499/406f822a0a09eb05feb22cd4b589768a
 
Last edited:
This ROM is working great but is there an easy way to change the default minfree settings without root access
/sys/module/lowmemorykiller/parameters/minfree

It seems to be very aggressive and causes some games to have issues, particularly Pokemon Go. The dilemma is that the game now blocks all phones with root access (yes there are workarounds but its a losing cat/mouse game) but I need to tweak the minfree settings with Kernel Aduitor in order to play the game and that requires root access. I've tried googling for a way to change the default minfree settings but all solutions required root access. Is there an easy way to change the defaults? Or does this need to be changed in the kernel? Thanks.
 
fido14dido said:
This ROM is working great but is there an easy way to change the default minfree settings without root access
/sys/module/lowmemorykiller/parameters/minfree

It seems to be very aggressive and causes some games to have issues, particularly Pokemon Go. The dilemma is that the game now blocks all phones with root access (yes there are workarounds but its a losing cat/mouse game) but I need to tweak the minfree settings with Kernel Aduitor in order to play the game and that requires root access. I've tried googling for a way to change the default minfree settings but all solutions required root access. Is there an easy way to change the defaults? Or does this need to be changed in the kernel? Thanks.
Click to expand...
you might be able to put the settings into a startup script. My honest recommendation though is to get a new phone with at least 2gb ram if you're able. If I weren't a cheapskate I'd have jumped to the Moto G4 already.
 
fido14dido said:
This ROM is working great but is there an easy way to change the default minfree settings without root access
/sys/module/lowmemorykiller/parameters/minfree

It seems to be very aggressive and causes some games to have issues, particularly Pokemon Go. The dilemma is that the game now blocks all phones with root access (yes there are workarounds but its a losing cat/mouse game) but I need to tweak the minfree settings with Kernel Aduitor in order to play the game and that requires root access. I've tried googling for a way to change the default minfree settings but all solutions required root access. Is there an easy way to change the defaults? Or does this need to be changed in the kernel? Thanks.
Click to expand...

If you use kernel Adiutor I think in settings it has a option to use a shell script to apply setting
 
spock1104 said:
OK this is a bit of a stretch, but try editing /sys/module/printk/parameters/always_kmsg_dump and change from N to Y. The next time the phone freezes, make sure to hold the power button to reboot, pulling the battery will definitely lose the log. I know you said you were holding, but this also goes for anyone else who might have reboots.
Click to expand...
That worked! My phone crashed again a few minutes ago, and now the log showed up. Uploading it, good luck, thank you
 

Attachments

andMego said:
That worked! My phone crashed again a few minutes ago, and now the log showed up. Uploading it, good luck, thank you
Click to expand...
Cool. I'll try to get something useful from it, but I'm not sure how far I can get. I've trying to fix some merge issues for the last two months, so my code no longer reflects the last build I released.
 
Thanks to OP, this ROM brought my Volt back to life, but it has an issue with WiFi that goes off few minutes after screen lock/off and I can't receive notifications since I'm 99% of the time on WiFi. I tried different battery mode settings but still the same, the only solution is to use an App to keep WiFi alive.
 
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.

The orientation can be changed by tweaking /etc/sensor/sensord_config_axis, but I haven't figured out the right combination that corrects the orientation.

I still recommend my previous build for day to day use

http://www.mediafire.com/file/4jz9un10iutbdyd/cm-13.0-20161105-UNOFFICIAL-x5.zip
1D2399A61213B2B32D2A55A82B504222
 
TDGlCah.png
 
You must log in or register to reply here.
Back
Top Bottom