Related
Hello Friends
Finally i have done to release the Tab S system ui by me which is still work in progress
Instructions
1.copy and replace the system ui and set the permissions
2.open xposed app settings if using tab 4 7.0 or 8.0 search system ui and set dpi 190 and resolution to 1280×800.(tab 4 10.1 users skip this)
3.reboot
4.In build.prop find these lines and replace them to get s finder and quick connect toggles
Find my tab s quick connect and s finder thread to activate them
"ro.product.name=ktlexx"
"ro.product.device=ktle"
Press thanks if you appriciate my work
Bugs
1.unfinished toggles soon will be as original
2.performance while pull down because of transparent status bar icons
Can any one test that it works on tab 3 and note 8.0 please
omg system ui not working ?????????
how you got this to work?????
Go step by step i have done it 100 times while testing
does not work for me either did the steps many times as well , build prop changed cleared cache and davik too nothing just crashes my device sm-t530nu correct me if im wrong but doesn't the systemUI work with the framework? that maybe a problem idk im no dev lol
Did not work on my SM-T530 either. Oh well, luckily I did not have a need for it, just figured I would try to test it before other people wasted time trying it out.
Sorry bud, but yeah, it is a no go on the 10.1
Guys did u use xposed app settings before copying the system ui
It will not crash
Plz give me full instructions
Sent from my SM-T231 using XDA Free mobile app
How do i open the xposed settings? this doesnt come up as a module or anything and I accidentally deleted the regular system ui so im kinda ****ed right now. It wont even boot. Bro.v
CTH*ABH* said:
How do i open the xposed settings? this doesnt come up as a module or anything and I accidentally deleted the regular system ui so im kinda ****ed right now. It wont even boot. Bro.v
Click to expand...
Click to collapse
If the system ui is deleted it should boot black background but it should boot... in anycase you made a nandroid backup before editing system files right?
zach61797 said:
If the system ui is deleted it should boot black background but it should boot... in anycase you made a nandroid backup before editing system files right?
Click to expand...
Click to collapse
No that didn't really even cross my mind. Any place I can download the old file?
CTH*ABH* said:
No that didn't really even cross my mind. Any place I can download the old file?
Click to expand...
Click to collapse
there are stock roms in android development download one and pull it from there or just flash it
zach61797 said:
there are stock roms in android development download one and pull it from there or just flash it
Click to expand...
Click to collapse
thanks man
note 10.1 2012
so will it work for note 10.1 2012
Worked for me!! True guide for tab 4 7.0 wifi:
1. Download the tab s system ui that is on this thread.
2. Download app settings from xposed installer if you dont have it already and activate it.
3. In app settings, scroll down until you locate system ui.
4. Change DPI to 205 and change screen (dp) to 1280x800.
5. Reboot to twrp. MAKE A BACKUP IF ANYTHING GOES WRONG.
6. Go to twrp/aroma file manager and locate the downloaded system ui.
7. Select "Copy". Then go to /system/priv-app and paste it.
8. It prompts you to overwrite the existing system ui. Press " Overwrite".
9. After that is done reboot. You should now have a working tab s system ui!!
Hit the thanks button if I helped
AhmedSafian said:
so will it work for note 10.1 2012
Click to expand...
Click to collapse
No lol, tab 4 only.
Val35353vr said:
Worked for me!! True guide for tab 4 7.0 wifi:
1. Download the tab s system ui that is on this thread.
2. Download app settings from xposed installer if you dont have it already and activate it.
3. In app settings, scroll down until you locate system ui.
4. Change DPI to 205 and change screen (dp) to 1280x800.
5. Reboot to twrp. MAKE A BACKUP IF ANYTHING GOES WRONG.
6. Go to twrp/aroma file manager and locate the downloaded system ui.
7. Select "Copy". Then go to /system/priv-app and paste it.
8. It prompts you to overwrite the existing system ui. Press " Overwrite".
9. After that is done reboot. You should now have a working tab s system ui!!
Hit the thanks button if I helped
Click to expand...
Click to collapse
That's surely the right way!
If you change directly SystemUi.apk with a root explorer, your device becomes instantly unusable, you can't even change permissions.
At least, it's my experience with other devices.
aftnoon2 said:
That's surely the right way!
If you change directly SystemUi.apk with a root explorer, your device becomes instantly unusable, you can't even change permissions.
At least, it's my experience with other devices.
Click to expand...
Click to collapse
Yup. Usually modifying critical files on the /system partition is best in the twrp recovery file manager to avoid crashes and malfunctions and all that other craZy stuff.
If you've used Android N-ify with Good Lock, you will have known that there's an annoying bug, that the Good Lock settings icon overlaps the alarm section when the Quick Settings is expanded.
This will fix that, and fix up a few things in Good Lock to match AOSP/Google Pixel visuals
Screenshots in attachments.
Should be supported on any Samsung device on a Touchwiz-based 6.0/6.0.1 Marshmallow ROM (7.0 Nougat or newer is unsupported, you can use this Substratum theme instead which makes your SystemUI more AOSP-like!)
Will update this modified Good Lock accordingly as Good Lock itself recieves updates as well.
Changelog
v2
IMPORTANT: you must go and follow this, even if you already installed the previous version, just this one time. Added proper install instructions in the OP, shouldn't have any issues with installing now (read below)
Removed charging/wireless charging water splash animations
Changed default lockscreen wallpaper to stock Google Pixel wallpaper
v1
Removed Good Lock settings icon in quick settings header, to not overlap alarm icon in Android N-ify's quick settings header (still clickable where it was to access Good Lock settings)
Changed auto brightness icon in quick settings header to AOSP style
Changed screenshot notification icon to AOSP style
Changed Good Lock app icon to AOSP Nougat's SystemUI icon
Install instructions
If you are using stock Good Lock, or if you are on the first release of the modified Good Lock, follow the instructions ahead. If you haven't installed any Good Lock, skip to Step 4. Otherwise, if you're on v2 or later of modified Good Lock, and are just updating, skip to Step 6
Disable Android N-ify and GravityBox in Xposed Installer, and reboot
Uninstall Good Lock normally from the app (optional: backup Good Lock data)
Go to /data/app/ in your favourite root file manager, and delete any "com.android.systemui-#" folders (# is substituted with a number)
Install stock Good Lock again
Flash the modified Good Lock zip in TWRP
Enable Android N-ify and GravityBox
Enjoy (optional: restore Good Lock data)
Download
Realy great, works a lot better. Thank you mate. :good:
Great work bro
It doesn't seem to get installed when I flash it, I tried with and without Good Lock installed but it had the same effect. S7 Flat on Superman Rom 1.19
DarkboyZX said:
It doesn't seem to get installed when I flash it, I tried with and without Good Lock installed but it had the same effect. S7 Flat on Superman Rom 1.19
Click to expand...
Click to collapse
Yes, the ZIP does not work if you try to flash it before installing GoodLock and N-ify. It is recommended that you wipe and reflash the system partition after uninstalling N-ify and GoodLock, and then install GoodLock and N-ify -> reboot once -> flash the ZIP through recovery.
New update!
v2
IMPORTANT: you must go and follow this, even if you already installed the previous version, just this one time. Added proper install instructions in the OP, shouldn't have any issues with installing now (read below)
Removed charging/wireless charging water splash animations
Changed default lockscreen wallpaper to stock Google Pixel wallpaper
DarkboyZX said:
It doesn't seem to get installed when I flash it, I tried with and without Good Lock installed but it had the same effect. S7 Flat on Superman Rom 1.19
Click to expand...
Click to collapse
Follow the new install instructions, it should work now.
Is it possible to for the QS panel to be bluish-greyish, like on AOSP?
Since right now, it is completely black.
moriel5 said:
Is it possible to for the QS panel to be bluish-greyish, like on AOSP?
Since right now, it is completely black.
Click to expand...
Click to collapse
Yes it is.
In Good Lock routines editor, on the section where you pick theme colours, you can try and pick the blue-greyish colour for the first hexagon to the left, then your QS panel background colour will be set accordingly.
OhayouBaka said:
Yes it is.
In Good Lock routines editor, on the section where you pick theme colours, you can try and pick the blue-greyish colour for the first hexagon to the left, then your QS panel background colour will be set accordingly.
Click to expand...
Click to collapse
Thanks, I haven't installed your modified Good Lock yet on my father's phone (I don't use TouchWiz, however I was unable for some reason to boot CM12.1 on his phone (when there will be enough time, I will try CM13, or whatever will exist then)) since I thought that the colors will be too jarring for him.
When I'll have time, I'll install your modified Good Lock on his phone.
Is there a way to get a gap between the notifications?
Done
Sent from my hero2lte using XDA Labs
..
Hello,
First of all, thanks for the mod! Developpers like you are great, and add something to the community! Thanks.
Getting to the question. I know it may sound stupid, but this is supposed to make Good Lock work with Android N-ify. But I don't know when I should instal android n-ify. Should I install Good Lock (fresh install), flash your GoodLock v2 zip, and then install Android N-ify module through Xposed? Or do I not need to install the Android N-ify module?
Thanks in advance for the clarification. Cheers!
CamilleBC said:
Hello,
First of all, thanks for the mod! Developpers like you are great, and add something to the community! Thanks.
Getting to the question. I know it may sound stupid, but this is supposed to make Good Lock work with Android N-ify. But I don't know when I should instal android n-ify. Should I install Good Lock (fresh install), flash your GoodLock v2 zip, and then install Android N-ify module through Xposed? Or do I not need to install the Android N-ify module?
Thanks in advance for the clarification. Cheers!
Click to expand...
Click to collapse
Yep, you install android n-ify and gravitybox after you flash the good lock zip.
OhayouBaka said:
Yep, you install android n-ify and gravitybox after you flash the good lock zip.
Click to expand...
Click to collapse
Well thanks for the answer.
I followed the procedure, installed Good Lock, then flashed your zip, then installed Android N-ify 0.2 and Gravity Box, but the navigation panel still looks like the original Good Lock panel (I don't see neither Android N-ify effect, nor your Good Lock).
Don't know what I did wrong, but too bad for me.
Thanks for the help anyway !
CamilleBC said:
Well thanks for the answer.
I followed the procedure, installed Good Lock, then flashed your zip, then installed Android N-ify 0.2 and Gravity Box, but the navigation panel still looks like the original Good Lock panel (I don't see neither Android N-ify effect, nor your Good Lock).
Don't know what I did wrong, but too bad for me.
Thanks for the help anyway !
Click to expand...
Click to collapse
N-ify 0.2 on the xposed repo is really old, you want the latest build from https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/
Also if installing my good lock made no difference, manually copy out the base.apk from the zip into /data/app/com.android.systemui-1, give -rw-r-r permissions and reboot
OhayouBaka said:
N-ify 0.2 on the xposed repo is really old, you want the latest build from https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/
Also if installing my good lock made no difference, manually copy out the base.apk from the zip into /data/app/com.android.systemui-1, give -rw-r-r permissions and reboot
Click to expand...
Click to collapse
I tried as well, but it seems I can't get Android N-ify to work on my S7 Edge. It probably isn't related to your mod.
Thanks for the help! :good:
CamilleBC said:
I tried as well, but it seems I can't get Android N-ify to work on my S7 Edge. It probably isn't related to your mod.
Thanks for the help! :good:
Click to expand...
Click to collapse
No problem
Scratch that. Think it's a bug with the version of N-ify I'm using nevermind!
CloudyxVision13 said:
Scratch that. Think it's a bug with the version of N-ify I'm using nevermind!
Click to expand...
Click to collapse
The same thing happens to me when I use the latest version of N-ify from jenkins. However it doesn't do the same with version 0.20 from xposed, but It doesn't look as good as the screenshots in the OP.
Hi im not developer
I just here provide you information to run Google camera App which can Produce HDR and Portrait Images in Note 5, even far better from Stock cam.
If something goes wrong, im not responsible for that damages...
First You need root access and Nougat + magisk Sorry MM user
--> You need to add camera2api in build.prop
Download camera2api Enabler from this thread and flash it >> https://forum.xda-developers.com/apps/magisk/module-camera2api-enabler-t3656651
[OR]
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1"
Reboot Phone
Now download this Google Camera App >> Click here
Then open app and give some permission
Now you need to do some setting in app, follow the screenshot >> https://postimg.org/gallery/1qi5mrgxo/
then close app/force stop app and reopen to apply those modifications
Enjoy
Credit:
BSG
SERJO87
Note:
After using google camera app, your stock camera app may not work properly, but who cares
Nice bro thanks
May there is a bug in "api2enabler"
When I flashed the api2enabler amd rebooted the device, it stuck on the boot screen and never booted untill I reflashed the stock.
So is there any solution ??
Pranay Deep said:
When I flashed the api2enabler amd rebooted the device, it stuck on the boot screen and never booted untill I reflashed the stock.
So is there any solution ??
Click to expand...
Click to collapse
maybe you downloaded wrong zip
Code:
[OR]
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1"
Reboot Phone
Pranay Deep said:
When I flashed the api2enabler amd rebooted the device, it stuck on the boot screen and never booted untill I reflashed the stock.
So is there any solution ??
Click to expand...
Click to collapse
download build prop editor and input
"persist.camera.HAL3.enabled=1"
line
tcpcd said:
Hi im not developer
I just here provide you information to run Google camera App which can Produce HDR and Portrait Images in Note 5, even far better from Stock cam.
If something goes wrong, im not responsible for that damages...
First You need root access and Nougat + magisk Sorry MM user
--> You need to add camera2api in build.prop
Download camera2api Enabler from this thread and flash it >> https://forum.xda-developers.com/apps/magisk/module-camera2api-enabler-t3656651
[OR]
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1"
Reboot Phone
Now download this Google Camera App >> Click here
Then open app and give some permission
Now you need to do some setting in app, follow the screenshot >> https://postimg.org/gallery/1qi5mrgxo/
then close app/force stop app and reopen to apply those modifications
Enjoy
Credit:
BSG
SERJO87
Note:
After using google camera app, your stock camera app may not work properly, but who cares
Click to expand...
Click to collapse
Now you need to do some setting in app, follow the screenshot: https://postimg.cc/gallery/1qi5mrgxo/
Google camera stopped working
After installing Google camera working stopped in Rooted Nougat
Now working fine
Siva creed said:
After installing Google camera working stopped in Rooted Nougat
Click to expand...
Click to collapse
Thanks for this thread
Hi everyone,
After installing EMUI 9 (.241) on my P20 Pro & switching to Lawnchair V2, I was happy with pretty much everything except EMUI's default app switcher (Recents Screen). It's bug ridden & lags way too much for usability. That was when I decided to try QuickSwitch Magisk module from @Skittles9823 & @paphonb . Unfortunately, it didn't work for EMUI 9 & I decided to dig further into it.
Background Info:
In Android Pie, "recents screen" feature is handled by the launcher & is no more part of the OS itself. Android OS triggers recents screen by starting an intent "android.intent.action.QUICKSTEP_SERVICE" which is bound to the default launcher. What this means is that only the application specified in the intent can receive it. Now, in case of most OEM roms, this value is defined inside an XML resource in "/system/framework/framework-res.apk" (the file name can be different for different roms) file. QuickSwitch Magisk module apparently replaces this value using "Runtime Resource Overlay" technique to setup any launcher of your choice as the default handler for recents screen or QUICKSTEP as it's called.
Huawei, you bad boy
In EMUI 9, instead of defining this value inside some xml resource, Huawei decided to create a jar file instead named "hwServices.jar" & hardcoded EMUI launcher's package name in a "String" variable to be used for triggering the QUICKSTEP intent. This effectively kills the approach taken by QuickSwitch magisk module & us Huawei device owners are left with no other option but EMUI 9's bad implementation.
The way around
There are couple of options in this case:
Patch "hwServices.jar" file to point so some 3rd party launcher
Remove default EMUI launcher, create an application with the same package name to relay QUICKSTEP intent between system & third party launchers
Remove default EMUI launcher & replace it with a third party launcher that's modified to have EMUI's default launcher's package name
After spending the entire weekend trying Option 2 with limited success, I decided to go for Option 3 as modifying "hwServices.jar" itself seemed like too much meddling with the system's functioning. And so I removed default EMUI launcher from my system, took the latest Lawnchair v2's alpha build, patched it to have EMUI's default launcher's package name & installed it instead with system permissions. This works like a charm!
Instructions
You need a rooted device with Magisk installed
Install (QuickSwitch Magisk module v1.1.2)
Delete "/system/app/HwLauncher6" folder's contents using some file-manager like ES explorer with root permissions ( Create a backup if you want, it can be restored by copying the files back in the same folder if needed)
Reboot phone
Install patched Lawnchair V2's apk attached to this post on your phone.
Using QuickSwitch app installed on your phone, select Lawnchair V2 as the default home app & QuickStep provider. (We are using QuickSwitch only to give our patched Lawnchair v2 app system privileges. If you have any other way of doing this, feel free to do so & you can ignore installing QuickSwitch & it's steps above entirely)
Reboot & everything should be setup correctly.
Note
The patched version of Lawnchair v2 attached here is based on the latest alpha build at the time of this post& although everything seems to be working just great, there might be few bugs here & there. I'll update the attachment as & when more stable versions are released.
Credits
Special thanks to both @Skittles9823 & @paphonb for interacting with me while I was trying to find a way to get this working on EMUI. Much appreciated!
Update 1
The patched version of Lawnchair attached isn't entirely perfect, I'll wait for it's source code to be released to refactor everything properly. Until then, you can use this to replace your existing recents screen & even use a different launcher along with it, as long as attached Lawnchair V2 is a system app.
Update 2
Have also added OnePlus's Launcher ported by Paphonb with patch for EMUI 9. You can use this one instead of Lawnchair V2 too, if you like. Kindly note that these might be unstable due to my patches.
Update 3
Have updated the attached Lawnchair v2 apk with patch v1.1 (Fixes crashes)
Latest build download for Lawnchair V2
You should find fairly recent builds of Lawnchair V2 patched for EMUI here: (To be updated soon!)
Hi. Thank you for the tutorial. The problem is that when I try to install the lawnchair apk I get "app not installed" error.
My bad. I had to remove huawei launcher first.
It works perfectly. Thanks so much.
abyssq said:
Hi. Thank you for the tutorial. The problem is that when I try to install the lawnchair apk I get "app not installed" error.
My bad. I had to remove huawei launcher first.
It works perfectly. Thanks so much.
Click to expand...
Click to collapse
I know its for rooted emui 9. Is there a possible way for non rooted. Just asking.
papoy1019 said:
I know its for rooted emui 9. Is there a possible way for non rooted. Just asking.
Click to expand...
Click to collapse
With this method definitely not. Maybe in the future huawei will do a better implementation for this, but not today.
abyssq said:
With this method definitely not. Maybe in the future huawei will do a better implementation for this, but not today.
Click to expand...
Click to collapse
I agree. For now, it's not possible without root, unfortunately.
abyssq said:
Hi. Thank you for the tutorial. The problem is that when I try to install the lawnchair apk I get "app not installed" error.
My bad. I had to remove huawei launcher first.
It works perfectly. Thanks so much.
Click to expand...
Click to collapse
Glad to hear that.
is it possible with adb?
Delete it.
moomoon03 said:
is it possible with adb?
Click to expand...
Click to collapse
Only if you're rooted.
Sent from my LGE Nexus 5X using XDA Labs
With emui 9 gestures, swipe up to home only shows recents.
With lawnchair, the apps and folders have different fonts. The folder font is my system default. Why is this?
abyssq said:
With lawnchair, the apps and folders have different fonts. The folder font is my system default. Why is this?
Click to expand...
Click to collapse
You were the lucky one to try this on April Fool's day unfortunately where they changed font as prank. Should be back to system font by 2nd or you can go change it in the 3 dot menu in settings.
Aodrulez said:
You were the lucky one to try this on April Fool's day unfortunately where they changed font as prank. Should be back to system font by 2nd or you can go change it in the 3 dot menu in settings.
Click to expand...
Click to collapse
OMG thanks. I looked everywhere and couldn't figure it out. :silly::laugh:
good work!thx
wonder how you modified to have EMUI's default launcher's package name,if you are okay to tell?
just want to get more recent update and add more third party launcher to choose
psrvi7 said:
good work!thx
wonder how you modified to have EMUI's default launcher's package name,if you are okay to tell?
just want to get more recent update and add more third party launcher to choose
Click to expand...
Click to collapse
Easiest way: In Android Manifest file, replace package name to "com.huawei.android.launcher". This works so far for Lawnchair V2 & ported OP Launcher.
Proper way: Download source, refactor code with new package name & compile. This is tedious and am not sure how reliably can be automated.
Aodrulez said:
Easiest way: In Android Manifest file, replace package name to "com.huawei.android.launcher". This works so far for Lawnchair V2 & ported OP Launcher.
Proper way: Download source, refactor code with new package name & compile. This is tedious and am not sure how reliably can be automated.
Click to expand...
Click to collapse
it actually worked.thx again
Hi there, I was wondering to know if it's possible to do this with any launcher, because I wanna try Asus and Samsung launcher
Theo1218 said:
Hi there, I was wondering to know if it's possible to do this with any launcher, because I wanna try Asus and Samsung launcher
Click to expand...
Click to collapse
Should work with any Launcher that provides QuickStep functionality as long as it works without crashing before it's package is renamed.
Aodrulez said:
Should work with any Launcher that provides QuickStep functionality as long as it works without crashing before it's package is renamed.
Click to expand...
Click to collapse
tried with latest lawnchair but it didn't work, wich tool do you use for changing package name?
Theo1218 said:
tried with latest lawnchair but it didn't work, wich tool do you use for changing package name?
Click to expand...
Click to collapse
There is no tool that'll do it automatically for you. I use apktool to dismantle the apk, change values & repackage it. You'll also have to sign the package using "jarsigner" which comes along with JDK.
I'm not responsible for any damage to your device of any sort.
By flashing this, you take responsibility of anything that happens.
Process at your own risk!
If you want to check - please make backup. Better to store all partitions.
What works
audio
bluetooth
brightness
camera
DRM
OTA
selinux
video
wifi
wifi display (fixed at build 20220830)
What doesn't work
Torch QS not working -> regression in 0903, fixed in 0904
Back camera preview : wrong rotation on preview in default app, open camera works (fixed at build 20220903)
Some Keyboard bug. Workaround : When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
Instructions:
0. Patched TWRP for FOTA
1. Factory reset if coming from another ROM.
2. Install ROM
3. Install GApps (optionally) [Recommended NickGapps Patched for ARM]
4. Install Magisk 25.2 (optionally)
Sources & Changes:
Device tree
Kernel tree
Vendor tree
TWRP tree
Download:
Downloads: builds
Note to users: I'm not responsible if you brick your tablet. See the disclaimer above.
Contributors
LineageOS team for source code.
@retiredtab for helping make mondrianwifi to work on Android12
@khalvat for its work on porting msm8974 to Android12 (https://github.com/LineageOS-UL)
@pocketrule, @bierma32, @Yxo 6o6uka for willing to test builds and leaving feedback
ROM OS Version: 12.1
Version Information
Status: Nightlies
Created 2022-08-28
Last Updated 2022-09-04
Wow! We can get Android 12 for such an old device. Many thanks to dev who keep it alive. With LOS 19 announcement I thought for devices with old kernel A12 is not possible. Miracle!
phoval said:
1. Factory reset if coming from another ROM.
Click to expand...
Click to collapse
Can we upgrade from your Los 18, or still need to reset no matter what?
mrmathematica said:
Wow! We can get Android 12 for such an old device. Many thanks to dev who keep it alive. With LOS 19 announcement I thought for devices with old kernel A12 is not possible. Miracle!
Click to expand...
Click to collapse
eBPF is mandatory for android 12, but you can disable it in the code.
Some things will be broken, eg: trafic monitor
mrmathematica said:
Can we upgrade from your Los 18, or still need to reset no matter what?
Click to expand...
Click to collapse
I didn't try myself, done a clean install. You can try, but make backup before.
Format system if you have gapps, install rom zip and gapps for 12.
New build up, wifi display lag is fixed. Casting is smooth with audio.
Updated my Tab over OTA to latest Version , it works perfect with your patched TWRP.
Excellent news!!
Thank you very much!!
I will try and report soon!!
george stamatos said:
Excellent news!!
Thank you very much!!
I will try and report soon!!
Click to expand...
Click to collapse
Create an backup, in case something go wrong.
I prefere an clean install.
Exciting, I'll try it tomorrow. Hope I can connect wifi .
I can't turn it off, please guide me to turn it off.
duc12323 said:
I can't turn it off, please guide me to turn it off.
Click to expand...
Click to collapse
Disabling the task bar:
Settings -> System -> Buttons -> enable nav bar -> go back -> Buttons -> disable task bar and nav bar
Nice work, thanks for A12.
Thank you @phoval
Great rom, mostly working fine with a dirty flash. A few issues though:
Taskbar shows on lock screen, hiding "swipe up to open" and generally not looking good
Lock screen cannot be landscape
Flashlight quick setting says camera in use
Quick settings menu laggy in portrait.
PiP to splitscreen button missing. Apparently removed in beta 3 https://9to5google.com/2022/02/09/android-12l-beta-3-new-features/
Craftyawesome said:
Great rom, mostly working fine with a dirty flash. A few issues though:
Taskbar shows on lock screen, hiding "swipe up to open" and generally not looking good
Lock screen cannot be landscape
Flashlight quick setting says camera in use
Quick settings menu laggy in portrait.
PiP to splitscreen button missing.
Click to expand...
Click to collapse
Taskbar not showing on lockscreen for me If I enabled it, but I don't use it.
Lock screen can be rotated but the option must be enabled: Settings -> Display > Rotation Settings
Flashlight QS was working early build: Will check why not working anymore.
QS is a bit laggy in portrait: dunno why.
What is PiP to splitscreen? In task view, there is a button to splitscreen.
phoval said:
Taskbar not showing on lockscreen for me If I enabled it, but I don't use it.
Lock screen can be rotated but the option must be enabled: Settings -> Display > Rotation Settings
Flashlight QS was working early build: Will check why not working anymore.
QS is a bit laggy in portrait: dunno why.
What is PiP to splitscreen? In task view, there is a button to splitscreen.
Click to expand...
Click to collapse
Thanks for the reply, I will check that option.
It looks like the picture in picture player should have an option to directly load split screen. https://www.xda-developers.com/andr...-picture-in-picture-window-double-line-clock/
I'm assuming it made it into final though, I don't have a real 12L device.
Apparently removed in beta 3 https://9to5google.com/2022/02/09/android-12l-beta-3-new-features/
Flash QS is fixed in build 4th sept.
Some commits were missing on last build.
I removed 3rd build from listing (zip in old)
I recommend upgrade to 4th if you are on the 3rd
Great job and example of sustainability!
I made clean install with lineage bootloader.
OTA works
I was only able to install with mindthegapps, the rest failed during installation and Nikgapps did not start the Google assistant. Maybe issue between arm and arm64 gapps
Keep going your work!
Hi!
This rom does ram plus?
Thank you for your effort!
pocketrule said:
Disabling the task bar:
Settings -> System -> Buttons -> enable nav bar -> go back -> Buttons -> disable task bar and nav bar
Click to expand...
Click to collapse
For me this doesn't work. Any other suggestions?