yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] almostthere:
[MENTION=4023029]Rycon33[/MENTION], quick suggestion

Why not post in OP if it's too difficult for you the steps for f2fs versions on how to install other kernels that are compatible so that they can do it on their own?
[ONE Android Development] Rycon33:
Only AK kernel is a bit tricky to install. It has this "any kernel" approach which is a very good thing actually but for normal users they are still always confused. It uses the original ROM's ramdisk and inject only its zimage(and modules).

On the other hand, other kernels(in already boot.img form which has its own ramdisk), as long as it is mentioned it is for F2FS, just flash it.

The AK zip I posted now can always be used as a base whenever you want to go back to AK. Once your currently on AK kernel, you can update to the zip provided by AK on his thread. But if you're currently on other kernel(let's say Tyr), you can't just flash the zip from AK's thread. You have to flash the zip I provided first then use the update from his thread. At least for F2FS, that's the case.

If anybody wants to do it on their own, the process for AK on F2FS is on the general section.
[ONE Android Development] ¿GotJazz?:
I just installed this ROM for the first time today. While things are running pretty smooth so far, one thing I noticed is that my battery is now charging way too aggressively.

The stock OPO used to significantly ramp down the charging current a lot sooner (somewhere in the 80% range). I just checked my charging, and it was pulling 1400 mA at 93%.

That's causing battery damage I don't want to have.

Is there a way to get the more graceful (and less stressful) battery charging curves that the Stock OPO normally has?

Thanks,

¿GJ?
[ONE Android Development] Rycon33:
I have a pretty good explanation about charging the battery that I posted on OnePlus forum that many people there found informative. Are you using an external kit that measures the "real current" draw while charging your OPO? I have one, and it is always attached to my OPO charger. The normal current draw of my OPO is around ~0.8A, regardless of kernel and/or ROM. See sample pics that I took from last time.

On some rare cases, my OPO can draw a maximum of ~1.8A. That's why our charger is rated 2A because it can really output such high and our device can really take it.

https://www.dropbox.com/s/7l2rcgqn6axz51x/Charging_current_drawn.jpg?dl=0

Sample on 1.8A

https://www.dropbox.com/s/0knu3soxfc5vuyx/DSC_0099.jpg?dl=0
[ONE Android Development] benzso63:
Is there a way I can remove the carrier from lockscreen. Right now it is showing t-mobile on the top close to upper left position.
[ONE Android Development] Rycon33:
Screenshot.

I'll check the carrier XML later, "probably" easy to adjust the margin or make it disappear. :p
[ONE Android Development] benzso63:
Attached Sorry
[ONE Android Development] Rycon33:
I can't do this permanently with the ROM, but for you, you can always flash this mod every after ROM update.

No-Carrier-label_mod

Note: Be careful flashing this on a secondary ROM, you might think it F'd up your primary ROM but not, just need to boot up on it and all fine.

Most probably due to the old flashable format I used. The mod is safe, it's the flashable format that I used that is too vintage.

Now you see it:

Now you don't:
[ONE Android Development] nicksmizzle:
holy good god, thank you, i have been trying to get something like this working for literally days, that cm bug, although not really important enough for me to ask about was driving me nuts lol
[ONE Android Development] byAidan:
Hey [MENTION=4023029]Rycon33[/MENTION] i'm having trouble getting SuperSU to work on the latest F2F2 build (with AK Kernel)

I flash the SuperSU zip and I don't have root and I also tried using the SuperSU app from the play store with the built in ROM root to install it but that also didn't work :(

I would use the built in root but Titanium Backup isn't working properly with it

Any help would be greatly appreciated :)

