[ROM][UNOFFICIAL][8.1] LineageOS 15.1 for Amazon Fire HD8 7/6th gen (douglas/giza) - Fire HD 8 and HD 10 Original Android Development

[ROM][UNOFFICIAL][8.1] LineageOS 15.1 for Amazon Fire HD8 7/6th gen (douglas/giza) - Fire HD 8 and HD 10 Original Android Development

⏱ Change log / Release Notes
2022-06-14 [douglas] [giza]
Updated sdcardFS to 2.0.
Updated the exFAT driver.
Fixed detection of external SDs.
2022-06-13 [douglas] [giza]
Rebased the entire tree, did a general cleanup
Fixed MicroG support (Signature Spoofing)
Fixed and re-enabled sdcardFS
Fixed direct Magisk installation/update
Enabled USB MIDI support
Enabled OTG ethernet support
Disabled binder logging
Enabled OpenGLES AEP
2022-01-02 [douglas] [giza]
Fixed USB tethering.
Added mediatek perf support.
Updated vendor blobs to the latest FireOS version.
Defined the vendor security patch.
2021-11-07 [douglas] [giza]
Fixed video recording on douglas.
2021-10-31 [douglas] [giza]
Fixed some DRM leftovers.
Added initial microG support.
Added exFAT support.
Fixed audio stream.
Added ged support.
Updated security patch to October 2021.
2021-10-03 [douglas] [giza]
Completely disabled sdcardfs.
Purged a lot of mtk/amazon logging.
Fixed missing symbols/libraries.
Reworked the audio configurations.
Fixed all the sensors.
2021-09-16 [douglas] [giza]
Fixed camera on douglas.
2021-09-12 [douglas] [giza]
Cleaned up wi-fi blobs/configs/service definitions.
Kanged the wi-fi HAL from a 8.1 mediatek device.
2021-09-07 [douglas] [giza]
Fixed swapped volume keys.
Show internal storage by default in the file manager.
Added option to reboot to hacked bootloader using ADB.
Disabled the update recovery function.
Added support for more SDs/USBs with other formats.
2021-09-05 [douglas] [giza]
Fixed over the air (OTA) updates.
Fixed Magisk/GAPPs installation.
The build is now signed with dev-keys.
Fixed installation of the ROM on giza.
Addressed a few SELinux denials.
2021-09-03 [douglas] [giza]
Audio works fine, incuding the mic.
DRM works fine, reports L1.
Video playback works partially fine.
Disabled camera as it doesn't work.

Reserved

Reserved

Rortiz2 said:
Magisk
For some weird reason, Magisk zip won't work (because of shims, wtf) so you'll need to manually patch your boot image with the Magisk Manager app and you'll need to flash it to boot_x with hacked fastboot mode or to boot with TWRP.
Click to expand...
Click to collapse
Fastboot is informed of the exploit so fastboot flash boot <path> will work.

SamDungUser said:
Fastboot is informed of the exploit so fastboot flash boot <path> will work.
Click to expand...
Click to collapse
No, fastboot isn't informed of the exploit, fastboot flash boot will overwrite the microloader and will brick the device.

Rortiz2 said:
No, fastboot isn't informed of the exploit, fastboot flash boot will overwrite the microloader and will brick the device.
Click to expand...
Click to collapse
Didn't know that. I think that's why I had to erase the boot partition just so I can install a rom again. it was able to boot to twrp so I just rebooted to hacked BL and erased then boot back and flash a rom in twrp

SamDungUser said:
Didn't know that. I think that's why I had to erase the boot partition just so I can install a rom again. it was able to boot to twrp so I just rebooted to hacked BL and erased then boot back and flash a rom in twrp
Click to expand...
Click to collapse
Yes that's possible, because TWRP restores the microloader (boot-exploit). Great to hear that you could recover it.

if you need to check the md5 upload the file and use https://emn178.github.io/online-tools/md5_checksum.html

The rom is abnormally large? When selecting the aroma package barely anything fits, in 7.1.2 it fit 5x more apps using th aroma package also 400 MB for the rom? what's causing this? how can I make the system partition bigger?

SamDungUser said:
The rom is abnormally large? When selecting the aroma package barely anything fits, in 7.1.2 it fit 5x more apps using th aroma package also 400 MB for the rom? what's causing this? how can I make the system partition bigger?
Click to expand...
Click to collapse
If I'm allowed to ask, what's aroma? And yeah, the ROM size it's quite normal since Android O includes vndk and hidls.

It feels really snappy compared to 14.1. I guess that's because of a different launcher?

dontpanic-xda said:
It feels really snappy compared to 14.1. I guess that's because of a different launcher?
Click to expand...
Click to collapse
I don't think the launcher has something to do with the snappiness. I guess Android Oreo it's more optimized than Android 7. You also need to keep in mind that I've updated the GPU drivers (kernel-side, mali).

Wow, great job @Rortiz2 ! Respect and thank you!

Rortiz2 said:
If I'm allowed to ask, what's aroma? And yeah, the ROM size it's quite normal since Android O includes vndk and hidls.
Click to expand...
Click to collapse
Aroma is an open gapps installer it includes all apps and offers a gui installer. Also, I found out what causes the screen issue. Apparently just installing a SELinux switcher app will cause the issue where if you put it to sleep by pressing the power button and you press the power button again to take it out of sleep nothing happens. I don't know how just installing a selinux switcher causes the screen issue and the Bluetooth crashes

SamDungUser said:
Aroma is an open gapps installer it includes all apps and offers a gui installer. Also, I found out what causes the screen issue. Apparently just installing a SELinux switcher app will cause the issue where if you put it to sleep by pressing the power button and you press the power button again to take it out of sleep nothing happens. I don't know how just installing a selinux switcher causes the screen issue and the Bluetooth crashes
Click to expand...
Click to collapse
Why would you set SELinux to enforcing..? Sepolicies aren't yet prepared to do so... Anyway, I don't have any clue about aroma, use the standard gapps package I guess.

Rortiz2 said:
Why would you set SELinux to enforcing..? Sepolicies aren't yet prepared to do so... Anyway, I don't have any clue about aroma, use the standard gapps package I guess.
Click to expand...
Click to collapse
I want to have it on enforcing to get safetynet to pass

SamDungUser said:
I want to have it on enforcing to get safetynet to pass
Click to expand...
Click to collapse
Alright, I guess I'll try to fix sepolicies then. Don't expect it to be quick though, this takes a lot of time.

I'm really impressed with this ROM. Running Services reports nearly 800 MB free after boot and it's definitely snappier. Also, viewing Settings with a pure black background is probably my favorite feature.
One thing I did run into was that during the install of GApps, it seemed to stall after the Installation Complete message. I just rebooted manually and it was all fine. Great job, Rortiz2

