yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] NoSpamDan:
Thanks. I am fully aware that Gerrit is public (unless I submit as a draft... :cowboy:). No worries. :D

So I have BT fixed, Screen off gestures added back, GPS, but no mobile data yet still. I had to revert the encryption support patch for now till this is sorted out, [MENTION=791219]fmc000[/MENTION]...
[ONE Original Android Development] tmimaesk:
[MENTION=4435460]NoSpamDan[/MENTION]

I was bored and streamed a log between regular camera and camu camera when it's recording

I don't know if it will help to debug it

I used catlog app to stream them

edit: plus the tombstone file
[ONE Original Android Development] ceiven:
when will the next build come?
[ONE Original Android Development] Setting.Out:
No ETA's
[ONE Original Android Development] _harmonic:
Overall it's pretty stable (check post 3), but I'd wait for the very next update as many issues will be fixed in it. No ETA, but I would expect it this week - maybe even in the next couple of days.
[ONE Original Android Development] NoSpamDan:
You folks are gonna like this I hope...

Slim-bacon-7.0.0.build.0.1-DEV-DM-20161009-1354.zip

Got LTE working finally... Still issues with Camera (no HDR and no video yet).

Added Slim sounds, Slim Launcher, Personalization options including Screen Off Gestures (arrow up not working, so re-assign it for now)...

Still working on video, but in the meantime you can use the Camu app as a work-around... stay tuned.

Peace...

EDIT: Slim Launcher will be included soon...
[ONE Original Android Development] NoSpamDan:
You should know that it is heavily frowned upon to ask when something will be ready, be it a ROM, or an app. It is even MORE frowned upon when the thread owner has said "NO ETA REQUESTS" in big red capital letters in his OP...

I understand you are new, so a little leniency is called for. I was new here too at one time. Honestly, I have been wondering the same thing, build after build, searching, researching, tweaking, cherry-picking, testing, failing... till now. Enough to make a grown man drink (more).

So just know that you should never ask for ETAs or you will most likely get flamed and otherwise harassed for it. I hope you enjoy the update.
[ONE Original Android Development] Barnett:
Thank you for that, I tried to flash the latest, but slim settings can not be used
[ONE Original Android Development] ceiven:
I'm sorry, I did not think so much, I'm really new here (although often come before, but due to language reasons I just browse your posts but had no reply, until used your 7.0rom, a great rom)
[ONE Original Android Development] Zeus20:
Moving forward most if not all dev's do this on their free time and not paid. Never ask for ETA.
[ONE Original Android Development] LucentBirch:
Is there a way to turn on stock recent? Thanks!
[ONE Original Android Development] david72262:
Still problems with recents causing system crashes. And can't choose stock recent instead of slim so system very unstable sorry to be the bad news guy. Is there a way to manually disable or override slim recents and select the default rest of the ROM is the bomb just the recents issue
[ONE Original Android Development] amstel:
hey,

thanks for the new release.

face recognition has been removed from the smart lock options,

anything I can do to restore it?

thanks.
[ONE Original Android Development] fmc000:
It used to work in a previous version. You have to flash opengapps nano at least, it worked for me. If you're using slim gapps you have to flash the face recognition add-on but I don't know if it works.

---------- Post added at 07:04 AM ---------- Previous post was at 06:59 AM ----------