Thanks!
[ONE Android Development] ¿GotJazz?:
Thanks, [MENTION=4023029]Rycon33[/MENTION] - I just purchased a similar USB current/voltage monitor from Amazon which had dual V/mA displays (http://www.amazon.com/dp/B00J3JSEG6?psc=1). I'll check your posting on the OPO forums, too.

I am also experiencing a huge problem with this ROM that I have seen with all other CM12 ROMs: My desktop display goes totally black and non-responsive, but the Status / Notification bar operates just fine. It obviously makes all CM12 ROMs unusable for me. It seems like with this ROM I saw something a little different - I did see what looks like the real screen display pop on for just a few msecs before it goes black.

Any help would be appreciated!
[ONE Android Development] raybit10:
Thank you so much :good:

Such little thing but hugely annoying.
[ONE Android Development] benzso63:
You are the best brother ! :cool:
[ONE Android Development] almostthere:
Clean flash or dirty flash?

I usually flash in the following sequence in TWRP

1. ROM

2. Gapps

3. Booloader.img for AK kernels

4. UKM

5. SuperSu v2.37 flahable

6. Other mods

Works for me until now and I make it a practice to clean flash /system and wipe /cache and /dalvik (if applicable)
[ONE Android Development] byAidan:
Thank you very much for taking the time to write that, managed to get it working now! :good:

Thanks again
[ONE Android Development] Rycon33:
It's unusual. I only experience sudden minor blackscreen(half of the screen actually) flashes on xda app sometimes. But not like as you mentioned like no response or freeze.

If your phone doesn't exhibit such behavior on CM11/CM11s, then I suggest you wait some more time for CM12 to become more stable or when official nightly really starts. We're only in the mercy of CM devs regarding coding. ?
[ONE Android Development] fburgos:
Hi i downloaded this ROM and wanted to try with multirom right now in multirom I have

Primary boot stock cm11s

Secondary (first multi) pbear cm12

When I try to add this in a new slot (third) I have the error

Is this ROM or multirom related?

I'm sorry if this doesn't belong here.

Regards
[ONE Android Development] Rycon33:
Update to the latest multi-rom(version 30b) and multi-rom recovery. It doesn't need the modified updater-script now.
[ONE Android Development] ¿GotJazz?:
I ran into this black desktop problem multiple times today, and I still don't have a solution. I'm not entirely sure, but I think that there may be a pop-up modal message box on the screen when this happens. I saw what looked like message box on the screen momentarily when the screen went black. I know that no desktop screen taps do anything, but the Notification and Status bars still worked fine.

Help? Pretty Please?
[ONE Android Development] Rycon33:
Sorry, I cannot help you on this one.

You may try other CM12 ROM, hope its ok on theirs. If the same, go back to your CM11. Or retry the process of installing CM12, from full-wipe.
[ONE Android Development] ¿GotJazz?:
Oh, well ... Thanks, anyways [MENTION=4023029]Rycon33[/MENTION]!

I always install doing a clean secondary ROM install from MultiROM, so I believe that it is equivalent to a full-wipe. All CM12 ROMs I have tried so far act this way on my OPO, so I doubt any other ROMs will act differently. I'm nervous that this could be a real issue once the official OPO Lollipop update gets released. It won't be as easy to go back then.
[ONE Android Development] Rycon33:
We cannot wipe /system on secondary. Installing a secondary ROM will always be dirty, we can only wipe cache and dalvik cache when we're on secondary.

Anyway, if it's not happening when you're on CM11, then the issue is your process of installing CM12 only. You can check, if you try installing it as a primary ROM, here you can full-wipe and see how it goes.

Backup your primary and secondary ROM.

Full-wipe, that includes wiping /system.

Install CM12 as primary ROM then see.

EDIT: Btw, that's just a suggestion, up to you if you want to follow. Always be careful flashing anything, may end up bricking your device. Though I must say OPO is pretty unbrickable like a Nexus.
[ONE Android Development] betalaga:
Hi, i have 2.5.1 version with f2fs file system. I have an issue, during a call screen switch off and it doesn't turn on until finish the call ..
[ONE Android Development] Rycon33:
Here is fine. At least on the few calls that I made. Anybody can second the motion??
[ONE Android Development] Rycon33:
While it isn't merged yet, guess what I cherry picked this time. Currently testing of its fine.
[ONE Android Development] Khizar:
You have the prevent accidental wake enabled? That was causing this for a few users..
[ONE Android Development] benzso63:
Nice!
[ONE Android Development] betalaga:
I have try to disable it but the issue remain

[emoji23]
[ONE Android Development] Rycon33:
If you're on Multi-ROM, give this ROM a try. Never had that issue here. You can always go back to your preferred ROM afterwards.
[ONE Android Development] betalaga:
Non thank i like this rom i wait next Update...
[ONE Android Development] Rycon33:
Temasek has just released a new update, try it mate.
[ONE Android Development] NOSTALGIA:
can u include the audio stutter fix feom fusionjacks github on ur build, since we both love music maybe u wanna try to consider
[ONE Android Development] Rycon33:
I've heard that, but can't see any commit about it.

Anyways, on kernel side we can also see improvement on music playback when 2 cores are consistent even on low loading such as playing music. I observed on Tyr kernel using mako hotplug, music playback is better than stock kernel.

Btw, to the few users that still cares about this ROM, I'm uploading now the build that was supposed to be for yesterday's, I was out and about and only now got the chance on my PC again.

It includes the yet to be merged weather panel on status bar header.

And other latest codes they merged yesterday.

I didn't upload the ROM for secondary, as the multi-ROM now is ok even without the modified updater-script.

So, EXT4 version can be installed as primary or secondary. F2FS version now can be installed as primary and secondary.

Note that you have to be on latest multi-ROM(v30b) and latest multi-ROM recovery for those using multi-ROM setup.

And both EXT4 and F2FS will now come on stock kernel. Flash the kernel you like afterwards if you're into custom kernels.
[ONE Android Development] ¿GotJazz?:
OK, very useful information! I'm still feeling pretty adventurous. So, just to make sure we're on the same page, you're recommending that I:

Do a TWRP backup of my current primary ROM (for safety if this doesn't work out)

Basically scrap MultiROM

Do a Factory Wipe + a System Wipe

Install this ROM as my only ROM (No need to keep my old ROM, right?)

Install my favorite GApps

Profit?

Correct?
[ONE Android Development] Rycon33:
Yes, try that. After you backed up, uninstall Multi-ROM then followed by full-wipe.

I'm using Bank's g-apps for Lollipop btw.

See how it goes.
[ONE Android Development] Khizar:
Yeah do the wipes before flashing and not after. After all, you do wanna boot into android and not be greeted by a black screen.... ??

I am using G's gapps. Based on bpear's, they were the best IMO.

If you want to try, here's a link. http://xdaforums.com/showthread.php?t=2963192
[ONE Android Development] kennonma:
i am not able to install the ex4 20141215 rom in mutlirom for sec rom,

the error code like error exceting updater binary in zip file mrupdate,zip
[ONE Android Development] Rycon33:
then i guess you still need the updater-script for second ROM.

get it from previous build

EDIT: Btw, 16-Dec build uploading.

Latest Changelog:

16-Dec

- new bootanimation

- cherry-picked "enable/disable scrolling-cache" mod from Temasek git

- Telephony: GSM: remove 'Carrier Settings' regardless of csp_enabled

- lots of frameworks_av and qcom_audio commits merged

- See Gerrit for the detailed merges/changes.

F2FS uses [MENTION=4804871]DerRomtester[/MENTION] kernel(v54), thanks to him.
[ONE Android Development] Linsanity:
Audio Issue?

Hi, so is the audio static issues fixed in the new build? I have been switching back and forth between cm11 and 12, so I was just wondering. Thanks
[ONE Android Development] benzso63:
Bro, can I flash this update this 16-Dec on the top of the previous one? I don't need to do full wipe?
[ONE Android Development] Rycon33:
if you're coming from other CM12, I'm not sure. But backup and try.

If you're coming from my previous build, dirty flash is fine. That's what I've been doing for some time now.
[ONE Android Development] Rycon33:
Audio issue is still there. I am using a custom kernel to at least make the issue less pronounced.
[ONE Android Development] benzso63:
no from your previous build. I have been using yours for l long time :D
[ONE Android Development] Linsanity:
Which kernel are you using? I have been using Ak but the problem is still there
[ONE Android Development] Rycon33:
Tyr kernel, intelliplug(performance) for hotplug settings. Mako hotplug is fine with music too.
[ONE Android Development] Rycon33:
had a quick make for SystemUI and Settings for the still yet-to-be merge Circle battery mod

Other battery forms(icon portrait and landscape) is a bit off though on my compile, but circle battery is fine. Maybe next time on clean build will be ok with other battery forms also, we'll see.

Flash this on top of 16-Dec build.
[ONE Android Development] benzso63:
Bro just letting you know I updated your new build 16-Dec. Then flash the "No-Carrier-label_mod" Now the screen shows "Unfortunately, System UI has stopped. I click ok and it keeps coming back lol.
[ONE Android Development] Rycon33:
mate, they took out that keyguard_carrier_text_view.xml , let me check later where they put it now:D

oops, I'm seeing it wrongly(i think it's still there), let me check later in the day

EDIT: If you also flash the battery-circle mod, then use this whole SystemUI.apk instead. Attached, move manually.
[ONE Android Development] ¿GotJazz?:
OK ... I did a fresh install of CM12 Lollinaro on my OPO as the only installed ROM. MultiROM was removed.

Unfortunately, I saw the same two problems that I have seen with all other CM12 ROMs.

One problem: The desktop screen randomly goes completely black, with nothing "touchable" on the desktop (at least, nothing that I can identify). However, the O/S is still operational. The Notification/Status bar still operate fine, and holding the power button in brings up the reboot screen - which also works fine. It doesn't seem to be related to the Launcher. I saw this problem occur on Nova Launcher and the Google Launcher. This seems to occur randomly after turning the OPO "On" from a sleep. Not fixable without rebooting. Once this problem starts, it happens more frequently until the phone becomes basically unusable.

Second problem: The Home button randomly stops working. Not sure when this happens, but more rarely than the first problem. Not fixable without rebooting.

Since I have seen this on all OPO CM12 ROMs so far, I'm really concerned that I won't be able to use the official OPO Lollipop release unless I can figure out the root causes of these problems beforehand.

I don't think there is any way to submit JIRA tickets for Bacon CM12 yet, right?

¿GJ?
[ONE Android Development] Rycon33:
Since you mentioned it's happening on all CM12 ROMs you tried and CM11 is fine on your device, then just stick with CM11 for the mean time.

Wait for official nightly and see how it goes, if it even makes a difference. Your case looks like a hardware problem but you mentioned everything is fine when your phone is on CM11. I personally don't know what to suggest already.:p
[ONE Android Development] Khizar:
First issue sounds like a SOD(sleep of death), I haven't had it and neither have I read reports of anyone else having that.

Second issue I read 1 or 2 others report that but I don't have that issue, never did.

My recommendation would be to wipe and flash latest stock, via fastboot manually, and then flash a custom recovery(I recommend twrp) and then this rom
[ONE Android Development] T0yK4T:
Wrong thread, my bad.
[ONE Android Development] kennonma:
working with script file ~ thx
[ONE Android Development] ¿GotJazz?:
Hi, [MENTION=4519152]Khizar[/MENTION] - I checked around, and the SoD failure sounds a bit different. From what I found, the SoD has the entire screen black, but I have some working components (like the Status/Notification bar and Power-Off pop-up). Maybe a new variation of the SoD has cropped up for Lollipop?

I came from the latest stock (44S), though it probably doesn't matter. I did a Factory Wipe + System Wipe before installing Lollinaro via TWRP - I think that removes the previous stock installation entirely from the picture.

None of these issues have ever appeared in my many OPO KitKat ROM installations, but they have all appeared in every one of my Lollipop trial installations after about 24 hours of use.

Is there any way I can submit a JIRA ticket somewhere?
[ONE Android Development] latenightchameleon:
[MENTION=344884]¿GotJazz?[/MENTION]? whether you will submit anything to JIRA or not, you should get logcats to diagnose what actually happens to your device.

I use this, you can also connect the phone to your pc and run adb logcat in terminal/cmd
[ONE Android Development] ¿GotJazz?:
[MENTION=5902796]latenightchameleon[/MENTION] - Yes, I do want to submit Bacon CM12 JIRA tickets (If I can - Not sure where, though).

I would also like to submit a logcat with the JIRA ticket, but I wasn't sure how I would be able to properly collect the logcat of the actual event if the screen is unusable. I'm guessing I would need to use the 'adb logcat" option, since I won't be able to use my screen, right?
[ONE Android Development] Rycon33:
Below is a message from logcat thread I'm following. This is what I always follow also. And regarding filing a ticket to JIRA, I think they won't be accepting any yet until the first official nightly becomes available.

adb logcat -v long > name_of_problem.txt

with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)

Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
[ONE Android Development] Daemos:
Aww...no more F2FS? Why??? F2FS is much better than EXT4!
[ONE Android Development] Rycon33:
Well, I thought nobody is using it except me, LoL. :p

