yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Crash:
[MENTION=5091734]dianlujitao[/MENTION] looks like the OOS camera now have everything working fine HDR,Video on 60FPS and even slowMotion! runing a 3t here thanks mate I still runing more test I runing the camera port and the gallery from [MENTION=4837394]siankatabg[/MENTION]:good::good:
[OnePlus 3 & 3T Cross Device Development] nadejo:
Did you have to modifie the zipfile to prevent error7 ?

And did you make a clean install. I cant seem to install it on op3t.
[OnePlus 3 & 3T Cross Device Development] Crash:
I was on Beta 3 simple factory reseat a flash hugs:good:
[OnePlus 3 & 3T Cross Device Development] nadejo:
So should i install the whole beta3 update first? Because i cant seem to find a modem/firmware-only.zip

Thanks
[OnePlus 3 & 3T Cross Device Development] :
OpenBeta12 fw & modem

https://www.androidfilehost.com/?fid=745425885120711796

For future updates: https://xdaforums.com/showpost.php?p=68852548&postcount=1
[OnePlus 3 & 3T Cross Device Development] nadejo:
I got the oneplus3t and i saw someone posted he bricked his device (op3t) flashing beta12 fw. I guess i need beta3 fw.
[OnePlus 3 & 3T Cross Device Development] Crash:
Well in my case I flash beta 3 to be safe hehe hugs
[OnePlus 3 & 3T Cross Device Development] nadejo:
I managed to sucessfully flash the latest build on oneplus3t

You must do a clean install.

You have to first flash open beta 3 firmware and on top of that the openbeta3 uniblob firmware. Because the kernel in this rom is working on both devices. After that flash the rom / even latest ex kernel works using this method. /

This method is only for oneplus3t.

For oneplus3 you have to flash openbeta12 firmware and uniblob firmware openbeta12 instead and then the rom.

You can trust me, nothing will go wrong and custom kernels will work. :)

Hope we can flash upcoming official build on top of this build without wiping.

Edit: however camera doesnt work. Confirmed its because ive flashed ex kernel

Reflashed rom to remove ex kernel and camera works :)
[OnePlus 3 & 3T Cross Device Development] [GR]Frostbyte:
I never said the opposite.

You keep insisting, but I neither complained, nor demanded for a fix. I know first hand that the developers donate their free time and that they do not have such obligations.

I'm not sure how exactly you came to this conclusion; just because I wrote that another build did not work for me and that I opted to revert again. (or that I refused to do a clean install, in general - it's my device I do whatever I want with it.. really now?)

First off, maybe you could stop being so condescending. Secondly, I would like to point out you're not fully participating in a constructive dialogue. If anything you're just spending alot of additional time to (and complaining yourself) just to prove that I was the one who's complaining - where in actuality I did no such thing (or at least I never intended to).

Sure, I cannot be bothered to wipe my device, but again, it's my device, right? I choose what to do with it. You seem to be awfully agitated that I refused to wipe it, but instead chose to reply with my reasoning/personal-opinion on the matter. Even more so, because I didn't initially opt to do the extra mile, just to see what's wrong before I posted (which I will at least give that point to you).

Yes, I also have developed apps with the Eclipse (ADT) and the Google API, and have a fair understanding of the platform. So what? You're just making yourself look bad with that attitude (no offense).

Let me just leave this here "The issue with capturing a logcat during a bootloop is that the boot process has to be far enough along to have started-up the adb daemon"

You apparently thought that I didn't try anything at all.. thing is, if I was able to produce a logcat with the standard methods, rest assured that I would already have done so.

However, I will thank you for the methods you posted. I will study them and see if I can come up with a solution. I will post my findings here.

Again I will say that there's no reason for all of this drama, I'd appreciate if we just left it here.
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
Skipped everything else you said because this is the only line that matters. Taking the time to do this helps everyone, so thank you. If you end finding out the core reason for the failure mention @ OP so he can see the log.
[OnePlus 3 & 3T Cross Device Development] nadejo:
I wonder if its possible to have conservative governor in the stock kernel included.
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
Conservative governor is not the answer to this issue--correcting the frequency switching issues in the interactive governor is. Setting the cores to conservative is only a workaround and not necessarily a battery friendly one. The reason the AKT tweaks work so well is because they modify the interactive governor to work better than stock values. Not all profiles are perfect by any means, but they were tuned by hand instead of providing a one-size fits all adjustment. We'll have to wait and see what Oneplus does in response to the information given or if they even modified the interactive governor at all from AOSP values.
[OnePlus 3 & 3T Cross Device Development] [GR]Frostbyte:
[MENTION=4685802]AlkaliV2[/MENTION]

