[ROM][10.0][OFFICIAL] LineageOS 17.1

Semaphor_

Member
Jun 2, 2011
21
1
23
Lübeck
Thank you!

Dirty Flash (I was lazy) with Hotfix 1 Firmware from official LOS 16 with newest TWRP. Root, Wifi, everything works without a problem.

Thanks for your work on this :)
 

ccpower

Member
Nov 21, 2016
44
22
8
@T1mb3

I get the occasional "Wifi watchdog triggered: wifi fixed after restart" popup, doesn't seem to affect anything as wifi works just fine before and after getting that message. I searched this topic and gerrit to see if someone else reported it but i didn't find anything relevant. Device is the 5T, latest (and first) official 17.1 from last week.
Also, proximity sensor doesn't seem to work, at least my screen doesn't wake up while waving a hand in front of it.
 
Jul 18, 2013
11
4
0
Please note that any dotfix/other camera mod will not work with updated camera blobs!
Uninstall any mods before reporting bugs (as always)!
Thank you again for all your work !

Regarding your post, does it mean that installing the latest firmware (firmware_10.0.1_cheeseburger.zip 2020-11-13) alongside with the latest official LOS (lineage-17.1-20201116) will make the GCam (nikita or other + magisk dotfix mod) app not functionning ?

I run currently the firmware_10.0.0_hotfix1_cheeseburger.zip + lineage-17.1-20201110 with no issue. Do you recommand to stick with this configuration for the moment?
 
Last edited:

ekoo0823

New member
Nov 13, 2020
2
0
0
Hi @T1mb3
Thank you for your maintenance.
I flashed firmware-10.0.1 and lineage os-1116.But i think there are still some problems with firmware.
Q1:i can't choose a screenshot or photo in Tencent QQ,i don't see it in Tencent QQ.
Q2:flashlight and camera don't work.
Sorry for my bad english.
 
Last edited:

T1mb3

Senior Member
Feb 14, 2016
633
611
103
Thank you, that worked. So sorry about that.

Please see attached the kernel log
Please try flashing without any Gapps/Magisk or other extras. If wifi works there, then your gapps are broken.
Logs didn't really show much info, but the little info is hinting at gapps:

Code:
E WifiService: Permission violation - startScan not allowed for uid=10073, packageName=com.google.android.gms, reason=java.lang.SecurityException: Location mode is disabled for the device
 

DaminouTav

Member
Jun 2, 2014
17
0
21
Is it possible to remove empty space below keyboard ? Some others rom have this options into gesture settings. I understand it's needed for borderless screen, but it's not the case for O5/O5T...
Thanks!
 

LuisCarlosHK

Senior Member
Jul 21, 2012
80
6
28
Anyone use yahoo email app?
I had switch off the auto sync email at the account setting but the app still auto sync email.
Can someone teach me how to solve it?
 

AshenFire579

Member
Oct 8, 2020
22
0
1
Please try flashing without any Gapps/Magisk or other extras. If wifi works there, then your gapps are broken.
Logs didn't really show much info, but the little info is hinting at gapps:

Code:
E WifiService: Permission violation - startScan not allowed for uid=10073, packageName=com.google.android.gms, reason=java.lang.SecurityException: Location mode is disabled for the device
I just did a clean flash of the latest LineageOS 17.1 file (without GApps/Magisk) and Wifi still isn't working (see picture). Despite me turning it on, Wifi is displayed as being off and is not working.

I've attached another log of boot-to-WiFi in the hopes that it may be helpful to you. I also attached another kernel log (I don't know if it's needed but just in case).

I couldn't find the above code ("WifiService: Permission violation . . . ") in the log.

I hope you're able to locate the problem as everything else about this ROM works perfectly for me.

Edit: I don't know if this will be helpful at all but I've also attached a picture of my wifi folder from root/data/misc/wifi.
 
Last edited:

Spidersoft

Member
May 19, 2009
43
7
28
I cant't change caller volume while talking. The slider appears when i press the rocker but it has no effect. Anybody else has this issue or could it be my dirty flash?
 
Jul 18, 2013
11
4
0
lineage-17.1-20201117-nightly-dumpling-signed.zip and 10.0.1 fw

- No trouble with Mobile network, Wifi, BT ... so far.
- Safetynet passes with Magisk, as expected ... (cf. this post)
- GCam ok ... (don't forget to remove OnePlus 5/5T Front Camera Fix (V5.7))

Thx @T1mb3 !
Hello,

I run currently the officials firmware_10.0.0_hotfix1_cheeseburger.zip + lineage-17.1-20201110 (first official release).
May you please tell me if I need to re-flash GApps (and eventually Magisk) if I update with the latests firware & LOS 17.1 ?
Thank you for your help :)
 

Eric_Lev

