yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] hgmichna:
Capacitive buttons back light

To my knowledge they wear out and become ever dimmer on all OnePlus One phones. They certainly have on all four OPO phones in my vicinity.

People get used to where they are located and press them, even if they cannot see them.

I personally chose to activate the on-screen nav bar, which shuts down the hardware buttons. I think they are the wrong way around anyway. I used to swap the left and right one by modifying a system file, but the soft on-screen keys are in the right positions (in my view) and have other advantages too.
[ONE Original Android Development] Kurt Krummbein:
Perhaps, your old adb-server was still running while you where trying to unzip the new version ... then windows can't overwrite the dlls and exes.

Doing a "adb kill-server" before unzipping solves this. Maybe you're running now a mix between versions, just to be safe, you should unzip new platform-tools again.

Cheers

Kurt
[ONE Original Android Development] JT1510365:
Notification light still does not work at all for the march 3rd 2019 build when kernel is set to enforcing which its set to by default. Are you guys going to fix it any time soon because I am thinking to just forget about pie and go back to either the nougat or Oreo lineage os builds. Why release pie officially so early when this bug still has not been fixed yet I'm just curious?

---------- Post added at 05:57 PM ---------- Previous post was at 05:53 PM ----------

Backlight keys on the opo are not that bright by default its just the way they are made. They don't wear out oneplus just makes them very dim by default for some reason. You can increase the button brightness in settings though but it won't be very bright because that's how its always been:)
[ONE Original Android Development] jrior001:
I already said it wasn't going to make it in time for today's build. I found the fix the first day but there was some discussion on how global the change should be and it hasn't been merged yet.

https://review.lineageos.org/c/LineageOS/android_system_sepolicy/+/242951 is the solution, when that gets merged it's fixed. I also spent 3 hours today testing upgrade scenarios to confirm and confirm a solution to the few users with 14.1->15.1->16.0 camera issues. Hopefully that gets merged later today as well
[ONE Original Android Development] JT1510365:
why do you have 200 apps that must make your phone so laggy! Why do you need 200 apps I am fine with about 20 or 30 I would never have 200 on my phone:)

Yes android is designed to be upgraded but that's only if you are on stock official ROM because instead of downloading the full ROM you download the ota instead when you want a newer android stock rom version which has the necessary files to upgrade your version. Its not the whole ROM which is why it does not cause issues. But dirty flashing lineage 16 newer builds over the old los 16 build is fine too:)

Cheers

---------- Post added at 06:06 PM ---------- Previous post was at 06:04 PM ----------

No problems like that on my phone

---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------

Okay thank you for clarifying I must of misunderstood:)
[ONE Original Android Development] Chrizl577:
Good to know those problems will be fixed soon. Are there any news regarding NFC as it doesn't seem to work at all?

After upgrading from 15.1, I also noticed another problem: Scrolling is really laggy in some app, for example Action Launcher. Scrolling through the app drawer is really laggy, other scrolling (betwenn home screens) is perfectly smooth. Other launchers scroll smooth too. This might be a problem of the app, however, I noticed the lags in other apps as well.
[ONE Original Android Development] drezz2:
Yes, I know that it should be something very punctual when you are not really using it, by weight I thought that it was still a problem of the "rom" although I do not have the latest if I have been updating previous versions and I have always had it, the same with the "wifi zone", once active even if you remove it, bbs marked awake continuously.

