Root Cyanogenmod 13 Beta 1

[DeltaXzombies]

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.

Its not buffering, I have decent WiFi (25 Mbps) at home so 720p videos never buffer but I may have found a solution, I'm not sure if it will work but if you change the following build.prop lines to "false" then it will fix the problem.
I'm on CM11 so I can't test, if anyone can than let me know

 

[SebasHacks]

Oh, and green camera issue here as well, though video recording has been fixed for me now. Let me test some of those things for you as well, if you want.

 

[jhofseth]

I want overclock, so I will flash this ROM and create a boot image with @Bad_MOFO_33's KoolAid kernel. Boot images need to be 'bumped' as some have discovered; you can't simply flash a new kernel, you have to create a new boot image that includes 'dtb' and then use the python2 script, openbump. I don't know if the KoolAid kernel will work 100% with CM13, but it's worth a shot for overclock.

--UPDATE--
KoolAid Kernel does not work with CM13, so either source files of the CM13 kernel would need to be modified to compile OC kernel or a different compatible OC kernel would be needed.

I'm reverting to my backed up 6/28/2015 @Bad_MOFO_33's CM12.1 unofficial beta install, because I want the overclock. Regardless, good job with CM13, @whoshotjr2006.

 

[andMego]

Deleted

 

[RICHRX]

IM new to here but i had this phone for some time, and i been in this form a long time just trying out the different roms and i only made this account to thankyou for this rom that somehoe fixed the audio proplem that i was having (Plug Headphone but all the music go out from the speaker) IM GLAD THAT WAS FIXED im willing to countinue to try out more stuff of rom ( i been trying them out for half a year or more) and i see that youtube is able to pllay in 480p just like stock rom and i got the camera OK.
Srry for any bad grammer of mine (I Speak Spanish)

 

[dvdavid888]

I want overclock, so I will flash this ROM and create a boot image with @Bad_MOFO_33's KoolAid kernel. Boot images need to be 'bumped' as some have discovered; you can't simply flash a new kernel, you have to create a new boot image that includes 'dtb' and then use the python2 script, openbump. I don't know if the KoolAid kernel will work 100% with CM13, but it's worth a shot for overclock.

--UPDATE--
KoolAid Kernel does not work with CM13, so either source files of the CM13 kernel would need to be modified to compile OC kernel or a different compatible OC kernel would be needed.

I'm reverting to my backed up 6/28/2015 @Bad_MOFO_33's CM12.1 unofficial beta install, because I want the overclock. Regardless, good job with CM13, @whoshotjr2006.

I thought overclocking was a placebo it never worked

 

[jhofseth]

I thought overclocking was a placebo it never worked

That's what some said about our CPU until we tested @Bad_MOFO_33's CM12.1 unofficial beta at stock settings and max overclock freq. I posted screenshots of the benchmark differences in his thread a while back. Currently, I use the 6/28/2015 CM12.1 unofficial beta build, but would switch to CM13 when/if we have an OC kernel.

From a related previous post of mine: "Dunno, Bad_MOFO_33's CM12 is 1600MHz. If you use SetCPU for Root Users to toggle between 1200 and 1600MHz, there is a measurable difference in CPU performance on many different CPU benchmarks. I posted screenshots of benchmark difference in the CM12 thread.

On CM12 thread page #23 I posted screenshots and wrote:
"bad_MOFO_33, it appears there is a difference in performance between OC 1.6 and non-OC 1.2:
(SetCPU for Root Users used to toggle between 1.2 and 1.6)

Quadrant OC 1.6=total 5,284, CPU 18,089
Quadrant non-OC 1.2=total 5,031 CPU 16,771
Pi to 10,000,000 digits OC 1.6=64.148s
Pi to 10,000,000 digits non-OC 1.2=66.271s

Screenshots of these and additional tests are attached. The slower Pi to 10,000,000 test is the one at 1.2GHz, the app just does not show the change explicitly--but some of the others do (just ignore 1.6GHz on slower of two pi tests). Good job, bad_MOFO_33!"
(2 screenshots re-posted here, rest on pg.23)"
OC 1.6