rom installs fine but it looks like it freezes after "installation compete" for opengapp.
Used the link above for openapp. Did not choose a different variation.

Related

[CM11][GT-S7562] Samsung Galaxy S Duos Kitkat 4.4.4

{
"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"
}
Samsung GT-S7562 CyanogenMod 11.0 Android 4.4.4
Unofficial Release
I proudly present my first Android related work.
The GT-S7560M has a similar hardware except the dual-SIM RIL, so the kylessopen firmware (thanks to jonypx09 and others) was a good initial source.
I reverse engineered the stock Java Radio Interface Layer, and based on that informations, I restructured the kylessopen’s sources.
Finally with my custom telephony-common, telephony-msim java layer, and with the stock rild, and libril*.so binaries, the GSM connection works.
Important: This is an unofficial release. If you find a bug, please send a feedback in this thread.
If you have a problem with the installation, write it down in the Q&A thread.
Compatibility:
S7562, S7562L supported.
S7562_C_, S7562_i_ are not supported. Don't flash on it, otherwise you will brick your phone.
Issues:
Video Encoding has bugs.
Camera is only 3Mpx.
FM radio not supported.
WiFi not works on L version, I need a tester.
Requirements:
TWRP Recovery latest (3.0.2) recommended
Installing TWRP method when no custom recovery is installed at all:
1. Download Odin flashable TWRP .tar to your PC
2. Reboot to download mode and flash TWRP with Odin
3. Reboot to TWRP recovery using VolUP+VolDN+Home+Power keycombo
4. TAKE FULL BACKUP of your system in order to be able to restore if something fails. This is important
5. proceed with cm Installation
Installing TWRP method when custom recovery cwm or twrp is already installed:
1. Download the latest Recovery flashable TWRP .zip package to your device
2. Reboot to custom recovery and flash TWRP .zip
3. TAKE FULL BACKUP of your system in order to be able to restore if something fails. This is important
4. proceed with cm Installation
CM11 Installation method:
1. Download the latest cm11 package to your device
2. Reboot to TWRP recovery.
3. TAKE FULL BACKUP of your system in order to be able to restore if something fails. This is important.
4. Make a factory-reset / Wipe your phone (everythig except SDCARD) important to prevent bootloops
5. Install Unofficial CM11 with TWRP (Uncheck zip file verification before install).
6. Reboot and configure your system
optional. If you are going to use gapps, reboot to TWRP recovery, flash gapps.
optional. If your mobile Connections are not working Flash the hungarian modem using TWRP recovery
Download links:
Hungarian Modem: Modem_S7562XXLJ3.zip Recovery flashable
Odin v3 for Windows: Odin3_GT-S7562.zip
Recovery - TWRP 3.0.2: recoveryTWRP302 Recovery flashable
Recovery - TWRP 3.0.2: recoveryTWRP302 Odin flashable
Latest version of gapps - opengapps.org. Select ARM as platform, select 4.4 as Android. As variant "pico" is recomended.
Stock Hun Firmware: S7562XXALJ4_S7562OXXALJ3_S7562XXLJ3_HOME.tar.7z
S7562 Cyanogenmod 4.4.4 RC3+
RC3 Maintenance updates + additional improvements built by klinkone and kengnatural
cm-11-20161028-UNOFFICIAL-kylessopen
The changelog of the latest build:
Latest security updates
Fixed OMX bug which did not allow the latest version of Viber app to work.
ART compile timeout increased to allow large program to be installed.
For primary-physical configuration, where there is no emulated external memory, only physical sdcard is used as an external memory, please see below:
cm-11-20161029-UNOFFICIAL-kylessopen-physical-primary.zip
Previous build:
cm-11-20160305-UNOFFICIAL-kylessopen
default cpu governor set to ondemand and min. cpu freq. set to 245 MHz by default
default minfree settings changed to avoid hanging of the phone when zram is full;
ART fix for gcc-4.8 (thank to JustArchi)
BLN support without external app (button backlights are used as notification leds)
fixed front camera preview hanging after taking a picture
initial fix of facebook app video codec issue (still buggy)
For primary-physical configuration, where there is no emulated external memory, only physical sdcard is used as an external memory, please see below:
cm-11-20160305-UNOFFICIAL-kylessopen-physical-primary
This build is the same as cm-11-20160305-UNOFFICIAL-kylessopen ROM with the following differences:
physical-primary configuration
experimental high vm.dirty_ratio setting for improving i/o speed
Old changelogs
20160207 changelog:
-mounting the "hidden" partition disabled
-obsolete start() and startvm() returned back to support xposed again
-fixed soft reboot issue when bluetooth is switched off and user sends some file using it
20160205 changelog:
-bluetooth soft reboot fixed by kengnatural
-theme uninstall soft reboot fixed by kengnatural
-available ram is 645mb (~20mb more which is as stock)
20160105 changelog:
-zram and zcache updated + fixed
-zram reduced to 128mb
-added missing things for low ram config according to: https://source.android.com/devices/tech/config/low-ram.html
-user friendly f2fs support
-ramdisk ext4/f2fs double entries for /data and /cache
-initial BLN (capacitive keys act as notification LED)
-some cleanup in device tree
-removed cm-updater (obvious why)
20151230 changelog:
-applied "JustArchi's ArchiDroid Optimizations V3 for CyanogenMod (11)" optimization level -O3
-using google's GCC4.8 for rom and kernel
-bluez updated to V5.36 thanks @Codename13 for sending the pull request
20151207 changelog:
-changed kernel repo to my fork of majonez BA2X-2.0
-xposed patch
-fstab updated
-unused 50mb hidden partition is mounted to /hidden on boot do whatever you want with it
-dalvik-cache devided system apps go to /cache/dalvik-cache user apps go to /data/dalvik-cache (saves some space in /data)
-256mb zram enabled by default
20151127 changelog:
-initial basic rc3 configuration for updated RC3+ builds
-some repos changed to up to date ones (legacymod)
-latest cm-11.0 sources of 27.11.2015 including android security-patches of 01.11.2015
-wifi reconnect working
-no systemupdateservice wakelock aka google play services wakelock battery drain etc.
S7562 Cyanogenmod 4.4.4 RC3
Changelog:
1. Improved Bluetooth support
2. Most kernel debug flags disabled
3. Added some missing libraries
4. Merged all CyanogenMod source changes
5. Bugfixes
Comments:
I think it's a little faster than previous versions. - What do you think?
You can update system from RC2 without wipe your phone.
You can enable "Force high-end graphics". Mostly, animations are smooth.
I ask everyone, who have bluetooth accessories to test the bluetooth layer, and provide feedback what is working or not (just with log cats).
ROM: cm-11-20150323-UNOFFICIAL-kylessopen-RC3.zip
Old Releases
S7562 Cyanogenmod 4.4.4 RC2 - download count close to 1k
Changelog:
1. Backported Bluetooth driver and Management Interface from Linux Kernel v.3.13
2. Newest Bluez 5.28 Bluetooth stack
3. Few bugfixes to wireless driver
4. All RC1 updates included
You must wipe your phone before upgrade to RC2!
ROM: cm-11-20150309-UNOFFICIAL-kylessopen-RC2.zip
kernel_kylessopen_RC2_v2.zip This update solves bluetooth wakelock issue, so the phone can go to deep sleep.
bluetooth_startup_fix.zip This update solves the system crash at startup.
KlinkOnE's kernel based on RC2_v2 with F2FS support: ==>
S7562 Cyanogenmod 4.4.4 RC1 - downloaded more than 1k times
Changelog:
ROM: http://uploaded.net/file/pionx3a0 mirror: cm-11-20150205-UNOFFICIAL-kylessopen-RC1.zip
Updates for RC1 (flash with TWRP):
browser_fix.zip
signal_strength_fix.zip
torch_fix.zip
CameraFIX_v2.zip This will fix the front and back videocamera. Before install this, disable Viber's videoConverterService with DisableService app (Play Store).
If your battery quickly discharges on RC1, disable all bluetooth service (org.codeaurora.bluetooth, Bluetooth Share) with DisableService (Play Store).
Comments:
Working Radio Interface Layer for both SIM card
WiFi direct is not supported, so you can't enable. Use Bluetooth, Dropbox, email etc...
If you want to install Viber, before the first start, disable Viber's videoConverterService with DisableService app (Play Store).
The "OneL+ Lollipop" theme with "IdeaL Theme Dark"'s icons is beautiful.
To prevent sound disruption, enable the equalizer.
About Google Apps, and GService Bug
Fixed with all releases after rc3. For reference see below
Latest gapps (ver. 7.x) has issues, and eat our baterry, so I recommend to install the package that I linked, disable autoupdate in Gapps, and disable GPlay's CheckWifiAndAutoUpdate service with DisableService (from Play Store).
If your Gservices app updated to the version 7.x, you can easily downgrade to 6.x
(you can do this, if you installed my linked package or earlier):
Settings-->Security-->Device Administrators-->Uncheck "Android Device Manager"
Settings-->Apps-->Google Services-->Disable-->Yes, you want to remove updated version
Recommended gapps: pa_gapps-modular-pico-4.4.4-20150117-signed.zip
Future:
bugfixes
XDA:DevDB Information
[CM11][GT-S7562] Samsung Galaxy S Duos Kitkat 4.4.4, ROM for the Android General
Contributors
m4jonez, KlinkOnE, kengnatural
Source Code: https://github.com/majonez
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Beta
Created 2015-03-27
Last Updated 2016-12-06

