yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] fmc000:
Doesn't work with encryption!

OK, I tried Yesterday's release on my phone, which has /data encrypted and formatted with ext4. Factory reset + wipe /system . The ROM boots, I can see the Slimrom bootanimation and then I'm asked to enter the decryption PIN. Then it says that the PIN is correct but unfortunately my data is corrupt and offers to reset everything.

However, my data is still intact (of course only my SDcard content, as /data was wiped before flashing the ROM) and a full nandroid restore gives back my phone up and running.

Tl;dr : if you're encrypted don't try this ROM unless you can afford a total loss of your phone internal data.

[MENTION=4435460]NoSpamDan[/MENTION] : maybe you should update post #3
[ONE Original Android Development] freshgiammi:
Actually, video recording isn't a problem on all roms. I have my self-compiled rom and i have both Video Playback and Recording working. The only issue is that some third party apps don't seem to record, but stock cameras and such work perfectly. [MENTION=4435460]NoSpamDan[/MENTION] if ya need help, just HMU on hangouts.

EDIT: Proof. https://www.youtube.com/watch?v=tpvWEZL6eYY
[ONE Original Android Development] amstel:
after updating from 3009 version to 0210,

I have 2 icons of the battery in the notification bar.

how come?
[ONE Original Android Development] Setting.Out:
Twice the battery life.. :)
[ONE Original Android Development] educavalcante:
This build has some Slim features added back: HW Key Rebinding, Navbar, Recents, Status bar customization...<br />

<br />

Still no video recording/playback, no MultiROM support, and still Testing status...<br />

<br />

You will likely have two battery icons in the Status bar. To get rid of the SystemUI Tuner one, pull down the QS tiles to expose the Settings gear icon at the top right by the clock. Long-press on it until it spins and keep holding until you see a message that SystemUI Tuner is unlocked/in the menu. Go in there, select Status bar, then Battery. Select "Do not show this icon"...<br />

<br />

Slim-bacon-7.0.0.build.0.1-DEV-DM-20161002-0541.zip

Enviado de meu A0001 usando Tapatalk
[ONE Original Android Development] amstel:
thanks! ☺️

works great.
[ONE Original Android Development] MoMaMeMi:
Did anybody try HW encrpytion yet?
[ONE Original Android Development] myshakugan:
Maybe this is what you're looking for.
[ONE Original Android Development] NoSpamDan:
I'll post a note, and mention it internally too. Thanks.

Thing is, you might need to decrypt your SD card on whatever "other" ROM you were previously on, and re-encrypt it with this one. I'm not sure how it all works 100% here yet.

So for the time being, please answer these:

1. What exactly do you mean, your /data/media/0 (Internal SD Card) is encrypted?

2. Coming from another ROM? If so, which ROM?

3. What encryption method was used before?

Any and all details may make for a better outcome for all here. :)

Sorry to say it, but because you didn't read. I mentioned this when I posted the ROM link in the thread a day or so ago, and also added a note to Post #3, the FYI/FAQ post...

I've also just added a note in Post #2 to check Post #3 for what is working or not.
[ONE Original Android Development] Setting.Out:
Oh, that's what's missing... You need a post on post 1 to read post 2 about reading post 3.. It's all about details... Lol
[ONE Original Android Development] KenjiHannya:
[MENTION=4435460]NoSpamDan[/MENTION] try test u Rom with Private Kernel R2.

Oh my dog!

Amazing combo dude

http://xdaforums.com/oneplus-one/orig-development/cm-private-kernel-r1-t3472729
[ONE Original Android Development] fmc000:
I'm not sure what you mean, in Android there's no "decryption", once you're encrypted you're done (or doomed :D). You have to format your internal storage.

When you encrypt all your internal storage gets encrypted, so both /data and /data/media are;

SlimSaber MM (6.0.1);

The one provided by SlimSaber (which is based on OmniROM).

I wrote a tutorial with the method I used: http://xdaforums.com/showpost.php?p=65570869&postcount=16933. After a period with SlimSaber MM I tried SmartisanOS, which is based on CM12.1 (therefore is Android 5.1.1) and it worked; after a few months I went back to SlimSaber without issues. The filesystem was originally formatted in ext4 under KitKat.
[ONE Original Android Development] tofu:
As a person who always uses encrypted file system I would say that by NOT formatting your device (and thus not removing your encryption) you are only asking for trouble. The type of issue you are describing is exactly the kind of problem you usually get if you haven't formatted everything when switching ROMs. From my experience I would never call that ROM / encryption issue.