non-OC 1.2

 

[andMego]

So today I flashed cm13. The no Sim card icon in the status bar comes back every time I reboot and only goes away after turning airplane mode off. While restoring apps with titanium backup my phone started boot looping. After multiple clean flashes I figured out it starts boot looping while restoring Spotify app+data. Titanium force closed on me a couple times. Changing the vibrator intensity in sound settings doesn't work.

 

[andMego]

Sometimes when I press back to leave an app it closes and then says that it force closed. The status bar doesn't always color properly (like in picture it should be green but its black)

 

[DeltaXzombies]

Sometimes when I press back to leave an app it closes and then says that it force closed. The status bar doesn't always color properly (like in picture it should be green but its black)

Some apps dont use the API that makes the status bar color change.

 

[whoshotjr2006]

Sometimes when I press back to leave an app it closes and then says that it force closed. The status bar doesn't always color properly (like in picture it should be green but its black)

Which app? Not all apps are upgraded yet to support the new permissions model in marshmallow. That could be the cause, hard telling. Try to catch a logcat when it force closes.

I'm still thinking about this ROM by the way guys. Life and school are kicking my butt right now, and this sinus infection isn't helping either. I'll get back to devving when I get a chance.

 

[che_edgar]

Which app? Not all apps are upgraded yet to support the new permissions model in marshmallow. That could be the cause, hard telling. Try to catch a logcat when it force closes.

I'm still thinking about this ROM by the way guys. Life and school are kicking my butt right now, and this sinus infection isn't helping either. I'll get back to devving when I get a chance.

Finals, at least for me. I'll be able to mess around more with the phone in around 2 weeks. [emoji25]

 

[BiggieStylin]

Just wanted to say... GREAT work on this ROM. I've using it for the past day or so and don't really have any issues. My data and LTE was a bit flaky when I first flashed the ROM, but once I rebooted a few times everything seemed to simmer down and start working smoothly. The only real issue I've noticed so far is the compass quick toggle doesn't work, just gets stuck on "Initializing" and never does anything. I'll update again once I've had a bit more time using the phone and see if I notice anything else.

Also worth noting... I'm in the IRC channel (BigE) if you ever want to ping me to test things. I'm mostly active while I'm work 9am-5pm CST, but I'm around some evenings too and I'd be happy to help in any way I can.

 

[andMego]

That compass not working happens to me also. Only noticed it yesterday

 

[spock1104]

I figured out most of the app crashes, especially the setup wizard and play services crashes if you install gapps after first boot. Because the apps were installed outside of the normal install procedure or first boot, the app's permissions weren't set up. Between the setup wizard crashes you'll want to pull down the notification center and go to settings, then go to apps, show system apps, go to setup wizard (the non-cm one), permissions, turn on both permissions, exit, and reboot. Now the phone shouldn't be frustrating to use any more, and you can go back and set the play services permissions and reboot again.

 

[Don_Kiraly]

Hey guys, I tried to make some modifications to @whoshotjr2006 build and I ran into an error when flashing. I haven't ever done this before and I got it to flash after fixing the updater-script a little, but I can't seem to figure this one out. Couldn't find much about this online so I was hoping someone might be able to help me out.

It says:

Veryifying the updated system image. . .
system partition has unexpected contents after OTA update
E: Error executing updater binary in zip '/externel_sd/cm-13.0-testbuild.zip'
Error flashing zip '/external_sd/cm-13.0-testbuild.zip'. . .
. . . done

 

[whoshotjr2006]

Hey guys, I tried to make some modifications to @whoshotjr2006 build and I ran into an error when flashing. I haven't ever done this before and I got it to flash after fixing the updater-script a little, but I can't seem to figure this one out. Couldn't find much about this online so I was hoping someone might be able to help me out.

It says:

