yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Great job my friend. Who never ran out of mem, has just not tried hard enough. With the machine I described in my previous posting, everybody can compile large projects! Really tough! (BTW: it's Murphy, that this happens just after you offered to do your first public build... ;) )

I'm not sure, but if I don't brainlock, we need to set lcd_density to the physical abillities of our display, which is 401 (@crlan: the numbers get nearer...)

If the dimensions look strange on [MENTION=7030109]mcdachpappe[/MENTION]'s test build, root the rom and set ro.sf.lcd_density in /system/build.prop to 400 or 420 and reboot.

EDIT: I would appriciate screenshots of QS, shutdown menu and Settings Overview page - especially if it looks unexpected. Thanx.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
haha yes .. murphy's rule indeed :D

screenshots attached
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] crian:
Changing density to 420 in the build.prop has no effect. Dp in dev options is still 360.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I need to look through the sorces, to see which AAPT config is used for computing the dp value. The concept of dp (so called "virtual pixel") is not completely clear to me. Also "smallest width" in regards to app layout and screen independent density are quite confusing for me atm, as well as los choice of screen size "normal" seems currently strange to me, though I'm sure it has a reason.

As you can see, I have a lot homework to do... ...which takes time.

On my current prority list this is second after merging ob15.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] gamal001:
can you add option : show cpu info , please .

I know some app can do this but I prefer built-in .
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
@ dev:

ive built from your current sources (aapt commits) and now i see a fade-out effect on my homescreen. is this related to the latest commits or didnt i noticed this in previous builds? no Problem for me, im just asking because i dont see any other change after these commits.

i drew red lines at the Screenshot were the fade-out effect ends..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
yes i like the new way it looks, too. ill keep that for my further builds (thanks to you for your repo's as my base!)

i dirty flashed the new build on top the old one (before no aapt related commits - after aapt commits). there was something mixed up with the previous (non aapt commits rom) configuration about my display scale (the value was "custom 336" or something like this). after sliding the slider back and forth it looks even better now ;)

about building:

you are welcome! im willing to help if you need a hand on this
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
op3 build

Some weeks ago, I've asked if someone ist interested in supporting nlos for op3. Since no one contacted me, I've decided to get rid of the unified build mimik. This is the last call:

Is anyone interested in building and supporting nlos for op3 in an own thread?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yes, because of the shifted densities. That's why you need to set default/standard once before setting to your prefered size. The same goes for fontsize.

Thank you very much - highly appriciated! I'm sure I'll come back on this (though I hope for an other reason! The night without knowing if cpu has survived, wasn't that great... ;) )
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] UnbracedTundra:
I read the patch notes that the bootanimation has changed, and I have been too busy working on other client projects to even try out the new build.

Wont changing the bin file change the initial splash screen permanently? What if people want to change the ROM?

We can work on creating a transition from the grey to pure black, but the asset size is going to increase significantly. We will be moving from 270 x 270 to 1080p on every PNG.

I have to see what the new bootanimation is first, if anyone can maybe post a short clip or gif, that would be helpful :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I have to check these. The bootanimation binary has changed as well, perhaps it's a new bootanimation format allowing to position the animation...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Clock Customization

Just stumbled over this:

https://xdaforums.com/oneplus-3/one...ds/k-klock-customize-statusbar-clock-t3587100
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You might want to try:

https://xdaforums.com/oneplus-3t/themes/sultanxdas-snapcam-app-manual-controls-t3614363
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] crian:
Here is a short Clip of the new bootanimantion. [youtube]9xdtkY8PP30[/youtube]
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Akash sky:
thanks already tried this and sultan los too actually... his camera has a bug in front camera ... while recording a video from front facing camera if you move the phone left right y9u will get jelly like effect in the video itself.

already reported this to him.

maybe some issue with stabilisation.

right on your los :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Don't buy GoPro!!!

Dear GoPro Markting Manager,

I understand, that you doesn't care about anything but your sales numbers. I also understand that you make ads for that. I also understand, that you want people seeing your ad.