Since now I know at least another one uses it, I'll still upload it, don't worry.
[ONE Android Development] aznracer62:
Awh dammit I just changed back to ext4. I jumped the gun too soon. I did like f2fs. Who here uses f2fs? I do (or did).
[ONE Android Development] Rycon33:
Don't worry, update will only come on Monday, you still have time to go back to F2FS :p

Been many features merged since my last repo sync. Should be a pretty huge update on Monday(at least from what I've seen merged in Gerrit)
[ONE Android Development] aznracer62:
Haha ok sounds good. Yea I noticed tons of changes on Gerrit.
[ONE Android Development] Daemos:
I've been using F2FS on my Note 2 when it came out! :)
[ONE Android Development] benzso63:
Current I am running EXT4_CM12_Bacon_16-Dec, but can I install this one ? cm-12-20141218-UNOFFICIAL-bacon.zip
[ONE Android Development] Rycon33:
Yes
[ONE Android Development] byAidan:
I also use F2FS so thank you for continuing to release them! :)

Thanks again
[ONE Android Development] MrPhilo:
Same, I'm using the F2FS ver. as well, hopefully you don't stop using it
[ONE Android Development] benzso63:
Bro, would the silent huge update today different than the new one on Monday ?
[ONE Android Development] Rycon33:
I'll add a couple more cherry picks for Monday. Today's one is the big update and also has cherry picks as mentioned in changelog at OP.
[ONE Android Development] byAidan:
Just flashed the test build, I saw there were quite a few changes so I clean flashed just to be safe and now my OnePlus is smoother and faster than ever ;)

