yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] fluffymadness:
I tried encryption again with the Slim-bacon-7.1.0.build.0.1-DEV-DM-20161208-0806 build.

Entering a pin before-> then encryption

But still the data is corrupt.

I tried getting logs with

adb -d logcat>mylogfile.txt

when entering a password...problem is that the debug bridge doesn't seem to be active, when I'm not authorized with the system.

Had the same problems with darkobas omni rom before...encryption just doesn't seem to be working. At least not creating the encryption via the nougat system.

I'm not rooted by the way, also no multirom, and I can test a bit...since there's nothing on my phone anymore ^^

Edit: interesting...after a reboot and entering the password again it is working....O.O

So...after the encryption process and entering the password for the first time...I got a data corruption error...rebooting again let me enter the password, any ideas?

Edit:twrp doesn't seem to care about my password, I can decrypt my system with my pin when starting the phone, but in twrp I get a decryption failed when entering the password
[ONE Original Android Development] TbMa:
Did someone tested encryption with root on last build?
[ONE Original Android Development] NoSpamDan:
Regarding encryption... I have found some changes that may help, and I'm trying to cook them into a first 7.1.1 build on my system here. I'll post for testing/confirmation when it's complete.

Depending on build errors, it could be as little as 1 hour or as long as * hours. :silly:

Stay tuned...

EDIT: Here is the build with decryption and selinux patches. I'm not sure about running this one as a secondary ROM just yet.

Slim-bacon-7.1.1.build.0.2-DEV-DM-20161210-2248.zip
[ONE Original Android Development] fluffymadness:
I sadly still have the same problems with the new build :( . Entering the password only works after the second boot when freshly encrypting the device and

TWRP still can't decrypt my data when entering the pin.

Can anyone reproduce the twrp bug, maybe its my twrp version.

I entered a pin before encrypting my phone...if you don't do this i think the password will be default_password for decrypting the data.
[ONE Original Android Development] fmc000:
Working good !! It's still running permissive Selinux, though. Extremely fast first boot, less than three minutes with a dirty flash of ROM, today's Opengapps nano and SR5 SuperSU (all this, of course, on an encrypted phone).

Congrats, you're damn good!

Edit: the fast boot is because there are no framework updates between 7.1 and 7.1.1 therefore there's no app optimization. Actually, there are no app versions changes at all between the two versions.

Also, 7.1.1 fixes the phone app FC that happened during the startup process when the system asks for the decryption pin - bug present in both 7.0 and 7.1 .
[ONE Original Android Development] fluffymadness:
Did you encrypt fresh with nougat or are you using the encryption from your previous version of android ? Are you using a system pin for encryption ?

And last question :), whats your twrp version? Maybe I'll find out whats causing the problems on my side.

Thx
[ONE Original Android Development] fmc000:
Encrypted with MM - used with 6.0.1 - 5.1.1 - 6.0.1 again - 7.0 - 7.1 and now 7.1.1 . I use the same PIN for encryption and unlock . TWRP is latest official, 3.0.2-0 .
[ONE Original Android Development] fluffymadness:
Ok. I'm also on 3.0.2-0...I guess my twrp version is not the problem then.

This sounds quite similar to my issue....https://forums.oneplus.net/threads/twrp-encryption-password.432114/

edit:

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/588

This should contain a fix, I'm trying that out now

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/596#issuecomment-215315628

edit: I can confirm, after flashing the modified twrp image from the link above I can successfully mount my data in the recovery mode with the pin I used for the encryption of my device.

---------- Post added at 02:57 PM ---------- Previous post was at 02:28 PM ----------

Nice. Looking forward to the enforcing builds now that I've found my daily driver.

Was using Slim back in the old days with my Galaxy S i9000.

What I appreciate most is, that this rom doesn't come with unnecessary stock apps, so that I can choose what I like to use, without having unused things flying around in the appdrawer.
[ONE Original Android Development] NoSpamDan:
Hmmm... so let me get this straight. It is the DEcryption that is an issue, not ENcryption? This sounds like a DEcryption issue.

[MENTION=6546557]fluffymadness[/MENTION], are you using a PIN or Password to encrypt/decrypt?

I just checked, and while I can't speak for the official TWRP source yet, the MultiROM TWRP source I used for the recent updates DOES contain this fix. So could you try the MultiROM v3.0.2-0 TWRP I posted here in the MultiROM bacon thread and see if decryption works properly? You don't need to flash or use MultiROM with this recovery if you don't want to...

