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

Root Cyanogenmod 13 Beta 1

whoshotjr2006

Android Enthusiast
Jul 31, 2012
680
1,252
Ohio
READ EVERYTHING BEFORE YOU CONTINUE ANY FURTHER!!!! DEV INFO IS IN 2ND POST.

NEWS:
First build in this post. Read everything before you continue. Thought we needed a dedicated rom dev thread.

Credits:
Cyanogenmod
Quarx2k
NikitaProAndroid
vm03
@Bad_MOFO_33
@spock1104
@whoshotjr2006

CHANGELOG:
042516: First build in this post. I used spock1104 and bad_mofo_33 trees as a starting point, then added in my own bugfixes.

DISCLAIMER:
i do not force you to flash these roms. what you do is on you. ill try to help you, but do not blame me for anything, especially if something goes wrong. you know the risk, and if you dont know or understand something, then dont flash this rom.

TAKE A GOOD BACKUP WITH TWRP BEFORE FLASHING!

RECOMMENDED RECOVERY:
TWRP lollipop link from bad_mofo_33:
https://www.androidfilehost.com/?fid=24052804347771339

Working:
Anything that is not listed below

half working:
ril functions (mms not working over lte yet)
green camera tint for some

not working:
compass
button backlights
nfc
you tell me

NOTE: Get a gps lock in stock rom or whichever rom you had before with working gps before you flash this. This is a quirk with many qcom based phones, if you dont get a lock before you flash this your gps probably wont work.

Flash the rom, THEN FLASH GAPPS WITH IT AT TIME OF INSTALLATION (marshmallow gapps, i recommend opengapps 6.0 pico) and then flash either the Virgin or Boost apn fix below.

Thanks to @MopedRyder for both:

ChangeofJinzo's Apn fix:
http://androidforums.com/threads/al...-lg-volt-on-cm13-cm12-other-roms-too.1024839/

To get quickremote working: http://androidforums.com/threads/cyanogenmod-13-beta-1.1023879/page-2#post-7288774

Rom Download Link:
https://www.androidfilehost.com/?fid=24499762636008554
 
Last edited:
Relevant dev info:

the relevant repos you need from me (based on Quarx2k's W7 source) are:
device: https://github.com/touchpro/android_device_lge_x5 (master branch)
device:https://github.com/touchpro/android_device_lge_msm8226-common
vendor: https://github.com/touchpro/vendor_lge_x5 (cm-13.0 branch)

you also need the msm8226-common vendor from spock:
vendor: https://github.com/spock1104/proprietary_vendor_lge

and kernel based on @spock1104:
https://github.com/spock1104/android_kernel_lge_msm8226
 
Upvote 0
You probably should link to the actual twrp 2.8.7.0 not just the thread since it's not on the first page or anything (link to that specific post or the download link)
EDIT
As in http://androidforums.com/index.php?posts/7022470 or https://www.androidfilehost.com/?fid=24052804347771339

fixed

I have green tint on one of mine, what's good?

im gonna want you to run some tests for me after a bit, gonna try different kernel configs and see what happens.
 
Upvote 0
Seems TWRP v2.8.7.0 (and maybe the one we have for TWRP v3.0.0) is incompatible with the "unified storage" a.k.a "adaptive storage". I just had to hard reboot by holding power to get out of TWRP as it just stuck at the TWRP loading screen.

I just recommended the old twrp since I have had a bunch of issues with twrp 3 going into bootloop hell. When I get time I'll add a link and a disclaimer about adaptive storage and twrp to the OP. Thanks for reporting this.
 
Upvote 0
Just verified the current LG Volt build of TWRP v3.0.0 sort of works but I cannot view any of the files on device but rebooting back to OS confirms the files are there. Plus the unknown reason for random bootloops make this even more iffy. There might need to be some kind of code tweaking as the official TWRP changelog mentions that v3.0.0 supports adaptive storage for select devices. http://www.xda-developers.com/twrp-3-0-0-has-arrived/

EDIT: Temporary workaround that worked for me, use app "flashify" from Play Store and have it copy whatever you want to flash to a safe location. This puts whatever file you want to flash in the /cache/ which TWRP v3.0.0 can see and gets around the current issue for people using "adaptive storage". Beware of bootloops though and know how to recover if it happens.
 
Last edited:
Upvote 0
I never made a logcat but hopefully I did it right, here's a logcat I took while watching a YouTube video at 720p
Video I watched (if needed)-https://youtu.be/B0IMT9uA434
I didn't notice any stuttering of the video at all

720p Youtube? Are you using OGMods Youtube? Regular Google Youtube app gives me 480p which works great on this rom.

EDIT: It is OGMods, I see messages referencing it being loaded in your logcat
 
Upvote 0
@whoshotjr2006, is this ROM overclocked like CM 12.1 unofficial beta for the volt? @Bad_MOFO_33 had his CM 12.1 unofficial beta with 192MHz min and 1593MHz max--at least for the build I currently use. Also, does FM Radio work yet? Thanks in advance! :)