It was in settings, one of the two latest entries (I don't remember at the moment - it was "interface <something>"). The first entry was about recents.
[ONE Original Android Development] david72262:
Thanks for trying to help but that's what I'm saying you can't change it there causes system crash, was wondering if like build prop edit or something would work to change it.
[ONE Original Android Development] NoSpamDan:
Thanks for the heads-up. Note that Recents works fine, but the bug is that you can't change the Slim Recents settings (for now)...
[ONE Original Android Development] fmc000:
Maybe freezing SlimRecents with titanium or something like that?
[ONE Original Android Development] Renosh:
[MENTION=4435460]NoSpamDan[/MENTION]

Would you consider adding a commit for allowing lower DPI than the current small in Display? It's available in CM and saw it in Omni gerrit. I'll post the link if you're interested
[ONE Original Android Development] fmc000:
It's already in developer options.
[ONE Original Android Development] Mike9966:
Settings - Navigation - Navigation bar > FC
[ONE Original Android Development] fmc000:
From the AOSP thread:

[MENTION=4435460]NoSpamDan[/MENTION]: maybe this approach can be used also with this ROM?
[ONE Original Android Development] LucentBirch:
I always have an empty recents bar or I click it and I have a system UI crash.
[ONE Original Android Development] _harmonic:
Same for me. No log at the moment, but using slim recents crashes and the new settings crash as well when selecting the highest level setting option

example: settings -> Interface -> Statusbar -> Statusbar Icons -> crash
[ONE Original Android Development] NoSpamDan:
If SlimRecents is the default then you will prob FC on recents if you do that. But if you try, do let others know your success please. It's being looked into in the interim. Should be much less time than the recent mobile data fiasco, but no promises... :p

I tested it and camera and video camera crashed terribly - black screen. The thing is, it is a huge security issue, and needs to be able to support many different devices, not just bacon. Last I knew, CM had not merged this approach yet https://review.cyanogenmod.org/#/c/165008/. It's going to be interesting where this goes.

Did you try a clean flash? Mine works on a clean flash, but I normally clean flash at this stage of the game :D.
[ONE Original Android Development] fmc000:
Well, i couldn't find SlimRecents within the Titanium apps but it turned out that there was no need. SlimRecents seem to work fine for me...
[ONE Original Android Development] fmc000:
Strange Bluetooth address.

My BT address is 00:00:00:00:5a:ad - quite strange. Anyone else?
[ONE Original Android Development] red5pade:
What's the radio modem being tested? Is it the best new modem? Sorry if its been asked. I searched the thread but I didn't see an answer for my question... Might be the mobile chrome
[ONE Original Android Development] fmc000:
I'm using this firmware. Here you can find some details about it. It seems to work fine for me.
[ONE Original Android Development] red5pade:
I can not get this to boot on multirom, even with lightning kernel
[ONE Original Android Development] Zeus20:
[MENTION=4435460]NoSpamDan[/MENTION] apparently pure nexus has a working video.

https://github.com/purenexusproject
[ONE Original Android Development] NoSpamDan:
Until you try to open the Recents settings... :p

No? But are you running the test build I sent you? Could be related...

It's not a kernel issue, and I think we had this when going from KK to LP. From what I recall, the newest OS had to be primary.

Although this is outside of the scope of my thread/support, I played some with MultiROM, and this is how I got it to work for now:

Make a nandroid of your daily driver ROM

Flash Slim7 as the Primary ROM

Flash the Multi ROM zip file

Inject boot sector or whatever...

Restore nandroid as a secondary ROM

Set MultiROM TWRP settings to boot from your DD secondary ROM always (unless you specify another)

If secondary ROM doesn't boot, according to the MultiROM thread, run restorecon on the secondary ROM entry in the MultiROM TWRP settings

If you have other issues or questions, please visit the official thread for support: http://xdaforums.com/oneplus-one/development/mod-multirom-v26-t2835738

On AOSP devices, which automatically work with N. Have you seen bacon or another CAF device there that works? It's still a WIP and we have to be patient.
[ONE Original Android Development] fmc000:
Yes, I'm running the test build. Despite the strange address, BT works fine and I can use my car adapter for answering phone calls and audio streaming.
[ONE Original Android Development] NoSpamDan:
Cool. Same here when I tested it. 00 is a valid hexadecimal value, so...
[ONE Original Android Development] tmimaesk:
BTW, with stock camera video recording works with 720p but only with stock camera or google camera from apksites..
[ONE Original Android Development] fmc000:
Confirmed with this APK. Cool!!
[ONE Original Android Development] Zeus20:
I'm just trying to help you with the camera.
[ONE Original Android Development] NoSpamDan:
And appreciated. Don't take my response the wrong way; I'm just being truthful here. PureNexus is just that... Nexus. The problems with camera/video are related to CAF HALs from what I've seen. That's all. :D

The FC issues are still being worked on, but close to resolution. Hope to have something to test after I'm home later tonight. Work calls...
[ONE Original Android Development] SDCore:
Whenever I go to Settings > Navigation > Navigation Bar, I get

"SlimSettings has stopped."

I want to change to On-Screen buttons, is that available yet? Did I goof somewhere?

Edit: I also get the same message when trying to access Settings > Interface > Recent Apps Panel
[ONE Original Android Development] fmc000:
It's because you post without reading the thread.
[ONE Original Android Development] fmc000:
A trick for capacity button backlight.

Button backlight timer is set to 5 seconds in the current release. Currently there's a bug: if don't wait these 5 seconds before turning off the device, the backlight remains lit. A temporary "fix" to avoid this problem is to disable the backlight completely. In a root terminal emulator write:

echo 0 > /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness

This doesn't survive a reboot, of course.
[ONE Original Android Development] NoSpamDan:
One thing after another, trying to sort out video camera internals here. I hope to have the touch lights issue fixed too, since we now have HwKey Rebinding with lights options built-in. I think my early change to enable them is now in conflict...

I have the Recents and other settings FCs fixed, so let's hope this next pending build is a good one... Even if the video cam is still borked, I will probably share it if the other things are good.
[ONE Original Android Development] NoSpamDan:
OK, here we go...

This build should have the FCs fixed, with 2 exceptions:

Settings>Interface>Status bar> Status bar icons will FC until you unlock the System tuner by swiping down the Quick settings and press and hold the gear icon by the clock in the upper right hand corner. You should see a toast message confirming that System tuner has been added to the menu if you did it correctly.

The video camera is still a WIP and will crash if you try to use it. I have plenty of logs, so this time around it's not necessary.

Slim-bacon-7.0.0.build.0.1-DEV-DM-20161012-1307.zip

Enjoy!
[ONE Original Android Development] LucentBirch:
Much better! Stock recents all the way! Did you remove the slim boot screen? Just had plain "Android" screen.
[ONE Original Android Development] fmc000:
Thanks. Does this version include the encryption commits?
[ONE Original Android Development] Mike9966:
Install from recovery this:
[ONE Original Android Development] NoSpamDan:
The boot animation is temporarily changed because it got broken. Lol

Yes
[ONE Original Android Development] fmc000:
Confirmed fixed.

Confirmed SlimRecents and Settings FC's fixed.

My encrypted /data partition is now correctly decrypted at boot time (with PIN request), so maybe it's time to update post #2 ;) (and while you're at it, you may also add that AOSP Calendar is also removed from this ROM).