I've let it run for 15 minutes, but the log shows nothing suspicious. (unless I missed something)

I will attempt a longer run to see for any repeating patterns.
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
After a bootloop will you open TWRP and with the file manager go to /sys/fs/pstore/console-ramoops copy that file and post it here? It's a good secondary file for diagnosing the issue. It will hopefully capture the output being seen right as it reboots.
[OnePlus 3 & 3T Cross Device Development] [GR]Frostbyte:
Will do, but this time I will let it run a little longer. Just to clarify, this isn't a typical bootloop. It's just getting stuck on the boot animation endlessly.
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
The only output the log is showing is all the steps from a TWRP boot to the start of execution of the build.prop settings towards the bottom of your first log. However, I noticed your internal storage is encrypted. Have you successfully dirty flashed over your system partition while leaving encryption intact or is this the first time you've dirty flashed with encryption?

I don't normally dirty flash that's why I'm asking. Hopefully the ramoops file will say exactly what it is seeing during boot.
[OnePlus 3 & 3T Cross Device Development] Michalko5896:
You will have to flash experimental for the official builds.
[OnePlus 3 & 3T Cross Device Development] [GR]Frostbyte:
I've let another test run for about 40 minutes. Did not see any differences in regards to last_log.

I've tried to both adb pull the file you requested, and navigate to it through the TWRP file manager, but /sys/fs/pstore/ appears to be empty.

I mounted the system partition and checked again, to see if that's the case, the folder is still empty.

It's not the first dirty flash.

Once I first got my phone, I had flashed the available CM13 stable release. (the only nightlies were for CM14/CM14.1 iirc)

I don't remember being prompted about encryption. Unless If you're referring to the option "encrypt my phone", which I always answer with "no".

Once the first LOS build was available, I flashed the experimental build on top of CM13 and successfully migrated without the slightest crash or issue.

Ever since I have successfully dirty flashed the following images (on top of each other):

lineage-14.1-20170125-nightly-oneplus3-signed.zip

lineage-14.1-20170131-nightly-oneplus3-signed.zip

lineage-14.1-20170207-nightly-oneplus3-signed.zip

lineage-14.1-20170208-nightly-oneplus3-signed.zip

lineage-14.1-20170214-nightly-oneplus3-signed.zip

I'm still keeping my phone inside the recovery, if you need me to look something up.

PS: I think that the internal storage encryption that you're speaking about, wasn't that similar to the adoptable storage that android 6.0 offered? Because I remember that I was struggling to find the key to decrypt the SD card* of my old Galaxy S3.. I remember that if you use the SD to store applications, it encrypts it. That must be the default behavior for the OP3's internal storage as well. I don't think it's something the user has a choice for.

*Gave up eventually, I had pulled a system image with dd, mounted it on an ubuntu VM and attempted whatever I could with testdisk + photorec.

Ironically, in that SD I was keeping the TWRP backups of the phone.. That day I learned to keep them stored elsewhere.
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
Your 15 minute log showed me the lines:

I:Created '/usb_otg' folder.
I:Setting up '/data' as data/media emulated storage.
I:Created '/sdcard' folder.
I:Can't probe device /dev/block/sda15
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda15', current file system: 'ext4'
I:Can't probe device /dev/block/sda15
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda15', current file system: 'ext4'
get_crypt_ftr_info crypto key location: 'footer'
I:Backup folder set to '/data/media/TWRP/BACKUPS/a74e3d9a'
I:Settings storage is '/data/media'
I:Device is encrypted with the default password, attempting to decrypt.
crypt_ftr->fs_size = 112477112
Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex, using passwd instead
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex, using passwd instead
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
crypt_ftr->fs_size = 112477112
Using scrypt with keymaster for cryptfs KDF
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
Using scrypt with keymaster for cryptfs KDF
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
load_crypto_mapping_table: target_type = req-crypt
load_crypto_mapping_table: real_blk_name = /dev/block/sda15, extra_params = fde_enabled ice
Password matches
Data successfully decrypted, new block device: '/dev/block/dm-0'