If I found a way to minimize it without restarting it was to activate and deactivate the GPS and Wi-Fi zone several times (leaving it disabled), but I don't think it's normal (I understand that while the Wi-Fi zone is active it is in wakelock, even if you don't have a device connected , but I don't understand the same behavior with GPS if it's only enabled but not in use)
[ONE Original Android Development] grzesiek811:
I have huge throttling when battery saving on. How to fix it?

In general Lineageos 16 is much slower than 15 was.

Unfortunately there is no stable version Lineageos 15 in main download page Lineageos team.
[ONE Original Android Development] Lanchon:
not only that: AFAIC remember, the phone was able to discern a bad pattern from a good one. only if you entered the good one, unlock failed somehow and the lockscreen popped up again. for whatever stupid reason, even though the my adb client is authorized, in Pie its being kicked out while the phone is locked. this is stupid as hell, cause i couldn't see the logcat to find out what was happening.

so i used this mirror:

https://xdaforums.com/oneplus-one/o...eageos-14-1-oneplus-one-t3543489/post78751582

and setup LOS migration build

then latest LOS 15.1

and i left it at that, without upgrading to pie. no unlock issues.

so i was able to upgrade from CM 13.0 to LOS 15.1. not perfect, but huge improvement.

thanks!
[ONE Original Android Development] incoog:
Am I doing something wrong? I can sideload and everything boots up just fine, but when I flash gapps I get stuck in a bootloop.

I've tried different variants, micro, nano, pico. I've tried flashing right after flashing OS and flashing after reboot but same thing everytime.

What am I doing wrong?

I chose Platform ARM, Android 9.0.
[ONE Original Android Development] :
Today's opengapps is broken, that's the cause of your issues. Take an older release, the last one before todays, for example
[ONE Original Android Development] incoog:
Thank you! Now it works!
[ONE Original Android Development] :
Great to hear! The thanks button will be your friend ;)
[ONE Original Android Development] Blackov:
I hope it is ok to post this here.

But I can't get LOS16 running on my OPO.

I use TWRP 3.3.1.0 to flash

I've tried:

The latest nightly of LOS, the oldest available on the LOS site and a random one in between.

The latest (yesterdays and today's) GApps, and an older (Oct 6) Gapps.

Clean and dirty flash.

I also tried first flashing the modem driver (saw this in another topic somewhere)

The flashing works without a problem, there are no errors.

But my phone just gets stuck in the bootloop animation (the orb on the line) for 15min. After that my phone just reboots and opens TWRP.

If I reboot it again, the same thing happens.

So what am i doing wrong andis there a way to fix this?

Thanks!
[ONE Original Android Development] :
Mmmh, maybe your system is now a bit mixed by these many flashes ...

Let's start with deleting system, data (without deleting media), cache and dalvik cache.

Now, flash latest Los together with opengapps nano 6th Oct without rebooting in between. After these two flashes reboot into system. Does it boot?
[ONE Original Android Development] Timmmmaaahh!:
First try [MENTION=2044343]accuphase[/MENTION]'s suggestions. If it still won't work, try this TWRP instead. It might also help to flash CM13 first (and wipe again). More info on this via my signature.

I must've flashed that device 500 times... :eek:
[ONE Original Android Development] fmc000:
Are you sure you flashed the correct gapps? You have to use ARM (not ARM64) and only nano or pico.
[ONE Original Android Development] :
What I meant is that he may doesn't know what's done at the end of flashing several versions of Los and opengapps forth and back, clean and dirty, ... ;)
[ONE Original Android Development] Blackov:
Already tried that. That's what I meant with clean flash. So sadly, no. It doesn't boot that way. But thanks anyway :)

---------- Post added at 09:22 PM ---------- Previous post was at 09:13 PM ----------

I think I had CM13 installed in the past (not sure though). But now I'm running LOS14.1

But will try it later anyway:fingers-crossed:

EDIT:

I tried the TWRP and that was enough to get LOS16 running. Thanks!

Can you explain on how this is possible?

---------- Post added at 09:23 PM ---------- Previous post was at 09:22 PM ----------

