yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] tiny4579:
That is what he was saying. Go stock.

My opinion don't flash a custom kernel unless you know why you want it and are ready to deal with possible issues.

There isn't really any reason to go with a custom kernel on opo though.
[ONE Android Development] Criton30:
ok, understand, thank you guys :good:
[ONE Android Development] daleski75:
Yes I do and always have done.
[ONE Android Development] daleski75:
Precisely and if you are flashing a new zip each and every day it's just easier and safer to keep it as simple as possible due to how many changes are happening on a daily basis and this helps to minimise the risk of potential issues from a custom kernel.
[ONE Android Development] daleski75:
And one other thing to add my builds are (from what I can see) the only ones with se linux set to enforced and if you flash a custom kernel it gets set to permissive.
[ONE Android Development] giaur:
Not permissive anymore?
[ONE Android Development] marvinandro:
[MENTION=251020]inffy[/MENTION], did you get it to encrypt so you can connect to work? I've tried several builds and 5.0.x ROMs and can't get it to work yet. When I hit the Encrypt button after entering my password, instead of going through the long encryption process, the phone just reboots back and it doesn't say Encrypted but offers me again to encrypt.

I've done this several times over the past few weekends and have to flash back to KK on a Sun evening so I can work during the week and repay to work related stuff.
[ONE Android Development] Criton30:
I have SIM Tookit application from my Carrier (T-Mobile HU), this application closing force....
[ONE Android Development] daleski75:
Not now no as CM have fixed the issues which did not work when se linux was set to enforced.
[ONE Android Development] fards:
I'm not getting cap buttons switching off, still needs the cap button app and permissive for that one.

are the lights going off on a clean flash?
[ONE Android Development] giaur:
Not true, main issue - hw buttons lights are not fixed. For the rest you are talking about, I don't even care.
[ONE Android Development] daleski75:
The buttons have always worked for me for a few weeks now.
[ONE Android Development] Khizar:
Better workaround than using capacitive buttons app(or at least it's better IMO) is to set the back light timeout duration to 1 sec. If you set it to 1 even if you turn off your phone while back lights are on, they'll stay off.
[ONE Android Development] Anoxymoron:
Latest 12/14 build—I can't add a second home screen page in Google Launcher. When I go to drag a widget over and create a second page, nothing happens. It was working fine on the previous build.
[ONE Android Development] fards:
it easy pretty easy to set permissive so I say leave it at enforcing :D
[ONE Android Development] tiny4579:
Cm file manager still doesn't work in enforcing mode. There are a few other odd denials.

Like these.

type=1400 msg=audit(1418573943.624:17): avc: denied { getattr } for pid=1828 comm="stat" path="/persist" dev="mmcblk0p15" ino=2 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:persist_file:s0 tclass=dir permissive=1
type=1400 msg=audit(1418525825.568:3): avc: denied { read } for pid=3570 comm="IntentService[W" name="wakeup_sources" dev="debugfs" ino=17 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:debugfs:s0 tclass=file permissive=1
type=1400 msg=audit(1418525825.568:4): avc: denied { getattr } for pid=3570 comm="IntentService[W" path="/sys/kernel/debug/wakeup_sources" dev="debugfs" ino=17 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:debugfs:s0 tclass=file permissive=1
[ONE Android Development] martix90:
Can't reproduce.

Working here (dirty flash).
[ONE Android Development] giaur:
How do I set it? Do you mean screen timeout? 15 seconds is min available, but 1 sec will be too short
[ONE Android Development] Anoxymoron:
Strange. I dirty flashed as well from a clean 12-12 build. Guess I need to start clean again.
[ONE Android Development] fards:
the /persist is an interesting one.
[ONE Android Development] giaur:
I can't understand pressure to selinux enforced. Don't get me wrong, I know all security considerations etc, etc but most of them don't make any difference in real life.
[ONE Android Development] tiny4579:
Especially why untrusted_app needs to see it. I know an fsck was introduced because of corruption issues to /persist. Maybe that's it. But the permission was getattr. Does fsck need getattr?
[ONE Android Development] Hanny:
Perfect. Confirmed working. Thanks for the workaround, and I can keep on dirty flashing :)
[ONE Android Development] fmc000:
This shoud take care of all the dialer issues in these few past days.
[ONE Android Development] benjamin.j.goodwin:
Cheers. Are you a previous mako user?
[ONE Android Development] Aavion:
i'm a former mako user :D

