[OTA] [10.0] [MONTHLY] CarbonROM CR8.0 PAX [OFFICIAL] [STABLE] - Xiaomi Redmi Note 4 [Snapdragon] ROMs, Kernels, Re

{
"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"
}
ABOUT:
CarbonROM is an aftermarket firmware based on the Android Open Source Project created with the purpose of adding versatility and customization to stock Android. Stability is our highest priority; our vision is to be the best alternative to a stock operating system for your device.
WHAT'S WORKING:
- All core features:
- Hotspot
- IR blaster
- Reading mode
- GPS (locks in 2 minutes)
- Goodix fingrprint (needs another verification)
- VoLTE
- LTE (speed reaches 50 MB/s)
- Agressive battery modes ( 3 versions - idle, standby, battery saver)
- umatched stability and INSANE battery life - second to none
- clean, lean and efficient
KNOWN ISSUES
- Nothing found
- You can report to this email address
SELinux Status Enforcing
SCREENSHOTS
CLEAN FLASH RECOMMENDED
Back Up Everything.
Use Orangefox Recovery. Link
Wipe Dalvik/ART cache, Cache, System, Data.
Flash ROM
Flash Gapps. (FlameGapps Recommended)
To update the ROM, you can use two methods - OTA or Dirty Flash. OTA is recommended.
DOWNLOAD:
CARBON CR8 RELEASES - MIDO
TEAM WEBPAGE: CarbonROM
TELEGRAM: CarbonROM
Support the efforts of the team: Donate
Version Information
ROM OS Version: Android 10.0.0
ROM Kernel: Linux 3.18 - KERNEL Repository
Status: Stable
Stable Release Date: 2021-04-20

Finally published on XDA, a very good ROM, I use it on a daily basis,screen 9+ hours, the speed is at the level of PE 9 CAF, who needs lightweight ROM, with the latest security patches, and without bugs, I can recommend Carbon

Solid ROM. I chose it thanks to the Kill option in the Recents task switcher.
Note that unlike LineageOS, CarbonROM doesn't come with a built-in firewall since contemporary android (last year or so) lets you use rootless firewalls via vpn redirects. Personally I've rooted and used afwall regardless since I need root for adaway.
Mi Remote works fine in case you're wondering. You don't need to allow any permissions and can even firewall it after "pairing" your TVs and it will still work.
One question/caveat: How do I enable lock screen rotation?
~ Redmi Note 4X 64GB

xdaluser0 said:
Solid ROM. I chose it thanks to the Kill option in the Recents task switcher.
Note that unlike LineageOS, CarbonROM doesn't come with a built-in firewall since contemporary android (last year or so) lets you use rootless firewalls via vpn redirects. Personally I've rooted and used afwall regardless since I need root for adaway.
Mi Remote works fine in case you're wondering. You don't need to allow any permissions and can even firewall it after "pairing" your TVs and it will still work.
One question/caveat: How do I enable lock screen rotation?
~ Redmi Note 4X 64GB
Click to expand...
Click to collapse
To be honest, I do not really know if this is possible.
The lock screen normally shuts down most of the censors.
If you are sure that the accelerometer is active when the screen is locked, it has to be researched.
Otherwise, you would need TYPE_MAGNETIC_FIELD and TYPE_ACCELEROMETER to adjust the settings.
I, personally, don't think it is possible.

