{
"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"
}
" #DroidOnTime "
Code:
/*
*
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
*
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration.."
dotOS is an Android Rom which focuses on performance and stability. Our aim is to enable a user to extract as much juice as possible and get most out of his/her device.
Initially started by Mohan CM and later joined by Ganesh, Sam, Kuber, Iacob and Hari. Together we stand strong.
Stability and Performance
Lagfree with High Performance Results
Clutterless UI
Perfect Interface for every User
Enhanced default apps
Redesigned settings and QS panel
Full OMS support
Colour Engine Support
DotExtras
STATUSBAR
* Clock Customisation
* Battery Customisation
Quick Settings
* Quick Pulldown
* QS Tiles Customisation
* Advanced Quick Setting Easy Toggles
Buttons
* Volume Key Cursor Control
Display
* Wake on Plug
* Pocket Detection
* Accidental Touch
Lockscreen
* Fingerprint Tweaks
* Powermenu Tweaks
* Double tap 2 sleep anywhere
* Lockscreen Media Customisation
* Blur Screen Lockscreen
Recents
* Clear all Button
* Immersive Recents
* Show Memory Bar
Navigation Bar
* On screen navigation Bar tweaks
* Home Button tweaks
* Menu Button tweaks
* Back Button tweaks
* Power Button tweaks
* Volume Buttons tweaks
Misc
* Advanced Reboot
* Disable Force Close
* ScreenShot Tweaks
* Camera Shutter Sound
CLEAN FLASH :
Download the latest build and GApps
Reboot to recovery
Make NAndroid backup (Not Necessary)
Wipe System, Data, Cache , Dalvik
Flash the latest build and GApps
Reboot
DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
Download ROM:
DotOS v1.2
Download Gapps:
Note : Pico or Nano Gapps are recommended. We Don't prefer STOCK/HEAVY Gapps
OpenGapps
dotOS team
LineageOS team
ResurrectionRemix team
AospExtended
crDroid team
AICP team
And all other open source Devs/Teams.
Djeman (Main Developer)
Danijel (Developer and Tester)
PixelBoot (Developer and Thread Manager)
BUGS
Wi-Fi Connections
#AlignTheDots
XDA:DevDB Information
dotOS N, ROM for the Samsung Galaxy J3 (2016)
Contributors
PixelBoot, [email protected], djeman
Source Code: https://github.com/djeman
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Abandoned
Created 2019-06-24
Last Updated 2020-01-26
I don't recommend installing dotOS in it's status right now.
I had a hard time dealing with sources, resulting in Wifi issues.
But if you want to take a look, go ahead!
PixelBoot said:
I don't recommend installing dotOS in it's status right now.
I had a hard time dealing with sources, resulting in Wifi issues.
But if you want to take a look, go ahead!
Click to expand...
Click to collapse
Screenshots pleaaasee
GabiML said:
Screenshots pleaaasee
Click to expand...
Click to collapse
Here they are!
PixelBoot said:
Here they are!
Click to expand...
Click to collapse
Hey! PixelBoot what sources did you use in local_manifest.xml?? Please put all of the links!!! Thank you ^^
Andissace said:
Hey! PixelBoot what sources did you use in local_manifest.xml?? Please put all of the links!!! Thank you ^^
Click to expand...
Click to collapse
I used djeman's local_manifest, but changing the device tree to danijel's version.
I am aware of the wifi error being due to some sources being changed by me
I had many errors while building so some stuff had to be cut out (I think...)
I hardly think it is due to provided sources.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="external/busybox" name="LineageOS/android_external_busybox" revision="cm-14.1" />
<project path="external/stlport" name="LineageOS/android_external_stlport" revision="cm-14.1" />
<project path="packages/apps/SamsungServiceMode" name="LineageOS/android_packages_apps_SamsungServiceMode" revision="cm-14.1" />
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" revision="cm-14.1" />
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" revision="cm-14.1" />
<project path="bootable/recovery-twrp" name="omnirom/android_bootable_recovery" revision="android-7.1" />
<project path="vendor/nxp-nfc/opensource/Nfc" name="LineageOS/android_vendor_nxp-nfc_opensource_Nfc" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/frameworks" name="LineageOS/android_vendor_nxp-nfc_opensource_frameworks" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/libnfc-nci" name="LineageOS/android_vendor_nxp-nfc_opensource_libnfc-nci" revision="cm-14.1" />
<project path="device/samsung/j3xnlte" name="danijelj2001/android_device_samsung_j3xnlte" revision="cm-14.1" />
<project path="kernel/samsung/j3xnlte" name="djeman/android_kernel_samsung_j3xnlte" revision="cm-14.1" />
<project path="vendor/samsung/common" name="djeman/android_vendor_samsung_common" revision="cm-14.1" />
<project path="vendor/sprd" name="djeman/android_vendor_sprd" revision="cm-14.1" />
</manifest>
PixelBoot said:
I used djeman's local_manifest, but changing the device tree to danijel's version.
I am aware of the wifi error being due to some sources being changed by me
I had many errors while building so some stuff had to be cut out (I think...)
I hardly think it is due to provided sources.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="external/busybox" name="LineageOS/android_external_busybox" revision="cm-14.1" />
<project path="external/stlport" name="LineageOS/android_external_stlport" revision="cm-14.1" />
<project path="packages/apps/SamsungServiceMode" name="LineageOS/android_packages_apps_SamsungServiceMode" revision="cm-14.1" />
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" revision="cm-14.1" />
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" revision="cm-14.1" />
<project path="bootable/recovery-twrp" name="omnirom/android_bootable_recovery" revision="android-7.1" />
<project path="vendor/nxp-nfc/opensource/Nfc" name="LineageOS/android_vendor_nxp-nfc_opensource_Nfc" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/frameworks" name="LineageOS/android_vendor_nxp-nfc_opensource_frameworks" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/libnfc-nci" name="LineageOS/android_vendor_nxp-nfc_opensource_libnfc-nci" revision="cm-14.1" />
<project path="device/samsung/j3xnlte" name="danijelj2001/android_device_samsung_j3xnlte" revision="cm-14.1" />
<project path="kernel/samsung/j3xnlte" name="djeman/android_kernel_samsung_j3xnlte" revision="cm-14.1" />
<project path="vendor/samsung/common" name="djeman/android_vendor_samsung_common" revision="cm-14.1" />
<project path="vendor/sprd" name="djeman/android_vendor_sprd" revision="cm-14.1" />
</manifest>
Click to expand...
Click to collapse
Thank you so much for taking your time!
Everything seems to be working fine except wi-fi as you said
I installed the rom .. everything was pretty amazing
I love the smooth animations and the quiz settings that mimics the Android O
But the placement of date and time in quick settings is annoying i hope i can fix it ..and wifi is already a bug .
Other than that everything is perfect .
Prettiest rom till date?
whether later can update from ota?
Wi-Fi not work?
Fo rme same question: What excat is the wifi bug? General or sometimes?
I ask because some had wifi (disconnecting ) probs also with lineage 13/14 - but i never with same builds. In this case seems be depedency which wlan routers used/serve wifi.
BEST ROM !!
PixelBoot said:
Here they are!
Click to expand...
Click to collapse
Maybe in free time you will try to port UBPorts to our device? ^^ https://docs.ubports.com/en/latest/porting/introduction.html :highfive:
PLEASE READ EVERYTHING VERY CAREFULLY!!!
Start with building Halium!
Build like any custom LineageOS rom!
Korzin146 said:
Wi-Fi not work?
Click to expand...
Click to collapse
no, it isn't working, developers don't have enough time to fix this issue
I think this rom is little bit slow
ntrimurthulu said:
I think this rom is little bit slow
Click to expand...
Click to collapse
Turn off live display
Volte work ?
I like los, rr, oct-n roms, nougat roms only working fine in my device.
Im looking for new nougat rom with new ui style.
I have not try this rom because wifi bug you have said.
I really like this ROM, the look and the feel. Too bad the wifi is the bommer. I see comments in the different threats that TIME is a problem. Why not make one or 2 or 3 ROM's good and stable , instead of creating many different ROM's and not be able to finish the programming of the ROM's.
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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About CyanogenMod
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for CyanogenMod is available in the CyanogenMod GitHub repo.
And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Official CyanogenMod 14.1 Release post : https://wiki.cyanogenmod.org/w/Huashan_Info
Downloads Links
CyanogenMod 14.x (Unlocked Bootloader) :
Xperia SP (Huashan) : https://mega.nz/#F!i4dnRRQS!Vg9KW-BnNg6jjcg35u7jXA
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.0 : http://forum.xda-developers.com/xpe...t/recovery-twrp-3-0-0-touch-recovery-t3309938
Useful alternatives to CM Updater (with Deltas) : CM Downloader on Play Store
About CyanogenMod : ChangeLog available on http://www.cmxlog.com/14.1/huashan/
About CyanogenMod 14 Device Side : See my GitHub trees linked below
Flashing and updating
CyanogenMod clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the CyanogenMod ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
CyanogenMod update / upgrade :
- (Information) Don't wipe anything unless you want to
- (BETA / UNOFFICIAL) Nothing to wipe when switching
- Flash the latest CyanogenMod ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
CyanogenMod day-to-day updates :
- (Information) Don't wipe anything unless you want to
- (Information) Being Nightlies, try to have a safe backup once a month
- Update to latest Nightly using CM Updater or CM Downloader (link above)
- Reboot
About the builds
Device tree : https://github.com/AdrianDC/android_device_sony_huashan/commits/cm-14.1
Kernel sources : https://github.com/AdrianDC/android_kernel_sony_msm8960t/commits/cm-14.1
Vendor blobs : https://github.com/AdrianDC/proprietary_vendor_sony/commits/cm-14.1
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
Q&A - FAQ
CM-14.x Huashan Regular Questions and Answers : Q&A Thread
About CM-14.x : https://en.wikipedia.org/wiki/CyanogenMod
The CyanogenMod team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!
CyanogenMod available for Huashan also thanks to :
- The CyanogenMod Team
- Everyone involved in working and testing
XDA:DevDB Information
CyanogenMod 14.1, ROM for the Sony Xperia SP
Contributors
Adrian DC
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: No Longer Updated
Created 2016-09-14
Last Updated 2017-03-20
Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- Dual Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok, only Ext4 support missing from ROM
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok (RTC real hardware clock, in TWRP recovery too)
- Powered-off alarm : Ok
- Offline Charging : Ok
- Encryption : Status unknown
- SEPolicies : Fully enforced
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open CyanogenRecovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
Reserved
Current local manifest of the ROM build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/CyanogenMod/android -->
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" />
<project name="CyanogenMod/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" />
<project name="CyanogenMod/android_packages_apps_FMRadio" path="packages/apps/FMRadio" remote="github" />
<project name="AdrianDC/android_device_sony_huashan" path="device/sony/huashan" remote="github" />
<project name="AdrianDC/android_kernel_sony_msm8960t" path="kernel/sony/msm8960t" remote="github" />
<project name="AdrianDC/proprietary_vendor_sony" path="vendor/sony" remote="github" />
</manifest>
Already testing, ROM is really smooth, and can be used as Daily Driver. Got microgapps installed with no issues.
Update: GPS not working for me. Phone doesn't want to see any satellites
Thank you very much
Now I can start theming for CM14/all thanks goes to you
Edit : I just installed the ROM to find there's no theming engine
It's Awesome to have CM14 in XSP this soon The ROM's smoooooth
Hope it gets developed soooon Missing CM theme engine
Thanks adriandc , you're GOD of xperia sp
Cm14!!!xperia sp!!!! You are very better as Sony support team
Mr Adrian once again your bless including us again what you did for our device is more than a magic sony support is very soon end even the promise of 4.4 is not true because its never update by sony... For an old phone like xperia sp from 2013 its completely fantasy to have nougat... We find a great man a great dev God bless you i really appreciate your kind and your time that really sacrifice for us i have a question from you mr Adrian after a very magical works like multirom im stick on multirom because its amazing i set official 4.3 on primary and cm 13 on secondary my question about when i can flash cm 14 on multirom as a secondary rom? Mr adrian i hope a great life for you a life with all success in all of chapters of your life im really sorry for my bad language ?
Sent from my Xperia SP using Tapatalk
You can do this about cm14.
n78 shadow said:
Thank you very much
Now I can start theming for CM14/all thanks goes to you
Edit : I just installed the ROM to find there's no theming engine
Click to expand...
Click to collapse
Exactly , May be it's because The ROM is in Alpha Stage !!! But pretty smart ROM Really missing CM theme Engine !!
Be patient ! its just an alpha !
Wow! ... just Wow!! This is unbelievable. The amount of time and work you put into this phone is unbelievable. If it wasn't for you, I would've already bought a new phone, but thanks to your awesome support I can still have an up-to-date software experience with the newest Android features and more.
I hope development for CM14 won't be as difficult as it was when moving from Kitkat/Lollipop to Marshmallow, but seeing that the alpha-build is already working pretty okay, I have faith in you getting to run our phone with CM14 better and faster, than it already did on CM13. Keep up the great work! You're a million times better in supporting our device than those million dollar phone companies.
Does SuperSU work with CM14?
Don't need supersu.
Read the first post here and on the Q&A.
Thanks for your great ROM.
But I have a problem , I can't install V4Android ,It give me IO error.
miladn78 said:
Thanks for your great ROM.
But I have a problem , I can't install V4Android ,It give me IO error.
Click to expand...
Click to collapse
Install version for recovery, and switch off SeLinux after that.
wow, you are very hard working for making cm14 / nougat, thanks...
Works fine!
But I miss some CM13 features like themes, NFC toggler in top bar, buttons editor, buttons on locked screen editor, battery % indicator, etc. These are only Android 6 features, that are disabled in 7, or CM will add customization later?
kvazimode said:
Works fine!
But I miss some CM13 features like themes, NFC toggler in top bar, buttons editor, buttons on locked screen editor, battery % indicator, etc. These are only Android 6 features, that are disabled in 7, or CM will add customization later?
Click to expand...
Click to collapse
It's an alpha build..the features will be add later..right now they are interested in stability and bug fixes other than make everything work on 7
Sent from my Xperia SP using Tapatalk
So far this rom very good. Battery life better than cm 13
/e/
As always, you take responsibility for what you do to your phone. Don't go filing civil lawsuits against me if your alarm fails to get you up for work in the morning.
The Hell's An /e/?
"/e/ is a non-profit project, in the public interest. We build open-source mobile operating systems that respect users’ data privacy. We’re an international core team of experienced entrepreneurs, developers and designers, and a growing community of contributors." --taken from their website.
Basically think Lineage AOSP but instead of just leaving gapps out of it, they're trying to take it a step further and really give Google the finger. Their ultimate goal for the future is to make a mobile OS featuring an entire ecosystem (/e/cosystem?) that respects users' privacy and avoids the "big-companies-that-sell-your-data". They will have alternatives to the most popular Google services baked in: F-Droid instead of Google Play, something like Telegram instead of Google Hangouts, Bliss with an icon pack instead of a proprietary Google launcher, etc.
What Works?
Everything except what's listed below!
What Don't Work?
--There's no market for apps built in, so you'll have to use the browser to grab an APK of FDroid or something after install (in a future build I'll try to include FDroid in there)
--Verizon data seems a bit weird, like it'll work fine for a little bit then decide it doesn't want to and quit later on as soon as you reboot. What you need to do is reboot the phone with the SIM card taken out, then reboot it again with it back in and it'll work again. If this still doesn't work, changing the APN to Straight Talk Verizon apparently worked for some people
--USB OTG is apparently broken as well
Where's My Source Code, and How'd You Build this?
Don't worry, this took me forever to find too. I used the V1-oreo branch which is Lineage 15.1 based. The trees I'm using come from The Moto8916 Github Repo.
Here's the roomservice XML I used so you don't have to manually add it all yourself
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Device -->
<project name="moto8916/android_device_motorola_osprey" path="device/motorola/osprey" remote="github" revision="lineage-15.1" />
<project name="moto8916/android_device_motorola_msm8916-common" path="device/motorola/msm8916-common" remote="github" revision="lineage-15.1" />
<project name="moto8916/android_kernel_motorola_msm8916" path="kernel/motorola/msm8916" remote="github" revision="lineage-15.1" />
<project name="moto8916/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.1" />
<!-- Linaro 7.3 kernel toolchain -->
<project name="dev-harsh1998/GCC_BUILDS" path="prebuilts/gcc/linux-x86/arm/arm-eabi-7.3" remote="github" revision="master" />
<!-- Boringssl -->
<project name="LineageOS/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" revision="lineage-15.1" />
</manifest>
To get the custom /e/ apps in your build you have to edit the portion of vendor/cm/config/common.mk that talks about "Custom CM Packages". Go to /prebuilts/prebuiltapks for a list of folders' names you can add to this list. Note that not everything will add properly, and adding some things may mess up your ROM, so experiment at your own risk
Where's My Download Link?
--MY GOOGLE DRIVE BUILD FOLDER
--If you want MicroG as well as a replacement for GApps, our resident MicroG expert @martianmarvel said he followed this thread here and got MicroG working on his /e/ harpia just fine
Can I See Some Screenshots? (It's an older Nougat build because I'm too lazy to get new screenies but it's more or less the same theme)
{
"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"
}
Who Should You Give a Special Thanks To?
--The /e/ team (including but not limited to Gael Duval)
--All the guys here on the harpia forums for their hard work in building the trees for this thing
--@bcrichster for showing me how to get the /e/ apps to build with the ROM on this thing so I don't have to steal from AOSP anymore
--The moto8916 github repo (and all its contributors) for the trees
--All the dudes on the english Moto G3 testing group for letting me know that the ROM is working fine, I don't have a G3 myself but they tested it all for me
Very fast and beautiful ROM... but spoofing signature missing and Micro g gms don't works!!!! Fix that please.
Gnzalobnites said:
Very fast and beautiful ROM... but spoofing signature missing and Micro g gms don't works!!!! Fix that please.
Click to expand...
Click to collapse
I don't know how to spoof a signature for a ROM, and I've never used MicroG GMS so I'm not sure how to fix that either. I'll look into it though, thanks for the feedback
Gnzalobnites said:
Very fast and beautiful ROM... but spoofing signature missing and Micro g gms don't works!!!! Fix that please.
Click to expand...
Click to collapse
You could try NanoDroid which has a system patcher to activate signature spoofing.
Sent from my Nvidia Shield Tablet using XDA Labs
jemail said:
You could try NanoDroid which has a system patcher to activate signature spoofing.
Click to expand...
Click to collapse
Didn't know this was a thing, thanks for making me aware. If this actually works out on this ROM, please let me know so I can cite it up in the OP for anyone else that wants to do it too
jasonmerc said:
Didn't know this was a thing, thanks for making me aware. If this actually works out on this ROM, please let me know so I can cite it up in the OP for anyone else that wants to do it too
Click to expand...
Click to collapse
I don't use OREO or PIE ROMs, only NOUGAT on my osprey. O and P don't run so well on osprey in my experience. The newest shiny thing is not necessarily the best ?.
Maybe you or another user can test NanoDroid system patching on your ROM ?.
Sent from my Nvidia Shield Tablet using XDA Labs
jemail said:
I don't use OREO or PIE ROMs, only NOUGAT on my osprey. O and P don't run so well on osprey in my experience. The newest shiny thing is not necessarily the best ?.
Maybe you or another user can test NanoDroid system patching on your ROM .
Sent from my Nvidia Shield Tablet using XDA Labs
Click to expand...
Click to collapse
/e/ os nougat is here: https://gitlab.e.foundation/e/wiki/en/wikis/device/osprey/info
Gnzalobnites said:
/e/ os nougat is here: https://gitlab.e.foundation/e/wiki/en/wikis/device/osprey/info
Click to expand...
Click to collapse
Be cautious with that though, as nougat Lineage (which /e/ is based off of) is no longer being supported or maintained. That's why I moved onto building Oreo roms, so we can get things like security updates down the road
jemail said:
I don't use OREO or PIE ROMs, only NOUGAT on my osprey. O and P don't run so well on osprey in my experience. The newest shiny thing is not necessarily the best ?.
Maybe you or another user can test NanoDroid system patching on your ROM ?.
Click to expand...
Click to collapse
Try du pie i am sure your gonna love it and its maintained on weekly basis
lonkar said:
Try du pie i am sure your gonna love it and its maintained on weekly basis
Click to expand...
Click to collapse
There is no official build of Dirty Unicorns for osprey. Osprey is not on the supported device list.
What is your link for this DU build?
Sent from my Nvidia Shield Tablet using XDA Labs
jemail said:
There is no official build of Dirty Unicorns for osprey. Osprey is not on the supported device list.
What is your link for this DU build?
Click to expand...
Click to collapse
Check latest builds here
https://androidfilehost.com/?w=profile&uid=23610159112650996
New April build is up for eelo on osprey. Not sure what changed, besides maybe a security patch update (maybe)
EDIT: Sorry about that, apparently the upload of the April build failed before, gonna reupload it again soon and hopefully it stays this time
lonkar said:
Check latest builds here
https://androidfilehost.com/?w=profile&uid=23610159112650996
Click to expand...
Click to collapse
Thanks for the link.
I may give it a try, although these are unofficial builds.
Sent from my Nvidia Shield Tablet using XDA Labs
{
"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:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Always Have a full functional Backup. Just in case!
Rom Download Link :
https://androidfilehost.com/?fid=8889791610682935022
Lineage Recovery link :
https://androidfilehost.com/?fid=8889791610682935019
Recomended Bootloader/Modem : https://androidfilehost.com/?fid=3700668719832239236 (I9506XXUDRB1_I9506XXUDRA1)
GAPPS: DOWNLOAD GAPPS - Not updated yet for 10.0 -- use Beta from link below
Platform: ARM
Android: 10.0
OpenGapps : https://opengapps.org/
BITAGaaps : https://androidfilehost.com/?fid=4349826312261650978
Device Source:
Device : https://github.com/Khalvat-M/android_device_samsung_ks01ltexx
Kernel : https://github.com/Khalvat-M/kernel_samsung_msm8974
Vendor : https://github.com/Khalvat-M/vendor_samsung
** Make sure you're running a proper working Recovery (TWRP is recommended)
TWRP Link : https://dl.twrp.me/ks01lte/
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 v20.1 (whatever is most recent, Android 10 is now supported)
ROM Asking for Decryption key on boot:
This isn't a ROM issue, but an issue with your device. Kindly boot into TWRP and go to wipe - choose FORMAT - TYPE - YES
***This WILL wipe your INTERNAL storage. Backup before performing the format.
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
1. You tell me
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:
- fagyi - Can't stress enough how much you do. Thank you so much for everything!!!
- Google
- LineageOS
- SlimRoms
- AOSPA
- AOSIP
- AICP
- OmniRom
- NamelessROM
- Many others... (if you've been left out just send a PM )
XDAevDB Information
[ROM] [10.0] crDroidAndroid v6.0 [UNOFFICIAL], ROM for the S4 i9506( ks01lte)
Contributors
khalvat
Source Code: https://github.com/crdroidandroid
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Stable
Created 2019-12-10
Last Updated 2020-09-11
mod edit: translated
Long live the S4. Thanks for the input
Sent from my POCO F1 mediante Tapatalk
Larga vida al S4. Gracias por el aporte
Enviado desde mi POCO F1 mediante Tapatalk
Which bootloader and Modem is it built for?
DiamondJohn said:
Which bootloader and Modem is it built for?
Click to expand...
Click to collapse
Added in post
jegogo99 said:
mod edit: translated
Long live the S4. Thanks for the input
Sent from my POCO F1 mediante Tapatalk
Larga vida al S4. Gracias por el aporte
Enviado desde mi POCO F1 mediante Tapatalk
Click to expand...
Click to collapse
Hey there please remember to post in english! I translated it for you!
khalvat said:
Guys I will not update Havoc until its problams are resolved. Our new android 10 CrDroid is available and its stable working android 10 features well:good:
Click to expand...
Click to collapse
FYI: I cannot get Magisk 20.1 installed on crDroid. however, the playstore does download and install apps.
crDroid home launcher crashes every time(see attached for logcat), pixel launcher works.
I also didn't get a GPS Fix. Admittedly indoors, but my current Havoc-OS Oreo did right next to it.
DiamondJohn said:
FYI: I cannot get Magisk 20.1 installed on crDroid. however, the playstore does download and install apps.
crDroid home launcher crashes every time(see attached for logcat), pixel launcher works.
I also didn't get a GPS Fix. Admittedly indoors, but my current Havoc-OS Oreo did right next to it.
Click to expand...
Click to collapse
All good here. No any crash
1 Flash Rom without gapps and boot to rom
2 After working for a while reboot and flash latest beta gapps
3 magisk for root will fix soon in next builds
New build 2019-12-16 is Available
Device changelog:
Fixed some minor bugs
Added samsung Doze
khalvat said:
All good here. No any crash
1 Flash Rom without gapps and boot to rom
2 After working for a while reboot and flash latest beta gapps
3 magisk for root will fix soon in next builds
Click to expand...
Click to collapse
khalvat said:
New build 2019-12-16 is Available
Device changelog:
Fixed some minor bugs
Added samsung Doze
Click to expand...
Click to collapse
I just dirty flashed the latest build over the previous build. It tried to re-instate Magisk, but failed.
Would a clean flash enable Magisk?
DiamondJohn said:
I just dirty flashed the latest build over the previous build. It tried to re-instate Magisk, but failed.
Would a clean flash enable Magisk?
Click to expand...
Click to collapse
Sorry Magisk issue still not fixed.
When I launch the music player, it seems, that the sound is skewed. The some is when I use the "Duolingo". In the previous version is all right.
kiprio said:
When I launch the music player, it seems, that the sound is skewed. The some is when I use the "Duolingo". In the previous version is all right.
Click to expand...
Click to collapse
Yeah. I know.its was my mistake in latest build. Fixed audio bug now so wait for new build
khalvat said:
Yeah. I know.its was my mistake in latest build. Fixed audio bug now so wait for new build
Click to expand...
Click to collapse
I have successfully built the ROM from your source:good:, but I have not test-flashed it to see if it works.:fingers-crossed:
The changes I had to make to get it to build (from memory)
Code:
echo "# dummy" > hardware/samsung/AdvancedDisplay/Android.mk;
echo "# dummy" > device/samsung/qcom-common/doze/Android.mk;
## (geany [B]hardware/interfaces/audio/common/all-versions/default/service/Android.mk[/B])
## [B]remove line 56[/B]
## [B][email protected] \[/B]
Is that related to above issue?
I personally do not use bluetooth audio (so NO issue for me personally), but does the above mean there is an issue with bluetooth audio? or do you use another fix not in github?
So, the takeaway is the source can be built pretty easily :good:
Can anyone check bluetooth audio?
===================================
edit: the actual error
Code:
hardware/interfaces/audio/common/all-versions/default/service/Android.mk: error: "[email protected] (EXECUTABLES android-arm) missing [email protected] (SHARED_LIBRARIES android-arm)"
DiamondJohn said:
I have successfully built the ROM from your source:good:, but I have not test-flashed it to see if it works.:fingers-crossed:
The changes I had to make to get it to build (from memory)
Code:
echo "# dummy" > hardware/samsung/AdvancedDisplay/Android.mk;
echo "# dummy" > device/samsung/qcom-common/doze/Android.mk;
## (geany [B]hardware/interfaces/audio/common/all-versions/default/service/Android.mk[/B])
## [B]remove line 56[/B]
## [B][email protected] \[/B]
Is that related to above issue?
I personally do not use bluetooth audio (so NO issue for me personally), but does the above mean there is an issue with bluetooth audio? or do you use another fix not in github?
So, the takeaway is the source can be built pretty easily :good:
Can anyone check bluetooth audio?
===================================
edit: the actual error
Code:
hardware/interfaces/audio/common/all-versions/default/service/Android.mk: error: "[email protected] (EXECUTABLES android-arm) missing [email protected] (SHARED_LIBRARIES android-arm)"
Click to expand...
Click to collapse
Nice:good:. If u can start pixelexprience build and share in our XDA page.
khalvat said:
Nice:good:. If u can start pixelexprience build and share in our XDA page.
Click to expand...
Click to collapse
Two problems there.
1. I build for my own devices/uses and share on XDA if there is no-one else building it, or has provided a recent build.
2. I like the most eye candy I can get , and Pixel Experience is targeted for an AOSP experience :cyclops:. ie not for me.
I can not get the GPS fix. The phone sees many satellites, but does not fix the position. How can I solve this?
PS. GOOD ROM. The battery lasts a long time!
replaced by I9506XXSDPL2_I9506XXUDOJ2_bootmodem GPS fix- OK!!!
A rooted crDroid!
khalvat said:
Sorry Magisk issue still not fixed.
Click to expand...
Click to collapse
FYI I just did a build using @kyasu kernel, and the small changes I noted above, and it built without a hitch, and Magisk flashed AND is working. So I now have a rooted crDroid :highfive:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-17.0" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-17.0" />
<project name="Khalvat-M/android_device_samsung_ks01ltexx" path="device/samsung/ks01ltexx" remote="github" revision="10.0" />
<project name="Khalvat-M/vendor_samsung" path="vendor/samsung" remote="github" revision="10.0" />
<project name="Khalvat-M/kernel_samsung_msm8974" path="kernel/khalavat_samsung/msm8974" remote="github" revision="10.0" />
<project name="kyasu/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-17.0-test" />
</manifest>
Not being rooted meant not being able to actually install/use my most commonly used apps. So this will be good until you get your kernel sorted:good:
oooo.... it really did not like the install of the latest viper, which uses Magisk.
DiamondJohn said:
FYI I just did a build using @kyasu kernel, and the small changes I noted above, and it built without a hitch, and Magisk flashed AND is working. So I now have a rooted crDroid :highfive:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-17.0" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-17.0" />
<project name="Khalvat-M/android_device_samsung_ks01ltexx" path="device/samsung/ks01ltexx" remote="github" revision="10.0" />
<project name="Khalvat-M/vendor_samsung" path="vendor/samsung" remote="github" revision="10.0" />
<project name="Khalvat-M/kernel_samsung_msm8974" path="kernel/khalavat_samsung/msm8974" remote="github" revision="10.0" />
<project name="kyasu/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-17.0-test" />
</manifest>
Not being rooted meant not being able to actually install/use my most commonly used apps. So this will be good until you get your kernel sorted:good:
oooo.... it really did not like the install of the latest viper, which uses Magisk.
Click to expand...
Click to collapse
Yeah it was from kernel but im working on other devices so have not time for change kernel source for now.
Also add devicesettings in roomservices from linneageos
New build 2020-01-01 is Available
Fixed bugs
I had not time to fix root problam so i will fix in next build
Happy new year???️??Merry christmas
khalvat said:
New build 2020-01-01 is Available
Fixed bugs
I had not time to fix root problam so i will fix in next build
Happy new year?️Merry christmas
Click to expand...
Click to collapse
Great News Sir
HNY & MC , Wishes You All The Success in Your Pro And Perso life
Regards .
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- TWRP boots.
- Decryption is working.
- Vibration
- System, Vendor and Product partitions mount is working but you can't modify them.
- You can flash magisk, miui roms, kernels, firmwares, etc.
Not working:
- Partition formatting (upstream)
- ADB sideload (upstream)
Install guide:
To boot (Reccomended):
Code:
fastboot boot <twrp.img>
To install (NOT reccomended):
Code:
fastboot flash recovery <twrp.img>
Download:
Now build is checking "ro.boot.hwversion". If it is begined with "1" then use Mi 10 Pro cmi profile, otherwise it will use Mi 10 umi profile.
Please report ro.boot.hwversion if possible. You can get it from getprop command.
Mega Drive Link
Source code:
Device Tree
Recovery Source
Thanks:
@mauronofrio @bigbiff and more open source TWRP devs.
Mi 10 (umi) thread:
https://forum.xda-developers.com/xi...t/experimental-unofficial-twrp-mi-10-t4106381
cc @TipzTeam Could you help me to do some functional test? I didn't own a Mi 10 Pro.
simonsmh said:
cc @TipzTeam Could you help me to do some functional test? I didn't own a Mi 10 Pro.
Click to expand...
Click to collapse
yes, you can send me the tree and i am able to compile, dont say you based on instantnoodles
TipzTeam said:
yes, you can send me the tree and i am able to compile, dont say you based on instantnoodles
Click to expand...
Click to collapse
The instantnoodle maintainer helped me a lot on decryption.
The source is in the post. In case you need, here is part of the roomservice.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="build/make" name="simonsmh/android_build" remote="github" revision="android-10" >
<copyfile src="core/root.mk" dest="Makefile" />
<linkfile src="CleanSpec.mk" dest="build/CleanSpec.mk" />
<linkfile src="buildspec.mk.default" dest="build/buildspec.mk.default" />
<linkfile src="core" dest="build/core" />
<linkfile src="envsetup.sh" dest="build/envsetup.sh" />
<linkfile src="target" dest="build/target" />
<linkfile src="tools" dest="build/tools" />
</project>
<project path="build/soong" name="AndroiableDroid/android_build_soong" remote="github" revision="ten" >
<linkfile src="root.bp" dest="Android.bp" />
<linkfile src="bootstrap.bash" dest="bootstrap.bash" />
</project>
<project path="system/core" name="simonsmh/android_system_core" remote="github" revision="android-10.0" />
<project path="bootable/recovery" name="simonsmh/android_bootable_recovery" remote="github" revision="android-10.0" />
<project path="device/xiaomi/umi" name="simonsmh/android_device_xiaomi_umi" remote="github" revision="android-10.0" />
</manifest>
Uncomment Thttps://github.com/simonsmh/android_device_xiaomi_umi/blob/android-10.0/init/Android.bp#L9 if you are on Mi 10 Pro.
Do you have Telegram account? You could find me there.
simonsmh said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- TWRP boots.
- Decryption is working.
- System, Vendor and Product partitions mount is working but you can't modify them.
- You can flash magisk, miui roms, kernels, firmwares, etc.
Not working:
Partition formatting (upstream)
f2fs (upstream)
Vibration
Install guide:
To boot (Reccomended):
Code:
fastboot boot <twrp.img>
Download:
Currently it's not unified. I provide two builds just for flashing rom with "ro.product.device" check, but they should be ok to boot either of them.
umi is for Mi 10.
cmi is for Mi 10 Pro.
Mega Drive Link
Source code:
Device Tree
Recovery Source
Thanks:
@mauronofrio @bigbiff and more open source TWRP devs.
Mi 10 (umi) thread:
https://forum.xda-developers.com/xi...t/experimental-unofficial-twrp-mi-10-t4106381
Click to expand...
Click to collapse
Have you noticed any Wi-Fi problems?
Thanx
simonsmh said:
The instantnoodle maintainer helped me a lot on decryption.
The source is in the post. In case you need, here is part of the roomservice.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="build/make" name="simonsmh/android_build" remote="github" revision="android-10" >
<copyfile src="core/root.mk" dest="Makefile" />
<linkfile src="CleanSpec.mk" dest="build/CleanSpec.mk" />
<linkfile src="buildspec.mk.default" dest="build/buildspec.mk.default" />
<linkfile src="core" dest="build/core" />
<linkfile src="envsetup.sh" dest="build/envsetup.sh" />
<linkfile src="target" dest="build/target" />
<linkfile src="tools" dest="build/tools" />
</project>
<project path="build/soong" name="AndroiableDroid/android_build_soong" remote="github" revision="ten" >
<linkfile src="root.bp" dest="Android.bp" />
<linkfile src="bootstrap.bash" dest="bootstrap.bash" />
</project>
<project path="system/core" name="AndroiableDroid/android_system_core" remote="github" revision="android-10.0" />
<project name="simonsmh/android_bootable_recovery" path="bootable/recovery" remote="github" revision="android-10.0" />
<project path="device/xiaomi/umi" name="simonsmh/android_device_xiaomi_umi" remote="github" revision="android-10.0" />
</manifest>
Then define cmi instead of umi in https://github.com/simonsmh/android_device_xiaomi_umi/blob/android-10.0/init/init_umi.cpp if you are on Mi 10 Pro.
Do you have Telegram account? You could find me there.
Click to expand...
Click to collapse
Please contact me on telegram asap, i can't pm people rn because i am blocked on telegram for doing that for some idk reasons. my tele is @TipzTeam
---------- Post added at 02:22 AM ---------- Previous post was at 02:07 AM ----------
Tested and works!
Awesome work Dude, the Mi 10 series ist finally getting a trustworthy TWRP. Keep up the good work.
I'll try when I just can unlock the bootloader. Can I flash magisk via twrp or should I patch boot.img?
henkka22 said:
I'll try when I just can unlock the bootloader. Can I flash magisk via twrp or should I patch boot.img?
Click to expand...
Click to collapse
I have tested this. You can install magisk zip and miui rom zips.
Do I have to flash it via ADB? I flashed your version with the closed source TWRP which is available. When I try to boot your TWRP I am forced into the fastboot mode
Hi guys, new build (rev. 2) has been uploaded. Tested fastboot flash recovery is working.
The way to fix it is just appending recovery dtbo from official recovery. Source code has been updated.
cc @nocturnoz
Thanks! I'd like to test it for my cmi, but I cant find an 3.3.1-2.img file
nocturnoz said:
Thanks! I'd like to test it for my cmi, but I cant find an 3.3.1-2.img file
Click to expand...
Click to collapse
Try umi, and report if it is detected as cmi. I'm testing the unified feature.
Use adb to get getprop result and post it here would be helpful.
simonsmh said:
Try umi, and report if it is detected as cmi. I'm testing the unified feature.
Unified is working.
Use adb to get getprop result and post it here would be helpful.
Click to expand...
Click to collapse
Here is my getprop:
Hi
Just wondering if it's working on cmi? Gonna unlock bootloader tomorrow
Awesome work
raven213 said:
Hi
Just wondering if it's working on cmi? Gonna unlock bootloader tomorrow
Awesome work
Click to expand...
Click to collapse
Try and tell us because and i wait 10 pro to come at 9 june
apokit said:
Try and tell us because and i wait 10 pro to come at 9 june
Click to expand...
Click to collapse
The unified fuction works and can be flashed. Flashing ROMs, Magisk etc works too. Backups not, but im sure the devoper will get it working soon
nocturnoz said:
The unified fuction works and can be flashed. Flashing ROMs, Magisk etc works too. Backups not, but im sure the devoper will get it working soon
Click to expand...
Click to collapse
will 3.4.0-1 work for cmi devices ..
sanish4u said:
will 3.4.0-1 work for cmi devices ..
Click to expand...
Click to collapse
Try it first, and report with getprop, otherwise nobody knows if it's working.
3.4.0-1 tried to fix backup binary bu
missing issue, now backup should be fine but not tested.
dude twrp gives a error failed to mount system_root(read only file system )
how i fix this ..
i m unble to install a rom
{
"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"
}
About Us:
Superior OS is an AOSP-based custom ROM with a bunch of features to fulfill the user's demands nowadays.
Code:
[/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER]
[FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER]* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration"
CLEAN FLASH:
Download the latest build and GApps (GApps only if vanilla build is downloaded)
Reboot to recovery
Take backup (not mandatory)
Wipe System, Vendor, Data, Cache, Dalvik
Flash the latest build and GApps (GApps only if vanilla build is downloaded)
Reboot
DIRTY FLASH:
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
NOTE: Don't flash GApps and Magisk again
Code:
[/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER][/FONT][/CENTER]
[FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER][FONT=Trebuchet MS][CENTER]THEMEING
- Black theme
- Custom accent picker
- Headline/body fonts
- Icon packs
- Icon shapes
- Monet customizations
- Statusbar icons
- WiFi icons
STATUSBAR
- 4G icon instead of LTE
- Battery styles
- Combined signal icons
- Colored notification icons
- Old mobile type indication
- Statusbar icon tuner
- Traffic indicators
- VoLTE icon toggle
NAVIGATION BAR
- Extended swipe actions
- Haptic feedback toggle for the back gesture
- System navigation
QUICK SETTINGS
- Brightness slider positions
- Quick pulldown option
- Vibrate on touch
GESTURES
- Statusbar brightness swipe control
- Double-tap to sleep
- Quick open camera
- One-handed mode
- Power button press and hold gesture
- Power button torch gesture
- Screen off the power button torch
- Three-finger swipe screenshot
BUTTONS
- Reorient volume buttons
- Skip music tracks
- Volume rocker wake
NOTIFICATIONS
- Heads-up options
- In-call Vibrations
- Notification header
- Toast app icon
POWER MENU
- Advanced reboot
- Power menu items
LOCK SCREEN
- Charging info
- Small clock toggle
- Media art as background
Lots more coming soon!
Stay Tuned!
Download ROM:
SuperiorOS
Gapps
Download GApps:
MindTheGApps
NOTE: Core version recommended
AOSP
Lineage OS
AospExtended
PixelExperience
Arrow OS
Pixys OS
SuperiorOS Core Team
Sipun Ku Mahanta
Jayant Deshmukh
Nipin NA (Joker-V2)
Adnan Faysal
Arun Teltia
Special Thanks
Sam Grande
Pavan Patel
Ionut Iacob
Loved the ROM? Want to help it imporove? Gift us with some credits!
Superior OS source
SuperiorOS-Device Sources
Telegram Group
Telegram Channel
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
XDA Information:SuperiorOS, ROM for the Redmi Note 11SuperiorOS Version Name: TwelveDevice: Spes/SpesnMaintainer: Enweazu Daniel (Danny)Build Type: UnofficialResources Used:Source Code:SuperiorOSDevice Tree Source:SpesKernel Source:KernelVersion Information:ROM OS Version: 12.1.xROM Kernel: 4.19.157ROM Firmware Required: Must be on Latest FirmwareBased On: AOSPStatus: StableCurrent Stable Version: TwelveSELinux Status: EnforcingStable Release Date: 2022-08-19Created 2022-06-14Last Updated 2022-09-18
I am really looking forward to a Google-less ROM. However currently AndroidFileHost doesn't offer a mirror to download from (at least since yesterday). This applies to both Note 11 builds.
Is it possible to build it yourself? With a custom roomservice.xml like this one:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/spes" remote="github" name="enweazudaniel/android_device_xiaomi_spes" revision="12.1" />
<project path="kernel/xiaomi/spes" remote="github" name="enweazudaniel/kernel_xiaomi_spes_header" revision="12" />
<project path="vendor/xiaomi/spes" remote="github" name="enweazudaniel/android_vendor_xiaomi_spes" revision="12.1" />
</manifest>
I have admittedly not a lot of experience with building Android
NetDwarf said:
I am really looking forward to a Google-less ROM. However currently AndroidFileHost doesn't offer a mirror to download from (at least since yesterday). This applies to both Note 11 builds.
Is it possible to build it yourself? With a custom roomservice.xml like this one:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/xiaomi/spes" remote="github" name="enweazudaniel/android_device_xiaomi_spes" revision="12.1" />
<project path="kernel/xiaomi/spes" remote="github" name="enweazudaniel/kernel_xiaomi_spes_header" revision="12" />
<project path="vendor/xiaomi/spes" remote="github" name="enweazudaniel/android_vendor_xiaomi_spes" revision="12.1" />
</manifest>
I have admittedly not a lot of experience with building Android
Click to expand...
Click to collapse
Yeah you can build with that but there's a mirror download link
enweazudaniel said:
Yeah you can build with that but there's a mirror download link
Click to expand...
Click to collapse
GDrive mirror doesn't seem to work either Thank you for the quick answer nevertheless. I am pretty hyped, if I get my hands on it today or in a week is not that big of a deal.
Answer from Google Drive said:
Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator.
Click to expand...
Click to collapse
NetDwarf said:
GDrive mirror doesn't seem to work either Thank you for the quick answer nevertheless. I am pretty hyped, if I get my hands on it today or in a week is not that big of a deal.
Click to expand...
Click to collapse
What normally works for you?
enweazudaniel said:
What normally works for you?
Click to expand...
Click to collapse
GitHub I guess.
GDrive and AndroidFileHost usually work, too. GDrive has its limitations, but AndroidFileHost does work for other downloads of yours, so I am a bit confused why it doesn't work for these specific ones. The DL counter also didn't move since yesterday (31 for non-GApps and 9 for GApps), so it's conceivable that it doesn't work for anyone.
Hi, just for spes, or can it be used for spesn? Thanks
NetDwarf said:
immortals1 said:
Hi, just for spes, or can it be used for spesn? Thanks
Click to expand...
Click to collapse
For Both
Click to expand...
Click to collapse
So far the best rom I've tried
immortals1 said:
So far the best rom I've tried
Click to expand...
Click to collapse
does this rom has annyoing fingerprint bug??
mzubairtariq said:
does this rom has annyoing fingerprint bug??
Click to expand...
Click to collapse
it does not and the camera works. The operation of the system is very nice
NetDwarf said:
GDrive mirror doesn't seem to work either Thank you for the quick answer nevertheless. I am pretty hyped, if I get my hands on it today or in a week is not that big of a deal.
Click to expand...
Click to collapse
Maybe this will help:
Oifan said:
Maybe this will help:
Click to expand...
Click to collapse
Thank you for this tip. It actually does work now, however it's the GApps version. I wonder why the AFH downloads are still broken.
Do we have DC dimming feature on this ROM.
Could someone upload the zip again? Not the GAPPS included one, but the core AOSP. Thanks.
hell-zerg said:
Could someone upload the zip again? Not the GAPPS included one, but the core AOSP. Thanks.
Click to expand...
Click to collapse
Zip still up there on Andriodfilehost but don't know why they're no mirrors I've written to them (Andriodfilehost) regarding this issue but no reply.
If you can wait once July sec patch is merged in the coming days I'll release a build and possibly use others cloud storage like sourceforge this time.
enweazudaniel said:
Zip still up there on Andriodfilehost but don't know why they're no mirrors I've written to them (Andriodfilehost) regarding this issue but no reply.
If you can wait once July sec patch is merged in the coming days I'll release a build and possibly use others cloud storage like sourceforge this time.
Click to expand...
Click to collapse
Okay, will wait for it, because I want a pure AOSP rom on my Redmi Note 11. Thanks for providing it.
enweazudaniel said:
Zip still up there on Andriodfilehost but don't know why they're no mirrors I've written to them (Andriodfilehost) regarding this issue but no reply.
If you can wait once July sec patch is merged in the coming days I'll release a build and possibly use others cloud storage like sourceforge this time.
Click to expand...
Click to collapse
Have you tried mega or mediafire, Might be a more reliable solution?
xynny said:
Have you tried mega or mediafire, Might be a more reliable solution?
Click to expand...
Click to collapse
Will do. Thanks
enweazudaniel said:
Will do. Thanks
Click to expand...
Click to collapse
No problem, It is weird that androidfilehost has issues but using multiple mirrors is a good idea.