[ROM][T710/T715][9.x] LineageOS 16.0 - Galaxy Tab S2 Original Android Development

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+ with treble support https://forum.xda-developers.com/showpost.php?p=78708796&postcount=2
- backup everything before install including efs partition
- wipe cache and vendor partitions before install
Install:
- Flash zip in compatible TWRP
- Don't forget about gapps (arm 9.0)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Doesn't work:
RIL
Download:
0207 build
T710: https://drive.google.com/open?id=1VScAyyvr8WcAseGAFVmIM4DPd2-Q1Us6
T715: https://drive.google.com/open?id=1q7oHTyV_JJGG3B56h0Wd_QiUsKn6hVzg
Device sources:
https://github.com/bonuzzz

treble-enabled twrp
t710: https://drive.google.com/open?id=1d0YycDthOxo7IM1b5gZbNI7zCdlu2Cix
t715: https://drive.google.com/open?id=1wrZKDMQcosQRrZGDypIG27Oqv-zL6m2G
known issues:
info on data partition is not accessible

Hi, thank you for the build, awesome! I was going to install LOS 15 but now I'll go directly for this one. I'll tell you how it goes
Sent from my Aquaris M5 using Tapatalk

Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.

Hockron said:
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Click to expand...
Click to collapse
Unfortunately it's not so simple. So no new builds for t810/t815 at least in near future (several months). I focus on t710/t715 only.

as usual gr8 job ma8 considering. We got los15.1 stable finally seeing this beta makes me really happy so, keep up the good work...

This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.

bonuzzz said:
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
Click to expand...
Click to collapse
Its very sad for everyone that you abandoned the rom, but I understand what not having the time and the energy means. Thank you very much for the build. In any case I installed as I said before.
I haven't tested it much but for the time being its running pretty smooth. I installed some apps and no crashes so far. Just an error message at boot saying something happened, after closing it everything OK.
I add some screenshots here.
Ill keep posting issues if I find any. Do you think I could compile your sources in my computer?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-T710 using Tapatalk

what to do when you are sick and staying at home? answer is simple:
new lineage16 builds are uploaded.
all hw stuff has been brought up except ril on t175, so no mobile network support yet. everything else should work.
links are in first post.

How much work should it be done to port this onto T810? And do you know anybody is doing it?

frankieboy1233 said:
How much work should it be done to port this onto T810? And do you know anybody is doing it?
Click to expand...
Click to collapse
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.

T815 plzz. I have no knowledge about porting roms, but if by any way I can help u in porting this to T815 plzz let me know...

sweet, i saw your trebel twrp in the other forum, freaking fntastic

#1. Loaded trwp and ROM only no root
Excellent power 97 percent remain after 13 hours
No 5gz WiFi. But because I had nothing else loaded I couldn't see the nvram_net.txt settings.
So I tried to load pico and lineageos add-on su, and had several boot up and setup issues with the play services kept crashing. After bypassing lots of stuff, gave up and reloaded, I was able to see the root permissions in the developer settings, but lineageOS extras shows only arm 15.1 no 16 for root. Thought that was an issue. Silly me I didn't do a logcat. Before I did #2
#2nd try wipe , load, pico and magisk 17 . no magisk 17 in apps.
Did a bypass load apps to get to desktop. Had a couple " this device has errors, please contact manufacturer "
Play store was able to install apps, but I had no access to my paid apps. See #1 I wanted to fix my 5gz WiFi files. And I use es file explorer pro, but since I didn't have root... Well.
Play store recovered my programs am going to try magisk 18 . BRB
Looks nice, a couple of google play store bugs, an actuall desktop black out.
In conclusion, awesome ! Work !
Will fiddle some more. couldn't get a logcat

Downloaded all my gapps, and I found an unofficial root for lineageos 16 in another forum.
Trying again. Cheers
https://androidfilehost.com/?fid=11410963190603875495

issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store