m4jonez said:
Samsung GT-S7562 CyanogenMod Kitkat Unoffical release
Click to expand...
Click to collapse

huntercity said:
doesn't works
Click to expand...
Click to collapse
What's wrong with links?
I can download files. It is a bit slow, but works for me.

m4jonez said:
What's wrong with links?
I can download files. It is a bit slow, but works for me.
Click to expand...
Click to collapse
both link response ... "ERR_CONNECTION_REFUSED"
the link about the sammobile firmware works

huntercity said:
both link response ... "ERR_CONNECTION_REFUSED"
the link about the sammobile firmware works
Click to expand...
Click to collapse
Maybe this site is blocked for you by your ISP or your DNS server is not serving this domain.
Try to set DNS servers for your computer to 8.8.8.8 and 8.8.4.4 (Google DNS).
Or use TOR browser.

m4jonez said:
Maybe this site is blocked for you by your ISP or your DNS server is not serving this domain.
Try to set DNS servers for your computer to 8.8.8.8 and 8.8.4.4 (Google DNS).
Click to expand...
Click to collapse
i tried different proxy and different connection but the results it's always the same

Link Please GAPPS for this rom
http://d-h.st/U30 tested by me works on stock hungary + cm11

deleted

I try the rom with EUR XXBML1 firmware and the ril doesn't work. If I have time i will try the rom again with the Hungary firmware. And something more, we will have update for those that don't work??

Your first job! The great one hats off brother gave another life to the device
Sent from my Micromax A106 using XDA Premium 4 mobile app

Hey
Hi, Thanks. just wanted to know if one sim card works or 2 are required??

You Nailed it bro! @m4jonez
YES! 100% Verified that we get network on both (you can insert single as well) .
However that the rom is a bit laggy (much better than one would expect from a first build).
Yes there are bugs ! but yeah! there is network too..
Where should we report the bugs bro @m4jones? I found some.
1 network on indian modem is super duper unstable.. so change op and recomended people to flash your modem file.
With your modem , i found the sim networks to be quite stable.
2 torch app is useless as neither app nor widget works. So fix it or remove it
( CAMERA WORKING FINE FOR ME)
COngrats and all the best ! continue your good work

The built-in browser fixed.
Where should we report the bugs bro @m4jones? I found some.
Click to expand...
Click to collapse
Post it here.

minor problem here:
Signal strength is reported wrong for both sims.
Always shows full strength.
Recognition seems to be working as values are changing but they are much too high. Around 2000dBm.
Phone calls in/out SMS and data rock stable on both sims for me.
Performance is good(better than expected).
Zram is not working init.rc entries(or script) are missing. Maybe a kernel problem too idk ATM.
Thanks @m4jonez you're great!!!!!
Gesendet von meinem GT-S7562

Perhaps it will help you to fix the flashlight in this time and the future.
http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267

KlinkOnE said:
minor problem here:
Signal strength is reported wrong for both sims.
Always shows full strength.
Recognition seems to be working as values are changing but they are much too high. Around 2000dBm.
Click to expand...
Click to collapse
fixed.
Vergilliy said:
Perhaps it will help you to fix the flashlight in this time and the future.
http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267
Click to expand...
Click to collapse
It was just a path issue with Torch. Fixed.

m4jonez said:
fixed.
Click to expand...
Click to collapse
working that was fast
Thanks
Gesendet von meinem GT-S7562

Step by Step Guide
Please provide step by step installation guide & few more after installation photos.

Review !!
Great Work !!:laugh::good: @m4jonez . Love to have a Cm Rom for our device
My thougts :
1) Battery drainage is an issue..
2) Interface Performance is good but can be better ( can't expect more from Rc1 )
3) Need a good overclocked Kernel !!
THANKS A TON
One Question ........Is lollipop next :fingers-crossed: ( kidding )

Can I flash Stock kernel in this??

[ROM][UNOFFICIAL][6.0.1] CyanogenMod 13.0 for Elephone Trunk