Thanks can't wait for what's to come! :good:
[ONE Android Development] Rycon33:
Music playback is still killing me though(on stock kernel).

Had to use custom kernel so that even on screen-off, the playback doesn't stutter especially on FLAC music files.
[ONE Android Development] Daemos:
I tried installing tyr's kernel on the new silent build...doesn't boot.
[ONE Android Development] Rycon33:
My repacked(for F2FS) boot.img of Tyr v55 also doesn't boot on mine, I had to make my ROM in the secondary then I was able to used my repacked Tyr.

On non-MultiROM(and EXT4) setup, should be fine.
[ONE Android Development] Daemos:
Easy fix hopefully? I find tyr kernel gives me the best battery/performance ratio

That and stock cm has limited options for UV/tweaking
[ONE Android Development] Rycon33:
My workaround is to use the ROM(F2FS) as Secondary ROM.

His previous versions were on "permissive" mode and doesn't have issue with F2FS Multi-ROM. He switched to "enforcing" on v55.

It's actually the limitation of Multi-ROM, not the kernel. Although having the kernel on permissive will make it compatible. But we can't just ask kernel devs what to do. Their work, their choice, and that's pretty fair also.
[ONE Android Development] Daemos:
I'm not using multirom...i use your rom as a my daily and only :)
[ONE Android Development] Rycon33:
You mean you're just using plain F2FS?