Yes i'm using ARM pico. I even tried without gapps. Doensn't work either. I also tried installing los16, rebooting and then installing gapps. No luck :(
[ONE Original Android Development] Blackov:
I tried the TWRP first without the CM13. And it works.

Strange how that can make a difference.

Thanks!
[ONE Original Android Development] VA_DOS:
I had a similar story as [MENTION=9178985]Blackov[/MENTION]:

Initially I had CM13.1.2 + TWRP 3.0.3-[something]-TugaPower and would like to move to the LOS16 2019-10-12.

My steps were:

1. Install TWRP 3.2.1-K2 by Kutep0v (found this suggestion first)

2. Wipe everything (system+data+cache+dalvik) except the internal storage

3. Install LOS16 2019-10-12 + open_gapps-arm-9.0-pico-20191012

4. About 15 mins of the boot animation... and it fails to boot :( Followed by reboot back into TWRP.

Then I found another suggestion: "if you're moving to LOS16 the very first time, you have to install the initial LOS16 2019-03-01 build + gapps first, then you can update to desired version".

Tried that (with the same kind of wipe)... And the LOS16 2019-03-01 + open_gapps-arm-9.0-pico-20191012 boots fine!

However it was premature celebrating. After applying the LOS16 2019-10-12 update through the "Settings - System - Update" I was kicked back to initial issue - TWRP installs it fine with Status 1 OK, trying to boot... ~15 mins of the boot animation and falling back to TWRP.

Found this topic with a recommendation to use the gapps 20191006.

One more wipe. LOS16 2019-10-12 + open_gapps-arm-9.0-pico-20191006 still gave me the same boot loop.

My next attempt was to update the TWRP to version 3.3.1-K1.

Wipe. And... the LOS16 2019-10-12 + open_gapps-arm-9.0-pico-20191006 boots fine so far! :)
[ONE Original Android Development] Moksu:
I was trying to do the same as you, but I had Lineage OS 14.1 before.

I am still getting stuck on a boot loop even after installing open_gapps-arm-9.0-pico-20191006 with K1 twrp. I guess there is nothing I can do? :(

edit: seems like I was able to boot into the OS by skipping the TWRP app installation at TWRP reboot screen.
[ONE Original Android Development] Timmmmaaahh!:
In my experience, patched versions of TWRP always work much better than official releases. I can't officially explain this but IMHO I believe this is due to the very wide coverage of TWRP. They support pretty much any major device so development happens quite generically. Maintainters for devices may not even be devs and "just" compile every release. If you have a dedicated dev that forks TWRP for a specific device, new doors open and there will be more focus on supporting available ROMs (in this case: LOS) for that device. TWRP team also seems to avoid features such as EFS backup/restore while forks enable the full potential of our recovery. I honestly have no idea why; these elements are key tools in successful and safe flashing. Perhaps it's some liability protection.. Who knows. I'm glad you got it running :)
[ONE Original Android Development] VA_DOS:
Anyone have issues with updating the song's title, artist and other info via Bluetooth AVRCP/A2DP with this firmware?

For me all the audio players I've tried were able to send only the initial audio track's info right after the A2DP connection. But failing to update it on next/prev track navigation.

edit: ok, I've found the "AVRCP version" option in developers settings. Currently it's set to v1.4. I'll try some experiments later.

edit 2: it seems works being set to AVRCP v1.3 for my 2015 Subaru stereo
[ONE Original Android Development] Blackov:
Thanks for the explanation.

But it seems I don't have it running... It works fine, for a day... Then I cant unlock my phone... I enter my pin, screen goes dark as it would unlock, but then it just goes back to the lockscreen...

Edit:

So I went back to LOS14.1...

I tried deleting cache and Dalvik cache, didn't work. Reinstalling (dirty) LOS doesn't help. Booting in safemode does nothing.

The only thing that helps is restoring a LOS16 backup. Which fixes the problem for a day or so.

What the f-ing F could causing this? I did not install any new apps. I did notice, however, that some apps are installed twice, like: clock, calculator...

So help? :)

Thanks!
[ONE Original Android Development] fmc000:
I had the same bug and ended up leaving LOS for POSP because it seems that only LOS is affected.
[ONE Original Android Development] eiwarmer:
Soooo if the media volume is turned down and I record a video it doesn't record any audio whatsoever? Why :eek:
[ONE Original Android Development] LTMendarynas7:
Is it only for me that stock camera takes flipped pictures? It went full 180 no scope yolo after 20191015 nigthly. I don't know if older ones got that same issues, because I update only when monthly security updates are merged
[ONE Original Android Development] ze7zez:
The camera takes photos correctly after upgrading from fresh lineage-16.0-20190926 to lineage-16.0-20191017.
[ONE Original Android Development] wzzupp548:
I also had same problem, it has something to do with systemui not loading correctly. Had it happen a few weeks, ago and then right now again. Time for a change :)
[ONE Original Android Development] hkponxda:
I'm installing custom rom for the first time

I'm on CyanodenMod 13.1, Android M.

Now, how should I proceed?
[ONE Original Android Development] Timmmmaaahh!:
Ooh, exciting first steps into flashing! And you've got the perfect device to do it on. As you're still on COS, I would recommend to install CM13 first. In my signature you can find a quite detailed guide with links that explains everything you need to do step by step. If you have any doubts or questions, do not hesitate to ask. Most of all: have fun! Don't panic if something goes wrong. Even if it all seems lost, there's usually is a way to fix it on Android.