bonuzzz said:
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
Click to expand...
Click to collapse
i have an 815 to test as well
---------- Post added at 05:35 AM ---------- Previous post was at 05:17 AM ----------
bonuzzz said:
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
Click to expand...
Click to collapse
Same here.
I got 5gz to work . I changed
Code:
ccode=US
regrev=69
Based on several posts over the years, I researched what regrev is in related to the ccode
It relates to what frequencies and I believe power outputs for different countries legal free and open radio frequencies.
The clues are in the driver for the wireless device source code.
Here is a broadcom driver for the 3.10 kernel
https://android.googlesource.com/ke...drivers/net/wireless/bcmdhd/dhd_custom_gpio.c
In there is a small database that should be consulted when you boot up your device and your country code should be selected when the driver is accessed
This has never worked properly for any lineageos based ROM.
Also most stock ROMs do not have this in their correctly.
All the files in /system/vendor/etc/wifi that have nvram in their name ( total 6 files ) need updated manually with an editor with root access.
As soon as I enter codes and reboot, I see all the 5 gz and many other networks that normally are too far away.
Kind of a chore to do this on every reloaded device, but that's what it takes.

Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?

samw52000 said:
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
Click to expand...
Click to collapse
Same here I cant flash Gapps with out it sticking on Samsung's boot logo

@samw52000 @legojoe8 read the first post carefully, in particular about twrp

Related