Gesendet von meinem Schinken. ?
[ONE Android Development] Bronyr:
Camera next very jittery but it's been fixed on Bliss; but I had terrible battery drain on Bliss.
[ONE Android Development] drewdatrip:
Everyone still having issues with audio pops and digitization with streaming services?
[ONE Android Development] inzaghi75:
How did he fixed it?
[ONE Android Development] fards:
Not sure what's going on.

Pity android doesn't have sealert to debug it.

personally I've though selinux was always a bit of a mess although I can see is advantages, used to be a nightmare on fedora when it was introduced
[ONE Android Development] Yammertime:
Nice. I wonder if it'll be included in tomorrow's build.
[ONE Android Development] inffy:
Nope. So i just bought he Nine Exchange app from Play Store, it can restrict the eas policies to only to the app.
[ONE Android Development] hughfollett:
Yep! Are you doing fine?
[ONE Android Development] benjamin.j.goodwin:
Yes cheers, how's you? Been on OPO long?
[ONE Android Development] Bronyr:
No idea but it's in the op on Bliss. The whole thing is so smooth. But like I said, battery life is poor. In trying to follow this guide from k900 on reddit to get better results:

http://www.reddit.com/r/oneplus/comments/2p7szq/oneplus_one_uber_battery_savings_guide/

I noticed my biggest offender by far was calendar storage, accessed 100's of times.
[ONE Android Development] Criton30:
what is enforced or permissive? can tell me somebody pls?
[ONE Android Development] fards:
No I think it's fine for daily use.

No one forces anyone to use it, or update every day.

The bugs are usually fixable with minor tweaks, and you don't need to clean install everytime.

Just the first time or if you come across a major issue that others say works in a clean install.

Selinux is security using rules on what can access what.

Permissive means it allows whether there's a rule or not but logs it.

Enforcing means only set allowed rules work.
[ONE Android Development] tiny4579:
Enforced means selinux policies are enforced. Permissive means the selinux policies are logged but not enforced.

I use cm12 as a daily and have been for over a month. Its good enough for me. I don't know. I don't clean flash every build. No one said you had to. If they did, they ate being cautious. I'd day just flash the ROM between updates and only do a clean install if you have odd issues.

Google backs up and restores apps if you have that option on, so you just would lose the app data.
[ONE Android Development] :
well I get way better batterylife on a custom kernel. Gui is much more fluid. At least in my opinion.
[ONE Android Development] Criton30:
For example, I use now the newest ROM, tomorrow come the newest ROM with bug fixes, and I have installed today approximately 20-30 apps, what I need for driving, for banking and other stuffs.... how can I install the newest ROM without losing my apps data? What is the update method? after the update will my apps running also good or I should re-install it? What do you mean with tweaks?

I use now this ROM 14122014 wit PA Gapps and stock kernel.

---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------

? what kernel? I have today the information, if you are expert or beginner for installing rom and soo on, better is to using the stock kernel.
[ONE Android Development] fards:
Just update the rom *if* it fixes a bug you're struggling with.

Otherwise don't bother.

You can always update each weekend if you feel the need.

If so Just flash the updated zip

gapps and app data will survive.
[ONE Android Development] magnamentis:
don't wanna sound rude but perhaps you really go and read the basics before starting to flash alpha software ? this kind of thread is not really about learning how to flash but do help develop the rom.

---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------

this is in no way contradictory, it's well possible to optimize or get an optimized battery life / performance ratio and still it can be tricky to use a custom kernel in a period where a rom is developed from the ground up to be a daily driver within weeks, thus at high speed. so if you want to try custom kernels, no problem, but you have to be aware of that mentioned fact that tomorrows rom might be incompatible with todays custom kernel and this from what you sound like is the sheer opposite of what you need.

i would gladly explain to you how to flash roms and the likes but it has all been said in this and every other rom thread so the only thing which remains to do is for you to read and decide whether it's worth the effort for YOU, nobody else can answer that but yourself
[ONE Android Development] Criton30:
so, for example downloading tomorrow the newest rom, goind to recovery and installing the zip file? whithout wiping data and cache... reinstalling gapps?

---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------

ok, thank you, therefore I use stock kernel :good::o

for clean install I do:

wipe system/internal storage/wipe cache/dalvik cache format data.

installing ROM

wipe cache/dalvik cache

installing Gapps

wipe cache/dalvik cache

reboot

for update then:

installing ROM

wipe cache/dalvik cache

reboot

If I am wrong, please say it.
[ONE Android Development] fards:
You shouldn't need to wipe internal storage.
[ONE Android Development] fards:
There's a fix in this thread already.

Use older camera lib..
[ONE Android Development] hunter0389:
First, always do a Nandroid backup. Most of the time, a "dirty flash" would work just fine. You will not lose your installed apps and data.

This is what I do:

Backup

Wipe cache, system, dalvik

flash new ROM

flash Gapp (I have always used the same one)

flash SuperSU

flash Google Now Launcher (my preference)

Reboot

Go to Settings and check out all the new fixes/added features.

My installed apps/data ALWAYS remain. Since I flashed Google Now Launcher, my home screens always stay the same as before.
[ONE Android Development] geowolf1000:
Erase sd/android/data for clean install
[ONE Android Development] Criton30:
why did you install SuperSU, root is already in the ROM included. flashing Google Now Launcher? It is better? Can you please give me a download link for Google Now Launcher? :) with dirty flash you say update and not clean install, correct?

---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------

I wipe my Internal storage for clean install , beacuse I flash everything via adb sideload. Or this is not the good method?
[ONE Android Development] :
For beginner keep it stock.

When you are confident and have time to do many clean installs then custom ones can be fun. Especially if you like tweaking and changing and stuff. But only if you have time haha.
[ONE Android Development] Criton30:
Thank you very much everyone, I hope in the future I will also come with constructive comments
[ONE Android Development] giaur:
Which lib do you mean? More specific please?
[ONE Android Development] hunter0389:
Until recently, the built-in Superuser was not working. I've always used Chainfire's SuperSU. So, it is just a preference. Also, I flash different CM12 roms. Rycon33's ROM uses SuperSU instead of Superuser (please see screen-shot).

Google Now Launcher is, again, a preference, not because it is better or worse than the stock launcher. You can google for the flashable zip.
[ONE Android Development] opee:
play movies doesn't work in the latest build!
[ONE Android Development] gianton:
Check here,

http://xdaforums.com/showpost.php?p=57424185&postcount=1715
[ONE Android Development] daleski75:
I reverted it until it's fixed officially as it caused other issues with video play back
[ONE Android Development] opee:
Okay thanks for the answer!
[ONE Android Development] Criton30:
no problem here

---------- Post added at 08:55 PM ---------- Previous post was at 08:51 PM ----------

only for question I know I must forget benchmarks, but Antutu closing force?
[ONE Android Development] giaur:
Seems CameraNext is a bit less laggy after this fix (but still laggy). However, it breaks 4k uhd recording with Google Camera
[ONE Android Development] NOSTALGIA:
antutu problem
[ONE Android Development] giaur:
Ok, does anybody have copy of this lib? After flashing it, again video playback does not work anymore with system player.

---------- Post added at 10:12 PM ---------- Previous post was at 10:02 PM ----------

Again and again... selinux enforcing.

---------- Post added at 10:55 PM ---------- Previous post was at 10:12 PM ----------

WARNING: don't flash it. It breaks video playback and it can''t be undone wihtout wipe all data.
[ONE Android Development] alepozzo:
GApps recommended

Hi guys!

I've flashed few minutes ago the latest unofficial CM12 build but there isn't GApps included.

Which GApps recommend? PA GApps is already in beta-version and there is only micro package, it's enough?

Thanks at all!
[ONE Android Development] hunter0389:
What? Just restore from nandroid backup or dirty flash latest ROM. Why do you have to wipe all data?
[ONE Android Development] Criton30:
Wake up display is very slow, can somebody please confirm that?
[ONE Android Development] giaur:
I didn't make backup and flashed that fix for camera. After this, video playback din't work anymore. So I reverted only that single lib to default version and still playback didn't work. So I was forced to wipe all data to make it working. So, my warning: don't flash it.

Dirty flash also won't help (tried it). You will be forced to wipe data or to do clean flash. In any case - all your apps are lost.
[ONE Android Development] burnski:
I did a full wipe, clean install of the 12-14 build (stock kernel) and still have the hardware button backlight staying on. . The only fix I've found is to use the selinux switcher then toggle the capacitive backlights app, but it quits working after a reboot.

