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

[f5bud]

I use for several days lineageos 16 and I have no problem. Only the compass does not work for me uses. A big thank you to all the developers.

 

[GuestK00160]

That's a discussion for another thread, this one is about development of LOS 16 for the deb/flo. Also, calling this "garbage" is really disrespectful towards the developer. It's really amazing to get an up to date Android on a 6 year old tablet, I'm really gratefull for the love given towards our oudated hardware. [emoji106][emoji4]

Skickat från min ONEPLUS A3003 via Tapatalk

Was talking about stock android 6.0.1. Im saying all roms are slow on this device except 4.3 and 4.4.

I still have a oneplus one and everything runs fine on that. This tablet however must have a very slow processor.

 

[jhford]

New dirty(?) install

Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.

I have followmsi's AEX 6.4 ROM installed on one of my 2 N7 debs which I repartitioned prior to installation. I want to try this ROM on one of them to see if the never-ending spontaneous reboots I'm experiencing will stop. Since "this is the same rom (Ripee's words)," can I dirty flash it on top of AEX 6.4? That would be great. But if not, I don't quite understand these instructions:
2. Download your LineageOS Rom and GApps Package,
[does this mean to download to my PC?]
3. Move your LineageOS Rom and GApps Package to the internal storage,
[this is the N7's internal storage, correct?]
4. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
[won't this delete the Rom and GApps?]
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
[hasn't the Rom and GApps been deleted in step 5?]

Thanks

 

[ripee]

I have followmsi's AEX 6.4 ROM installed on one of my 2 N7 debs which I repartitioned prior to installation. I want to try this ROM on one of them to see if the never-ending spontaneous reboots I'm experiencing will stop. Since "this is the same rom (Ripee's words)," can I dirty flash it on top of AEX 6.4? That would be great. But if not, I don't quite understand these instructions:
2. Download your LineageOS Rom and GApps Package,
[does this mean to download to my PC?]
3. Move your LineageOS Rom and GApps Package to the internal storage,
[this is the N7's internal storage, correct?]
4. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
[won't this delete the Rom and GApps?]
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
[hasn't the Rom and GApps been deleted in step 5?]

Thanks

Lazy copy-paste from another device on my part, but if you have experience in flashing other custom roms, do you really need instructions?

 

[jhford]

Lazy copy-paste from another device on my part, but if you have experience in flashing other custom roms, do you really need instructions?

Sorry. I figured it out. I used OTG. I also use your Trlte Rom for my N910T and love it. Great job on this ROM. Thanks for your help. Ripee now controls everything I have, one phone and two tablets.

 

[shuvabrata]

Which version of Gapps are you guys using? I am getting insufficient storage irrespective of whatever version I choose. Followed all instructions.

---------- Post added at 03:39 AM ---------- Previous post was at 03:28 AM ----------

I will try
thanks

--- Does not work... tried everything... stock, modify... format, reformat...

What did you finally do? Even Pico didn't work for me

 

[shuvabrata]

Worked finally

 

[f5bud]

Hello,
about the compass, I made a small program to test the return of the sensors.

Sensor.TYPE_ROTATION_VECTOR does not return a result.
Sensor.TYPE_GRAVITY, Sensor.TYPE_ACCELEROMETER and Sensor.TYPE_MAGNETIC_FIELD return a correct values.

If it helps developers!
Thank you for your work.

 

[dealpapa1]

finally move on to LineageOS 16.0. thank you ripee.

do you support ota?

 

[peterCR56]

finally move on to LineageOS 16.0. thank you ripee.

do you support ota?

IIRC you can only get ota from LOS official builds

 

[pitrus-]

IIRC you can only get ota from LOS official builds

Not quite true, my builds do ota... Tested on my flo [emoji4]

Skickat från min ONEPLUS A3003 via Tapatalk

 

[peterCR56]

Not quite true, my builds do ota... Tested on my flo [emoji4]

Skickat från min ONEPLUS A3003 via Tapatalk

If that's the case then i also would look forward to ota's for this build.
I've been rooting my phones now for about 5 years and have never been offered ota on any of the unofficial builds
that i've had which is what my answer was based on, so i stand corrected thank you for your reply

 

[ripee]

If that's the case then i also would look forward to ota's for this build.
I've been rooting my phones now for about 5 years and have never been offered ota on any of the unofficial builds
that i've had which is what my answer was based on, so i stand corrected thank you for your reply

In order to modify the OTA updater app to point to a custom download URL, that URL needs to be known or at least predicted prior to the build being run. This is possible if a traditional hosting server is used such that the download URL can be customized for each build usually because it includes the build's date-stamped filename or some other uniquely defining reference.

I upload all my builds to Google Drive because it's free. Unfortunately, Drive's download URLs consist of a unique file ID that is only generated by Google after each build is successfully uploaded, thus making it impossible to generate the download URL before the build is run.

The most straightforward hosting services are either a custom FTP server or BasketBuild, the hosting and bandwidth costs of the former can get expensive, while the latter suffers from random downtime. Even AFH generates a custom URL only after the build is uploaded.

 

[dealpapa1]

If that's the case then i also would look forward to ota's for this build.
I've been rooting my phones now for about 5 years and have never been offered ota on any of the unofficial builds
that i've had which is what my answer was based on, so i stand corrected thank you for your reply

oh yeah. we need ota for this build.

 

[dealpapa1]

best rom ever in my 7. I should upgrade that earlier. I am so happy.

 

[cedge]

I successfully updated my newly acquired Nexus 7 running stock Marshmallow ROM using a combination of the first post in this thread and the 'quickie guide to installing lineageos 15.1 on the Nexus 7 (2013)' posted on Reddit. It's my first Android device in quite a few years so I was a little nervous about the whole process even though the device only cost £40. Anyway, it all went well for the most part, I installed nano gapps alongside LineageOS 16 and the system is now running really well. I did have issues with loading maps in google maps but will restart and retest later. Thanks to everyone's efforts for providing and updating these ROMs.

I did almost come unstuck when I had completed all the necessary wipes before flashing and then had a head scratching moment in working out how to put the ROM and Gapps back on to the device as I couldn't work out the whole adb push commands in the reddit guide ; then I noticed that my computer had already detected the device so its internal storage was accessible to facility the transfer of the necessarily files.

One question I do have, is do I have to reinstall SuperSU to gain root access or is Magisk deemed the best option these days?

 

[ripee]

I successfully updated my newly acquired Nexus 7 running stock Marshmallow ROM using a combination of the first post in this thread and the 'quickie guide to installing lineageos 15.1 on the Nexus 7 (2013)' posted on Reddit. It's my first Android device in quite a few years so I was a little nervous about the whole process even though the device only cost £40. Anyway, it all went well for the most part, I installed nano gapps alongside LineageOS 16 and the system is now running really well. I did have issues with loading maps in google maps but will restart and retest later. Thanks to everyone's efforts for providing and updating these ROMs.

I did almost come unstuck when I had completed all the necessary wipes before flashing and then had a head scratching moment in working out how to put the ROM and Gapps back on to the device as I couldn't work out the whole adb push commands in the reddit guide ; then I noticed that my computer had already detected the device so its internal storage was accessible to facility the transfer of the necessarily files.

One question I do have, is do I have to reinstall SuperSU to gain root access or is Magisk deemed the best option these days?

As per the OP, my builds have lineage su root included, but you can flash Magisk anyway if you wish, and it will remove lineage su root before it flashes itself. SuperSU is yesterday's news.

 

[cedge]

As per the OP, my builds have lineage su root included, but you can flash Magisk anyway if you wish, and it will remove lineage su root before it flashes itself. SuperSU is yesterday's news.

Thanks and Doh! Sorry for probably a noob question, but can I flash Magisk via the TWRP App or do I need to do this in TWRP Recovery?

 

[ripee]

Thanks and Doh! Sorry for probably a noob question, but can I flash Magisk via the TWRP App or do I need to do this in TWRP Recovery?

TWRP recovery.

 

[grantd]

@ripee Just want to start off, great ROM. Went from official 14.1 to this and absolutely loving how it performs.

One question though, would it be possible to enable SELinux by default? That way if we unroot it will fully pass SafetyNet checking. When I enabled SELinux and then unrooted (but left my root shell open), SafetyNet passed completely (basic integrity and CTS profile match) but the battery status icon stopped working and showed as unknown. I then set SELinux back to permissive and the battery icon worked again. Not sure what else might not work right.....but I was able to launch and play Pokemon Go at that point with no battery status in the top bar.