[ROM][8.1][UNOFFICIAL][MP260&TP260] LineageOS 15.1 for LG K20 Plus

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[COLOR="red"]Your warranty is now void.[/COLOR]
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you 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 me for messing up your device, I will laugh at you.
Learn to Google.
WARNING: THIS ROM IS NOT FOR DAILY USAGE, IT'S ONLY A ALPHA AND A FEW THINGS ARE BROKEN. ALSO, IT'S POSSIBLE THAT YOU WON'T BE ABLE TO RESTORE A NANDROID BACKUP AFTER FLASH THIS ROM. FLASH AT OWN RISK!​
/* What’s working */
Audio
Bootanimation
Brightness Level
Bluetooth
Microphone
MTP
Wi-Fi
Sensors
SD Card
Screen Casting
Camera/Camcorder
Flashlight
Wi-Fi hotspot
/* What’s not working */
The Fingerprint sensor is not yet implemented into my builds
APN needs set to IPv4/IPv6 to support full data capabilities for T-Mobile/MetroPCS
VoLTE isn't working
Wifi MAC address is not properly set
Double Tap 2 Wake on devices with a Synaptics display (which is about half of the LG K20 Plus devices)
Formatting /data as F2FS limits the partition to only 4GB so definitely avoid doing that for now
Please let me know if there are issues so i can update this list and work towards making it shorter than it already is.
Install Instructions​1. Download ROM from the link below.
(This ROM is a 64bit ROM please install the 64bit PBRP from the Official PBRP thread unless you have an old 64bit capable recovery)
2. Wipe dalvik/cache/data/factory reset. (also delete the /Android folder from your external SD card, this can be done in PBRP under advanced/file manager)
3. Flash the rom in recovery.
4. Flash OpenGApps in recovery. (Make sure to choose 8.1 ARM64)
5. Reboot device.
Error 255 when flashing 64bit roms is because you are running 32bit twrp. Try PBRP in the Official PBRP thread
To fix fp enrollment on my builds or stock will require you to either delete the enrolled fingerprint(s) before clean install or switching to/from stock, alternatively you can root the device, use a root file explorer to navigate to the /persist-lg/ partition and delete the goodix folder. (FP is currently not implemented into my Oreo builds and will take time to shim to work, I however will be keeping this bit here for those who decide to revert back to stock or to my Nougat builds)​
Downloads
DOWNLOAD​
If you are happy with my work, please donate to help me keep this project going.
https://www.paypal.me/travisholt92
Thank You! :victory:​
XDA:DevDB Information
LineageOS 15.1, ROM for the LG K20 Plus
Contributors
Travisholt92,
Deadman96385 (helped to provide bandwidth and the Q6 Stock Oreo kernel which my Oreo+ builds and this project utilize),
33bca (For his work on the Redmi 4A/5A, my device/vendor trees for Oreo/Pie are forks of his trees from [url]https://github.com/redmidevs trimmed/reworked to best support our LG devices, without his work this project would likely have taken ALOT longer with alot more bugs) [/URL]
Source Code: [url]https://github.com/LG-SD4XX/android_kernel_lge_sd4xx-common/[/URL]
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.18.120
Based On: LineageOS
Version Information
Status: Beta
Created 2019-02-05
Last Updated 2019-01-31
Changelogs:
2-6-2019
Fixed reboot recovery and 2D gaming issues
Travis, Try this Apn_Conf I had way more stable data and ip6
https://www.dropbox.com/s/3xramb2cbkq7gas/apns-conf.xml?dl=0
New build is up with reboot to recovery and 2D gaming fixed
Aw man.
Good to see the official thread take off!
@Travisholt92 unless I'm doing something wrong when trying to play a couple games (Idle Hero's being one) it won't allow me to play Via data it won't connect unless I'm on Wi-Fi? I can get a log but just wanted to let you know also if anyone wants what seems to help data a bit including faster switches from 3g to lte after calls try flashing this
https://www.dropbox.com/s/rak3v7mc6it4vqm/Apn_and_More.zip?dl=0
Also cleaned up build.prop and added some tweaks to it
---------- Post added at 05:51 AM ---------- Previous post was at 05:44 AM ----------
Also posted in your 7.1.2 thread that Magisk 16.0 doesn't freeze up
hawknest said:
@Travisholt92 unless I'm doing something wrong when trying to play a couple games (Idle Hero's being one) it won't allow me to play Via data it won't connect unless I'm on Wi-Fi? I can get a log but just wanted to let you know also if anyone wants what seems to help data a bit including faster switches from 3g to lte after calls try flashing this
https://www.dropbox.com/s/rak3v7mc6it4vqm/Apn_and_More.zip?dl=0
Also cleaned up build.prop and added some tweaks to it
---------- Post added at 05:51 AM ---------- Previous post was at 05:44 AM ----------
Also posted in your 7.1.2 thread that Magisk 16.0 doesn't freeze up
Click to expand...
Click to collapse
Yeah that data issue is related to ipv6 not allowing full network connectivity. Change that to ipv4/ipv6 in your APN and you'll be golden. It's something kernel related preventing full IPv6 connectivity. I'll check out your build.prop tweaks though. I plan to change the built-in APNs to address that issue until I can get that issue resolved. I probably won't work on debugging that until Pie since its not quite a high priority issue.
I installed the mentioned game just to make sure that was the issue. Loaded up just fine over LTE with ipv4 enabled
Dirty flashing from a previous Oreo build to 2/7 will likely result in a bootloop if you had magisk installed. You will need to reflash magisk and possibly gapps to resolve this issue. Its because I changed the filesystem type for certain partitions from ext4 to f2fs for a slight performance boost.
Travisholt92 said:
Dirty flashing from a previous Oreo build to 2/7 will likely result in a bootloop if you had magisk installed. You will need to reflash magisk and possibly gapps to resolve this issue. Its because I changed the filesystem type for certain partitions from ext4 to f2fs for a slight performance boost.
Click to expand...
Click to collapse
Lol, sure after I find out the hard way
hawknest said:
Lol, sure after I find out the hard way
Click to expand...
Click to collapse
Sorry about that lol
I'm going to revert those changes since they were personal preference but the change won't affect users that had issues installing the most recent build.
I am not sure what's up, I've flashed 2/9 a bunch and just bootlooping.. Clean install and fresh magisk flash
EDIT: Tried a few more times and no go.. I'll wait for the revert
I'm starting to think people don't know this thread exists yet
hawknest said:
I am not sure what's up, I've flashed 2/9 a bunch and just bootlooping.. Clean install and fresh magisk flash
EDIT: Tried a few more times and no go.. I'll wait for the revert
Click to expand...
Click to collapse
Revert build is up under the same name as yesterdays build with yesterdays build renamed to the proper date. It will work with ext4 and f2fs now. Its likely your issue was from cache being formatted as EXT4 which yesterdays build didn't support, today's does.
hawknest said:
I'm starting to think people don't know this thread exists yet
Click to expand...
Click to collapse
Me too lol. Once I get a new screen I'll get a YouTube video up with a side by side comparison between lineage 15.1 and stock. Should make for a very enlightening video.
Travisholt92 said:
Sorry about that lol
I'm going to revert those changes since they were personal preference but the change won't affect users that had issues installing the most recent build.
Click to expand...
Click to collapse
imma slap it on an give it a whirl ... uhhh...any way you could mix in magisk like with RR .. i can flash a backup...maybe
just wondering? i can take no for an answer
and i canT find the LIKE button.....serious
i've looked over the OP 10+ times...
Cyconumnum said:
imma slap it on an give it a whirl ... uhhh...any way you could mix in magisk like with RR .. i can flash a backup...maybe
just wondering? i can take no for an answer
and i canT find the LIKE button.....serious
i've looked over the OP 10+ times...
Click to expand...
Click to collapse
I can but won't for users who for some reason prefer SU, but magisk installer is baked into PBRP so close enough right? Lol also a new build is being uploaded now with overall performance improvements. Maybe I'm just crazy but even networking seems faster on 2/08. Should be up in about an hour. I'm off to bed now. Enjoy the super fluid 2/8 build.
Its a thumbs up lol
Going to need help testing something that everyone wants ??
hawknest said:
Going to need help testing something that everyone wants ??
Click to expand...
Click to collapse
Obviously I'm up for it. Lol.
reboot to recovery :good:
just flashed the 2/8 build 20-30 minutes ago, all is great so far.

