Database Info

[ROM][DEVELOPMENT] Unofficial LineageOS 14.1 (Updated 7/10)

{
"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"
}
What it is
A custom ROM built from LineageOS sources.
Disclaimer
Code:
/*
* Your warranty is now void.
*
* We are 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.
*
*/
Prerequisites
- Xperia Z3 Compact on latest .291 firmware (Any variant)
- Unlocked Bootloader ONLY
- TWRP
Download
ROM:
https://androidfilehost.com/?w=files&flid=222053&sort_by=date&sort_dir=DESC
Recovery:
https://www.androidfilehost.com/?fid=961840155545571844
Changelog
Code:
7/10/17
- October security patches
- Test netmgrd from Bacon
21/8/17
- Kernel upstreamed 3.4.0 -> 3.4.113
- Updated sdcardfs
- Upstream LineageOS changes
8/8/17
- Merge android-7.1.2_r29 with August security patch (excl. kernel patches)
- Fix mixer_paths (stuck on boot issue)
5/8/17
- 3am reboot fixed thanks to Diewi
- Sync with whatever changed in LineageOS
21/7/17
- Moved to stock RIL blobs
- Fix audioserver crashes
- Disabled fluence to workaround mic quality issue
- Fix camera not working on first boot
- Merge 70+ Security patches in kernel
- Fix bluetooth calls for some users
7/7/17
- Merged Android 7.1.2 r24
- July Security patches
- Disabled NFC-F HCE (May fix terminal payments)
- Updated widevine blobs from kipper (may help with DRM videos)
- Return to MPDecision hotplugging and interactive tunings inline with other msm8974 devices
- Return to QCOM PowerHAL
- Kernel built with -O2 flag
- Revert round icon support (on the road to official)
23/6/17
- ambient display support (can disable in settings)
- tuned cpu hotplugging (won't wildly jump during idle anymore)
- cleaned up GPS/location related settings
- charging LED for <90% now actually orange
- aptX codec support
- Assertive display enabled
- changes to USB current control
- call microphone quality improvements
7/6/17
- More aggressive CPU tunings
- Bluetooth calls fixed??
- June security patches
- Merged Android 7.1.2_r17
25/5/17
- Misc Kernel security patches merged
- Back to CPUQuiet, with powerHAL by Kholk
- flags for Acoustic Echo Cancellation and Noise Suppression for voice pre processing
- Audio cleanups
12/5/17
- May Security Patch
- Android 7.1.2_r8 merged
- NFC changes (maybe better)
- Audio "improvements" (blame xkeita)
- Thermal settings closer to stock
21/4/17
- Adaptive brightness tuning (thanks to [user=4550727]@xkeita[/user])
- USB OTG path fixed
- Change back to MPDecision hotplugging temporarily
- Android 7.1.2_r2 merged
- April Security Patch
- Charging while phone turned off now turns screen off
13/4/17
- Change to CPUQuiet hotplugging
- MHL drivers included
- Time services added for RTC things
- Vibration intensity interface works now
- WIFI MAC Address randomisation issue fixed
- SELinux set to enforcing
- Switch to sdcardfs, superseding fuse
- WIFI hotspot possibly fixed
- 23/3/17
- Initial release
Sources
https://github.com/LineageOS/android_device_sony_shinano-common
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_kernel_sony_msm8974
Credits
Main developers
@nailyk
@rcstar6696
@xkeita
External contributors
@derf elot
Testers
@tomgus1
@gr8st
@mcgi5sr2
@doriandiaconu
@Robot76
@panzerox123
Benjamin Pham
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the Sony Xperia Z3 Compact
Contributors
tomascus, nailyk, rcstar6696, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2017-03-22
Last Updated 2017-10-08

Installation guide for new users:
Things you need:
- Stock firmware (if you're not on .291): https://forum.xda-developers.com/showpost.php?p=56046548&postcount=2
- TWRP Recovery image: Above in OP, downloads area
- The ROM: Above in OP, downloads area
Make sure you're on the latest stock firmware, version 23.5.A.1.291
If you're not:
1. Download the firmware from the above link or somewhere else, it doesn't matter which region you pick
2. Flash the FTF file with Flashtool, latest version obtainable here: http://www.flashtool.net/index.php
3. Power off the phone after completion
Flashing TWRP Recovery:
1. Download from above
2. Enter fastboot mode - while the phone is off, hold the vol up button and insert your USB cable (connected to PC), blue led light should appear
3. Enter the following command: fastboot flash FOTAKernel twrp_z3c_2017-04-26.img (or whatever the file is called)
Flashing the ROM:
1. To enter recovery, hold the power and vol-down keys while the phone is powered off
2. Wipe system, data, cache, dalvik cache
3. Select the ROM zip and flash away
4. OPTIONAL: Flash any extras, Gapps (open gapps work well) and root from here: https://download.lineageos.org/extras use addonsu-arm-signed.zip for ROOT, not SuperSU
5. Reboot
If coming from previous version:
What I recommend is full wipe. No support for those who dirty flash.
- Backup apps with Titanium Backup or other alternatives.
- Backup SMS/call log with SMS backup app.
Known Issues
* Bluetooth connection issues
* Mobile data reconnection issues
* Encryption and adoptable storage leads to bootloops
How to report bugs:
- Attach any relevent logs: dmesg or logcat (clear logs with "adb logcat -c" first, then reproduce issue)
- For random reboots, provide a last_kmsg
- Screenshots or written explanations of how to reproduce

Snap Camera Mod
Simply exposures (pun not intended) Sony variables for the Snap camera app (default one).
- Capture prio modes (ISO/Shutter speed/Manual/Auto)
- More ISO values selectable
- Sony metering modes
- Sony video stabilisation control
Download:
https://androidfilehost.com/?fid=673791459329051895
Instructions:
1. Flash ZIP in TWRP
2. Clear data for Camera

First
Thoroughly tested, everything works. Great Job on this one
link removed

Oh yeah I'm downloading right now to give it a try later.... If i succeed and find the time i'll report
For now A REAL BIG THX
Rhonin

One more ovation for @nailyk and @tomascus

@nailyk @tomascus great work!
Now, for those of you getting the Error7 in TWRP, delete these lines from META-INF>com>google>android>updater-script
Code:
(!less_than_int(1490124938, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Mar 21 19:35:38 UTC 2017) over newer build (" + getprop("ro.build.date") + ").");
assert(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" || getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" || getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" || getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || abort("E3004: This package is for device: D5803,D5833,z3c,aries; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Sony/D5803/D5833:6.0.1/23.5.A.1.291/2769308465:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
If anyone asks about how to fix error 7... I will personally send hand them over to cannibals XD

This version uses stock blobs ?

yes uses stock blobs

Great work guys!

So no working version yet? The one mcgi5sr2 posted couldn't go through setup after booting, didn't respond to anything other than power menu.

Pisiont said:
So no working version yet? The one mcgi5sr2 posted couldn't go through setup after booting, didn't respond to anything other than power menu.
Click to expand...
Click to collapse
It is an issue when you doesn't have gapps. Reboot should work.

nailyk said:
It is an issue when you doesn't have gapps. Reboot should work.
Click to expand...
Click to collapse
Reboot doesn't help, but I'll try with gapps. Hope that works

Thank you,mcgi5sr2, nailyk Yes, it really takes a very long time to install the firmware. Camera does not work. Black screen, the first launch of the camera with the button, now without a button on the display, very sorry.
P.S. Gapps is not set

Guys, just to clear out any misconceptions, the ROM is fully working and stable for daily use . The build was taken down because of a model specific issue. A new fixed build will be out soon. (No I am not developing it. Just testing the builds)

panzerox123 said:
Guys, just to clear out any misconceptions, the ROM is fully working and stable for daily use . The build was taken down because of a model specific issue. A new fixed build will be out soon. (No I am not developing it. Just testing the builds)
Click to expand...
Click to collapse
Is that model specific issue a not working camera? Expect that seems stable, some lineageos settings crash also but that's not a big deal.

Pisiont said:
Is that model specific issue a not working camera? Expect that seems stable, some lineageos settings crash also but that's not a big deal.
Click to expand...
Click to collapse
Yes. My device has a front camera that is used in Leo, that's why camera apps crashed for me

panzerox123 said:
Yes. My device has a front camera that is used in Leo, that's why camera apps crashed for me
Click to expand...
Click to collapse
leo has different camera than our compact? don't really understand what you mean

Pisiont said:
leo has different camera than our compact? don't really understand what you mean
Click to expand...
Click to collapse
In a nutshell... There are 2 difference front cameras... There was only one driver in the build

panzerox123 said:
In a nutshell... There are 2 difference front cameras... There was only one driver in the build
Click to expand...
Click to collapse
I am a little confused: Is camera working or not?

[ROM][Android 10][Android 11]Meizu E3 LineageOS 17.1/18.1 ROM Porting (20210418)

{
"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"
}
Hi there,
I prepared an alpha version of LineageOS 17.1/18.1 for Meizu E3 for your taste about it. Now it so more useable as dev-phone for outdoor YouTube viewing. Do play with it your own risk. I am not responsible any liability, nor any technical support too. So please think twice before taking action. AND be safe to backup ALL partitions before and action taken.
You can visit another thread of Meizu E3 unlock bootloader tutorial from your author, to unlock Meizu E3 without any external tool.
Instruction:
(0) to make it align with latest flyme v8000 fw, update system to v8000 is highly recommended. (20200926)
(1) get the phone unlocked bootloader as above mentioned.
(2)download below mentioned fw (boot.img.signed, system.img, vendor.img, recovery.img) in to a folder like "E3_LOS17.1", unzip and get "vendor_image.emmc.win", "system_image.emmc.win" and "boot.img.signed", rename them as boot.img, system.img, recovery.img and vendor.img
(3)hold power+vol_down and do "fastboot.exe boot recovery.img"
(4)in twrp, backup all partition to /sdcard, aka, "/sdcard/system.img", "/sdcard/persist.img"
(5)in host PC backup from phone and upload all above downloaded and unzip rom.img to phone, procedure like open cmd.exe, "mkdir E3", "cd E3/", "adb.exe pull /sdcard .", "adb.exe push E3_LOS17.1 /sdcard"
(6) twrp install, choose install img, select /sdcard/E3_LOS17.1/system.img, system partition, go
(7) twrp install, choose install img, select /sdcard/E3_LOS17.1/vendor.img, vendor partition, go
(8) twrp wipe, choose data partition, go (your data partition got WIPED, all data are LOST)
(9) wait above finish, go back to PC terminal, cmd.exe, issue "adb.exe reboot-bootloader", then "fastboot.exe boot boot.img"
(10) wait for LOS17.1 boots up
optional steps
(2a) you can choose to phh's quack build instead of jasmine_sprout system image as well. download it from phh's github release channel, unpack the zip, use simg->img tool to get regenerated system.ext2.img; check with linux "file" util and get
[email protected]:/mnt/jasmine_vendor# file /mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img
/mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img: Linux rev 1.0 ext2 filesystem data, UUID=05050abd-8baa-4dd4-905c-903071f9ac68, volume name "system" (extents) (large files) (huge files)
Click to expand...
Click to collapse
Note:
(1)Please sure to DO backup all the partitions
(2)Please sure DO NOT to flash boot.img to boot partition, every time use fastboot to boot into LOS17.1 thus can easily restore to flyme8 rom
(3)please sure when revert back flyme8, please DO use your own twrp backup to restore all partition is your first choice. Second choise is by flyme8's recovery from recovery partition, or at least the flyme8 recovery downloaded below. DO NOT use TWRP restore the flyme rom directly, and this can avoid many issues; otherwise you are compulsively to reflash flyme once again at least and all your data partition backup become useless; and if you force restore data partition, it wont help, due to internal hw keystore and crypto salt changes. so step (5) "adb.exe pull /sdcard/ ." is essential.
(4)use twrp recovery to restore data partition might not work at all. so once again, backup by using "adb.exe pull /sdcard ." is important. As said, some partition might get changed by bootloader and internal fw, so hw crypto and salt, keystore partition might get changed too after first boot LOS17.1; and you cant backup these partition at twrp screen operation. and even through if you are expert enough, restoring those partitions in adb shell also might not work at all due to same reasoning.
(5)using "adb.exe pull /sdcard ." is important! this is important so as i said 3 times.
(6)backup all partition by "adb shell" if possible. TWRP only list some of usual partition, and some rarely used partition are not listed. Like i suffered from persist partition wiped out and cant restore without a copy. so do a "dd if=/dev/block/bootdevice/by-name/XXX of=/sdcard/XXX" is a good idea.
(7)I had tried my best to make the all mount as "r/o" as possible, but i CANT guarantee all other partition are safe. So best is do as note(6) said.
Release Alpha 13
==================
Latest alpha release on LineageOS 18.1, camera is not working, check below for detail:
Release Alpha 13 · 99degree/android_vendor_meizu_m851q
This release (Alpha 13) is an alpha release that based on brand new Nokia PL2 LineageOS 18.1 release. Detail refer to below: https://lineageos.org/Changelog-25/ This release have an issue about cam...
github.com
Release Beta 2
==================
Latest stable ROM on LineageOS 17.1
Release Beta 2 (20210221) · 99degree/android_vendor_meizu_m851q
This release aimed to get entire system updated to Feb-05 Security bulletin. Changelog: Update to LineageOS Amber 20210214 Known issue: LineageOS clean (wipe data in TWRP) and first time startup wi...
github.com
Older release:
Release note 20210124
==================
Update dts and libmmcamera module. Camera should be alright, actuator is still in progress.
download release 20210126
Release note 20201214
==================
Update to CAF LA.UM.8.2.r2-03400-sdm660.0
Based on LineageOS Nokia PL2 Dragon build 20201208
This is no longer pure CAF due to adreno older fw logic fail.
Selinux enforced now on
Release note 20201011
==================
Update to CAF LA.UM.8.2.r2-02700-sdm660.0
LineageOS Amber 20201011 release, kernel is no longer pure rely on CAF anymore.
It is due to a adreno fw checking logic fail on older fw.
Release note 20200813
==================
Update to CAF LA.UM.8.2.r2-02500-sdm660.0
LineageOS Amber 20200809 release
Release note 20200705
==================
Some sensors are available.
external speaker (TAS2560 SmartAmp) functioning.
Release note 20200701
==================
(1)Special release! Voice-out-loud for social injustice!
(2)Mobile feature enablement
https://github.com/99degree/LineageOS/releases/tag/20200701
Release note 20200613
==================
First version with earphone sound playing. So YouTube is more than possible! This version shifts to official LineageOS.org Yandex Amber build
https://mirrorbits.lineageos.org/full/Amber/20200607/lineage-17.1-20200607-nightly-Amber-signed.zip
Release note 20200303
==================
Workaround the wifi problem, now wifi is working. boot.img.clear is updated.
Release note 20200223
==================
This is a ported version of LineageOS 17.1 based on this thread so you can download the original version of the build over there. In case of preference in phh's treble quack release, it seemed system.img is working well too.
The solo modification in vendor.img included:
(A) fstab.qcom to disable persist partition mount by "r/o", so no longer as "r/w" mode in order to protect it against lost wifi firmware, lost signal, mac address etc.
(B) replace all file lived in /vendor/firmware/* with flyme8's
The modification in system.img:
NIL
Things verified to work:
LCD PANEL
TOUCH PANEL
BLUETOOTH
USB
CHARGING
WIFI
vibration
earphone w/button
mobile feature
speaker and incoming ringing
GNSS
sensors (luminous, proximate, compass, magnet)
selinux-enforced
front camera
back imx362 camera
back imx350 camera(not tested)
Things not working:
those not listed above is considered not working
ROM download:
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210418 for LOS18.1
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210221 for beta 2
release 20210126
release 20201214
https://github.com/99degree/LineageOS/releases/tag/20201011
https://github.com/99degree/LineageOS/releases/tag/20200813 for boot.img and recovery.img
https://github.com/99degree/LineageOS/releases/tag/20200705 system and vendor image
https://github.com/99degree/LineageOS/releases/tag/20200701
https://github.com/99degree/LineageOS/releases/tag/20200613
https://github.com/99degree/LineageOS/releases/tag/20200223
https://github.com/99degree/LineageOS/releases/tag/20200303 for boot.img.clear
Repositories:
https://github.com/99degree/
kernel https://github.com/99degree/android_kernel_meizu_m851q
vendor & release https://github.com/99degree/android_vendor_meizu_m851q
So if you wanted to cook it yourself, please find necessary file with you. All needed files are hosted either in GitHub and LineageOS official Amber/PL2 build),
Please consider to show your support by donation or even YouTube clicks. Last and most importantly, happy ROM flashing and stay away from corona-virus outbreak!
Regards,
99degree

Can you public source code of kernel with device driver? Thank mate

thinhx2 said:
Can you public source code of kernel with device driver? Thank mate
Click to expand...
Click to collapse
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.

99degree said:
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.
Click to expand...
Click to collapse
Nice sir

99degree said:
...
kernel https://github.com/99degree/android_kernel_meizu_m851q
...
Regards,
99degree
Click to expand...
Click to collapse
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.

Spencer_D said:
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.
Click to expand...
Click to collapse
No! Not the way you through. I managed to clone kernel from CAF and search for hardware info. By app "device info hw", google and find some public available driver (basically touch driver and sound driver), add them to CAF tree then analysis the device tree dtb->dts difference. Move them to new dtsi and compile it with kernel as a whole. Then make use of LineageOS Yandex Amber ROM, modify and make it boots into LineageOS, that's it.
So best wish your development on SantinK1.

[Treble][GSI] Ubuntu touch for Oneplus 3/3T

{
"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:
/*
* Your warranty is now void.
*
* 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.
*/
What is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
This operating system is developed and maintained by UBports: An international community of passionate volunteers.
This means Ubuntu Touch is 100% community driven and independent.
What is Halium?
Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.
How it is a GSI?
First of all, I should mention ubports GSI definition is different from android, but both are generic.
ubports root file system was always generic and works for most cases, but devs were porting halium system image to add device-specific (HALs and configs) support to ubports Android container.
But after project treble which introduced in android 8, all device-specific parts of android system image moved to vendor partition and we can use "Generic system images" over one vendor partition.
In halium version 9, we use this adventure and have a totally generic system image + root file system.
Requirements:
The only Requirement of booting this GSI is having Halium patched kernel.
Keep in mind having android 9 firmware installed on the device as GSI base is mandatory
What's needed ?
Phone needs to be treblized - thanks to the project : https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Then custom kernel & lineage image dedicated to Ubports - OP3 https://drive.google.com/drive/folders/1vnJEKkhO3xqH-fWWG55-yxwx5K1EeKq7?usp=sharing
Ubports GSI image are required
Installation steps:
- Download:
Recovery : twrp-op3treble-3.3.1-1.img : there
LineageOS 16 Ubuntu touch custom : there
Firmware 9.0.6 : oxygenos-9.0.6 be careful the firmwares are device specific : there
Download the latest GSI zip from there
Download the Halium-ramdisk there
Download the halium-boot.img there
Download the OP3_GSI_Fix_V1.1.zip there
- Reboot into fastboot and install the TWRP recovery => Check the official link for installation TWRP link
- Treblelize your OP3(t), by following the information there : https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
- Reboot into the TWRP Recovery
- Update the firmware
- Install LineageOS 16 Ubuntu touch custom
- Reboot into Lineage, confirm everything works fine.
- Ensure your /vendor (after mounting) is populated with content from an Android 9 ROM (LineageOS)
- Flash the GSI zip file
- Flash the halium-boot.img from before to your boot partition (if you didn't yet):
Code:
adb push ~/Halium/out/target/product/oneplus3/halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Or
Code:
fastboot flash boot out/target/product/oneplus3/halium-boot.img
- Flash the halium-ramdisk.zip
- Flash the fix for OP3 : OP3_GSI_Fix_V1.1.zip
- Reboot
- Enjoy
What's work:
Audio
Calling
SMS
4G - Yes but no icons - need to activated once after GSI is flashed
Wifi - Need a fix to restart it see the github repo
GPS
Vibration
Orientation sensor
Bluetooth
camera - zooming is sluggish
Video recording/decoding
Fingerprint + home button calling the dash <= Sweet !
What's Missing:
GSM tends to crash time to time on low signal.
Flash light
ADB/MTP - replaced by SSH
Libertine - didn't try yet
Anbox - Not tried yet
others ?
Thanks to :
https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
https://forum.xda-developers.com/pr...development/gsi-ubuntu-touch-ubports-t4110581
And Ubports team : https://ubports.com/

Hi, thanks for this port.
What's the differences between this gsi build and the official build that flash with ubports-installer?

Sbodezzi said:
Hi, thanks for this port.
What's the differences between this gsi build and the official build that flash with ubports-installer?
Click to expand...
Click to collapse
Hello Sorry, I didn't see your reply.
It's a good question, I'm trying to maintain both port, as a quick glance :
- Official Ubports is based on halium 7.1 based on lineage 14.1.
- Ubports GSI is based on halium 9 based on lineage 16.0.
The first one doesn't need partition modification while the second requires the dedicated vendor partition.
On the other side installing via the ubports installer is annoying sometime due to the partition management of oneplus3. (The same to format to install lineage)
Experience wise, the GSI tends to be smoother than the official Ubports on the other side the update (edge = unstable) on the GSI are currently coming randomly depending on Erfan works. I don't know in the future how this will be handle. GSI doesn't have OTA while Official ubports yes.
Hardware wise the GSI has the advantage to have : Video recording, fingerprint reading, incall volume working, on the other side there are some bugs graphic/touch glitch, no data icon etc...
Some bug listed in the github repository, I found a fix and now I need to create a script post GSI install.
I personally prefer to use daily the GSI due to the feeling to be smoother.
A good video describing this port : https://www.youtube.com/watch?v=UyOcQtNDZwM

Thanks for the thread!!
Are you the Kevin I talked to on the Halium TG? Seems you fixed RIL, that's cool!
Thanks

slash.tux said:
Hello Sorry, I didn't see your reply.
It's a good question, I'm trying to maintain both port, as a quick glance :
- Official Ubports is based on halium 7.1 based on lineage 14.1.
- Ubports GSI is based on halium 9 based on lineage 16.0.
The first one doesn't need partition modification while the second requires the dedicated vendor partition.
On the other side installing via the ubports installer is annoying sometime due to the partition management of oneplus3. (The same to format to install lineage)
Experience wise, the GSI tends to be smoother than the official Ubports on the other side the update (edge = unstable) on the GSI are currently coming randomly depending on Erfan works. I don't know in the future how this will be handle. GSI doesn't have OTA while Official ubports yes.
Hardware wise the GSI has the advantage to have : Video recording, fingerprint reading, incall volume working, on the other side there are some bugs graphic/touch glitch, no data icon etc...
Some bug listed in the github repository, I found a fix and now I need to create a script post GSI install.
I personally prefer to use daily the GSI due to the feeling to be smoother.
A good video describing this port : https://www.youtube.com/watch?v=UyOcQtNDZwM
Click to expand...
Click to collapse
Thank you for your exhausting answer.
It seems worth taking a ride ?

thanks very much for your hardwork

what is the default password?i tried 0000 but cant access my files

The default password is phablet, by ssh [email protected]

how to making system be rw?
this [guide](https://ubports.com/blog/ubports-blogs-news-1/post/terminal-chapter-3-3073) need adb but adb doent work,anyother idea?

weigeloveu said:
how to making system be rw?
this [guide](https://ubports.com/blog/ubports-blogs-news-1/post/terminal-chapter-3-3073) need adb but adb doent work,anyother idea?
Click to expand...
Click to collapse
Use the application UT tweak tool (from Open Store) and go to the system menu.

stuck at oneplus logo
EDIT:
Now it works!!!!!!!!!!!!!!!! I made the Format Data with TWRP and then flashed the boot image by fastboot. It seems like the path is wrong, I think the right path for the dd would be /dev/block/by-name/boot. But now it works!
Hello all,
I am not totally new to the whole flashing thing but also not an expert so please excuse some lack of knowledge.
But I tried now several times this instrucions and got some issues fixed by myself, but always I end up with a stucked boot logo.
Flash TWRP treble -> treblized -> flash LOS 16.0 treble - > Updated Firmware with op3.zip (more to that later) -> flash LOS 16.0 Ubuntu -> check if LOS works -> Flash halium-boot.img with adb -> Flash GSI -> flash halium-ramdisk.img -> flash GSI Fix -> Reboot
So my first question, and sorry for my dumbness, but what is meant by " - Update Firmware " ? Are there maybe some more detailed instructions for that ?
Because what I did was downloaded the linked git repository, and then I zipped the files wich were inside the op3 folder only. And this zip I "installed" with TWRP. But that felt always kida wrong so maybe thats my issue. But what else I have to do?
The second thing I noticed is that the command for flashing the boot.img with adb points to "/dev/block/bootdevice/by-name/boot" but "bootdevice" seems to be a file if I got to FileManager within TWRP. The only place where a "boot" file is located at my device is "/dev/block/by-name/boot" so should I use this path instead then?
Besides that I didn´t do "Format Data" before flashing the boot.img like it mentioned in the linked description. But not this thread here so I was not sure if I will destroy something by formatting....
I hope you can help me
And pls apologize my bad language

Hy guys, I followed instructions to install UT on my OP3T but mobile data doesn't work. Any suggestion?

Hello, thanks a lot for this, I ran it and it did run better than the official UT mostly. I was wondering if you could make a GSI_fix for the phone for droidian. Or if you could perhaps guide me/send any tips because I really don't know how to go about making an adaptation package for the droidian_gsi. Thanks in advance!

Afaik you do not need any fix for it. But we are OT. It should work with droidian-rootfs-api28gsi-arm64 and optional the -devtools package. Do not use any fixes!

[ROM][UNOFFICIAL] LineageOS 18.0 for Sharp Aquos S2 [SS2] [11.0]

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
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.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. For VoLTE, you need to enable it on stock firmware, then flash this modem via fastboot. Download link
Code:
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
Downloads Links
LineageOS 18.0:
Unofficial-build: Link
LineageOS 17.1:
Unofficial-build: Link
Notice: For LineageOS 17.1, if you doesn't have signal, please flash heineken78's treble 5.3 and my modem. REMEMBER, you need to get singal on treble 5.3 at first, then flash LineageOS 17.1.
Google Applications (optional):
You need to find the one for Android 11.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 8.1 from Sharp
Unlock bootloader is necessary.
You could flash 20201010 version via fastboot.
Root access:
Flash Magisk in recovery via adb sideload.
XDA:DevDB Information
Lineage 18.0 for Sharp S2, ROM for the Sharp S2
Thanks for heineken78's work of camera blobs on his LineageOS 17.1 build.
Source
Source Code: https://github.com/LineageOS
Device-tree: https://github.com/sharp-sdm660
ROM OS Version: Android 11
ROM Kernel: Linux 4.4
ROM Firmware Required: Official Android 11.0 firmware
Based On: LineageOS
Version Information
Status: Testing
Created 2020-10-10
Last Updated 2020-11-13

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Not-tested
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Not-tested
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: No
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Bluetooth audio: connect to the headphones but doesn't work

stillka said:
Bluetooth audio: connect to the headphones but doesn't work
Click to expand...
Click to collapse
Thanks for feedkback, this should be because of LineageOS 18.0' source is not completed. I will check it when compile again.

@Sjll, thank you for LOS 18. Am noting some comments about it on the largest Sharp S2 4pda.ru forum, particularly compared to the widely used @heineken78 LOS 17.1. Integrating TWRP recovery would be appreciated.
Usual TWRP recovery is missing
Recovery is different. It is necessary to put something like a gaps through a fastboot
recovery is similar to stock
Can someone sew custom recovery into the bottle from Los 18? In the Los 18 boot stock recovery.
just need to put the boot from LOS 17.1, the firmware has a standard recovery
Click to expand...
Click to collapse
Google Pay not working
Google playmarket error constantly: the device is not certified
If you make a format after installing gaps, it starts, but the device does not write certified
Click to expand...
Click to collapse

paulzie said:
@Sjll, thank you for LOS 18. Am noting some comments about it on the largest Sharp S2 4pda.ru forum, particularly compared to the widely used @heineken78 LOS 17.1. Integrating TWRP recovery would be appreciated.
Usual TWRP recovery is missing
Google Pay not working
Click to expand...
Click to collapse
No problem, For twrp, I think there is a hot-boot version if you googled it. Link
If necessary, I will build one for S2.
Try
Code:
fastboot boot twrp.img
About Gpay and other bugs, we need to wait for LineageOS fix them.
BTW, if someone could catch a log on SAT(sdm660), I will try to fix LineageOS 18.0 on it.
Method:
1. Flash LineageOS 18.0 by fastboot.
2. Hot-boot into twrp, then format data.
3.
Code:
adb push adbkey.pub /data/misc/adb/adb_keys
For Linux, adbkey.pub is in
Code:
cd ~/.android
For Windows, it is in
Code:
C:\Users\<YOUR USER NAME>\.android
4. Reboot, catch a full log
Code:
adb logcat -b all > sat.txt

Sjll said:
About Gpay and other bugs, we need to wait for LineageOS fix them.
Click to expand...
Click to collapse
Hi there is no Lineage fixes for Gpay.
Gpay has dependencies from props and selinux status, even official Lineage will fail Gpay checks.
Gpay is only for locked device and stock rom or look for solution with Magisk.

heineken78 said:
Hi there is no Lineage fixes for Gpay.
Gpay has dependencies from props and selinux status, even official Lineage will fail Gpay checks.
Gpay is only for locked device and stock rom or look for solution with Magisk.
Click to expand...
Click to collapse
KK, other people told me Gpay is supported if we could pass safetynet. But I could not test it because Gpay is not available for me.

Sjll said:
KK, other people told me Gpay is supported if we could pass safetynet. But I could not test it because Gpay is not available for me.
Click to expand...
Click to collapse
Hello, I installed your firmware. I tried to put google through bitegapps, the device is not certified. You can solve the problem with google to further study the firmware.

Noticed a new lineage-18.0-20201019-UNOFFICIAL-SS2.zip (Oct-19) download is available. Any feedback for the developer?

heineken78 said:
Hi there is no Lineage fixes for Gpay.
Gpay has dependencies from props and selinux status, even official Lineage will fail Gpay checks.
Gpay is only for locked device and stock rom or look for solution with Magisk.
Click to expand...
Click to collapse
Hi. I flashed your Lineage 17.1 rom for Sharp S3 from scratch, without any fixes and so on, just flashed Gapps and Gpay works without any problems. No magisk or any tools are installed. Is this fine?

@Angel_666, there is a dedicated thread you may consider directing your @heineken78's LOS17.1 query to:
Lineage 17.1 *UNOFFICIAL* for FIH (SAT/SS2/HH1/HH6/HD1/DRG)

New version uploaded.
@stillka Bluetooth-audio fixed. :

@Sjll , thank you for the new build. Are there any other changes here for previous mentioned issues?
- integrated TWRP recovery
- Gapps "not certified" fix
- Gpay working?
- SAT (SDM660 6/128GB) support

Sjll said:
New version uploaded.
@stillka Bluetooth-audio fixed. :
Click to expand...
Click to collapse
Hi,
the ROM is packaged in .zip, inside is "payload.bin", HOW should I flash it?!
Thank you.

paulzie said:
@Sjll , thank you for the new build. Are there any other changes here for previous mentioned issues?
- integrated TWRP recovery
- Gapps "not certified" fix
- Gpay working?
- SAT (SDM660 6/128GB) support
Click to expand...
Click to collapse
Hi, for twrp, there is a standalone one, after I solved some issues left, I will release it. If you need built-in twrp. You could install it manually.
For gapps, you need to ask other people, I do not know the meaning.
For SAT, I only have a sdm630 S2, I will try to solve it if I have time.
stillka said:
Hi,
the ROM is packaged in .zip, inside is "payload.bin", HOW should I flash it?!
Thank you.
Click to expand...
Click to collapse
Flash the old fastboot version.
Enable adb debug, then run
Code:
adb reboot recovery
You will boot into Lineage rec.
Choose apply update, then adb sideload the new zip.

Sjll said:
Flash the old fastboot version.
Enable adb debug, then run
Code:
adb reboot recovery
You will boot into Lineage rec.
Choose apply update, then adb sideload the new zip.
Click to expand...
Click to collapse
I downloaded older version but its same format, can you give me link for that oldest initial version (which I tested first time..)
Sent from my Mi MIX 2S using Tapatalk

stillka said:
I downloaded older version but its same format, can you give me link for that oldest initial version (which I tested first time..)
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
The oldest version is v20201010-fastboot.

Sjll said:
The oldest version is v20201010-fastboot.
Click to expand...
Click to collapse
Hi, thanks, I am on latest release now, but I was not able to find gapps which can be flashed using adb sideload and works, can you recommend working gapps version?
(or how to flash gapps?)
p.s: I had to flash gapps again because first time it flashed to wrong slot (_a/_b), now I have gapps, I am getting to test the rom...

So, I cant use google store - This device isn't play protect certified.....

[ROM] [TB3-710F] [BETA] [UNOFFICIAL] [7.1.2] LineageOS 14.1 for Lenovo Tab3 7 Essential Wi-Fi

{
"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"
}
Aptivi presents...
LineageOS 14.1 for Lenovo Tab3 7 Essential TB3-710F​
Disclaimer
----------
Code:
#include <std_disclaimer.h>
/*
*
* I'm 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.
*
*/
This ROM is currently in alpha state and bugs might exist without us spotting them. Please use the ROM with caution.
Description
-----------
LineageOS is a free, community-built, aftermarket firmware distribution of Android 10, 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 restores 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.
Downloads
---------
* For ROM:
- Link to all the LineageOS builds made by us is found on MEGA!
- Link to download GApps
* For recovery:
- Link to download Tzul's TWRP
- Link to download SP Flash Tool
Installation
------------
First, make sure that your TB3-710F tablet contains the TWRP recovery made by Tzul to be able to install LineageOS 14.1 into it. If you want to get the recovery, you can follow this guide on YouTube to install the recovery or you can follow the recovery part of this thread. After installing the recovery, follow the steps:
1. Download the latest build of LineageOS 14.1 in the MEGA folder listed in the Downloads section. It's found in the LineageOS > TB3-710F folder.
2. Download the GApps package
3. Place the downloaded files to your tablet. We recommend storing them on your external SD card.
4. Power off your Lenovo TB3-710F.
5. Turn the tablet on to recovery mode by holding the POWER + VOLUME UP + VOLUME DOWN buttons simultaneously until you see the TeamWin logo.
6. Backup your system, data, boot, and recovery partitions. TWRP provides you an option to store the backup on your external SD card.
7. Now, wipe your system, data, cache, and dalvik cache partitions by Wipe > Advanced Wipe.
>>> If you're upgrading LineageOS 14.1 to the newer build, don't wipe the data partition. The first time you reboot into the newer build, the boot time will be longer. It should take no more than 15 minutes. If any problems occur, wipe your data partition.
8. Once the wipe is done, go to Install and navigate to the folder that contains the LineageOS zip file. It should say "lineage-14.1-xxxxxxxx-UNOFFICIAL-TB3710F.zip". Click on the ZIP file and install it. Beware that it may take a long time.
9. Now, repeat the previous step, but this time, selecting the GApps ZIP file. Make sure the version you're installing is GApps for Android 7.1 ARM Pico.
10. Once you're done, wipe the cache and dalvik cache to make sure that no stale cache is left.
11. Go to Reboot > System to boot to your LineageOS installation.
Known issues
------------
This ROM is not perfect and could have stability issues.
* Build March 11th, 2023 -> March 23rd, 2023
- GPS may have trouble initializing
- Internal speakers may only play one sound channel instead of mono just like Stock ROM
* Build March 8th, 2023
- Camera not working with the green screen
- E-mail app not working with force closes
- GPS may have trouble initializing
- Internal speakers may only play one sound channel instead of mono just like Stock ROM
* Build March 5th, 2023
- Camera not working with the green screen
- E-mail app not working with force closes
- GPS may have trouble initializing
- Internal speakers may only play one sound channel instead of mono just like Stock ROM
- Microphone may not work
- WiFi listing may display "NVRAM WARNING = ERR 0x10"
Working features
----------------
* WiFi and Bluetooth
* Sound and Headphones
* Microphone [Build March 8th onwards]
* Touch
* SD card support
* Camera
* ...and more
Changes
-------
* lineage-14.1-20230323-UNOFFICIAL-TB3710F.zip [Beta]
- Fixed Internal storage issues with sdcardfs by reverting to FUSE
* lineage-14.1-20230311-UNOFFICIAL-TB3710F.zip [Beta]
- Fixed camera not working
* lineage-14.1-20230310-UNOFFICIAL-TB3710F.zip [Internal]
- Fixed E-mail force closes
* lineage-14.1-20230308-UNOFFICIAL-TB3710F.zip [Alpha]
- Fixed microphone not working
- Suppressed the "NVRAM WARNING = ERR 0x10" warning message
- Imported some patches from the device tree
* lineage-14.1-20230305-UNOFFICIAL-TB3710F.zip [Alpha]
- Fixed Android failing to boot because of missing libstlport.so
- Initial public alpha release
* lineage-14.1-20230304-UNOFFICIAL-TB3710F.zip [Internal]
- Initial internal release
Reporting issues
----------------
* 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:
Credits
-------
* Android AOSP Team: for the Android operating system source code
* LineageOS Team: for the ROM source code
* andrew264: for his kernel, device, and vendor trees for TB3-710F
* We maintain our own forks for his trees that shouldn't have been abandoned. Links below:
- Kernel: [Original] [Fork]
- Device: [Original] [Fork]
- Vendor: [Original] [Fork]
* @Tzul: for his TWRP build for TB3-710F
Screenshots
-----------
Screenshots are found in the bottom of this post as attachments.

What is your: TB3-710F Tablet
LineageOS version: 14.1
LineageOS Download url: from this post
Gapps version: from the link of the post
Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer: no
a non-stock kernel: no
other modifications: no
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: when i want to move a file from SDCard to internal storage, doesnt work, or when i want to move a file in the internal storage, doesnt work also, some apps have trouble writing some files on internal storage, they have fully permitions for writing and modifiying

IsaacCastle said:
when i want to move a file from SDCard to internal storage, doesnt work, or when i want to move a file in the internal storage, doesnt work also, some apps have trouble writing some files on internal storage, they have fully permitions for writing and modifiying
Click to expand...
Click to collapse
Thanks for reporting this issue!
We're aware of this issue and will investigate it. Once investigation is done, the fix will be released shortly.
By the way, we tested creating and writing a file on the internal storage using QuickEdit, and received this error on Logcat:
Code:
java.io.FileNotFoundException: /storage/emulated/0/untitled.txt (Invalid argument)

@IsaacCastle Good news!
We found a fix for your problem with the internal storage. It involves disabling sdcardfs and restarting your tablet. This is caused by incompatibility with sdcardfs on the TB3-710F.
1. Open Settings
2. Tap About and tap on the Build number 7 times to unlock developer settings
3. Go to Developer options and enable Android debugging
4. Enable Android debugging and set "Root access" to "Apps and ADB"
5. Connect your tablet to your PC (assuming that it's Windows) and download the Platform tools from here: https://developer.android.com/studio/releases/platform-tools
6. Unzip the platform tools ZIP file (we recommend unzipping to C:\platform-tools for easier access)
7. Open the command prompt to the platform tools directory.
- 7a. Open the command prompt
- 7b. Change the current directory to the platform tools folder (cd C:\platform-tools)
8. Execute the following commands:
Code:
adb.exe devices
adb.exe shell
- We require running adb.exe devices before the shell to verify that you can authorize your tablet to your computer.
9. Re-mount the system, because we're going to edit build.prop
Code:
su
mount -o rw,remount /system
10. IMPORTANT! Back the build.prop file up in case something is wrong
Code:
cp /system/build.prop /system/build.prop.bkp
11. Now, use the sed command to replace the ro.sys.sdcardfs=true line with ro.sys.sdcardfs=false:
Code:
sed -i 's/ro.sys.sdcardfs=true/ro.sys.sdcardfs=false/g' /system/build.prop
12. Restore the system to read only
Code:
mount -o ro,remount /system
13. Exit the ADB shell and unplug your tablet from your computer
14. Restart your tablet
15. Try to write a file to the internal storage now. It should work.
If it still didn't work, post your dmesg and logcat.
Meanwhile, we'll upstream the fix to the second beta release!
Again, thanks for reporting this to us!

All right! Thank you very much for your attention! I will fix the problem as you said, i will be waiting for the beta release, again thank you very much for your attention!

I will download the other beta release with that fix, i will be analising the beta in this (Really old) tablet, i need to say something: the performace is really really awesome, it is much better even from the stock rom! your work is really apreciated, and again thank you very much for your attention!

You're welcome, @IsaacCastle! Enjoy this ROM!

Hello! I've used this ROM and it's pretty good! The performance is good and i fell it really stable, but i've found some problems:
YouTube vídeos get lagged with 720P Quality, in 480P is ok, but looks píxeled, the camera is not working (I don't even use the camera but is a detail) and that's all! It would be great is you can optimize the operating system lowering the RAM usage, and that would be all! I wanna thank you for your hard work of this ROM for reviving my old tablet, again, thank you very much.

What is your--
LineageOS version:14
LineageOS Download url: mentioned above
Gapps version:mentioned above
Did you--
wipe:yes
restore with titanium backup:no
reboot after having the issue:yes
Are you using--
a task killer:no
a non-stock kernel:no
other modifications:no
Provide any additional information (observations)
Hello, i just came across this rom and i tried installing it the exact way mentioned, andit just doesnt boot whatever i do, i tried about 4-5 times now, i didnt restore anything, just flashed rom and gapps mentioned above, it still doesnt boot.