Database Develop

[ROM][N5110]Official Nightlies CM11.0[KTU84P][4.4.4]

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
INSTRUCTIONS
First time installing CyanogenMod 11.0 to your Galaxy Note 8 N5110, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM11.0 ZIPs to your SDCard
- Boot into Recovery
- Flash CM11.0 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 11.0:
- Copy CM11.0 ZIP to your SDCard
- Boot into Recovery
- Flash CM11.0 zip from SDCard
- Reboot
BUG LIST
-BT Voice Search
[Nightlies] http://download.cyanogenmod.org/?device=n5110
[GAPPS 4.4] http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
[CWM 6.0.4.4 w/ swipe] Heimdall: http://www.androidfilehost.com/?fid=23212708291675367
OUTDATED:
[11/11] ROM: http://www.androidfilehost.com/?fid=23212708291676598
CHANGES:
-Initial Release
[12/2] ROM: http://www.androidfilehost.com/?fid=23252070760972532
Changes:
- Upstream CM merges (yes home button recent apps is back)
- fixed internal sd / storage
[12/10] ROM: http://www.androidfilehost.com/?fid=23252070760974755
Changes:
- Upstream CM changes (includes fix for rotation distostortion)
Source: http://github.com/CyanogenMod

Yes this is an updated build from the one I posted in the 10.2 thread

A quick pointer to the PA Gapps thread:
http://forum.xda-developers.com/showthread.php?t=2397942
There's a lighter version of the Gapps package there if you don't use so many of the Google services, and it should always have links to up to date versions.
Don't forget to format your system partition and re-flash the whole ROM if you are changing between GApps versions, or you may have some leftovers from the previous version.

Wrong Thread......

testing the 11-11 built. Seems like there is a problem accessing files on the /storage/emulated/legacy (or 0).
Can't delete anything. Can't modify anything... but you can browse... Read Only almost like?

Thanks for quick work !
Code:
set_metadata_recurcive : some changes failed (status 7)
Even with a cwm 6.0.4

I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Edit: what's the difference between pa_gapps-full-4.4-20131111-signed.zip and gapps-kk-20131031.zip?

kingofcomedy said:
I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Click to expand...
Click to collapse
If you have a recovery that work with this build, could you share it here ?
thanks

kingofcomedy said:
I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Edit: what's the difference between pa_gapps-full-4.4-20131111-signed.zip and gapps-kk-20131031.zip?
Click to expand...
Click to collapse
Posted my heimdall in the OP, can you just shoot up a link to your odin copy?
The difference that I've noticed in the 2 are the PA gapps have the "OK google" feature. Maybe they both do but I noticed it after flashing the PA gapps