Not overclocked from what I can tell and yes the FM radio works fine.
 
  • Like
Reactions: jhofseth
Upvote 0
I clean flashed the first build but I've been dirty flashing since then. I'm not sure if that's the reason I can't record or not still but I did capture a log while trying to record.

Full log attached.

Just took a quick look & found this:
Code:
04-25 16:44:54.479 E/CAM_VideoModule( 5810): stop fail
04-25 16:44:54.479 E/CAM_VideoModule( 5810): java.lang.RuntimeException: stop failed.
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at android.media.MediaRecorder.stop(Native Method)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at com.android.camera.VideoModule.stopVideoRecording(VideoModule.java:1997)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at com.android.camera.VideoModule.onError(VideoModule.java:1792)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at android.media.MediaRecorder$EventHandler.handleMessage(MediaRecorder.java:1049)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at android.os.Handler.dispatchMessage(Handler.java:102)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at android.os.Looper.loop(Looper.java:148)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at android.app.ActivityThread.main(ActivityThread.java:5461)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at java.lang.reflect.Method.invoke(Native Method)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
04-25 16:44:54.479 E/CAM_VideoModule( 5810):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
04-25 16:44:54.479 V/CAM_VideoModule( 5810): Deleting video /storage/emulated/0/DCIM/Camera/VID_20160425_164453.mp4.tmp

This was also captured during the recording process:
Code:
04-25 16:44:51.841 E/NFC  ( 5810): NFC service dead - attempting to recover
04-25 16:44:51.841 E/NFC  ( 5810): android.os.DeadObjectException
04-25 16:44:51.841 E/NFC  ( 5810):    at android.os.BinderProxy.transactNative(Native Method)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.os.BinderProxy.transact(Binder.java:503)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.nfc.INfcAdapter$Stub$Proxy.setAppCallback(INfcAdapter.java:501)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.nfc.NfcActivityManager.requestNfcServiceCallback(NfcActivityManager.java:339)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.nfc.NfcActivityManager.onActivityResumed(NfcActivityManager.java:475)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.Application.dispatchActivityResumed(Application.java:214)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.Activity.onResume(Activity.java:1211)
04-25 16:44:51.841 E/NFC  ( 5810):    at com.android.camera.CameraActivity.onResume(CameraActivity.java:1650)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1259)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.Activity.performResume(Activity.java:6327)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3126)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3168)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1407)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.os.Handler.dispatchMessage(Handler.java:102)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.os.Looper.loop(Looper.java:148)
04-25 16:44:51.841 E/NFC  ( 5810):    at android.app.ActivityThread.main(ActivityThread.java:5461)
04-25 16:44:51.841 E/NFC  ( 5810):    at java.lang.reflect.Method.invoke(Native Method)
04-25 16:44:51.841 E/NFC  ( 5810):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
04-25 16:44:51.841 E/NFC  ( 5810):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
 

Attachments

  • 2016-04-25-16-44-45.txt
    240.4 KB · Views: 177
Upvote 0
So when I use 720P it seems to lag and stutter every 15 seconds or so but when I use 480p it rarely lags, every few videos it may lag a few times but not as much as 720
I would get a logcat but I'm back on CM11

Lag? Are you sure it wasn't buffering? Everything I've tried so far works like a treat. Couple of games like GTA3 from the Play Store work fine. OGMods YouTube hasn't stuttered at all for me and I can view videos up to 1080p but it throws a error at 1440p which makes sense (attached screenshot). Apps that didn't play video at all now do like Crunchyroll (yes anime lol). NFC, OTG, and the backlight on the touch buttons are the only things I find not working so far in the ROM.
 

Attachments

  • Screenshot_20160426-081939.png
    Screenshot_20160426-081939.png
    130.8 KB · Views: 431
  • Like
Reactions: DeltaXzombies
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones