yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] drexciya:
Noticed that 'advanced reboot' option in security settings doesn't work for me. Not a biggie since can reboot to recovery by other means. Just reporting for the record.
[ONE Original Android Development] fmc000:
Mentioned by the OP in post #573
[ONE Original Android Development] JAY28W:
Yep, exactly what I am getting, too. I even tried [MENTION=4435460]NoSpamDan[/MENTION] GApps that he said he used, open_gapps-arm-7.1-nano-20161109.zip, and had it.

Keep me posted, if you would, if you find a solution or have some ideas to try. I'm not real advanced so off hand I don't have any other ideas.
[ONE Original Android Development] fmc000:
Have you tried not to enter the setup wizard at all? I mean, skip all the procedures and when you're at the launcher screen, activate wi-fi and configure your google account using the Play Store or the gmail app. This should work without issues, with the only drawback that the automatic Google restore probably won't work (I've never used it, though).

Also, you can try a more recent gapps that comes with an updated Play Store, an updated Google App and the 10.x Play Services with the correct 480dpi (Yesterday's or Today's should work).
[ONE Original Android Development] JAY28W:
Thanks for the suggestion. I'll try again but skip the restore wizard, which it sounds like you're suggesting. Also, I had tried the most recent Open GApps ARM Pico and Nano before trying the one that [MENTION=4435460]NoSpamDan[/MENTION] had specifically mentioned.
[ONE Original Android Development] chainer1:
Awesome work, tested the nougat build and I think this is the only rom out there that doesn't come with all the stock apps preloaded and I really like that.

Just out of curiosity, is there an ota updater planned for future versions of this rom ?
[ONE Original Android Development] FunkyRasta:
Well , same stuff on new build. I guess it is the issue with 7.1 and GAPPS. I've choosen to set-up device as fresh, didn't take too long to get everything sorted.
[ONE Original Android Development] fmc000:
Actually my suggestion was to skip everything related to Google during the first boot, not only the restore wizard.
[ONE Original Android Development] JAY28W:
Got it. Call me a little dense, but typically I'll catch on at some point.

Clean flashed ROM, rebooted into OS. (no google play, no ability to add google user acct or email)

Rebooted to Recovery, flashed latest Nano GApps, rebooted to OS. Config'd WiFi.

Added Google Account

Accessed Play Store and added apps.

Looks like this method works well, except the I'd prefer using the setup wizard to reload accounts & apps but no biggie.

I don't have time right now to reinstall and config everything, I restored from backup and will repeat above later and finish the install.

Thanks a ton for your help. Not only is this helping me get to the next version but I also learned another trick.

jay
[ONE Original Android Development] _harmonic:
Just curious if anyone has been able to get OK GOOGLE detection working with Google Assistant in this latest 7.1 build.
[ONE Original Android Development] Chris.C:
No have tried all sorts but while the mic works, OK Google needs new hearing aids, as it fails
[ONE Original Android Development] fmc000:
[MENTION=4435460]NoSpamDan[/MENTION]: do you think you could update the kernel to 3.4.113 for the next release?
[ONE Original Android Development] Chris.C:
Anybody got Substratum working with 7.1?

Mine goes into boot loop after installing the layers and rebooting.. Not a big deal am loving back on Slim
[ONE Original Android Development] Anuj Mahajan:
Hi,

I flashed this ROM but when I am setting up the Wifi, the "connect" option is faded and I cannot connect to any network after entering the details. Please help
[ONE Original Android Development] zjxpot:
http://xdaforums.com/showpost.php?p=69749644&postcount=1431
[ONE Original Android Development] nartex2:
Blutooth OnStar Interface Issue?

Blutooth won't connect to Onstar. Connects to other devices fine. Did the radio change on 7.1. This ROM has been spectacularly stable in the two months of use. Sorry, no logs; because if it's just me it's obviously my wipe and flash procedure; no use having anybody digging through logs for a problem I caused.
[ONE Original Android Development] Chris.C:
Thanks :)
[ONE Original Android Development] zjxpot:
I might ne wrong, I also read this http://xdaforums.com/showpost.php?p=69751078&postcount=1433 not sure wht to make of it..
[ONE Original Android Development] fmc000:
I just noticed that the double "%%" is still present in both the battery stats screen (settings and QS tiles).I saw a screenshot in one of the various CM thread with this fixed.

It's hardly a issue, I know, but i thought it was worth reporting nonetheless.

