yashsingh1/xdaforums huggingface dataset:
[Motorola Droid Bionic] Oggie7797:
OctOs for targa, will build for other OMAP4 devices too, building Spyder as I type this.
[Motorola Droid Bionic] stargo:
Hi,

I have just uploaded new CM 12.0 builds for the OMAP4 devices which contain SELinux changes.

You have to do a manual fix for your current system to continue working without going through a wipe:

Edit: This is only necessary when updating from 2014-01-14 or 2014-01-15 as they include a commit which broke SELinux handling and causes unlabeled files on /data to appear. Upgrading from earlier builds is fine.

Due to SELinux changes, you have to relabel your data-partition on the first boot of a ROM built after 2014-01-17 when upgrading from a ROM from before that date. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) (do this before installing the new rom and try to access your device with "adb shell" from your PC to make sure you can get a shell).

After the system has booted up and is at the lockscreen, execute the following in an "adb shell" session:

su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'

I'm sorry that this can't be integrated into the ROM directly and has to be done manually.

This has been tested on maserati and umts_spyder and should also work on spyder and targa.

Cheers,

Michael
[Motorola Droid Bionic] Oggie7797:
Thanks [MENTION=3457922]stargo[/MENTION] for bringing our OMAP4 devices to life :) if I may ask, when did you make these commits? I sync'd up to build OctOs around 1am CST. Lol thanks again for everything :)
[Motorola Droid Bionic] stargo:
The commit which forces you to relabel everything was this one:

http://review.cyanogenmod.org/#/c/85759/

Prior to that we only had a subset of SELinux enabled, which caused /data/data (and a few other places) to remain unlabeled...

I'm also pretty sure, that you want this commit:

http://review.cyanogenmod.org/#/c/85839/

EDIT: Actually, if you have booted an image which includes http://review.cyanogenmod.org/#/c/82838/ but not my fix http://review.cyanogenmod.org/#/c/85759/ you have to relabel, as the first commit actually disables SELinux and booting then causes unlabeled files on /data to appear...

Cheers,

Michael
[Motorola Droid Bionic] Oggie7797:
I just went ahead and built clean with a fresh sync of your repos, thanks bud :)
[Motorola Droid Bionic] Oggie7797:
[MENTION=3457922]stargo[/MENTION] can you please edit default.prop for targa to reflect the following?:

Original line:

ro.telephony.default_network=10

New:

ro.telephony.default_network=6

^this will "fix" the APN/LTE issue and make LTE a lil more stable for us. Original settings default to global and screws with our CDMA Verizon stuff. I'm not the greatest with git commands so I don't feel like forking and pushing and asking for a pull request. Thanks! :)
[Motorola Droid Bionic] ShadyDreamer:
Isn't 6 EvDO only? 8 is what the stock rom uses, which is for LTE/EvDO/CDMA mode on that.
[Motorola Droid Bionic] Oggie7797:
Yes 8 is for LTE but 6 is the only setting that I have found that will allow you to boot into setup without any phone fc and will auto connect to 3g. Every other setting will either connect to 1x or will fc.
[Motorola Droid Bionic] stargo:
Hi,

With the help of [MENTION=1070688]joojoobee666[/MENTION] I think we have found the real fix: http://review.cyanogenmod.org/#/c/86329/1 :)

Can you please check if this also fixes it for you?

I'm also in the process of rebuilding todays unofficial builds and will upload them to a test-directory later.

EDIT: Uploaded to: http://droid.cs.fau.de/cm-12.0/.test/

Thanks & regards,

Michael
[Motorola Droid Bionic] Oggie7797:
Thanks guys! This has been the biggest turnoff for LP so far for me... I don't have my lappy on hand but I'll be sure to check into that when I do. Thanks! :)
[Motorola Droid Bionic] rfresh:
Stargo's latest build for 1/24/2015 has fixed the LTE DATA issue, thanks so much

But could this ROM be more optimized? it is still laggy and running a little slower.
[Motorola Droid Bionic] Oggie7797:
Enable ksm inside of build.prop other than that, keep recents clear and wipe cache once a week. LP in and of itself is gonna be buggy.
[Motorola Droid Bionic] rfresh:
How can I modify the build.prop file since the rom is not rooted? where is the line I need to change?
[Motorola Droid Bionic] Bobcus Leper:
ro.ksm.default=0
[Motorola Droid Bionic] DrJwC:
Root is turned on in developer options [emoji6]
[Motorola Droid Bionic] Oggie7797:
Flash supersu.zip 2.45 is current. Better root management than stock cm12 "privacy guard"
[Motorola Droid Bionic] stargo:
Starting with the next nightlies-cycle, the Bionic should receive official CM12.0 builds :)
[Motorola Droid Bionic] Oggie7797:
Woohoo thanks man for all you've done!!! :D
[Motorola Droid Bionic] ax562:
Droid Bionic CM12 2/1/15 build fresh out the oven. Get it while it's hot! Thanks to [MENTION=3457922]stargo[/MENTION] [MENTION=5660618]Oggie7797[/MENTION] [MENTION=4523997]alteredlikeness[/MENTION] !

https://www.mediafire.com/?3pmvz8r9b4euw32
[Motorola Droid Bionic] Oggie7797:
Good job bud! Glad you got the manifest fixed. Mines not exactly right for cm12 since OctOs has there's setup for shortcuts. cm=CyanogenMod and tm=the muppets drove me nuts when porting till I figured that out.
[Motorola Droid Bionic] The Doctor04:
And so it begins......Time to flash

http://get.cm/get/mLC
[Motorola Droid Bionic] pairdime:
Tried to install it to rom-slot2 and it failed, didn't have time to figure out why. SafeStrap 3.73 TWRP 2.7.0.0
[Motorola Droid Bionic] Oggie7797:
^read the freaking op.

Wrong safestrap. You need the new one with SELINUX to flash LP ROMs....
[Motorola Droid Bionic] pairdime:
Is it this one? Will it brick my CM11 slot? http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/Safestrap/

edit: installed that recovery 3.75 (view the readme) and my old slot is fine, for anyone wondering.

Well I managed to get cm-12-20150202-NIGHTLY-targa.zip installed, but PA gapps fails now (as recommended in OP), so I am stuck once again :P

edit2: booted into CM12 and went through the intros, rebooted and tried installing PAgapps once again, this time it worked as expected.

Getting LTE coverage and testing this out now. Should someone start an official CM12 thread, rather than this unofficial one?

edit3: 02-02 build seems to be running great for me, haven't run into any issues... just a little slowness here and there. With just some quick testing calls/LTE/wifi/GPS/camera/bluetooth/wireless tether/gapps/google sync all seem to be working fine. Going to try using this as my daily driver, will report on the battery usage in a day or two.

Nice work everyone involved :good: have run into zero issues so far, and zero bugginess.

edit4: after a day of usage this is mostly good to go. Very good battery usage, better than CM11 M12 anyway. Had some random issues as would be expected from a nightly but nothing clearly broken/show-stopping:

A few occurrences of extreme lag. For example, Google Now homescreen taking 15-20+ seconds to repopulate widgets. Seemed like a GC issue, as closing open apps and/or clearing the caches seemed to make the phone usable again.

Got a random hard reset after plugging in my charger once, didn't get a log sorry.

A couple force closes, one of a random app, and once of settings, could be theme engine related. Not a big deal as it only happened twice total and was not repeating.

Noticed repeat screen wakeup after a long period of sleep and then an alarm. Screen would light up the lockscreen, go out, light up again, and so on. Seemed like unlocking the phone and then locking it again fixed the issue. Something like this could really kill your standby battery, but I haven't seen it happen since.

LTE connectivity seems maybe a tiny bit spotty? Nothing that reconnecting the network won't fix. One time stuck in 3G when it shouldn't be, one time couldn't connect until I manually reset it after phone boot, small things like that.

Slow LTE speeds just in general. Was averaging around 5mbit speeds when otherwise I would get 20mbit+ in CM11. For example just tested now and got 4.0 mbps down yet 9.5 mbps up.

More often than not though a nice, responsive experience.
[Motorola Droid Bionic] DrJwC:
I had none of the install problems pairdime had. Fresh maxed out slot one, safestrap 3.75, installed flawlessly with PA gapps 0202. Like pairdime I have noticed 4g is probably really 1x, it's definitely not 4g speeds. My wifi connection is a lot faster though. Otherwise this is the best first build ever. Thx everyone
[Motorola Droid Bionic] Oggie7797:
Updated OP with links and official status.
[Motorola Droid Bionic] pairdime:
Out of curiosity I went back to CM11 M12 and ran a speed test. Strangely it gave me the same slow speeds (6 down, 12 up).

Then I noticed the README of safestrap 3.75 says: (source http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/Safestrap/README.txt )

"If you enter recovery, the device will now also execute a new kernel, so you will get the kexec-vibrate at this point, too."

I wonder if this new kernel is causing LTE speed problems? Not what I was expecting when I simply wanted SELinux support.

Edit: downgraded to safestrap 3.73 just to see, then ran a speedtest from CM11, same slow speeds... kind of confused what is the cause now :confused::crying:
[Motorola Droid Bionic] The Doctor04:
Have you tired stock jelly bean to see what your speeds are there? If you are getting slow speeds there too, then it could be your call area. Maybe Verizon has an outage in your area?
[Motorola Droid Bionic] Oggie7797:
Safestrap, regardless of selinux or not, executes a kexec kernel. That is how you are able to flash roms in it so it has nothing to do with LTE. You probably have used too much data and are being throttled or you simply live in a bad area.
[Motorola Droid Bionic] sd_shadow:
or local bandwidth is simply maxed out, because too many devices streaming netflix at the time.
[Motorola Droid Bionic] DrJwC:
1. I have an unlimited data plan.. One reason why I am still using my bionic.

2. Indicated connection is 4g, but I noticed a lag starting downloads and while browsing and so I ran a connection speed test

3. My area has a really good 4g service

4. Speed test was about half of what I can get in kit kit cm 11

For note : it seems to be a handshake problem

I have already set the preferred network from global to lte.

Anyone having a problem with notification tones? I cannot get a tone even when just trying different notification tones in settings /sounds! Any ideas?
[Motorola Droid Bionic] Oggie7797:
I didn't have any issues with speed on my bionic. I also have unlimited data grandfathered from Alltel. I now have a droid4 and gave my dad the bionic so I can't exactly test the newest build as far as speed, since he has it stock tweaked jb.
[Motorola Droid Bionic] DrJwC:
I just updated to the latest nightly using the cm updater and it's all better. 4g is as fast as cm 11. Must have been a weird download or install the first time.
[Motorola Droid Bionic] pairdime:
I too was able to debunk the LTE slowness I reported, wasn't sure if network or a previous nightly, but seems fine now.

The real issue I am having now in CM12 is the random severe lag. Talking like 15-20 seconds to reload my homescreen with all of 2 widgets, after opening just 1 or 2 apps. Also random LTE drops.
[Motorola Droid Bionic] kitcostantino:
Netflix

The newest Netflix didnt work on the 2.3.15 build, so im rockinghigh bit rate Netflix 2.4.1 with no issues. ;) Overall, LP runs well. Thank you OP and Stargo!!!
[Motorola Droid Bionic] DrJwC:
For me the Lag was caused by themes. It was not enough to set it to the default theme I had to remove all themes. Speed came back.
[Motorola Droid Bionic] antennaman1969:
I like it

I installed the first official nightly yesterday. I let it install everything overnight. Like Pairidime, I flashed the ROM, rebooted, then flashed full gapps. It worked like a charm. Thanks to [MENTION=5660618]Oggie7797[/MENTION] and [MENTION=3457922]stargo[/MENTION], as well as all who tested, reported, and complained patiently.
[Motorola Droid Bionic] platypoid:
new safestrap load

Hi,

I want to try out CM12 for my Bionic - have CM11 and all is well. I have no Sim card and everything has worked fine. But process for unloading old safestrap is boot into stock rom slot - okay do that but get keypad lock pad . I tried emergency dialer and various codes I read about and pushing corners but can't get past this screen. When I did a wipe and reboot for stock rom I can use press 4 corners trick to bypass sim card lock but then there is no safestrap, busybox, or Super user showing up in apps. I went back to slot one CM 11 and all is okay.

Anyone have any way to get past Sim card lock or do I have to find one to put in there ? I tried some old simcard from another type phone but it doesn't let me get past it either.

Thanks for any help !
[Motorola Droid Bionic] Oggie7797:
Su binary, busybox, and safestrap is still there since you wiped /data not /system. Download the safestrap version that you had and uninstall recovery (just open the apk in stock slot also delete cm11 slot) and then delete the apk, install new safestrap, install new recovery, and then everything else is the same as older kitkat roms.
[Motorola Droid Bionic] platypoid:
Thank you - that worked and I have CM12 installed but still getting it set up .
[Motorola Droid Bionic] pairdime:
Speed never came back for me. Does anyone have speeds comparable to CM11? Wondering if my dirty flashes since the first build left me with a nearly inoperable phone, or if CM12 just isn't well enough optimized for the Bionic yet.
[Motorola Droid Bionic] DrJwC:
CM12 is the fastest rom ever on my bionic, noticeably faster than cm11. I don't put much into benchmarks but scored a 3460 on quadrant, never saw over 2900 with cm11. I also have been dirty flashing since the first nightly using the updater. It does not play well with all apps. I had to remove chrome to phone as it seems to have a memory leak, and I cannot use chrome browser, but from the play store reviews chrome has major issues in lollipop on devices with lp stock roms. Look at apps you have installed. Maybe one or more isn't playing nice [emoji6]
[Motorola Droid Bionic] pairdime:
You are right, CM12 is fast after all, I ended up doing a clean install and after "settling out" with gapps/sync/etc it is at least as responsive as CM11. I wonder if it was a theme that had ruined the install or the wrong apps or what, but I will be making minimal modifications from here on out and hope that CM12 remains snappy. :fingers-crossed:
[Motorola Droid Bionic] Oggie7797:
Yea chrome beta on both targa and maserati are very glitchy on lollipop. I'm not willing to use aosp browser so I either deal with it or I grab the tablet or laptop. Also a couple games I play are by no means optimized for lollipop.
[Motorola Droid Bionic] coffee85:
I was experiencing a lot more lag on CM12 compared to Slimkat 9.0 I've been using. What's your guy's secret on getting good performance?

I gave CM 12 a shot, but I switched back to Slimkat after the 20150206 nightly build because the lag from switching between my home screen and apps was too much. Text messages were also intermittent after the last build I tried.

This was on a fresh install on a fresh slot. Could my problem have been caused by the amount of cache I used on the slot? I was running low on available space, so I had it set to around 400MB. Are you guys running custom kernels? I was also using the Slimrom gapps because the PA gapps failed to install.

Other than that I can't figure out why some people are getting good results and I'm getting such lackluster performance. I had zero widgets running and only the stock apps. I'm going to try it again in a few days and see if I notice an improvement, but for now CM 12 doesn't seem to be stable enough for use as a daily driver
[Motorola Droid Bionic] Oggie7797:
400mb is fine lol as long as you have the correct safestrap there is no reason for pa gapps to fail and no reason for you to have so much lagg. For a boost I enable ksm but even without it just keep recents clear and don't use a task killer apk like noobs do and you'll be fine. Sorry you're having issues because honestly, lollipop is awesome on our omap4 devices.
[Motorola Droid Bionic] coffee85:
Thanks for the response.

I am using Safestrap v3.75. I can't recall the exact error message I received while trying to install PA Gapps, but it failed. I know PA's Gapps was recommended with this ROM, just not sure exactly why other than it being really popular? Definitely not using a task killer app, like I said, I get lag with nothing other than the stock Apps installed. Maybe I'll give PA gapps another go.

Lollipop is awesome. The week of use I got out of it was really fun apart from it being slow. LP is very sleek and it's neat to see this OS running on our 3 1/2 year old phones! Props to everyone who made it possible.
[Motorola Droid Bionic] DrJwC:
Which gapps did you use? I used PA micro modular 5.0.1 rc3 and it installed perfectly using safestrap and installing at the same time as the rom
[Motorola Droid Bionic] Oggie7797:
As far as "why do you use pa gapps other than they're popular?" Goes...pa, slim, cm, (insert rom name here) doesn't matter.....gapps are simply that: they're google applications. The guy who does them simply slaps pa on them for whatever reason. The reason I ALWAYS suggest pa gapps is because it gives you options of how much you want whereas other gapp downloads from say aokp, will give you full gapps and a lot of it I simply declare as bloat. I always use nano pa gapps...has the basics amd if you want more you can just download them.

Btw [MENTION=4530833]DrJwC[/MENTION] sorry I meant to quote the other guy but I'm too lazy and tired to correct it from mobile :P
[Motorola Droid Bionic] coffee85:
I used pa_gapps-stock-5.0.1-RC3-20150201
[Motorola Droid Bionic] Oggie7797:
Read what I said 5 seconds before you lol try nano. Never do full....it failed because the system partition became full.
[Motorola Droid Bionic] pairdime:
I've had the same problem with 2 installs of CM12. Error code 70 -- not enough space. For some reason if you install CM12, boot into it, then reboot to recovery and install gapps it works. It is probably a problem with the detection in the PA gapps installer rather than the rom/recovery, is my guess.

As for your slowness issues, I had the same problem and could not resolve until I reflashed today. On CM12 2-08 and PA gapps 2-08 and it is great. I honestly think that during the initial builds there was some problem with the CM theme engine that caused these slowness issues, at least one other person in this thread reported problems with that. If you start off slow and don't install too much crap at once you will see the rom is very fast, hopefully in my case it will stay that way over time.

The slowness issues I had were very extreme, like 10+ seconds to load the home screen with no apps loaded -- this isn't the state of the speed of the rom, rather I somehow managed to configure it into that state and couldn't get out of it until reflashing. After giving it another go it is at least as fast as CM11, probably better honestly.
[Motorola Droid Bionic] coffee85:
Yeah, I read about someone (possibly you?) going through the initial boot up then back into recovery and installing PA gapps without problems, but at the time I had both Slim and PA gapps in my folder and Slim worked the first time.

