• 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

When playing asphalt nitro the phone crashes (kinda like soft reboot). Here are the logs. Any idea what went wrong?
 

Attachments

Last edited:
andMego said:
When playing asphalt nitro the phone crashes (kinda like soft reboot). Here are the logs. Any idea what went wrong?
Click to expand...

Looks like maybe it was trying to play a video that the phone didn't like. First it complains about a DRM plugin and then there's an SELINUX audit denial

Code: 
12-04 13:51:16.882 E/Drm     ( 3755): Failed to find drm plugin
12-04 13:51:16.897 W/DG.WV   ( 6025): Widevine DRM not supported on this device
12-04 13:51:16.897 W/DG.WV   ( 6025): android.media.UnsupportedSchemeException: Failed to instantiate drm object.
12-04 13:51:16.897 W/DG.WV   ( 6025):    at android.media.MediaDrm.native_setup(Native Method)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at android.media.MediaDrm.<init>(MediaDrm.java:215)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at oam.a(:com.google.android.gms:119)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at nxf.run(:com.google.android.gms:1092)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at kyl.run(:com.google.android.gms:450)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at lco.run(:com.google.android.gms:17)
12-04 13:51:16.897 W/DG.WV   ( 6025):    at java.lang.Thread.run(Thread.java:818)
12-04 13:51:16.975 V/SysLog  ( 5664): Path: /storage/emulated/0/SysLog/2016-12-04_13.51/
12-04 13:51:17.014 V/SysLog  ( 5664): Done grabbing logs
12-04 13:51:17.053 D/su      ( 6056): su invoked.
12-04 13:51:17.053 D/su      ( 6056): starting daemon client 10083 10083
12-04 13:51:17.058 D/su      ( 6058): remote pid: 6056
12-04 13:51:17.058 D/su      ( 6058): remote pts_slave:
12-04 13:51:17.059 D/su      ( 6058): waiting for child exit
12-04 13:51:17.059 D/su      ( 6060): su invoked.
12-04 13:51:17.060 E/su      ( 6060): SU from: u0_a83
12-04 13:51:17.060 D/su      ( 6060): Checking whether app [uid:10083, pkgName: com.tortel.syslog] is allowed to be root
12-04 13:51:17.062 D/su      ( 6060): Privilege elevation allowed by appops
12-04 13:51:17.062 D/su      ( 6060): Allowing via appops.
12-04 13:51:17.062 D/su      ( 6060): 10083 /system/bin/app_process32 executing 0 /system/bin/sh using binary /system/bin/sh : sh
12-04 13:51:17.063 D/su      ( 6060): Waiting for pid 6061.
12-04 13:51:17.063 I/SuControllerImpl( 4304): Got change
12-04 13:51:17.094 I/art     ( 5664): Background sticky concurrent mark sweep GC freed 24794(1425KB) AllocSpace objects, 4(80KB) LOS objects, 33% free, 4MB/7MB, paused 5.254ms total 79.630ms
12-04 13:51:17.565 E/Drm     ( 3755): Failed to find drm plugin
12-04 13:51:17.608 I/Binder_2( 6037): type=1400 audit(0.0:9648): avc: denied { read } for name="/" dev="tmpfs" ino=6211 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=dir permissive=1
12-04 13:51:17.608 I/Binder_2( 6037): type=1400 audit(0.0:9649): avc: denied { open } for name="/" dev="tmpfs" ino=6211 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=dir permissive=1
 
spock1104 said:
Looks like maybe it was trying to play a video that the phone didn't like. First it complains about a DRM plugin and then there's an SELINUX audit denial
Click to expand...
I restricted cellular data access of the game in data usage since when it connects it says I need to update and won't let me play, and also to block the ads it shows, could that be why?
 
andMego said:
I restricted cellular data access of the game in data usage since when it connects it says I need to update and won't let me play, and also to block the ads it shows, could that be why?
Click to expand...
There was also a network connectivity complaint in the log right before it, so could very well be.

I did check through the kernel logs and didn't see anything suspicious there.
 
Hey, i was taking a look for a new rom to try and help out with before i get my new phone. I wanted to try this one but i couldn't figure out where the latest build was. Do you think you can point me in the right direction? Is it this one?
ShapeShifter499 said:
I have a working build! Tested it myself, OTG works and I synced in your changes that enabled the Gello Browser, everything but IR and NFC work. This makes use of the stock msm_otg.c from stock source. Download below.

cm-13.0-20160818-UNOFFICIAL-x5.zip
md5sum: 1360ce9f183aa82d9bbb3ee7b1264a67

https://www.androidfilehost.com/?fid=24651430732236256


@spock1104 What sort of driver changes?
Click to expand...
 
lilggamegenuis said:
Hey, i was taking a look for a new rom to try and help out with before i get my new phone. I wanted to try this one but i couldn't figure out where the latest build was. Do you think you can point me in the right direction? Is it this one?
Click to expand...
spock1104 said:
New build, enabled OTG. My earlier issue was in fstab.

Thanks to @ShapeShifter499

http://www.mediafire.com/download/b39ptx5sgu6u9iu/cm-13.0-20160819-UNOFFICIAL-x5.zip
MD5: 46F47A810BDD242BAEF480509517D256

I'm using a different OTG driver, if anyone gets to use both let me know how the two builds compare. I did see some code suggesting that the OTG power drain bug may have been fixed.
Click to expand...
This is the latest stable one (there is a newer one that the proximity doesn't work but nfc does, don't remember what else is affected).
 
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.

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
Click to expand...
This is the newest one (NFC mostly works in it).
 
If/when an update is released would I be able to just flash it over my current setup or would I have I to wipe then flash
 
HOLY HELL months of kludging and I finally get a working TWRP image! Had to compile from CM sources and get busybox to compile. Not fun. I'll also make a new thread. Let's test the heck out of this thing, if it's working right then we can switch the phone to use F2FS and gain a little more speed.

http://www.mediafire.com/file/4dsyvb5d36csp5e/twrp_302_volt.img
DB280F6D9962D88BBC8765F427452B2B
 
okay, I'm on the latest build, most recent TWRP, using F2FS and I just have to say, amazing. simply amazing. great work on all of this, it really gives the phone a good boost. I hope you can get the orientation fixed, but as is, it's not hard to swap between the modes when needed, so it's really not a big deal. thanks again for all your hard work. it really makes my life much more sane when I'm using this phone as my primary!
 
spock1104 said:
New build, enabled OTG. My earlier issue was in fstab.

Thanks to @ShapeShifter499

http://www.mediafire.com/download/b39ptx5sgu6u9iu/cm-13.0-20160819-UNOFFICIAL-x5.zip
MD5: 46F47A810BDD242BAEF480509517D256

I'm using a different OTG driver, if anyone gets to use both let me know how the two builds compare. I did see some code suggesting that the OTG power drain bug may have been fixed.
Click to expand...

This build probably needs its own thread for more attention. Been using it for months and it has been extremely stable. The links to it are buried in the middle of this thread and limits the number of people who would find it better than their current ROM.
 
You must log in or register to reply here.
Back
Top Bottom