[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo]

Search This thread
By:
Advanced…
D

dcmandrel

Member
Mar 18, 2020
24
8
Madrid
Hi there,
I just flashed the ROM and Magisk Manager and everything is working perfectly except WiFi conexion. It connects and works great 80% of the time but sometimes it randomly disconnects and I have to manually enable it again just pressing on the WiFi network (picture attached).
I thought maybe it is related to WiFi battery saving mode? Is there any way to fix it?
Thanks in advance
 

Attachments

  • IMG_20200410_124630.jpg
    IMG_20200410_124630.jpg
    23.6 KB · Views: 310
R

rho-bot

Senior Member
Jul 1, 2017
256
104
I have a similar issue with Wifi connection:
Each time I reboot system, at startup the Wifi tries to connect to my network 3 times, but sth. during authentication seems to fail. After this, wifi is unconnected, my netork is even not shown anymore in the list.
When I disable/enable the Wifi, my network is shown again, and wifi tries to auto-reconnect, but fails. If I select it manually, it instantly connects.
But it also randomly disconnects during sleepmode with the same effect.
 
D

dcmandrel

Member
Mar 18, 2020
24
8
Madrid
I went to system > system profiles and modified the WiFi option to be turned on, for the default profile.
Been using it for a while and ok
 

Attachments

  • Screenshot_20200411-115521_LineageOS_Settings.png
    Screenshot_20200411-115521_LineageOS_Settings.png
    188.1 KB · Views: 411
Last edited:
pitrus-

pitrus-

Senior Member
Sep 4, 2011
1,278
575
Östersund
www.wickenberg.nu
dcmandrel said:
I think it's solved.

I went to system > system profiles and modified the WiFi option to be turned on, for the default profile.

Been using it for a while and so far so good.
Click to expand...
Click to collapse
That explains why it turned itself off all the time, it just did what was programmed to do, although you hadn't exactly told it to do so [emoji16]

I haven't clean flashed ever so can't speak if this is for some reason default, which it shouldn't be. I usually just turn off profile support as I don't need it.
 
D

dcmandrel

Member
Mar 18, 2020
24
8
Madrid
pitrus- said:
That explains why it turned itself off all the time, it just did what was programmed to do, although you hadn't exactly told it to do so [emoji16]

I haven't clean flashed ever so can't speak if this is for some reason default, which it shouldn't be. I usually just turn off profile support as I don't need it.
Click to expand...
Click to collapse

Still not working. When I'm watching videos on YouTube it disconnects every 2min.
I have disabled profile manager but the problem persists...
 
M

maruchandd

Member
Dec 22, 2017
46
14
pitrus- said:
You should follow Clamors repartition guide here

https://forum.xda-developers.com/ne...repartition-nexus-7-2013-repartition-t3844386

Check out my LOS daily builds at https://lineageos.wickenberg.nu
Click to expand...
Click to collapse

Just want to say I am glad I chose your LOS builds, other than Syncthing not working (not crucial to me for this device) I have had a flawless experience on this rom with many improvements over my ancient 5.x.x that I was too afraid to mess with.

I recommend this rom to others after months of use. However if you have particular app needs (some pepole just need Netflix, e.g.) be sure to research the best mod for your needs before pulling the trigger
 
  • Like
Reactions: Serpico_One
C

Covariant

New member
Nov 23, 2012
1
0
Getting Netflix working?

Everything I tried in this ROM seems to work great, apart from Netflix - I have tried a few different side-loaded versions, but get the same problem reported here (except once, out of many many attempts I was able to watch Contagion complete). I guess we don't know of a workaround for this ROM? Is this a problem with just this ROM or a general problem on custom ROMs?

Thanks!




schnee1 said:
This build us getting better with every iteration! Thanks for the work!

I have only 1 issue: Netflix does not work properly....

The app itself loads, I can see the tittles etc. However when I try to play any of the tittle the playback crashes after -30 seconds. Playback in the does not work till the next restart of the device, when it works for another 30 sec....

Earlier in this thread I uploaded some debug output which show some kind of codec crash. Other applications (example Amazon Prime video) works fine
Click to expand...
Click to collapse
 
M

MorpheusUK

Member
Mar 22, 2009
26
5
Magisk not working

Hi folks,
I'm a little stuck and need some help, I was planning to upgrade to the 17.1 build after a long time using this one without root but first wanted to back up my apps and app data via Migrate Ng or oandbackup.