Great solid release IMHO.
[ONE Original Android Development] NoSpamDan:
Thanks, good to know. I can't do much with calendar, mostly because there are plenty available on the Play Store.

Unfortunately, it's the same with Messaging.

I flash a lot of ROMs without GApps, so when I miss a text from my wife, I hear about it. I don't always flash an SMS Client app when testing... Lol
[ONE Original Android Development] fmc000:
FWIW, I very much prefer ROMs with fewer apps included, leaving to the user the choice on what app to install. If this ROM were mine, I wouldn't even include a camera app.

I have a question: are you planning to include the October security patches in the next release?
[ONE Original Android Development] NoSpamDan:
Depends on what gets merged before then.
[ONE Original Android Development] LLStarks:
165008 was merged into CM. Does that help video recording?
[ONE Original Android Development] Renosh:
[MENTION=4435460]NoSpamDan[/MENTION]

This is where I was talking about

On CM and some other ROMs it has smaller and smallest option which I personally like the smaller option. Please let me know if you can merge that for future releases

Here's the commit

https://review.cyanogenmod.org/#/c/161859/
[ONE Original Android Development] NoSpamDan:
I can't merge it straight off, but I will take a look Thanks :)

EDIT: You got lucky on the timing... ;)

https://review.slimroms.org/21704
[ONE Original Android Development] fmc000:
I doubt that this is needed but I have managed to capture a logcat of the AOSP keyboard FCing while swiping.
[ONE Original Android Development] seapoint:
This is great [MENTION=4435460]NoSpamDan[/MENTION] - can I have access also please?

Thanks!
[ONE Original Android Development] Raul027:
Androidfilehost seems to be down. Anybody have a mirror for latest release?
[ONE Original Android Development] NoSpamDan:
Access to what? I'll include it in the next release. It should be easy to get that merged...
[ONE Original Android Development] NoSpamDan:
Working here...
[ONE Original Android Development] fmc000:
AOSP keyboard FC

Well, it turned out that there's no bug at all in the ROM! The actual bug (or missing feature, if you prefer) is in the OpenGapps 7 packages, which don't provide the closed source google swipelibs.