Per5on said:
To be honest, I do not really know if this is possible.
The lock screen normally shuts down most of the censors.
If you are sure that the accelerometer is active when the screen is locked, it has to be researched.
Otherwise, you would need TYPE_MAGNETIC_FIELD and TYPE_ACCELEROMETER to adjust the settings.
I, personally, don't think it is possible.
Click to expand...
Click to collapse
Thanks for replying. I'm asking because it's fairly common in other ROMs so I assumed the setting was buried somewhere in the menus. I even looked it up over the github repos ( https://github.com/search?q=org:CarbonROM+lock+screen+rotation&type=commits ) and found multiple commits suggesting it's an existing feature: https://github.com/CarbonROM/android_frameworks_base/commit/afc54cf30f9c3adb4038dc3363cf47bbefc01564
sdm660-common: overlay: enable lock screen rotation · CarbonROM/[email protected]
Contribute to CarbonROM/android_device_xiaomi_sdm660-common development by creating an account on GitHub.
github.com
Sensors wise, I think that's the sleep mode that cutoffs those circuits rather than the lock screen itself so once the display turns back on the sensors are back on as well. But that's just me making guesses really.

Ok I managed to get the lockscreen rotating but it isn't easy. Basically you need to add a line to build.props using magisk's MagiskHide Props Config module. So, from the terminal after installing and rebooting you su and run props which is a menu driven terminal script. You add a new one (I think it was no.4 in the menu? follow the on-screen instructions...) called lockscreen.rot_override and give it the value true. Then let props initiate the reboot and you're done.
TL;DR lockscreen.rot_override=true in build.props
Anyhow, would have been nicer to have it as a CarbonFiber but so long as it works, I'm not complaining Thanks.

Another day another odd bug / missing feature: It's likely at least two-three separate su (magisk) and missing permissions possibly related to the new Android privacy polices, but Automation / Easer / Automate / LibreTasks can't use the wifi as a trigger due to missing permissions. E.g. previously I'd use LineageOS's System Profiles to turn off mobile data when my home wifi was connected but now nothing can list the wifi networks (related permissions maybe?) or switch off mobile data (su / magisk root elevation by the service probably needs work on the app dev's side) but third party tools are all broken for various reasons.
Anyhow, It's probably not ROM related but since LineageOS circumvents the issue by providing their own, I think it's still a valid point of comparison especially for people that consider event driven automation as necessary. Personally I guess I'll just try and remember to turn it on/off.
p.s. Links of what I've tested not to work:
Automate - Apps on Google Play
Automate almost any task on your device
play.google.com
Easer | F-Droid - Free and Open Source Android App Repository
Event-driven Android automation
f-droid.org
Automation | F-Droid - Free and Open Source Android App Repository
Automate stuff on your device by creating rules.
f-droid.org
LibreTasks | F-Droid - Free and Open Source Android App Repository
Trigger actions when certain events happen
f-droid.org

xdaluser0 said:
Another day another odd bug / missing feature: It's likely at least two-three separate su (magisk) and missing permissions possibly related to the new Android privacy polices, but Automation / Easer / Automate / LibreTasks can't use the wifi as a trigger due to missing permissions. E.g. previously I'd use LineageOS's System Profiles to turn off mobile data when my home wifi was connected but now nothing can list the wifi networks (related permissions maybe?) or switch off mobile data (su / magisk root elevation by the service probably needs work on the app dev's side) but third party tools are all broken for various reasons.
Anyhow, It's probably not ROM related but since LineageOS circumvents the issue by providing their own, I think it's still a valid point of comparison especially for people that consider event driven automation as necessary. Personally I guess I'll just try and remember to turn it on/off.
p.s. Links of what I've tested not to work:
Automate - Apps on Google Play
Automate almost any task on your device
play.google.com
Easer | F-Droid - Free and Open Source Android App Repository
Event-driven Android automation
f-droid.org
Automation | F-Droid - Free and Open Source Android App Repository
Automate stuff on your device by creating rules.
f-droid.org
LibreTasks | F-Droid - Free and Open Source Android App Repository
Trigger actions when certain events happen
f-droid.org
Click to expand...
Click to collapse
If you want to inform the team, you can use the email address in the description.
As to automation, normally when you have both LTE and Wi-Fi connected, the connection is set to sign in to the closest cell, irreleveant of the technology used. The distance marks ping times, strength of signal, velocity but even when it connects, you still have the both sensors active (which drains battery). Currently, I don't think there is a way to automatically shut down one of them, or both of them, if this is what you mean.
In terms of selection of the network, it has always worked. In terms of dozing the sensors after a certain time of inactivity, I cannot help you.
Hopefully, this is useful.

Per5on said:
If you want to inform the team, you can use the email address in the description.
Click to expand...
Click to collapse
Nah it looks like the automation stuff is being shifted into the assistant APIs and SDKs and most projects and foss just hasn't caught up with the changing permissions and such: https://www.xda-developers.com/android-10-rules-automation-feature-rolls-out-some-pixel-devices/
Per5on said:
Currently, I don't think there is a way to automatically shut down one of them, or both of them, if this is what you mean.
Click to expand...
Click to collapse
I guess google wants their machine learning to do this automatically for users instead of the users having to go into the settings and script logic.
Anyhow, I'm sure things will sort themselves out with time so no worries.
Offtopic, for some reason Axet's Call Recorder didn't work for me even after giving it root so I had to use the magisk module that installs it as a system app. It's sorta weird since android.permission.CAPTURE_AUDIO_OUTPUT should have been granted as I checked "System Mixer Incall Recording" and approved it for superuser but it didn't. I even thought something went wrong with magisk itself but adaway and afwall test fine so...
Anyhow, thought it's worth mentioning since I keep running into similar premission related issues and some of them are common enough that people already have apps to solve/circumvent them.

Changelog - 20/04/2021​

Hello!
I've switched to this ROM because android 11 and kernel 4.9 was not stable for me, with all kind of slowness and issues.
I'm glad to see an up-to-date android 10 rom. The performance is just insane compared with the other rom's i've tested.
But I do experience a bug with wireless. When my phone is connected to a 2.4ghz wifi AP, the performance is really low, below 4mbps with high jitter, even with the signal at 100%. If I connect to the 5ghz band, the performance is perfect, above 115mbps.
How can I help you with troubleshooting this? Unfortunately this is a massive problem for me. Changing wifi channels and 20 or 40mhz bandwidth makes no difference at all.

TigTex said:
Hello!
I've switched to this ROM because android 11 and kernel 4.9 was not stable for me, with all kind of slowness and issues.
I'm glad to see an up-to-date android 10 rom. The performance is just insane compared with the other rom's i've tested.
But I do experience a bug with wireless. When my phone is connected to a 2.4ghz wifi AP, the performance is really low, below 4mbps with high jitter, even with the signal at 100%. If I connect to the 5ghz band, the performance is perfect, above 115mbps.
How can I help you with troubleshooting this? Unfortunately this is a massive problem for me. Changing wifi channels and 20 or 40mhz bandwidth makes no difference at all.
Click to expand...
Click to collapse
Hi!
First, I have none of your issues and have no information on anyone else experiencing it.
If you connect to 2,4 Ghz, the range is longer and wider, which means the strength and velocity is somewhat disturbed by the distance from the router or the AP, but ensures longer distance. Drops are fewer than in the 5 GHz.
If you use 5 Ghz, it is much more stable but the distance is shorter and the channel is narrow, which leads to easy disturbance of the connection.
If you use the Hotspot for someone close to you (not far than 5-7 metres) use the 5 GHz.
Changing the bandwidth of the channel might improve something but rather not.
If you have any other questions, do not hesitate.

Thank you for your answer but unfortunately I do experience this problem with this ROM and not with others
I'm aware how wifi networks works but where I'm mostly using my device, I don't have 5ghz available.
I need proper 2.4ghz stability because I use ms teams on my device for home office.
This problem is not present with other android 10 roms with kernel 3.18 like lineage os.
Let me know if you need logcats or anything

Per5on said:
View attachment 5265955
ABOUT:
CarbonROM is an aftermarket firmware based on the Android Open Source Project created with the purpose of adding versatility and customization to stock Android. Stability is our highest priority; our vision is to be the best alternative to a stock operating system for your device.
WHAT'S WORKING:
- All core features:
- Hotspot
- IR blaster
- Reading mode
- GPS (locks in 2 minutes)
- Goodix fingrprint (needs another verification)
- VoLTE
- LTE (speed reaches 50 MB/s)
- Agressive battery modes ( 3 versions - idle, standby, battery saver)
- umatched stability and INSANE battery life - second to none
- clean, lean and efficient
KNOWN ISSUES
- Nothing found
- You can report to this email address
SELinux Status Enforcing
SCREENSHOTS
View attachment 5265947View attachment 5265953
CLEAN FLASH RECOMMENDED
Back Up Everything.
Use Organefox Recovery. Link
Wipe Dalvik/ART cache, Cache, System, Data.
Flash ROM
Flash Gapps. (NikGapps Basic Recommended)
To update the ROM, you can use two methods - OTA or Dirty Flash. OTA is recommended.
DOWNLOAD:
CARBON CR8 RELEASES - MIDO
TEAM WEBPAGE: CarbonROM
TELEGRAM: CarbonROM
Support the efforts of the team: Donate
Version Information
ROM OS Version: Android 10.0.0
ROM Kernel: Linux 3.18 - KERNEL Repository
Status: Stable
Stable Release Date: 2021-04-20
Click to expand...
Click to collapse
This looks like a good rom. I will test it on my device.

TigTex said:
o Thank you for your answer but unfortunately I do experience this problem with this ROM and not with others
I'm aware how wifi networks works but where I'm mostly using my device, I don't have 5ghz available.
I need proper 2.4ghz stability because I use ms teams on my device for home office.
This problem is not present with other android 10 roms with kernel 3.18 like lineage os.
Let me know if you need logcats or anything
Click to expand...
Click to collapse
Ok, send them to me. I will take a look when I have some time to do so.
No promises.

I found the problem it's bluetooth.
I have a mi band that is always connected to my device. Just by having bluetooth enabled, I can't have more than 4mbps. Disabling it, I can use wifi happily at 70mbps.
Is there a bluetooth coexistence mode that can be tweaked?

TigTex said:
I found the problem it's bluetooth.
I have a mi band that is always connected to my device. Just by having bluetooth enabled, I can't have more than 4mbps. Disabling it, I can use wifi happily at 70mbps.
Is there a bluetooth coexistence mode that can be tweaked?
Click to expand...
Click to collapse
They are on the same chip
Check here

I'm aware of it. But like I said, this was a non-issue with miui and LOS17.1.
Perhaps there's a tweak on WCNSS_qcom_cfg.ini that can be done? Or maybe los17.1 uses different blobs? You could try to push zeelogs 17.1 kernel to cr-8.0.
These are just ideas, not complaints

TigTex said:
I'm aware of it. But like I said, this was a non-issue with miui and LOS17.1.
Perhaps there's a tweak on WCNSS_qcom_cfg.ini that can be done? Or maybe los17.1 uses different blobs? You could try to push zeelogs 17.1 kernel to cr-8.0.
These are just ideas, not complaints
Click to expand...
Click to collapse
Good suggestions!
you can send them to the email address in the description

Great rom!!! Very stable in my 3/32 mido. Good battery backup so far.
A bug I found - google assistant is not working and it's showing 'not available in this device'.. Is there any way to fix it??

Related

[8.1.x][OFFICIAL][RELEASE] CarbonROM | cr-6.1 [z3c]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3 Compact
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-04-01
Last Updated 2018-07-19
Wow thats good. Thank you very much.
Hi, Myself5! Thanks a lot that you still support our device though you have newer devices.
User experiences and issue list for 2019-03-11 Release
First of all, thanks to @Myself5, @rcstar6696 and all other members of the CarbonROM team for the release of CarbonROM 6.1 Oreo for our device! :good::victory:
User experiences with CarbonROM 6.1:
Installation was smooth. I flashed cr-6.1 and OpenGapps ARM 8.1 on top of my working cr-5.1 installation (dirty flash), so all of my apps and their settings were kept. MindTheGapps 8.1.0 arm, which are recommended by the Carbon devs, are also working fine. Keep in mind that there is no guarantee that a dirty flash works in all cases, so you might have to wipe your data partition. This generally is recommended when updating to a new Android version anyway.
Besides of some small issues (see below), everything runs stable and the system is snappy and smooth. Thermal management and charging speed is fine.
Magisk 16.0 works fine, as well as Xposed Framework (SDK 27) v90-beta3 or alternatively Systemless Xposed (SDK 27) v90.1-beta3 Magisk module. However, there are some force-closes of background apps every now and then, caused by the beta status of Xposed v90.
My Xperia Torch Boost Magisk module is still working well on cr-6.1.
Selinux is set to enforcing, just as it was in cr-5.1.
I found out that Android Messages SMS/MMS app has a high battery drain, which e.g. is also reported for Pixel devices on Android 8 Oreo, so a general bug by Google. Because of this, I switched to Textra SMS (of course you can also use one of the other SMS/MMS apps around), which fixes the battery drain.
Improvements in comparison to cr-5.1:
The camera button now acts exactly like in Sony Stock ROMs, so now focussing and taking pictures is possible with Stock Sony Camera. You can also invoke the Stock Sony Camera by long-pressing the camera button, just like in Stock ROMs, but this doesn't work when the device is off or locked. In this case you can use a double press on the power button, which can be enabled in Carbon Fibers settings.
Booting the device is noticably faster than on cr-5.1.
Lower battery drain than on cr-5.1.
Better, more uniform design.
The ROM is being updated to the latest Android Security Patches.
Apps can be "locked" in the Recent Apps, so when pressing the Clean All button, they keep running.
4K video recordings are possible.
Missing features in comparison to cr-5.1:
There is no option to turn on Network Traffic Indicators yet. (This has been added in 2018-04-05 Weekly.)
Default Camera-App does not allow to save photos to sd-card, puts photos in wrong orientation and is all around very limited. However, there are good alternatives like Open Camera and the Stock Sony Camera. (Since 2018-05-01 Weekly, Snap Camera is used again.)
Issues in Carbon ROM 6.1:
Video recording doesn't work yet with the built-in Camera app, as well as with several other apps like Open Camera and the Stock Sony Camera. Until this is fixed, you can use Footej Camera for video recording as a workaround. (This has been fixed in 2018-05-08 Weekly by @AdrianDC and Milos Ratkovic.)
DoubleTap2Wake isn't working yet. (This has been fixed in 2018-04-11 Weekly.)
The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. (See @Myself5's reply in post #14.)
The gyroscope doesn't work properly yet with certain apps, e.g. Vr Tester - Gyroscope Sensor App and Accelerometer Gyro Tester. (Obviously this is a bug of those apps or of Oreo in general, since @Myself5 could reproduce it on his Pixel 2 XL device, running on stock ROM. Many other apps that use the gyroscope are working fine on cr-6.1.)
Saving and accessing files on SD card doesn't work for certain apps and tools, which could be a Linux permission or SELinux denial issue. For further information and partial workarounds, see post #45, post #49 and post #51. (This has been fixed in 2018-06-05 Weekly.)
Screen Cast still isn't working for me with 2018-04-11 Weekly (I tested this with a Sony and an LG Smart TV which both connected fine to my Z3c on stock ROMs), even with the new boot image from post #103 which is working with @Myself5's Fire TV stick and Wireless Display Adapter. This has been fixed in 2018-04-17 Weekly.
WiFi isn't working on 5 GHz band in some countries, as has been reported in post #1634 on the Z2 cr-6.1 thread, including links to posts with possible workarounds and fixes. There's also an article in the xda wiki with further information. Since 2018-05-01 Weekly, Germany (DE) is used as Wifi country code, but there have been several reports by users from other countries that this doesn't work for them, so is not an universal fix. As a workaround, until this is fixed, you can use my Magisk module from post #195, which you have to change to your own country code by following the instructions that I gave there. Edit: @marcogiannetta posted an improved Magisk module in post #373 which changes the Wifi Country Code accordingly to the system language. A similar issue (wifi dosent connect in Iran) also has been reported on the bug tracker and is being looked after by the devs. Edit: According to post #2092 on the Z2 thread, this issue can also be fixed by installing WiFi regional problem solver Xposed module.
Music files can't be played from SD card with Vanilla Music, Sony Music and several other players. This issue was fixed in 2018-05-08 Nightly, but reappeared on 2018-05-15 Nightly. Until this is fixed again, you can use jetAudio HD Music Player as a workaround. (This has quickly been fixed again in the 20180515-2340 Weekly build.)
When making a screenshot via the Power menu, most of the time the Power menu itself is visible in the screenshot. There should be a slight delay (just 1/10th second might already be sufficient), so the Power menu is already hidden again before the screenshot is taken. This has been fixed in 2018-07-05 Weekly.
Apps like Netflix, MyCanal and MagineTV don't work because DRM WideVine is not supported yet, whereas in CarbonROM 5.1 it was supported. This has been fixed in 2018-08-15 Release.
Lock screen rotation has been removed since 2018-09-11 Release. It was a useful feature when using the phone in landscape orientation e.g. in a car holder and IMO should be added again. Edit1: As a workaround, I made LockscreenRotationEnabler Magisk module which adds this functionality by adding a setting to 'build.prop'. Edit2: Lock screen rotation can also be enabled with GravityBox [O] Xposed module.
NFC extended length isn't supported, which is needed e.g. for reading identity cards with apps like AusweisApp2. (This has been fixed in 2019-03-11 Release.)
NFC-HCE isn't supported, which is needed for Google Pay. (This has been fixed in 2019-03-11 Release.)
Wish list for some further improvement of Carbon ROM 6.1:
Long press camera button to wake and launch camera app when the screen is off or the phone is locked. Edit: I found a workaround which I described in this post.
A toggle to switch to dark UI theme for quick settings. Edit1: The dark UI theme can be forced with ForceDarkModeOreo Xposed module. Edit2: ForceDarkModeOreo unfortunately is one of the Xposed module which cause random app crashes, so it's not advisable to use it. Let's hope that the devs will add this feature eventually.
About time this one got its own thread, huh
Everything works great, no bugs so far and no problem with camera recording (using Footej Camera), though missing hardware key rebindings and i cant enable power notifications
Downloading right now. Lets see how it compares to Omni 8.1
EDIT (my comment from a few pages later):
After a few days with it, I can say it's already suitable for daily use. Using MindTheGapps (tho I will switch to OpenGapps pico, I don't want Google app ), Magisk 16.
It's smooth and very stable. No crashes or major issues for me so far.
Battery life is acceptable, worse than stock (doh), and perhaps even LOS 14.1. Thermal management and charging speed is fine.
No idea about the camera, mine is broken (HW) and I never use front one.
A few suggestions and comments:
Add some power balancing options like with LOS (better performance or battery life).
Also, I love how you can customize RGB values on LOS to make it more yellowish even during day, plus night light. Any idea what workaround I could use? My blueish screen is killing me and I can't use night light all day.
Good to hear night mode is being worked on.
How to make quick tiles menu like on 7.x? I preferred auto expanding options for mobile data and silent mode. Can't find it in fibers.
Hi, Great that development is ongoing - Thanks a lot!
One thing, got the same problem with the none carbon Oreo Version:
got problems with whatsapp. Video isn't running. The phone doesn't build up a connection. Chat works, but whatssap call or video not.
Skype ist working without problems ...
Any Ideas?
I installed it with a full wipe - system, cache, dalvik, data, internal storage. Used TWRP 3.2 for ROM (to mind error 7) and TWRP 3.1 for installation of MindTheGApps.
Thanks for help!
Thanks for the ROM, working great for me.
I have accidently deleted live wallpaper picker. Tried download a few different versions from the internet but nothing works. Where can I get the one this ROM is using?
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Nice post, okij
okij said:
[*]The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. Also, forcing dark theme via Dark Tricks Xposed module doesn't work.
Click to expand...
Click to collapse
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Kocane said:
Nice post, okij
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Click to expand...
Click to collapse
Doesn't substratum work?
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
Substratum works fine
Greets ted!
okij said:
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Click to expand...
Click to collapse
For things like Networks indicator: Some additional features will surely come with time, as you said.
Video recording: I think it was the Z3 thread where I explained it in detail: The commits to fix Video recording do work (kind of), but are WIP, so we're all working on getting them stable and polished, then they will be merged as fast as possible. When that happens is rough to estimate, I wouldnt expect it to take much longer than 2-3 Weeks though.
DT2W: As you said. Fixed and merged, will be included in the Next Weekly.
For the Dark Theme: Isn't that a Pixel only feature? For that to work you'd need assets for a "dark theme". On Pixel devices those are on the /vendor partition, so obviously not present on our Z3C. Correct me if I'm wrong please.
Thanks for the detailed report, will gladly keep on checking it with followup builds.
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
It does. Install the Substratum app and flip the switch in CarbonFibers -> Privacy to make it work.
The Switch is disabling the Security measures Google merged in the March ASBs. By default Subs completely removes them, but we decided to go for an opt-in for those that want to use it while keeping the "security" Google intended to have with merging it for those that don't want to.
First off all, thank u for this amazing work! Rom is awesome.
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
2 - Someone can tell me if led notification works? Not work here...
Sorry bad English...
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Any idea anyone?
Thanks!
marlontravagli said:
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
Click to expand...
Click to collapse
Yes, this is a great additional feature when using DT2W and one of the reasons that I use GravityBox. @Myself5: It would be great if you could implement this feature for those of us who don't use Xposed. In GravityBox it can be found under "Power tweaks -> Proximity wake up" and the additional option "Ignore for incoming call" which is also worth implementing.
2 - Someone can tell me if led notification works? Not work here...
Click to expand...
Click to collapse
I can confirm that LED notifications are working here, just tested this with missed call (using Google Dialer) and incoming email (using AquaMail).
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Laus_bub said:
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Click to expand...
Click to collapse
I don't use WhatsApp, but I guess that the not working video call has to do with the not fully working video recording (see #1 in the issues list I posted here).
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
ElLoloFR said:
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
Click to expand...
Click to collapse
Did you try removing all other modules? For me the very same thing is happening if I try to use the fbind (Folder Bind) module. You can try to remove all modules, if u use the Magisk Manager for Recovery Mode (mm).
I tried and :
"No magisk installation found."
So I installed Magisk v16, then installed this one.
I could install mm, this was the only module installed.
I uninstalled mm, rebooted without uninstalling Magisk V16, and the phone booted !
But I can't open Magisk Manager v5.6.4, stucked in the app logo...So Magisk seems to be installed, but I can't use it :/
EDIT : Well, after a recovery reboot, reinstall f magisk V16, phone boot correctly and Magisk is alive.
I don't know how this is working, but it's working.
No doubt, you helped me, many thanks

[ROM][64BIT][8.1] UNOFFICIAL LineageOS 15.1 for LG STYLO 2 PLUS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Video Playback
Audio
Sensors
GPS
FingerPrint
tap 2 wake
Known issues:
Volte
you tell me!
Follow Instructions Carefully otherwise you will get error :
Use this 64 bit twrp to flash http://www.mediafire.com/file/i1911qqxlx9v6sm/twrp-3.2-x64-ph2n.zip
Wipe cache, dalvic cache,system,data
Flash ROM-Flash Gapps [Arm64-8.1]
Done-Reboot Now
Enjoy the clean rom
Downloads :
https://www.mediafire.com/download/t9b8g097ihhu7b4
Credits:
Lineage Team
Please Consider donating if you appreciate my work
https://paypal.me/messi2050
Sources:
Device:
https://github.com/messi2050/android_device_lge_ph2n
https://github.com/messi2050/android_device_lge_msm8937-common
Kernel:
https://github.com/messi2050/android_kernel_lge_msm8937
XDA:DevDB Information
[ROM][64BIT][8.1] UNOFFICIAL LineageOS 15.1 for LG STYLO 2 PLUS, ROM for the LG Stylo 2 Plus
Contributors
messi2050
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Nougat bootloader
Version Information
Status: Abandoned
Created 2018-05-03
Last Updated 2019-05-09
Reserved
2018-june-13 build changelog:
-June security patch
-Update power scripts from last caf
-Fix vendor mismatch error message
-enable dual wifi bands
-build using last sources
Thanks for the ROM, messi, it's greatly appreciated even if development stops cold after the post you just made.
And for those that might care, the MD5 of the archive is: 00dd56ee08963da05195915dd528d9b1

			
				
The headphone audio output on this ROM is rather weak, but that's not messi's fault, it's because of how Oreo is working on this device. There appears to be no mixer_paths.xml file in Oreo now, and I added the older mixer_paths.xml (with permissions 0644 as required) with the necessary adjustments to boost the audio output from the default of 84 to 92. It had zero effect so it seems the audio subsystem in Oreo is now working differently for whatever reason, not sure if there's a way to adjust the defaults at all.
Also, the kernel for this ROM appears to be defaults to just 6 core operation: I've installed the ROM twice now on my S2P and when I check the core activity with CPU-Z it always shows 2 little cores active, 2 offline (always), and all 4 big cores active. And of course the minimum CPU speeds are 960 for the little cores and 768 for the big cores - they should be (or at least I should say they could be set in the kernel parameters down to the minimum of 384 MHz and that would save a bit of battery life.
Overall it's been great so far, really, everything seems to work fine. The flashlight didn't work so I installed a flashlight app then suddenly the toggle started working so, there's something funky going on there but everything else so far has been great. Would be nice if there was a more customized kernel available, yes, with more governors and perhaps even some undervolting potential but I know this device just doesn't have much developer love at all.
Regardless, it's very cool to be able to run Oreo 8.1 now since I have never really given a damn about it at all previously. I may go back to running the stock T-Mobile 20a rooted ROM on my S2P however, it depends on how things work out.
:good:
br0adband said:
The headphone audio output on this ROM is rather weak, but that's not messi's fault, it's because of how Oreo is working on this device. There appears to be no mixer_paths.xml file in Oreo now, and I added the older mixer_paths.xml (with permissions 0644 as required) with the necessary adjustments to boost the audio output from the default of 84 to 92. It had zero effect so it seems the audio subsystem in Oreo is now working differently for whatever reason, not sure if there's a way to adjust the defaults at all.
Also, the kernel for this ROM appears to be defaults to just 6 core operation: I've installed the ROM twice now on my S2P and when I check the core activity with CPU-Z it always shows 2 little cores active, 2 offline (always), and all 4 big cores active. And of course the minimum CPU speeds are 960 for the little cores and 768 for the big cores - they should be (or at least I should say they could be set in the kernel parameters down to the minimum of 384 MHz and that would save a bit of battery life.
Overall it's been great so far, really, everything seems to work fine. The flashlight didn't work so I installed a flashlight app then suddenly the toggle started working so, there's something funky going on there but everything else so far has been great. Would be nice if there was a more customized kernel available, yes, with more governors and perhaps even some undervolting potential but I know this device just doesn't have much developer love at all.
Regardless, it's very cool to be able to run Oreo 8.1 now since I have never really given a damn about it at all previously. I may go back to running the stock T-Mobile 20a rooted ROM on my S2P however, it depends on how things work out.
:good:
Click to expand...
Click to collapse
Mixer is moved to vendor/etc in o
messi2050 said:
Mixer is moved to vendor/etc in o
Click to expand...
Click to collapse
Geezus, I spent an hour looking for that information on multiple forums and websites and you're the first person to point out where it is, damn.
Thank you, thank you, thank you. Adjusted the default path name="headphones" from 75 to 90 and w00t, much much better now.
messi2050 said:
Mixer is moved to vendor/etc in o
Click to expand...
Click to collapse
I want to ask a question. This Custom ROM support the LG Stylus 2 Plus K520TR model?
There are two issues I've noticed, can't say they will, would, or do affect other people and I'm using the MetroPCS model with T-Mobile (I was using the T-Mobile stock ROM originally).
- the Mobile Hotspot does not function. It says it's working in the Settings submenu but the actual hotspot never does function, it never shows up as a visible AP for another device to connect to, the SSID is not broadcast, etc
- the USB options when you plug in a USB cable will not stick, I've got into the Developer Options and I have it set to always MTP and every single time I plug in I have to go manually change it from charging to MTP to get it working
They're not massively important things but for me the Mobile Hotspot could be useful for my Wife when we're out and about; her Flex 2 doesn't have cellular service so in the past she'd just tether to my Stylo but now that's not possible.
Not sure this can even be resolved given the nature of the usage but it would be nice to have those two nitpicks working properly. Aside from that this ROM so far has been spectacular: I'm getting 7+ hours of SOT at 50% brightness, with cellular and Wi-Fi enabled constantly, and using L Speed to handle background performance.
So far so good.
I am getting a vendor ID error every time I restart the phone. T-Mobile version stylo. Clean install followed to a T. I also noticed some games aren't working either like they cannot community ate with the server mainly Paladins strike that game also starts with an error.
I'll try to screenshot the error and write it down as well as the vendor id it says I need to match
Did a full reflash and the vendor id error persists. Also not sure if its because of that but most of the apps and games I try to play are giving me network errors and not downloading the content. I can download from the app store no problem but its within the app that problems with network start. My APN is correct as well.
Wondering if I missed a nougate update that is causing the vendor id error.
rsuthers08 said:
Did a full reflash and the vendor id error persists. Also not sure if its because of that but most of the apps and games I try to play are giving me network errors and not downloading the content. I can download from the app store no problem but its within the app that problems with network start. My APN is correct as well.
Wondering if I missed a nougate update that is causing the vendor id error.
Click to expand...
Click to collapse
I believe the vendor id is used to pass safetynet easier. Expected behavior
Anything going on with this rom?
rsuthers08 said:
Anything going on with this rom?
Click to expand...
Click to collapse
@messi2050 said he was done with this phone and I haven't heard anything from him since, so no. @deadman96385 @Travisholt92 @xRaZeR_FuZioNx and @cospalet are all working on roms still. If you wanna talk to them and see what their plans are, we have a telegram group, but you'll have to find it yourself
Ya I'm not looking to pay for nightlies of an unfinished rom
The ROM works, the only thing that doesn't for me is the hotspot but that's a given anyway and nothing can really be done with it.
Only thing I wish we had at this point is a custom kernel to get the idle speeds down from the current ones of 960/768, they should be 384/384 and it would help with battery life (which is fine even in spite of this current limitation). Maybe some more governors would be nice too but so far I've been running this ROM since it was put out and haven't had a single thing to legitimately complain about unlike others it seems.
Use it, don't use it, but for Pete's Sake® STFU about it and messi, will ya?
I just got my computer up with 14.04.5 TT and set up my build envir. I just need the time. I cant leave my computer set up at home right now and thats where i have the best connection. Its my first time so i intend to do a couple dry runs first, maybe play around with the kernel. But i never have to time to get rling with it
Google lens
I can't believe it but Google Lens actually works on this ROM. I haven't done a lot of testing but so far so good.
---------- Post added at 06:08 AM ---------- Previous post was at 05:42 AM ----------
I can't believe it but Google Lens actually works on this ROM. I haven't done a lot of testing but so far so good.
Edit, I haven't found anything not working.
rsuthers08 said:
I am getting a vendor ID error every time I restart the phone. T-Mobile version stylo. Clean install followed to a T. I also noticed some games aren't working either like they cannot community ate with the server mainly Paladins strike that game also starts with an error.
I'll try to screenshot the error and write it down as well as the vendor id it says I need to match
Click to expand...
Click to collapse
Did you ever find a fix for the mismatching vendor.img? I feel dumb bit its been years since i've fiddled with android internals. They've change quite a bit since lollipop lol
lixer8 said:
Edit, I haven't found anything not working.
Click to expand...
Click to collapse
So, for you, if you have cellular service, can you test out the hotspot functionality and let me know if you're successful with getting it to work? It's the only thing that doesn't work for me, so I switched back to the 7.1.1 ROM where it works just fine. I'd love to continue using the 8.1 ROM but without that hotspot it's a problem.

[ROM][8.1][UNOFFICIAL] non-gsi AICP-mordiford [clover/Mi Pad 4]

[ROM][8.1][UNOFFICIAL] non-gsi AICP-mordiford [clover /Mi Pad 4(PLUS)]
This is the rom created by lindwurm . All thanks and respects for working with this ROM are due to him.
Wiki : https://wiki.maud.io/aicp/oreo
Sources : https://github.com/lindwurm
ROM download : https://cloud.akane.blue/nextcloud/s/PbGugWPefp9fFNZ?path=/clover
More info on his blog : https://blog.maud.io/entry/2018/12/13/mi-pad-4/ https://blog.maud.io/
"It seems that burning Generic System Image (GSI) was mainstream until a while ago,
but GSI did not deal with notice LEDs, covers with magnets etc,
recently it only finally released Xiaomi kernel source , I decided to build it
for AICP-mordiford support myself, for example because MoKee 81.0 was released
and maintainers released the source . ROM is common to 8 inch version and 10 inch version (Plus).
Since we started publishing while waiting for Unlock, we have already received reports
of problems and defects from some users. Because there was a change on the side of MoKee,
there might be something like this, so it was saved. "
I tried to contact lindwurm without success . The information about this project is very hard to detect , because it does not exist in english language. I decided to create this thread as the information of existence this ROM exclusive for Mi Pad 4/Mi Pad 4 Plus. It is the best custom rom for this device because it is created by owner of this hardware. It includes fixes for hardware specific problems not existed on other devices . Because the roots of AICP are LOS , this ROM has many (maybe all) features good known in LOS .
I am using this ROM for a month on my Mi Pad 4 (WiFi only) and I am yet to find any bugs. Great job from Hota and the team.
about AICP-mordiford
Tomek0000 said:
I tried to contact lindwurm without success . The information about this project is very hard to detect , because it does not exist in english language. I decided to create this thread as the information of existence this ROM exclusive for Mi Pad 4/Mi Pad 4 Plus.
Click to expand...
Click to collapse
Sorry for not responding sooner.
NOTE:
We are NOT an offcial build/project of Android Ice Cold Project (AICP).
It's my UNOFFICIAL / individual fork to improve Japanese translation and add some changes.
Please do NOT report our ROM-related bugs or issue to AICP Official community.
INFORMATION:
test on my Mi Pad 4 (3GB/32GB, wifi, 8inch). other version (4GB RAM | LTE | 10inch) may work, reports are welcome.
our SlimOTA is available. Open AICP Extras -> Update center.
And we recommend you enable "Automatic update interval", because it will notify you when new tested-release is coming. (maybe monthly)
Upload runs every build is complete, not tested. Wait OTA notification is more safe/recommended.
TESTED HARDWARE-SPECIFIC FEATURE:
magnetic cover (tested with Official SmartCase). can sleep/wake.
DT2W with 8".
Screen rotation.
aptX™ Audio.
Screenshots(aptX):
{
"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"
}
Click to expand...
Click to collapse
I CAN'T KNOW ABOUT THESE (TELL ME IT WORK OR NOT):
FingerPrint sensor on Mi Pad 4 Plus(10")
some user said DT2W didn't work with Mi Pad 4 Plus(?)
LTE
KNOWN ISSUE:
SELinux: Permissive
We recommend you take a backup of /persist before flash it first time. (GUIDE: https://forum.xda-developers.com/mi-pad-4-plus/how-to/guide-mi-pad-4-plus-lineageos-15-1-t3893264 )
THANKS:
AICP
GuaiYiHu - 95% based on his work
AndroPlus - AICP-mordiford GSI author, and donated me mi pad 4
Pie info : read #22
@1indwurm
thank you for a responce. When you will release next build, could you public release notes? It will be nice, but the rom seems to be finished and bug free. I am not able to report any problems. I have to check if lte modem and gps working, when I will cut my micro gsm card.
I read about problem with battery leaks by lte applications (LOS) in wifi only model. I have lte models only , but maybe someone else will write if this problem exists or not.
It is interesting, I used gsi aicp previously and I have problem with autorotation after some time of use. Your non-gsi seems to not have this problem.
Pie - nice to read it. Personally I will use Oreo as long as we will have working version of xposed for Pie.
Today I tested my mi pad 4 lte in antutu bench. The result was 90000 in last release of this rom (L Speed set to battery optimalisation).
Edit.
Balanced=142713
Tomek0000 said:
@1indwurm
thank you for a responce. When you will release next build, could you public release notes? It will be nice, but the rom seems to be finished and bug free. I am not able to report any problems. I have to check if lte modem and gps working, when I will cut my micro gsm card.
I read about problem with battery leaks by lte applications (LOS) in wifi only model. I have lte models only , but maybe someone else will write if this problem exists or not.
It is interesting, I used gsi aicp previously and I have problem with autorotation after some time of use. Your non-gsi seems to not have this problem.
Pie - nice to read it. Personally I will use Oreo as long as we will have working version of xposed for Pie.
Today I tested my mi pad 4 lte in antutu bench. The result was 90000 in last release of this rom (L Speed set to battery optimalisation).
Click to expand...
Click to collapse
How long does the table stay in standby mode with this rom ? It seem's that other roms suffer from standby mode not working properly.
Tomek0000 said:
Today I tested my mi pad 4 lte in antutu bench. The result was 90000 in last release of this rom (L Speed set to battery optimalisation).
Click to expand...
Click to collapse
At "balanced" it should be about 140k.
Tomek0000 said:
[MENTION=6024671]
I have to check if lte modem and gps working, when I will cut my micro gsm card.
Click to expand...
Click to collapse
I have a card for use in new tablet. It does not work. My gsm operator does not use B20 at all, this can not be a problem. I am able to list possible to use operators , I select mine and I have information it is not avialable . The APN I have defined ok. Is it a problem of this rom ? Is someone using LTE without problem ? ( I tried with WiFi enabled and disabled and firewall disabled )
leitoo0 said:
How long does the table stay in standby mode with this rom ? It seem's that other roms suffer from standby mode not working properly.
Click to expand...
Click to collapse
I do not know. I am using my own otimalisations for keeping standby over month . It works for me on all of my android devices .
Tomek0000 said:
I do not know. I am using my own otimalisations for keeping standby over month . It works for me on all of my android devices .
Click to expand...
Click to collapse
Can you give me some advice over how you optimize it? I would love to keep mine from getting buggy after awhile.
What to do?
1. I use automagic for automate interfaces managing.
I turn off wifi and mobile data on smartfons and wifi and gsm modem on tablets in the script. Additional IT turns off nfc, bluetooth... on every lcd lock. Turn it on, on lcd unlock and use only wifi if it is available.
2. L Speed lets me use device with battery optimalisation.
3. Use Greenify for restricted hibernation all not needed apps. You have to use it with xposed. (My email I synchronize manual in script after network back. If you see app was stopped change hibernation in it from normal to not deep.)
4. Wakelock Detector will monitor for detect problematic apps and hibernate it in Greenify. It worked for me some time in mordiford and stopped. Today I use BetterBattery for it.
5. Use AppOps or os build-in functions to set privilages for your apps. Cut auto start with system an do not let system sleep for all apps you know they do not need it.
6. If something autostarted after cut this privilage, uninstall it or use MyAndroidTolls[Xposed] for fight wit it without uninstall.
7. Use Netguard or other firewall for cut intertnet for apps like flashlight... which do not need it.
8. I suggest to use too the XPrivacyLua if yor privacy has any value. If you disable access to some info, you will be able to limit some activity too.
Like you see, you can do everything if you have root and xposed. I am sorry, but android pie(9) is useless today.
Edit.
I measured power consumption by mi pad 4.
1. Stand by : 14 mA
2. wifi off, lte off : 230 mA
3. wifi on, lte off: 250-350 mA
4. wifi off, lte on: 240 mA
5. wifi on, lte on: 290 mA
6. wifi on, lte off, youtube: 410 mA
7. wifi off, lte on, youtube: 420 mA
8. wifi on, lte on, youtube: 420 mA
It looks like normal use of the tablet consumes a lot of power. It does not look good. It is bad.
Tomek0000 said:
I have a card for use in new tablet. It does not work.
Click to expand...
Click to collapse
This is proffesional provider Plus with contract card and big limit. Pad 4 is not able to register to it's network.
I cut my old card to nano size. It is semi professional provider Aero2 and card is free with free internet with small limit. This card works at once without any problem. I have had to change prefered network type from global to lte/wcdma.
Does this rom have read/write speed slow problem. Is it better than mokee or MiUi rom?
Andoid bench test with latest:
NisseGurra said:
Andoid bench test with latest:
Click to expand...
Click to collapse
that's weird, I only got these score, I don't use any modification and the tablet seem pretty laggy now. I'll try to clean flash the rom again.
I have very good battery life on the aicp_clover_o-13.1-mordiford-20181220 on my mipad4:
12 h SOT in 2 weeks standby. Best ever on my mipad. Good work!
A new build is available.
New build is up, and ...
aicp_clover_o-13.1-mordiford-20190129_043407 is up.
CHANGELOG:
System: Bump Security Patch Level to 2019-01-05.
device/kernel: nothing new.
Notes, information, tested features, known issues: read post #3.
Other information: see Our Wiki.
Tasting a piece of pie... ?
We're working on Pie, and we "rebrand" it to FlokoROM. It is our fork of AICP-p, basically our works are same as mordiford...
screenshot:
^^
will update be pushed via OTA soon or I have to install it manually?
banesi said:
^^
will update be pushed via OTA soon or I have to install it manually?
Click to expand...
Click to collapse
sorry for late, OTA is out now
Thanks, I am now receiving notification but after clicking it SlimOTA windows open again and nothing happens. No download is starting, please check screenshots.

[ROM][UNOFFICIAL][13][N7100][Samsung Galaxy Note 2][LineageOS 20.0][ALPHA]

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version of LineageOS 20.0 for our Samsung Galaxy Note 2 (3G).
At first I want to thank @rINanDO, @ChronoMonochrome for all your work on these devices!
This is an alpha version, it's not finished from the LineageOS side and also not from mine.
Most of the LineageOS specific features are missing or not working yet,
please do not report bugs.
Attention:
As it looks like does the device stuck at the "Samsung Note II" screen when you boot out of TWRP,
simply touch the screen with your fingers and it will move on...
I try to find out whats going on there
If you wan't to enable the back gesture for gesture navigation, do the following:
adb shell
setprop toggle_navbar true
You can do the same to disable it.
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
NFC
Encryption
BT audio in a phone call
Network monitoring because of missing eBPF
Maybe random reboots
Spoiler: Links
TWRP
ROM direct link
ROM Android-Filehost
ROM Mega
Spoiler: Changelog
29.09.2022
17.10.2022
26.01.2023
10.03.2023
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N7100][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive
Version Information
Status: Alpha
Created 2022-09-23
Last Updated 2023-03-10
*reserved
Thank you 6405.
Please keep up the good work.
Let me try it out will come up with reviews
Just downloaded the ROM.
The new themed icons seems to work for some apps.
The battery icon on the notification bar seems broken. You can't change the style or percentage.
Languages per app screen shows no apps.
I will share my real experience after testing some more.
It seems like you forgot to upload this ROM on Adroid-Filehost.
<accidentally double post removed>
Great job. Thanks for implementation. But I can't find the device/kernel/vendor sources in you github repros. Only device for LOS18.1
Update 29.09.2022:
Fixed GPS
Tried to fix surfaceflinger crash, let's test if it worked
It's Good
Unfortunately it isn't very good at all!
Not suitable as a daily driver yet!
Even the experimental LineageOS 19.1 GO builds here much more stable.
After some weeks of trying this ROM, I like to share my experience.
I started from a clean install / clean flash.
As usual, I really appreciate that you enhance the privacy and security with your degoogled Roms.
I know this is a based on a beta release of LineageOS and this ROM is in alpha release, but I like to help you improving this ROM.
Here is a list of things that are not working or are not working as intended:
Spoiler
- A lot of random reboots. Worst part, after the reboot ,WIFI won't work. You need to reboot the device manually again in order to fix this which is a huge waste of time.
The reboots mostly happens while browsing with the Brave browser or while typing long messages. I use OpenBoard as keyboard.
- A lot of (FC) force closes while opening some apps.
I can even barely use F-droid! Session and is even as good as unusable on this ROM!
Some apps like NewPipe are usable for a while, but suddenly closes for no particular reason.
Started from a clean slate, so all apps were clean installed as well.
- Very long startup times (Samsung Galaxy Note logo, not the LineageOs splashscreen)
- One day, I could no longer use my device.
When the device was booted, a message was displayed about factory reset and it will reboot automatically. After rebooting, the same message was shown again. The only option was to format the device using TWPR an flash everything over.
Fortunately, this happened only once, but that's a big problem that shouldn't happen again!
- After previous problem I decided to give encryption a try sine I got nothing to loose after all. Encryption still doesn't work!
- 5Ghz WIFI networks don't work. It's not a router problem because I can connect other devices just fine.
Problems occurs on our corporate network and my home network as well.
- Sometimes, the screen starts flickering black on pages with some more graphical intensive tasks, such as websites with embedded video's on it. I only could trigger this in the Brave browser and Firefox Focus.
- Colour correction mode won't work and isn't even available in settings. This prevent the blue light filter from working when it's late or dark. (orange tint).
- The battery icon is broken. You can't see the battery percentage.
Even if you enable circular and percentage in icon, the battery icon won't change.
- Display settings are not saved after a reboot. (example, go to settings>display and change the icon shape to squirqle and choose a custom font. After a reboot, the icon shapes will be circles again and custom font is default font.
Besides all the negative stuff, I also have some positive feedback as well.
I was really surprised (in a positive way) to see the Aurora Store was preinstalled.
This saves me some time downloading/installing it after a clean slate.
Receiving Android 13 on this device before same brand new Galaxy A devices was already a big surprise on its own.
Some nice to gets to make the ROM even more better:
Spoiler
- Make encryption work
- Completely degoogle LineageOS to protect our privacy even more. This will saves me some time after eery update of your ROM.
I referring to removing/replacing Google's DNS (default DNS is 8.8.8.8), Removing or replacing Google's SUPL (A-GPS).
Preferable better privacy respecting DNS:
Quad9: 9.9.9.9 149.112.112.112
Cloudflare: 1.1.1.1 1.0.0.1
Adguard DNS: 94.140.14.14 94.140.15.15
Here is a blog that can help you to understand the privacy problems and how to solve them:
https://www.reddit.com/r/degoogle/comments/cldohl
My goal is not to "tweak" or making any "cool mods " to your ROM.
My goal is to make it more privacy friendly by default for people who doesn't choose to flash MicroG or GAPPS.
- Remove the VIA browser or replace it with something more privacy respecting.
After a clean install, deleting it with ADB is often one of my first steps.
Bromite, Fennec or even Brave are some better alternatives.
- Optionally, you can replace the default AOSP system webviewer with Bromite as well.
- Optionally, a preinstalled F-Droid would be nice as well.
My apologies for the overload of information.
As usual, I like to help making this ROM as good as your previous ROMs or even better!
I hope my feedback is could be useful.
wiijordends said:
Unfortunately it isn't very good at all!
Not suitable as a daily driver yet!
Even the experimental LineageOS 19.1 GO builds here much more stable.
After some weeks of trying this ROM, I like to share my experience.
I started from a clean install / clean flash.
As usual, I really appreciate that you enhance the privacy and security with your degoogled Roms.
I know this is a based on a beta release of LineageOS and this ROM is in alpha release, but I like to help you improving this ROM.
Here is a list of things that are not working or are not working as intended:
Spoiler
- A lot of random reboots. Worst part, after the reboot ,WIFI won't work. You need to reboot the device manually again in order to fix this which is a huge waste of time.
The reboots mostly happens while browsing with the Brave browser or while typing long messages. I use OpenBoard as keyboard.
- A lot of (FC) force closes while opening some apps.
I can even barely use F-droid! Session and is even as good as unusable on this ROM!
Some apps like NewPipe are usable for a while, but suddenly closes for no particular reason.
Started from a clean slate, so all apps were clean installed as well.
- Very long startup times (Samsung Galaxy Note logo, not the LineageOs splashscreen)
- One day, I could no longer use my device.
When the device was booted, a message was displayed about factory reset and it will reboot automatically. After rebooting, the same message was shown again. The only option was to format the device using TWPR an flash everything over.
Fortunately, this happened only once, but that's a big problem that shouldn't happen again!
- After previous problem I decided to give encryption a try sine I got nothing to loose after all. Encryption still doesn't work!
- 5Ghz WIFI networks don't work. It's not a router problem because I can connect other devices just fine.
Problems occurs on our corporate network and my home network as well.
- Sometimes, the screen starts flickering black on pages with some more graphical intensive tasks, such as websites with embedded video's on it. I only could trigger this in the Brave browser and Firefox Focus.
- Colour correction mode won't work and isn't even available in settings. This prevent the blue light filter from working when it's late or dark. (orange tint).
- The battery icon is broken. You can't see the battery percentage.
Even if you enable circular and percentage in icon, the battery icon won't change.
- Display settings are not saved after a reboot. (example, go to settings>display and change the icon shape to squirqle and choose a custom font. After a reboot, the icon shapes will be circles again and custom font is default font.
Besides all the negative stuff, I also have some positive feedback as well.
I was really surprised (in a positive way) to see the Aurora Store was preinstalled.
This saves me some time downloading/installing it after a clean slate.
Receiving Android 13 on this device before same brand new Galaxy A devices was already a big surprise on its own.
Some nice to gets to make the ROM even more better:
Spoiler
- Make encryption work
- Completely degoogle LineageOS to protect our privacy even more. This will saves me some time after eery update of your ROM.
I referring to removing/replacing Google's DNS (default DNS is 8.8.8.8), Removing or replacing Google's SUPL (A-GPS).
Preferable better privacy respecting DNS:
Quad9: 9.9.9.9 149.112.112.112
Cloudflare: 1.1.1.1 1.0.0.1
Adguard DNS: 94.140.14.14 94.140.15.15
Here is a blog that can help you to understand the privacy problems and how to solve them:
https://www.reddit.com/r/degoogle/comments/cldohl
My goal is not to "tweak" or making any "cool mods " to your ROM.
My goal is to make it more privacy friendly by default for people who doesn't choose to flash MicroG or GAPPS.
- Remove the VIA browser or replace it with something more privacy respecting.
After a clean install, deleting it with ADB is often one of my first steps.
Bromite, Fennec or even Brave are some better alternatives.
- Optionally, you can replace the default AOSP system webviewer with Bromite as well.
- Optionally, a preinstalled F-Droid would be nice as well.
My apologies for the overload of information.
As usual, I like to help making this ROM as good as your previous ROMs or even better!
I hope my feedback is could be useful.
Click to expand...
Click to collapse
yes you're right. But fren: Android 13 on an ancient device (more than 10 years old). And at the end: it works!
Of course not very stable, maybe as you said android 12 (ever made by html64) is better, but also android 9 by comicox works fine.
In my case: i really can't use n2 as a primary or secondary smartphone. N7100 hasn't 4g, in my country is not more usable outside your home. So i want to se what is his limit. Even if there more crash and restart. no problem for me
There is a problem with the alarm clock. After opening the clock and then alarms that have been set in the clock app I only see a grey area for a set alarm. It is just a grey box without any text. Only after I click on the entry I see the details of the alarm.
PS: Any chance you could indicate in the file names what version(alpha, beta, final) it is from your point of view? May be an _alpha, _beta_, _final at the end of the archive file? Thx again for all the hard work!
Update 17.10.2022:
Fixed tethering
Synced with LineageOS sources
Fixed most missing / broken features
Fixed hang on boot screen
Updated gps.conf for A13
Update 18.10.2022:
Fixed crash when uninstalling any app
Hello my friend,
It looks like you've been working hard, I'm glad to hear you've made progress on Lineage20's development. I hope you can solve all the bugs so that we have a very stable version to use in our daily lives.
I'm looking forward to the release for the Note 10.1 tablets.
But I understand that there is still a lot of work ahead.
But here's my respect for your work.
lineageos 20 on my device crashes when i unplug the charger it turns off when i plug it back in it comes back on
Tranvy2022 said:
lineageos 20 on my device crashes when i unplug the charger it turns off when i plug it back in it comes back on
Click to expand...
Click to collapse
Hmm strange, just tried it again on my device, it behaves correct, stops charging and wakes up, are you using a n7100 or a different model number?
I really don't see any problem here.
Hi
I try to pit a custom rom tó my gt n7100 16 gb.
The rom is ok, its work fine, bút i cant install google apps őackage, always runt to error 70 in trwp, not enough disk space. The phone has got 8-10 gb free space . What is the problem?
html6405 said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version of LineageOS 20.0 for our Samsung Galaxy Note 2 (3G).
At first I want to thank @rINanDO, @ChronoMonochrome for all your work on these devices!
This is an alpha version, it's not finished from the LineageOS side and also not from mine.
Most of the LineageOS specific features are missing or not working yet,
please do not report bugs.
Attention:
As it looks like does the device stuck at the "Samsung Note II" screen when you boot out of TWRP,
simply touch the screen with your fingers and it will move on...
I try to find out whats going on there
If you wan't to enable the back gesture for gesture navigation, do the following:
adb shell
setprop toggle_navbar true
You can do the same to disable it.
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
NFC
Encryption
BT audio in a phone call
Network monitoring because of missing eBPF
Maybe random reboots
Spoiler: Links
TWRP
ROM Android-Filehost
ROM Mega
Spoiler: Changelog
29.09.2022
17.10.2022
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /vendor/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N7100][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive
Version Information
Status: Alpha
Created 2022-09-23
Last Updated 2022-10-17
Click to expand...
Click to collapse
Say what ? Did I miss this ? Big Up HTML !!!!!
stefannn said:
What is the problem?
Click to expand...
Click to collapse
The problem ist the free space of the system partition,
I've never tested gapps on this ROM and will not recommend them.
But if you wan't to install them you maybe have to expand the system partition before (with parted).
Or try to find a smaller package.

Development [ROM][13.0][SAFETYNET][OPTIMIZED] LineageOS 20 for Motorola Edge 30

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 13.x (T),​which is designed to increase performance and reliability over stock Android for your device.​​All the source code for LineageOS is available in the LineageOS GitHub repo.​And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.​​Official LineageOS website : http://lineageos.org​
About Optimizations
Android Runtime
Disable debugging related features
Compile with D8 optimizations
Adjust watchdog timeout
Android Bionic
Sort host cache in-memory for performance
Switch to jemalloc memory allocator
msmset and pthread related changes
Android Build
Compile with ARMv8-2a-dotprod optimizations
Compile with O3
Compile with lse+fp16
Don't compress resources and assets
Use dexpropt speed
Increase heap size and use aapt2
... and sqlite, zlib related optimizations
Android Recovery
Allow installation of unverified zips i.e the most functional change ever
Android FWB
Reduce blur intensity to ease CPU/GPU
3 finger screenshot support (Please check under Gestures)
Added related missing permissions
SurfaceFlinger related optimizations
View/Layout optimizations
Android Telephony
Latest prebuilt APN from Stock
Updated CarrierConfigs from CAF
Additional cherry-picked IMS related fixes
Android System
Safetynet fixes
Improved Magisk evasion fixes
Disabling data for all connection interfaces and not just mobile data
Additional alarms and ringtones
Dialer
Allow auto-call recording as per country laws
UI changes
DocumentsUI
Start with Internal Storage instead of Downloads
Gallery2
Start with albums activity
Trebuchet
Allow double tap to sleep on homescreen
Updater
Allow local update feature
About Issues
MotoCamera's night mode doesn't work correctly (same as LineageOS), replaced by Aperture, use GCam if needed. MotCamera4 fixed thanks to Marc
NR only mode (5G only mode) works with Jio only. For using 5G on other ISP, use NR/LTE or any other bands, during heavy network traffic, it switches to 5G and fallbacks to 4G during power save automatically
Downloads Links
LineageOS 20.x (Unlocked Bootloader) :​Link : https://drive.google.com/drive/folders/1wXGs7pitUvOCETdCHjVsvpVD3iilbiNl?usp=share_link​​Google Applications :​Not required (has inbuilt minimal set of Google Applications including SetupWizard)​​Flashing and updating​LineageOS clean install :​- (Optional) Flash the boot.img recovery from the ROM zip with Fastboot​- (Optional) Wipe the data & cache (Backup to make sure not to loose data)​- Flash the LineageOS ROM zip from the Recovery​- Reboot to recovery again​- (Optional) Every additional zip you want to flash like Magisk​- Reboot to system​​LineageOS Update using "Local Update" feature :​- You need to be on an existing ROM developed by me​- Download the ZIP from download link above and storage in local storage (example Downloads folder)​- Go to Settings -> System -> Updater​- Click 3-dot buttons and select Local update​- Select the zip using File Manager​- Let it update (takes some time)​- Reboot​​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​- Make sure you also tell the ROM version you're using​
XDA:DevDB Information
[ROM][13.0][OPTIMIZED] LineageOS 20 for Moto Edge 30
Contributors
Daedroza, Albert
Source Code: https://github.com/daedroza
ROM OS Version: 13.x Android T
ROM Kernel: Linux 5.4.x
Version Information
Status: Stable
Created 2023-01-26
Last Updated 2023-01-26
Changelog (You can use updater to update from local storage)
Android 13 Blobs + Android 13
June 25, 2023
Sync with June security patches
Added MotCamera4
Added Android 13 blobs
Updated system wide ad block hosts
Android 12 Blobs + Android 13
May 15, 2023
Sync with May security patches
Added Dolby support
Minimal ad block (system-wide, all apps)
April 18, 2023
Sync with April security pathces
Even more aggressive battery optimizations
Wifi optimizations (2.4GHz bonding)
More fluidity at 60HZ
March 27, 2023
Hot-fix for 5G Networks
Enabled 5G by default if supported
Enabled 5G Voice over Network (VoNR)
March 25, 2023
Sync with March security patches
Aggressive inline optimization using LTO
Aggressive sleep optimizations
Respect restricted apps
Platform fixes for GMS package
Fixed a bug where Android Studio's debugger didn't connect (for developers)
February 19, 2023
Complete fix for SafetyNet
February 13, 2023
Synced with February security patches
More SQLite optimizations and updates
Reverted to Lineage's UDFPS implementation
Use Aperture instead of MotCamera4 (crashes with face beauty and night mode...)
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
rjawan said:
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
Click to expand...
Click to collapse
Thanks for your response!
I've picked "most" of the patches across different ROMs but there might be one or two missing. For time being, you can use Magisk and Zygisk to hide your relevant apps.
For me, using Magisk + Zygisk Hide on Google Play Store gave certified status which is good enough for me. At the moment, I am using ProtonAOSP's related patches (mostly with exception for others) for SafetyNet from Android 12 but it seems Android 13 is bit different. I will take a look into it however I am sure you can get it done easily using Magisk + Zygisk combo for time being.
EDIT: Magisk fixed. Please use builds after 18th February!
is any of these improvements suppose to improve longevity of battery? (except lowering blur, that i can understand ) wondering if this build is for me over default LOS.
possible to see build without google stuff included?
alekksander said:
is any of these improvements suppose to improve longevity of battery? (except lowering blur, that i can understand ) wondering if this build is for me over default LOS.
possible to see build without google stuff inincluded
Click to expand...
Click to collapse
From a non developer's perspective, ROM is quite smooth. Most layers of the code are optimised. There are some functional changes like able to install unsigned packages in recovery which official Lineage doesn't allow.
For battery life, I get maximum 10 hours of screen on time. I never crossed that mark. Usage is no social media and mostly video browsing (means no screen touches with 480p/720p streaming) @ 60HZ/48HZ combo.
Regarding Google Play services, it was a design decision. I like functional changes and hence kept a minimal package that is oriented towards battery life. I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
I had done a comparison with Lineage's recommended MindTheGapps package and I get additional 2 hours of screen on time (maximum 10 hours of screen on time as said before).
profound answer. thank You.
Daedroza said:
I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
Click to expand...
Click to collapse
does it mean no plans to release g'less variant?
Daedroza said:
From a non developer's perspective, ROM is quite smooth. Most layers of the code are optimised. There are some functional changes like able to install unsigned packages in recovery which official Lineage doesn't allow.
For battery life, I get maximum 10 hours of screen on time. I never crossed that mark. Usage is no social media and mostly video browsing (means no screen touches with 480p/720p streaming) @ 60HZ/48HZ combo.
Regarding Google Play services, it was a design decision. I like functional changes and hence kept a minimal package that is oriented towards battery life. I had done my fair share of living without Google services and I think modern devices are fairly powerful now.
I had done a comparison with Lineage's recommended MindTheGapps package and I get additional 2 hours of screen on time (maximum 10 hours of screen on time as said before).
Click to expand...
Click to collapse
10 hours is impressive, even with just 60hz. So that means if you do not have the MindTheGapps you have 2 hours extra battery? Or is it 2 more hours if you have the MindTheGapps vs the Google bloat?
Thanks
alekksander said:
profound answer. thank You.
does it mean no plans to release g'less variant?
Click to expand...
Click to collapse
No plans as such. Building Android 13 is already very costly for me with these optimizations. Building it twice once with and without is something I am not looking forward to simply because of my constrained resources. I do a lot of building outside Lineage too, so simply cannot waste my SSD read/write cycles. Secondly, I already shipped first version with those services built-in. Removing those in next update will cause a lot of problems and could be fixed with clean flash only.
JorgeTone said:
10 hours is impressive, even with just 60hz. So that means if you do not have the MindTheGapps you have 2 hours extra battery? Or is it 2 more hours if you have the MindTheGapps vs the Google bloat?
Thanks
Click to expand...
Click to collapse
MindTheGapps is a more complete Google services package which includes accessibility and few other components. My minimal built-in package doesn't include those. If you require accessibility services, my recommendation is to use official Lineage with MindTheGapps.
Got it.
Really last question – does this ROM works anything different to LOS regarding UDFPS? (It doesn't seem so, but i prefer to ask since i cannot decode most of the changelog acronyms).
alekksander said:
Got it.
Really last question – does this ROM works anything different to LOS regarding UDFPS? (It doesn't seem so, but i prefer to ask since i cannot decode most of the changelog acronyms).
Click to expand...
Click to collapse
The UDFPS implementation is same as official build, no difference whatsoever except that my build has slightly more screen flashes because the UDFPS implementation doesn't support multi rect correctly. A workaround is present in official build that causes more battery life to be consumed.
For now that workaround is reverted in my build because I'm trying to understand how far it's effect is on battery life.
I don't think you will even notice it if you use 90HZ+ or more as default.
EDIT: Reverted to original Lineage implementation on new release!
rjawan said:
Appreciate your kind efforts. Feels perfectly smooth and stable.
Just a noob question regarding the "Safetynet fixes", my device still cannot pass the CTS (which I assumed would be one of the fixes compared to stock LOS 20). Or may be I misunderstood the whole thing. Thanks.
Click to expand...
Click to collapse
Hi @rjawan , please use build from February 19, 2023. It has complete SafetyNet fixes. Remember to remove Magisk as some apps still detect it and banks might app not work because of it. But CTS profile does pass and my bank app works now. Enjoy
Daedroza said:
Hi @rjawan , please use build from February 19, 2023. It has complete SafetyNet fixes. Remember to remove Magisk as some apps still detect it and banks might app not work because of it. But CTS profile does pass and my bank app works now. Enjoy
Click to expand...
Click to collapse
Thank you. Amazing work. Works like a charm, just as you said. Passed the CTS test straight away. BTW I am not using Magisk to begin with so have nothing to do on that front. Cheers mate. Thanks.
Daedroza said:
Changelog (You can use updater to update from local storage)
March 25, 2023
Sync with March security patches
Aggressive inline optimization using LTO
Aggressive sleep optimizations
Respect restricted apps
Platform fixes for GMS package
Fixed a bug where Android Studio's debugger didn't connect (for developers)
February 19, 2023
Complete fix for SafetyNet
February 13, 2023
Synced with February security patches
More SQLite optimizations and updates
Reverted to Lineage's UDFPS implementation
Use Aperture instead of MotCamera4 (crashes with face beauty and night mode...)
Click to expand...
Click to collapse
Hi, thanks for this build.
March 27 changelog ?
Thank you for making this great version of lineage, it really is very polished and it runs 11/10, the battery lasts a long time and the fluidity is magnificent, it passes the safetynet verification by itself, which is greatly appreciated, I loved it a lot, I wish it could be added the "amoled" night mode (I don't know if it already has it and it's hidden) and the game space and without a doubt I would stay in this rom forever
Roonicks said:
Thank you for making this great version of lineage, it really is very polished and it runs 11/10, the battery lasts a long time and the fluidity is magnificent, it passes the safetynet verification by itself, which is greatly appreciated, I loved it a lot, I wish it could be added the "amoled" night mode (I don't know if it already has it and it's hidden) and the game space and without a doubt I would stay in this rom forever
Click to expand...
Click to collapse
Check in display dark theme and there is a menu there
Rom is very stable and smooth but there is a very huge battery drain in idle mode around 2-3%/hr even after fresh install and can you please add network speed indicator on status bar on your next update if possible thanks in advance
aslam2121 said:
Rom is very stable and smooth but there is a very huge battery drain in idle mode around 2-3%/hr even after fresh install and can you please add network speed indicator on status bar on your next update if possible thanks in advance
Click to expand...
Click to collapse
You can use Battery Manager to detect applications that are sucking battery life or just check Battery Usage graph. Usually few applications hold some wakelock to perform activities in the background which usually ends up being the culprit. My recommendation is to disable applications running in background and disable background mobile data usage.
If you have done clean install, I recommend waiting for cache to build which generally takes time if you have lots of applications.
@aslam2121 : Check with new April build, there are more battery optimizations which reduces random wakelocks.
Thanks for this awesome ROM, any chance to add Dolby Atmos? (Without rooting the phone)
Where to get the boot image? And can I flash magisk zip directly from recovery?

Categories

Resources