[ROM][OFFICIAL][fajita][9] LineageOS 16.0

Search This thread

the00guy

Senior Member
Jul 14, 2010
226
32
It took me forever to figure this out, but a change in android is the problem. Go into developer options and uncheck "verify apps over usb". This should allow TB to restore apps again. The hard part is remembering to do this the next time.
Wow! That should be a pop up in Titanium like the usb debugging notification if that's causing restoration to break across the board! Hopefully the dev is aware, thanks for that invaluable tip!
 

5umi

Member
Jul 17, 2010
5
0
Just as a general question, what is everyone using to migrate apps between ROM reinstalls nowadays? I've all but given up on Titanium as it's been unable to restore backup data on lineage 16 as of the last 6 months or so for me. I've also tried Migrate, but it too was giving errors on restoring the data. I'm wondering if this is symptomatic of an inherent issue with my app data or if both apps are just not working as intended with the recent versions of lineage for the 6t. Thanks!

I'm new to TWRP, but here's my question: why would you prefer TB or any other software over the Backup feature from TWRP?
 

dwardo

Senior Member
Jan 15, 2011
527
434
France
OnePlus 6T

Attachments

  • IMG_20200221_221107.jpg
    IMG_20200221_221107.jpg
    75.1 KB · Views: 241
  • Like
Reactions: niphoet

the00guy