[ROM] [sailfish] [9] [LOS-based] **crDroid**OMS**v5.8

crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello
I have created this rom using the Lineage sources and a fix from the creator of the rom of this page: http://customromz.proboards.com/thread/11/crdroidandroid-9-marlin-v5-zip?page=1&scrollTo=16. I don't have too much knowledge in how the rom is developed so perhaps I won't be able to solve all your questions.
Please let me know if you have any issue.
Regards
SourceTree
LineageOS
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your google pixel, or coming from another ROM:
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Install stock rom
2) Copy crDroid zip, gapps zip and twrp zip to your device
3) Boot into Recovery
4) Wipe cache, system, & data (or just cache & system for a dirty flash).
5) Flash ROM
6) Reboot into recovery
7) Flash gapps
8) Boot up
9) when the setup wizard starts execute the following command to allow it to connect to wifi
adb shell pm grant com.google.android.apps.pixelmigrate android.permission.WRITE_SECURE_SETTINGS
10) Open the contacts and phone apps and accept the permissions requests
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
you tell me...
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Joe pacino
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE​
I might take a look at this, what have you done since the last build in the main thread?
GeTex said:
I might take a look at this, what have you done since the last build in the main thread?
Click to expand...
Click to collapse
Hello
Thanks for your answer. What your are interested in is the process I follow to compile the rom ?. I can post the script I use, that is one I have created from the crdroid sources: https://github.com/crdroidandroid/crdroid_build.
Regards
Why not post this in the Pixel Development forum? Would gain more traction there.
PapaSmurf6768 said:
Why not post this in the Pixel Development forum? Would gain more traction there.
Click to expand...
Click to collapse
Hello
I am not allowed yet to post in the Pixel Development forum because I haven't made enough posts yet.
Regards
jontxo said:
Hello
I am not allowed yet to post in the Pixel Development forum because I haven't made enough posts yet.
Regards
Click to expand...
Click to collapse
Oh
Well thanks for your work anyway, has this been running well for you? Might be able to try it, the old crDroid was my favorite ROM.
PapaSmurf6768 said:
Oh
Well thanks for your work anyway, has this been running well for you? Might be able to try it, the old crDroid was my favorite ROM.
Click to expand...
Click to collapse
It is the rom that I use in my phone in a daily basis and I haven't found any issue yet.
Are anyone try this rom? How was the performance and battery life? Any problems?
SoKa1993 said:
Are anyone try this rom? How was the performance and battery life? Any problems?
Click to expand...
Click to collapse
I flashed it, all good so far.
Couple things to note, the Stock OpenGapps package said it was too big for system storage, had to move to Mini package.
When going through setup, the adb command given wasn't working until I went through setup a little bit, then came back to the beginning. Not sure exactly how to fix it but it worked eventually, and WiFi connected.
Will put it through its paces over the next couple days, thanks for the build!
PapaSmurf6768 said:
I flashed it, all good so far.
Couple things to note, the Stock OpenGapps package said it was too big for system storage, had to move to Mini package.
When going through setup, the adb command given wasn't working until I went through setup a little bit, then came back to the beginning. Not sure exactly how to fix it but it worked eventually, and WiFi connected.
Will put it through its paces over the next couple days, thanks for the build!
Click to expand...
Click to collapse
You are welcome. And thanks for trying it.
Regards
jontxo said:
You are welcome. And thanks for trying it.
Regards
Click to expand...
Click to collapse
Suitable for daily driver? How frequent will it to be update?
SoKa1993 said:
Suitable for daily driver? How frequent will it to be update?
Click to expand...
Click to collapse
I use it as a daily driver for my phone. I will update it whenever a new crdroid version is out.
Regards
jontxo said:
I use it as a daily driver for my phone. I will update it whenever a new crdroid version is out.
Regards
Click to expand...
Click to collapse
Thanks. Will try it tonight and give feedback to you.
Good features, like the "past" features. Your kernel has very good sleep mode, and speed stepping. Overnight battery life looking good. I haven't tried cell radio yet, this is the second pixel I use for testing first. I will try a couple of ways to get Google photos app to work Like Pie, before I commit more. Photos device file backups not working correctly, but that might be my device to device transfer process to move master work data to a newly flashed build. THANKS for your time and efforts.
Edit- yep had device transfer problem. Complete wipe / reinstall apps. Photos fine again.
kkjb said:
Good features, like the "past" features. Your kernel has very good sleep mode, and speed stepping. Overnight battery life looking good. I haven't tried cell radio yet, this is the second pixel I use for testing first. I will try a couple of ways to get Google photos app to work Like Pie, before I commit more. Photos device file backups not working correctly, but that might be my device to device transfer process to move master work data to a newly flashed build. THANKS for your time and efforts.
Edit- yep had device transfer problem. Complete wipe / reinstall apps. Photos fine again.
Click to expand...
Click to collapse
I am glad everything is OK.
Everything is ok but the charging speed is quite slow. Max i got just 5.0W. Is it because the rom or the kernel i used? Currently using latest franco kernel. But on others rom it works fine. Other than that, i loved it. Thanks
SoKa1993 said:
Everything is ok but the charging speed is quite slow. Max i got just 5.0W. Is it because the rom or the kernel i used? Currently using latest franco kernel. But on others rom it works fine. Other than that, i loved it. Thanks
Click to expand...
Click to collapse
How have you managed to flash franco kernel. I have this error: new image larger than host partition. Aborting...
Regards
After a few days on this I can say this is easily the best Pie ROM I've put on my phone. Features are great and no problems to report in my day to day use.
Couple notes I had; I had to flash the Mini Gapps since the Stock package said it was too large for the partition. After booting, the trick to get WiFi to work during setup didn't work immediately but did work after clicking around a bit. Then Photos was crashing on start so I deleted it as a system app and just installed it from Google Play. That works fine, and I haven't had any other apps do this.
Thanks again OP, will be on this one for a while.
jontxo said:
How have you managed to flash franco kernel. I have this error: new image larger than host partition. Aborting...
Regards
Click to expand...
Click to collapse
I just flash it and it work like usual. Maybe something wrong when u flash the rom file. Did u clean flash it or dirty? Mine clean flash. After flashing the rom, i boot it to system. Then install gapps, magisk. Boot it again. Then franco. Work like a charm. Btw, this rom is smoother than other roms. Love the extra setting on this rom. Thanks for ur work.
New version of crdroid- 5.8
Hello
I have uploaded a new version of the room, the 5.8.
https://androidfilehost.com/user/?w=settings-dev-files&flid=298676
Greetings