The last line is what you normally see starting TWRP when it attempts to mount an encrypted data partition. However, since you've been dirty flashing updates this whole time I can't specifically say that this is what is causing the issue. Without the ramoops and no real errors in your log file I'm unable to really help you troubleshoot further. I also don't really know what information is available to give to the dev based on what I am seeing from you last log.

The hard time I gave you earlier was unwarranted and I apologize. You've put in the time to find a solution, or at least the problem, and I've come up with nothing helpful to offer. I'm hoping that all this posting someone with more understanding of what is going on will help you gain traction and fix your issue. But as of now your backup is the safest option.

Edit: One more shot: http://bootloader.wikidot.com/linux:android:kmsg

Will you attempt to get me your kmsg output during the boot hang?
[OnePlus 3 & 3T Cross Device Development] [GR]Frostbyte:
Don't worry about it, it's all fine. :)

I am a little but unsure on how to do it properly though, since the phone does not reach a state where I can adb shell into.

I am wondering what I need to modify in order to pass the kmsg through a serial port and capture it with putty. Any advice?

"ls /dev | grep tty" gives me:

tty

ttyHS0

I assume I have to seek some sort of initialization parameters inside the build.prop and sneak in a "console=" ?

PS2: Upon further investigation, I think this requires me to modify and recompile the kernel. I don't really feel confident touching it, what can we do?
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
I have to assume that ttyHSO is the UART, but the "MSM2" might be the default name for the MSM chipset UART port the article is referencing. You could push a copy of the build.prop to /system/ once you've made the edits, but this is new territory for me so you'll have to experiment and tell me what works. I'm Googling as much as I can on this, but there's not a lot of XDA articles on redirecting kernel messages through putty.

Edit: I'm checking the build.prop now to see if this is a user or user-debug build to see if we have any remaining options. A debug build allows for the kernel module you are talking about being enabled though I doubt I'm going to lsmod/modprobe this into working. Let me check and see what we have left as options.
[OnePlus 3 & 3T Cross Device Development] [GR]Frostbyte:
This is my build.prop - I couldn't find any relevant line to sneak the console parameter into though. Looks like we might have to compile :|
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
I'm going to grab the OP3 Lineage .config and see if this option is enabled in the userdebug kernel. It may be compiled but not shown in the build.prop

I'm also going to switch to PM to keep helping since I don't want the next few pages to be us troubleshooting the issue.
[OnePlus 3 & 3T Cross Device Development] [GR]Frostbyte:
Roger that, thanks a bunch! :)
[OnePlus 3 & 3T Cross Device Development] nitz2889:
On the latest experimental build with OB12 blobs the [MENTION=4837394]siankatabg[/MENTION] camera port works flawlessly. Comparable pictures with oxygenOs, HDR HQ and slomo all working. Really recommend this to everyone flashing latest experimental build. Thanx [MENTION=5091734]dianlujitao[/MENTION] and [MENTION=4837394]siankatabg[/MENTION] for support.
[OnePlus 3 & 3T Cross Device Development] thefraggle:
Was anybody able to install the latest experimental build dirty over an existing installation?

Any hints?

If I do need to clean flash, I will wait for the next weekly :svetius:
[OnePlus 3 & 3T Cross Device Development] themcfly:
Just as info... is it working that way without flashing the HAL1 enabler? Asking because I was getting the functionality you described on the 1402 build flashing the HAL1 enabler, which on the other hand broke cameras in other applications.

About this and the comments going on in the topic:

https://review.lineageos.org/#/c/164175/
[MENTION=5091734]dianlujitao[/MENTION] Hope this gets merged in the next official build, getting the Snap camera working out of the box would be a great deal!
[OnePlus 3 & 3T Cross Device Development] nitz2889:
No need of HAL 1 enabler, just install apk and you are good to go.
[OnePlus 3 & 3T Cross Device Development] Zenns:
how is the camera quality ?
[OnePlus 3 & 3T Cross Device Development] Uqbar:
With 0302 build the camera app forcecloses. Opencamera is OK and quality seems as good as the stock camera, when it used to work.

---------- Post added at 09:03 AM ---------- Previous post was at 09:01 AM ----------

Hi all.