Senior Member
Jan 27, 2019
1,070
2,126
138
Angers
androidfilehost.com
Hello,

I run currently the officials firmware_10.0.0_hotfix1_cheeseburger.zip + lineage-17.1-20201110 (first official release).
May you please tell me if I need to re-flash GApps (and eventually Magisk) if I update with the latests firware & LOS 17.1 ?
Thank you for your help :)
No need to re-flash Open Gapps.

Note: I uninstalled Magisk and removed screen lock before flashing 10.0.1 fw & latest build... (optional, but to be safe).
 
Last edited:

AshenFire579

Member
Oct 8, 2020
22
0
1
I installed the official build of LineageOS 17.1 on my Oneplus 5 today however during the initial setup process I couldn't connect to a WiFi network (it just kept searching). I skipped this process and used my data for the rest of the setup and then when I went into the WiFi I noticed that the WiFi would turn itself off after about 5 seconds of me turning it on.


These are the steps I took during the flashing process:

- Backed up phone

- Wiped everything and formatted data

- Flashed the latest firmware (firmware_10.0.1_cheeseburger.zip)

- Flashed LineageOS 17.1 (lineage-17.1-20201110-nightly-cheeseburger-signed.zip)

- Flashed Pico Open GApps

________________________________


Flashing the older Hotfix 1 firmware didn't work as that caused a bootloop on my phone.


If anyone has experienced this or knows how to fix it please do respond to this.
UPDATE: WiFi has been fixed with the help of T1mb3.

According to them the WiFi Mac address which was stored in a bin folder was incorrect. This issue is planned to be fixed in the next official build should anyone else experience it.
 
Last edited:

Besuz

Member
Feb 3, 2017
24
6
0
Lübeck
v6.0 is out and works with latest Firmware:
https://www.celsoazevedo.com/files/android/google-camera/op5fix/v6-0/

Only thing which I was not able to get working, is second back camera.

Edit: Just had to enable second camera in settings. :D

Edit2: My Wifi issue is also fixed, but i dont think it was a Rom related issuse.
I was also setting up a new Unifi Wifi-Controller last weekend and enabled 802.11r "fast roaming", which seemed to cause the issue. When I disable 802.11r on my networks, Wifi is working fine!
 
Last edited:

wizardknight

Senior Member
Nov 1, 2009
1,000
293
103
Seattle WA
Does anyone know a way to get notification sounds to route to both the phone's speaker and Bluetooth when a Bluetooth headset is connected?
I keep missing notifications if take my headset off, and it is very annoying.
I know I used to be able to do this on older versions, but I will be damned if I can find that setting in v17.
 

NazuNalika

Member
Jun 30, 2014
9
1
0
At one point, when I moved from LineageOS 16 official to 17.1 unofficial, I ran into some weird file permission issues. On the official builds, I'm still having the same issues. For example:

  • Screenshots do not show up at the top of the list in the gallery
  • Pictures sometimes taken with the camera do not show up properly or show at the bottom of the list
  • Gallery doesn't update half the time
  • Timestamp of files are 1969

The one way "around" this is I just reboot and things are fine after, but not for any new files, pictures, or screenshots. It doesn't make sense why this started happening. I tried wiping cache, davlik, and the like. Same problems. And just like with the old official, I did a full clean flash and I got the same problems. I'm not entirely sure why any of this is happening. Any suggestions on where to go from here?

---------- Post added at 02:08 AM ---------- Previous post was at 02:08 AM ----------

At one point, when I moved from LineageOS 16 official to 17.1 unofficial, I ran into some weird file permission issues. On the official builds, I'm still having the same issues. For example:

  • Screenshots do not show up at the top of the list in the gallery
  • Pictures sometimes taken with the camera do not show up properly or show at the bottom of the list
  • Gallery doesn't update half the time
  • Timestamp of files are 1969

The one way "around" this is I just reboot and things are fine after, but not for any new files, pictures, or screenshots. It doesn't make sense why this started happening. I tried wiping cache, davlik, and the like. Same problems. And just like with the old official, I did a full clean flash and I got the same problems. I'm not entirely sure why any of this is happening. Any suggestions on where to go from here?
 

InsaneNutter

Senior Member
Jun 26, 2010
172
110
73
Yorkshire
  • Screenshots do not show up at the top of the list in the gallery
  • Pictures sometimes taken with the camera do not show up properly or show at the bottom of the list
  • Gallery doesn't update half the time
  • Timestamp of files are 1969
I clean flashed the first official build and I'm also finding all of the above, except the timestamp of the files are correct for me.

Possibly an issue with the gallery app as the screenshots will show up at the top of the list as expected when sending an image via WhatsApp or Facebook Messenger.

On the Lineage Gallery app screenshots are ending up in the middle of the gallery on the album view and near the bottom of the current date range on the timeline view.