MARS SOM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first so called SOM
Systemless-On-Memory
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 12 GSI (Pixel Expierence)
[Preferred ARM64 A/B VNDKLITE]
Downloads:
Dev Ice Technologies
WELCOME
sites.google.com
Non GSI related Bugs:
Report them if You found one!
Donations:
paypal.me/miustone
Instructions can be found in the README on GitHub: https://github.com/Miustone/MARS_SOM
since gestures dont work does this mean we have to use the 3 button layout? Also, thank you for your work mate! Im pumped to try out the ROM
eqbirvin said:
since gestures dont work does this mean we have to use the 3 button layout? Also, thank you for your work mate! Im pumped to try out the ROM
Click to expand...
Click to collapse
Right. I can also recommend Fluid Navigations Gestures from the Play Store. Hope to fix this soon... Sorry for that!
Hope You will enjoy it anyways
Gestures worked for me on the .25 update! But I had to set the pixel launcher as default home manually! However, I just clean flashed and everything to update to the .51 update and the SOM causes bootloops on the .51. Did you get it running on .51 or just .25 so far?
Miustone said:
Right. I can also recommend Fluid Navigations Gestures from the Play Store. Hope to fix this soon... Sorry for that!
Hope You will enjoy it anyways
Click to expand...
Click to collapse
Thanks for putting this together! I'm not familiar with Gcam (Been a while since I last rooted) but does using this "SOM" mean if I install it I can use Gcam? Or does other development have to be done?
eqbirvin said:
Gestures worked for me on the .25 update! But I had to set the pixel launcher as default home manually! However, I just clean flashed and everything to update to the .51 update and the SOM causes bootloops on the .51. Did you get it running on .51 or just .25 so far?
Click to expand...
Click to collapse
Well, Bootloops shouldn't happen with newer Firmwares. Sounds Like SONY has changed Something bigger... I need to take a look
TripodKnight said:
Thanks for putting this together! I'm not familiar with Gcam (Been a while since I last rooted) but does using this "SOM" mean if I install it I can use Gcam? Or does other development have to be done?
Click to expand...
Click to collapse
You're Welcome! Actually am i struggling with GCAM Support. I have much Expierence with Camera related Things but SONY really screwed it Up since the 2019 Xperias (Maybe already on the 2018s which i havent used). 2021 could be anyways the Year i can fix it with Android 11. Fingers crossed!
Btw. actually will GCam Ports never be able to deliver a truely benefit over the SONY Cam since porting the APK only means bypasses and Tricks to make it Work (different to what i am doing). Just Take a look on the Pixel Expierence which is actually on the 2019 Xperias allowing to use any GCam Ports. Sadly i haven't found the Reason for this yet. Maybe i missed some libs or so. We'll See
Miustone said:
Instructions can be found in the README on GitHub: https://github.com/Miustone/MARS_SOM
Click to expand...
Click to collapse
Thank you so much for making this, I thought we would never see a ROM for our phone.
I want to try it but I have a few questions about this, if you don't mind and find the time. Is this kind of rom common for all devices? The same files are used on xperia and pixel phones for example? Changing the "fingerprint" of the device means that it will be recognized as a pixel device (build.prop etc)? Will that cause issues with the sony exclusive apps that are not supported on other devices?
Gestures only work with default launcher, it is a known android limitation. When I installed nova launcher I was greated with a pop up about this. Android 11 should fix it.
palamosteliaro said:
Thank you so much for making this, I thought we would never see a ROM for our phone.
I want to try it but I have a few questions about this, if you don't mind and find the time. Is this kind of rom common for all devices? The same files are used on xperia and pixel phones for example? Changing the "fingerprint" of the device means that it will be recognized as a pixel device (build.prop etc)? Will that cause issues with the sony exclusive apps that are not supported on other devices?
Click to expand...
Click to collapse
All Apps should Work fine so far. But You will notice that there are almost No SONY Apps left.
My ROMs are only working on the 2019 and 2020 Xperia Flagships, other Devices would need different Configs from Me, but Yes. I'm using non edited Pixel Firmwares for My ROMs, means You will use original Pixel 4 XL or 5 Files on Android 10-11. I'm the only one on XDA who works Like that as far as i know... Hope You will like it too Have fun!
SeriousFlash said:
Gestures only work with default launcher, it is a known android limitation. When I installed nova launcher I was greated with a pop up about this. Android 11 should fix it.
Click to expand...
Click to collapse
High hopes for Android 11! Since i have still the Xperia 5 do i need to wait some longer... But i'm prepared for it Pixel 5 Firmwares are already Explored from Me
SeriousFlash said:
Gestures only work with default launcher, it is a known android limitation. When I installed nova launcher I was greated with a pop up about this. Android 11 should fix it.
Click to expand...
Click to collapse
Any indication that'll happen for sure? Sony plans to upgrade to 11?
hovikg said:
Any indication that'll happen for sure? Sony plans to upgrade to 11?
Click to expand...
Click to collapse
Yes. Release Dates are also known. The 2019 Xperia Lineups gets Android 11 starting the next Month. 2020 Xperias are already receiving it
Sony sure taking their time with that a11 update.
When I flashing it on android 11, it mentioned that api version is too high. Dear Atuthor I keenly need your update.
Miustone said:
Yes. Release Dates are also known. The 2019 Xperia Lineups gets Android 11 starting the next Month. 2020 Xperias are already receiving it
Click to expand...
Click to collapse
Still no update February 19th!
My 3 year old Pixel got 12, but still no 11 on the Sony ...
So, everyone should be on Android 11 now right!? Someone here who runs it with Magisk 22.0?
Android 11 Updates are out on GitHub! Will push a ready-to-use Version on My Website next!
I would love to try but patched boot.img on A11 still brings a bootloop on my 5II (XQ-AS52).
Hmm, even with the latest Magisk 22.0 Beta? @T3chDelicious
Miustone said:
Hmm, even with the latest Magisk 22.0 Beta? @T3chDelicious
Click to expand...
Click to collapse
I will try again when the new update is available in European market (58.1.A.5.55) which is hopefully this night since I must re-unlock bootloader anyway and make a fresh install of firmware. Then I will patch boot.img with Magisk Beta or Canary when Beta fails.
I will let you know.
T3chDelicious said:
I will try again when the new update is available in European market (58.1.A.5.55) which is hopefully this night since I must re-unlock bootloader anyway and make a fresh install of firmware. Then I will patch boot.img with Magisk Beta or Canary when Beta fails.
I will let you know.
Click to expand...
Click to collapse
Did the same yesterday with the Beta. The Magisk Changelog looks promising...
Thanks in advance for keeping me updated!
Related
im using oxygenos 5.1.6 with unlock bootloader and official twrp installed. but substratum doesn't work on mine. already grant the root access on the magisk manager, enabled the theme then restart system ui. stil nothing . and told me to reboot my devices. and still nothing. maybe you guys have the same problem with me. thxx (sorry for bad english). btw the theme that u tried to use it "navigate navbar".
It works for me. You have to change overlay states even after rebooting.
{
"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"
}
Sent from my ONEPLUS A6003 using Tapatalk
Andromeda - subtratun Ok, in 5.1.6
No issues here to,works just great.
Running pitch black and swift black.
Most things you can theme without a problem, some overlays doesn't work on oxygen .
Regards ysco..
Azhar_Fahry said:
im using oxygenos 5.1.6 with unlock bootloader and official twrp installed. but substratum doesn't work on mine. already grant the root access on the magisk manager, enabled the theme then restart system ui. stil nothing . and told me to reboot my devices. and still nothing. maybe you guys have the same problem with me. thxx (sorry for bad english). btw the theme that u tried to use it "navigate navbar".
Click to expand...
Click to collapse
You need to build & update not enable, then reboot and enable
U have to install themes, then reboot and then enable and possible reboot again
Hitman478™ said:
You need to build & update not enable, then reboot and enable
Click to expand...
Click to collapse
Bradl79 said:
U have to install themes, then reboot and then enable and possible reboot again
Click to expand...
Click to collapse
tried to use both of ur instructions, and still nothing.
Works for me
NateDev said:
Works for me
Click to expand...
Click to collapse
can u give me a details insructions how did u do it ?
oneplus6 with oos.5.1.6 definitely had issue with substratum theme especially when you update the system, it throws "system ui has stopped".
However, in combination "domination", "ozone", "pitch black" theme I finally got almost fully functional black theme with white text and white icons. And it runs on oos.5.1.6.
But what I'm highly upset about is that customizable black theme must be already be available on pure Android or at least on oem oneplus6.
Shame on you Oneplus once again for poor software development department as well as Google.
there's other people who got the same problem with me which can't cant change navbar icon with substratum. @ArolWright on reddit explained this :
OnePlus uses a proprietary navbar on the 5T instead of the AOSP one. Hence, themes need to be made from scratch with the 5T navbar in mind.
here's the link : https://www.reddit.com/r/oneplus/comments/7o2esw/unable_to_change_navbar_with_substratum_is_this_a/
Azhar_Fahry said:
there's other people who got the same problem with me which can't cant change navbar icon with substratum. @ArolWright on reddit explained this :
OnePlus uses a proprietary navbar on the 5T instead of the AOSP one. Hence, themes need to be made from scratch with the 5T navbar in mind.
here's the link : https://www.reddit.com/r/oneplus/comments/7o2esw/unable_to_change_navbar_with_substratum_is_this_a/
Click to expand...
Click to collapse
This is true for the OnePlus 6 too, yeah, but I'm afraid that's not the problem here. Since the March security patch, Google introduced certain overlay-related restrictions for both Android 8.1 and Android P, heavily hindering Substratum development. It's a security thing, so all Android builds with the March security patch and up will have this issue. While I don't have a OnePlus 6 myself, I have a OnePlus 5T on OxygenOS 5.1.2 (May security patch), and I haven't been able to apply themes properly on my side, not even those made for OOS like Ozone.
I made a Substratum theme fixing an issue with swipe gestures on the AOSP 8.1 lockscreen (and made an article about it on the XDA portal, here), and received several emails of people complaining about it not working following the March security update.
So I'm fairly certain this is the issue here, and it would require a fix from Google's side (or at least OnePlus', if they revert the relevant commits). Anyone who is more knowledgeable than me in this area is more than welcome to correct me if I'm wrong.
Cheers!
ArolWright said:
This is true for the OnePlus 6 too, yeah, but I'm afraid that's not the problem here. Since the March security patch, Google introduced certain overlay-related restrictions for both Android 8.1 and Android P, heavily hindering Substratum development. It's a security thing, so all Android builds with the March security patch and up will have this issue. While I don't have a OnePlus 6 myself, I have a OnePlus 5T on OxygenOS 5.1.2 (May security patch), and I haven't been able to apply themes properly on my side, not even those made for OOS like Ozone.
I made a Substratum theme fixing an issue with swipe gestures on the AOSP 8.1 lockscreen (and made an article about it on the XDA portal, here), and received several emails of people complaining about it not working following the March security update.
So I'm fairly certain this is the issue here, and it would require a fix from Google's side (or at least OnePlus', if they revert the relevant commits). Anyone who is more knowledgeable than me in this area is more than welcome to correct me if I'm wrong.
Cheers!
Click to expand...
Click to collapse
bro, thx for your explanation btw. at least I know some of the reasons why I cant theme my navbar. thx again. let's just hope oneplus will revert or at least change the stock navbar icon.
thx
Azhar_Fahry said:
tried to use both of ur instructions, and still nothing.
Click to expand...
Click to collapse
You didn't say that navbar is not theming, so my navbar won't theming too but only with some layers, have you tried another theme/navbar? For me for example, s8 navbar isn't working neither on oneplus 5 and 6
Hitman478™ said:
You didn't say that navbar is not theming, so my navbar won't theming too but only with some layers, have you tried another theme/navbar? For me for example, s8 navbar isn't working neither on oneplus 5 and 6
Click to expand...
Click to collapse
yes i did. navigate, n navbar, navbars. so far just that. imma keep trying till got at least one. or just disable it and use a gestures. lol:laugh:
Azhar_Fahry said:
yes i did. navigate, n navbar, navbars. so far just that. imma keep trying till got at least one. or just disable it and use a gestures. lol:laugh:
Click to expand...
Click to collapse
Mmh.. flux is working, also desire and Valerie
Sent from my OnePlus6 using XDA Labs
Hitman478™ said:
Mmh.. flux is working, also desire and Valerie
Click to expand...
Click to collapse
it's all paid tho haha. do know the free one that works too? coz I'm broke after bought this phone.
[edited]
btw SubNa : Navbars works for a bit. but it requires xposed.
(edit again)
nvm it's not working very well. keep resetting to default icon after every reboot
Azhar_Fahry said:
it's all paid tho haha. do know the free one that works too? coz I'm broke after bought this phone.
[edited]
btw SubNa : Navbars works for a bit. but it requires xposed.
(edit again)
nvm it's not working very well. keep resetting to default icon after every reboot
Click to expand...
Click to collapse
Disable navbar and go with gestures :fingers-crossed:
Sent from my OnePlus6 using XDA Labs
Hitman478™ said:
Disable navbar and go with gestures :fingers-crossed:
Click to expand...
Click to collapse
lol. that's exactly what I'm gonna do now. :laugh:
Azhar_Fahry said:
lol. that's exactly what I'm gonna do now. :laugh:
Click to expand...
Click to collapse
ahahah they're very good and after a while you'll forget the navbar
This magisk module was quickly thrown together for the Android Q Beta 3 to port the Pixel Launcher and other apps to the essential. Most taken from the Pixel system images. Hoping this quick module will inspire someone to improve (@Banks )
*Requires root and Magisk, only tested on PH-1 Q Beta 3*
Current Features:
Pixel Launcher (causes QuickStep to crash)
Action Services
Google Sans on Lock Screen
Blue Pixel Accent
Rounded Pixel UI
Sounds
Markup
Screens:
{
"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"
}
https://i.imgur.com/YNxCKDK.jpg
https://imgur.com/O3V2Lxu.jpg
https://imgur.com/TNgpJvK.jpg
To Do:
Markup app crashing
Google Sans on "at a glance" widget, Doesn't work on Pixel phones
Overview selection with Action Services
Troubleshoot: Delete /data/resource-cache and /data/system/overlays.xml and reinstall module
Ensure all apps have correct permissions
Download:
Q PIXEL MODULE V1
This looks Great.
Can you please provide steps how to apply. My phone is un-root at the moment.
Any idea why the suggested apps below the search bar in the launcher might not show up?
Edit: nvm, I reinstalled it and disabled the QuickSwitch module and now it's all good.
Boal said:
Any idea why the suggested apps below the search bar in the launcher might not show up?
Edit: nvm, I reinstalled it and disabled the QuickSwitch module and now it's all good.
Click to expand...
Click to collapse
Does quickswitch work correctly on Q? I disabled it before updating for fear of bootloops
gavinfernandes2012 said:
Does quickswitch work correctly on Q? I disabled it before updating for fear of bootloops
Click to expand...
Click to collapse
It doesn't cause bootloops but it also doesn't work properly, or at least I don't know how to use it properly. Eg app suggestions don't work for some reason.
---------- Post added at 12:17 PM ---------- Previous post was at 11:45 AM ----------
H0lmEd said:
This magisk module was quickly thrown together for the Android Q Beta 3 to port the Pixel Launcher and other apps to the essential. Most taken from the Pixel system images. Hoping this quick module will inspire someone to improve
Click to expand...
Click to collapse
I really just want the Pixel Launcher, not the Pixel style. Could you tell me what I have to remove from the zip to accomplish this? I tried doing it on my own but I don't think I know what I'm doing and I keep getting severe force closes
Just create a new magisk module with the /system/product/priv-app/nexuslauncher folder. Add in Matchmaker for app suggestions
Then use QuickStep to change recents provider to pixel launcher.
That or use Lawnchair
H0lmEd said:
Just create a new magisk module with the /system/product/priv-app/nexuslauncher folder. Add in Matchmaker for app suggestions
Then use QuickStep to change recents provider to pixel launcher.
Click to expand...
Click to collapse
Thanks, I almost have it. But the app suggestions are again not showing up. Do you maybe know what I need to consider to have them back?
edit: I've tried reverse engineering your module and it seems like app suggestions require /system/product/overlay/PixelConfigOverlayCommon.apk to function, which also changes some parts of the UI. I'm not too happy about this but I've also reached the end of my knowledge :-|
Do you know of any ways to get lockscreen weather like this
Was thinking it's just a port of overlay?
Thx!
VoidWalkerAlpha said:
Do you know of any ways to get lockscreen weather like this
Was thinking it's just a port of overlay?
Thx!
Click to expand...
Click to collapse
there's a hacky module on reddit that does this on pie that replaces the systemUI.apk that brings that functionality. i dunno if we can do this atm with the new lockscreen clocks and all of that.
H0lmEd said:
Just create a new magisk module with the /system/product/priv-app/nexuslauncher folder. Add in Matchmaker for app suggestions
Then use QuickStep to change recents provider to pixel launcher.
That or use Lawnchair
Click to expand...
Click to collapse
Wait so do lawnchair and quickstep work correctly with android Q and the new gestures??
Lawnchair no, Quickstep mostly.
I'll just drop this off
https://drive.google.com/folderview?id=12A7lM4Av5Jp0vG-ZqkCZmTBzqXnJCsn7
Pixel Essentials Q 3.9 zip
-First Q module from me
-Everything works
@op if you want module removed from thread just let me know. Just. Contributing. ?
BaNkS said:
I'll just drop this off
https://drive.google.com/folderview?id=12A7lM4Av5Jp0vG-ZqkCZmTBzqXnJCsn7
Pixel Essentials Q 3.9 zip
-First Q module from me
-Everything works
@op if you want module removed from thread just let me know. Just. Contributing. ?
Click to expand...
Click to collapse
nice mate. so glad to see ya here ??
I guess this means that we can root Q
Sent from my PH-1 using XDA Labs
avd said:
I guess this means that we can root Q
Click to expand...
Click to collapse
Yeah magisk can (I'm using canary personally, don't remember if beta and stable can yet). The easiest way to do it is to patch the fastboot boot.img and flash it to your active boot partition, at least in my opinion. I don't think twrp on our device works with Q yet.
gavinfernandes2012 said:
Yeah magisk can (I'm using canary personally, don't remember if beta and stable can yet). The easiest way to do it is to patch the fastboot boot.img and flash it to your active boot partition, at least in my opinion. I don't think twrp on our device works with Q yet.
Click to expand...
Click to collapse
Yeah 19.1 is working fine here for me. Which I believe is the latest stable.
gavinfernandes2012 said:
Yeah magisk can (I'm using canary personally, don't remember if beta and stable can yet). The easiest way to do it is to patch the fastboot boot.img and flash it to your active boot partition, at least in my opinion. I don't think twrp on our device works with Q yet.
Click to expand...
Click to collapse
I'm using beta (which I think is currently the same as stable, because it's the same version number), and I flashed it with TWRP. It works fine.
BaNkS said:
I'll just drop this off
https://drive.google.com/folderview?id=12A7lM4Av5Jp0vG-ZqkCZmTBzqXnJCsn7
Pixel Essentials Q 3.9 zip
-First Q module from me
-Everything works
@op if you want module removed from thread just let me know. Just. Contributing. ?
Click to expand...
Click to collapse
Thank you for getting this out and sharing it with the XDA community, I was almost about to leave Q and go back to a custom ROM
I do have an issue with action services FC when selecting text and with a memory leak which means the phone gets slowly unusable and have to reboot about 1-2 a day.
Is this issue known or do you need more info from my side?
venkatsrin said:
Thank you for getting this out and sharing it with the XDA community, I was almost about to leave Q and go back to a custom ROM
I do have an issue with action services FC when selecting text and with a memory leak which means the phone gets slowly unusable and have to reboot about 1-2 a day.
Is this issue known or do you need more info from my side?
Click to expand...
Click to collapse
It's known. Trying to figure out a fix. Hopefully it's just an Android Q beta or Actions Services bug.
How did you patch the boot.img? I’m on Q beta 3 and scared of boot looping the phone...I would be really thankful if you could tell me how to root Q beta 3
Pixel Launcher for Android 11 with TEXT Selection. No quick switch is required.
Features:
- Pixel Launcher
- DevicePersonalization
- Pixel Wallpapers
Working perfectly on Statix 4.0 Android 11 ROM for Essential Ph-1.
Thanks to TONY for v3.0 which helped me add some tweaks. Ported by SKULSHADY.
Instructions
1. Install module using magisk manager.
2. Reboot
3. Go to settings and change the default launcher.
4. Reboot.
Screenshots
{
"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"
}
CHANGELOG
Pixel Launcher R v3.1.1 - without wallpapers - Navbar stuff removed.
Pixel Launcher R v3.1.1 - without wallpapers
Pixel Launcher R v3.1.0 - with wallpapers and other stuff + Navbar stuff removed.
Pixel Launcher R v3.1 - with wallpapers and other stuff.
Enjoy!!
Will this work on lineage 18.1 gsi...Nokia 8.1 snapdragon 710..whenever I change something in product/overlay like dump apk from on gsi to other without editing phone bootloops...so will this work on my device...I am on lineage 18.1 gsi
Encryption on, selinux enforcing
mhamzas said:
Pixel Launcher for Android 11 with TEXT Selection. No quick switch is required.
Features:
- Pixel Launcher
- DevicePersonalization
- Pixel Wallpapers
Working perfectly on Statix 4.0 Android 11 ROM for Essential Ph-1.
Thanks to TONY for v3.0 which helped me add some tweaks. Ported by SKULSHADY.
Screenshots
View attachment 5178509View attachment 5178511View attachment 5178513
Pixel Launcher R v3.1.1 - without wallpapers
Pixel Launcher R v3.1 - with wallpapers and other stuff.
Enjoy!!
Click to expand...
Click to collapse
Sangfor Engine Zero malware reported from VirusTotal...is this real?
chanh2018 said:
Sangfor Engine Zero malware reported from VirusTotal...is this real?
Click to expand...
Click to collapse
Most likely a false positive, 99% of the time one of the noname AVs seem to catch something no other AV does, it's gonna be a false positive.
Hello, I'm installed magisc module on Arrow Os android 11 . V3.1 all stuff. It's working good but don't show recent apps. Any ideas? Thanks.
It's working for me, but Text-selection isn't. Are there any dependencies I need to know about?
I usually run minimal-Google setup so I'm not sure which might be the exact uh culprit.
D4DDY-C001 said:
It's working for me, but Text-selection isn't. Are there any dependencies I need to know about?
I usually run minimal-Google setup so I'm not sure which might be the exact uh culprit.
Click to expand...
Click to collapse
I was able to fix this issue by installing Device Personalization Services
nexlay said:
Hello, I'm installed magisc module on Arrow Os android 11 . V3.1 all stuff. It's working good but don't show recent apps. Any ideas? Thanks.
Click to expand...
Click to collapse
Yes same here.. please kindly fix devs
Edit: simply restart fix the problem thanks devs
@mhamzas will it work for OOS 11 Open BETA 2 - one plus 7 pro??
mhamzas said:
Pixel Launcher for Android 11 with TEXT Selection. No quick switch is required.
Features:
- Pixel Launcher
- DevicePersonalization
- Pixel Wallpapers
Click to expand...
Click to collapse
I know I'm in the Essential forum, but I'll post my experience anyway in case anyone is interested. I installed v3.1 on a Pixel 5 Running unofficial Lineage 18.1 with open gapps nano. Everything works except for text selection; I tried granting permissions to Device Personalization Services, but it didn't help. It would be nice to have that feature, but I'm happy to use this module even without it.
Thanks for sharing.
user602 said:
I know I'm in the Essential forum, but I'll post my experience anyway in case anyone is interested. I installed v3.1 on a Pixel 5 Running unofficial Lineage 18.1 with open gapps nano. Everything works except for text selection; I tried granting permissions to Device Personalization Services, but it didn't help. It would be nice to have that feature, but I'm happy to use this module even without it.
Thanks for sharing.
Click to expand...
Click to collapse
I managed to have text selection working ! I'm running crdroid no gapps.
I installed the pixel 5 version of Device Personalization Services R.11.playstore.pixel5.353007393 (arm64-v8a) (Android 11+). Check on apkmirror
Thx @mhamzas for sharing this incredible magisk module @SKULSHADY U rock !
nexlay said:
Hello, I'm installed magisc module on Arrow Os android 11 . V3.1 all stuff. It's working good but don't show recent apps. Any ideas? Thanks.
Click to expand...
Click to collapse
Try rebooting the phone after selecting Pixel Launcher as the default Launcher.
Event_Horizon said:
@mhamzas will it work for OOS 11 Open BETA 2 - one plus 7 pro??
Click to expand...
Click to collapse
Technically it should but please try and report us back here.
mhamzas said:
Technically it should but please try and report us back here.
Click to expand...
Click to collapse
Tried and ****ed up for 3 hours.. OnePlus 7 pro running Android 11 OOS OB 2.. why 3 hours because my phone is rooted with no twrp with modded boot image patched with magisk for android 10 that's the way OnePlus 7 pro users having root...
Well I want pixel launcher 11.. pls do something.
Actually after magisk installation device getting into boot loop with the bigger size module.
And for smaller package device got re-start, but when I tried to access settings app the phone get restart, I tried 3 times to get into settings app after that phone went into bootloop.
Nomgastro said:
I was able to fix this issue by installing Device Personalization Services
Click to expand...
Click to collapse
And this worked beautifully tyvm.
kkosnuss said:
I managed to have text selection working ! I'm running crdroid no gapps.
I installed the pixel 5 version of Device Personalization Services R.11.playstore.pixel5.353007393 (arm64-v8a) (Android 11+). Check on apkmirror
Click to expand...
Click to collapse
Thanks for posting your solution. I installed the version you listed from the play store, but text selection still doesn't work for me. Oh, well.
Bootloop on OnePlus 8T Android 11 OOS 11.0.6.8 Magisk without TWRP.. ( can someone help me install this module successfully?
Event_Horizon said:
Tried and ****ed up for 3 hours.. OnePlus 7 pro running Android 11 OOS OB 2.. why 3 hours because my phone is rooted with no twrp with modded boot image patched with magisk for android 10 that's the way OnePlus 7 pro users having root...
Well I want pixel launcher 11.. pls do something.
Actually after magisk installation device getting into boot loop with the bigger size module.
And for smaller package device got re-start, but when I tried to access settings app the phone get restart, I tried 3 times to get into settings app after that phone went into bootloop.
Click to expand...
Click to collapse
Im rooted the same way and why 3 hours? You couldve just disabled all magisk modules by plugging in ur phone to pc while its in bootloop screen and running these commands in cmd:
Code:
adb devices
adb wait-for-device shell magisk --remove-modules
Looks like some of the components are conflicting with OxygenOS components and causing bootloop. Unfortunately, I do not have OP device to test the module.
The module should work fine on AOSP roms.
OP users, please share the logcat.
mhamzas said:
Looks like some of the components are conflicting with OxygenOS components and causing bootloop. Unfortunately, I do not have OP device to test the module.
The module should work fine on AOSP roms.
OP users, please share the logcat.
Click to expand...
Click to collapse
How do i fetch the logcat? Guide me pls, newbie here
{
"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"
}
UPDATED FOR April 21st 2023
I am not affiliated with the official Evolution-X team.
link to kernel source: https://github.com/psybernetiq/kernel_google_redbull_tiramisu-pixel
my other repos for the device and vendor are there as well.
downloads:
EvolutionX-13 - Google Drive
drive.google.com
flash the vendor_boot img. Then adb sideload the zip file in recovery.
Notes:
BACKUP YOUR DATA FOR THIS BUILD. YOU WILL PROBABLY HAVE TO RESET YOUR DEVICE TO FLASH THS ROM. SORRY FOR INCONVENIENCE.
I make reference to 9.9.9.9 (quad9 dns) rather than 1.1.1.1 (cloud flare) to 1 part in the code under bionic/libc/dns/net/getaddrinfo.c.
I added bromite webview support (does not require you to be rooted)
I added a flag called TARGET_IS_PIXEL_5 := true so that this device gets a hit to make persist.sys.disable_rescue=true. Without this, the device will boot but then reboot to recovery within ~10seconds.
I did not add wireguard support to the kernel this time. Let me know if you want me to add it back in.
passes safety net
The screen on my pixel 5 cracked back in March and I got a Pixel 7 Pro. I still have the pixel 5, though, and I tested this rom on the device before uploading and sharing here.
The March update was super late coming from Google, and the Evolution-X team was making a bunch of changes during this time (and they still are.) So consider this release an off-cycle release.
I was also having trouble building the ROM for a few weeks due to my laptop's RAM (32GB) being fried but not really making it clear to me that that was the problem. I had been using Qubes as my OS but have since gone back to good 'old Linux Mint. I liked Qubes but it's kinda a pain to constantly fuss with allocating the USB drives and I suspect the constant use of my 32GB of RAM to run all the virtual machines therein contributed to the premature death of my RAM cards (~1 yr old).
I build this ROM in the same tree as for my Pixel 7 Pro, so I should continue to make updates going forward for the Pixel 5. I'm planning on adding the Pixel 3XL and OG Pixel ("sailfish") as well, since I own all those phones, too.
Due to this trouble with my PC, the pathways to my keys (the ones you can see in /system/etc/security/otacerts.zip, you can see it includes the entire pathway where the keys are actually located in my PC) changed and I think that's why you have to clear data on this ROM. I'm also using a different Github repo now, too, as part of a rebranding process I'm doing.
Enjoy!
Can we flash this on top of your unbound rom without a factory reset?
screenshots of just some of the features
elong7681 said:
Can we flash this on top of your unbound rom without a factory reset?
Click to expand...
Click to collapse
I dont' know...sorry about that
aleph.mercury said:
I dont' know...sorry about that
Click to expand...
Click to collapse
Thanks for your fast response
elong7681 said:
Can we flash this on top of your unbound rom without a factory reset?
Click to expand...
Click to collapse
Asking the same question. Waiting for brave soul to try it.
saxmydix said:
Asking the same question. Waiting for brave soul to try it.
Click to expand...
Click to collapse
If the worst that could happen is having to factory reset and start over if it doesn't work then I'll give it a shot.
elong7681 said:
If the worst that could happen is having to factory reset and start over if it doesn't work then I'll give it a shot.
Click to expand...
Click to collapse
This is my main and only device, too lazy to backup at this point.
Why another thread? Why just update an old thread. just one question. Bluetooth volume up?
saxmydix said:
This is my main and only device, too lazy to backup at this point.
Click to expand...
Click to collapse
My only device too but I will try it after work
elong7681 said:
My only device too but I will try it after work
Click to expand...
Click to collapse
I just did, update on top of previous without wiping. Working good.
saxmydix said:
I just did, update on top of previous without wiping. Working good.
Click to expand...
Click to collapse
Awesome thanks for letting me know, so to update the rom would I just sideload it in recovery?
saxmydix said:
I just did, update on top of previous without wiping. Working good.
Click to expand...
Click to collapse
Please, cann you try bt headphone volume? On prew build was litlebit low.
got some freezes here and there when adjusting quick settings and had to reboot, but all in all seems to be a nice rom.
only thing i'm missing are advanced navbar settings like "force close active app when holding back-button"
also "connectivity thermal power manager" apparently draws way to much battery
@aleph.mercury I really do enjoy this rom but is there any chance that we can get Now Playing working on this ROM? I tried to enable it through the settings and it does nothing.
elong7681 said:
@aleph.mercury I really do enjoy this rom but is there any chance that we can get Now Playing working on this ROM? I tried to enable it through the settings and it does nothing.
Click to expand...
Click to collapse
I'll look into it. I never tried to use it before, I'll see what I can do
aleph.mercury said:
I'll look into it. I never tried to use it before, I'll see what I can do
Click to expand...
Click to collapse
Thank you
Aospmods magisk module will add some stuff you guys need
[MOD][Xposed+Magisk][13 Compatible] AOSP Mods - System modifications for AOSP-based Android 12+
This is a mixed Xposed+Magisk module, which is made to allow customizations that are not originally designed in AOSP (Android Open Source Project). Features: Currently, AOSP Mods offers customizations on different aspects of system framework and...
forum.xda-developers.com
badaas said:
Aospmods magisk module will add some stuff you guys need
[MOD][Xposed+Magisk][13 Compatible] AOSP Mods - System modifications for AOSP-based Android 12+
This is a mixed Xposed+Magisk module, which is made to allow customizations that are not originally designed in AOSP (Android Open Source Project). Features: Currently, AOSP Mods offers customizations on different aspects of system framework and...
forum.xda-developers.com
Click to expand...
Click to collapse
I want to say that I tried to install it on the unbound evolution x rom and it didn't work I ended up in a bootloop, have you tried it on this rom yet
Edit: It works on this rom
seems that "connectivity thermal power manager" and "com.android.hbmsvmanager" are drawing way to much power. together they drew like 50% and i had to recharge my phone midday, which usually never happens
Android 14 Beta program for the Pixel 7 Pro [Cheetah]
Download links in the middle of the OP.
Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback. Android 14 Developer Preview 1 is an early baseline build that's still in active development, so the Android system and apps running on it might not always work as expected.
Click to expand...
Click to collapse
{
"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"
}
Note to anyone who flashes a Developer Preview or Beta OTA without having the capability to unlock your bootloader - you'll be stuck in the Developer Preview and Beta program until it goes final - in the case of Android 14, somewhere between August and October 2023. There is absolutely nothing that can be done about this without being able to unlock the bootloader. And even with an unlocked bootloader, you'll have to perform a complete wipe when going back to Stable.
June 14, 2023:
Beta 3.1:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing preview system images for Pixel devices.
developer.android.com
OTA images for Google Pixel | Android Developers
Instructions for downloading and appying preview OTA images for Pixel devices.
developer.android.com
Get Android 14 | Android Developers
Get Android 14 on your eligible device.
developer.android.com
Android 14 Preview | Android Developers
How the Android 14 Preview works, the timeline, and what is included.
developer.android.com
We'll be glad if someone provide screenshots pf new features and changes
Dr.Pepper said:
We'll be glad if someone provide screenshots pf new features and changes
Click to expand...
Click to collapse
No screenshots, but adding this to the OP now:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com
roirraW edor ehT said:
No screenshots, but adding this to the OP now:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com
Click to expand...
Click to collapse
This message was for someone who will install DP)
Right now i dont have access to PC and cant install on my P7 DP)
Will patinetly waiting for SS!)
I'll be flashing this as soon as I get home from work
I just flashed it without wiping, coming from A13 February stable build. Boots up fine and just started looking around. All my apps that I've opened so far work fine.
I'm going to try and root it soon, I'll let you know how that goes.
Rooted fine for me. Coming from A13 Feb stable build.
Device will NOT pass Device Integrity within Play Integrity at all now on USNF 2.3.1 Diplax mod, BUT works intermittantly on USNF 2.4.0. Will now have to try with GooglePay. Seems like the Play Security Update of February may have something to do with it?
Added the following (LONG!):
Android Developers Blog
News and insights on the Android platform, developer tools, and events.
android-developers.googleblog.com
pogo-airsupport said:
Rooted fine for me. Coming from A13 Feb stable build.
Device will NOT pass Device Integrity within Play Integrity at all now on USNF 2.3.1 Diplax mod, BUT works on USNF 2.4.0. Will now have to try with GooglePay
Click to expand...
Click to collapse
I was just about to send you a reply asking what version of USNF you're on, but then I saw my quote of your post was different (edited) from your original post.
SIM manager seems extremely unstable.
And yes, T-Mobile n25 is still missing.
No way to flash without wipe on a locked bootloader, right?
gpvecchi said:
No way to flash without wipe on a locked bootloader, right?
Click to expand...
Click to collapse
Only download and flash only for the DP builds unfortunately, so correct
gpvecchi said:
No way to flash without wipe on a locked bootloader, right?
Click to expand...
Click to collapse
And you probably don't want to unless you can unlock your bootloader when you choose, because with a locked bootloader, you would be stuck in this Android 14 Developer Preview and then Beta until it goes Final somewhere between August and October 2023.
I'm seeing a full compliment of 32-bit libraries inside the system image and inside the APEXs, so Google is still shipping with multilib for the time being.
I haven't tested the preview with my forks of Magisk that provide 32-bit support to see if they work, but in theory it should work fine.
Now I'm questioning why Google is still doing multilib and if their plans are at some point in the preview process to make all libraries 64-bit only, or if the Pixel 7 is just going to have this half-way transition to 64-bit only for the rest of it's Android releases.
Should update that warning to a
roirraW edor ehT said:
And you probably don't want to unless you can unlock your bootloader when you choose, because with a locked bootloader, you would be stuck in this Android 14 Developer Preview and then Beta until it goes Final somewhere between August and October 2023.
Click to expand...
Click to collapse
Should update that first post warning to a big red DO NOT FLASH for locked bootloaders. We should refuse to support anyone that does and then complains.
Not putting up with a repeat of 13 DP1.
First hour of playing with the update, everything seems pretty smooth. Scrolling especially.
Device is still warm, but that's expected with the optimization and updating going on behind the scenes.
GooglePay is going to be a write off for the time being, until root and modules are a bit more optimized. The update does seem to break it more consistently, so reproducing the error will at least be easier.
All apps still seem to work.
I went from a g5300n radio to the bundled g5300g radio. I had been using the QPR2.1 radio with the stable builds for better reception. Took about 1-2 minutes for g5300g to lock on to 5G, but since then has had stable signal.
Notable bugs:
1. Central clock widget time is NOT centered.
2. Device battery widget will not show % or name when shrunk under a certain size
3. LSPOSED menu is BROKEN
The https://developer.android.com/about/versions/14/overview has already changed with some minor corrections.
It did say:
What's included in the Android 14 Preview?...
SDK & NDK tools...
SDK, NDK, and tools for Android 14
...
For more inforamtion, see Get Android 14.
Click to expand...
Click to collapse
Now it says:
What's included in the Android 14 Preview?...
SDK & tools...
SDK and tools for Android 14
...
For more information, see Get Android 14.
Click to expand...
Click to collapse
LLStarks said:
Should update that warning to a
Should update that first post warning to a big red DO NOT FLASH for locked bootloaders. We should refuse to support anyone that does and then complains.
Not putting up with a repeat of 13 DP1.
Click to expand...
Click to collapse
I'll consider it, thank you. There's really nothing we can do to support anyone who does and can't unlock their bootloader, anyway.
I might go for several flashy, annoying danger GIFs instead.
LLStarks said:
Should update that warning to a
Should update that first post warning to a big red DO NOT FLASH for locked bootloaders. We should refuse to support anyone that does and then complains.
Not putting up with a repeat of 13 DP1.
Click to expand...
Click to collapse
Okay, I've modified the warnings. If that's not enough heads up, then I give up.
https://twitter.com/i/web/status/1623382609056129025