Inviato dal mio SM-T719 utilizzando Tapatalk
[ONE Original Android Development] Chris.C:
I have just re-installed substratum selecting all but the system layers and it works just fine. I know have my favourite davyannhilation domination black theme back we'll almost all back

Edit: Again [MENTION=4435460]NoSpamDan[/MENTION] you are the Man Slim7.1 is great
[ONE Original Android Development] JAY28W:
Finally got a fresh install of the current ROM and current GApps. Ended up wiping all and formatting data. Seems to work like a champ now.

I did notice that the initial screen on bootup, I think it is the Get Started, with the Vision Settings in lower right, this time was a tad different than prior to this install. Only 2 options on the bottom, previous attempts had 3, and the next screens would not give me the option to restore from account. Same ROM, same GApps. I wish I had paid more attention to these details. Whatev... it seems to be working fine now.

Thanks for the assist.
[ONE Original Android Development] tye_time:
Going to give this a flash at the weekend :)
[ONE Original Android Development] IO13:
Hi

this ROM doesn't work in multirom like secondary ROM?

I've SlimRom MM like primary, I've flashed this one like secondary but doesn't start.. OPO freeze on Boot screen
[ONE Original Android Development] consolation:
I'm curious, what's stopping SELinux being set to "enforcing?"
[ONE Original Android Development] NoSpamDan:
Try it if you like?

It should work but I haven't had time to fully test it with the video camera nonsense on 7.0 and 7.1...
[ONE Original Android Development] IO13:
somebody can confirm me that Slim7 doesn't work on multirom?
[ONE Original Android Development] molonad:
I tried, i had few force closes, for example when opening Developer options (for me very important) and for now i cant use nougat as primary. Nuclearom has it already fixed and it doesnt have any problems when Flashing as secondary. Maybe there will Developer find solution to get fully compatible rom for multirom, if he is interested.
[ONE Original Android Development] LTMendarynas7:
Hey guys, how's battery life compared to Slim6 weeklies?
[ONE Original Android Development] k3vink3vin:
FYR my phone is using around 0.6% / hour when idle with location disabled, around 1% / hour when idle with location enabled. Haven't really paid attention to screen-on time and all that...

BTW, sometimes my phone won't switch to cellular data after wifi got disconnected.

Toggling airplane mode didn't help, I have to reboot to restore internet connection over cellular data.

Anyone else experiencing this?
[ONE Original Android Development] -Fedde-:
Yep, same here. But only sometimes..
[ONE Original Android Development] _harmonic:
Happened to be a couple of times as well. Not sure of the cause
[ONE Original Android Development] fmc000:
You may try a different firmware.
[ONE Original Android Development] -Fedde-:
Well, it doesn't bother me enough ;)

I do like the ROM very much
[ONE Original Android Development] fmc000:
I meant firmware as in modem (baseband) - tz and so on, not ROM.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] tye_time:
Never used Slim 6, but i am getting over 5 hours SOT with 48 hours of usage which i find to be on par with what i got on darkobas 6.0.1
[ONE Original Android Development] ninjasumit:
Battery stats and graph please.
[ONE Original Android Development] tye_time:
I didn't take screenshots, but I will get some of this charge cycle as i think it should be similar.
[ONE Original Android Development] kingwp1:
Does this ROM have a screen timeout quick settings button? For some reason they left it out of the CyanogenMod 7.1 build, and I use it all the time.
[ONE Original Android Development] fmc000:
No.
[ONE Original Android Development] tye_time:
Not a true reflection as I usually charge my phone at about 8% - but I could easily get 5 hrs + with 25% left!
[ONE Original Android Development] fritzcola:
Somehow my custom buttn actions dont work and how to get rid of the Onmi Recnet?

Otherwise, nice rom!!
[ONE Original Android Development] se7enlyn:
In hardware buttons settings page, Press the reset button at the top right of the screen, then set your actions

Go to recents app panel settings and disable slim recenta and enable running apps
[ONE Original Android Development] dataq23:
Would have been a great rom if camera worked.

Each camera app force closes.

Also the hardware buttons custom settings don't apply.
[ONE Original Android Development] alroger:
Would be a great user if you read the thread. (all works)
[ONE Original Android Development] gianton:
Anyone knows how to disable NFC, setting is enabled and greyed out. I get huge wakelocks from NFC service... running latest build all stock.
[ONE Original Android Development] fmc000:
Fwiw, I don't have this problem and nfc is disabled (never used). I use a different firmware but I doubtthat this is relevant. Maybe you have some nfc relayed apps installed that may be playing bad with it?