I'm wondering if [MENTION=791219]fmc000[/MENTION] is using the MultiROM recovery too since it appears his setup is working to decrypt the /data partition...?
[ONE Original Android Development] fluffymadness:
I'm using a pin to encrypt/decrypt.

When encrypting from a fresh install I set a pin before.

The next step was encrypting, the device reboots and then I have to enter my pin.

After entering the pin, it says password correct, but cannot decrypt, the data is corrupted.

If you reboot again and enter the pin for the second time it works.

So first time boot after encrypting the system doesn't work for decrypting.

Second boot, decryption with the pin works.

Decrypting in recovery also didn't work with the standard twrp 3.0.2.0 for me.

https://dl.twrp.me/bacon/

The build date for this version is April 2016.

After entering my pin, I got a decryption error.

Flashing the twrp build from the git thread I linked allowed my to mount data in twrp after entering the pin.

So atm everything is working fine for me.
[ONE Original Android Development] NoSpamDan:
So...

1. Have you tried my MultiROM TWRP I linked?

2. Has the "official" TWRP source been updated with this patch? Based on the build date it may not have been... 2016-04-04 11:53:21 EDT
[ONE Original Android Development] fluffymadness:
I've now installed your multirom recovery via adb flash, but sadly it doesn't work for me. Password failed, please try again!

edit:

https://gerrit.omnirom.org/#/c/17716/1/crypto/lollipop/cryptfs.c

according to the git post I've referenced before, this should be the fix, thats implemented

in the custom twrp build I've flashed.
[ONE Original Android Development] fmc000:
No but please note that I encrypted my phone many months ago with an Omni-based ROM that wasn't using the current encryption libraries but an earlier version, so maybe this can be the reason. Is there any way to retrieve the "version" of my encrypted volume?
[ONE Original Android Development] NoSpamDan:
Then that fix is not what's causing your issue because it is in my MultiROM TWRP.
[ONE Original Android Development] fluffymadness:
Oh ok...no clue then
[ONE Original Android Development] NoSpamDan:
This may seem obvious, but you did reboot to recovery after installing the MultiROM one, correct?

EDIT: This is the commit in the TWRP MultiROM source I'm using:

https://github.com/MR-op3/android_bootable_recovery/commit/9f1f2f744b6593f2d05bec571eb66485a21a47ba
[ONE Original Android Development] fluffymadness:
Yes of course. I flashed the multirom recovery (TWRP_multirom_bacon_20161210-02) you've linke me via fastboot flash recovery <filename>

I pulled some logs from the two recoverys:

Working Recovery

...
Using scrypt with keymaster for cryptfs KDF
Trying to convert ascii string of odd length
Failed to convert passwd from hex, using passwd instead
[B]keymaster module name is Keymaster QCOM HAL
keymaster version is 3
Found keymaster0 module, using keymaster0 API.[/B]
Signing safely-padded object
load_crypto_mapping_table: target_type = req-crypt
....

multirom recovery

...
Using scrypt with keymaster for cryptfs KDF
Trying to convert ascii string of odd length
Failed to convert passwd from hex, using passwd instead
[B]could not find any keystore module[/B]
Failed to init keymaster
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
...
[ONE Original Android Development] fmc000:
FWIW, this is what I get with the standard 3.0.2-0 , i.e. without the patch you're talking about:

Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex
kdf failed
failure decrypting master key
Failed to decrypt master key
crypt_ftr->fs_size = 117021080
Using scrypt with keymaster for cryptfs KDF
keymaster module name is Keymaster QCOM HAL
keymaster version is 3
Found keymaster0 module, using keymaster0 API.
Signing safely-padded object
get_dm_crypt_version flag: 1, name: 'req-crypt'
load_crypto_mapping_table: target_type = crypt
load_crypto_mapping_table: real_blk_name = /dev/block/mmcblk0p28, extra_params =
Password matches
Data successfully decrypted, new block device: '/dev/block/dm-0'
[ONE Original Android Development] fluffymadness:
Thx for the log.

The unpatched recovery fails, because the fix is not included. The Keystore module however is found.

printf("Failed to convert passwd from hex, using passwd instead\n");,
master_key = strdup(passwd);