If yes, My repacked could work on yours, I'm uploading it on the same folder. try it. Or from the attached, should be fine on non-MultiROM F2FS.
[ONE Android Development] Daemos:
Yes I'm using plain f2fs. I'll give this a try, thanks! Why does the kernel need to be repacked? I thought it was already f2fs ready.
[ONE Android Development] Rycon33:
Yes, it will work on plain F2FS. Let me know how it goes.

And also on Multi-ROM, but only as secondary. On primary, it'll get stuck at bootanimation.
[ONE Android Development] Rycon33:
He stopped the F2FS version as very very few users are using it. But the kernel has still the patch, we only need to edit the fstab.bacon file.
[ONE Android Development] Daemos:
Unfortunately, the repacked kernel doesn't work :( it does get past the one+ screen but gets stuck at the cyanogen loading animation. Does AK kernel require repacking?
[ONE Android Development] Rycon33:
Re-flash the ROM first then flash latest AK from his thread.
[ONE Android Development] aznracer62:
That buzzing sound from the audio is still there. What is that from? It's even on AOSP lollipop so it's not a cm12 thing.
[ONE Android Development] Rycon33:
Yes, that's been annoying as F'd. Haven't seen any lollipop ROM that doesn't have it(as far as I know).

The temporary workaround is to use a custom kernel that makes a minimum two-core running. That seems to make it ease that music playback.

Btw, new build compiling atm. If no problem then will upload after awhile.
[ONE Android Development] aznracer62:
What is your daily kernel? AK and use synapse?
[ONE Android Development] Rycon33:
I'm juggling between AK and Tyr.

I'm on F2FS and using Tyr v54 at the moment. Intelliplug on performance seems to be better on music playback. And mako hotplug also good in music playback.
[ONE Android Development] Daemos:
Fyi, latest ak I'm getting sod, but no issues with older version of tyr.
[ONE Android Development] Rycon33:
22-Dec build is being uploaded

- Navigation bar height adjust(cherry-picked from other ROM), placed at display-settings. On-screen ON-OFF toggle is still at buttons-settings.

- Re-orient volume buttons when in landscape(still not merged in CM yet but I already cherry-picked it)

- SystemUI: properly hide mobile data type while wifi is in use(still not merged in CM yet but I already cherry-picked it)

- Cleanup battery style code(still not merged in CM yet but I already cherry-picked it)

- See Gerrit for the merged ones -> frameworks_base and packages_apps_Settings
[ONE Android Development] LecterMe:
I miss a way to swap onscreen back and recent buttons. Will this be possible anytime soon?