Inviato dal mio SM-T719 utilizzando Tapatalk
[ONE Original Android Development] gianton:
No nfc apps installed, I have freezed NFC service.apk with TiBu for now and charging it to 100%. Will check out battery life again and report back if that solved the issue.
[ONE Original Android Development] fmc000:
Another test: with the apk frozen, power off the device and then on (not reboot and without the charger). After the device has fully booted, check the NFC status, disable it if you can and if all goes well you can unfreeze the nfc service.

Also,

dmesg|grep -i nfc

immediately after boot may give some more hints.
[ONE Original Android Development] NoSpamDan:
OK here... sorry it's been a while. I have been keeping tabs on my threads but have been out of the country on vacation and last week 900 miles from home working 14 hour days...

For whatever reasons, we missed the first Alpha weekly release on the Slim site, BUT you folks are in luck.

This build has fixed touch key backlights timeout (touch lights turn off with screen), working reboot menu, Snap camera is the default included camera now, new boot animation and more. NFC should be a non-issue.

Make sure you make a nandroid, and use a 7.1 GApps package... oh, and enjoy!

Slim-bacon-7.1.0.build.0.1-DEV-DM-20161204-1932.zip
[ONE Original Android Development] fmc000:
I'm not familiar with the alpha / weekly builds. Is it similar to the CM nightly process? One more question, what happened to this commit?
[ONE Original Android Development] Artificialkid47:
Hardware buttons dont work. I clean flashed. Do Anybody has the same problem?
[ONE Original Android Development] LastLeg:
Settings -> Navigation -> Hardware Buttons

Long press doesn't seem to take settings. Long Press home is Recents, Menu is Google Now/Now on Tap. I like to set those the other way around... I did and it stayed the same. Not a major bug, as long as I long press the right one.

Otherwise great ROM.
[ONE Original Android Development] fmc000:
In the previous version you had to reset the button mappings with the top right icon, then it worked. Have you tried if it's still applicable?
[ONE Original Android Development] LastLeg:
Awesome! That fixed it!! Thanks so much!!
[ONE Original Android Development] NoSpamDan:
Nothing "happened" to it; it breaks things and is not ready yet. I already tried it... ;)
[ONE Original Android Development] fmc000:
LOL, it looked so promising ;)
[ONE Original Android Development] fmc000:
Do you remember this old post of mine:

That happened when I first flashed Slim7, the test release you prepared for me to test the encryption, and it has been like that until today. The latest release actually "fixed" this problem as now my BT address is exactly the same of my Wi-Fi address (!!)

Does this happen to anyone else? I just noticed it because my phone wouldn't pair with my car BT this morning, I had to reset and pair again and it seem to work, although I did not test phone calls and music streaming.

Any ideas?

Apart from this, everything works, snap camera is a very welcome addition and the new boot animation is really cool. As there are no framework modifications in this release, there's no app optimization at all with dirty flashing with no wipes (not even hidden by the bootanimation) and the first boot is almost immediate.
[ONE Original Android Development] tye_time:
I customised the on screen software buttons today so long pressing the home button turns the screen off. was missing the double tap to sleep, but this is better!
[ONE Original Android Development] fluffymadness:
I guess encryption is not working...at least for me :/

It encrypts, but after a reboot when entering the pin:

The password you've entered is correct but the data is corrupted....
[ONE Original Android Development] Bobbi lim:
[MENTION=4435460]NoSpamDan[/MENTION] I tried compiling Slim 7 today and yesterday and have been encountering an issue.

Any idea how to solve this?

[ 3% 1048/31178] target Java: core-al...RARIES/core-all_intermediates/classes)
FAILED: /bin/bash /media/bobbi/DATA_ROM/ROM/Slim7-Bacon/out/target/common/obj/JAVA_LIBRARIES/core-all_intermediates/classes-full-debug.jar.rsp
libcore/dalvik/src/main/java/dalvik/system/ZygoteHooks.java:53: error: cannot find symbol
System.closeLogSockets();
^
symbol: method closeLogSockets()
location: class System
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
[ 3% 1048/31178] Aidl: framework <= f...a/android/media/IVolumeController.aidl
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/media/bobbi/DATA_ROM/ROM/Slim7-Bacon'