I've installed Magisk 20.4 zip from TWRP (no errors), turned off aggressive doze in Naptime and added Magisk Manager to the not battery optimised list but anything that requests root permission is automatically denied no prompt. It's even denied if I set the default to grant

I guess I'm missing something either from the Magisk install or subsequent setup but I have no idea what. Is there something else that I need to do to get it working with this ROM on Flo? The Magisk log is below in case that provides any clues to what I'm missing:

--------- beginning of main
--------- beginning of system
07-18 14:43:27.911 217 217 I Magisk : Magisk 20.4(20400) daemon started
07-18 14:43:27.912 217 217 I Magisk : * Device API level: 28
07-18 14:43:27.953 217 218 I Magisk : ** post-fs-data mode running
07-18 14:43:27.957 217 218 I Magisk : * Initializing Magisk environment
07-18 14:43:28.026 217 218 I Magisk : * Mounting mirrors
07-18 14:43:28.026 217 218 I Magisk : mount: /sbin/.magisk/mirror/system
07-18 14:43:28.027 217 218 I Magisk : mount: /sbin/.magisk/mirror/data
07-18 14:43:28.027 217 218 I Magisk : link: /sbin/.magisk/mirror/vendor
07-18 14:43:28.027 217 218 I Magisk : link: /sbin/.magisk/mirror/product
07-18 14:43:28.028 217 218 I Magisk : * Setting up internal busybox
07-18 14:43:28.087 217 218 I Magisk : * Running post-fs-data.d scripts
07-18 14:43:28.090 217 218 I Magisk : * Running module post-fs-data scripts
07-18 14:43:28.091 217 218 I Magisk : * Loading modules
07-18 15:43:28.423 217 279 I Magisk : ** late_start service mode running
07-18 15:43:28.429 217 279 I Magisk : * Running service.d scripts
07-18 15:43:28.465 217 279 I Magisk : * Running module service scripts
07-18 15:43:56.487 217 1010 I Magisk : ** boot_complete triggered
--------- beginning of crash
07-18 15:46:06.180 217 3983 W Magisk : su: request rejected (10144)
07-18 15:46:06.180 217 4137 W Magisk : su: request rejected (10144)
07-18 15:46:06.180 217 4137 E Magisk : write failed with 32: Broken pipe
07-18 15:46:06.180 217 3983 E Magisk : write failed with 32: Broken pipe
07-18 16:26:36.409 217 25615 W Magisk : su: request rejected (10230)
07-18 16:48:11.656 217 32189 W Magisk : su: request rejected (10230)

Are there any pointers in the right direction you can give me?

Thanks,

Morpheus
 
Last edited:
M

mathiraj

Member
Apr 24, 2009
13
0
Nexus 7 (2013)
Moto E6
headphone detection problem?

Thank you for this wonderful ROM.

One thing i notice with this ROM is that it can not distinguish between headphones without mic and with mic.

*) If i connect a headphone with mic, the mic doesn't work. (though it is detected correctly as headphone with mic) It shows this icon
Mobile-Headset-icon.png
on the status bar

*) if i connect a headphone without mic, the icon still shows it is a headphone with mic (i guess it is wrongly detected?) It shows
Mobile-Headset-icon.png
icon instead of
headphones-512.png


is there any way to fix this? and get the microphone working on the headphone?
 
kozmo2k4

kozmo2k4

Senior Member
Nov 4, 2010
442
147
Nature Coast
Nexus 7
Sprint Samsung Galaxy S4
Anyone else has experienced system reboots after installing and opening the latest Firefox fro Play Store? It used to work just fine, until the major update of FF two weeks ago.
I wiped data, uninstalled, rebooted, re-installed, and it still reboots the tablet when I open Firefox.
The latest Fennec from F-Driod works just fine, but it is on it's last leg.

Sent from my TF300T using Tapatalk
 
A

anivegmin

Member
Mar 29, 2019
44
19
kozmo2k4 said:
Anyone else has experienced system reboots after installing and opening the latest Firefox fro Play Store? It used to work just fine, until the major update of FF two weeks ago.
I wiped data, uninstalled, rebooted, re-installed, and it still reboots the tablet when I open Firefox.
The latest Fennec from F-Driod works just fine, but it is on it's last leg.
Click to expand...
Click to collapse

Yes,same here. On both my Nexus 7 with LOS 16 and Nexus 5 with LOS 15. No idea why. I've reverted to using Chrome.
 
kozmo2k4

kozmo2k4