As a basic rule of thumb when switching to new ROM (if you want working encrypted file system): always start from clean, freshly formatted device.
[ONE Original Android Development] fmc000:
Well, that's a quite a strong assertion IMHO. Especially on a 64GB device, wiping the internal storage every time is just overkill IMHO. Right now I have about 30GB on it and I am surely not ready to give'em up.
[ONE Original Android Development] ziepicwaffle:
This ROM isn't cm based, does the kernel still work?
[ONE Original Android Development] tofu:
I know I know. Life is a pain and then you die.
[ONE Original Android Development] fmc000:
[OT]The Pogues used a different word to describe life a few years ago :D https://www.youtube.com/watch?v=jBAgkmy2vrg (jump to min. 1:40) [/OT]

The point is that encryption is supposed to work across releases, therefore this is simply a bug. Of course, always IMHO.
[ONE Original Android Development] KenjiHannya:
Kernel it is. Work fine dude :good:
[ONE Original Android Development] NoSpamDan:
Some ROMs used to provide this capability. Stock Sammy for sure, maybe even COS 11S...

So you can't copy your user data off for safe keeping?
[ONE Original Android Development] NoSpamDan:
I actually found Slim recents crashed when I flashed GApps, but not without them... strange.
[ONE Original Android Development] david72262:
Yea, they turn themselves on a couple of times to even tho toggle is off, its early sure they will get fixed eventually. What gapps did you use I used slim
[ONE Original Android Development] fmc000:
Yeah, i was thinking that it may be a good time to also try f2fs, Does this ROM support it? (XDA search doesn't give a single hit on "f2fs" in this thread, strange...)
[ONE Original Android Development] NoSpamDan:
That's strange... I haven't seen that, but some optimizations were just made, so we'll see next build...

The kernel should support it, as well as the device tree, so give it a shot, and let us know... :fingers-crossed:
[ONE Original Android Development] Zeus20:
Slim has always been a winner in my books and can't wait to see this become a daily.
[ONE Original Android Development] Mike9966:
On Slim-bacon-7.0.0.build.0.1-DEV-DM-20161002-0541.zip not works GPS (Device only). High accuracy work.

Clean install by TWRP-3.0.0-0-bacon-20160309 with open_gapps-arm-7.0-pico-20161003.
[ONE Original Android Development] fmc000:
Try to revoke the location permission to the app you want to use and then grant it again.
[ONE Original Android Development] Mike9966:
Not help

Spoiler content hidden.
[ONE Original Android Development] fmc000:
I meant revoke location permission, reboot the device, grant it again, start the app.
[ONE Original Android Development] Mike9966:
Not help. Later I well wipe factory reset and check again.
[ONE Original Android Development] fmc000:
Anyone else can confirm GPS problems with the latest release?
[ONE Original Android Development] theekilla:
Is there a way to disabled/remove slim recents and use default?

Or is there a better way to enable multi-window?

Never mind got it!!!
[ONE Original Android Development] NoSpamDan:
Not seeing N Dev work there? Maybe I missed it.
[ONE Original Android Development] NoSpamDan:
I'm able to duplicate. Testing...
[ONE Original Android Development] Zeus20:
He is doing private work. By the sounds of it.
[ONE Original Android Development] fmc000:
Could you simply try in a root terminal emulator:

pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION

[MENTION=5780804]Mike9966[/MENTION] maybe you could try this too.
[ONE Original Android Development] Setting.Out:
https://forums.oneplus.net/threads/cm14-legendrom.468222/

Telegram Group of LegendROM:- https://telegram.me/LegendROM

.

SOURCES

Rom:- http://github.com/CyanogenMod

Device:- http://gitlab.com/amardeep434/ndevice

Kernel:- http://gitlab.com/amardeep434/nkernel
[ONE Original Android Development] thom@s:
Just downloaded latest build, will be the first N on my OPO !

Thank you, I will come back with feedbacks.
[ONE Original Android Development] Mike9966:
Just a minute. I test last and previous build and gps not work. But on cm-13.0-20161001-NIGHTLY-bacon GPS work fine. I'll be back :)

---------- Post added at 06:29 PM ---------- Previous post was at 06:11 PM ----------

1|u0_a266@android:/ $ pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 10266 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
1|u0_a266@android:/ $ pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 10266 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
1|u0_a266@android:/ $ su
root@android:/ # pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
Operation not allowed: java.lang.SecurityException: Cannot grant system fixed permission android.permission.ACCESS_FINE_LOCATION for package com.google.android.gms
1|root@android:/ # pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
Operation not allowed: java.lang.SecurityException: Cannot grant system fixed permission android.permission.ACCESS_COARSE_LOCATION for package com.google.android.gms
1|root@android:/ #
[ONE Original Android Development] NoSpamDan:
Wait a sec... where did you find Android 7 Slim GApps? Slim is not doing the GApps mess any longer. Use Open GApps or BaNks GApps linked in Post #2 please.

And please link where you got Slim N GApps.

You need to flash SuperSU first... need root to use the SU command.
[ONE Original Android Development] david72262:
[MENTION=5165039]Setting.Out[/MENTION] has been building them I'm guessing but probably off of Dan's tutorial about building your own Slim gapps

http://xdaforums.com/oneplus-one/themes-apps/revisited-slim-gapps-6-0-7-0-unofficial-t3462088/page6
[ONE Original Android Development] Mike9966:
I have SuperSU and give access su. You can see above.

I can repeat:

1|u0_a266@android:/ $ su
root@android:/ # pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
Operation not allowed: java.lang.SecurityException: Cannot grant system fixed permission android.permission.ACCESS_FINE_LOCATION for package com.google.android.gms
1|root@android:/ # pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
Operation not allowed: java.lang.SecurityException: Cannot grant system fixed permission android.permission.ACCESS_COARSE_LOCATION for package com.google.android.gms
1|root@android:/ #
[ONE Original Android Development] mustang_ssc:
Dan did you think about implement the snapdragon camera in a short future instead of the stock one included?

I know it's not a priority right now while we have the video recording problems and the early age of the rom but I'm just curious to know.
[ONE Original Android Development] NoSpamDan:
Well maybe it needs sorting upstream then.

Oh OK, you fooled me, lol. As long as you are using N GApps. :D
[ONE Original Android Development] NoSpamDan:
No... Snap apparently is not compiling... not sure

Like I mentioned, try the Camu app. It can record video in the meantime:

https://play.google.com/store/apps/details?id=com.sumoing.camu&hl=en
[ONE Original Android Development] NoSpamDan:
Fixed GPS, partial reboot menu, should have fixed Slim Recents, plus other goodies... like possible encryption support.

There no NO built-in video recording yet; I suggest to use Camu camera for now. I'm looking into Snap. Updateing's HAL zip file does not work for Slim (sticks at kernel splash).

(Link pulled because of no data connection)
[ONE Original Android Development] NoSpamDan:
Forgot to mention that the last release includes a device tree commit to add the keystore.msm8974 HAL in. We'll have to see, but with any luck, this may solve the encryption issue. If you can test this it would be appreciated. I don't use encryption.
[ONE Original Android Development] KenjiHannya:
No 2 battery icon

Config hw buttons with double amd press button work fine and good options. Battery text work fine.

Good rom ;D

Hope come soon to help us

http://review.cyanogenmod.org/#/q/s...d/android_device_oneplus_bacon+branch:cm-14.0

Tnx dude ;D
[ONE Original Android Development] fmc000:
I may be able to do this today, I need a few hours because it takes a lot of time to backup 30GB of data via adb.
[ONE Original Android Development] maxed4901:
Hi Dan,

Wooh- back from China! MIUI8 is good but needs a lot of work. back to CM AOSP builds. Tried your 161002 build on multirom as secondary with installer script modification as per [MENTION=5165039]Setting.Out[/MENTION] guide few posts back but same thing. It hangs on boot screen. this time kept for good 10-15 minutes but no cigar. as per your last update i am guessing no changes made for multirom compatibility? no prob...take ur time and hope you will make it compatible..

I had no problem installing slim6 as secondary or primary.

Cheers!
[ONE Original Android Development] fmc000:
Latest version:

encryption works

. I have Slim installed and I'm now in the process of restoring my apps / data with Titanium. Will report back.
[ONE Original Android Development] codyedmonson:
Latest version, no data connection is working for me.. Tried changing apns and all that
[ONE Original Android Development] fmc000:
Ah, me too. I thought that it was only me but now i see that I'm not alone. APN is correct but mobile data is not working at all.
[ONE Original Android Development] wozn:
bluetooth also dead here, gone back to previous :) had to quickly restore a previous build so haven't got any logs to share sorry
[ONE Original Android Development] NoSpamDan:
Well sorry folks. If it isn't one thing, it's another...