#### make failed to build some targets (03:21 (mm:ss)) ####
[ONE Original Android Development] LucentBirch:
Is there autofocus clicking on the camera here?
[ONE Original Android Development] NoSpamDan:
Unless something broke encryption in ng7.1, [MENTION=791219]fmc000[/MENTION] has tested it on ng7.0 and I thought it was working. I'm going to need logs since I don't use encryption.

You can temporarily revert this: https://github.com/SlimRoms/android_libcore/commit/1239eba65b84e7724a061b97e1dcebee826ce855

More details please
[ONE Original Android Development] LucentBirch:
When recording video there is a clicking sound on nearly all 7.1 Roms it seems.
[ONE Original Android Development] NoSpamDan:
New build, for those interested... Going forward I've set SELinux to enforcing, and...

The build will now flash in MultiROM as a secondary ROM

.

Make a nandroid backup, and please provide logs since there could be some SELinux denials I have not seen or caught yet. If you want to switch SELinux to permissive to see if that's causing an issue, you can:

Open a terminal window or command prompt on your computer (or open a terminal on your device directly; there are apps for this).

Type adb shell. Acknlowledge any root prompts on the device.

Type su to switch to root user.

Type setenforce 0 to set SELinux to permissive, and setenforce 1 to set SELinux to enforcing.

Here's the build. Enjoy!

Slim-bacon-7.1.0.build.0.1-DEV-DM-20161205-1524.zip
[ONE Original Android Development] NoSpamDan:
Yes I've seen this. Try switching the focus mode to something other than Continuous...
[ONE Original Android Development] fmc000:
Works still fine for me but please note that I encrypted my device with a MM ROM months before switching to N, I didn't encrypt my phone with Slim7 .
[ONE Original Android Development] mp3deviant721:
This doesn't have notification/battery LED controls does it? The battery light is annoying at night. Lol
[ONE Original Android Development] LucentBirch:
Well it even happens on some 13.1 Roms except for sultan's...
[ONE Original Android Development] NoSpamDan:
Agree, I'll look for the commits once the 7.1.1 updates settle down.
[ONE Original Android Development] dharmabm:
What are you using for Gapps? Last I tried beanstown's 7.x.x mini didn't work for me
[ONE Original Android Development] david72262:
Slim gapps work well for me

http://xdaforums.com/oneplus-one/themes-apps/revisited-slim-gapps-6-0-7-0-unofficial-t3462088/page23
[ONE Original Android Development] dharmabm:
Thanks for reminding me of that, I was actually going to build my own from PN but the opengapps worked for me this time. I am curious what Dan is using though
[ONE Original Android Development] fmc000:
This release is unable to mount my encrypted /data . I'm restoring my nandroid now (fingers crossed...)

Edit: restore went fine but I noticed that I lost my taskbar and button customization, the Developer Option setting and the Slim Recents settings. Aren't they kept within /data ?
[ONE Original Android Development] suryachandranr:
Even battery circle setting also reset while restore from nandroid backup. This happened early builds also.
[ONE Original Android Development] fmc000:
Yes, that is what I meant with "taskbar customization". My question is why is this happening? We're performing a full /data restore, so...
[ONE Original Android Development] NoSpamDan:
open_gapps-arm-7.1-nano-20161109.zip

Did you try setting SELinux back to permissive?

Any logs to help?
[ONE Original Android Development] fmc000:
How can I do that? It doesn't boot...
[ONE Original Android Development] NoSpamDan:
Hmmm...

Did you try the previous ROM version, which was still permissive?

You were on 7.1 already when you dirty flashed?

That boot log sounds like gold... ;)
[ONE Original Android Development] fmc000:
I'm running your latest permissive release and it works fine. And of course I was running it when I dirty flashed your first enforcing release.

About the boot log: am I right that even a permissive boot log from my ROM I'm currently running should show you the selinux denies? If it's so, I can collect a boot log this evening when I come back home from work.
[ONE Original Android Development] NoSpamDan:
OK, I'll post a permissive build with MultiROM support for now.

As far as the boot log, the enforcing one should show where it's getting hung up, whereas the permissive one may just skip right by the offending denials.