I notice some people still having the same problem but others not. Is there a log file i can pull to help fix this bug for good?
[ONE Android Development] giaur:
It works for me even after reboot. Install selinux mode changer and capacitive buttons.
[ONE Android Development] marvinandro:
Thanks. I'll check if Nine Exchange can full the MDM software.

Update: No dice with Nine Exchange - Your phone has been quarantined.... Back to KK, back to work tomorrow.
[ONE Android Development] Tunasty:
Got an advice for you man. Flash cm11s and your good to go.
[ONE Android Development] rlaw:
On 12/14 build, anyone else unable to get Facebook Messenger and Tinder to login using FB properly? (I don't have FB app installed, previous builds worked fine logging in).
[ONE Android Development] Criton30:
Hey man, after the first boot was this problem, all is working now. HW keys back light working too without issue.
[ONE Android Development] 69gm:
Another general observation of the different CM12 ROMs I've been trying out... They don't play. WAV files. I hope that gets fixed!
[ONE Android Development] fizfaka:
Screen take long time to turn on fix already?
[ONE Android Development] lordsinasina:
I Still have the problem with facebook videos sounds are out of sync. it was fixed a couple of builds ago but it is back again with the latest build. any idea ?
[ONE Android Development] nolsen311:
Why are you playing WAV files? 1995 called, they said mp3 is right around the corner.

Whatever floats your boat, I guess.
[ONE Android Development] 69gm:
Ah spoken like a true I don't understand fidelity noob... :D
[ONE Android Development] nolsen311:
(LOL)ossless. Personally I notice the difference and have learned not to care because the advantages outweigh the disadvantages. To me. I just couldn't resist though.
[ONE Android Development] daleski75:
Doing a new build now so will be posted in a while (doing a make clean each and everytime now) however I have posted a changelog on the first post if anyone asks.
[ONE Android Development] giaur:
Changelog is not impressive, considering if it's worth to update now. I'm personally waiting for button lights and camera fixes, especially google camera focus issue.
[ONE Android Development] daleski75:
Flash this it reverts the camera lib to an older version which solves the lagginess.

https://mega.co.nz/#!gQIjnQiA!M0HeoY4WVaieEkK6aZ6W8Wr8QcXplcCy5lK4VQKE-Jg
[ONE Android Development] shure2:
Well I did a clean install yesterday, it was painful. Anyway none of the little nags I got from numerous dirty flashing were fixed so for me at least dirty or clean flashing doesn't make a difference
[ONE Android Development] giaur:
Nope, already tried this. First, it breaks Google Camera 4k recording, second it breaks video playback (at least in my case).

After reverting this lib to original version, still playback problem (sounds really weird). I even tried to wipe data, but after this I noticed, that /sdcard and /strorage/emulated/0 is not mounted. Had no time for any further tries so I restored last backup I had (12.13).
[ONE Android Development] agrifoni:
Given the recent kernel changes, do you suggest to use the stock kernel or AK?

THanks
[ONE Android Development] daleski75:
Unless there is a specific reason why you need a custom kernel it's always best to stick to stock.
[ONE Android Development] andip71:
Of course I have to slightly disagree here :)

If the custom kernel is updated, there is no reason to stay with stock neccessarily.

I will get my updated kernel out in 2 hours, with all the same code base than stock kernel, i.e. all patches available are in (and even more).

Of course, everyone's own opinion what to use :)

Andi
[ONE Android Development] agrifoni:
THanks!
[ONE Android Development] :
Love the ROM but is still no fix for the HW buttons staying on? I know a fix for it but it restarts the phone from time to time.
[ONE Android Development] shure2:
I use keyboard backlight controller app which turns them off completely. However when you reboot you need to go into the app to apply it again
[ONE Android Development] daleski75:
Of course I totally agree as your a dev ;)
[ONE Android Development] Yammertime:
I haven't tried Facebook Messenger but Tinder worked for me. This is on a clean install without the Facebook app installed (12/14 build). I had a your issue with an older build but it went away on its own.
[ONE Android Development] daleski75:
I saw a fix on github somewhere just trying to remember if it was temasek or crdoid.
[ONE Android Development] :
Something you plan to use? ROM is great just that one thing annoys me but I know you do this for free and in your own time so I can't complain. :)
[ONE Android Development] daleski75:
Unless CM add it in then I won't be pulling in commits from elsewhere and also Lord Boeffla uses my rom as a template for kernel dev work as it contains zero changes so I would like to keep it this way.