Senior Member
Nov 4, 2010
442
147
Nature Coast
Nexus 7
Sprint Samsung Galaxy S4
anivegmin said:
Yes,same here. On both my Nexus 7 with LOS 16 and Nexus 5 with LOS 15. No idea why. I've reverted to using Chrome.
Click to expand...
Click to collapse

I don't have the same problem on deb, but it is running LOS17. I guess time to back this one up, and upgrade it to 17 too.
I would never use Chrome.
Try Brave, Duckduckgo or Fennec (nightly Firefox, it will sync your account across devices and OS's).
Too bad there are no plans for Waterfox for mobile platforms....

Sent from my Nexus 7 using Tapatalk
 
Last edited:
杨

杨明星

New member
Oct 9, 2020
1
0
ROM包没有了。

---------- Post added at 02:23 AM ---------- Previous post was at 02:14 AM ----------

进入ROMs下载网址，显示“404 Not Found
nginx/1.19.2”。再发一个下载网址吧。
 
You must log in or register to reply here.

Similar threads

followmsi
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
Replies
4K
Views
915K
TamD
TamD
ripee
[ROM][DISCONTINUED][10] LineageOS 17.1 [deb][flo]
Replies
716
Views
188K
B
blaze2051
Scott
[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1
Replies
2K
Views
365K
S
Suici Doga
zaclimon
[ROM][OFFICIAL][KitKat 4.4.4][Flo/Deb] PAC-man 4.4.4.RC-1
Replies
1K
Views
219K
Memo13v
Memo13v
BeansTown106
  • Locked
[ROM][6.0.1][FLO]★ The Pure Nexus Project ★ Substratum ★ [08/21/16]
Replies
1K
Views
325K
BeansTown106
BeansTown106

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 81
    ripee
    ripee
    android-p-logo.jpg


    LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
    ​

    Code: 
    * [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.


    FREQUENTLY ASKED QUESTIONS

    (Please read them BEFORE posting anything in the thread!)​
    Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
    A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.

    Q: I am seeing Error 7 when trying to flash a GApps package.
    A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.

    Q: When will any of the variants receive official builds from LineageOS?
    A: Not before all the issues listed under "Bugs" below are fixed.
    Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.

    Q: What will some of the differences be between unofficial and official builds?
    A: The following technical changes will take effect:
    - Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
    - Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
    - The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
    Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.

    Q: How often will new builds be released?
    A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.


    [REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]


    ROMs
    pitrus-
    - LTE: deb
    - Wi-Fi: flo

    LineageOS Extras
    - addonsu-16.0-arm-signed.zip
    - addonsu-remove-16.0-arm-signed.zip

    Magisk

    Open GApps



    How to flash LineageOS and Open GApps​
    1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
    4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    5. Swipe to Wipe at Bottom of Screen,
    6. Back to Main start screen,
    7. Wipe > Format Data,
    8. Type 'Yes' and press blue checkmark at the bottom-right corner,
    9. Go Back to Main Start Screen,
    10. Move your LineageOS Rom and GApps Package to the internal storage,
    11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.


    Problems known to happen after a Dirty Installation​
    1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.

    * Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.

    * Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.

    Bugs
    - Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
    - You tell us!

    Changelog
    All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.

    Credits
    - Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.

    Sources
    - deb device tree
    - flo device tree
    - kernel
    - blobs

    XDA:DevDB Information
    LineageOS 16.0, ROM for the Nexus 7 (2013)

    Contributors
    ripee, followmsi, pitrus-, flex1911, Clamor
    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.x
    ROM Firmware Required: System partition large enough to accommodate the rom and GApps.

    Version Information
    Status:     Stable
    Current Stable Version: 9
    Stable Release Date: 2019-08-11

    Created 2019-02-22
    Last Updated 2019-11-10
    View
    13
    ripee
    ripee
    Switching to pitrus-'s builds!

    I have updated the links in the OP to point to his folders. He builds with the same sources as I do, which are followmsi's repos linked at the bottom of the OP. It will be up to him how often he build for deb and flo, but I will continue to maintain this thread and answer questions. I am working on other devices right now and my build environment doesn't have the space to keep building for deb and flo, but rest assured I still have my flo tablet and will enthusiastically and regularly flash pitrus-'s builds.
    View
    12
    ripee
    ripee
    Reserved
    View
    12
    ripee
    ripee
    Reserved
    View
    10
    ripee
    ripee
    Changelog

    Build 0301 for both variants
    * Synced with LineageOS sources.

    Since today is the day that Pie has become official, it's a good day to build even though our tablets are not among the lucky few devices. You can be sure that the builds are stable enough as daily drivers, with the exception of NFC.
    View

New posts