[OFFICIAL] LineageOS 18.1 for the Moto Z2 Force

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Z2 Force
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto Z2 Force.
Join our Moto Z2 Force Discord!
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
nash
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in LineageOS, as the normal proximity sensor works fine.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Code:
Technical details on our Treble implementation:
Treble is enabled with VNDK30, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8998
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
PrivyetCyka said:
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
Click to expand...
Click to collapse
Am the developer - and it is building on official servers tonight, check back in 24 hours.
npjohnson said:
Am the developer - and it is building on official servers tonight, check back in 24 hours.
Click to expand...
Click to collapse
Oh awesome. Thank you for the hard work ! Glad to see roms still being made for this phone
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
I fixed it! Please make sure to flash lineage from your computer when you are updating to a new version of lineage... NP Johnson makes this clear in his instructions. Unfortunately it has been awhile since I have flashed a rom onto a phone and I forgot that step...
here is how I did it
fastboot flash boot_b recovery-nash.img
factory reset your phone
flash the lineage zip from your computer using adb sideload lineage 18.1 nightly
Very good upgrade, thanks for the hard work and making this real
Thank you for not letting our device die
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
The clock app is not working and I think usb tethering is not working.
Vibration is not working
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Big_Brother_Is_Watching said:
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
Click to expand...
Click to collapse
Flashing from recovery is fine - so long as you can see the zip, it's no problem. Not sure where your problem hit.
But thank you for ultimately flowing the guide and using your PC, it just raised and more seamless.
vivebatu said:
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
Click to expand...
Click to collapse
Yup! And will from here on out
Big_Brother_Is_Watching said:
The clock app is not working and I think usb tethering is not working.
Click to expand...
Click to collapse
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
Manuelmartad said:
Vibration is not working
Click to expand...
Click to collapse
It works, your motor may have died.
wyldwilly said:
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Click to expand...
Click to collapse
dlopen, HDR, and save to SD: all expected and WIP. Working on them
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
wyldwilly said:
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
Click to expand...
Click to collapse
That's efficiency mode and proper battery mod support for ya! Haha.
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
no, its not working i tried it on;stock and it works well
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
idelgador said:
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
Click to expand...
Click to collapse
sounds like a persist issue - did you ever flash pie firmware?
npjohnson said:
sounds like a persist issue - did you ever flash pie firmware?
Click to expand...
Click to collapse
Is that related to a previous flash of pie? :O

[OFFICIAL] LineageOS 18.1 for the Google Pixel 3a XL

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Going to try it now.
Thank you!
npjohnson said:
​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?
ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.
Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team
What is the official way to obtain root access? or is there one any more?
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed
adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.
First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!
Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.
Haven't been able to use twrp since Android 9 far as i know
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Nevermind, user error.
ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.

[11][OFFICIAL] CarbonROM | cr-9.0 [fajita]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​
FINALLY! YES! WOOHOO!
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.
When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.
So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever
Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.
Google Camera, just google up gcam ports
only reason fr nt using Carbon is there is no
face unlock
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website
I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?

Categories

Resources