This ROM is a genuine CM13 build from source for the Elephone Trunk. It's based on mdeejay's Ark Benefit code with modifications by @BlueFlame4 and @hisname. The source code is available on GitHub.
Working:
Phone
Mobile data in dual-sim configuration
Wifi
GPS
Bluetooth
Audio
Known Bugs:
Torch tile in the status bar is not available
Haptic feedback on soft buttons
XDA:DevDB Information
CM13 for Elephone Trunk, ROM for all devices (see above for details)
Contributors
ottmi, siljaer
Source Code: https://github.com/ottmi/android_device_elephone_trunk
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20160902
Beta Release Date: 2016-09-02
Created 2016-06-07
Last Updated 2016-09-02

Changelog
20160902
First try to fix sdcard issues, will need more testing
Fix thermal-engine to actually start
Fix audio_effects.conf
Tweak auto-brightness
Enable OTA updates
Use Wileyfox Swift blobs for everything but camera
Update to latest CM13 source
20160816
Enable thermal-engine to fix overheating emergency shutdowns
Update kernel to latest MSM8916 to fix Quadrooter vulnerabilities
Re-enable AEC audio effects
Update to latest CM13 source
20160811
Revert changes to mixer_paths.xml and audio_effects.conf to fix echo problems
Update to latest CM13 source
20160803
Update to latest CM13 source to fix surfaceflinger crashes
20160803
Tweak GPS settings to obtain faster locks
Enable input event for headphone jack
Use ACDB libraries from Wileyfox swift, fix some ACDB-related settings
Update to latest CM13 source
20160722
Incorporate @siljaer's modifications to mixer_paths.xml to fix echoes and low volume audio recordings
Pull in additional permissions to reflect actual hardware of the phone (light & proximity sensor)
Change screen density to 300dpi
Backport LZ4 compression from Linux 3.12 for use in ZRAM
Try to fix Torch problems by restarting media service after full boot
Update to latest CM13 source
20160708
Fix wpa_supplicant crashes
Update to latest CM13 source
20160706
Switch to generic CyanogenMod MSM8916 kernel
Use Wileyfox Swift kernel configuration as template
Increase partition sizes of system and data to 1.8GB and 12GB
Update to latest CM13 source
20160630
Fix bug in libstagefright properly
Fix sensor glue code to only show actually existing sensors
Fix device permissions
Use own key to sign code instead of testkeys
Set selinux to enforce
Update to latest CM13 source
20160616
Fix mediaserver crashes to a bug in libstagefright (roll back to commit 8f270dc)
Use Adreno binary blobs from Wileyfox Swift (which are more complete)
Update to latest CM13 source
20160614
Enabling of Qualcomm Fluence as suggested by @Bingo Bronson
Backport of the F2FS driver from Linux 3.12
Enabling of LTE as preferred network on 2nd SIM card as well
Some changes to the auto brightness thresholds
Update to latest CM13 source
20160611
Enable haptic feedback on soft keys
Change default device name for wifi direct and hotspot to "Trunk" (not Benefit!)
Update to latest CM13 source
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source

Flashing Instructions
You will have to disable the bootloader lock first:
Enable developer options in Android by tapping the Build version in Settings > About 7 times
Check "Enable OEM unlock"
Next you will have to boot into TWRP, use @hisname's TWRP:
http://forum.xda-developers.com/gen...410-5-inch-t3177753/post66208281#post66208281
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash recovery twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.

Installation Xposed Rom Ottmi
Installation Xposed Rom Ottmi
 @ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work

josoft86 said:
Installation Xposed Rom Ottmi
@ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work
Click to expand...
Click to collapse
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?

josoft86 said:
I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64
ottmi said:
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.

ottmi said:
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source
Click to expand...
Click to collapse
Great, so many thanks, but, the link?

marcachas said:
Great, so many thanks, but, the link?
Click to expand...
Click to collapse
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
{
"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"
}
Visit xda with your browser if you are currently on xda labs or some kind of forum app.

Bingo Bronson said:
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
Visit xda with your browser if you are currently on xda labs or some kind of forum app.
Click to expand...
Click to collapse
Oh, thanks, you are the best, this rom is so table and smooth, your job is awesome, a hug.

Thank you. I decided to buy the Elephone Trunk because I was interested in a economic phone that could 'easily' be upgraded with non stock ROM (preferably CM 13).
I have gone through the previous conversation and I must admit I'm impressed with your progress so far. Congratulations and a big thank you!
I will definitely flash your build as soon as I receive the phone.
Enviado desde mi Nexus 5 mediante Tapatalk

Great job!
Great job and super useful guide @ottmi.
Thank you!
I am currently running your previous release (cm-13.0-20160515-UNOFFICIAL-trunk) and have no issues to report at all!
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
Thank you for the excellent work.
Kind regards.
P.S. I have downloaded and installed GAPPS (Google Apps) from CM portal and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.

kbezerianos said:
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
[...] and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.
Click to expand...
Click to collapse
Dirty flash is enough, no need to clean everything. Just install the new build, wipe the caches afterwards like it is suggested by TWRP recovery.
Some of your apps may have a survival script, others need to be reflashed (this is just the case for special tools, like Xposed, etc.)
Nano Gapps is a smart choice either way, because all the pre-installed Gapps will be outdated soon enough, so why bother to install a "huge" Gapps pack...
I use microG and have roughly 260 MB left on the system partition.

Bingo Bronson said:
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.
Click to expand...
Click to collapse
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you

josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
But, but... I'm also on 3.0.2-0 and the Xposed zips & ROMs, for example, are processed without error, Aroma installer is also supported...
Who compiled / ported your TWRP version? I used only @hisname releases and they never let me down. ?
ottmi said:
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.
Click to expand...
Click to collapse
I didn't even consider that possibility, since it has been mentioned numerous times in the old thread, ignorance is bliss (on my side), ahem...
I'm out of "thanks" to give, so I'll "upvote for awareness" later...

josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.

ottmi said:
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash boot twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.
Click to expand...
Click to collapse
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!

One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Enviado desde mi Nexus 5 mediante Tapatalk

21prods said:
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!
Click to expand...
Click to collapse
Bummer. You're right, I've fixed the instructions accordingly. Sorry for that!

21prods said:
One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Click to expand...
Click to collapse
I'm using a 32GB microsdhc to store music and pictures, no issues at all. I've also used 64GB mirosdxc without problems. I've never tried moving apps though.. How does it show in Settings->Storage & USB?

Yes, that's it. There you have the possibility of formatting the SD card to use it as (more) internal memory.
Enviado desde mi Nexus 5 mediante Tapatalk

[EOL][ROM][SDCLANG-6][microg-ready][OMS Service Mode]NLOS-15.1 - 20190208