Veryifying the updated system image. . .
system partition has unexpected contents after OTA update
E: Error executing updater binary in zip '/externel_sd/cm-13.0-testbuild.zip'
Error flashing zip '/external_sd/cm-13.0-testbuild.zip'. . .
. . . done

it looks like you missed something in the steps of unpacking the image, modifying it and then repacking the build. there are some good guides on xda on how to do this the right way that i cant really link to off the top of my head but a simple google search for "unpack lollipop system img" should net you the results your looking for.

 

[whoshotjr2006]

here is the newest local_manifest.xml for building cm13, has everything you should need.

https://github.com/touchpro/android_local_manifest/tree/cm-13.0

 

[ShapeShifter499]

@whoshotjr2006 How should I go about enabling init.d support on this rom?

 

[whoshotjr2006]

@whoshotjr2006 How should I go about enabling init.d support on this rom?

should already have it, thats what gets the home ring led to stop pulsing, an init.d script

 

[ShapeShifter499]

should already have it, thats what gets the home ring led to stop pulsing, an init.d script

Must be my script then? Some apps do not like to use adopted storage, includes apps that never had app2sd enabled. However Link2SD seems to be able to see and make use of the adopted storage if I bind mount (or find another way to mount) the adopted storage to /data/sdext2/ I just cannot seem to get the script to mount it early enough before Link2SD runs. The script below is saved as /system/etc/init.d/99link2sd

#!/system/bin/sh

# Script should bind mount the adopted storage mounted in /mnt/expand to the folder /data/sdext2 so Link2SD can find it.

# Wait for adopted storage to mount

while [ ! -d /mnt/expand/<UUIDofSD>/sdext2 ]
  do
  sleep 10
  done

# Wait for /data to mount and look for sdext2

while [ ! -d /data/sdext2 ]
  do
  sleep 10
  done

# Bind /mnt/expand/<UUIDofSD>/sdext2 to /data/sdext2

mount -o bind /mnt/expand/<UUIDofSD>/sdext2 /data/sdext2

 

[whoshotjr2006]

sorry i have not been very active guys, its finals week and i completely screwed something up on my end to where every build i make has borked usb functions and broken vibration. i have tried to roll back to clean sources multiple times to no avail, even rolling all the way back to spock1104's sources in the beginning with no luck. not sure what i did, but i can say for sure that it was spectacular lol.

i figured out quick remote by the way. i modified nikita's/quarx's irrc patch to work around our need for bumping the boot image and will post the solution soon once i figure out the best way to roll it out. it will just be a flashable zip like they provide to flash after flashing rom, gapps, and apn zip.

 

[whoshotjr2006]

ill add this to the op, but to get irrc (quickremote) working do the following:

flash this: http://forum.xda-developers.com/showpost.php?p=64957882&postcount=678 in recovery (thanks to Nikita and Quarx for making this)

then flash forirrc.img https://www.androidfilehost.com/?fid=24531035584725244 in recovery also (when choosing a zip file, down in the bottom right corner it says img, click that and select the forirrc.img to flash and tell it to flash to boot.)

reboot and enjoy. there are not a lot of makers and vendors supported yet but my lg bluray player worked just fine.

 

[che_edgar]

ill add this to the op, but to get irrc (quickremote) working do the following:

flash this: http://forum.xda-developers.com/showpost.php?p=64957882&postcount=678 in recovery (thanks to Nikita and Quarx for making this)

then flash forirrc.img https://www.androidfilehost.com/?fid=24531035584725244 in recovery also (when choosing a zip file, down in the bottom right corner it says img, click that and select the forirrc.img to flash and tell it to flash to boot.)

reboot and enjoy. there are not a lot of makers and vendors supported yet but my lg bluray player worked just fine.

Nice Jr., it flashed with no problem. Thanks a lot for this.

**Do you know if we can add more manufacturer's?

 

[dvdavid888]

Will this work for a 4.4.4 build? And thank you to all the dev's for your hard work