That's what I just did:
- boot into recovery (rename the attached file to recovery.tar.md5 and flash it with odin) (or download it from here: https://mega.co.nz/#!J18HxR7C!WJMuYhLvpYCPlN-giWs2u0Sr4wRzgBvajTNOP_L5gyU)
- "format /system"
- "format /cache"
- flash cm_n5110-ota-sbrissen_11-11.zip
- flash pa_gapps-full-4.4-20131111-signed.zip
Issues:
- back- and menu-button are not working (sometimes I can close popup-messages with the back-button)
- /storage/emulated/0 not writeable (as already stated by mbze430)
- gallery is not working
- no screenshots
- screen goes a bit crazy during rotations
Edit: I tried to install Root Explorer via the Play Store, but no keyboard showed up. Voice search did work. After I have started Root Explorer and set / to be rw the back- and menu-buttons are working and the keyboard showed up too.

PA GAPP definitely good for ART.. However one of the most important tool "TiBu" doesn't work with ART. That is like the biggest "WTF". lmfao. Seems like ConfigUpdate has been taken out from this new release.
Do we REALLY need torch.apk ? lol
Will the CM team ever accept this as an official? Would love to see nightlys
EDIT1: Almost ****ted in my pants... ExtSdCard is reading empty on the device... but I checked it with a PC... everything is there... so ExtSdCard isn't being read correctly? Also seems like Android 4.4 is dumping all kinds of txt files in the ExtSdCard. It is being recognized as "/mnt/media_rw/sdcard1" in Solid Explorer??
EDIT2: Definitely something is wrong with the partition permissions... Viper4Android no longer can write to the /system partition with 11-11 built.

PdroidAndroid said:
Thanks for quick work !
Code:
set_metadata_recurcive : some changes failed (status 7)
Even with a cwm 6.0.4
Click to expand...
Click to collapse
Hey
I got this same error, what I did was that I flashed the TWRP aroma touch recovery from the XDA thread for GT-N5110 and it worked like a charm!
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2483844

mbze430 said:
PA GAPP definitely good for ART.. However one of the most important tool "TiBu" doesn't work with ART. That is like the biggest "WTF". lmfao. Seems like ConfigUpdate has been taken out from this new release.
Do we REALLY need torch.apk ? lol
Will the CM team ever accept this as an official? Would love to see nightlys
EDIT1: Almost ****ted in my pants... ExtSdCard is reading empty on the device... but I checked it with a PC... everything is there... so ExtSdCard isn't being read correctly? Also seems like Android 4.4 is dumping all kinds of txt files in the ExtSdCard. It is being recognized as "/mnt/media_rw/sdcard1" in Solid Explorer??
EDIT2: Definitely something is wrong with the partition permissions... Viper4Android no longer can write to the /system partition with 11-11 built.
Click to expand...
Click to collapse
Checking the extSdCard issue now. CM just forked my repos last night, I'll start the process to get 10.2 nightlies going. They have not start 11.0 nightlies for any devices yet.

I can also confirm the sdcard not being writable. I'm thinking between that and the extSdCard strangeness perhaps the storage just gets mounted weirdly upon boot.
In addition, it seems to me that long pressing the home button no longer brings up the recent apps drawer.

This version installed without a hitch and aside from the SD card issue, works great!
Also, not that important but Im just curious- why can't I get the launcher looking like kitkat? It still retains jelly bean look even after third party launchers and what not.
Thanks and when the funds allow I'd be glad to donate!

Hi guys! First of all thanks a lot sbrissen for your work!!!! I've been waiting for CM working on my Note8 since I bought it.
Two questions I have:
- When it will be available to download from CM official site.
- Does all the s-pen features work with this build? (by features I mean the quick access, aerial preview, etc)
Thanks again!

titotito1983 said:
Hi guys! First of all thanks a lot sbrissen for your work!!!! I've been waiting for CM working on my Note8 since I bought it.
- Does all the s-pen features work with this build? (by features I mean the quick access, aerial preview, etc)
Thanks again!
Click to expand...
Click to collapse
Simple answer is no. From the way things look, it will never. You will need 3rd party apps to get some of those features back

Keep getting a status 7 error, any help?
Sent from my SPH-L720 using XDA Premium 4 mobile app

Jaimemex said:
Keep getting a status 7 error, any help?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try the TWRP Aroma Touch recovery, it works like a charm and no error occured to me
Sent from my GT-N5110 using XDA Premium 4 mobile app

kinda quiet in here... did everyone jump back to 10.2?? lol

[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia ZR

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 7.x (Nougat),
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​
Downloads Links
LineageOS 14.x (Unlocked Bootloader) :
Nightlies : https://download.lineageos.org/dogo
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Informations and references :
About LineageOS updates : ChangeLog available on http://www.cmxlog.com/14.1/dogo/
About LineageOS device side : See my GitHub trees linked below​
Flashing and updating
LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot​
About the builds
Device tree : https://github.com/fusion3-common/android_device_sony_Dogo/commits/cm-14.1
Kernel sources : https://github.com/fusion3-common/android_kernel_sony_apq8064/commits/cm-14.1
Vendor blobs : https://github.com/fusion3-common/proprietary_vendor_sony/commits/cm-14.1​
Issues and reports
- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example​
About LineageOS Legal : http://lineageos.org/legal/
The LineageOS team would like to thank everyone involved
in helping with testing, cDogog, debugging & documenting! Enjoy!
[/INDENT]
LineageOS available for Dogo also thanks to :
- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing​
XDA:DevDB Information
[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia ZR, ROM for the Sony Xperia ZR
Contributors
Daedroza, AdrianDC, Chippa_a, Olivier, Namelos, CyberwalkmaN, sigprof
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2017-07-17
Last Updated 2017-11-10

Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Fully enforced

Yes! I've been waiting for this. Do I have to use (or does it work with) POC DRM from @munjeni ? Otherwise great work! Any pictures? (Y)

ra1n25 said:
Yes! I've been waiting for this. Do I have to use (or does it work with) POC DRM from @munjeni ? Otherwise great work! Any pictures? (Y)
Click to expand...
Click to collapse
Do I have to use (or does it work with) POC DRM from munjeni?
- I'm not aware of this DRM thing, though I'd preferred if you keep using this without any mods.

what is the difference between this rom and Chippa_a rom?

Daedroza said:
Do I have to use (or does it work with) POC DRM from munjeni?
- I'm not aware of this DRM thing, though I'd preferred if you keep using this without any mods.
Click to expand...
Click to collapse
If you have your TA backed up, then you can re-flash your DRM keys for X-reality(picture enhancement) and other good stuff
Here is @munjeni thread: https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893

Does this rom have oms support and daedroza will love to see more work from you thank you

Folks asking, this is a development thread.
- No custom mods
- No Substratum Support
- Nothing that will create unwanted noise in developing / stabilizing this ROM.
Thanks, use only if you're willing to test and are ready to go outside your comfort zone at the time being.

whenever I have vioce call using facebook messenger, whatsapp, viber I can't use the speaker because the mic doesn't work anymore, strangely I can use speaker in regular phone calls with mic working and everything

rabe3ab said:
whenever I have vioce call using facebook messenger, whatsapp, viber I can't use the speaker because the mic doesn't work anymore, strangely I can use speaker in regular phone calls with mic working and everything
Click to expand...
Click to collapse
Thanks, I will look into this.

Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?
I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.
I've also included a minor hack for auto-brightness. Let me know how you feel about it.
@rabe3ab : Please give it a go? Thanks

Testing and letting you know.
1) USB not getting detected, cleared cache, dalvik twice to see if it's detecting
***It worked after third attempt - might be my ***mistake
2) Sorting in launcher do not sort applications properly (have screen shot)
3) upon screen unlock, infrequently it gets stuck with opaque screen with only back button visible and the it stops responding for 30 seconds then it works
4) reboots infrequently logs attached. It crashes on chrome, SwiftKey etc apps
5) WiFi - shows connected but no packets are sent / received after 1-2 hours, need to either tap to disconnect and then reconnect or needs reboot to get connected to same wifi.