FYI, you may be aware already, but not all avc denials are bad...
[ONE Original Android Development] fmc000:
I see, let's see what I can do - no promises, though.
[ONE Original Android Development] NoSpamDan:
Cool, well whatever you can do is appreciated.
[ONE Original Android Development] NoSpamDan:
This build has SELinux temporarily set back to permissive until some denials can be fixed. The MultiROM compatibility should be unaffected.

Slim-bacon-7.1.0.build.0.1-DEV-DM-20161208-0806.zip
[ONE Original Android Development] molohov:
Not sure why but I clean flashed this version as a secondary ROM and it doesn't boot (doesn't get past the OnePlus One screen). I do not know how to get any logs at this stage (is it even possible?)
[ONE Original Android Development] TareqA:
ive searched through the thread about ota, is ota available in this rom or not?
[ONE Original Android Development] gmillz:
Mind telling me everything you found wrong? :D
[ONE Original Android Development] NoSpamDan:
Did the previous 2 version(s) work for you?

You are probably going to need the updated MultiROM recovery that Martin and I worked on.

No

I'll hit you up in Slack, dude... LOL
[ONE Original Android Development] molohov:
No I only tried the latest version (12-08). Let me try to find the MultiROM that you are referring to.
[ONE Original Android Development] fmc000:
Please find attached the boot log from my current installation (20161204), collected with catlog. I don't seem to be able to get logs via adb. I tried:

adb reboot
adb logcat > logcat.txt

but I always get an empty file. What am I doing wrong?
[ONE Original Android Development] TareqA:
quick question im on cm14.1 nightly do i just clean flash?
[ONE Original Android Development] NoSpamDan:
See my post in [MENTION=5093942]KINGbabasula[/MENTION]'s MultiROM thread.

Try this:

adb -d logcat>mylogfile.txt

After you first power on your device...

EDIT: The log you posted looks like the permissive one...

Yes, that should work, hopefully you mean wiping /data too... Don't forget to make a nandroid backup!
[ONE Original Android Development] TareqA:
Everything works but that recent app i dislike the look of it, but its very user friendly :) its a nice aosp rom probably the best out there for oneplus one
[ONE Original Android Development] NoSpamDan:
You can choose AOSP or Slim recents...
[ONE Original Android Development] TareqA:
what? lol my bad where do you find it?
[ONE Original Android Development] NoSpamDan:
Settings>Interface I believe
[ONE Original Android Development] fmc000:
Of course, the enforcing one doesn't boot and wants to wipe my phone to proceed. I cannot afford it, I need my internal SD files.
[ONE Original Android Development] catxda:
Everything goes fine until flashing SuperSu.

After , did not boot anymore.

Which version of SuperSU is recommended and when should be flash it ???

In Multirom ; Secondary
[ONE Original Android Development] javiges:
Return slim pie?

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] fmc000:
[MENTION=4435460]NoSpamDan[/MENTION] do you think that this can be the cause of my non-booting installation ? I'm not using multirom but who knows...

I'm willing to test an Enforcing build without the latest Multirom compatibility patches if you think it's worth.
[ONE Original Android Development] NoSpamDan:
Could you folks try this? I hear it works...

SR4-SuperSU-v2.78-SR4-20161115184928.zip

Here's the SR5 version FYI:

SR5-SuperSU-v2.78-SR5-20161130091551.zip

I haven't messed with root myself yet.
[ONE Original Android Development] NoSpamDan:
The SR5 SuperSU is reported working.

Encryption may not work with root. Further testing is needed.
[ONE Original Android Development] joshiameya:
wiping /system and flashing this rom and gapps should be enough. if the performance s not good then clean flash
[ONE Original Android Development] catxda:
The only way to get Slim 7.1 to work with Root in Multirom (Secondary ) was :

- backup CM14.1 Jgcaap lnternal with multirom twrp.

- flash TugaPower recovery over multirom recovery.

- flash Slim 7.1 Internal, slim revised gapps 7.1

- flash SuperSu SR5

- boot fine Slim , all OK

- install twrp multirom and multirom , Slim Still booted fine .

- move Slim 7.1 secondary

- restore CM 14.1 Jgcaap

- Slim 7.1 still booted fine

- run restorecon for another two secondary (Slim 6 and Cos 13.1)

- boot fine in above two restored

- next I was trying to boot Slim 7.1 and nothing only oneplus logo .

Internal and secondary still booted fine.

This short long story show that everything went fine until run restorecon for Secondary.
[ONE Original Android Development] fmc000:
Exactly, I already use SR5 and that's the version I tried with the enforcing release.