[GSI][arm64] Ubuntu Touch (ubports) [DRG/B2N/PL2] - Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
This operating system is developed and maintained by UBports: An international community of passionate volunteers.
This means Ubuntu Touch is 100% community driven and independent.
What is Halium?
Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.
How it is a GSI?
First of all, I should mention ubports GSI definition is different from android, but both are generic.
ubports root file system was always generic and works for most cases, but devs were porting halium system image to add device-specific (HALs and configs) support to ubports Android container.
But after project treble which introduced in android 8, all device-specific parts of android system image moved to vendor partition and we can use "Generic system images" over one vendor partition.
In halium version 9, we use this adventure and have a totally generic system image + root file system.
Requirements:
The only Requirement of booting this GSI is having Halium patched kernel.
Keep in mind having android 9 firmware installed on the device as GSI base is mandatory (GSI can be used on android 8.0 and 8.1 vendors but experimental and not supported yet)
How to install?
1. Boot TWRP and FORMAT data
2. Flash vendor image and halium-boot.img (Halium-boot.img confirmed working on DRG and PL2, B2N needs testing)
3. Flash GSI installer zip
4. Reboot
Note: if the device is stuck on the splash screen on boot, simply force reboot using the power/volume button combo meant for your device
Download:
GSI - built by @mrcyjanek (download ONLY target.zip)
Vendor images
Halium-boot
Whats suppose to work?
Bluetooth
Camera
Cellular Radio
Mobile Data
GPS
Graphics
Sensors
Sound
In-call Audio
Touch
Wifi
Vibration
Anbox
Media Playback
Known bugs?
Random (but rare) BSOD + reboots
no way to unlock using Fingerprint
Touching Fingerprint sensor can reduce media volume
oh and of course VoLTE
Camera (on B2N)
Supports:
Halium telegram group
UBports telegram group
UBports Porting telegram group
ErfanGSIs telegram group
Report Bugs:
Explain your bug in proper support telegram groups (from above)
Please don't ask about spoon-feeding or helping on building kernel or device specific builds.
Please don't ask about picking/reverting commits or any basic git commands.
bug reports without logs will be ignored
logs we need are: android logcat, kernel log, syslog
kernel log:
Code:
dmesg
syslog:
Code:
cat /var/log/syslog
logcat:
Code:
sudo -s
LD_LIBRARY_PATH=/system/lib64 lxc-attach -e -n android -- /system/bin/logcat
Taken with all due respect from Erfan's Thread
Appendix:
Anbox installation guide (by SevralTi on Github)
Code:
sudo mount -o rw,remount /
sudo apt update && sudo apt install -y anbox-ubuntu-touch android-tools-adb
mkdir ~/anbox-data
wget http://cdimage.ubports.com/anbox-images/android-armhf-64binder.img -O ~/anbox-data/android.img
touch ~/anbox-data/.enable
sudo chmod -R o+wrx /home/phablet/anbox-data/data
sudo start -q anbox-container
reboot, wait 2 minutes the reboot again
To symlink anbox files to system:
ln -s ~/anbox-data/data/media/0/Documents ~/Documents/android
ln -s ~/anbox-data/data/media/0/Pictures ~/Pictures/android
ln -s ~/anbox-data/data/media/0/Music ~/Music/android
ln -s ~/anbox-data/data/media/0/Movies ~/Videos/android
To make the QS panel occupy the whole screen, install UT Tweak Tool from the Open Store and increase device display scaling
Libertine containers can't be created from the settings app for now. To create a container, pass the command "TMPDIR=/tmp" in the terminal and follow documentation here

IMPORTANT
I take NO credit for the UBPorts community. All that I've simply done is patch our kernel to make it compatible.
Default password is "phablet" (without the quotes)
If you like my work, consider buying me a coffee and join our telegram groups
Cheers,
Sid

I would like to offer a special thanks to a bunch of people who've been with me through this ridiculous journey of mine:
@Sahil_Sonar - for all the help and advice he's given
@krushndayshmookh - for being a generally sweet guy and looking out for me
@CarbonGTR and @Nikhilkumar038 - for being solid friends and motivators throughout my struggle
@Catharsis007 - for being best boi
@ArcherTanu - for being extremely helpful
The UBPorts community
EVERYONE who's worked on the LOS sdm660 Kernel
and a special unnamed best friend who helped me power through the last couple of months.
Cheers,
Sid

Wonderful Work!! GBU!!

Pru

Updated #1 with a new GSI link that doesn't have the reduced storage bug