Daedroza said:
@rabe3ab : Please give it a go? Thanks
Click to expand...
Click to collapse
do you recommend clean install?

rabe3ab said:
do you recommend clean install?
Click to expand...
Click to collapse
I always recommend clean install, though dirty flash and wipe dalvik cache works too.

Lλmdα said:
Testing and letting you know.
1) USB not getting detected, cleared cache, dalvik twice to see if it's detecting
***It worked after third attempt - might be my ***mistake
2) Sorting in launcher do not sort applications properly (have screen shot)
3) upon screen unlock, infrequently it gets stuck with opaque screen with only back button visible and the it stops responding for 30 seconds then it works
4) reboots infrequently logs attached. It crashes on chrome, SwiftKey etc apps
5) WiFi - shows connected but no packets are sent / received after 1-2 hours, need to either tap to disconnect and then reconnect or needs reboot to get connected to same wifi.
Click to expand...
Click to collapse
Can you please test the attached zip and tell me? Thanks.

Okay
Daedroza said:
Can you please test the attached zip and tell me? Thanks.
Click to expand...
Click to collapse
Downloaded... Flashing and re-testing..
Keep you folks posted.
Cheers

Logs
Daedroza said:
Can you please test the attached zip and tell me? Thanks.
Click to expand...
Click to collapse
After longs test it crashed while using playamp music player and chrome downing mp3

New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you

Robust!!!
Daedroza said:
New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you
Click to expand...
Click to collapse
Stunning, robust and healthy build!
Thanks for that excellent build!
-Lamda