I took them from the [MENTION=5165039]Setting.Out[/MENTION] package and copied them in /system/lib. Now swiping works perfectly with the AOSP keyboard.
[ONE Original Android Development] balaaje:
Rom is perfect for daily driver :svetius:
[ONE Original Android Development] LucentBirch:
Weird, video was working on Snapchat prior to update yesterday. Now it just remains a still picture after recording.
[ONE Original Android Development] NoSpamDan:
It seems that AOSP Keyboard is still looking for the swipe libraries even when GApps is not installed. Tried to make a new contact entry to test. So there is still some keyboard work to do.

Thanks for pointing out the libraries issue. To what [MENTION=5165039]Setting.Out[/MENTION] package are you referring?
[ONE Original Android Development] fmc000:
Swiping can be achieved only with the closed source Google libraries, even with the AOSP keyboard. You have two options IMHO: either you provide the binary-only libs or you set the default for the swiping to off.

For the [MENTION=5165039]Setting.Out[/MENTION] package: look for "Revised slim gapps" in the OnePlus forums on xda.

BTW, I checked the opengapps sources and it's mentioned explicitly that they don't provide the swipelibs on nougat.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] NoSpamDan:
Right. The way we did it on M was to default swiping off until GApps was installed and the libraries were available. The way it is now, it FCs, and shouldn't.
[ONE Original Android Development] Alonzzo2:
Anybody got this to work?

http://xdaforums.com/android/software/guide-how-to-enable-google-assistant-t3477879

= Google assistant from the pixel devices
[ONE Original Android Development] darrie1:
Nope.
[ONE Original Android Development] tofu:
There seem to be still some issue with encryption:

I tried to set separate boot & lockscreen passwords (as I've done since KitKat). First I set the short pin for lockscreen, and then via adb shell enable the encryption using longer boot password: vdc cryptfs enablecrypto inplace password [superlongandsecurepasswordherewithoutbrackets]

It encrypts fine, the "type in your password" -screen comes normally as expected, but then after correct password it claims that my password wrong.

I've done this thousand times before, and this is the first time that I encounter this kind of issue.
[ONE Original Android Development] fmc000:
A few people can't hear me during normal phone calls. A possible solution.

[MENTION=4435460]NoSpamDan[/MENTION] : a few people complain that they cannot hear me during phone calls, my wife included. Please note that I have the "OK google" hotword detection disabled.

Looking on the CM jira I found that BACON-289 describes my issue perfectly. Quite impressive is that this problem dates back to the earlier COS11 days, two years ago more or less and it's still present for many people with COS13.1 .

I tried this possible solution: set this value in build.prop

ro.qc.sdk.audio.fluencetype=none

and reboot. Now my problem is gone and people can hear me without me needing to scream as an animal. Basically, this disables the fluence-noise-cancellation (values for this can be "fluence" or "fluencepro" or "none"). This solution was implemented in SlimSaber MM, with good feedback.

Comments?
[ONE Original Android Development] TheNerd:
I didn't change this property but edited mixer_paths.xml as follows: https://forums.oneplus.net/threads/...k-of-microphone-while-on-speakerphone.118232/

In my case people couldn't hear me only on speakerphone.
[ONE Original Android Development] NoSpamDan:
There is a problem where it is not building properly yet.

No clue... What firmware are you running?

Where is your logcat? :confused:
[ONE Original Android Development] se7enlyn:
after flashing this rom+opengapps nano 7.0, could not enable wifi, wrong mac address,unknown baseband and no mobile service/simcard not detected. tried flashing oneplus firmware c6 241 but still not working.

went back to tugapower 7.0 and phone working again.
[ONE Original Android Development] klassical:
Love the Slim6. Cannot wait to test the Nougat. Great job Dev!
[ONE Original Android Development] zjxpot:
thanks for the reply, I am on slim 6 now I will try 7 again next update...
[ONE Original Android Development] wozn:
same here, except used pico gapps. no sim, unknown baseband etc
[ONE Original Android Development] fmc000:
Same question for you, logcat, firmware version and so on...
[ONE Original Android Development] txanflin:
same problem with wifi
[ONE Original Android Development] zagzag99:
Please consider making the ROM multirom compatible.
[ONE Original Android Development] Setting.Out:
http://xdaforums.com/oneplus-one/development/cyanogenmod-14-0-t3464337/post68763439
[ONE Original Android Development] zagzag99:
Thanks, i know it can be done. But I most of the time experiment rom while being on the move, without a pc around. And manipulation of scripts is not easy on a mobile screen. That's why I asked Dev to consider implementing it in his posted zips.
[ONE Original Android Development] Anghirrim:
Do you have more info about modem/firmware version as well as some logcat?
[ONE Original Android Development] NoSpamDan:
Stand by, folks. I switched from the Slim Build server to my local box to test and hopefully improve build times.

As I was going through changes, I found that I may have missed a RIL commit. It will hopefully be fixed in the next build, along with WiFi.

Stay tuned... :cool:
[ONE Original Android Development] aliffaminuddin:
thanks! but still no camera?
[ONE Original Android Development] NoSpamDan:
<sarcasm>Oh, ye of little faith... :rolleyes:</sarcasm>

Time will tell, but of course I have addressed it to some degree. We'll see... :fingers-crossed:

#StillExperimental

EDIT: And now... this
[ONE Original Android Development] rolarocka:
Same here after flashing this rom... Baseband is unknown and imei is missing.. How do i solve this omg i think its bricked... Tried official nightys.. oxygen os too already and still no luck with getting baseband and imei back.
[ONE Original Android Development] KenjiHannya:
Flash another rom dude
[ONE Original Android Development] Setting.Out:
http://xdaforums.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389

https://forums.oneplus.net/threads/no-imei-number.292198/page-5

Color OS or Oxygen.. If you made a backup restore it..

Once fixed, make a backup.. :)
[ONE Original Android Development] NoSpamDan:
You're not bricked. We have already establisthed that RIL is broken. I'm working on it, so sit tight already with the brick comments. Jeez... (Unless you flashed this ROM on the wrong device? )