Awesome work!!! (though I can't try it out--I have a PL2)

Vedanth Padmaraman said:
Awesome work!!! (though I can't try it out--I have a PL2)
Click to expand...
Click to collapse
You can! Our kernel sources are unified and known to work on all 3 devices, DRG, PL2, and B2N
I've listed the bugs specific to DRG only because I own only a DRG, but in theory, you should be able to flash this on PL2 or B2N as well

Ok! Installing it soon
It works on the PL2, encountered nothing broken so far :good:. I received an SMS, downloaded some stuff, etc (but haven't tried calling yet). Once in while it does hang with a black screen while booting, but simply holding Vol. up + Power to force-restart does the trick, like mentioned in the OP. Set up whatsapp successfully on Anbox, but graphics on any anbox app are jerky and laggy at times, in a manner similar to that of the anbox installation on my Linux Mint, so this doesn't seem to be an issue pertaining to this GSI/Halium port. Still, would be nice to have an improvement

Updated kernel to fix media playback. Download from link in OP

Oh looks like really interesting. I'm downloading now. I'll test this for a few days. Question: It isn't Android totally. It's Ubuntu yes? Does it meant that other OS's can be ported as well like HarmonyOs? If that's true how it is can be ported.

SamandaR1112 said:
Oh looks like really interesting. I'm downloading now. I'll test this for a few days. Question: It isn't Android totally. It's Ubuntu yes? Does it meant that other OS's can be ported as well like HarmonyOs? If that's true how it is can be ported.
Click to expand...
Click to collapse
It isn't Android, it isn't exactly Ubuntu Desktop either. Canonical was working on Ubuntu Touch/Ubuntu Phone until 2017, and after they dropped the project, the UBports community was born and carried it forward. I'm not sure about HarmonyOS

#1 updated with halium-boot.img (confirmed working on DRG and PL2, B2N needs testing), new flashing method added

Which flashing method is prefered? Anybody who can tell a little on how it is in use? (Does it feel snappy or any lags)

Just about to flash to my B2N. The file B2N####-vendor.img needs to be set to a partition. "Select partition to flash image". I'm guessing boot or system, but honestly I have no idea. help?
---------- Post added at 11:43 AM ---------- Previous post was at 11:32 AM ----------
So.. I'm not exactly known for my patience.. Using method 1 I flashed the vendor image to system image, and boot image to boot partition. then changed to zip and flashed gsi. Twrp prompted me to install official twrp app, I was curious to see if it would work so I chose to do so. Then reboot turned me into a bootloop...

n00bDroid said:
Just about to flash to my B2N. The file B2N####-vendor.img needs to be set to a partition. "Select partition to flash image". I'm guessing boot or system, but honestly I have no idea. help?
---------- Post added at 11:43 AM ---------- Previous post was at 11:32 AM ----------
So.. I'm not exactly known for my patience.. Using method 1 I flashed the vendor image to system image, and boot image to boot partition. then changed to zip and flashed gsi. Twrp prompted me to install official twrp app, I was curious to see if it would work so I chose to do so. Then reboot turned me into a bootloop...
Click to expand...
Click to collapse
Code:
fastboot flash vendor <B2N####-vendor.img>
fastboot flash boot halium-boot.img # NOT B2N-0-354H-00WW-boot.img
Let the keyword "vendor" in <B2N####-vendor.img> serve as a reminder that it is meant to be flashed to the vendor partition.

Vedanth Padmaraman said:
Code:
fastboot flash vendor <B2N####-vendor.img>
fastboot flash boot halium-boot.img # NOT B2N-0-354H-00WW-boot.img
Let the keyword "vendor" in <B2N####-vendor.img> serve as a reminder that it is meant to be flashed to the vendor partition.
Click to expand...
Click to collapse
Immidiately after my post I made the same realization that vendor.img = vendor partition. So I did that, and it still didn't work.. But then again, I actually flashed B2N-0-354H-00WW-boot.img because I hadn't seen the halium-boot
So I went again. Now according to recipe. Then reboot system..I've been stuck on the "AndroidOne" logo for 15 minutes....after a forced reboot I see the Ubuntu Touch logo!!! thank you!

Camera isn't working. Any tips?

i did not thank you @Sid127 ! That's done !

Sorry for the recent inactivity
n00bDroid said:
Camera isn't working. Any tips?
Click to expand...
Click to collapse
I notice you're on B2N... System logs would be helpful from when you're trying to use the camera. That'd be the dmesg. Without that, I can't be of much help.

Related

[7.1.2][UNOFFICIAL] LineageOS 14.1 for Lenovo P2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 6 (marshmallow), 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 :
Boots
Touch
RIL [Calls, Mobile Data]
Wi-Fi
Wi-Fi Hotspot
Bluetooth
Camera
Audio
Sensors
Fingerprint
Flash
GPS
NFC
Known issues:
VoLTE doesn't work.
LED.Note: You can use LED with this awesome method: https://forum.xda-developers.com/lenovo-p2/themes/lenovo-p2-rooted-custom-led-t3589859
This is the one of the first builds for p2a42, so minor bugs are expected.Please report them if any.
Instructions :
Flash Twrp :- LINK
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Latest build [19/06/2017]: https://mega.nz/#!KgcS1boY!f1veK_D-kw_8WYDMD9Id0qytacZuHVN3xvQzB7t0SP0
Google Apps: http://opengapps.org/
Credits :
One Team Forum
XDA:Rom Information
LineageOS 14.1,p2a42, ROM for the Lenovo P2
Contributors
wzedlare
ROM OS Version: 7.1.x Nougat
Version Information
Status: Stable
Created 2017-03-18
Last Updated 2017-06-19
#rezerved for me
How to install Root for Apps on Android Nougat Custom Rom
Download and transfer the Lineage SU addon zip file from the download link above to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the Lineage SU addon zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once Lineage SU addon is flashed, you’ll get Reboot System option, select it.
How to Enable Root for Apps on Lineage OS
Once you’ve installed the Lineage SU addon zip, do the following to enable root for Apps on Lineage OS:
Enable Developer options: Go to Settings » About phone » Tap seven times on Build number.
Go back to Settings main menu and open Developer options from there.
Look for Root access setting, and set it to Apps and ADB or Apps only, as per your need.
That’s all. Your Android device running on Lineage OS should have full root access for apps now.
If you ever need to disable root access, just go to Settings » Developer options » Root access and select the Disabled option from there.
Download;
addonsu-arm64-signed.zip
Great job, no idea how you build new kernel 3.18.31 for lineage14.1
Thank You!
i want to Root LOS 14.1
is it the same way?? or should i do anything more??? !!
i am thinking of SystemRoot..
please give your suggestions ..
nandakis4 said:
i want to Root LOS 14.1
is it the same way?? or should i do anything more??? !!
i am thinking of SystemRoot..
please give your suggestions ..
Click to expand...
Click to collapse
LineageOs AdeenSu
Download And Flashing
Developer Setting>Root
@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release
Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
hendibudi said:
@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release
Click to expand...
Click to collapse
Why not fix it yourself?
hendibudi said:
@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release
Click to expand...
Click to collapse
They(boot.oat) are being generated automatically if you compile any custom rom.Home button wakes up the device, I won't disable that feature.It is useful for everyone.
ilmervanhattem said:
Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
Why not fix it yourself?
Click to expand...
Click to collapse
You don't have to format anything.Just make your wipes and flash it.
ilmervanhattem said:
Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
Why not fix it yourself?
Click to expand...
Click to collapse
I am sorry, i just junior member on xda, i didn't mean that, i just want to give little contribution to revive our community user p2 experience
WiFi is not working here...
When I turn on WiFi it turns off instantly...
Fawk
I've used the 'super' version of gapps for 7.1 (64bits) btw. Also tried it with TWRP 3.0.2.0 and the aroma installer of gapps, same WiFi error.
Hi there, i am thinking of buying this device for my gf because she needs something with a ****load of battery power. So this device seems the obvious choice. But i have a question:
i noticd that on every rom there is no led and no fingerprint. Is this something that will be added in the future or is it not possible due to unavailabe firmwares?
Kind regards
DDQW said:
Hi there, i am thinking of buying this device for my gf because she needs something with a ****load of battery power. So this device seems the obvious choice. But i have a question:
i noticd that on every rom there is no led and no fingerprint. Is this something that will be added in the future or is it not possible due to unavailabe firmwares?
Kind regards
Click to expand...
Click to collapse
I couldn't fix them, that's my fault.It is not caused by firmware or something.I don't know what will happen in the future.
ilmervanhattem said:
WiFi is not working here...
When I turn on WiFi it turns off instantly...
Fawk
I've used the 'super' version of gapps for 7.1 (64bits) btw.
Click to expand...
Click to collapse
Flash stock rom and use it for ten minutes, wipe data,system,cache,dalvik cache (don't wipe your internal storage, wiping it causes bugs.), then flash the rom.
wzedlare said:
Flash stock rom and use it for ten minutes, wipe data,system,cache,dalvik cache (don't wipe your internal storage, wiping it causes bugs.), then flash the rom.
Click to expand...
Click to collapse
OK my friend.
Got some error and passcode error when restoring. Will try some things and talk to you later.
UPDATE: wifi is working but have to root.
UPDATE: Rooted with version 2.79
UPDATE: Now restoring 484 apps with Titanium Backup
UPDATE: ROM is working smooth af, for how much I experienced by now
i was wondering why i couldnt get gapps to install , then realised i was trying to install the wrong version lol
The Mero said:
i was wondering why i couldnt get gapps to install , then realised i was trying to install the wrong version lol
Click to expand...
Click to collapse
7.1 > arm64 > choose whatever you want, pico is the smaller zip.
cpu-z is saying governor is stuck on performance .. constantly running at 2016mhz on all cores .
Is it possible to change it to dynamic ?
The Mero said:
cpu-z is saying governor is stuck on performance .. constantly running at 2016mhz on all cores .
Is it possible to change it to dynamic ?
Click to expand...
Click to collapse
Use a kernel editor?
which one would be safe / recommend to use ilmervanhattem ?
I wouldnt have a clue where to start ,

[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Storm

[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Storm
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on kipper
IF YOU ARE CURRENTLY RUNNING LINEAGE 15.1 w/ENCRYPTION A FULL DATA FORMAT WILL BE REQUIRED TO MOVE TO 16.0. AN ISSUE WITH ENCRYPTION WAS FOUND IN 15.1 THAT CANNOT BE CORRECTED WITHOUT A FULL FORMAT
Official Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want)
Changelog:
Changes for kipper
Bug reports:
How to submit a bug report
Donate to support development:
Donate via PayPal to jrior001
Donate via PayPal to LineageOS
XDA:DevDB Information
LineageOS, ROM for the Wileyfox Storm
Contributors
jrior001, mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2019-04-15
Last Updated 2019-04-15
great job
i haven't seen any problem on the first build
Brievly tested first build and not very good performance, i've not tested all things cause was laggy.
HUGE THANKS to compile android 9 ;D
---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------
RastHacker said:
Brievly tested first build and not very good performance, i've not tested all things cause was laggy.
HUGE THANKS to compile android 9 ;D
Click to expand...
Click to collapse
i'll continue to test and send feedback
I have testes android 9 on multiple devices like galaxy tab a, redmi 5 plus, one plus 5t and elderdriver's xposed work great but not on wileyfox storm. Someone can telle me why?
When i reboot with xposed installed it make a blackscreen but phone is booted.
RastHacker said:
I have testes android 9 on multiple devices like galaxy tab a, redmi 5 plus, one plus 5t and elderdriver's xposed work great but not on wileyfox storm. Someone can telle me why?
When i reboot with xposed installed it make a blackscreen but phone is booted.
Click to expand...
Click to collapse
did you Wipe and Format Data ?
Code:
Installing LineageOS from recovery
Wipe
Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
Return to the previous menu and tap Advanced Wipe.
Select the Cache and System partitions to be wiped and then Swipe to Wipe.
https://wiki.lineageos.org/devices/kipper/install
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
Changes included in lineage-16.0-20190507-nightly-kipper
Code:
RotationPolicy: Don't crash if configstore 1.1 isn't available
android_frameworks_base
I'll try
For some reasons, the /system partition is resized from ~2.5GB to ~1.5GB after install, so not even the nano-gapps fit (insufficient space).
The /system partition can be "resized" back to 2.5GB via TWRP (you have to do it twice(!) to see the result), but I think, this shouldn't be hard to fix...
ghertas said:
did you Wipe and Format Data ?
https://wiki.lineageos.org/devices/kipper/install
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
Changes included in lineage-16.0-20190507-nightly-kipper
Click to expand...
Click to collapse
Magisk say my data is not encrypted, i really need to format data?
After updating to "lineage-16.0-20190513-nightly-kipper", the /system partition was against decreased to ~ 1.5GB and had to be increased to 2.5GB from TWRP!
Screenshots:
Original size, before installing (or after resizing)
{
"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"
}
After installing LOS 16:
ghertas said:
my device couldn't find my tv via the cast
Click to expand...
Click to collapse
You're not connected to internet it's normal. Connect before to same wifi network as your tv
RastHacker said:
You're not connected to internet it's normal. Connect before to same wifi network as your tv
Click to expand...
Click to collapse
nothing
I can't find a refresh button to refresh the cast page to find my tv
i think the cast is not in the lineage rom package (kipper)
ghertas said:
nothing
I can't find a refresh button to refresh the cast page to find my tv
i think the cast is not in the lineage rom package (kipper)
Click to expand...
Click to collapse
You're tv created an other network named by your tv, it's look like "Bravia-XXXX" for sony and other for other brands. Connect to this network and now you can cast
ghertas said:
nothing
I can't find a refresh button to refresh the cast page to find my tv
i think the cast is not in the lineage rom package (kipper)
Click to expand...
Click to collapse
Wifi-direct casting does not work at all in 16.0 for most legacy devices. You can still cast to Chromecast devices but that's about it. Unfortunately I don't see this getting fixed at all as the back end for WFD changed quite a bit in P and only newer devices (with at least stock O blobs) have been able to get this working.
Sent from my Mi MIX 2S using Tapatalk
RastHacker said:
I have testes android 9 on multiple devices like galaxy tab a, redmi 5 plus, one plus 5t and elderdriver's xposed work great but not on wileyfox storm. Someone can telle me why?
When i reboot with xposed installed it make a blackscreen but phone is booted.
Click to expand...
Click to collapse
Hi,
have the same problem on my Wileyfox Storm (arm64-v8a) with Pie (OS only - no other apps installed jet) I installed.
I have testet every up to now available pie version for Storm.
Magsik v19.1 with Magisk Manager v7.1.2 (also tried v18.1 and v7.1.1)
Riru core 18 (also tried v10, v11, 15, 16)
EDXposed v4.1.2 (also tried v3.1.2, v3.1.7 and v2.9.6)
EdXposedInstaller_v2.2.4 (also tried some other Versions)
I also tried different Lineage Pie versions.
The Problem: immediatly after the boot is finished the ui becomes black and freezes completly.
For a second I could see the message Smartphone ist starting, but then it becomes black screen.
About very 5 seconds the screen flashes very short the status bar and becomes black again - seems to be a loop.
one Time, after wiping all partitions and installing lineage from scratch Xposed seems to be running fine,
but after the first boot I have the same problem.
In all cases - after removing EDXposed via TWRP Pie works fine again, but I need Xposed.
Please anybody can help?
Thanks
hjr06 said:
Hi,
have the same problem on my Wileyfox Storm (arm64-v8a) with Pie (OS only - no other apps installed jet) I installed.
I have testet every up to now available pie version for Storm.
Magsik v19.1 with Magisk Manager v7.1.2 (also tried v18.1 and v7.1.1)
Riru core 18 (also tried v10, v11, 15, 16)
EDXposed v4.1.2 (also tried v3.1.2, v3.1.7 and v2.9.6)
EdXposedInstaller_v2.2.4 (also tried some other Versions)
I also tried different Lineage Pie versions.
The Problem: immediatly after the boot is finished the ui becomes black and freezes completly.
For a second I could see the message Smartphone ist starting, but then it becomes black screen.
About very 5 seconds the screen flashes very short the status bar and becomes black again - seems to be a loop.
one Time, after wiping all partitions and installing lineage from scratch Xposed seems to be running fine,
but after the first boot I have the same problem.
In all cases - after removing EDXposed via TWRP Pie works fine again, but I need Xposed.
Please anybody can help?
Thanks
Click to expand...
Click to collapse
There is news, i finally booted with xposed 4.x elderdriver version sandhook, edxposed manager say it's working and active but any modules seems to work, they say 'module not active' even if it is. :/ and phone is laggy. (sorry for my english)
I can't install TWRP.
When I try to flash the image I get:
fastboot flash recovery twrp-3.2.3-20190306-kipper.img
target reported max download size of 268435456 bytes
sending 'recovery' (30096 KB)...
OKAY [ 0.976s]
writing 'recovery'...
OKAY [ 0.385s]
finished. total time: 1.361s
Which seems far too quick to transfer 30 Meg.
Then when I do <fastboot boot twrp-3.2.3-20190306-kipper.img>:
I get:downloading 'boot.img'...
OKAY [ 0.981s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.244s
I'd be grateful for some hand-holding, please!
Jim
vel_tins said:
For some reasons, the /system partition is resized from ~2.5GB to ~1.5GB after install, so not even the nano-gapps fit (insufficient space).
The /system partition can be "resized" back to 2.5GB via TWRP (you have to do it twice(!) to see the result), but I think, this shouldn't be hard to fix...
Click to expand...
Click to collapse
This doesn't work for me. I'm on TWRP 3.2.1.0 and whenever I let /system be resized, nothing changes.
The image has been installed by ADB Sideload. I also have rebooted the device to recovery multiple times, but the resize-operation doesn't show any results.
Sent from my Redmi Note 4 using Tapatalk
EDIT
The Download-Link does not work any more? Where can i download the latest ROM?
I get that its not supported any more, but thats no reason to remove old downloads.

[UNOFFICIAL] LineageOS 18.1 for Xiaomi Mi Note 10 Lite (toco)

{
"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"
}
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
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.
The device side sources can be found here:
android_kernel_xiaomi_sm6150
android_device_xiaomi_toco
android_device_xiaomi_sm6150-common
Installation
These Instructions are based on the LineageOS Wiki instructions.
Basic requirements​IMPORTANT: Please read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
Unlocking the bootloader​NOTE: The steps below only need to be run once per device.
WARNING: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
TIP: It is highly recommended to have the latest official MIUI package installed on the device, before proceeding with unlock.
NOTE: The following instructions require a machine running Windows 7 or newer.
Create a Mi account on Xiaomi’s website.
TIP: A Mi account is required to unlock the bootloader. Beware that one account is only allowed to unlock one unique device every 30 days.
Add a phone number to your Mi account.
Insert a SIM into your phone.
Enable developer options in Settings > About Phone by repeatedly tapping MIUI Version.
Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status.
Download the Mi Unlock app (Windows is required to run the app).
Run the Mi Unlock app and follow the instructions provided by the app.
NOTE: The app may tell you that you have to wait up to 30 days. If it does so, please wait the quoted amount of time before continuing to the next step.
After device and Mi account are successfully verified, the bootloader should be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Installing a custom recovery using fastboot​
Download a custom recovery - you can download the recommended lineage recovery here.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
TIP: If you see no permissions fastboot while on Linux or macOS, try running fastboot as root.
Flash recovery onto your device:
fastboot flash recovery <recovery_filename>.img
TIP: The file may not be named identically to what stands in this command, so adjust accordingly.
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar .. , fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Now reboot into recovery to verify the installation:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Installing LineageOS from recovery
Download the UNOFFICIAL LineageOS installation package for Xiaomi Mi Note 10 Lite (toco) that you would like to install or build the package yourself.
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Wipe.
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the previous menu and tap Advanced Wipe, then select the Cache partition and then Swipe to Wipe.
Sideload the LineageOS .zip package:
On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success.
(Optionally): If you want to install any add-ons, repeat the sideload steps above for those packages in sequence.
Once you have installed everything successfully, run ‘adb reboot’.
WARNING: Depending on which recovery you use, you may be prompted to install additional apps and services. We strongly advise you to opt out of installing these, as they may cause your device to bootloop, as well as attempt to access or corrupt your data.
Downloads
Download UNOFFICIAL LineageOS 18.1 for Xiaomi Mi Note 10 Lite.
Download UNOFFICIAL LineageOS recovery for Xiaomi Mi Note 10 Lite.
Donate to support development:
Donate via PayPal to NeoArian
Donate via PayPal to LineageOS
Note that these builds include Google Apps. A vanilla version will be available later.
This project does not rely on MIUI vendor, the vendor image is being built with the ROM and huge parts of it are being built from source.
Changelog
Here you can find all changelog's.
2021-05-20
Code:
* Fixed Dynamic system updates -> You can now launch the Android 12 DSU from developer settings (Note that it does not have much of the new design yet. If you look for that go for other GSIs).
* Update vendor security patch level to 2021-05-01
* Removed unused notification light settings
2021-05-18
Code:
* Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
* Fixed Microphone during calls
2021-05-14
Code:
* Fixed brightness during FOD
* Updated to may Android Security Bulletin
Great work! Thank you, Arian!
simplytb said:
Great work! Thank you, Arian!
Click to expand...
Click to collapse
I have uploaded a new build.
Download: https://sourceforge.net/projects/ep...ge-18.1-20210514-UNOFFICIAL-toco.zip/download
Changelog:
* Fixed brightness during FOD
* Updated to may Android Security Bulletin
Thanks for your work sir
Good job.
thanks!
Hi NeoArian problem with microphone
@NeoArian Hi! I tried the rom, and everything is great! thanks! But the rom has problems with the microphone seems to not be working properly. It doesn't work on the Phone dialer, but it works on video camera and other apps but with bad audio quality and low volume on the microphone. I decided not to go back to MIUI, cause this is way way better, so I'll just wait when the fix comes up. Cheers!
Good evening!
Thanks for the reports about the microphone issue. I have fixed it and uploaded a new build: https://sourceforge.net/projects/ep...ge-18.1-20210518-UNOFFICIAL-toco.zip/download
Changelog:
• Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
• Fixed Microphone during calls
Greetings, Arian.
Would it be possible to provide a list of the included Gapps?
Jisaka said:
Would it be possible to provide a list of the included Gapps?
Click to expand...
Click to collapse
Sure. My repository with the GApps can be found here.
The exact list of google apps can be found here. All the files from this list are extracted from the latest Google Pixel 5 factory image (which can be found here: https://developers.google.com/android/images).
NeoArian said:
Good evening!
Thanks for the reports about the microphone issue. I have fixed it and uploaded a new build: https://sourceforge.net/projects/ep...ge-18.1-20210518-UNOFFICIAL-toco.zip/download
Changelog:
• Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
• Fixed Microphone during calls
Greetings, Arian.
Click to expand...
Click to collapse
Thanks for the update @NeoArian! Everything works fine already. Thanks alot!
please users of this rom I have a question. does the fast charge function work? Thank you
MKey_CZ said:
please users of this rom I have a question. does the fast charge function work? Thank you
Click to expand...
Click to collapse
Good Morning,
Fast Charging does not work correctly. It's limited to 15-20W instead of the possible 30W. The bad thing about it is that xiaomi has been doing something in system which i'm not aware of currently. Fastcharging does not work at all with MIUI vendor + MIUI kernel with an AOSP system image, i have at least got to the same state with OSS kernel and built vendor image but i didn't figure out what unlocks the real fastcharging.
Greetings, Arian.
Good Evening.
I have uploaded a new build. https://sourceforge.net/projects/ep...ge-18.1-20210520-UNOFFICIAL-toco.zip/download
Changelog
* Fixed Dynamic system updates -> You can now launch the Android 12 DSU from developer settings (Note that it does not have much of the new design yet. If you look for that go for other GSIs).
* Update vendor security patch level to 2021-05-01
* Removed unused notification light settings
Greetings, Arian.
Thanx a lot for the effort but i have a qst do i have to reflash the phone for Every update toi make ? Or there IS another way to update thanx again
Aymenbekkari6s said:
Thanx a lot for the effort but i have a qst do i have to reflash the phone for Every update toi make ? Or there IS another way to update thanx again
Click to expand...
Click to collapse
You can flash the new updates without any wipes. Just go into recovery and flash the new zip. If you use lineage recovery connect your phone to your computer and use adb sideload.
I will setup automated weekly build with OTA functionality later.
NeoArian said:
You can flash the new updates without any wipes. Just go into recovery and flash the new zip. If you use lineage recovery connect your phone to your computer and use adb sideload.
I will setup automated weekly build with OTA functionality later.
Click to expand...
Click to collapse
Thanx bro ^^ do you suggest that i use TWRP or lineage recouvert ?
Aymenbekkari6s said:
Thanx bro ^^ do you suggest that i use TWRP or lineage recouvert ?
Click to expand...
Click to collapse
I would recommend lineage recovery if you are able to use ADB sideload to update. TWRP would probably also work fine but I did not confirm that.

[Beta] [11] ProjectSakura-x86 for PC's [OFFICIAL]

{
"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"
}
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.
This is an unofficial port of Project Sakura for PCs running x86 CPUs by using patches provided by Android-Generic project.
Made with Android-Generic v2.0 - Android for PCs & GSI devices
More detail : https://android-generic.github.io/
Code:
* Your warranty is now..... I don't know this is PCs ¯\_(ツ)_/¯
* It's very important to read the instructions and understand what you are doing. So please, READ !
* I am not responsible if you accidentally wiped your data on your hard drives or making your main OS like Windows unable to boot.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration."
Currently the best method I recommend to use is to dual-boot with a Linux distro, using its Grub2 bootloader to load the OS.You can check out BlissOS wiki or SupremeGamers wiki for the instruction.
Manual Install on Linux - Documentation
docs.blissos.org
Linux
Android-x86 is just a highly modified Linux. As a result, it has lot of similarities with Linux.
wiki.supreme-gamers.com
Alternatively, If you want to install using Windows
Advanced Android-x86 Installer - Knowledgebase
knowledgebase.blissos.org
Windows
Due to how Android-x86 is structured, it can be installed in any system.
wiki.supreme-gamers.com
For .rpm
Howto install Android X86 RPM images
I DON'T RECOMMEND TO FLASH ISO ON USB BECAUSE THE BOOTABLE INSTALLER IS HAVING PROBLEM.
Click Here
-Android-x86 Project
-BlissLabs (with works like BlissOS and Android-Generic)
-Lineage OS
-AOSP
-Superior OS
-AOSiP
-DerpFest
-Pixel Experience
-Extended UI
-Havoc OS
-CrDroid ROM
Project Sakura Source
The kernel source which I use for the build : https://github.com/hmtheboy154/Darkmatter-kernel
ProjectSakura-x86 Source which include all the changes for x86 will be available soon
ProjectSakura-x86 source : https://github.com/supremegamers/android/tree/sakura/11-x86/
Project Sakura's Telegram Group (if you want to feedback about the ROM)
BlissOS/ AG (x86/ x86_64) Telegram Group (if you need help installing or feedback about the PC builds)​
​This is a x86_64 build so please make sure your CPU support 64bit and SSE4.2
About bugs : Unlike Custom ROMs on phones where people can just put "You tell me", PC builds do have problem..... a lot.
- Not all the hardware will work perfectly or even supported (*cough Nvidia GPUs ).
- Screen Recording is not working yet (gbm_gralloc limitation)
- FaceUnlock is not working (and don't even hope it work)
- Bluetooth might not working yet.
- SwiftShader is broken so you can't boot with Software Rendering.
- For user using AMD GPUs (or APUs), there's graphic bugs when you have to choose default apps like for default launcher or default browser. Here's an explanation by Mauro Rossi - one of the member of Android-x86 Project :
A long standing issue is "the tiling artifacts" happening with gbm_gralloc at ResoverActivity window when SW write buffer used, one example is the launcher selector at first boot and another is visible with Chicken Invaders advertisements windows on SW write buffer
Intel i915 and i965 were not affected, while r300, r600, radeonsi and nouveau are all affected,
iris and crocus expected to not be affected, but I need to check.
Click to expand...
Click to collapse
So if you are seeing this (or worse) then it's the one I'm talking about.
(Iris and crocus actually not affected btw)
Update : Iris got reported to be affected, and there are some cases of crocus too. So I will mark this as a bug for both AMDGPUs and Intel iGPUs in general. If you want to read more about the bug, you can read this post by Mauro for more info
Project Sakura-x86 for PCs
Maintainer: HMTheBoy154
Build Type: Unofficial
ROM OS Version: 11.0 r40
ROM Kernel: Linux 5.10.61
ROM Firmware Required: Included in the build
Based On: LineageOS 18.1
Version Information
Status: Alpha
Current Stable Version: 5.R
SELinux Status : Permissive
Release Date: 2021-09-06
This is the first initial build which include FOSS pack from BlissOS. FOSS pack provide some FOSS application and also microG as the GMS replacement. Also here's what I put into the build :
- Mesa 21.2.1, libdrm 2.4.107 and LLVM12.0.1
- alsa-utils and alsa-lib are on version 1.2.5.1 with alsamixer tool
- My customized Kernel 5.10.61 which include patches from GoogleLTS (kernel/common android13-5.10 branch), xanmod and Android-x86 (More detail)
- AOSP SystemWebView got replaced with Bromite SystemWebView (big thanks to them for providing x86_64 builds)
- Using FakeStore 0.1.0 instead of 0.0.2 provided by FOSS package.
- Adding Open Camera since the stock Camera app is broken.
Here are some screenshot :
where is the famous xda bugs description " bugs ? You tell me "
Ni8 said:
where is the famous xda bugs description " bugs ? You tell me "
Click to expand...
Click to collapse
Pro :3
For anyone looking how to fix "serial console enabled, performance will be impacted" warning in notifications, here is how i fixed it.
Open termux, type following commands.
Bash:
su
nano /default.prop
Then edit ro.debuggable=1 to ro.debuggable=0 and press ctrl + x, save and exit.
alternatively,
Bash:
su -c 'sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop'
I installed it in my realme c2 and its working very fine.
New builds have been uploaded, here are the new changes :
- Upstream to September Security patch
- Update Mesa to 21.2.2
- Fixed broken Bluetooth (require restarting bluetooth app)
- Adding thermal-daemon from Project Celadon
- Adding Thermal HAL from Project Celadon
- Pull houdini and Widevine from ChromeOS 92 recovery file for hatch
- Now comes with both GMS and FOSS build
For bluetooth, just restart `com.android.bluetooth` by using `pm disable` then `pm enable` and then it will work if your card already recognized by Android-x86 before. I tested with a fake CSR card and it's running as expected.
By the way, I applied for ProjectSakura maintainer, both for PCs and Oneplus Nord So expect a new OFFICIAL build soon.
cjeu100 said:
For anyone looking how to fix "serial console enabled, performance will be impacted" warning in notifications, here is how i fixed it.
Open termux, type following commands.
Bash:
su
nano /default.prop
Then edit ro.debuggable=1 to ro.debuggable=0 and press ctrl + x, save and exit.
alternatively,
Bash:
su -c 'sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop'
Click to expand...
Click to collapse
NOPE! even with root is a read only filesys.
And the SED command returns formatting error as well.
Pleas share proper in depth steps if you might. thanks
joshyakadamien said:
NOPE! even with root is a read only filesys.
Click to expand...
Click to collapse
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
cjeu100 said:
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
Click to expand...
Click to collapse
Thanks, one Q though, if i installed the system as R/W then again i need to mount it as R/W?
joshyakadamien said:
Thanks, one Q though, if i installed the system as R/W then again i need to mount it as R/W?
Click to expand...
Click to collapse
Only in Android 11, you need to mount as r/w again, ro by default unlike previous versions of Android x86.
Hello! I use now the rom ProjectSakura-5.2-OpenGapps-pico-20210922-1750--UNOFFICIAL.iso
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Is anybody can help me?
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Veselchak787 said:
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Click to expand...
Click to collapse
Hello my Russian friend from 4pda.
We are also waiting for the update
One more question: how I can download files using build in this rom internet browser?
Veselchak787 said:
Hello! I use now the rom ProjectSakura-5.2-OpenGapps-pico-20210922-1750--UNOFFICIAL.iso
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Is anybody can help me?
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Click to expand...
Click to collapse
I just tested from the latest beta build I have here (haven't release it yet) and I do have the same problem, still don't know why, maybe I will take a look at it soon
But in the meantime, please try other Browsers that are not having any GMS-relation like Bromite or Firefox. I know that without sync will have some tough time to you, but those browsers are working well so far.
kamazok said:
Hello my Russian friend from 4pda.
We are also waiting for the update
Click to expand...
Click to collapse
I'm still planning for the new update tho, aiming for BoringDroid in the next version so we might have 4 Desktop Mode to choose. So I am waiting for utzcoz to fix it on newer security patch.
by the way, this thing is on 4PDA ???
We
HMTheBoy154 said:
this thing is on 4PDA ???
Click to expand...
Click to collapse
We are disсuss differen variants of Android x86.
Android OS на x86 - 4PDA
Android OS на x86, [androidPC]
4pda.to
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Click to expand...
Click to collapse
I'm rocking this on a HP Elitepad 1000 G2 with nice batt times
But in the meantime, please try other Browsers that are not having any GMS-relation like Bromite or Firefox. I know that without sync will have some tough time to you, but those browsers are working well so far.
Click to expand...
Click to collapse
Brave is stable for. ex.
cjeu100 said:
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
Click to expand...
Click to collapse
Thanks, did the trick.

[ROM][OFFICIAL][laurel_sprout] Syberia Project [12L][OSS]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* Syberia Team 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.
*/
Read the whole OP! Be respectful to each other and don't ask for ETAs, it's considered as being rude!
Syberia Project (aka Syberia OS) is a custom ROM for Xiaomi MI A3 that implements various features. This project was designed by our "Syberia Team" from scratch based on AOSP source code with some CAF fixes and improvements. Our team: @DennySPB, @blinoff82, @alexxxdev. Also many thanks to our designers @rlshukhov and @a18h for logos, wallpapers and bootanimations.
If you like our work you can buy us a cup of coffee or a glass of beer
Here
Code:
Monet
VoLTE, VoWiFi
LineageOS LiveDisplay
MicroG support
Pocket Judge
Call recording
Statusbar items switches
Three finger swipe to screenshot
Extended powermenu
...Settings and features will be gradually added.
SyberiaOS ROM Download
Recovery Download
Magisk Download
First time clean installation:
Code:
- Unlocked bootloader is required!
- You must have installed FW11 based ROM.
1 - Boot your device into fastboot mode:
adb reboot bootloader (or power off and power on again
while pressing Power + Vol Down)
2 - Flash Syberia recovery via fastboot
fastboot flash boot <name of the file>
3 - Reboot to recovery
4 - Perform factory reset (formatting data is important)
5 - Here you have 2 choices to install rom
1) Install > Sideload from ADB
on PC open terminal and type - adb sideload <rom zip name>
2) Install > install from sdcard or OTG
Just copy rom to the sdcard or OTG and install from it.
6 - Reboot to system, wait until rom booted, then reboot
in recovery again.
7 - Now you can install other zips (gapps, magisk etc) if needed by
using the methods described in the 5'th line of guide.
8 - If you flashed gapps, factory reset once more is a Must!
Updating:
Code:
1. Reboot into recovery
2. Here you have 2 choices to install rom
1) Install > Sideload from ADB
on PC open terminal and type - adb sideload <rom zip name>
2) Install > install from sdcard or OTG
Just copy rom to the sdcard or OTG and install from it.
3. Reboot to system
Code:
- You tell me only with logcat (screenshots)
Attention! We are not responsible for the operability of your device if you use third-party kernel, Xposed Framework or unverified Magisk modules.
Official website
Syberia Project Github
Syberia Project Gerrit
Device Source
Kernel Source
Official Telegram Group
Announcements Telegram Group
Development Telegram Group
Device Support Group
Code:
- LineageOS
- AOSPA (aka Paranoid Android)
- Nitrogen Project
- Benzo Rom
​
Update 11/07/2022
Changelog:
Fixed GPS logspam after caf update.
Updated GPS blobs to a12.
Updated GPS stack to LA.UM.9.11.r1-05600-NICOBAR.QSSI12.0
Ported DolbyAtmos from MOTO G PRO.
Implemented VPN tethering support.
Fixed QS clock size and placement.
Bring back "old" style QS brightness slider (temporary, until new style is fixed).
Spoiler: Archive
Update 30/06/2022
Changelog:
Removed mic boost.
VoiP changes.
Added keylayout for wired headphones.
Again increased haptics a bit.
Dropping prebuilt camera stack and building OSS camera stack.
Reworked Syberia UI Style.
Notes:
This build contains big changes for UI, so to avoid issues "clean flash" recommended
Update 01/06/2022
Changelog:
Implemented UDFPS dim layer (no brightness flicker)
Another VOiP fixes.
Added custom UDFPS animations and icons.
Added missing FM radio.
Increased haptics strength a bit.
Improved UDFPS scanning speed.
Update 17/04/2022
Changelog:
Improved boot time for ~3sec.
Fixed some system errors from log spam.
Added new NTP servers for faster Location.
Improved GPS stability and accuracy.
Enabled LiveDisplay HAL for picture adjustment.
Improved UDFPS callback delay’s.
Lowered size of UDFPS scan circle-point (theoretically this change should increase scanning speed but requires a good finger scan)
Imported from stock Health HAL (fixes charging calculations)
Upstreamed kernel to 4.14.275
Selinux Enforcing
Update 28/09/2021
Changelog:
Initial Build
Switched to ICE FBE encryption
Vendor updated to CAF LA.UM.9.11.r1-04500-NICOBAR.0 (except camera, audio, gps and DRM)
Switched to AOSP BT impl
Bugs:
Some modes in MIUI camera are not working
Reserved
This is fantastic!
But no matter what I do I can't install even core gapps. I flash them via adb sideload, perform a factory reset and nothing.. I feel like I've tried everything. There's no problem with Magisk tho. Can you please include some gapps in the rom?
Amazing news! Official ROM and latest Android version!
Hopefully the permissive SELinux can be sorted out with enough logs, but still, very nice work so far.
Does anyone can help me about the recovery via fastboot installation? I mean is there need to change slot e.t.c... And after recoverie's flashing, how we reboot to recovery, via a simple fastboot command?Thanks.
jeff.rey said:
This is fantastic!
But no matter what I do I can't install even core gapps. I flash them via adb sideload, perform a factory reset and nothing.. I feel like I've tried everything. There's no problem with Magisk tho. Can you please include some gapps in the rom?
Click to expand...
Click to collapse
Yeah, a12 not so fast at gapps bringup, we have limited chose to BitGapps, Nikgapps or FlameGapps, and Nikgapps with FlameGapps have some issues while flashing it on some devices (already reported to the dev), and only BitGapps works fine, but there are only Minimal package.
However i created a modified Nikgapps(stock) package - download
papafan said:
Does anyone can help me about the recovery via fastboot installation? I mean is there need to change slot e.t.c... And after recoverie's flashing, how we reboot to recovery, via a simple fastboot command?Thanks.
Click to expand...
Click to collapse
Generally speaking, IMHO doesn't matter how you got into recovery be it by command or power+vol+
maluus said:
Generally speaking, IMHO doesn't matter how you got into recovery be it by command or power+vol
Click to expand...
Click to collapse
And the slots? Is there any need to change them during flashing?
papafan said:
And the slots? Is there any need to change them during flashing?
Click to expand...
Click to collapse
When you flash something over fastboot you are to manage slots. When you do by recovery it manages slots. So up to flashing the recovery you'll manage slots. Afterwards flashes are done by recovery. Since recovery changes slots when you flash rom or update. Both slots should have the same firmware level (e.g. android 11 firmware.) If you have incompatible firmware on other slot it may cause problems on next update or full flash. IMHO op should explain a bit more about slot management. The same process is known to cause unwanted problems before. You can check the lineageos 18.1 oss thread for it.
Magicxavi said:
Update 28/09/2021
Changelog:
* Initial Build
* Switched to ICE FBE encryption
* Vendor updated to CAF LA.UM.9.11.r1-04500-NICOBAR.0 (except camera, audio, gps and DRM)
* Switched to AOSP BT impl
Bugs:
* Some modes in MIUI camera are not working
* Selinux Permissive
Click to expand...
Click to collapse
Hi,
Is it possible to safely install this ROM from android 10 stock EU version? (or, must I already be under A11 and in this case what should I do?)
I'm still stuck on A10 and the September 2020 security patch on my French version of the Mi A3
Sorry I'm a beginner
I think you must first update to a11. Do factory reset on your a10 first.
NikBos said:
I think you must first update to a11. Do factory reset on your a10 first.
Click to expand...
Click to collapse
Problem is that I still do not have the possibility to do OTA to A11...
In France we are literally blocked on A10 and the September 2020 security patch...
Then you can flash it with mi flash.
NikBos said:
Then you can flash it with mi flash.
Click to expand...
Click to collapse
I don't understand what to do in order not to lose my data, I would just like to update.
If I want to install the update without fear I have to make a backup. OK
To make a full backup I need TWRP. OK
To install TWRP to be able to make my backup and not lose any data I have to root my device with magisk. OK
If I root my device with magisk it makes me wipe all my data...
Hobbi1 said:
I don't understand what to do in order not to lose my data, I would just like to update.
If I want to install the update without fear I have to make a backup. OK
To make a full backup I need TWRP. OK
To install TWRP to be able to make my backup and not lose any data I have to root my device with magisk. OK
If I root my device with magisk it makes me wipe all my data...
Click to expand...
Click to collapse
If I were you I wouldn't rely on twrp for backup. Because once you update to A11 you ll have problem with twrp hence restoring it. On the other hand even if you are able to restore it somehow, probably you would end up with a bootloop anyway. Because when android version changes, data partition backup of other versions won't be compatible with newer one. I suggest you to have per app backup within os.
New update is out!
New update is out!
everything working fine, new icons and animations for udfps are pretty good and now it recognizes really fast. one thing i noticed is that the screen flicks when unlocking with figngerprint but just a little bit, its not something that really bothers as before. updating was fine without even needing to make a backup. anyways ty for, basically, the best rom for mi a3, if it wasnt that, i think we all would have already changed it. keep up the good work!
I just did the installation and the rom is fantastic!
Leaving Miui..
Everything seems to work very well.
Congratulations to those involved!!
Sorry for my english, I'm from Brazil

Categories

Resources