So you decided to make an ad, that requests the browser to jump to your ad (that alone offended me, because I'm here for the people, not for your product), and then reloading your ****ty ad, whats make the browser jump again to your ad... this renders xda unsuble for me.

Even with the social handicap sales men typically suffer from (your misbehaving ad is obviously the best proof to this psychological inabillity), you should understand that this kind of marketing makes people annoyed instead of making them buy your (overrated and overpayed) products.

xda needs ads to keep their service up and running, but I'm pretty sure, xda does not accept ads behaving like yours!

DON'T BUY GOPRO PRODUCTS!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] crian:
Got the same annoying ad but for a contest to win an iPhone 7. Got this bull**** for a couple of weeks on XDA. Couldn't use chrome to browse xda without that thing popping up.

But since few days it stopped and never showed up.

Hope I won't see this ****ing ad again.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] takui:
Hey guys, op5 camera provided in OP is working good enough, or it has the same problems as months ago? I remember to have tried it around june with ****ty problems like hdr ****ed up,artifacts, original cam ****ed up and so on
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] UnbracedTundra:
What the actual **** is that. :eek::eek::eek:

Thanks for the upload :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
That washed out gray makes me on each reboot cleaning my sceeen, just to find it's the bg...

The animation itself is - what should I say - not minimalistic enough to match my taste... (yeah, this was quite euphemistic)

For the update to ob15: snapdragon llvm was updated to 4.0.2, I lost track of time when starting to play with it. It's not working atm. I'll publish the update later this night or tomorrow morning, sorry.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (ob15, AAPT fixed)

Build 20170923

Sorry for the delay my friends, but my carrier avoided the upload til one hour ago or so... Vodafone has a real great business model: If my upload of a half GB fails 7 times at 80 - 90 %, this is about 3GB of traffic. Vodafone charges me at 15€ per 3GB... ...and the rom was still not uploaded... Good job, Mr. Vodafone! :(

Anyway, I used the time to do my AAPT homework and finally got virtual pixels and physical pixels having the very same value. I consider AAPT as fixed.

I also rebased NLOS' kernel on the updated los sources.

Please read the releasnotes and the note on dirty flashing very carefully!

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). This build ships with the updated (original OnePlus) firmware including the new boot logo. As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images.

I added the flashable zip back_in_black_bootlogo-v1.0.zip to the archive:

I strongly recommend flashing this directly after this build, otherwise you risk to puke on every reboot. This zip flashes the pre-ob15 boot logo (belive me: you want the black one!).

Note on dirty flashing:

Before anything else set display size and font size in display settings to default/standard.

Wipe cache and dalvik after flashing!!!

If you encounter any issues with your normal update procedure, try wiping system prior to flashing:

Before anything else set display size and font size in display settings to default/standard.

Wipe cache, dalvik AND system.

Flash this build.

Flash all system altering zips you need (i.e. beans and addonsu)

Instead of rebooting to system switch the op3t off.

Wait at least 50 seconds.

Switch device on.

If you have forgotten to do 1., just go to settings set display- and font size to standard and reboot.

Changelog:

AAPT: set ro.sf.lcd_density to 430. — nvertigo

op3t: overlay: enable burnIn protection support — Joey Rizzoli

op3t: blobs: readd extraction of firmware. — nvertigo

op3: Update file extractors to match new template — dianlujitao

op3t: init: nuke the unified boot logic. — nvertigo

board-info.txt: update to ob15: set modem version to "2017-09-15 20:39:11". — nvertigo

AAPT: adjust config to the physical abillities of 3t's display. — nvertigo

op3t: init: update to ob15: update build fingerprint. — nvertigo

op3t: firmware: update to ob15: add logo.bin. — nvertigo

rebase kernel on los updated kernel (LA.UM.5.5.r1-05800-8x96.0)

back_in_black_bootlogo-v1.0.zip

Camera- and Gallery-Download (If you havn't done so, update com.oneplus.camera and com.oneplus.gallery.)

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Sadly this depends on omnigear. Before you ask: definetly NO. It's much easier to adapt my device tree for omni, then to port omnigear into NLOS (hint, hint, hint... ;) ).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] gamal001:
it's available in most custom rom ( RR, Pure Fusion, Omni, NucleaRom, Legend, ..)

but forget my suggestion.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
[MENTION=4405529]nvertigo67[/MENTION]

Thanks man. Fully compatible with my op3t. But when I've been read your instruction I was confused about 5 and 6 points of that. So what the reason of such advice? (btw I've did exactly like you said)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Because it makes a difference, if you just reboot or shutdown and restart. It's a similar difference like restarting windows or shutting completely down before restart. The time is just an estimate: if modern diods (Phrase? It's "Dioden" in German) need about 30 s to loose all electric energy, I thought with 50s we are on the safe side.

