CLOSED PER OP REQUEST
{
"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"
}
Download:
DOWNLOAD Official
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS
MAJOR BUGS:
huh ?
Minor bugs:
flash on your own risk.
FLASHING
First Time:
First Time:
update fastboot and adb ( https://developer.android.com/studio...platform-tools )
download twrp
fastboot boot twrp-blabla.img
flash stock OOS (we use stock vendor, if you have that skip this step)-(but make sure your both slots are fine (look flashing oos update below))
flash omni
reboot to bootloader
fastboot boot twrp-blabla.img again
flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
reboot
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
updating when stock OOS update is released:
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash gapps
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7 Pro
Contributors
darkobas, vache, maxwen
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS 10
Version Information
Status: Stable
Created 2019-10-02
Last Updated 2019-11-19
amazing , thanks
The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?
Gordietm said:
The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?
Click to expand...
Click to collapse
That should be ob obvious, but i will add it
[ROM][BETA] Omnirom for Oneplus7pro [10]
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro
paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Click to expand...
Click to collapse
Always nano
paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Read OP : flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
[ROM][BETA] Omnirom for Oneplus7pro [10]
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Sent from my iPad using Tapatalk Pro
paatha13 said:
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Click to expand...
Click to collapse
Yes
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Good luck
B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Probably you missed something, skipped one step etc.
B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
No, oos camera also works fine
I have no idea what it is. Had to boot a fastboot rom just to get back up and running after that last crashdump. going to go back to OOS for a little I think. I have never had a rom do this but this one has done it every time I have tried. Thing is I love Omni so I hope one day i can get it running properly.
---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------
gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
Don't worry i didn't forget lol. That's why i'm going to keep trying after every release. It will work for me one day.
[ROM][BETA] Omnirom for Oneplus7pro [10]
Everything fine with installations no had any issue with first attempt.
Installing nano gapps not had any issue too this time at opposite with weekend build.
Seems this build more stable and I'm now charging the phone,download my usual staff from play store,will setup my device and will start to work on it later when phone full charge.
Thanks @darkobas.
darkobas said:
No, oos camera also works fine
Click to expand...
Click to collapse
Yes I can confirm OOS camera working fine.
Sent from my iPad using Tapatalk Pro
Does anyone know of an app or mod that allows the navigation buttons to be inverted? The custom navbar app doesn't work on 10 yet and that isn't integrated into the rom yet. I'll live but it is tough to try to retrain the brain, ha!
First impressions using couple of hours is solid.
Battery life look promising and satisfactory.
Very smooth experience so far.
Speaker loudness and quality is on par with oxygen just like with Pie version.
Brightness level seems on par with high oxygen levels although I haven't test it in sunlight, will do tomorrow [emoji14]
Stock(android 10) gesture navigation works great but prefer oxygen one and since using nova launcher I'm with vivid gesture navigation app since when using third-party launcher automatically stock gesture navigation are disabled.
There's dark mode but I'm not fan of it since it's dark gray and not black that prefer (will use substratum to apply truly black theme almost everywhere)
Vast majority Omni features working fine so far.
Wi-Fi, mobile data, so far all excellent, BT will test tomorrow intensively.
Almost all oxygen features are present and worked fine, except vibration need some tuning but that also appy to stable OOS 10 version.
On Pie vibration was better both Omni and OOS.
High brightness level is still present
I found some bugs though like dt2w not such reliable almost half of the attempts needed 2 and rare 3 times to wake up screen or even press the power button at end because not responding at all.
Aldo digital wellbeing to me every time try to open I'm getting fc.
Safety net not passing through magisk also.
I assume will improve in future build don't forget it's still beta.
More observations and safe conclusions will have after couple of days of using the new rom.
But so far general impressions after few hours is at good and satisfactory level and the build is safe to be daily driver for sure.
Sent from my GM1913 using Tapatalk
Just wondering why I can't download the Samsung wearable app in the Google Play Store on this. When I get it from the APK it tells me that this software which is on my phone is not compatible with the watch is there a way to fix this so I can connect my Galaxy watch to this amazing ROM this happens to me on every single ROM except CR Droid 9.0 don't know why:crying:
This is a pic of what the Samsung wearable app said
Related
{
"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"
}
Thank u to the Liquid Team for continuing this project!
Many credits go to CyanogenMod for their device trees and their code that was incorporated into this project.
Downloads and installation
+ Download the ROM
+ Download the (Recommended) GApps
+ Copy the ROM to the SD
+ Copy the GApps to the SD
+ Install the ROM and the GApps
+ If you are already in LiquidSmooth, do a cache wipe and dalvik cache wipe
+ If you come from any other ROM, do a wipe data / format system
+ Reboot
CREDITS
LIQUIDSMOOTH TEAM and everyone they are involved with!
chainfire for root!
MEET THE TEAM
Liquid0624
Deadman96385
jsnweitzel
Somber73
TheBr0ken
Cdub50
Sat this one out
Donations are always appreciated
Liquid0624
XDA:DevDB Information
LiquidSmooth, a ROM for the HTC One S
Contributors
phoenixita
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.15
Version Information
Status: Testing
Created 2013-12-19
Last Updated 2013-12-29
Reserved
http://www.androidfilehost.com/?fid=23269279319197376
I've not tested it!
Let me know! Use Flemmard's recovery.
BUGS
Rapier said:
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Edit: I see others noticed the wake-up/sistemui FC as well. I'll try what phoenixita suggests. Dirty flashing over BeanStalk could be an option? Nevermind...I'll try it anyways
Click to expand...
Click to collapse
You beauty!. Thanks will test
Sent from my One S using XDA Premium HD app
is for hboot 2.16 or 2.15?
Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
2.15! Building for 2.16 is like building for another device i don't know if i have all this time! I'll try for 2.16 right now.
Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
You are either joking or to lazy to read at least the OP.
Tell you what...regardless of which hboot is for, it is surely not for you
Sent from nowhere over the air...
Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
Pmsl....Read op its hardly a novel...
Sent from my One S using XDA Premium 4 mobile app
Any feedback?
Download is slow, so no report yet....
The ROM is very fast and smooth but I miss the support for German or other languages
Sent from my HTC One S with Tapatalk 4
Hai96 said:
The ROM is very fast and smooth but I miss the support for German or other languages
Sent from my HTC One S with Tapatalk 4
Click to expand...
Click to collapse
LS is only in english you can use morelocale2 but you won't hve full traslations! I'm italian and searching the net and asking To teamliquid they won't support other languages cause they have no time! Language pack were available for LS 4.2.2 and $doryd$ joined the teamliquid to port languages but it was just for 4.2!
Ok, Thanks!
But there is one big Bug, if you want to wake up your device from standby the display won't turn on, only the buttons are lighting. If you reboot you will get a forced systemui FC bootloop.
Sent from my HTC One S with Tapatalk 4
Hai96 said:
Ok, Thanks!
But there is one big Bug, if you want to wake up your device from standby the display won't turn on, only the buttons are lighting. If you reboot you will get a forced systemui FC bootloop.
Sent from my HTC One S with Tapatalk 4
Click to expand...
Click to collapse
Not here too! DAMN! Try dirty flashing over a cm11....and see if it works as a workaround. There is something wrong with our device/device-common trees!
I mean flash cm11 let it boot and then flash liquid over it with gapps!
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Edit: I see others noticed the wake-up/sistemui FC as well. I'll try what phoenixita suggests. Dirty flashing over BeanStalk could be an option? Nevermind...I'll try it anyways
Rapier said:
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Click to expand...
Click to collapse
could you try dirty flashing over a cm11 nightly?
phoenixita said:
could you try dirty flashing over a cm11 nightly?
Click to expand...
Click to collapse
I was in recovery after I've restored BeanStalk. I'll try flashing over it first to see if it's working, then I'll try over CM11 latest nightly as well
Rapier said:
I was in recovery after I've restored BeanStalk. I'll try flashing over it first to see if it's working, then I'll try over CM11 latest nightly as well
Click to expand...
Click to collapse
lemme know!
phoenixita said:
lemme know!
Click to expand...
Click to collapse
LOL. It works and more than that, I got some extra features as well since I've flashed it dirty over BS...like the network speed meter in status bar (an option that is not present in CM nor in LiquidSmooth ROM). Only strange thing now is that sistemui restarts itself every time when I connect the phone to USB...it's restarting in a loop without any message. I've rebooted phone and I'll try again.
Rapier said:
LOL. It works and more than that, I got some extra features as well since I've flashed it dirty over BS...like the network speed meter in status bar (an option that is not present in CM nor in LiquidSmooth ROM). Only strange thing now is that sistemui restarts itself every time when I connect the phone to USB...it's restarting in a loop without any message. I've rebooted phone and I'll try again.
Click to expand...
Click to collapse
You and phoenix are a great duo together. Phoenix always building and supporting our device and Rapier always tests and provides quality feedback. Thanks to you both for your contributions, very much appreciated. I had those systemui errors constantly on the BeanStalk build, as well, so I reverted back to a 4.3 ROM until the issues are more ironed out. This is expected considering KitKat is still in some infant stages and our device needs a lot of pruning to get it right. Is it true that the battery life is horrendous in 4.4? Thanks to you both again, keep it up! Very eager to try 4.4 again when there is no more systemui errors.
phoenixita said:
Not here too! DAMN! Try dirty flashing over a cm11....and see if it works as a workaround. There is something wrong with our device/device-common trees!
I mean flash cm11 let it boot and then flash liquid over it with gapps!
Click to expand...
Click to collapse
Didn't worked, I still have the same problem with the display...
Sent from my HTC One S with Tapatalk 4
It's ooooout
I don't know why I've been obsessively checking to see when they released the build for our device but I have been and hey here it is finally
https://miui.g3d.codes/8.9.13/xiaomi.eu_multi_MIMix2S_8.9.13_v10-9.zip
Whats new on this version.?
DMart9406 said:
Whats new on this version.?
Click to expand...
Click to collapse
The jump to pie ? haven't found any new feature or improvement so far.
Did you factory reset to install or full data wipe?
Slow boot time.
There is something wrong with this version. Boot time is always veeeery slow!!!
gptwarrior said:
Did you factory reset to install or full data wipe?
Click to expand...
Click to collapse
I've flashed it on top of oreo build. Worked. First boot time is very long, but after that everything is okay.
---------- Post added at 06:24 AM ---------- Previous post was at 06:21 AM ----------
dimisarta said:
There is something wrong with this version. Boot time is always veeeery slow!!!
Click to expand...
Click to collapse
Yeah you are right. Boot time is pretty long. Hopefully they will fix it in future update.
Seems they fixed encryption status display.
In 8.8.3, it's "Phone encrypted" and now it's "Phone not encrypted".
The phone is indeed not encrypted since TWRP doesn't require password / PIN when entering.
But how can I make it encrypted? I know the encrypt option in settings doesn't work before and I would not try again. I checked fstab.qcom and it's already encryptable=ice,quota, so I have no idea - I think data should be encrypted when I do full wipe.
MacLaughlin said:
I've flashed it on top of oreo build. Worked. First boot time is very long, but after that everything is okay.
---------- Post added at 06:24 AM ---------- Previous post was at 06:21 AM ----------
Yeah you are right. Boot time is pretty long. Hopefully they will fix it in future update.
Click to expand...
Click to collapse
Eh I suppose it's kind of slower, but it's still fairly fast in my opinion, it's about 10 seconds from beginning to end by my timing just now.
Also, when I flashed it, I instinctively first did a complete flash_all from the current global beta 8.9.13 fastboot, and then booted into it, and finally flashed this ROM
EraserKing said:
Seems they fixed encryption status display.
In 8.8.3, it's "Phone encrypted" and now it's "Phone not encrypted".
The phone is indeed not encrypted since TWRP doesn't require password / PIN when entering.
But how can I make it encrypted? I know the encrypt option in settings doesn't work before and I would not try again. I checked fstab.qcom and it's already encryptable=ice,quota, so I have no idea - I think data should be encrypted when I do full wipe.
Click to expand...
Click to collapse
Whaaaat weird, I immediately had flashed the Universal DM-Verity/ForceEncrypt disable script after ROM flash, so when I saw the encryption is disabled message I had just assumed the script had worked ?
Anti-rollback 3 or 4?
ShotSkydiver said:
Eh I suppose it's kind of slower, but it's still fairly fast in my opinion, it's about 10 seconds from beginning to end by my timing just now.
Also, when I flashed it, I instinctively first did a complete flash_all from the current global beta 8.9.13 fastboot, and then booted into it, and finally flashed this ROM
Click to expand...
Click to collapse
Also performed a clean flash now. Still very long boot time. Did you format data partition?
Yesterday i did xiaomi.eu global and first it was also long boot but now after restart it is all ok.
ShotSkydiver said:
Eh I suppose it's kind of slower, but it's still fairly fast in my opinion, it's about 10 seconds from beginning to end by my timing just now.
Also, when I flashed it, I instinctively first did a complete flash_all from the current global beta 8.9.13 fastboot, and then booted into it, and finally flashed this ROM
Click to expand...
Click to collapse
So, you flashed 8.9.13 global beta from fastboot and then installed the ROM? Did you format data before flashing the ROM?
Thanks and sorry for the obvious questions
Got it today as normal OTA update. Miu 10 but Android Version 8.0 ist that normal?
What is the point of this if there is no difference to MIUI10 based on Oreo?
MIUI 10 is based on Android 9.
{
"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 Mi MIX 2S using Tapatalk
MinhAshura said:
Anti-rollback 3 or 4?
Click to expand...
Click to collapse
anti: 1
anybody knows what that means ?
gianton said:
MIUI 10 is based on Android 9.View attachment 4598560
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
Miui10 can be based on whatever Xiaomi want. Currently as a stable release it's on 8.0, but beta users are ok 9.0.
Remember that miui versions and Android versions have almost nothing to do with each other.
Also again this has nothing to to with xiaomi.eu
M.
mattman83 said:
Miui10 can be based on whatever Xiaomi want. Currently as a stable release it's on 8.0, but beta users are ok 9.0.
Remember that miui versions and Android versions have almost nothing to do with each other.
Also again this has nothing to to with xiaomi.eu
M.
Click to expand...
Click to collapse
I think Mi5S has MIUI 10 based on Nougat btw
My bluetooth car connection connects, but shows no signal and doesn't call Back to xiaomi.eu_multi_MIMix2S_8.8.3_v10-8.0 it is ...
@ andriu123 same question with me - what does anti: 1 mean?
**** Work in progess ****
{
"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"
}
AOSP Extended is an AOSP based rom which provides stock UI/UX with various customisations features along with the Substratum theme engine. The project has been made by cherry-picking various commits from various other projects. Being based on AOSP it provides a smooth and lag-free experience out of the box. We will constantly try to add more features and make it even better in future updates. A ROM by a user, for a user. #StayAOSP #ExtendYourDevice #BeExtended
Features
Silky smooth Android experience
Tons of customisation
Pixel-like UI (Launcher, settings, Google Now swipe...)
Full Substratum/OMS support
And much more (check official AEX website)
HW Accleration working !!!
Camera working
Kernel Features
Added IO Schedulers:Zen,Sio,Maple,Tripndroid
Added Governours:ElementalX,SmartMax,Tripndroid
Added Filesystem:SDCardFS,F2fs
Removed:EXFat causes random Bootloops and compatibility problems
Modified Dtb for faster charging (Tested around 2.4A at 5 Volt Chargepower with Anker 20W Wallcharger and 2A at 9V with Anker Power Port+1) experimental QC2.0 enabled Tests needed
Optimized for Battery:SmartmaX Cququiet:runnable Maple IO Sheduler as default
If you need performance change to Interactive and Cpuquiet:Balanced
Download
Latest release here.
https://androidfilehost.com/?w=files&flid=305454 no Zram
https://androidfilehost.com/?w=files&flid=305455 with Zram
https://androidfilehost.com/?w=files&flid=305556 DTB with QC2.0
Installation
Be on the latest firmware - if you are not, or aren't sure just flash latest stock recovery image for your device (you will lose data and TWRP so back data up and prepare to reflash TWRP)
From TWRP3.3.1 wipe Cache, Dalvik, System, Data and Internal Storage
Flash ROM
Flash ARM (not arm64!) 8.1 mini gapps
Flash DTB after all with : fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Netflix with SD:
Install latest Magisk
Download Libeoemcrypto patch and Props Fingerprint Mod
after reboot run in Terminal with Root rights Props choose 1 Edit device fingerprint
f Pick a certified fingerprint
16 Nvidia after that choose your device
Reboot and download Netflix from Store
Fixed: HW Accleration OMX works now
Camera full functional now
Kernel Bootloops/Random reboots
LTE Fix no Sim Card detected
Bugs
Netflix HD still not working
Nvidia Games crashes
As Workaround you could use Moonlight Gamestream to stream PC Games
Report bugs if you find any, every opinion is welcome, try to describe problems with as much detail as possible
Thanks
AEX team, LineageOS team, and all people around this project and this device
Special thanks to Steel01 and Artemka2008 for there help with the OMX Fix
XDAevDB Information
AOSP Extended for Shield Tablet, ROM for the Nvidia Shield Tablet
Contributors
Triodexe, Steel01, Artemka2008
Source Code: https://github.com/aospextended
Kernel Source: https://github.com/Triodex/TrioX-V04-Kernel
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.x
Based On: AOSP+LineageOS
PLATFORM_SECURITY_PATCH := 2020-02-05
Version Information
Status: Testing
Current Stable Version: 5.8
Stable Release Date: 2020-02-20
Created 2020-02-20
Last Updated 2020-02-29
So, the one thing left not working is the camera? Any hope of fixing that?
Thanks for releasing this. Can't wait to give it a try. Curious about the zram vs no zram. What is that? Also, what is dtb? Thanks again.
Hi
For the Camera bug i still try to get this fixed.
@bigcletus
Rom with Zram have 510MB Compressed RamSwap that you can increase with Kernel Managers like the StockRoms
Rom without Zram didnt have this
The Dtb is needed for the correct Charging Amps and Voltage Regulation so if you notice after flash the Rom that Quickcharge isnt working flash the Dtb again with Fastboot.
Greats Triodexe
I tried to install ROM (no Zram), but got stuck on Nvidia logo bootloop. Came from LOS 14.1 ROM, wiped everything mentioned except internal storage.
bigcletus said:
I tried to install ROM (no Zram), but got stuck on Nvidia logo bootloop. Came from LOS 14.1 ROM, wiped everything mentioned except internal storage.
Click to expand...
Click to collapse
Hi
Did u use the Latest Twrp 3.3.1 to flash the Rom ?
For the Bootloop i dont know yet why it happens sometimes have the same problems again after a few restarts device stucks at Nvidia Logo but after manualy Poweroff/On its boots most af the time .
Guess there is a problem with one of the Governours/Shedulers i added or the Exfat Kernel Support.
But curios is the same stuff works in the Aosp4.6 Roms.
Could be that the Old Nvidia Vendor Blobs arent so good for Oreo based Roms but the newer ones from Shield Tv have no Hardware Accleration yet
But Dmesg didnt help me for this when i boot into recovery device always boots
You could try flash another Kernel the K1 Nougat from bleeblob or Bitos Kernel Version 10 should work better
So i reflashed the nozram over my Rom again and got no bootloop only wiped cache and dalvik
Could you look Into your Internal storage if there is some stuft left Form the Old Rom Apps and Magisk
Stores the Data there.
Greats Triodexe
I am using TWRP 3.2.3. I have flashed LOS 14.1 and 15.1 with this version of TWRP but maybe this rom needs the newer version?
I will try again when I have more time and I'll wipe the internal storage as well. Thanks.
Install and boots OK. I can't get Netflix to work.
Darkside281 said:
Install and boots OK. I can't get Netflix to work.
Click to expand...
Click to collapse
Hi yep Netflix is a beast cause it didnt accept the Widewine Version we got
Solution i used is Downloaded Netflix over ApkPure and use the Netflix Magisk OemCrypto patch.
Only in SD Quality then but for me its ok
Maybe with other Widewine Files we got Netflix in HD
Greats Triodexe
First off, thank you!
Will we need to flash this DTB with QC2.0 after every update or a one time deal?
xconwayx said:
First off, thank you!
Will we need to flash this DTB with QC2.0 after every update or a one time deal?
Click to expand...
Click to collapse
Hi
No normaly the Dtb is inside the Kernel you only need to reflash it when Qc2.0 not working you can see it when dmesg kernel and look at the Bq2419-st8 message if it shows Qc2.0 Charger.
Or easier use ampere App when your charge mA goes around 2500 then QC works.
Qc2.0 charge takes then around 45 Minutes from 15% to 90% the last percents from 90-100% charges a liitle bit slower i wouldnt stress our Batterys to much
Greats Triodexe
So flashing the dtb file using fastboot caused my Shield K1 to lock up completely, recovery and system were both bootlooping.
I was able to fix this by flashing the dtb located in this XDA thread with fastboot and wiping data, system, and cache, again using fastboot, afterwards. I was then able to boot into TWRP 3.3.1 normally and flash the ROM without the new dtb and it worked fine.
Maybe this new dtb needs more testing? Or maybe my shield is weird. Anyway just posting this here in case anyone else has this problem.
I was able to get the rom to boot after updating TWRP to the latest version. Haven't had much time to check it out yet. I tried to get the Nvidia Games app to run a game but it force closes when selecting a game. Has this worked for anyone else?
Kf_Umbra said:
So flashing the dtb file using fastboot caused my Shield K1 to lock up completely, recovery and system were both bootlooping.
I was able to fix this by flashing the dtb located in this XDA thread with fastboot and wiping data, system, and cache, again using fastboot, afterwards. I was then able to boot into TWRP 3.3.1 normally and flash the ROM without the new dtb and it worked fine.
Maybe this new dtb needs more testing? Or maybe my shield is weird. Anyway just posting this here in case anyone else has this problem.
Click to expand...
Click to collapse
Hi
Never had this problem with the dtb can you post your Bootloader Version
Needed for this rom and Dtb are the Latest bootloader=4.00.2016.04-8b2413b7
Greats Triodexe
Well, I thought i solved the booting problem with updating TRWP but it started to only boot 1 out of three times. Now it stopped booting completely so I restored my backup of LOS 14.1. How can I check the bootloader version?
bigcletus said:
I was able to get the rom to boot after updating TWRP to the latest version. Haven't had much time to check it out yet. I tried to get the Nvidia Games app to run a game but it force closes when selecting a game. Has this worked for anyone else?
Click to expand...
Click to collapse
Hi
Nvidia Games didnt work for me too i can open it and register but when i start to stream a game it crashes
With the newer Vendor Files it works but then the HW Accleration is broken.
Try to get this fixed together with the no working Camera but this crappy Logs in Logcat from Nvidia didnt show the reason why it crashes.
Only for the Camera i know that it happens after Jpeg creation that it crashes
Greats Triodexe
Triodexe said:
Hi
Never had this problem with the dtb can you post your Bootloader Version
Needed for this rom and Dtb are the Latest bootloader=4.00.2016.04-8b2413b7
Greats Triodexe
Click to expand...
Click to collapse
My bootloader is version 4.00.2016.04-8b2413b7, the latest one. I'm not sure why the dtb caused this to happen either. I even flashed NVIDIA's last recovery image before flashing this ROM, so I can't see where anything could go wrong.
Kf_Umbra said:
My bootloader is version 4.00.2016.04-8b2413b7, the latest one. I'm not sure why the dtb caused this to happen either. I even flashed NVIDIA's last recovery image before flashing this ROM, so I can't see where anything could go wrong.
Click to expand...
Click to collapse
I tryed the Dtb again flashed with Fastboot and no bootloop dont know why it didnt work for you.
Did Quickcharge works when you only flash the Rom ?
Greats Triodexe
bigcletus said:
Well, I thought i solved the booting problem with updating TRWP but it started to only boot 1 out of three times. Now it stopped booting completely so I restored my backup of LOS 14.1. How can I check the bootloader version?
Click to expand...
Click to collapse
Hi
To see Bootloaderversion boot into bootloader with volume down and Power On.
You have the Shield K1 without Lte or the normal Shield with Lte ?
Greats Triodexe
Triodexe said:
Hi
To see Bootloaderversion boot into bootloader with volume down and Power On.
You have the Shield K1 without Lte or the normal Shield with Lte ?
Greats Triodexe
Click to expand...
Click to collapse
I have the original LTE model.
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your zeroltexx, or coming from another ROM:
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
voLTE
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- enesuzun2002
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
XDA:DevDB Information
crdroid zerolte, ROM for the Samsung Galaxy S6 Edge
Contributors
SimurgAnka, Enesuzun2002
Source Code: https://github.com/Exynos7420
ROM OS Version: Android 10
Version Information
Status: Stable
Created 2020-04-16
Last Updated 2020-04-16
Reserved 1
Reserved 2
No Sim
No sim detected on s6E G925i
zerofltexx:crying:?
does this rom get updated monthly just like other Android 10 roms?
i just flashed this rom. thanks.
Thanks for the work of my favorite CrDroid rom, I hope and you can fix the problem of the sim, it does not detect it and you cannot make calls or browse with data. I have a G925i
the camera does not focus
is it possible to use the rom even without the gapps?
Thanks
Any reason why this wouldn't work with the tmobile variant (and other american carriers)? Just curious.
Any issues on G925i?
areyouanand said:
Any issues on G925i?
Click to expand...
Click to collapse
Sim card keeps turning on and off.
flip cover support
Installed this ROM on my girls S6 Edge and it runs great so far. So thanks for your effort.
Is there any chance to get the official flip cover working again? Currently it doesn't lock/unlock the phone when closing/opening the cover.
Alphalife said:
Sim card keeps turning on and off.
Click to expand...
Click to collapse
Am running Samsung Galaxy s6 edge sm-g925t
But my SIM card is not detected
Great ROM!
I just installed the latest rom, everything is fine! (g925f)... even bluetooth works! which was the reason i tested this rom, because all the other rom's i tested crashed my bluetooth-carradio, this rom works perfekt! GPS, cam, wifi, mobile data, all working fine... :good: very great rom! thanks a lot to the developers!!!!!
Awesome Rom. Everything working perfectly. No issue at all.
I flashed magisk and installed Servicely., the battery backup is now excellent specially when the phone is idle.
Thanks for this awesome rom.
I had the same issue as the other guys. I received my first call on the phone and since then the signal keeps appearing and disappearing, and no reboot fixed it. It's a shame since everything else, from camera, mobile data, bt, ringtones, works, and works well. It's a great rom if it wasn't for that issue makes a great daily driver rom. I have a SM-G925I, and somehow the rom says it's a G925F.
Great rom on 925f
I tested the rom for a while (daily use).
Everything is working fine, no issues found with call's, bluetooth, cam, gps. battery life is very good.
The only thing is that i have to turn wifi off and on to make it work again sometimes..
Before flashing this rom (and of course any others) I reinstall the official samsung rom, then i install twrp, boot into twrp, do a factory reset, wipe everything, then mount a usb drive and install the rom from the usb drive... this prevents me from the most issues other people have with this and of course other custom roms....
again a great :good: THANK YOU :good: to the developer(s)!!!
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
redfox64 said:
.......I have a SM-G925I, and somehow the rom says it's a G925F.
Click to expand...
Click to collapse
...this often happens if you do a "dirty flash". a time ago i tried to flash my g925f with a custom rom, in twrp the flash ended with "...this rom is for a g925f, your device is a g920" even wipe and/or factory reset did'nt do it for me.
i reinstalled the original samung rom, then twrp, then factory reset and wipe everything. after that i was able to install the rom without error....
buddy_67 said:
I tested the rom for a while (daily use).
Everything is working fine, no issues found with call's, bluetooth, cam, gps. battery life is very good.
The only thing is that i have to turn wifi off and on to make it work again sometimes..
Before flashing this rom (and of course any others) I reinstall the official samsung rom, then i install twrp, boot into twrp, do a factory reset, wipe everything, then mount a usb drive and install the rom from the usb drive... this prevents me from the most issues other people have with this and of course other custom roms....
again a great :good: THANK YOU :good: to the developer(s)!!!
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
...this often happens if you do a "dirty flash". a time ago i tried to flash my g925f with a custom rom, in twrp the flash ended with "...this rom is for a g925f, your device is a g920" even wipe and/or factory reset did'nt do it for me.
i reinstalled the original samung rom, then twrp, then factory reset and wipe everything. after that i was able to install the rom without error....
Click to expand...
Click to collapse
I dont know why but the issue with the signal solved itself. The only other bug I found was with screen casting. When it's connecting with wireless screen option enabled (without it, no tv is seen by the phone) the phone restarts itself.
{
"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"
}
Evolution X 5.2 for the OnePlus 7 Pro [guacamole]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
single tap gesture doesn't work, WFD doesn't work and No Verizon Network Support
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Have latest OOS 10.x flashed to both slots!!
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery
4. Wipe Data/Cache/System
5. Format Data (Required)
6. Flash the ROM
7. Reboot to System
8. Reboot to Recovery (Optional)
9. Flash Magisk (Optional)
10. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery (Optional)
4. Flash Magisk (Optional)
5. Flash the ROM
6. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
Android OS version: 11.0_r20
Security patch level: December 2020
Build Author: Justin Crawford
Source Code: https://github.com/Evolution-X
Kernel Source Code: https://github.com/Justasic/kernel_oneplus_sm8150
ROM Developer: joeyhuab
Thanks: npv12, spookcity138, chandu dyavanapelli, madgeniusgamer
Reserved
Screenshots by Android 10 ????
I have Evolution X android 10. And it's amazing it has so many features and modification Love it. Does EvoX 11 have all of these features and even more? keep up the good job
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
@justasic What version of the camera program?
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Nice ROM,so smooth,,dualboot with MSM xtended rom,
Video with OOS Cam crash,,even with shortcut,,
Parkourkid93 said:
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Click to expand...
Click to collapse
Dont wipe system,,just do format data
muphetz said:
Dont wipe system,,just do format data
Click to expand...
Click to collapse
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Parkourkid93 said:
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Click to expand...
Click to collapse
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
SaintZ93 said:
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
Click to expand...
Click to collapse
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
SaintZ93 said:
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
Click to expand...
Click to collapse
Good question, I bought it off of Amazon like a year ago though, so I don't have a 100% answer on that. Since I've gotten the device, I was able to OEM unlock, flash twrp, magisk etc. off the rip. I even dual simmed it with Google FI & Mint together without any issues and I use the global stock .zip from the OnePlus site everytime I update. If there's a way to check for sure, deff lemme know & I'll get back at you. Message me though since this isn't really ROM related & I don't want to clutter up the thread.
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
H4X0R46 said:
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
Click to expand...
Click to collapse
You can use magisk v21.2 or the modded one, it seems the fastboot issues were fixed in v21.2.
Eagle-no1 said:
@justasic What version of the camera program?
Click to expand...
Click to collapse
OOScam version 3.8.114, I didn't focus a lot on getting camera working quite yet which is why it still has some crashes, should be getting fixed as best I can in the next few updates.
ImjustSaiyan92 said:
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
Click to expand...
Click to collapse
This framerate issue is because I am forcing 90hz from the kernel (since automatic 90hz needs some work still), just lock the device and unlock it and it will go away.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
hmm I only had to use msmtool once in my experience, generally as long as you're able to get to fastboot and you've already oem unlocked, you can go back to oos usually by fastboot booting a recovery image and flashing from there. I have not heard of Google FI before so I will look into this, we just merged our January security patch so I'll be making a new release soon and it might be related to that. I've not had any issues with wiping system on my device and I keep it there in case others are looking to come from other roms. Wiping vendor would cause issues though which is why I have flashing oos there but you're welcome to skip the wiping system step as I don't believe it will cause problems since the rom flashes over system anyway.
Done all the steps. Cant connect to my home wifi, I enter password and nothing happens. Any ideas? Wifi worked before on android 11