Senior Member
Jul 14, 2010
226
32
I'm new to TWRP, but here's my question: why would you prefer TB or any other software over the Backup feature from TWRP?
Mostly because TB will allow you to flash another rom/a clean flash of a rom and then restore your apps and/or their respective data. This is helpful if you screw up the rom and it becomes unbootable, infected, slow, etc...and you want to start fresh or swap to a new rom without losing your app data (especially for the majority of us who don't want to give all of our personal data to Google through Google app backup).

TWRP Backup/Nandroid is great for backing up your ROM and reflashing it back to the exact state that it was at, filesystem, data, and all, in the case of screwing something up and effectively needing to undo what you did.
 
  • Like
Reactions: 5umi

sajeel

Senior Member
Mar 11, 2007
147
12
OnePlus 5T
OnePlus 6T
I can only link to this post from OhioYJ: Installation steps for LineageOS
Pay attention to the version of OOS you are coming from and proceed accordingly.

These steps have worked out for me, after much trouble and frustration.

Brilliant followed and worked a treat the only thing to add was how to switch slots in twrp but im sure anyone flashing should be aware of that anyway.

Very happy with rom and stability well done again lineageos
 

OhioYJ

Senior Member
Feb 25, 2011
1,536
797
Brilliant followed and worked a treat the only thing to add was how to switch slots in twrp but im sure anyone flashing should be aware of that anyway.

Very happy with rom and stability well done again lineageos

Normally you shouldn't need to switch slots in TWRP. The ROM will automatically flash to the opposite slot, when you reboot to recovery it will reboot to that slot.
 
  • Like
Reactions: sajeel

the00guy

Senior Member
Jul 14, 2010
226
32
Any updates on if the camera focus issue has a workaround? Every camera app seems to lose focus as it's snapping the picture. The only temporary remedy I've found is rebooting the phone. I did a clean install of LOS and the issue persists.
 

derekn13

Member
Jun 26, 2014
10
10
Any updates on if the camera focus issue has a workaround? Every camera app seems to lose focus as it's snapping the picture. The only temporary remedy I've found is rebooting the phone. I did a clean install of LOS and the issue persists.
I've been seeing the same problem, with both the LOS camera app and OpenCamera.

I just discovered the "Camera2 API" setting in OpenCamera, and that seems to have fixed the problem. I will admit that I've only done a little bit of testing so far, and that I'm not really sure exactly what this setting does. Can anyone else verify this?
 
  • Like
Reactions: the00guy

the00guy

Senior Member
Jul 14, 2010
226
32
I've been seeing the same problem, with both the LOS camera app and OpenCamera.

I just discovered the "Camera2 API" setting in OpenCamera, and that seems to have fixed the problem. I will admit that I've only done a little bit of testing so far, and that I'm not really sure exactly what this setting does. Can anyone else verify this?
Oh wow thanks for the tip! This has been bothering me for over a year now! Just switched to that setting, I'll happily test it out.
 

the00guy

Senior Member
Jul 14, 2010
226
32
Oh wow thanks for the tip! This has been bothering me for over a year now! Just switched to that setting, I'll happily test it out.
Reporting back, this seems to be the fix! It seems that the stock camera isn't using this API that the option fixed in OpenCamera. Much thanks again for the tip!
 

OhioYJ

Senior Member
Feb 25, 2011
1,536
797
Is this a pretty stable rom like the camera and everything working ok, I'm still in the thinking stages and haven't even rooted my phone yet?

This has been stable for a long time. Even the unofficial LOS 17 is very stable in my opinion. The biggest difference between 16 and 17 is features and customizations. 16 still offers many features that haven't made it into 17 yet.

As for the camera I never had any problems with it, but the pictures were just OK if I'm being honest. You would be much better off installing a GCam of some sort. For LOS 16 I linked to the one I always used in this thread and the settings I used.
 

divhandyman

Senior Member
Sep 3, 2010
293
73
Virginia Beach
This has been stable for a long time. Even the unofficial LOS 17 is very stable in my opinion. The biggest difference between 16 and 17 is features and customizations. 16 still offers many features that haven't made it into 17 yet.

As for the camera I never had any problems with it, but the pictures were just OK if I'm being honest. You would be much better off installing a GCam of some sort. For LOS 16 I linked to the one I always used in this thread and the settings I used.

Thanks for the reply, I think I will give it a try.:good:
 

OhioYJ

Senior Member
Feb 25, 2011
1,536
797
Thanks for the reply, I think I will give it a try.:good:

Lineage is always my go to. I don't buy a device that doesn't have Lineage support. I found the post for GCam: Here was my post about GCam. (link) That version only works in LOS 16. There is a different version for LOS 17. So if you try 17, you'll need a different version, let me know.

These are the instructions I've been posting about LOS installation, just note the LOS 16 / 17 stuff. Use the appropriate versions. Only use Android 9 with LOS 16 and only Use Android 10 stuff with LOS 17, don't mix the two. Any questions feel free to ask. The key is just make sure you start with 9.0.17 for LOS 16.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 82
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    • Download the latest build and gapps
    • Boot to recovery
    • Flash the latest build
    • Boot to recovery again
    • Flash gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
     
    Did you--
    wipe:
     restore with titanium backup:
    reboot after having the issue:
     
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
     
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    XDA:DevDB Information
    [ROM][OFFICIAL][fajita][9] LineageOS 16.0, ROM for the OnePlus 6T

    Contributors
    LuK1337, luca020400
    Source Code: https://github.com/LineageOS

    ROM OS Version: Windows 8 Mobile

    Version Information
    Status: Testing

    Created 2019-02-05
    Last Updated 2019-08-25
    14
    when can we expect fingerprint to work?
    (days, weeks, months)?

    Sorry, I can't predict the future.
    9
    @LuK1337 I don't think this has been mentioned so I'm not sure if you are aware of it. However, when using in app payments tied to the biometric (fingerprint) authorization, if the app forces landscape, the FP sensor appears in the wrong location and is not usable. Is there a way to always force portrait mode for the FP sensor?

    Have you thought about trying out using newer builds before reporting issue? ^.^
    iuPrxYK.png


    BTW don't update yet, I'll be uploading new build in like <20 minutes.
    9
    @LuK1337 So far so good. Zero crashes. Zero hiccups. (I've fooled with every setting imaginable including some dev test just, and the mobile ones you mentioned. Default phone and Google phone NP) A small handful of complaints but those will be worked out in due time. Good work so far gents
    @Logix That seemed a bit aggressive. Threats arent the way to go. Everyone assumes their opinion means fckall these days and what better place to share. I don't agree, but its 2019 you can walk ur third leg into the ladies restroom legally
    Following the rules shouldn't be threatening they are provided in the link and at the bottom of the page.
    Nor should be respecting the op or devs who put their time and work in for free.