The multirom recovery has the fix but somehow doesn't find the keystore module
[ONE Original Android Development] fmc000:
BUG with the 7.1.1 version: I don't get the "answer" button when I receive a call. I have to swipe down and answer from the notification bar. The "close" button is present, though, so the call can be closed normally.
[ONE Original Android Development] suryachandranr:
Also no call log available.
[ONE Original Android Development] fmc000:
Confirmed. I don't have any log for the phone calls I did today.
[ONE Original Android Development] fmc000:
Alpha Build

I noticed that there's the first Alpha build on SlimRoms.org . [MENTION=4435460]NoSpamDan[/MENTION], can you please tell us what are the differences between the two versions? I'm confused...
[ONE Original Android Development] NoSpamDan:
Thanks, I'm trying to investigate this.

See attached image for Settings > SystemUI Tuner > Power notification controls. I played with the Phone app's settings after enabling this, and set it to 5, but I haven't migrated fully to N as a DD.

Sure. My own DEV-DM builds have been including unmerged commits for the most part. The last 0.2 Alpha "official" build posted on the Slim web site has had much of the open commits merged now, so they are almost identical.

Thanks for the log. This is exactly the kind of information needed when reporting bugs... You get a GOLD STAR! :D :good:

Seriously, thank you.
[ONE Original Android Development] fmc000:
Nice trick for the phone notification. And thanks for the star ?

Edit: the trick doesn't work when answering a call. No answer button and no notification over the incallui. I'm trying to collect a logcat for this
[ONE Original Android Development] evronetwork:
So this rom is not for daily driver I suppose?

I'm always looking for slim roms, Cyanogenmod got fat over the years 416.19MB for the latest update? damn and that's without GAPPS of course
[ONE Original Android Development] david72262:
This rom works perfect for me
[ONE Original Android Development] csabreu:
I've been using it for the past 2 days. Almost all is fine until now. No random reboots and just a few sparse FC when changing some settings on specific menus. Nothing detrimental, however. Functions perfectly as a daily driver to me. Works perfectly fine with my ZW2 and car bluetooth as well. Battery seems good as well. Not as fast as Pure Nexus, but battery seems better.
[ONE Original Android Development] NoSpamDan:
Yes, you're welcome for the star... :p

I have a build brewing that should fix this. Some Dialer commits it seems are needed for incoming call notification. The "trick" is just an N feature to fiddle with. I wasn't sure if it would help or not.

I'll share the build if it's good, and incoming calls are fixed. Super swamped at work this week, so finding time to flash my main communication device is going to be challenging. Maybe at lunchtime tomorrow (today, lol). We'll see.

Peace
[ONE Original Android Development] evronetwork:
Is NFC working? (I've got a ring and I unlock it by just grabbing it to my hand :p )

EDIT: Is the camera working as expected? if you take a picture during low light with flash does it halve the image or it's proper as it should? (one picture with low light and flash enabled would show this issue ..if it exists)
[ONE Original Android Development] csabreu:
Android beam works fine, so I suppose everything should work as expected NFC wise.

EDIT: no halving of picture with low light and flash either.
[ONE Original Android Development] noname115:
Hi.. Is anyone having problem using WiFi hotspot? I keep getting this error status once I turn it on. I'm using the latest build. Here's a log. Hopefully I capture it correctly..
[ONE Original Android Development] evronetwork:
Cool, good to know ..I'll give it a go on weekend or earlier if I have spare time
[ONE Original Android Development] cikenkari:
Hi,

Could you upload slimlauncher.apk, thanks
[ONE Original Android Development] NoSpamDan:
Thanks I should have this fixed in my latest builds. Just trying to get the dialer incoming answer stuff fixed. We have call log fixed it seems already.

Stay tuned.

EDIT: In the meantime, you can try flashing the attached kernel img in TWRP to see if it fixes hotspot.
[ONE Original Android Development] NoSpamDan:
Hotspot seems to be working for me with the kernel I posted in my previous post. Anyone else?
[ONE Original Android Development] NoSpamDan:
New DEV-DM build

Fixed WiFi hotspot, Call Log, and Lock screen call answering... Call barring still FCs, but will most likely be removed anyway.

If you dirty flash, make sure you wipe data for your Phone app because there was a database upgrade and you need to clear old, incompatible data.

Slim-bacon-7.1.1.build.0.3-DEV-DM-20161218-1703.zip
[ONE Original Android Development] frogger55:
tested and confirmed working, ta :)