No logs to help me out?

EDIT: I've pulled the last build for now.
[ONE Original Android Development] fmc000:
I can't send logs because I have no internet connections available but it seems that netmgrd is the cuplrit. Copied from 'dmesg':

diag: invalid private data
diag: Invalid private datainit: service 'netmgrd' (pid 27502) exited with status 255
init: Service 'netmgrd' (pid 27502) killing any children in process group
init: Starting service 'netmgrd'...
type=1400 audit(1475776610.368:318): avc: denied { dac_override } for pid=27534 comm="netmgrd" capability=1 secontext=u:r:netmgrd:s0 tcontext=u:r:netmgrd:s0 tclass=capability permissive=1

this is continuously repeated.

---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------

BTW, this ROM is awesome, blazingly fast even coming from SlimSaber which is the fastest MM ROM I ever tried. However, I have found some minor bugs that I will report later, I don't want to distract the dev from some more important issues.

Congrats [MENTION=4435460]NoSpamDan[/MENTION] .
[ONE Original Android Development] NoSpamDan:
Thanks. Your information is helpful enough I think.
[ONE Original Android Development] fmc000:
Sorry to cause you so much trouble :)
[ONE Original Android Development] dragsterman:
[MENTION=4435460]NoSpamDan[/MENTION]

Which camera blobs does this ROM have? CM or Sultan's (Oxygen cam libraries+Sultan's custom HAL).
[ONE Original Android Development] NoSpamDan:
They are CM. I can't use Sultan's for mainstream ROM purposes because the base kernel, HALs and blobs all work together, and there are core differences that affect things like Ambient display.