I just downloaded the latest version of PA nano gapps and the latest CM12 nightly. Going to give it another shot and see how it goes.
[Motorola Droid Bionic] The Doctor04:
I have also had issues with Chrome, even on KK. FireFox for Android is much, much better and more reliable
[Motorola Droid Bionic] DrJwC:
Dolphin is working well also
[Motorola Droid Bionic] pairdime:
My second install of CM12 has mostly gone well, most of the lag has gone away. Here are the random issues I've had in the last couple days, figured I'd at least mention them:

When you snooze an alarm with other notifications up, the lockscreen will fade & light up numerous times.

When phone boots LTE has a 50/50 chance not to connect, I don't believe it to just be poor coverage. Resolved by disable/enable data (2 screens deep into Settings).

Music app continually was force closing for me. I originally disabled it, then decided to enable it again which is when I was having the FC repeatedly while it was not even loaded. Had to disable it again.

Skype, which updated yesterday, has massive performance problems. Additionally, when you Sign Out through it, it manages to sign itself back in. Probably Skype's problem, beware of this app.

All in all seems to be going well this time around. Battery life appears to be quite a bit better than CM11, then again I don't have as much crap loaded on it.
[Motorola Droid Bionic] platypoid:
clock wrong

I notice the clock display is one hour fast when using Automatic date and time setting . I am using 2-10-15 nightly.
[Motorola Droid Bionic] sd_shadow:
Usually incorrect time is caused by incorrect time zone selected, turn off auto, select correct time zone, turn on auto
[Motorola Droid Bionic] platypoid:
Super User

When I installed CM 12 everything worked okay. I enabled Root Access in developers options .

I never saw any Super User in Apps so I installed SuperSU from Play Store . When I open that it says I need to install some updated binaries but does not seem to be able to accomplish that by it's two options of Normal or rebooting into recovery.

Do I need to have a Super User app of some sort ?

thanks
[Motorola Droid Bionic] sd_shadow:
Rom is Rooted but it's limited, so installing SuperSU Flashable in Safestrap/TWRP is recommended

Install current SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
[Motorola Droid Bionic] The Doctor04:
Anyone else having trouble pulling down today's nightly? Both links give me a 404 error, and OTA on targa keeps telling me unsuccessful

Disregard :D
[Motorola Droid Bionic] pairdime:
I think I fixed my LTE not connecting automatically on phone boot. Maybe obvious to some but I hadn't tried this until now.

1. Go to "Data usage" then "Mobile network settings"

2. Preferred network type: change to "LTE (recommended)" (was set to "Global" previously)

3. CDMA subscription: change to "RUIM/SIM" (was set to "NV" previously")

Seems to have improved the speed issues I was having previously too, from 8mbps down to 18mbps.

Been using CM12 as DD since Sunday when I did a fresh install, everything has been fast & stable. :good::good:
[Motorola Droid Bionic] Oggie7797:
Lol yea that's always preferred.
[Motorola Droid Bionic] Aravindtop:
I am having problems here with Safestrap. I installed Safestrap targa 3.75, but when I hit install recovery, it goes through the process but doesn't install. What do I do?
[Motorola Droid Bionic] sd_shadow:
In Stock Rom? Superuser popup?
[Motorola Droid Bionic] Aravindtop:
My current setup: FRESH of a factory reset, and was already rooted. Updated SuperSU from google play. Then adb install the safestrap targa 3.75. Go into safestrap, grant superuser access, hit install, goes through the install process, then nothing. The 3rd option to boot into recovery is greyed out. Not sure if this affects anything, but I activated the phone without a SIM card.
[Motorola Droid Bionic] sd_shadow:
Download safestrap again, maybe bad download
[Motorola Droid Bionic] Aravindtop:
Have already tried nothing. Though, v3.65 works.
[Motorola Droid Bionic] ShadyDreamer:
You need to install the apk for 3.65 again then open the app and tell it to uninstall Safestrap recovery, then uninstall the apk. Then you can install the apk for the new one and install that version of Safestrap recovery.
[Motorola Droid Bionic] Aravindtop:
That didn't work either. I found out a solution. I did a universal unroot from within SuperSU, factory reset via the recovery menu, re-rooted, installed Safestrap 3.75, and it worked. This has apparently been a problem on a wide variety of devices on a wide variety of safestrap versions. This solution has worked about 90% of the time.