oops, sorry a bit slow - you have new build up. thanks again for your work!
[ONE Original Android Development] :
Can't see to find setting to tweak power menu, just wanted to hide ringer profile from there. Aside from this everything is awesome
[ONE Original Android Development] Claudiosvs:
Hardware button remapper is buggy. Otherwise I haven't run into any issues yet. Any chance for a toggle to show the IME selector? I always found this notification incredibly annoying, but I don't want to hide all system notifications. CM has the perfect little toggle for this. Omni has it too. Thank you for your work maintaining this device.
[ONE Original Android Development] -Fedde-:
Sorry, for a noobish question, how do I wipe the data for the phone app only?
[ONE Original Android Development] NoSpamDan:
Go to Settings > Apps

In the upper right corner, touch the three dot hamburger menu

Select "Show system"

Scroll to the Phone app and open it

Select Storage > Clear data
[ONE Original Android Development] -Fedde-:
Ah, thanks and done!

Obvious. I was looking around TWRP actions... ;)
[ONE Original Android Development] evronetwork:
Why the tittle doesn't say 7.1.1 android? just wondering :P

btw I'm willing to help with the Greek translation e.g. in the power menu? (basically everywhere needed) if you are interested [MENTION=4435460]NoSpamDan[/MENTION]

P.S. The only thing I'm missing from other roms is the "Recents" with the first hardware button(menu), the "back" buttom to kill the apps and not sure if it has a circle battery with percentage inside the icon(didn't search that one, maybe it has :p )
[ONE Original Android Development] NoSpamDan:
You can assign different HwKey actions in

Settings > Navigation > Hardware buttons...

After enabling the settings, hit the rest icon once before changing them to make sure they take on the first try.
[ONE Original Android Development] :
Kernel is great, no bugs encountered till now. I want to request a feature i.e kernel undervolting. Pls respected op can u add this.
[ONE Original Android Development] evronetwork:
Yeap, I was about to strike my message(edit), for back key and circly battery :p ..and saw your message too heh

EDIT: Done

EDIT2: Although I've chance the back key to kill the app and home key for google now, the rom doesn't honor my change - It's like I didn't chance anything(tried to do a reboot ..Windows solution ahahahh still nothing)

Things I did, Full wipe, flash rom, flash gapps(pico), flash supersu and install ex explorer ..nothing more so far :D
[ONE Original Android Development] csabreu:
Odd, I've the same exact settings except for normal press in back key to "back" and home double tap to "recents", and all is working as expected. I suppose you have reset all entries to default before applying the changes like [MENTION=4435460]NoSpamDan[/MENTION]an advised?...
[ONE Original Android Development] evronetwork:
Aren't they in their defaults since it's freshly flashed? :p

EDIT: Did a reset as you suggested, nop still the same :(
[ONE Original Android Development] csabreu:
In principle. But what I tried to say is to set them, toggle the switch "Enable custom actions" back to OFF and then ON, reset all settings and finally readjust everything to your liking and see how it goes.
[ONE Original Android Development] evronetwork:
Well tried to reset them, didn't disable them. Lets try one more time :p

EDIT: I've disable them, enable them and reset them ...now they work (ahahhaah, weird bug but at least there's a workaround :) )

P.S. Is there an option to make the settings dark(black or gray or something ahahah)? (yeah I'm asking a lot but in the dark that white settings are like headlights to my eyes :p
[ONE Original Android Development] NoSpamDan:
No dark mode... Yet
[ONE Original Android Development] evronetwork:
damn :p

The offer about the Greek translation still stands :D
[ONE Original Android Development] csabreu:
Good to know that it worked :)
[ONE Original Android Development] evronetwork:
Yeap, thx ..glad it worked too. Hope this would be fixed in newer revisions so people won't try to guess what's going on :p
[ONE Original Android Development] alroger:
It's been mentioned several times.
[ONE Original Android Development] :
Just flashed it and after seeing boot image I already fell in love with this ROM xD.

ROM looks really neat and simple which i like (just like stock android) and smooth too.

Good job

Edit 1: Clean Flash with Gapps: Enable navigation bar and disable hardware buttons, Menu visibility in navigation bar to 'never'. While typing Navigation bar shows 'menu' and then disappear bringing navigation bar little to right side.

But this does not happen if i flash without Gapps.

1st one without Gapps

2nd one with Gapps
[ONE Original Android Development] NoSpamDan:
Define "buggy"...? There is a known quirk, but it works, as long as you initially use the work-around I posted.

Not sure what will happen with the IME selector.
[ONE Original Android Development] NoSpamDan:
Thanks... Probably where the 3 dot menu or IME selector might show up. I'm guessing you have both AOSP keyboard and Gboard (or another keyboard) installed?