(This was already discussed here some months ago, but I can't search, because my ip hookup is constantly droped from Master Vodafone before the search results return... :( Though: always use your own brain, thread search and internet search before posting.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The world of source build custom roms is great, isn't it? So much great roms to choose from!

A stated in OP, if you look for the most and most current features, NLOS is propably not the best choice for you.

Hmm, your sugestion was to add cpuinfo. If your suggestion would have been adding omnigear, I would have had the chance to say no before digging in the source of the suggested patch.

Making me work on that, ending with "forget my suggestion" is at least a very unfortune way to end this discussion. I'm no bot - I'm a human beeing, who tried to help you though very limited time. "Ah, sorry forgot that this patch depends on omnigears. Thank you, anyway. " would have been much more polite and respectfull, then this soggy "forget my suggestion" after generating work...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] gamal001:
I am respect you work, and thanks for hard work, and I am not looking for more features.

I will continue to used your rom till I change my mobile.

sorry if I push you, I will be silent without any suggestions more.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Can anybody confirm video (at least 720p and 1080p - though 4k is working on 0923)?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
Just played a 4k sample with VLC and built in player just fine.

Also got loads of 720p videos, both MP4 and mkv play fine with both too.

The sample I played

http://4ksamples.com/elysium-2013-2160p-1-minute-sample-footage/

?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Oh sorry, I've meant video taking.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
4k recording is working fine. With inbuild camera and with gcam
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yes, I know. But are videos with 1080p or 720p broken?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Yes. They broken if I try record with snap cam. But with latest gcam (mod 3.8) all work perfectly.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
As nearly always only HAL1 is effected. opencam and gcam are using HAL3 and are doing fine.

I'm still testing...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
If you will need one more tester, I'm here. :cool:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx.

I have excluded kernel rebase and ob15 blobs so far...

EDIT: It seems, that setting the lcd_density from 420 to 430 breaks video modes for HAL1 using apps. After a night of diving and digging into this, I have to admit I DON'T KNOW WHY this breaks HAL1.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
So now we have to select display size standard every time before flashing an update? ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
Why all these density changes? It worked perfect before this single whish of one user came up [emoji19] (if I remember correctly).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
No. There was made some changes with DPI (read a few pages before). That is why we should reset it to default, to prevent any possible bugs. That's all.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Perhaps I wasn't clear enough: Since 12.1 on bacon, why the screensize for 1080p devices is set to "normal". I always doubtwd that xonfig. The single user wish, was just the event, that made me finally (after 3nearly 3 years... ;) ) changing it. As you can read from [MENTION=7030109]mcdachpappe[/MENTION]'s posting, at least one system app (Trebuchet) is behaving different.

No, no, that's only nesseccary if the lcd_density setting is changed. If required, I'll mention in release notes. It's just a matter of point of view: one clould also point out,that the dev found a way to normally update (dirty flash), though the devices density was changed... ;) In the next update the vodeo issues will be fixed - the lcd_density is changed once again back to 420.

Bottom line: I like driving the device with a configuration, which honors the physically abillities of our hardware as good as possible - in the end this is why we all like NLOS.

EDIT: It's NOT! the density setting. Either I mixed up my tested builds (most propably), or somthing, which is a result of the combination of patches. Anyway, the next build is with 430 again, so no need to expect any AAPT issues, setting screen size to standrad will not be required.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (video fix)

Build 20170925

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images.

I added the flashable zip back_in_black_bootlogo-v1.0.zip to the archive:

I strongly recommend flashing this directly after this build, otherwise you risk to puke on every reboot. This zip flashes the pre-ob15 boot logo (belive me: you want the black one!).

Changelog:

I removed the following commits again:

op3t: overlay: enable burnIn protection support — Joey Rizzoli

op3t: init: nuke the unified boot logic. — nvertigo

The first one doesn't matter, because it is only needed on always on ambient display. The latter was just an idea, to simplify updates of build fingerprint - I'll come back later on this. Removing these fixes the video taking issues.

back_in_black_bootlogo-v1.0.zip