The good news is though there is a lot of lollipop roms out there now so if one doesn't suit your needs another one definitely will.
[ONE Android Development] tsiftsism:
Considering the slow wake up display.

As I have written some days ago, I only have problems when the device is inside my pocket and I get an incoming call.

Then the display won't wake up, I have to press the power button to wake the display up.

If the device is in table, everything is good. No slow wake up when I get an incoming call, no slow wake up when I double tap the screen.

Is it only me having this issue? I have it since the last updates (since 10/10 if I can recall), there was no problem with old builds.
[ONE Android Development] daleski75:
I get it sometimes but not everytime which does not help.
[ONE Android Development] h4rl4n:
Am i the only one here not being able to make notification lights work?
[ONE Android Development] Hanny:
Not sure if its merged on 13/12 or 14/12 builds, but something has changed that made TWRP backups not showing in /storage/emulated/0/TWRP/Backups or /storage/emulated/legacy/TWRP/Backups.

I did a backup of 12/12 before flashing 13/12 and it was completely fine. Showing in non-root file managers, and can be moved into the PC through MTP.

However now I am unable to use non-root file managers or PC to view the backup files, and can only access them in /data/media/0/TWRP/Backups through root explorer.

In TWRP recovery itself, the recovery can see the backup files, and should be able to restore them. But I am not sure will they be wiped when flashing clean, since they lie exclusively in /data/media but not /storage/emulated which is linked to /sdcard.

I also notice a new "USB Storage" tab in Settings/Apps, but I believe we don't need that since we don't have an external SD card.

Can anyone please shed some light on this, or idea on which commit caused these?
[ONE Android Development] giaur:
Seems you experienced the same issue as me, directories /sdcard, /storage/emulated/0 are empty (not mounted?). I had this 2 times on different 5.0 roms, sometimes is ok, sometimes not, even after clean flash. I'm not sure what causes this. All data are actually present, not lost but available only by /data/media/0

This does not affect TWRP, because TWRP mounts all dirs by itself, there is nothing related to installed rom here
[ONE Android Development] tsiftsism:
So my case is worse than yours.

It happens every time.

Thanks for replying.
[ONE Android Development] daleski75:
New build is up on the first post guys, go grab it :)
[ONE Android Development] Hanny:
My /sdcard and /storage/emulated/0 are not empty. They consist the same content as /data/media but only except the TWRP backups.

New files created in system, for example taking a picture with camera, will show in all locations: non-root file explorers, PC MTP, /sdcard, /storage/emulated, /data/media.

However files created in TWRP only shows in /data/media.

I've done a bit of search on this and I have found this thread. My situation is similar to his, and an explanation for his issue is about the employment of multi-users.

But I am 100% sure on 12/12 build I did a TWRP and it simply shows up in all the above locations fine. Only after flashing 13/12 or 14/12, this happens. So something have changed.

I have ruled out other variables since nothing else have been modified except flashing the ROM.

Also I'm sceptical about the appearance of USB Storage in App Info.
[ONE Android Development] giaur:
I have a question about dirty flash. How do you do it? Wipe first (cache, dalvik cache, system) then install, or install first, then wipe? My problem is that every time I do dirty flash (wipe first), everything is ok, but video playback does not work with system player. Then I need to do clean flash or wipe data to make it working again.

Did anybody have the same?
[ONE Android Development] teamrf:
thanks for the Information..... quick light button was blocking some ok buttons screen apps..
[ONE Android Development] tobitege:
[MENTION=3614073]Miasmic[/MENTION]: run these 2 commands via adb or terminal emulator:

su
restorecon -FR -v /data/media/0

Afterwards all your TWRP should show up fine in both phone and MTP.
[ONE Android Development] Silverquark:
A dirty flash is only wiping cache and davlik then flashing the ROM....

A clean flash is a factory reset/data wipe + cache (factory wipe takes care of /cache ) Maybe doing a format /system as well.

I always do a clean flash and i also have problems with audio output. It works but there are some sort of electirc noises which are interupting my audio, if that is what you mean