It's not possible any more to block incoming calls from "unknown" and the option to use widcards is also gone.

I presume this is by design and not by mistake. But why?
[OnePlus 3 & 3T Cross Device Development] Defferex:
HAL3 enabled? I mean does HAL3 work with OB12 blobs or you just using HAL1?
[OnePlus 3 & 3T Cross Device Development] Zenns:
The Camera app is Snap.
[OnePlus 3 & 3T Cross Device Development] AcidNoteZ:
Hey Guys, I installed the latest nightly along with gapps, elemental x & Akt profiles.

I have a very slow mobile data on LTE about 400kb max

Is that a known issue or does it have anything to do with the AKT profiles?
[OnePlus 3 & 3T Cross Device Development] Uqbar:
I would suggest you to test incrementally: LOS, LOS+GAPPS, LOS+GAPPS+ELEX ...

It could be also a temporary issue on your operator, though.
[OnePlus 3 & 3T Cross Device Development] AcidNoteZ:
Okay, I'm gonna try it when i am at home.

I tried a speed test and the download went up to 4mb!

Downloading files is slow tho.
[OnePlus 3 & 3T Cross Device Development] DaReDeViL:
getprop persist.camera.HAL3.enabled

on experimental build, this commands returns 0 so HAL3 is disabled and HAL1 is enabled instead .
[OnePlus 3 & 3T Cross Device Development] themcfly:
Anybody have issues with Ambient Display? On my 3T the pulse on pickup never works. Hand wave really inconsistent, even really close to the sensor. I'm still on the latest nightly build by the way.

I saw this commit but I can't understand if it's related to the OP3/T branch or not:

https://review.lineageos.org/#/c/164267/
[OnePlus 3 & 3T Cross Device Development] AcidNoteZ:
Okay, i flashed the regular oxygen os and everything was fine.

If I switch to LOS its slow again.
[OnePlus 3 & 3T Cross Device Development] Defferex:
Sad.
[OnePlus 3 & 3T Cross Device Development] B3rt0:
How did you achieve that? I flashed OB12 and afterwards lineage-14.1-20170304-UNOFFICIAL-oneplus3.zip but still the post processing of a hdr or hq photo takes about 2-3 seconds. Can you help me understand what you did differently.
[OnePlus 3 & 3T Cross Device Development] nitz2889:
What I meant was quality and features as compared to o2os. Obviously the performance is going to get a hit on custom ROMs.

Not a single fc and all features working is something really commendable.
[OnePlus 3 & 3T Cross Device Development] B3rt0:
Ok. I thought you meant by flawlessly really flawless ;)
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
I get a 1 on latest Nightly.

I'm using Snap Camera HDR from PlayStore and Camera is working fine.

I have set my Camera App to use Camera2 API

L
[OnePlus 3 & 3T Cross Device Development] simmeone:
The latest nightly has a Bluetooth bug. When my mobile is connected with the car radio, the radio does not show called numbers/contacts. When I call a number with Bluetooth, this number isn't shown in the list of called numbers. This list is always empty, when I press the redial button in my car.

I can confirm, when the Bluetooth isn't connected, the symbol shows, that the mobile is connected with Bluetooth.

In nightly 20170214 is works perfect.
[OnePlus 3 & 3T Cross Device Development] djsubterrain:
Probably not, it says device_lge, that's LG phones. It's more likely to be LOS prepping an LG V20 rom as it shares the same processor : http://www.gsmarena.com/lg_v20-8238.php
[OnePlus 3 & 3T Cross Device Development] Deerar DS:
Hi guys,

Have any one noticed that automatic display mode isn't starting up sometimes! And if you were at night and go to settings > use 24 hours format and switch it on and off, the automatic display mode will work and apply the night mode!
[OnePlus 3 & 3T Cross Device Development] Defferex:
Can you test Oxygen camera port?
[OnePlus 3 & 3T Cross Device Development] themcfly:
Also suffering this one. Bluetooth remains paired after I switch off the car, and also it can't seem to import contacts to the infotainment system. On previous build 0802 it worked as expected.
[OnePlus 3 & 3T Cross Device Development] nadejo:
The performance on the latest experimental build is out of this world. An Aspahlt 8 race loads within 4 seconds, how is this even possible? :eek: and open camera managed to take 3500 pictures within 10-15 minutes burst mode high quality images.

