[8.1.x][OFFICIAL][RELEASE] CarbonROM | cr-6.1 [z3c] - Xperia Z3 Compact Original Android Development

[8.1.x][OFFICIAL][RELEASE] CarbonROM | cr-6.1 [z3c] - Xperia Z3 Compact Original Android Development

{
"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

Related

[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7

ViPER4Android FX
{
"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"
}
By pittvandewitt and MrWhite214
Introduction
Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look of the app. As a solution for these troubles we have rewritten the 2.4.0.1 app source and added all 2.5.0.5 features to it. Many more features have been implemented too.
With our huge success of ViPER4Android 2.6 we decided to completely rewrite the ViPER4Android app in Kotlin. This allowed us to squeeze out the remaining bugs and clean up the code even more. After a long time of waiting for you and developing for us, ViPER4Android 2.7 is finally here!
There are many new features and improvements compared to 2.6, of which some can be found in the changelog. Hit the download button to check it out yourself!
Downloads
You can download the latest version on XDA Labs
If you were pointed here for the installer by @Zackptg5, the link can be found here
pittvandewitt's vdc service
If you've always wanted to get the most neutral and arguably best sound coming from your headphones, make sure to join the VDC service to request a file!
Donate
You can donate to us via PayPal or buy our donation package from XDA Labs with extra features!
Donate via PayPal
Buy our donation package *coming soon*
Dev Note
If you want to include the app in your work, you're free to do so as long as you give proper credits
Legal notice
We are not associated with vipersaudio nor audlabs.
Stating their Github readme we're free to use the driver as long as it's not used commercially.
The driver parameters are obtained from the 2.4.0.1 source. The graphical EQ interface is inspired by the Cyanogenmod DSP application
The app is still named ViPER4Android, because the driver isn't any different from what ViPER ACOUSTIC provides.
Renaming it without changing anything would be considered kanging, which is not what is going on here.
Credits
ViPER ACOUSTIC for the driver
Bappo for Swedish translation
pittvandewitt for Dutch translation
sazuke0703 for Thai translation
R1DEN for Russian translation
Hede for Danish translation
gloeyisk for Indonesian translation
LCS for Chinese simplified and traditional translations
razor84 for Turkish translation
Installation
Download and install the APK from XDA Labs
Follow the instructions when opening the app
XDA:DevDB Information
ViPERAndroid, App for the Apps & Games
Contributors
Team_DeWitt, pittvandewitt, Mr_White_214
Version Information
Status: Stable
Current Stable Version: 2.7.2.1
Stable Release Date: 2020-10-27
Created 2018-04-09
Last Updated 2020-10-27

Currently on the wishing list
Car mode / head unit detection
More translations. If you're interested, take a look over here to find the files. Fork the repo and make a pull request to get your translation merged in next release!
EMUI (Huawei) 8.0+ refuses to load the driver. Ask ViPER ACOUSTIC for a 64bit driver (Can't fix)
Updated driver that does not require selinux injections or the libstdc++ dependency workaround (Can't fix)
Before reporting:
Make sure you use the latest APK provided on XDA Labs
Make sure any other audio mod is disabled/removed before installing the driver. We really cannot afford fixing every single device setup, especially when it's not related to the app
If you would like to report a bug, pm @Team_DeWitt using the following format:
[Describe the problem and your steps you take to reproduce it]
[Phone brand and model]
[OS (ROM) + Android version]
[Root method (in case of magisk: core or full)]
[Provide a link to your log file]

Changelog
2.7.2.1
Improved loading logic for convolution files
Fixed an issue when installing the module on older Magisk versions
Bug fixes
Stability improvements
2.7.2.0
Android 11 support
Automatically save/restore settings based on the device type/name
Add preset widget
Reworked presets
Performance improvements
Close service when no music playback is active if legacy mode is disabled
Add optional crashlytics to help improving future versions
2.7.1.6
Support Magisk 20.3
Long press a feature to show description
Material theme update
Support scoped storage on Android 10+ (Preset dir is now /sdcard/Android/data/com.pittvandewitt.viperfx/files/Preset)
2.7.1.0
Support Magisk 19
Add compatibility setting
Add ability to attach to sessions
Fix preset loading bug
Switch from setools to magiskpolicy
Important release notes: Link
2.7.0.0
Full rewrite in Kotlin
New UI
Presets can be managed in the app itself
Effects can be set more precisely with seekbars
Min API 23
Uses 2.5.0.4 driver only
Audio routing bug fixed
Driver status bug fixed
Cross device effect changing bug fixed
App follows system dark/light mode (can be toggled with google messages e.g.)
Installation is faster and more versatile
Notification settings
Reduced APK size significantly
2.6.0.5
Add app shortcuts (7.1+)
Minor interface redesign
Fix muffled sound
Fix options not applying
Fix profile conversion
Introduce vdc service
Improve performance
Update driver installation
Update chinese translations, thanks to KiSS
2.6.0.4
Retain service after clearing recents
Emergency service.sh fix
Support Magisk core mode
Fix profile load loop
Recover speaker service
Fix convolver
Support Pixel devices
Use su.d if possible
Force global effect mode
Add Korean translation by @nebulac
2.6.0.3
Fix /system install and uninstall.
Add temporary workaround for the convolver
Updated strings
2.6.0.2
Fix FC while installing the driver
Add root check before installing the driver
Removed lucky patcher check
Capitalized driver status outputs
Updated strings
2.6.0.1
Fix profile loading
Fix assets bug
2.6.0.0
Initial Release

Answers to some related questions
Help, the driver status says no
In case of Enabled: no; Please flip the Master limiter switch and go sit in a corner for a while
In case of Processing: no; If you use an application that uses audio sessions, enable session attaching in the settings. If that does not work, the audio is routed over session 0. You might want to try Audio Compatibility Patch from the Magisk repository in this case.
What happened to the profiles?
They're now called presets. They are reworked to use independently per device, a feature that was very welcome. Because of many technical changes and improvements on how the preset is stored and loaded, they are not compatible with older versions than 2.7. You will have to recreate them by hand unfortunately. You can access the menu by pressing the selected device in case you missed the huge showcase when you first launched the app after installing the driver
Why does your Magisk module not work?
Probably because you installed some other mod that also has an audio_effects file in it. Whatever module gets loaded last will become active
The easiest way to bypass this is to let the app build a module after you installed all your favorite audio mods, and delete all files containing audio_effects in the other modules
AudModLib will not come in handy this time, because the app doesn't flash a zip that AML can intercept
Where can I find the source code?
You can't. And there is an obvious reason for that: This app is more sensitive to kangers who start selling this app, likely after adding their bullsh*t to it, rather than to people who actually want to help improve the app. Something like that already happened in the past to other audio software here on xda. Not really something we want to see happen again
Where did the Selinux switch go?
What..? Are you really that careless security wise?
The app handles this in a much more sophisticated way now. It injects only the absolute necessary rules to allow V4A to process, fully automatically
Help, why do I still experience service drops?
Probably because doze is kicking in because Android doesn't like long running services. The service has been implemented the way the docs suggest. You can try excluding it from doze. Alternatively you can check out dontkillmyapp.com for tips
Do you have a zip file for me?
No. There is no point in providing a zip file anymore. The driver installation is written from scratch and actually works now
How do I uninstall the driver?
Use Magisk Manager to delete the module. If you use another root solution, you can dirty flash your rom or just leave it there

Awesome! Works perfectly with the super quality driver 2.3.4.0 :good:

Oh my goodness.... That Easter egg... Scared the s h i t out of me, coz had the volume pretty much on max

Is there an option to install systemlessly with magisk?

Hey could we possibly get a black version instead of grey, it would look fantastic on AMOLED displays. There ones was a Substratum theme like that for the original materialised version, maybe something similar for this one?

shuli81 said:
Is there an option to install systemlessly with magisk?
Click to expand...
Click to collapse
Hello Shuli,
There is currently not an option for that, however when Magisk is detected, it will automatically create a Magisk module to install the driver systemlessly.

Ragnar Eldur said:
Hey could we possibly get a black version instead of grey, it would look fantastic on AMOLED displays. There ones was a Substratum theme like that for the original materialised version, maybe something similar for this one?
Click to expand...
Click to collapse
We're are currently in the progress of creating that, so stay tuned!

this ester egg ^^ Realy good work install with driver in less 1 minutes everithings more beautifull and still amazing sound thanks for your hard work

"Devices other than headset not loading (fixed in next release)"
Bluetooth works for me after I load an effect profile
Also, that was the fastest that Viper has ever installed for me. Well done.

Hmm, it seems to have a funny audio glitch whenever I launch the app. My music kinda gets quieter for a second.
Will there be a way to revert to the old materialised look? I feel like either an option to go back or have a hybrid would be nice.
I also miss the dials since the huge menus aren't fun to scroll through. Especially since you can't fine tune some of them. Maybe a slider would work too?
Also another thing is to add back the search option in the DDC menu.
Love theme though.

Been testing it all day. Gotta say nice job guys! Super easy to install, nice look and feel, improved work flow having everything on one page. I also like that there is no static when changing the settings.
Nice app, 5 stars! If I could add something it would be the ability to collapse the sections so that it isn't cluttered with the settings I don't use. Also an easy way to download convolvers.
Favorite feature: the way you built the EQ. I can just drag my finger along it and make the arc I want. Beautiful!
Thanks guys!

Unfortunately doesn't work on my Pixel 2 XL. Both drivers say they installed fine in the app and to reboot, then gets stuck on the Google splash screen, from which I have to manually reboot to get the phone to come on again, and after this neither driver sticks (0.0.0.0, driver status abnormal etc).
It's strange as the last V4A to work for me was Ahrion & zackptg5's version 2.8 (which weirdly still works fine); all of their subsequent releases didn't either.
Let me know if providing any logs will help!

Working great on OP5 OOS 5.0.4 with Magisk Detected

erak606 said:
Hmm, it seems to have a funny audio glitch whenever I launch the app. My music kinda gets quieter for a second.
Will there be a way to revert to the old materialised look? I feel like either an option to go back or have a hybrid would be nice.
I also miss the dials since the huge menus aren't fun to scroll through. Especially since you can't fine tune some of them. Maybe a slider would work too?
Also another thing is to add back the search option in the DDC menu.
Love theme though.
Click to expand...
Click to collapse
Hey erak606, currently there is no way to revert to our old themed version, however we will put it online again on XDA Labs soon. About fine-tuning, we've thought about but sticked with the lists, however we might change that in the future. We are not sure about it yet.
Adding back the search option is an good idea, we will pay some attention to that in our next release.
Bartws95 said:
Unfortunately doesn't work on my Pixel 2 XL. Both drivers say they installed fine in the app and to reboot, then gets stuck on the Google splash screen, from which I have to manually reboot to get the phone to come on again, and after this neither driver sticks (0.0.0.0, driver status abnormal etc).
It's strange as the last V4A to work for me was Ahrion & zackptg5's version 2.8 (which weirdly still works fine); all of their subsequent releases didn't either.
Let me know if providing any logs will help!
Click to expand...
Click to collapse
Hey Bartws95, bummer to hear your driver installation is not working, logs are definitely helpfull, make sure to grab the logs after the installation and before rebooting. Since you stated it did work with Ahrion & zackptg5's version, I will also contact them. Thanks for the report!

surajloharia said:
Doesn't go well with Lucky Patcher
Click to expand...
Click to collapse
You mean xda? It's supposed to be that way ... :silly:

Great work guys

kopitalk said:
You mean xda? It's supposed to be that way ... :silly:
Click to expand...
Click to collapse
viper

[OTA] [10.0] [MONTHLY] CarbonROM CR8.0 PAX [OFFICIAL] [STABLE]

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??

Development MARS_SOMs - Stock - VoLTE, VoWifi, Carrier Video Calls

MARS SOM
{
"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"
}
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 13 Stock Xperia FW
Magisk Init.d Injector
Download:
Sign in - Google Accounts
Bugs:
Report them if You found one!
Donations:
paypal.me/miustone

Reserved :>

How stable is this? I would like to install on my Xperia 5 III. Any known issues so far?

SPEEDHAMMER said:
How stable is this? I would like to install on my Xperia 5 III. Any known issues so far?
Click to expand...
Click to collapse
I can just speak for the 2019 Xperias:
-BT AAC Codec isn't working actually
-Calls may have no Audio
But that's all on My Bug List. It seems like the latest Versions aren't booting on the Xperia 1 III so it will be the same on the 5 III. But I will help to fix that if People are willed to test around... That's why I'm also on GitHub...

Updated the Thread, MARS_SOMs and GitHub<3

Miustone said:
I can just speak for the 2019 Xperias:
-BT AAC Codec isn't working actually
-Calls may have no Audio
But that's all on My Bug List. It seems like the latest Versions aren't booting on the Xperia 1 III so it will be the same on the 5 III. But I will help to fix that if People are willed to test around... That's why I'm also on GitHub...
Click to expand...
Click to collapse
Are you willing to develop a stable version for me? I am willing to donate higher amounts to fund the development. I'm quite tired of the way Sony does their software.
The auto downgrade to 60Hz everytime the phone gets slightly hot. That software feature itself drives me mad from using the phone.

SPEEDHAMMER said:
Are you willing to develop a stable version for me? I am willing to donate higher amounts to fund the development. I'm quite tired of the way Sony does their software.
The auto downgrade to 60Hz everytime the phone gets slightly hot. That software feature itself drives me mad from using the phone.
Click to expand...
Click to collapse
Totally agree with You about the Software since the Z3 (Z3+/Z4). They started a Semi-Public Beta Program to optimize the Firmwares with an Bareboned AOSP. Still lacking a lot of the old famous Featurs like the Mini Apps, Extra Apps, Widgets, Brands like Cybershot, Walkman and so on... It's sad!
I'm really trying to get the best out of it (still). So i will solve the issues asap (next 24hrs).
Let's try to solve the Performance issues right after that!
I splitted My MARS SOMs into 3 Gears. Everything is explained on GitHub. Also updated the Threads and the ReadMe's. Also made huge Progress with My own Overlay. It's a firsty on Android Development (including incredible and tons of Features). Give "Gear Second" and "Gear First" a try for now. It should work fine yet (except for the Audio issues maybe)

Miustone said:
Totally agree with You about the Software since the Z3 (Z3+/Z4). They started a Semi-Public Beta Program to optimize the Firmwares with an Bareboned AOSP. Still lacking a lot of the old famous Featurs like the Mini Apps, Extra Apps, Widgets, Brands like Cybershot, Walkman and so on... It's sad!
I'm really trying to get the best out of it (still). So i will solve the issues asap (next 24hrs).
Let's try to solve the Performance issues right after that!
I splitted My MARS SOMs into 3 Gears. Everything is explained on GitHub. Also updated the Threads and the ReadMe's. Also made huge Progress with My own Overlay. It's a firsty on Android Development (including incredible and tons of Features). Give "Gear Second" and "Gear First" a try for now. It should work fine yet (except for the Audio issues maybe)
Click to expand...
Click to collapse
Yes thank you for your contributions so far. I will be more than happy to test out once it can be installed. Looking forward to supporting your work by way of finance and feedback.

Are you able to integrate with Franko Kernel Manager?

SPEEDHAMMER said:
Yes thank you for your contributions so far. I will be more than happy to test out once it can be installed. Looking forward to supporting your work by way of finance and feedback.
Click to expand...
Click to collapse
Thank You very much for Your Support! Really appreciate it! I just updated MARS again and it's free of bugs i think. I just need help to find out why it Bootloops on 2020 and 2021 Devices...
SPEEDHAMMER said:
Are you able to integrate with Franko Kernel Manager?
Click to expand...
Click to collapse
I bought this App too, but do You mean a own Kernel for the Xperias? Or are You thinking about Profiles for the Stock Kernel?

Miustone said:
Thank You very much for Your Support! Really appreciate it! I just updated MARS again and it's free of bugs i think. I just need help to find out why it Bootloops on 2020 and 2021 Devices...
I bought this App too, but do You mean a own Kernel for the Xperias? Or are You thinking about Profiles for the Stock Kernel?
Click to expand...
Click to collapse
We should be the one to thank you! I will try your new build out and give feedback. Yes i think the Xperia needs s custom kernel or custom profiles at least.
Something is not right with how the stock kernel processes tasks. Games do not get the phone hot. But teamviewer, uber and google maps does for some reason. One other Xperia 5 III owner reported that the Franko Kernel Manager solves this issue. Perhaps we can take reference from this and improve?

SPEEDHAMMER said:
We should be the one to thank you! I will try your new build out and give feedback. Yes i think the Xperia needs s custom kernel or custom profiles at least.
Something is not right with how the stock kernel processes tasks. Games do not get the phone hot. But teamviewer, uber and google maps does for some reason. One other Xperia 5 III owner reported that the Franko Kernel Manager solves this issue. Perhaps we can take reference from this and improve?
Click to expand...
Click to collapse
The Problems with the Performance should be fixed over the MARS Base SOM. I played around with the Kernel Settings and it doesn't seems to improve stuff further. LMK and ZRAM are the bad Guys at the end. Paired with wrong rendering of certain Apps like Google Maps. Everything of that and more should be improved with My fully working SOMs. I would be glad to make it work on the last 6 Flagships from SONY (Maybe even the Pro Devices). Just need some help with the testing...
Really reached some big Goals the last week or so. Really looking forward to make it 100% stable for everyone. There are also more things planned for our Xperias which are really ambitious...

Miustone said:
The Problems with the Performance should be fixed over the MARS Base SOM. I played around with the Kernel Settings and it doesn't seems to improve stuff further. LMK and ZRAM are the bad Guys at the end. Paired with wrong rendering of certain Apps like Google Maps. Everything of that and more should be improved with My fully working SOMs. I would be glad to make it work on the last 6 Flagships from SONY (Maybe even the Pro Devices). Just need some help with the testing...
Really reached some big Goals the last week or so. Really looking forward to make it 100% stable for everyone. There are also more things planned for our Xperias which are really ambitious...
Click to expand...
Click to collapse
Hey there. Just managed to install your SOM and test it out for a while. Overall stability is there and performance seems identical to stock.
Just would like to raise some stability issues:
Unable to turn on Wi-Fi on my end so far. Turning it on through notification shade shortcut causes System UI to freeze momentarily and W-Fi goes off after that. Turning it on through settings causes Settings to freeze momentarily and Wi-Fi goes off after that. It doesn't show list of Wi-Fi networks
Screen refresh rate still drops to 60Hz when phone gets warm and there is no way to force change it back to 90Hz or to turn this feature off
Also raising these suggestions:
We have to find a way to improve the time from fingerprint scan to home screen. It has taken too long since the first Xperia 5. Also, pressing the power button and resting finger on the sensor at the same time seems to get to home screen faster. Just resting finger on the sensor without pressing the power button takes a longer time. I think it is something to do with software
Is it feasible to port over Lineage OS or similar?
Thank you and looking forward to hearing from you and supporting your work!

Thanks again for Your detailed Feedback @SPEEDHAMMER ! I have just released another big Update which should improve things further...
I would really like to see You on My Disco rd Server to share more Details about my upcoming work with You!
I'm about to create an Xperia Exclusive OS with many great Features. There are already some people around and I'm sure they would like to see You too!

HUGE UPDATES INCOMING!
MARS will be available over GitHub Releases so You can easily Download ready-to-use Zips of MARS for Magisk. Also included are now OTA Updates for MARS over Magisk and the focus Changed to GSIs again. Use PHH AOSP 12 or PIXEL EXPIERENCE 12 by Ponces to unleash Your Xperias

Excuse me, I've just come back after 3 years of stock ROMs. What is the order of flashing the Pixel Experience? I used to use a custom recovery, but as I see there's no such one for 5 III and I didn't find any instruction. Do I just flash the ROM via "fastboot flash system_b pe.img"?
Now I have a stock ROM with all-working Magisk. Do I need a full-wipe also? There's a GSI flashing after Magisk installation in your general instruction, right?

Graegor said:
Excuse me, I've just come back after 3 years of stock ROMs. What is the order of flashing the Pixel Experience? I used to use a custom recovery, but as I see there's no such one for 5 III and I didn't find any instruction. Do I just flash the ROM via "fastboot flash system_b pe.img"?
Now I have a stock ROM with all-working Magisk. Do I need a full-wipe also? There's a GSI flashing after Magisk installation in your general instruction, right?
Click to expand...
Click to collapse
You're not alone! Just read and follow My Guide over here:
[CLOSED] Deleted
Here was a Guide. Someone said people don't care about Me or My Work so...
forum.xda-developers.com

Thanks for your answer and the tutorial. I went through step 5, but I still don't understand how to flash Pixel Experience .img file (Android 12 GSI (Pixel Expierence ARM64 A/B VNDKLITE) . Should I extract it, use any flasher etc.?

Graegor said:
Thanks for your answer and the tutorial. I went through step 5, but I still don't understand how to flash Pixel Experience .img file (Android 12 GSI (Pixel Expierence ARM64 A/B VNDKLITE) . Should I extract it, use any flasher etc.?
Click to expand...
Click to collapse
You need the Pixelsystem.img File
Place it next to fastboot and execute:
fastboot flash system_a Pixelsystem.img
Followed by
fastboot flash system_b Pixelsystem.img
Wipe Your Device or it doesnt Boot
fastboot -w
Thats it

Sorry, have the same error during step 5 and during flashing PE. I made a mistake somewhere.

[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.

[ROM][UNOFFICIAL] LineageOS 20

Reserved.

Any known bug?

Do you need to install Gapps? Any recomendation if needed?

I installed this rom and it works fine, but the fod doesn't work with the screen off, is it like that or is there any configuration or procedure to be done?

ashwany.yadav said:
Any known bug?
Click to expand...
Click to collapse
None.
vetalpeo said:
Do you need to install Gapps? Any recomendation if needed?
Click to expand...
Click to collapse
Mindthegapps, nikgapps.
alessandro-villa said:
I installed this rom and it works fine, but the fod doesn't work with the screen off, is it like that or is there any configuration or procedure to be done?
Click to expand...
Click to collapse
It's not included in LineageOS sources either my code.

I tested this ROM for two days and so far it is a great experience without any major issues. Thanks!
Issues which I ran into:
- Fingerprint scanner works much worse when night backlight is turn on.
- Google camera from Play Store don't work, it just crashes.

Cool. But I cant download with android orginal browser and phone calls just playing ringtoone but nothing appeared in scrren to amswer and I should call to a number to unhide incoming call dialog!

Hello everyone.
First of all, a big BIG thank you @Englezos for this ROM, even unofficial. For the little I used it, it is extremely functional, much more than the unofficial ROM /e /OS https://community.e.foundation/t/un...-mi9t-pro-raphael-e-os-q-build/24814?u=parhit (last update in May 2021 and many bugs). No worries on my side about digital recognition, ergonomics and even the separation of personal and professional profiles (via Insular). I had a bit of trouble installing it (the adb sideload was showing 40% and made me restart but it didn't work, same thing the second time but there I just waited maybe a bit more before seeing with relief the Lineage logo).
I'm reporting some bugs I've encountered, on the personal or pro side.
# Applications (via Aurora Store)
Yuka https://play.google.com/store/apps/details?id=io.yuka.android&pli=1 doesn't launch, the screen is white and makes a strobe effect
Brain FM https://play.google.com/store/apps/details?id=com.brainfm.app&hl=en_US stays on initial load
UpHold https://play.google.com/store/apps/details?id=com.uphold.wallet&hl=en&gl=US same
# Default browser
I can't download via the default browser .apk files, it says to check in the settings but I couldn't find anything. Another
# General configuration
The alarm clock does not ring if the phone is switched off. So I was late this morning
Again a BIIIIG UP. I was going to go back to MIUI out of spite but to have a stable OS, thanks to you I stay on the right side

MartinPL said:
I tested this ROM for two days and so far it is a great experience without any major issues. Thanks!
Issues which I ran into:
- Fingerprint scanner works much worse when night backlight is turn on.
- Google camera from Play Store don't work, it just crashes.
Click to expand...
Click to collapse
1. That's the default AOSP behavior until Google changes it. You can try lower the density.
2. Because this device is not a Google Pixel.
mablue said:
Cool. But I cant download with android orginal browser and phone calls just playing ringtoone but nothing appeared in scrren to amswer and I should call to a number to unhide incoming call dialog!
Click to expand...
Click to collapse
It appears that it was a LineageOS bug which is already fixed and will be included into the next build. About the phone calling issue that you just described I can't reproduce it.
parhit said:
Hello everyone.
First of all, a big BIG thank you @Englezos for this ROM, even unofficial. For the little I used it, it is extremely functional, much more than the unofficial ROM /e /OS https://community.e.foundation/t/un...-mi9t-pro-raphael-e-os-q-build/24814?u=parhit (last update in May 2021 and many bugs). No worries on my side about digital recognition, ergonomics and even the separation of personal and professional profiles (via Insular). I had a bit of trouble installing it (the adb sideload was showing 40% and made me restart but it didn't work, same thing the second time but there I just waited maybe a bit more before seeing with relief the Lineage logo).
I'm reporting some bugs I've encountered, on the personal or pro side.
# Applications (via Aurora Store)
Yuka https://play.google.com/store/apps/details?id=io.yuka.android&pli=1 doesn't launch, the screen is white and makes a strobe effect
Brain FM https://play.google.com/store/apps/details?id=com.brainfm.app&hl=en_US stays on initial load
UpHold https://play.google.com/store/apps/details?id=com.uphold.wallet&hl=en&gl=US same
# Default browser
I can't download via the default browser .apk files, it says to check in the settings but I couldn't find anything. Another
# General configuration
The alarm clock does not ring if the phone is switched off. So I was late this morning
Again a BIIIIG UP. I was going to go back to MIUI out of spite but to have a stable OS, thanks to you I stay on the right side
Click to expand...
Click to collapse
Thanks for your words and your detailed feedback. I'm glad that you have managed to installed the rom successfully.
About the Yuka app unfortunately its not available on my country and I can't install it via Google Playstore.
Brain and Uphold apps are loading and working fine.
Android browser: It appears that it was a LineageOS bug which is already fixed and will be included into the next build.
The alarm clock won't work if your device is powered off. Why would you want such thing?

Hi Englezos, thanks for the fast feedback.
Englezos said:
About the Yuka app unfortunately its not available on my country and I can't install it via Google Playstore.
Brain and Uphold apps are loading and working fine.
Android browser: It appears that it was a LineageOS bug which is already fixed and will be included into the next build.
The alarm clock won't work if your device is powered off. Why would you want such thing?
Click to expand...
Click to collapse
Yuka only in France? ****... Maybe with a VPN? Can I help?
Brain.fm and Uphold working fine? Holy sh*t. I don't know why it doesn't work here. What tool do you use to install apps?
Browser: ok, I am using Bromite but it sounds good if it will be fixed.
Alarm: well, an alarm clock that doesn't ring is strange, isn't it? I didn't have a watch and I turn off the phone at night. So I thought the alarm would go off even if it was off (which is what was happening with Murena). Am I the only one doing this?

Installed this ROM as OTA for Los 19.1 (SebaUbuntu). Thanks for new version.
All work as need.

MoodRoff said:
Installed this ROM as OTA for Los 19.1 (SebaUbuntu). Thanks for new version.
All work as need.
Click to expand...
Click to collapse
So you dirty flashed this ROM? Via recovery?

Plex82 said:
So you dirty flashed this ROM? Via recovery?
Click to expand...
Click to collapse
Yes, need do format data later install

Englezos said:
About the phone calling issue that you just described I can't reproduce it.
Click to expand...
Click to collapse
I always have this problem in iran region with mobile calls +98Xxxxxxxxxx.
And it's too bad .Maybe I think it's a nonclean installation bug

parhit said:
Hi Englezos, thanks for the fast feedback.
Yuka only in France? ****... Maybe with a VPN? Can I help?
Brain.fm and Uphold working fine? Holy sh*t. I don't know why it doesn't work here. What tool do you use to install apps?
Browser: ok, I am using Bromite but it sounds good if it will be fixed.
Alarm: well, an alarm clock that doesn't ring is strange, isn't it? I didn't have a watch and I turn off the phone at night. So I thought the alarm would go off even if it was off (which is what was happening with Murena). Am I the only one doing this?
Click to expand...
Click to collapse
At least it's not available on my country. Maybe get some logs related to this app.
Rest applications are installed through Google Playstore.
Alarm is ringing well when the phone is powered on.
mablue said:
I always have this problem in iran region with mobile calls +98Xxxxxxxxxx.
And it's too bad .Maybe I think it's a nonclean installation bug
Click to expand...
Click to collapse
You should always clean flash when coming from another rom. Try another phone app also.

New release is up with November security patch and many critical fixes!! Links are on the first post!!

Does this rom passes safetynet by default? Also google photos spoofing is there or not ?

deleted

Englezos said:
New release is up with November security patch and many critical fixes!! Links are on the first post!!
Click to expand...
Click to collapse
Hi there. Great
So is it necessary to reinstall everything from scratch or is a classic update possible? This is the first time I've had an update available on an unofficial ROM

Database Info

welcome