Wrapped with delicious Fajita [emoji896]
[ONE Original Android Development] customAdvocate:
Phone does not connect to WiFi with hidden SSID

I changed the configuration of my WiFi to hide the SSID...

Today I tried to connect my good old OPO with the Wifi-Network but I failed.

Usually the phone should connect to the newly added Hidden WiFi network when in proximity of the network. (Like my Oneplus 6)

Current Behaviour:

Phone not only does not connect but the hidden network does not show up in the available networks.

Is this a known issue?

Just for your information I added the SSID as a hidden one, so there should not be any issue in my settings
[ONE Original Android Development] drezz2:
I thought I saw in some article that for the one they were going to take lineage with Android 10? is that so?
[ONE Original Android Development] Timmmmaaahh!:
If you'd have searched this thread for "hidden", you would know its a known issue.

What I'd try:

remove the network from my phone

make the network visible in your router settings

add network again into the phone

let it stay connected for a little while

hide the network on the router

change hide settings on the phone

hope it connects now (let it settle for a bit first, reboot a few times)

Wrapped with delicious Fajita [emoji896]
[ONE Original Android Development] SethGeckoXDA:
The issue was discussed here. However, the devs were not able to reproduce it. Feel free to submit additional information about your network which might help make it reproducable.
[ONE Original Android Development] fmc000:
Just look at the Lineage 17.0 gerrit. There are no Bacon related commits.
[ONE Original Android Development] drezz2:
ok, I can not find the article I saw, looking again I have seen others that refer but nothing conclusive, is it possible that the bacon dies with android 9 not?

Sorry for the ignorance what is "Lineage 17.0 gerrit."? I mean where can I see that?
[ONE Original Android Development] fmc000:
https://review.lineageos.org/q/branch:lineage-17.0
[ONE Original Android Development] Tomoms:
This is not important. The fact that no one is working on bacon now doesn't imply that no one will work on it in the future. Other msm8974 devices are under active development in the lineage-17.0 branch. My little development skills & experience make me think that it's not impossible for us to take advantage of the work of other devs who develop for the same platform we have got. Just be patient and wait. If magic can be done for us, someone will take care of doing it :)

There's simply no point in worrying so much now, it'll take several months for the LineageOS team to implement all their custom features into the ROM anyway!
[ONE Original Android Development] saywa:
https://github.com/LineageOS/android_device_oneplus_bacon/commits/lineage-17.0
[ONE Original Android Development] drezz2:
retaking this issue, a doubt, if in both captures different units are being used (although in both I put GB) if my operator offers me 15gb I understand that they are 15 gigabytes not 15 gib?

So, in limit should I put 13.96? (I think in the limit section the unit used is Gib and in the other it is GB?)
[ONE Original Android Development] dinny:
https://www.getdroidtips.com/lineage-os-17/

In the upcoming list, there is One Plus One ;)
[ONE Original Android Development] Tomoms:
Please, please, please stop paying attention to these garbage websites who only publish articles with clickbait titles, filled with shallow words that mean absolutely

nothing

and are not based on any official statement nor any true evidence of what they state. Every year they spam the web with their useless tutorials and forecasts about alleged "LineageOS release dates" or "lists of supported devices", yet they know absolutely nothing and are barely able to pull together a list of unofficial builds found on XDA.

I'm confident that we'll get LineageOS 17 sooner or later, but trust me, it won't come because they say it will.

I'm sorry for this outburst, but I'm sick and tired of these websites and their balderdash. All the info you need can be found here on XDA, in the posts of the devs, maintainers, and experienced users who actually know what they are saying.
[ONE Original Android Development] daniga74:
Installed LOS 16 on my bacon and the ROM works very well; could someone confirm that slow motion video and lookscreen message doesn't work?
[ONE Original Android Development] hystrix65:
Hi all, I' ve installed tugapower on my bacon, i'd like to change to Lineage 16, can i install it over my tugapower, after classical wipes, or should i do something different? Thanks
[ONE Original Android Development] flug32:
I believe the official word is the two roms are different enough you should clean flash when switching one to the other. But unofficially they are similar enough that you could probably try dirty flashing.