Camera- and Gallery-Download (If you havn't done so, update com.oneplus.camera and com.oneplus.gallery.)

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Burn-in protection (device-specific): statusbar and navigation bar (if any) icon’s position is shifted every minute to help prevent burn-in of these areas

source: https://lineageos.org/Changelog-14/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Ah, ok. That makes sense. I'll look into.

Does everyboey agree, that in doubt the video taking for HAL1 is more important then burIn protection? (We can't c8mpletely drop HAL1 because of video support for i.e. whatsapp or hangouts- BTW: can somebody confirm videocalls are working?)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
I agree, HAL1 is more important.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
[MENTION=4405529]nvertigo67[/MENTION]

I can. A few sec ago I've talking with my son through Viber video call. And video recording by the camera works as well.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
I've just clean installed the latest version and am setting it up without SIM card... and the setup app keeps failing at skipping the SIM card step. I checked the known issues and it seems like GApps issue, but the thing is at first I flashed the Beans GApps Mini and after that didn't work I clean flashed the rom + Open GApps Pico which didn't work either. I'm at a loss now :( Does anyone have any idea why I can't even enter setup properly?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
It's because WiFi isn't on, but you have no option to turn WiFi on, and setup crashes. It's been like that since nougat came out I think. You need a sim card to get through initial setup.

Not sure how you could get around it sorry, other than microG or maybe there is a gapp out there with a work around!

On my Asus transformer, the developer put a WiFi button on the navigation bar to get around it!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Please describe/mention every single step. What exactly do you mean by "failing" and "not working"? Error message? Have you tried setting up sim-less without gapps? Wiped system? From what rom did you start from - firmware version? Can you temporary borough a sim and check clean flash with sim in?

(If I make a unsecure build, would you be able to get logs? My problem - besides not knowing where to take the time from - is, I can't effort beeing unreachable on phone till December for more then 30 minutes.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
WIFi should be on:

https://github.com/nvertigo/android...mmit/db401befdd629451cda9d7576d963fdd24d4f1cd

If this is a general problem with los (or perhaps android7 alltogether) the best option is to open a jira ticket. Honestly, I think this is a rare case and it doesn't make sense for me to spend nights on this. It would be nice to have sim-less installation working, but this is one, which would take many sleepless nights... I don't want to leave behind anybody with rare use cases, but if a team of gurus can't fix this for months, I can guess what this means for the time budget a one-man-show would need...

BTW: thanx, for pointing out it's a general los issue. I really wonder if reports not mentioning, that this is a general bug are just thought- and careless, or ... Thanx again.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm working atm at the LITTLE cluster: though our big cluster is working at full 2.34 GHz, our LITTLE cluster is cripled to 1.6 GHz. Perhaps this is needed to do unified builds or it was just forgotten, when adding sd821 to the game (just a guess, really don't know). Anyway: we have 2.2GHz on LITTLE and I want to use it.

Though I have explicitly set the max freq to 2.2 GHz in init.qcom.power.rc, the device always come up with the crippled LITTLE. When setting it manually to 2.2 again it won't stick: though explicitly setting the 2.2 it sticks through screen off/on, but is reset to 1.6 after an app start.

If anybody has an idea on this, let me know, please.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
A link to the page where I first saw this problem mentioned, I think the bug is still present in open Gapps. Last time i did a full wipe, it used mobile data to setup Google, nothing to do with NLOS.

Don't let it take you away from working on other more important issues. It's been there since at least April.

https://xdaforums.com/showpost.php?p=71847989&postcount=497
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vampire36:
That's cos of ported Marlin Powerhal. Pixel is under locked. So the frequency is set to same as pixel
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
Is the AOSP webview in upstream broken? Play store seems to not work with AOSP webview selected but it works with Google webview, on multiple devices running various Lineage builds :/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
So when the phone boots up, the first setup screen is the choice of language (English (United States)) and then on the next screen I get the no-SIM-card warning. There's a SKIP button. When I click the skip button, I get a FC dialog box (can't remember the exact error message, sorry, but it was something short like it stopped working or something like that) and am pushed back to the first step (language choice). It keeps happening over and over and I can't proceed to the step after the SIM card skip.

I had flashed the rom version with the firmware included. Had wiped everything (system, data, cache, dalvik) before flashing.

I'm migrating from another phone and want to set up the phone exactly the way I want before moving the SIM card over from the previous daily driver. I didn't have this setup problem with other roms that I've tried so far (VertexOS + Open GApps Pico and the stock OOS). Currently on the stock OOS 4.5.0. So it's not a general Nougat problem. In the setup process along the way I would choose a wifi network to connect to and continue setting up the phone with the Google account.

I really wished this rom would work, though... so it was a huge disappointment when the setup didn't work. Once I set up the phone with all the apps and such and move the SIM card over, I'll take a nandroid backup and try this rom again. Maybe the setup will work with the SIM card in? Hopefully it's as easy as that and there's no more problem down the road.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Maybe. If I stop perfd the issue persists. If I use interactive governor (with perfd running) the issue is gone - so I still hope it's not the blobs... I think it's hardcoded somewhere else. I can't see in the logs, what is resetting the values. In dmesg I can see the cpu cores are initialized with the correct values (of course: I can set 2188 MHz manually).

No, it's working fine here (beans from July). Last change on webview (upstream) is from 21. of August.

Clean flash with beans mini works fine.