NLOS is an unofficial LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. This build is optimized for oneplus3t - it will flash and run on a oneplus3, because it's an unified build, but it's optimized for 3t!
In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch, ported to Oreo) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps).
NLOS doesn't require any mods to work with @Arnova8G2's GoogleCamera Mod (more details in S4turno's thread ). Just install the modded Gcam - no need to flash twrp-front-fix-oreo-op3-3t.zip, nor to use the magisk module.
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
NLOS features OMS Service Mode - the successor of ThemeInterfacer. This means you don't need root and/or andromeda to have full Substratum Theming! It's faster then andromeda and does not rely on a tethered pc-connection. It has more exposueres (items exposed to the themers) then the rooted solution. If substratum should ask for root previlegs, deny it.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"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 isn't void: we are on an oneplus device.
*
* 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 us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 15.1 builds for oneplus3 and onepluy3t. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files (i.e. by using gapps larger then opengapps-nano)
First time flashing NLOS 15.1 on your device, or coming from another ROM:
Backup your current ROM and make sure you have backups of your data you want to keep.
Download the ROM below in the downloads section.
Download current MindTheGapps for arm64. If you insist on using gapps, don't use a package larger then nano.
Download and flash twrp-3.2.3-0!
Download and flash latest OxygenOS Oreo firmware.
Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you are insisting to use f2fs see: https://forum.xda-developers.com/on...1-20180223-t3754855/post75688089#post75688089 - NOT recommended!
Wipe system, data and caches.
Flash NLOS.
Flash Google Apps. If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Optional: flash Magisk (if you need root)
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery (if necesarry flash the firmware zip recommended by the release notes) and flash the updated NLOS zip - don't forget to wipe dalvik and cache. Settings, apps and even google apps are preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.cmxlog.com/15.1/
Build 20190208
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 8 Feb 2019, 14:09:19 CET / 8 Feb 2019, 13:09:19 UTC):
Merge tag 'v3.18.134' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
ARM: dts: msm: FIxup GPU 0mhz clock — Nvertigo
drivers: video: mdss: Fix direct references to HZ — celtare21
drivers: ipa: Fix direct references to HZ — Humberto Borba
drivers: platform: gsi: Fix direct references to HZ — Humberto Borba
drivers: hwmon: Fix direct references to HZ — Humberto Borba
drivers: i2c: Fix direct references to HZ — Humberto Borba
Convert few critical drivers to use msecs_to_jiffies insted of HZ — Dorimanx
msm: kgsl: Remove POPP — Sultan Alsawaf
current.pick.sh: O_asb_2019-02. — Nvertigo
current.pick.sh: introduce a safer repopick. — Nvertigo
op3/t: nfc: advertise support for extended length NFC — Paul Keith
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
History
Build 20190127
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 27 Jan 2019, 13:01:40 CET / 27 Jan 2019, 12:01:40 UTC):
current.pick.sh: force picking abandoned battery customisation commits (220407, 220422, 219299) — Nvertigo
op3: Restore better load balancing after boot — Thomas Shum
WG: squash WireGuard-0.0.20190123. — Nvertigo
Merge tag 'v3.18.133' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
TWRP
Latest official twrp
Thread for official twrp
Google Apps:
MindTheGapps-8.1.0-arm64-20180223_195845.zip
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/nlos-15.1 (If you want to build this rom yourself, consult the file named README, it's outdated, but still helpfull)
Aytex, who made all of the banners on this post.
team-exynos5420 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
The microG Team
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
@Arnova8G2 for his GoggleCamera port.
@S4turno for this great thread on GoggleCamera Mods.
@knpk13 for debugging this OP.
Substratum Dev Team
@danieldmm for opening my eyes for the obvious...
@mcdachpappe for helping me with additional notification slider options.
...and everybody I forgot.
Happy flashing!
XDA:DevDB Information
NLOS-15.1, ROM for the OnePlus 3
Contributors
nvertigo67, dianlujitao
Source Code: https://github.com/nvertigo/local_manifest/tree/nlos-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: latest
Based On: LineageOS 15.1
Version Information
Status: Stable
Created 2018-12-04
Last Updated 2018-12-04

Known Issues
fixed: NLOS can't initially encrypt f2fs data partitions (though ext4 is working flawlessly).
fixed: NLOS can't change the encryption passphrase for f2fs/ext4 data partitions (though ext4 is working flawlessly).
fixed: adb and mtp doesn't work out of the box. Workaround:
put in QS-tile "adb over network"
disable wifi
enable "adb over network" with the added tile (tile shows 0.0.0.0)
connect usb cable
an expandable notification shows up
expand it, tap it and select "file transfer": voila.
If you've run through the above adb and mtp are working fine - even trough reboots... automagicaly...
If secure boot password, pin or pattern is set: LiveDisplay's Settings show color profile as "Standrad" after a reboot, though the configuered LiveDisplay's color profile is correctly aplied.
Notification lights have hickups.
fixed: With no substratum themes applied and dark mode enabled the qs edit page is in stealth mode (white text on white background). For reference see: https://forum.xda-developers.com/ap...um-support-t3606400/post76619564#post76619564

Where has "keep wifi on during sleep"?
Sadly this isn't working anymore.
The maker of betterbatterystats offers also a tool to accomblish this task and much more:
betterwifionoff
When switching from lineage-14.1 to lineage-15.1 I found idle bat usage doubled: what has been 0.4 % per hour on nougat increased on oreo to 0.8 to 1.0 % per hour.
On n I've always used "only if charging" for "keep wifi on during sleep", but the access to this setting has been vanished by google. So I exprimented with wifi conf file, kernel driver and wakelock blocking on kernel level. Nothing really solved the adsitional idle drain.
I'm still surprised, what I found while searching settings (cli): the setting "wifi_sleep_policy" is still there! Google has just droped the access via Settings->Network&Internet->Wi-Fi and makes "Always" the default , but the setting is still available and is working like on n.
Value: Function
0: Never
1: only when plugged in
2: Always
To get restore my n setting (keep wifi on while sleep only when plugged in), I only need to connect via adb (I prefer adb over network, but it works as well with usb), and issue this command:
Code:
adb shell settings put global wifi_sleep_policy 1
After spending endless hours on kernel and debugging, this simple command brought back 0.4%/h idle bat usage.

How To: format data with f2fs with current official TWRP
Current twrp (3.2.1-0) can't change the data fs to f2fs. The reason for this breakage is, that twrp expects a mkfs.f2fs command that knows "-r size" as cli-option, but the image is shipped with a version that doesn't know about "-r".
To get data formated as f2fs with space for the encryption footer, you just need to follow these simple steps:
Download attached mkfs-f2fs.zip.
Unzip and place the contained mkfs.f2fs in /sdcard/Download.
Boot to current twrp-3.2.1-0.
In twrp:
Home-Screen->Advanced->Terminal
Code:
cp -vi /sdcard/Download/mkfs.f2fs /tmp
chmod 0755 /tmp/mkfs.f2fs
/tmp/mkfs.f2fs -t 0 -r 16384 /dev/block/bootdevice/by-name/userdata #for the lazy, if on op3/t can use /dev/block/sda15
flash rom (or use the installed rom, which is factory reseted by formating data), reboot t system amd encrypt your device.
The mkfs.f2fs binary is taken from the original twrp-3.2.1-0. This will only work for 64-bit devices:
Code:
file mkfs.f2fs
mkfs.f2fs: ELF 64-bit LSB pie executable ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /sbin/linker64, BuildID[md5/uuid]=46b5f32d88973c91f79744258599a19a, stripped

stuff.

UPDATE
Build 20180225
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta03 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
Update GoogleCamera to GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk — Nvertigo
Bring back busybox. — Nvertigo
Switch kernel branch to linux-stable/nlos-15.1. — Nvertigo
Merge tag 'v3.18.96' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!

set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.

With the version from 18th February the setup wizard is working, if you are going for a fresh installation.

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
crian said:
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
Click to expand...
Click to collapse
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).