Slim's 8974 audio, display and media HALs are not just used for bacon, and I was not able to get even a small change applied for bacon. The HALs are shared across multiple devices, and track CM .
[ONE Original Android Development] noahvt:
I just installed the latest build with BANKS gapps and my HW keys don't work at all, they and light up and the phone vibrates when pressed but nothing happens
[ONE Original Android Development] fmc000:
They work perfectly with yesterday's opengapps nano.
[ONE Original Android Development] noahvt:
I just tried opengapps as well and they still don't work, strange...
[ONE Original Android Development] dragsterman:
Thanks for the great explanation!

Noob here, but what if you use Sultan's kernel base like in your CandySiX ROM? Maybe that would work with Sultan's camera blobs?
[ONE Original Android Development] NoSpamDan:
In may, but like I said, it will break other things, some for bacon, and some for other devices.

After speaking with Sultan, I tried an Ambient display work around on Slim6, but since it wasn't going to be merged, and for various other reasons, I switched to CM HALs, blobs and kernel. This got our Ambient display working, and provides a shared path going forward with the OPO and other msm8974 platforms.

You find Sultan's kernel, HALs and blobs on my CandySiX bacon build because I am a Gerrit admin for Candy, and I merged the Ambient display work around myself. I created a board config flag that if not set, would allow Ambient to work as normal for other 8974 devices, but if set (bacon) would fix Ambient display.

There were literally 2 lines if code needed, but because this was rejected by Slim, the alternative would have been to fix all the missing Doze commits in Sultan's kernel. No thanks. I'll let CM handle the bulk kernel items.

So, is what it is. Last I heard, Sultan had the OP3, and gave his father his bacon. I'm not sure what his plans are for bacon going forward.

Peace
[ONE Original Android Development] spyd4r:
just installed the latest build with fresh download of gapps, google play services keeps crashing.. cannot setup device.

edit: also, i have 2 battery icons
[ONE Original Android Development] dragsterman:
Thanks, I see now Android ROM development is not a piece of cake. :)
[ONE Original Android Development] fmc000:
For the first point: if you're using opengapps that include google webview you may have to exclude it.

For the second point: look at post #2 (something you should have done already, BTW).
[ONE Original Android Development] spyd4r:
Thanks, BaNks Dynamic GApps cured the crashing google play services. I'll stick with those for now
[ONE Original Android Development] transvin:
How do I install this parallel to my current CM13 firmware? I have the MultiROM recovery installed.
[ONE Original Android Development] NoSpamDan:
Post 3
[ONE Original Android Development] KenjiHannya:
OpenGapps 7 Pico work
[ONE Original Android Development] david72262:
Here are logs for yesterday's no data issues if you still need them. Wasn't home so installed this am before seeing data didn't work on the forum. I'm on WiFi for most of day so leaving it installed for now everything else seems to be running good. Camera is improved over previous build.
[ONE Original Android Development] fmc000:
A few notes:

Video with Camu works but it's "jumpy" and I can't find a way to adjust some settings;

Trusted Face works fine;

AdAway must be installed systemless and after that it works just fine.

A few bugs:

slim recents crashes SystemUI;

Phone / Settings / Call Settings / IMS Settings -> FC;

Phone / Settings / Call Settings / Call barring -> FC;

QS tiles / Battery -> the "%" symbol is printed twice.
[ONE Original Android Development] codyedmonson:
Sorry for not pulling logs, for some reason when I get drunk I like to flash roms lol so no logs from last night and I'm back on my mm ROM until I get off work tonight
[ONE Original Android Development] NoSpamDan:
What build? Got a log at all? If it's the current one in Post 2, I rolled back to the previous release temporarily since data/bluetooth, etc is not working on my current build. Still sorting it out, but I"m at work for another hour or so, then have to drive home. I can hopefully sort this tonight.
[ONE Original Android Development] SirSoviet:
It seems like the battery icon in Slim doesn't scale correctly with custom DPI.
[ONE Original Android Development] darrie1:
After a reboot it is scaled properly.
[ONE Original Android Development] fmc000:
The only one I can run because of the working encryption, 20161004-1700. I cannot reproduce anymore the slim recent crash but for the other two the logcats are attached. I used "adb logcat" to collect them.
[ONE Original Android Development] mustang_ssc:
About the slim recents, did you tried long pressing them? When i installed the latest build from the day 10/04 that's how i get slim recent crashes.
[ONE Original Android Development] Walter yzw:
Can I install this ROM as a secondary ROM in multi ROM?
[ONE Original Android Development] mustang_ssc:
Search bar is your friend
[ONE Original Android Development] :
This ROM looks great. I wil try it in the weekend. But before I flash. Is it possible to flash the Stock Gapps of OpenGapps on this ROM without any errors?
[ONE Original Android Development] fmc000:
I managed to crash SystemUI with Slim Recents. Logcat taken with "adb logcat" in attachment.
[ONE Original Android Development] NoSpamDan:
No, use pico, and install the rest from the play store. Others have reported good results with BaNks GApps too.

Thanks, will look, but I could make it crash on this older build by swiping down in Slim Recents.
[ONE Original Android Development] fmc000:
Thanks to you. I've been using yesterday's build since it was released and I have to say that it works extremely fine. Once mobile data and BT are fixed it will make a perfect daily driver.
[ONE Original Android Development] NoSpamDan:
Thanks. I do agree, except for the video recording issue...
[ONE Original Android Development] fmc000:
Yup, forgot about it. At least with camu there's a partial workaround for it. BTW, when I start camu for the first time it prints the warning shown in the screenshot, then the app starts. Maybe it can be useful, I don't know.
[ONE Original Android Development] Anghirrim:
Yep me too. I used to have this issue as well on several apps.
[ONE Original Android Development] fmc000:
Bluetooth issue.

[MENTION=4435460]NoSpamDan[/MENTION] and others: please have a look at this post and report back. I had to rollback to MM because of the mobile data issue on 201004 and therefore I can't test it myself, sorry.
[ONE Original Android Development] SirSoviet:
Wasn't it already pointed out that BT on the 10-04 build was broken and was removed from downloads?
[ONE Original Android Development] fmc000:
Yes, that was exactly my point: to see if that single line was enough to fix it.
[ONE Original Android Development] LukaszBobrek:
Already in gerrit, so let's keep fingers crossed for BT issues to be fixed - https://review.slimroms.org/#/c/21163/

I do also hope that switching back to RILv10(https://review.slimroms.org/#/c/21165/) solves the problems with mobile data and then I can go for a daily with Slim7 (despite camera recording is broken)
[ONE Original Android Development] fmc000:
Very promising indeed. Thanks for pointing that out. BTW, how about this?
[ONE Original Android Development] NoSpamDan:
Thanks, got this from another dev buddy yesterday while I was at the doctor's.

Yes I pushed that change after verifying it fixed BT.

No progress so far on the mobile data. I fear that one or more of the 200 telephony commits (both merged and open) may be to blame. Good times.

Not feeling stalked on Gerrit at all... :p
[ONE Original Android Development] LukaszBobrek:
Well, if you prefer I can stalk you on github instead :P

But seriosly, thanks for a great job with making slim7 alive for OPO ;)