Its not even overclocked. Didn't even flash a kernel. I wonder how fast this device will run when laos is more optimized ...kernel... Throttling... Cpu scaling... Im so amazed each week by this device.
[OnePlus 3 & 3T Cross Device Development] Defferex:
3500 pictures? So basically 3-4 photos per second? So I guess HAL3 enabled and works OK?

What device btw?

I doubt that you get this performance for free, battery isn't infinite.
[OnePlus 3 & 3T Cross Device Development] nadejo:
Oneplus3t. And the drain was lower than usual playing aspahlt 8. i ll make a video

And opencamera burst mode usually heats the device. But this time it stayed cood. And i can tell it was like at least 10 pictures a second, i forgot to mention that i made some pauses taking pictures.
[OnePlus 3 & 3T Cross Device Development] themcfly:
Hey, can you test if with the stock OOS Camera port the Beauty function crashes the camera? (not that I need it, I'm just trying to figure out all of this mess of 7.1.1 blobs, HAL1, HAL3, camera apps, and how they interact with each other). [MENTION=4837394]siankatabg[/MENTION] in his penultimate build told that everything was working on HAL3 and OOS Camera, but then a day after he switched back to HAL1 and Google Camera. I can't understand what is going on and which of the two routes would be ideal. Maybe [MENTION=5091734]dianlujitao[/MENTION] can chime in on this?
[OnePlus 3 & 3T Cross Device Development] siankatabg:
I was using hal1 with the oos cam, but video recording is broken for me on it. Beauty mode was working fine. Now I'm using hal3 and the Google camera.
[OnePlus 3 & 3T Cross Device Development] simmeone:
Yes, I confirm this, with the latest nightly no import of contacts to car radio with Bluetooth works! In the second February nightly it works all very fine. I hope this will fixed as soon as possible, otherwise I will downgrade, I use my mobile very often in my car :mad:
[OnePlus 3 & 3T Cross Device Development] nadejo:
Oneplus3t Using onepluscamera v5.apk (no flashing of any zip like hal enabler etc). . i can set hq and hdr. And 720p slowmo.

Also video recording longer than 40secs without issues. I noticed using hq or hdr it takes a second to save the image.
[OnePlus 3 & 3T Cross Device Development] Joloxx9:
What about 1080p@60 fps does it work? It important for me

Also have you flashed firmware from 7.1.1 beta or you are still using 7.0?
[OnePlus 3 & 3T Cross Device Development] Xellotath:
op3t with onpluscamera v5.apk, 1080p60 recording works fine. I didn't have HDR / HQ show until I flashed that zip though.
[OnePlus 3 & 3T Cross Device Development] nadejo:
​

I flashed only the beta3 firmware + uniblobs and latest experimental build. And no other zip like hal enabler etc. And yes 1080 60 fps is working fine.

---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------

What firmware files you have flashed? And what build you are using?

I wonder why you had to flash the zip to have it working
[OnePlus 3 & 3T Cross Device Development] Joloxx9:
Uniblobs?
[OnePlus 3 & 3T Cross Device Development] B3rt0:
What uniblobs file? I've read about that from you before but couldn't find any references to that. What do you mean by that?
[OnePlus 3 & 3T Cross Device Development] nadejo:
To all oneplus3t owners you have to flash these two red highlighted files (the bigger firmware file first then the small uniblob below) before !clean! flashing latest experimental build. Doing so you dont have to flash any hal enabler and only this way you will be able to dirty flash the next comming official builds. Other wise you have to do a clean flash when the next official build is out.

https://xdaforums.com/oneplus-3t/development/rom-lineageos-14-1-t3547024

To have oos camera working you only need oos camera v5 apk and oos galery v5.1 apk from afh

Edit: the uniblob file is in the second highlighted link. Its for roms using a kernel that works on both devices. This official cm build works on both devices so it includes a kernel that works on both. Thats why you should install the renamed uniblobs.
[OnePlus 3 & 3T Cross Device Development] Xellotath:
Using OnePlus3T_4.0.3_firmware with latest nightly
[OnePlus 3 & 3T Cross Device Development] nadejo:
So i guess you are not using the experimental build with the new open beta3 blobs

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

Just noticed im first on this thread. So i guess i will put some links and description on first page. So ppl dont ask again and again for the same things. Ill make it for both devices.