What happens if you touch in that left area where it is shifted? Do you get a menu?

EDIT: This appears to be a known issue: https://bugs.slimroms.org/issues/127
[ONE Original Android Development] :
I didn't had any other keyboard installed when it happened with Nano or higher gapps package.

It didn't happened with Pico gapps. But when i installed Gboard it started happening again.

No, i don't get any menu. It just appears for a second and navigation bar shift to the right.
[ONE Original Android Development] fluffymadness:
can anyone tell me if the actual build is still permissive?
[ONE Original Android Development] evronetwork:
It's a 75 pages thread and I just jumped in, this is a bug which is not mentioned as a problem. Surely you don't expect me to read all the pages for any possible bug/glitch right? :p
[ONE Original Android Development] ziepicwaffle:
I mean a quick search and I found it on page 58...
[ONE Original Android Development] NoSpamDan:
Not trying to gang up on you here, but please note that post 3 covers what's working or not. I did mention the HwKey Rebinding reset there. :)

A good rule of thumb is to always read at least the first page and last few pages of a newly visited thread, if nothing else... :cool:

This HwKey quirk will hopefully be sorted soon. Thanks everyone for keeping it friendly in here. :good:
[ONE Original Android Development] pbergonzi:
Yes it is still permissive.
[ONE Original Android Development] evronetwork:
Knowing what you were looking helps, if you don't know bet you'll need to read all pages :p

If it's noted in post 3 it's my bad for not checking it out, anyway it's not big deal although it would be best if it's solved for new people comming to this rom(about the translation I've mention a couple of times, should I send you a pm? do you want a translation or you're not interested - I've got no issue with English but I prefer to watch things in my native language :D)
[ONE Original Android Development] NoSpamDan:
No worries.

As for the translation, thanks for the offer. I think we use crowdin.

Let me check in our dev chat and I'll PM you if you can help. Thanks!
[ONE Original Android Development] evronetwork:
I had to ask for access to the translations, gain access and did 41->62% so far(its a long way until 100%) :p

EDIT: [MENTION=4435460]NoSpamDan[/MENTION] Checked the charging animation(when phone is turned off), it has this lousy animation from old cyanogenmod, darkobas rom use the same in the past, after my recommendation he made the battery animatio bigger(from that tiny it was) and added a percentage, after multiple recommendations from me(cyanogenmod jira and 2 years delay) the cyanogenmod now has the same BIG good animation as CyanogenOS ...anyway you can get your hands on that?

Cyanogenmod is open source so it's not stealing :P
[ONE Original Android Development] NoSpamDan:
The powered-off battery animation? Hmmm can you link the commits? I'd be happy to take a look.
[ONE Original Android Development] fmc000:
Judging from the changelog it seems that the latest alpha contains all the dialer fixes and something else. [MENTION=4435460]NoSpamDan[/MENTION], [MENTION=3877985]prbassplayer[/MENTION] can you please confirm?
[ONE Original Android Development] :
I don't know if you already knew about this but i have found a workaround. I've enabled just one keyboard (Gboard) and disabled others like AOSP keyboard, google voice typing. This has stopped that navigation bar shifts.

Also, can i dirty flash between DEV-DM builds and alpha builds that are on slim website ?
[ONE Original Android Development] prbassplayer:
Yup has the Dialer fixes
[ONE Original Android Development] TbMa:
Already asked few pages ago but didnt got exact answer.

Someone using encryption please specify are you using SuperSU or not?

I am on encrypted cm-13 and really wanna jump to slim but i am afraid of losing data pointlessly, because no-root is deal breaker for me.
[ONE Original Android Development] fmc000:
Yes I am. Latest alpha with encryption and latest SuperSU stable. Perfect daily driver.
[ONE Original Android Development] evronetwork:
Yeap the powered-off battery animation :D ...well tried to find my post of JIRA(the complain) ..not the commits themselfs

and just find out that CM is dead, damn!(sorry about my language). This was posted on 24/12/16

https://www.cyanogenmod.org/blog/a-fork-in-the-road

So cyanogenmod is dead guys and this is all thanks to the guy who turn CM into CyanogenOS aka CyngnOS. Hope something else to replace cyanogenmod, I mean most roms rely on that(for something), for kernel...firmware you name it

RIP CyanogenMOD, long live the king(Lineage Android Distribution) :P

http://lineageos.org/Yes-this-is-us/