nvertigo67 said:
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
Click to expand...
Click to collapse
Will this work on op3 too?

Aasresh said:
Will this work on op3 too?
Click to expand...
Click to collapse
Most propably: yes.
I don't have my hands on a 3, and I made it my self a rule to only build and push for devices I have my hands on. That's why I stay in 3t forum though it's essentially an unified build. On the other hand: whenever a setting can be tuned for either for sd820 or sd821, I go for sd821. Other then that, NLOS should work on both models, and I try my best to give you support here.

Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
Nope

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.

OMS service mode
TheGatorade said:
Can't wait for rootless OMS patch
This rom looking good, surprisingly stable for a beta
Click to expand...
Click to collapse
Stay tuned. Need to cleanup the sources and make a clean build.

nvertigo67 said:
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
Click to expand...
Click to collapse
Gotcha. Good to know that plain LOS is just as good with battery life. Thank you

For people having trouble with gapps try flashing the rom then complete the setup wizard then flash gapps.
Worked for me.

UPDATE (OMS Service Mode)
Build 20180226
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta04 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
OMS Service Mode is still work in progress. Sometimes you need to activate a theme once again after "compile&activate". Some themes (i.e. flux - though it's working flawlessly) refuses to deactivate, but flashing /sdcard/substratum/SubstratumRescue.zip removes all activated overlays. Rebooting is sometimes neccessary. Wiping caches and dalvik may be a good idea, too. SwiftDark and Flux seem to work otherwise.
Special thanx to @danieldmm for helping me out of my brainlock with pointing me to https://substratum.review/ . Without his help I would be still searching for commits currently not meeged... ...that would have taken looooong.... *lol*
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
OMS Service Mode: https://substratum.review/#/q/branch:o+(status:merged+OR+status:open) and https://github.com/nvertigo/android_frameworks_base/commit/e5cc87691ea4ba482914adee36821243fe39f7b4
op3: Use exfat-nofuse — dianlujitao
Merge remote-tracking branch 'lneageos/lineage-15.1' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
EDIT:
HOTFIX:
Set sepolicy temporary to permissive, if you want to deactivate an overlay.

Dirty flashed nlos-15.1 20180226 over 20180225 cause some bugs.
Op3T boots but few seconds after the screen becomes black and the phone reboot to recovery.
Revert to 20180225.

[9] GlassROM

This ROM contains dm-verity
This ROM will encrypt your device by default
This ROM will replace your current recovery if you do not disable verity
Please be careful before flashing
We are not responsible for anything that happens to your device, your data, people next to you, people on the opposite side of the earth or anyone, including you for the matter. You are choosing to do these modifications
Only builds with their sha2-512 (newer devices can use sha3-512) hashes uploaded to glassrom-verification are official, stable builds. If a hash is absent from the glassrom-verification page for a file then either the file is corrupt or the file you downloaded was not meant for you. You are requested not to visit the download server and download files that do not have entries in glassrom-verification. Such builds/files is used will not be supported
Glassrom for op3 and 3t
Download links:
Download from glassrom server (no logging) (ipv4 and ipv6):
https://glassrom.pw/op3_glassrom.zip
Download from CDN (see privacy and GDPR notice below) (ipv4 only):
https://cdn.glassrom.pw/op3_glassrom.zip
Build verification: https://github.com/GlassROM/glassrom-verification
Verifying builds: use the build verification link to verify your download. The hashing algorithm is sha2-512. The commit is signed with an x25519 private key. Glassrom is signed with a 2048-bit e3 RSA key with sha2-256 as the hashing algorithm. The glassrom server discloses DANE TLSA records and has certificate transparency, HPKP and CAA and only replies over TLS 1.3 with a secp384r1 private key. The domain supports DNSSEC
Donate to glassrom: https://donorbox.org/glassrom
Note that glassrom is a for-profit company. Donations are not tax exempt
Privacy policy:
Glassrom collects absolutely zero data
Lineageos might collect some data like analytics. Read their privacy policy at the link below
https://lineageos.org/legal/
We use bunnycdn. Read their privacy policy here: https://bunnycdn.com/privacy
https://bunnycdn.com/gdpr
Note that if you access the server with glassrom.pw you bypass bunnycdn and connect to the server directly. If you don't want to use the CDN use https://glassrom.pw which directly connects to the server
Features:
Kernel hardening: selinux compiled in release mode, unsafe configurations turned off, enabled yama with ptrace scope 3, kspp patches applied
A completely clean kernel with no "optimisation" or other nonsense
Tripndroid I/O scheduler is used as the default
Upstreamed kernel to 3.18.140
F2FS backported from the latest 5.2-rc1 release
P gestures and navbar are enabled by default
Substratum exposure support
Aggressive battery optimisation*
Maximum permissible password length is 64 characters instead of 16
Aggressive AOT compilation**
Includes both microg as well as Google apps packages. Full freedom of choice. Signature spoofing is supported. Installing proprietary webviews even when using microg is supported. Open source/self-built webviews need to be put into /system/app for proper functionality. Minimal gapps packages can be flashed as well as opengapps super
Light optimisation. Utmost care has been taken to ensure that optimisation doesn't break anything
Kernel compiled with totally stock GCC and ROM compiled with AOSP clang. No gimmicks
Full resize support for encryption
Support for booting off locked bootloaders
User build signed with release-keys. Release-keys ensure authenticity and security. User build removes a lot of debugging code and enforces stricter and more secure defaults
No dependency on firmware. Flash and run on any firmware
Did we mention that we collect absolutely zero data and have strong data protection policies for any data you willingly agree to submit through us through our support channels
*Agressive battery optimisation shuts down the CPU during doze. Alarm apps and all apps that implement GCM will continue to receive notifications. Implementation is tightly integrated into doze. Whitelisting an app from doze will also whitelist it from agressive battery optimisation. Aggressive battery optimisation never kills or moves apps out of RAM. It can achieve as low as 1% battery drain overnight (as per tests)
**This feature improves performance immediately on first boot. As a consequence the first boot takes 50 minutes however this optimisation seriously improves both performance as well as battery life
Instructions: flash the ROM
Flash anything else that you want
If you want to boot with dm-verity tick "mount system partition read-only" before flashing the ROM and don't flash anything after flashing the ROM
Do not wipe caches. Read this first https://forums.oneplus.com/threads/...-and-battery-calibration-myths-busted.993896/
Bromite webview users should install https://glassrom.pw/bromite.apk
Once bromite system webview is installed go to the "verifying installation" section of the wiki https://github.com/bromite/bromite/wiki/Installing-SystemWebView#verifying-installation
Installing updates:
Dirty flash the build. No need to wipe caches or any other nonsense
Remember to reflash all your mods (including gapps) since backuptool is not present
Update firmware as required. Note that glassrom doesn't enforce firmware requirements
Troubleshooting:
Stuck on oneplus logo: dm-verity failure. Make sure you ticked mount system partition read-only and didn't flash anything after the ROM or use a dm-verity disabler like https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Boots, get stuck on bootanimation then reboots to TWRP
This happens if glassrom fails to reserve space for the crypto footer. Space will be reserved even if you disable encryption. Format data partition (not wipe) using enhanced twrp if this is the case
Doesn't flash with enhanced TWRP:
Use official twrp to flash glassrom and then flash enhanced twrp. Enhanced twrp can only flash new glassrom releases and not the current glassrom release. When upgrading glassrom always update glassrom before updating enhanced twrp
Decryption unsuccessful error:
This can happen if you use F2FS and flash a custom kernel. Glassrom uses the latest F2FS and enables all new F2FS features very quickly. If your custom kernel does not support the same features as glassrom's kernel them you'll run into this error
Remember that data recovery is possible through TWRP
Boots for a long time
This is a feature. First boot can take 50 minutes. If you want to boot faster then don't wipe dalvik-cache in recovery
This has been fixed on newer builds and should no longer be a problem
Overnight battery drain:
Agressive battery optimisation while saves more battery than OOS allows apps to continue running instead of killing them. If you have battery drain it's because of some app and not the ROM's issue
Also I will NOT listen to these bug reports. You are supposed to leave your phone on a charger overnight while it is turned on. If you're not doing what the android system already expects then I can't help you.
TWRP flashing errors:
Error codes are useless. Read the message above the error
Sources: https://github.com/GlassROM
https://github.com/GlassROM-devices
https://github.com/anupritaisno1/proprietary_vendor_oneplus
https://github.com/LineageOS
https://bitbucket.org/anupritaisno1/aarch64-linux-gnu
Flashing instructions: just flash it in your recovery and flash whatever else you flash
For TWRP I recommend enhanced twrp but you can use any TWRP and the result will be the same
If you use enhanced twrp you must use 1 version older than the current release. Whole flashing you must remember to update the twrp after the ROM
Latest OOS firmware needs to be flashed
Unlike other ROMs there is no need at all to wipe cache or clean flash new builds. In fact it is advised not to do so while flashing an update
The following is not allowed when reporting bugs: xposed, custom kernels, anything other than gapps that is installed to the system and magisk
An exception is made for xposed - merely having the framework installed causes no issues. While asking for support only xposed modules need to be disabled. The framework itself can be kept installed
Magisk is strictly forbidden while submitting bug reports. Bug reports made with it installed will be rejected and I won't even read your log. If you have magisk uninstall it and clean flash the ROM before making bug reports
Locking your bootloader:
This is dangerous. Glassrom takes absolutely zero responsibility if you try this
Note: currently the lineageos recovery is not available so there is no way to update glassrom on a locked bootloader. Upgrading glassrom on a locked bootloader will be possible once lineage recovery has been finalised
Flash glassrom and preserve dm-verity
Boot and interrupt the boot process
Boot to recovery. Make sure it has been replaced with glassrom's recovery
Boot to fastboot and issue this command
Code:
fastboot oem lock
Caveats: currently there is no way to format the data partition correctly. This will be fixed once lineage recovery is up
Notes for custom kernel developers:
Note: only custom kernels built by the modding system are officially supported. The requirements for official support are way different than this
If you package a kernel and use a special configuration app glassrom lacks selinux policy to allow the app to read out values. Make sure you ship a proper selinux policy or make sure your configuration app always runs commands as root
Make sure your kernel has the sdfat driver and the configuration options (SDFAT=y SDFAT_USE_FOR_VFAT=y) are enabled or ship your own fstab
Optionally include the tripndroid I/O scheduler or use your own init script to set an I/O scheduler
F2FS MUST at least support inline_dentry and fsync_mode=nobarrier. Backports for 3.18 are available from Google and other parties
To support USB-OTG devices properly make sure (SDFAT_USE_FOR_EXFAT=y)

Can you post screenshots?
and is this an aosp , lineage, caf, oos rom ?

[email protected] said:
Can you post screenshots?
and is this an aosp , lineage, caf, oos rom ?
Click to expand...
Click to collapse
Lineage with OMS
Microg support is present too but you'll have to manually install the microg apps

Glassrom is looking for maintainers, designers, etc
I mean just look at how bad this thread is presented we seriously need people who could lend a hand

Hi guys,
Los based or AOSP bases???

karkiankit said:
Hi guys,
Los based or AOSP bases???
Click to expand...
Click to collapse
Read 2 or 3 above your message. Reading is free

karkiankit said:
Hi guys,
Los based or AOSP bases???
Click to expand...
Click to collapse
LOS is AOSP with some CAF additions
Also it is very difficult to actually differentiate between AOSP and CAF because code of both is present on the branches anyway
AOSP does have CAF code for HALs and CAF does have AOSP code for HALs

confused. tried flashing in my one plus 3 but stuck on 1+ logo

karkiankit said:
confused. tried flashing in my one plus 3 but stuck on 1+ logo
Click to expand...
Click to collapse
Please read the first post

Guys can we have a few testers on discord?
Please join if you're interested in testing

Is SELinux enforcing like in LineageOS?

Master_TC said:
Is SELinux enforcing like in LineageOS?
Click to expand...
Click to collapse
Yes

New build is out
Changes:
December security patch
More optimisation

?????

meprakash_pyc said:
*emoji removed*
Click to expand...
Click to collapse
{
"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"
}

Can somebody provide screen shot!

Updated
Changes:
This update satisfies all new changes in glassrom's charter. No changes that would be easily noticeable to the user

rohitg347 said:
Can somebody provide screen shot!
Click to expand...
Click to collapse
No

Everything is back to normal now

Thread closed by request of OP.

[ROM][UNOFFICIAL][10] LineageOS 17.1 for Amazon Fire HD8 7/6th gen (douglas/giza)

⏱ Change log/ Release notes
2023-05-20 [douglas] [giza]
Restored functionality for early suspend.
Transitioned to a generic variant for the CPU.
Activated GL composition backpressure.
Incorporated support for MicroG (signature spoofing).
Introduced UKSM (Ultra Kernel Samepage Merging).
Fine-tuned MEMCG settings (swappiness) for devices with lower RAM.
Implemented support for dynamic loading of Bluetooth device names.
Made partial fixes to FBE encryption (it's not yet compatible with lockscreen).
Kanged and updated the network stack from Umidigi F2 (aligning it with the most recent HIDLs).
2023-16-02 [douglas] [giza]
Fixed GAPPs installation.
2023-13-02 [douglas] [giza]
Fixed Wi-Fi not connecting to certain routers.
Fixed OOM issues when trying to use some playback apps.
Introduced Ultra Kernek Samepage Merging (UKSM).
Introduced a new HIDL-based lights HAL.
Fixed wrong bootanimation resolution.
Switched to LZ4 ZRAM compression.
Added WireGuard support.
2022-08-09 [douglas] [giza]
Fixed all the sensors (automatic rotation too).
Fixed shutter button in the camera app.
Enabled tablet characteristics/features
2022-08-06 [douglas] [giza]
Added ADB only config (fixes ADB on boot).
Switched to minimal LineageOS configs.
Switched to LZ4 compression for ZRAM.
Disabled vsync for CPU rendered apps.
Introduced and enabled IORap (prefetching).
Switched back to software gatekeeper hidl.
2022-08-04 [douglas] [giza]
Enabled DVFS support.
Switched to HIDL PowerHAL.
Added support for Amazon's dynamic boost impl.
Fixed installation errors on giza.

Reserved

Reserved

Installed just fine, thank you. Can confirm that USB and Wifi are working, as well as security.
Installed open_gapps-arm64-10.0-pico-20220215.zip without a problem, again thanks.
I can also confirm that Magisk works just fine.
Great job as expected, @Rortiz2!

I also installed LOS17.1. Yes, everthing is okay for my usage (don`t play games at all). Only issue I noticed is that battery drain seems like LOS15.1 (no deep sleep). Am I right?
Anyway, it is great have A10 with douglas. Nice job @Rortiz2.

Korin67 said:
I also installed LOS17.1. Yes, everthing is okay for my usage (don`t play games at all). Only issue I noticed is that battery drain seems like LOS15.1 (no deep sleep). Am I right?
Anyway, it is great have A10 with douglas. Nice job @Rortiz2.
Click to expand...
Click to collapse
Yeah, that's correct. I forgot to add that to the buglist, thanks for the reminder.

@Rortiz2 Thanks for your wonderful work! Works perfectly! Feels faster (could be Placebo effect )
I have 2 questions:
1. Is the Multi-tasking split screen broken?
2. (Asking because Searches yielded no result) There's no 'Extend Display' setting in Android 10? (Where one can hide Status Bar and Navigation Bar) Edit: Hidden using ADB

After wiping data, system, and cache, I can't flash the new LOS 17 image. I get the error "E1001: failed to update system image". I have tried to flash it with both adb sideload and through the local storage, and also tried recreating the /cache/recovery folder with nothing changing. My version of TWRP is 3.3.1-0. Device is a 16gb giza.

BrianSamsungTab said:
After wiping data, system, and cache, I can't flash the new LOS 17 image. I get the error "E1001: failed to update system image". I have tried to flash it with both adb sideload and through the local storage, and also tried recreating the /cache/recovery folder with nothing changing. My version of TWRP is 3.3.1-0. Device is a 16gb giza.
Click to expand...
Click to collapse
Can you send me /tmp/recovery.log?

kirik_party said:
@Rortiz2 Thanks for your wonderful work! Works perfectly! Feels faster (could be Placebo effect )
I have 2 questions:
1. Is the Multi-tasking split screen broken?
2. (Asking because Searches yielded no result) There's no 'Extend Display' setting in Android 10? (Where one can hide Status Bar and Navigation Bar) Edit: Hidden using ADB
Click to expand...
Click to collapse
It seems to be working for me?

Rortiz2 said:
Can you send me /tmp/recovery.log?
Click to expand...
Click to collapse
Here you go:
26 KB file on MEGA
mega.nz
(XDA file upload was broken for some reason)

BrianSamsungTab said:
Here you go:
26 KB file on MEGA
mega.nz
(XDA file upload was broken for some reason)
Click to expand...
Click to collapse
Thanks. I messed up the giza partition sizes. I'll upload a new build tomorrow.

Yes, same issue here. Will test as soon as the new build is up. Thanks!

Rortiz2 said:
It seems to be working for me?
Click to expand...
Click to collapse
Its working when using default Trebuchet launcher, but not when using any Custom launcher (tried Lawnchair and Nova launchers). Would you please check?

New build available
2022-08-04 [douglas] [giza]
Enabled DVFS support.
Switched to HIDL PowerHAL.
Added support for Amazon's dynamic boost impl.
Fixed installation errors on giza.
NOTE: OTAs are enabled by default, but I haven't tested them. If you're brave enough, try to update through the built-in updater and let me know if it works.

kirik_party said:
Its working when using default Trebuchet launcher, but not when using any Custom launcher (tried Lawnchair and Nova launchers). Would you please check?
Click to expand...
Click to collapse
It's late here, so I'll try to debug that problem tomorrow.

Rortiz2 said:
New build available
2022-08-04 [douglas] [giza]
Enabled DVFS support.
Switched to HIDL PowerHAL.
Added support for Amazon's dynamic boost impl.
Fixed installation errors on giza.
NOTE: OTAs are enabled by default, but I haven't tested them. If you're brave enough, try to update through the built-in updater and let me know if it works.
Click to expand...
Click to collapse
I tried the OTA, it didn't work through the built in updater. Had to install it manually.

Rortiz2 said:
New build available
2022-08-04 [douglas] [giza]
Enabled DVFS support.
Switched to HIDL PowerHAL.
Added support for Amazon's dynamic boost impl.
Fixed installation errors on giza.
NOTE: OTAs are enabled by default, but I haven't tested them. If you're brave enough, try to update through the built-in updater and let me know if it works.
Click to expand...
Click to collapse
Normal installation works, thank you! I notice it being faster overall compared to 15.1, really nice!

Nimrud7 said:
Normal installation works, thank you! I notice it being faster overall compared to 15.1, really nice!
Click to expand...
Click to collapse
Is camera (photos) working fine there?

Database Info

welcome