I' ve decided to give it a go. Thank you @Daedroza. But to be sure that everything goes well, I need little help. Right now i'm on stock 5.1.1 locked bootloader(C5503). Rooted, Xposed and using XZDualRecovery 2.8.26 RELEASE by [NUT]. And my question is: do i NEED to clear my fotakernel before or after unlocking bootloader?( checked from the menu,yes i'm allowed to unlock it). What version TWRP is recommended? Thanks in advance!

[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD: Fixed....
Things that are different from official build:
fixed wrong theme color in screenshots on OP6.
Add support for QCOM haptics vibrator. (fixed vibration)
BUGS:
mtp (causes kernel panics) (can add a test build if needed)
flashing aroma packages
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDAevDB Information
[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]
Contributors
Joemossjr
Dees_Troy
wuxianlin
@notsyncing on github for the fixes
Source Code: Github
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-07-07
Last Updated 2018-08-01
Donation Link: Buy this man a beer

Thanks for this. Add the version that supports MTP. Will test and let you know!

It's definitely bugged lol but I'll add it tomorrow

Thank you very much!

joemossjr said:
It's definitely bugged lol but I'll add it tomorrow
Click to expand...
Click to collapse
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?

Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.

xXx said:
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Click to expand...
Click to collapse
I'll be getting logs tonight while flashing an aroma package to see what's needed lol I feel like it's something simple but we will see. Thanks for the support everyone I do this on my free time lol I'll post the mtp enabled here shortly

mtp has been added to the downloads folder and is specified in the name!

https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned

joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
thanks, very much appreciated :highfive:

joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
Yes I have tested it and can confirm it's working. Just make sure you unmount mtp and remount it before attaching the USB cable (thanks to @DocRambone for the tip)

DocRambone said:
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
Click to expand...
Click to collapse
This works, thanks!

It's not working for me both new versions. Boot looped.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app

mbr007 said:
It's not working for me both new versions. Boot looped.
Click to expand...
Click to collapse
Did you remember to flash magisk after reboot into twrp?

lollyjay said:
Did you remember to flash magisk after reboot into twrp?
Click to expand...
Click to collapse
Yeah you have to flash magisk if you already had it flashed before hand

joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?

Can you add another mirror like androidfilehost please? Unable to access google drive...

xXx said:
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Click to expand...
Click to collapse
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?

adiher said:
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
Click to expand...
Click to collapse
I can make a new build that's higher

joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
Could this have anything to do with why aroma isn't working?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
From the magisk 16.6 change log.
Note to ROM Developers
If you are embedding Magisk Zip into your ROM, and your ROM uses Aroma Installer, please be aware that on some devices (most likely Samsung devices), it is possible that the installation process of Magisk could break Aroma. Please test flashing your ROM zip before releasing to your users. If you found out you are the few unfortunate devices, unzip the Magisk zip, and do the following changes and re-zip the installer:
Code:
# Remove or comment out these 2 lines in META-INF/com/google/android/updater-script eval $BOOTSIGNER -verify < $BOOTIMAGE && BOOTSIGNED=true $BOOTSIGNED && ui_print "- Boot image is signed with AVB 1.0"
The reason why Aroma Installer breaks is unknown. Maybe consider letting the project that's abandoned for nearly 5 years go?

[ROM][12][UNOFFICIAL]LineageOS 19.1[WIP]

Code:
*** Disclamer
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.
Introduction
This is the LineageOS for OnePlus 6t
Click to expand...
Click to collapse
This rom is different from offical lineage by the means it build vendor from source and proprietary blobs instead of reusing oxygenos vendor image.
Monet included.
Installation instructions
1. Install R Stock Rom onto your phone , follow some tutorial you can find in this forum
2. Flash boot.img and dtbo.img by typing fastboot flash boot boot.img and fastboot flash dtbo_a dtbo.img and fastboot flash dtbo_b dtbo.img
3. Wipe your userdata by typing fastboot erase userdata
4. Reboot the phone and immeditly do the recovery key combination
5. In Lineageos recovery select install and then sideload from adb
6. On your computer type adb sideload pathtotheromzip and press enter
7. The rom should now be flashed , flash gapps and other mods like magisk the same way
Click to expand...
Click to collapse
Download
ROM
RECOVERY
Click to expand...
Click to collapse
Changelog
Code:
Current changelog:22.03.2022
[note] 1st Release of LineageOS 19.1
[new] Lineage 19.1 based on Android 12.1
[changed] idk anymore
[fixed] fod now works as intended thanks to the lineageos guys
Older changelogs:
Click to expand...
Click to collapse
Code:
Current changelog:23.11.2021
[note] 2nd Release of LineageOS 19.0
[new] mobile data works again
[changed] fixed mobile data
[fixed] mobile data
Code:
Current changelog:02.11.2021
[note] 1st Release of LineageOS 19.0
[new] sensors work now gapps work now
[changed] included monet theme engine
[fixed] sensors
[/HIDE]
FAQ
What doesnt work ?
you tell me
This rom is for fajita only
For Gapps i recommend NikGapps
Click to expand...
Click to collapse
Thanks To/Credits
Code:
@SGCMarkus
@LuK1337
Sources
Code:
[URL="https://github.com/J0SH1X/android_kernel_oneplus_sdm845"]Kernel[/URL]
[URL="https://github.com/J0SH1X/android_device_oneplus_sdm845-common"]Common[/URL]
[URL="https://github.com/J0SH1X/android_device_oneplus_fajita"]Device[/URL]
[URL="https://github.com/J0SH1X/proprietary_vendor_oneplus"]Vendor[/URL]

Rip Arrow Os

I don't understand why Arrow was dropped in favor of Lineage ? Is there any specific reason to it ?

Hey OP, The ROM link goes to the old Arrow ROM.

Release fajita-20211122 · J0SH1X/Lineage-OTA
host for json response file for supporting ota updates on unoffcial lineageos || EOL FIND ANOTHER IDIOT TO DO YOUR **** - Release fajita-20211122 · J0SH1X/Lineage-OTA
github.com

MrUrgit said:
Hey OP, The ROM link goes to the old Arrow ROM.
Click to expand...
Click to collapse
fixed

Adiker said:
I don't understand why Arrow was dropped in favor of Lineage ? Is there any specific reason to it ?
Click to expand...
Click to collapse
cause lineageos sources now cna be build without too much trouble and i only build lineageos normally

Updated latest build with working audio and bt and mobile data

Just tested latest build both VoLTE and VoWifi works, as for issues - so only FOD is pending

How do I mount the system as rewritable? I'm unable to in root explorer. Thanks for the rom it runs great so far. I have noticed a bug that status bar tuner doesn't open btw

Also, I don't believe that NFC is working correctly. I was unable to pay for gas, NFC kept turning on and off according to Google pay and trying to open the connectivity settings freezes and/or crashes the settings app, which actually happens on my pixels stable Android 12 anyway..lol.

I do have Magisk however all of my backing apps work and safety net is passing

For me dash charger isnt working.Start charging for a sec and then it stops. Quickcharge 3 charger works

Got this from Octobot, it was for PE12 but it works great. Flash this TWRP zip through FK kernel manager and reflash Magisk if you are rooted once TWRP boots. No crashdumps...etc.

Has anyone had luck getting this to work on Verizon. Just installed, and it doesn't detect sim

Is this project still alive? I switched because there were no updates. Probably going to stick with EVO 12 when released tomorrow, unless this is still in the works... I'll have to at least try it

Yeedatoy said:
Is this project still alive? I switched because there were no updates. Probably going to stick with EVO 12 when released tomorrow, unless this is still in the works... I'll have to at least try it
Click to expand...
Click to collapse
I'd assume the community took a break since it's the weekend of Christmas in the US, not sure if that would apply to the dev working on this project or not. I'd just be patient.

Of course. Im not one of those who nags at the guys who put in hard work to provide something for free, nothing irritates me more,lol. It's just been a while since the last release so im curious whether or not I should keep an eye on this thread or if Josh has moved on with something else for a while.

waiting for the stable version on oneplus 6

New Release of Lineageos 19.1
Download

[UNOFFICAL] [RECOVERY] [FBE_V1/V2] OrangeFox Recovery R10.0 / R12.1 for Xperia 1 II

WARNING: THIS IS UNOFFICAL BUILD, USE IT AS YOUR OWN RISK.​
Code:
/*
* Your warranty is now void.
*
* We're 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 recovery
* 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.
*
*/
OrangeFox R12.1 build Support ROMs which using FBE_V2 only, for example: Lineage OS 19.1/20 by @clfbbn.
About FBE_V2, see Google's documents please: https://source.android.com/docs/security/features/encryption/file-based
If you're using ROM with FBE_V1, you should use the recovery which support FBE_V1 to make data decryption works well.
OrangeFox R10.0 build Support ROMs which using FBE_V1 only
for example: Lineage OS 17.1 by @Sjll , sony stock Android 10/11
INSTALLATION:
First, reboot your phone to bootloader and connect your phone with PC.
Then type in your terminal(like CMD, powershell and so on):
Code:
fastboot flash recovery <the-file-name-of-recovery-image>
If you wanna reboot to recovery now, type:
Code:
fastboot reboot recovery
Okay, you can enjoy it imperfect UNOFFICAL recovery now
WORKS:
Decryption (R12.1 build only work on FBE_V2 ROMs, R10.0 build only work on FBE_V1 ROMs)
Fastbootd
Adb sideload
Flash zip file(You can use it flash @clfbbn's Lineage OS).
Touchscreen.
Vibration (It has been fixed on OrangeFox R12.1 230221 builds)
NOT WORKS:
Vibration (Sorry, I am a real noob, ask our pro plus ultra dev bootloopuru who build TWRP without ANY XPERIA device to solve it xD)
Decryption on Sony Xperia Stock Android 12 ROM (I am not sure about the reason: maybe TWRP branch 12.1 only support FBE_V2 decryption for device which using Android 12+ ROM with FBE? )
Some strange layout (I don't want to do anything about it for now, because OrangeFox's UI is not compatible with our 21:9 long screen）
Vibration has been fixed on R12.1 branch after 230221 builds, thanks to @sekaiacg.
Layout has been fixed after 230215 builds, sorry for OrangeFox team, I am noob, I forget to set OF_SCREEN_H values.
I am sorry for my blame and my noob jobs.
OTG (Okay, I will try to fix it if I have enough time.)
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
* clfbbn - for his kernel source
* sekaiacg - for his twrp device tree for umi
* cramfs28 - for his help
* lolipuru - Okay, he got a real Xperia 5 II and fix many issues now, I really thank to him, but I still hate someguy build rom/recovery without devices.
Downloads:
Please download the LATEST build for the branch you need to use (R10.0 or R12.1).
My noob project in sourceforge, flash it as your own risk: https://sourceforge.net/projects/homosenpai/files/Recovery/OrangeFox/
Device Tree:
GitHub - ShirokaneShizuku/twrp_device_sony_sm8250
Contribute to ShirokaneShizuku/twrp_device_sony_sm8250 development by creating an account on GitHub.
github.com
(Actually who care about it lol, The open source community is getting worse, some pro guys even build ROM for the device they don't have, haha)
Bug Report:
Please report it wit log please, and because this is a noob UNOFFICAL build, I can't fix bugs as soon as possible, thanks for your understand.
Donation:
Hey guys,Why would you donate to someone who hasn't contributed to the open source community?

1. Why you keep repeating that this is an UNOFFICAL build？
Because some bad guy thinks my previous releases are pretending to be an official build (actually I put UNOFFICAL tag in the title every time)
2. Hey guys, can you help me compile a ROM or Recovery for a XXX device?
NO, absolutely NOT, I would not do such a thing. All released builds should be rigorously tested by developers, at least to ensure that the basic functions are effective, which is the basic guideline of the open source community.
I'm not an unprincipled and no bottom line guy like lolipuru, if you want bootloop go for that guy, they're good for nothing but messing with the community
3. Hey man why are you so aggressive can you calm down？
Sorry I may seem grumpy, but I can't stand someone taking something from the open source community and doing it badly irresponsibly
4. What can I do if I am using FBE_V1 ROMs ?
Please use OrangeFox-R10.0-Unofficial-pdx203-230217.img.
5. When I use OrangeFox-R10.0 on Android 11 ROMs, I got some error about APEX, what can I do?
I am sorry for that, but please ignore it now, or wait for the OrangeFox 11.0 builds.
6. Why you don't build OrangeFox-R11.0 for Xperia 1 II ?
I am sorry about it, I face some strange issue: like decryption dead or touchscreen not work, I need time to figure out about it, as you see, I am noob here QwQ.
7. Hey, why not you build TWRP bro?
I am tired, I don't wanna sync source again now. If I have enough time, I will build it.

Update Log:
2023-02-15:
Fix strange layout, sorry for OrangeFox Team, I am very sorry for that QwQ
2023-02-17:
Fix strange layout for OrangeFox R10.0 build (which build for FBE_V1) and release it now.
2023-02-21
Fix vibration for OrangeFox R12.1 build, thanks to @sekaiacg and TWRP Teams. (Our device should use QTI AIDL for haptic)

Thanks for making the recovery, and after some update it's became very good. Also waiting for your derpfest update

leomate said:
Thanks for making the recovery, and after some update it's became very good. Also waiting for your derpfest update
Click to expand...
Click to collapse
You're welcome bro, but I will not update derpfest build because I am busy until July this year.
Absolutely I can build it, it only take my PC's 3 hours, but I need to test and debug it (basicly I need to make sure it's bootable), I will not release ANY build that have not been tested.
No matter what, thanks for your appericate

RealNoobKanger said:
You're welcome bro, but I will not update derpfest build because I am busy until July this year.
Absolutely I can build it, it only take my PC's 3 hours, but I need to test and debug it (basicly I need to make sure it's bootable), I will not release ANY build that have not been tested.
No matter what, thanks for your appericate
Click to expand...
Click to collapse
Ahh that's okay. I just feel when this recovery saving me from the hassle. That's what I'm using from my old phone.
As long the ROM stable enough for me (no memory leak like stock rom) its good, and the 3-finger screenshot feature that I'm miss a lot when switch to Xperia phone. It's rare to see a flagship SOC with microSD slot.
Anyway, thanks for once again for the effort making Recovery :3

leomate said:
Ahh that's okay. I just feel when this recovery saving me from the hassle. That's what I'm using from my old phone.
As long the ROM stable enough for me (no memory leak like stock rom) its good, and the 3-finger screenshot feature that I'm miss a lot when switch to Xperia phone. It's rare to see a flagship SOC with microSD slot.
Anyway, thanks for once again for the effort making Recovery :3
Click to expand...
Click to collapse
Vibration should be fixed on 230221 R12.1 build, enjoy it!

Is there no hope for decrypting stock 12? What kind of bullcrap did Sony pull off with it

Xspeed said:
Is there no hope for decrypting stock 12? What kind of bullcrap did Sony pull off with it
Click to expand...
Click to collapse
TWRP's decryption might be work now on Xperia stock Android 12, refer to it:https://github.com/TeamWin/android_bootable_recovery/commit/9ab7cf500595c9809142c3294ca477fcedf7e56d

Looked promising, I compiled the recovery with this new change, but unfortunately still no dice, same errors in logs as before

Xspeed said:
Looked promising, I compiled the recovery with this new change, but unfortunately still no dice, same errors in logs as before
Click to expand...
Click to collapse
Do you change the fstab? Maybe you need to change it to adapt to Stock Android 12

Xspeed said:
Looked promising, I compiled the recovery with this new change, but unfortunately still no dice, same errors in logs as before
Click to expand...
Click to collapse
Do you using Xperia Stock android 12 bro? I am using MIUI for Xperia 1 II now, I don't wanna flash to Stock android 12 again (backup take too many time for me)
If you wanna try to decrypt Stock android 12, you can change the mount flags about data and Metadata, make sure it same with Stock ROM

RealNoobKanger said:
1. Why you keep repeating that this is an UNOFFICAL build？
Because some bad guy thinks my previous releases are pretending to be an official build (actually I put UNOFFICAL tag in the title every time)
2. Hey guys, can you help me compile a ROM or Recovery for a XXX device?
NO, absolutely NOT, I would not do such a thing. All released builds should be rigorously tested by developers, at least to ensure that the basic functions are effective, which is the basic guideline of the open source community.
I'm not an unprincipled and no bottom line guy like lolipuru, if you want bootloop go for that guy, they're good for nothing but messing with the community
3. Hey man why are you so aggressive can you calm down？
Sorry I may seem grumpy, but I can't stand someone taking something from the open source community and doing it badly irresponsibly
4. What can I do if I am using FBE_V1 ROMs ?
Please use OrangeFox-R10.0-Unofficial-pdx203-230217.img.
5. When I use OrangeFox-R10.0 on Android 11 ROMs, I got some error about APEX, what can I do?
I am sorry for that, but please ignore it now, or wait for the OrangeFox 11.0 builds.
6. Why you don't build OrangeFox-R11.0 for Xperia 1 II ?
I am sorry about it, I face some strange issue: like decryption dead or touchscreen not work, I need time to figure out about it, as you see, I am noob here QwQ.
7. Hey, why not you build TWRP bro?
I am tired, I don't wanna sync source again now. If I have enough time, I will build it.
Click to expand...
Click to collapse
我想知道这可不可以在中国版本上使用？
I want to know if this can be used on the Chinese version?

I have sony xperia 1 ii au version. I have unlocked bootloader and downloaded europe rom from sony xperfirm and installed it now I’m getting no sim card emergency only. How to solve this please help me