Not sure if that really helps! Some general discussion here.
[ONE Original Android Development] hkponxda:
Help
[ONE Original Android Development] trancinguy:
What was your setup and what were you planning?
[ONE Original Android Development] Loriot:
Your TWRP is to old for LOS16. Use this one

https://xdaforums.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
[ONE Original Android Development] hkponxda:
Installed LOS 16 successfully but camera is way to blurry.
[ONE Original Android Development] hkponxda:
Phone app(dialer) automatic stops whenever I check call history.
[ONE Original Android Development] thx84:
Have you checked your permissions?
[ONE Original Android Development] hkponxda:
For dialer im using Google phone but camera ain't good.
[ONE Original Android Development] Flounderist:
Try this camera

https://drive.google.com/file/d/1Z7at0nCRdE9WOrE4PxbKll3qHGmChBDH/view?usp=drivesdk
[ONE Original Android Development] hkponxda:
LED light won't light up while charging on switched off phone.
[ONE Original Android Development] harsha1097:
while flashing LOS 16 nightly stuck at 47% saying * failed to read command: No error
[ONE Original Android Development] eiwarmer:
Maybe incomplete download, did you check the hashes?
[ONE Original Android Development] drezz2:
what camera is?
[ONE Original Android Development] Flounderist:
It is the latest GCam available for bacon.

It's version 3.2.045
[ONE Original Android Development] harsha1097:
Can you explain briefly how to check Hashes of Downloaded Lineage OS 16 zip file in Windows 10?
[ONE Original Android Development] SethGeckoXDA:
Open a command-line interface (WIN key + R)

Type

cmd

Hit Enter.

Type

certutil -hashfile <pathToFile> SHA256

Replace <pathToFile> with the complete path to the file you want to calculate the checksum of (e.g. C:\Users\WindowsSucks\Downloads\lineage-16.0-20191113-nightly-bacon-signed.zip).

Hit Enter.

Compare the resulting string with the one on the download page (click on the link which says sha256, depending on which file you downloaded).
[ONE Original Android Development] eiwarmer:
Lol I see what you did there :laugh:
[ONE Original Android Development] smechacha:
Front camera bug

Does anyone else have a problem with front camera? I did a clean full wipe flash and still cannot get it work This problem also oddly occurs on my nexus 5 device as well. Did I miss something from the logs? Is this a known bug?
[ONE Original Android Development] drezz2:
the changelod indicate

"

Base 'call recording allowed' decision on current country.

android_packages_apps_Dialer "

This means that they have enabled the possibility of recording in places where it was not before and has been removed in others? Is there a way to know that list of countries?
[ONE Original Android Development] SethGeckoXDA:
There are some known issues with the camera. For me, the front camera works well.

Try using an app like "Open Camera".

No. Call recording now depends on the country you are currently staying in. Before it depended on where you purchased your SIM card from.

I don't know if there is an official list. You can visit this page and click on the Expand All button. Then simply CTRL + F and type the country you are looking for. If it says

<bool name="call_recording_enabled">false</bool>

call recording is disabled for this country, obviously.
[ONE Original Android Development] drezz2:
Thank you, I had seen one or two, but I had not noticed that put the name of the country in the file :cyclops::eek:
[ONE Original Android Development] smechacha:
I don't get the option to flip the camera at all with default camera app, like the system doesn't recognize its existence.

With google camera I get the option to flip when recording is selected but then does nothing and some other camera from play store gave me an error to connect while trying to switch to front camera.

Very peculiar behavior that also happens on my n5 which is on latest official LOS for that device (I think LOS14).
[ONE Original Android Development] SethGeckoXDA:
The flip option is greyed out? Can you take a screenshot when using the camera app and upload it?

Also some additional info (Settings - About Phone - Android version):

- Baseband version

- LineageOS version

Have you tried other custom ROMs as well?
[ONE Original Android Development] smechacha:
It's pretty much non existant (with gcam disappears moment after turning on the app)

Here are the pictures:
[ONE Original Android Development] eiwarmer:
Did you try to clear data and cache of the camera apk?
[ONE Original Android Development] eldin90:
[MENTION=2836769]jrior001[/MENTION] can you please help me with this?

https://xdaforums.com/oneplus-one/help/how-to-transfer-recovery-file-to-phone-t4005555

After trying to update to the latest version of LineageOS and failing, my phone now boots directly to TWRP every time. And I can't boot to OS no matter what I try