What radio are you using? Reflash one, or flash the latest CM13 nightly, which includes firmware. This ROM does NOT include firmware, and I can't speak for OxygenOS.
[ONE Original Android Development] rolarocka:
im using c6 modem from latest oneplus one nightly flashed twrp 3.0.2.4 by tugapower. i flashed your rom and tried restoring a functional slimsaber mm backup with all partitions saved (EFS. MODEM, Boot etc..). It restored well but got bootloop right after seing slimsabers logo. After that i tried several firmware for the one, its always unknown baseband and no imei. Aslo flashed cm13 nightly (fastboot image) via fastboot and the rom boots but no baseband and imei... Like if the efs partiton is corrupted or something. Restoring EFS trough twrp says successfull but no imei
[ONE Original Android Development] rolarocka:
Hi, i have the same problem like you after flashing this ROM, how did u went back to tugapower ? Through restore? I've been trying the whole day to get baseband and imei working again and no luck ??

Gesendet von meinem GT-I9505 mit Tapatalk
[ONE Original Android Development] lieferant:
on 1210 editing statusbar icons is not possible (fc) / toggling mobile data from the quicksettings is not possible (menu opens and closes immediatelly)
[ONE Original Android Development] fmc000:
It's because you didn't read the release announcement and made things worse not using the search function.
[ONE Original Android Development] JAY28W:
Here is where everyone's been hanging out... lol, been wondering why the Slim6 conversation so quiet.
[ONE Original Android Development] xtremez:
Time to move on to Nougat :p
[ONE Original Android Development] gerciolisz:
You guys seems have broken one of 3 mics this is why fluence stop to work and you have to disable it.. this is why this problem still occurs ppl.. we have 3 mics if one of them is broken it starts to happen
[ONE Original Android Development] fmc000:
Sorry but I don't think you're right. I never had this problem with KK or LP, it started as soon as I moved to MM and disappeared when I went back to LP for a few months. Then it showed up again when I reinstalled MM and it's still there with N.
[ONE Original Android Development] gerciolisz:
Not every rom had fluence enabled so it could work with no problems
[ONE Original Android Development] fmc000:
KK was the original COS and two of the LP ROMs were HydrogenOS and SmartisanOS but whatever. Is it possibile to disable Fluence permanently without having to update the build.prop at every ROM update?
[ONE Original Android Development] arjun:
by making the build.prop changes to the rom source itself.
[ONE Original Android Development] jon_lee9900:
Google Assistant

I can get the Google Assistant to start up and undertake voice recognition, but then it loads back to Now on Tap. There must be something within Slim which is blocking it as it worked on the Experimental CM Nougat build.
[ONE Original Android Development] xtremez:
I have tried many options to get Google Assistant working but so far nothing has worked