You're stuck on MIUI 12.5.4.0 and you cant flash a working custom recovery?
You're too lazy or too newbish to build your own?
Cant flash any Custom Rom?
Well you can just learn how to flash these TREBLE PHH Images, GSI-AOSP based images.
Here i show you how to flash CRDroid v316 . Its based on Android 11R
These images can be flashed with just fastbootd, and they work PERFECTLY, even better than many of the images i've tried here.
You wont have to face hardbricks ever again (specially when flashing MIUI), you can get rid of it once and for all, get rid of Xiaomi and all of its bloatware.
And you can always continue flashing these ROMS or other ROMS (If they're the same Android version or 1 version above). They have root by default most of them.
I made a guide showing how to flash this image.
Xiaomi Redmi 9A 9i 9AT 10A
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Supported Devices: Xiaomi Redmi 9A 9i 9AT 10A
To flash
Basically you just need:
Stock Recovery
Bootloader Unlocked
vbmeta.img (you can also use the one that comes with your MIUI IMAGE)
ADB/Fastboot
An " arm32_binder64 " image (Also called A64 image) that is compatible with your Android Version. (For example This image of CRDroid crdrom-v316-220330-a64-bvZ.img.xz is compatible for us, its the one being used in the tutorial).
Patience
What works?
Everything works, there are bugs in Display Brightness and Headphones
VOLTE (UNTESTED)
What doesn't Work?
In some images, of A10 - A13, for somer eason, RIL , the Radio Interface Layer is dead, so SIM doesn't work, we need to build Images or somehow work-around it, or try various images, to see which ones work.
So far RIL works perfectly, sim card works in eremitein Images, you will find a link to these images posted on the guide.,
RIL/SIM works in the the CRDroid image i used, it was built/published by eremitein.
All credits go to these people.
Fixes*Improve Wifi - Disable Wifi Power Saving
Important fix " In many Android 11 custom roms the Wifi in this phone becomes weaker, Less txpower, refresh 3 times max every 2 mins, has sometimes latency, range issues, this will improve it by 10-15%
Open Terminal Emulator
Turn your wifi on like a big man, use:
su
iw dev wlan0 set power_save off
(to check that your wifi powersaving has been turned off, use)
iw dev wlan0 get power_save
exit
exit
(To make this persistent between reboots, use an apk to launch scripts on boot)
*Improve Wlan0 TxPower
(In the future i will add how to change TxPower, lets be patient, im learning too, it seems possible though, i need it for pentesting, i discovered a way to use our precious monitor mode, but its my secret only, if someone teaches me how to improve txpower i will teach them to use monitor mode, we can trade)
*Fix headphone issues, if present, execute these lines on any Terminal Emulator then reboot.
su
setprop persist.sys.overlay.devinputjack true
*Fix brightness/display adjustment,
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
Please Report if the CRDroid Image works for you. And if you have the Time/Internet available feel free to download other Images from different developers and report if other Images work perfectly or not.
I for my part will stick to this rom for a looooong time, and wait until android 14-16 has released, maybe then i will meditate upon using another phone/rom (because it just works very well for me).
More information can be found here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list/
Well, was stuck on MIUI 12.5.3.0 global, did not wanna test my luck flashing custom recoveries so tried this, so far good, only bug for my is bluetooth can t transmit data, connects ok but no data or music, so i use headphones and everything is ok, ,RIL is ok, don t use volte, auto brightness bug is more or less livable, haven t tested the fix in terminal yet, SOT more than 5hours in a no game scenario, more than 48 hours of charge from 100% to 13%, phone charges as expected, feels very snappy, using a Gcamgo and almost as good as miui cam, excellent work to eremitein.
cvmg333 said:
.... using a Gcamgo and almost as good as miui cam, excellent work to eremitein.
Click to expand...
Click to collapse
Thanks for this! Do you know if camera2 API is enabled in this ROM? By that, I mean do manual camera options like ISO, shutter speed options exist? You can check by installing camera apps like Open Camera.
Thanks.
MaverickNextDoor said:
Thanks for this! Do you know if camera2 API is enabled in this ROM? By that, I mean do manual camera options like ISO, shutter speed options exist? You can check by installing camera apps like Open Camera.
Thanks.
Click to expand...
Click to collapse
Hi, its not enabled by default, but it can be activated in crdroid settings, and yes Open Camera manual options are working.
cvmg333 said:
Hi, its not enabled by default, but it can be activated in crdroid settings, and yes Open Camera manual options are working.
Click to expand...
Click to collapse
Thanks so much!
Found glitch in this Rom, if i turn on lockscreen security by pattern, sudenly home key and recents key stop working, if i deactivate the lockscreen security feature, navbar buttons work as the should again.
Related
This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m
Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:
Updates and Notes
Reserved
Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.
@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here
Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:
@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel:
Note: Since the patches essential for making this device work has been merged into LineageOS main repo, there is no need to maintain a separate unofficial build anymore. All fixes go to the official repository and you can expect the official LOS nightly builds to contain the most updated code. You can still use this thread for bug reports though. But bear in mind that some bugs that only appear on specific batches and cannot be reproduced on our devices are harder to fix.
Introduction
This is an UNOFFICIAL build of LineageOS for OnePlus 7 Pro (5G version NOT TESTED, probably won't work). While most features should be working, remember that this is a very early version and things could break, especially for a device as new as this one. I have literally just got hands on it last weekend and spent a few days fixing issues like the fingerprint scanner and motorized front camera. Please always flash with caution.
What's working
- All basic stuff like telephone, bluetooth, nfc, camera, volte, etc.
- Fingerprint scanner (works but with a few minor issues that doesn't affect using it)
- Front camera motor
- Light sensor (sort of, read below for information)
- 90hz screen (with some bugs described below)
Known Issues + TO-DOs
- When booting, the system will alert you of an "internal problem". This is completely fine, just ignore it for now no more internal problems since 20190629 because it comes with its own vendor image.
- Bluetooth audio not working sometimes. Fixed in 20190622
- Auto brightness doesn't work. Partially fixed in 20190622
- In some cases the phone will crash when playing audio. Seems to be problem of AudioFX. I'm looking into it. If you get stuck in recovery after the phone crashes, you can fix it by simply re-flashing anything. Even re-flashing Magisk will work. Fixed in 20190624
- Light sensor doesn't work exactly as it is in official ROM, causing some issues with auto brightness. This is due to the fact that the light sensor is located under the screen, and OnePlus seem to have some magic in their frameworks code to cancel the effect of the screen. For now, I did a very very dirty hack to make it at least work, but no magic is implemented. Expect some issues with this thing. If you find it annoying, I'd suggest disabling it at least for now.
- I have tried to implement an algorithm to correct the readings of the in-display ambient light sensor, but it is still very very funky especially in low-light environment. Fixed since 20190706
- Fingerprint scanning has some quirks here and there. Sometimes the screen goes entirely black except for the scanning area, sometimes the screen may flash a little bit while scanning (tried to reduce it since 20190629). On landscape mode it appears at the wrong place. (fixed since 20190629) But it at least works. I am working to figure out exactly how to make it perfect but it would take some time. (These were also bugs present on the OnePlus 6T / Xiaomi 9 implementation. I have tried to clean them up and fixed some of the issues that were present. At least the screen now doesn't dim like crazy as on OnePlus 6T / Xiaomi 9 implementation, because it dims the correct amount to make screen area other than the scanner circle to appear as bright or dark as it was before increasing the brightness for scanning. Also it works around the somewhat eye-straining Android brightness-changing animation by using a kernel interface provided by OnePlus, exactly as how they did this in their official ROM.)
(Note: if your fingerprint icon gets stuck on home screen, try the following steps: lock your phone, turn on the screen, swipe up for password/pattern unlock, then immediately press the back button, then use fingerprint to unlock. I'll try to get this fixed in the future.)
- Screen colors and refresh rate is a bit messed up when booting. If you find your screen laggy or strange, just turn it off and turn it back on. Fixed by a hack since 20190629, but expect a slight short blink when booting.
- No 48MP for camera. Kind of what you'd expect for these imx586 devices.
- This ROM doesn't come with its own vendor image yet. It needs to be flashed over OxygenOS to function properly. Comes with full vendor image since 20190629
- Importing keys to TEE does not work. Do not even try it, you may lose access to your data.
- SELinux is permissive.
How to flash
Use the TWRP recovery here https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
Since 20190629, you DO NOT need to flash OxygenOS before flashing this ROM anymore.
Note: this rom is only tested with firmware images from oxygen 9.5.5 for now. If you encounter any problem for things like mobile data, please try using firmware from 9.5.5 first.
This procedure is a bit tedious, but it's only because we are on an A/B system device.
1. Restart to bootloader, use `fastboot boot` to boot into the TWRP image
2. In TWRP, wipe data (better: format data)
3. Flash this LineageOS image (this installs it to the other slot)
4. Go to Reboot -> Bootloader (this will reboot to the other slot)
5. Again, use `fastboot boot` to boot into the TWRP image
6. Install OpenGAPPS / Magisk etc. (this installs to the current slot)
7. Reboot system
Downloads
20190706-1: https://mega.nz/#!LQxRhawQ!23i11FlIsO6LY35P1K3F1W0KRHGw8ozkUM66C3icdio
A lot of development has been going on this week due to luk1337, maintainer of official LineageOS for multiple devices, joining the party. Most of changes this week are either directly done by luk1337 or inspired by him.
- Corrected the calibration algorithm of the ambient light sensor. It works mostly fine now.
- Fixed support for in-display fingerprint sensor in Always-on Display mode.
- Fixed support for Wi-Fi Display
- Fixed LiveDisplay calibration / reading mode.
- Revamped the icon of in-display fingerprint scanner
- Fixed GNSS (GPS) support. Before this release, all the location information was network-based.
- Fixed NFC HCE.
- Added support for free-fall protection and manual-press warning for front-facing motorized camera.
- Fixed battery usage data.
History versions:
20190629-1: https://mega.nz/#!rRYRmIRY!4WW0FXYkWvu39t0LF-2RbRkl0aDfSbz_kjgZPotdLMQ
- Now comes with full vendor image, no need to flash OxygenOS vendor anymore.
- No more "internal problems" on boot anymore.
- Rebased the kernel
- Reduced screen blinking when fingerprint scanner is active (due to the rebased kernel)
- Hacked to make the screen work at 90Hz right after booting. No need to lock & unlock anymore (but expect a short blink while booting)
- Fixed double-tap-to-wake. Now the option in settings should be working.
- Fixed the position of fingerprint scanning circle when the screen is rotated.
- Tried to fix the ambient light sensor, but its behavior in an extremely low-light environment is still pretty funky. I hope maybe OnePlus can open-source their official algorithm to correct this thing...
20190624-1: https://mega.nz/#!nF4DwADT!xZ8tbrkCGtWL3A7DYIV_e6GfiprqGJXHEZLqufPCmmg
- Fixed crashes caused by playing audio
20190622-1: https://mega.nz/#!OMASTCZK!wXH7WdvVdAxqv7VjGzPwHy40Pk6cfghTGao-7u-PJQk
- Fixed bluetooth audio
- Added dash charging daemon
- Hacked to make the light sensor ( + auto brightness) at least work
20190621-1: https://mega.nz/#!rEglBKxS!OpA3tNSzlnpJ5pL8PW-x9Ax8Ee695GeIaDi4c-qcrw0
Stock Camera App
I have a modified version of the OxygenOS camera app here for use with LineageOS. It mostly works after a simple hack, however:
- No 48MP available. There must be some magic in official ROM on the frameworks side, and I doubt there is much to do about it
- Gallery integration does not work. Clicking on the gallery shortcut in camera will always say "no photos". You need to go to gallery app manually.
- Slow motion works but it will show a black screen when first started. Switching to another app and then back will fix it.
Remeber that I am not a professional camera modder at all. I have little knowledge in this field, and this is only a fallback solution given that nobody else has worked on modding the official camera of this device yet.
OnePlusCamera-guacamole-20190623: https://mega.nz/#!3YRWSKBR!lrRlslmenLXIBoUQQZnqydogKG4GZxmylX6rVHprHQs
Thanks
- LineageOS (obviously) and especially luk1337 (who maintains LOS for oneplus 6t also)
- OmniROM & phhusson (for their fingerprint scanner implementation as a basis, I cleaned it up a bit and abstracted device-specific logic from the somewhat messy frameworks implementation out to HAL. I think their original implementation for Xiaomi 9 / OnePlus 6T should have been done this way also.)
- All contributors to OnePlus 6T device tree of LOS & OmniROM (I took a good amount of code from there)
- HolyDragon guys (for their early work on the kernel)
- aviraxp
- Guaiyihu
XDA:DevDB Information
LineageOS for Oneplus 7 Pro, ROM for the OnePlus 7 Pro
Contributors
PeterCxy, ashwin4rc, holydragon
Source Code: https://github.com/PeterCxy/android_device_oneplus_guacamole
Kernel Code: https://github.com/PeterCxy/android_kernel_oneplus_sm8150
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2019-06-21
Last Updated 2019-06-21
Woohoo! Let the custom ROMs begin...
Let's begin the voyage.
+1 [emoji106]
Thank god for more rom development. I was starting to lose hope on this.
Thanks for this see piece of work.
My only question is atm why 9.5.5 if we have 9.5.8 already?
Thanks in advance #kudos
Gesendet von meinem GM1913 mit Tapatalk
Flashaholic said:
Thanks for this see piece of work.
My only question is atm why 9.5.5 if we have 9.5.8 already?
Thanks in advance #kudos
Gesendet von meinem GM1913 mit Tapatalk
Click to expand...
Click to collapse
+1
mcn1970 said:
+1
Click to expand...
Click to collapse
Flashed over 9.5.8 just fine. You will get vendor internal problem error tho
Any chance of it working on 1901 aka OnePlus 7? Should be working If the model check doesn't hardcode it to use on pro
Looks like on fps test I'm getting 90 although earlier I was getting 60 weird it bounces around like that lol also can't seem to get my Galaxy bids to connect or even get seen.
Edit. Also faceunlock seems to work pretty well also.
Flashaholic said:
Thanks for this see piece of work.
My only question is atm why 9.5.5 if we have 9.5.8 already?
Thanks in advance #kudos
Gesendet von meinem GM1913 mit Tapatalk
Click to expand...
Click to collapse
Simply because when I started it I didn't get 9.5.8. Didn't bother to update the blobs. But the rom should work ok on 9.5.8.
joemossjr said:
Looks like on fps test I'm getting 90 although earlier I was getting 60 weird it bounces around like that lol also can't seem to get my Galaxy bids to connect or even get seen.
Edit. Also faceunlock seems to work pretty well also.
Click to expand...
Click to collapse
Looks like there might be some problems with Bluetooth audio. Will look into it later.
PeterCxy said:
Looks like there might be some problems with Bluetooth audio. Will look into it later.
Click to expand...
Click to collapse
Also auto brightness seems to not work
Very nice! I hope in future build we might be able to choose between fhd+ and QHD resolution
Hopefully the Muppets repo will fork some, thanks for your work
Thanks for your work,I have already flash the img, and hope to find some bugs for you
How would it work if you don't have the EU version since 9.5.5 image is not the global version ?
xdamember143 said:
How would it work if you don't have the EU version since 9.5.5 image is not the global version ?
Click to expand...
Click to collapse
Use any one it doesn't matter
Nice to see here! Kudos
Running this baby
Only bugs
1. Bluetooth earphones won't connect to music but works with calls.
Really miss that 90ghz option, waiting for that to be added.
Hi Guys,
Some of you may remember me if you had a Galaxy S9 or Note 10... I rooted my Note 10+ 5G (N976B) Last night and decided to try and have a stab at getting stock android on there by means of project treble. This is a Semi Generic System Image - meaning it's been/being enhanced specifically for our note devices and less focused towards being cross compatible with other devices.
If you have already tested the existing treble roms you'll know that the back lighting doesn't work and you can't adjust brightness. I've had a play around and I've got a working Android 10 AOSP build with fully working backlighting. I thought I'd share as I'd seen a few people who said they can't get GSI's working.
Download System Image
Gapps are included, the image is not rooted. You can flash Magisk yourself.
How to flash:
Make sure you're on a stock based rom (and rooted/twrped) Dr Ketan posted a good guide for this.
Download the System Image above
Reboot to TWRP
Select Wipe
Slide the bar across the bottom of the screen
Go back to the main TWRP menu and select install
Press "Install Image" at the bottom right.
Select the system image you downloaded and swipe to flash.
Once the GSI boots perform another reboot - for some reason the navbar doesn't start up on first boot.
What's working and not working:
Obviously you lose S-Pen functionality, but can still use it as a stylus. You also lose the ability to use your telephoto and telescopic lenses.
UltraSonic Fingerprint isn't working at the moment, but I'm looking into fixing that.
How can you help me?
Let me know how it's working for the different device models. People on other versions please can you let me know your device vendor fingerprint. (to do this On your device, in adb or Termux app use this command: getprop ro.vendor.build.fingerprint)
Credits:
phhusson - for all the project treble work, this is all thanks to him.
Please please support N976n. ???
xshaowenruix said:
Please please support N976n.
Click to expand...
Click to collapse
It should work, it's semi generic. Give it a try and let me know if it works.
If it doesn't I'll need your device fingerprint.
Good work!
Nice ... you stared to work whit the N10+ , still remember havoc in my N9 was a great time , keep goin Fox
@CodeFox. Thank you so much for your work with this! I booted successfully into Android 10 which is awesome. Installing Magisk was successful as well. Do you have any plans to add mods to this?
Welcome aboard
carandcar said:
@CodeFox. Thank you so much for your work with this! I booted successfully into Android 10 which is awesome. Installing Magisk was successful as well. Do you have any plans to add mods to this?
Click to expand...
Click to collapse
Glad to hear it worked for you - can I ask what specific device you're using?
No mods to this really, but right now I'm compiling a AEX pie based sGSI which I'm hoping should have some more improved functionality and potentially the fingerprint sensor working. There's no reason to mod bog standard Android 10, may aswell just use custom roms.
CodeFox said:
Glad to hear it worked for you - can I ask what specific device you're using?
No mods to this really, but right now I'm compiling a AEX pie based sGSI which I'm hoping should have some more improved functionality and potentially the fingerprint sensor working. There's no reason to mod bog standard Android 10, may aswell just use custom roms.
Click to expand...
Click to collapse
I have N975f. I understand what you mean about keeping it pure. I just like to be able to change the look up. ? Thank you again for bringing this to us.
I managed to get fingerprint working
I seem to have gotten it working by doing a fresh reset, flashing this version of gapps (https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500), wiped cache/dalvik then rebooted. i dont know if it made a difference or not but i also held my thumb on the sensor for extra long during the initial set up. Did it on N975F
Jamjarr said:
I seem to have gotten it working by doing a fresh reset, flashing this version of gapps (https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500), wiped cache/dalvik then rebooted. i dont know if it made a difference or not but i also held my thumb on the sensor for extra long during the initial set up. Did it on N975F
Click to expand...
Click to collapse
Hmm, Interesting. I will look into it. Thank you.
Thanks (and a quick question)
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
saghm said:
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
Click to expand...
Click to collapse
Was there any trick to getting the fingerprint to work?? I've had no joy with it. As soon as I try to register my fingerprint it says there was an enrolment error.
Would this gsi theoretically also fix the s10's brightness issue too?
CodeFox said:
Was there any trick to getting the fingerprint to work?? I've had no joy with it. As soon as I try to register my fingerprint it says there was an enrolment error.
Click to expand...
Click to collapse
It did this to me too when I was first setting up the phone, but after it was all set up, I went into the settings to try again, and it worked that time. It didn't show the fingerprint logo during this setup (and it still doesn't on the lock screen), but after a couple tries I was able to estimate correctly where the sensor was. Interestingly, the fingerprint logo does come up in the password manager app I use when I go to unlock it.
Not sure if there are logs that would help or if recording my screen while adding a new fingerprint would be informative, but I'd be happy to do either if that helps you debug in some way.
saghm said:
Thanks for the rom! This works for me on an N975F, including the fingerprint sensor. The only slight nit I have with it is that I can't figure out how to get rid of the cursor showing up on the screen when I use the stylus. Is there any chance there's a way to hide the cursor, or if it can be added? I don't use any other external input devices ever, so I'd be fully satisfied with a way to just disable the cursor globally on my device.
Click to expand...
Click to collapse
DBDPCG said:
Would this gsi theoretically also fix the s10's brightness issue too?
Click to expand...
Click to collapse
What's the issue with the S10? The backlight doesn't work?
CodeFox said:
What's the issue with the S10? The backlight doesn't work?
Click to expand...
Click to collapse
As I've heard, haven't tried it yet though
DBDPCG said:
As I've heard, haven't tried it yet though
Click to expand...
Click to collapse
For what it's worth, all the other GSI's I've tried for the Note 10+ weren't able to adjust the backlight; this is the first one where it just worked. I don't have an S10 to try this out on though, so I have no idea how this ROM would run on it.
LTE working despite phone claiming 3G
One thing I've noticed with this ROM is that the phone claims that it's always only getting 3G rather than LTE and has no bars; however, from doing a speed test on data (with wifi turned off, of course), I got around 8.5 Mbps down, which from a quick Google seems to be will beyond 3G range and into the range that LTE would give. If anyone else thinks they are having issues with getting LTE, I suggest doing a speed test, since you might actually be getting it despite what the phone reports.
saghm said:
One thing I've noticed with this ROM is that the phone claims that it's always only getting 3G rather than LTE and has no bars; however, from doing a speed test on data (with wifi turned off, of course), I got around 8.5 Mbps down, which from a quick Google seems to be will beyond 3G range and into the range that LTE would give. If anyone else thinks they are having issues with getting LTE, I suggest doing a speed test, since you might actually be getting it despite what the phone reports.
Click to expand...
Click to collapse
Go into your network settings and change the default connection from 3g to LTE/4G/3G.
For some reason it seems to default to 3g preferred.
Android 10
Release date: Tuesday, May 26th, 2020
Build Version: QKQ1.191002.002.V11.0.5.0.QDLMIXM
Kernel Version: 3.18.124-perf-g6d04eb4a
#1 Mon May 18 22:15:26 WIB 2020
Bootloader Version: MSM8953_DAISY2.0_20200518220803
Baseband Version: 953_GEN_PACK-1.202044.1.240106.1,953_GEN_PACK-1.202044.1.240106.1
Android Security Patch Version: May 2020
Please report bugs via Xiaomi's Feedback app.
How to Generate Bug Reports
Bugs:
1- [email protected] fps Video Recorder doesnt work on OmniVision OV12A10 Camera sensor. (Tap here for more info)
2- Still no way to discard Setting app suggestions.
3- Screen Lock/Unlock sounds doesnt work. (Factory reset fixes it)
4- Sim settings does not respect system theme. (only white) Source
5- Old charging sound still persist. (Factory reset fixes it)
6- Customize your Pixel still there. (Factory reset removes it)
7- Wifi icon on the statusbar is flickering. (Still same after factory reset)
8- Sometimes Wifi and Cellular icons on the statusbar is turning black while others white.
9- Direct share is broken. Source (Same after factory reset)
10- Some options in the Network settings are not translated correctly. Source
11- Volte still does not work (despite activation in options, the phone during the call switches to 3G network and does not display the volte icon) Source
12- 4G speeds slightly slower then Android 9 Source
Missing features:
1- There is no Equalizer.
Enhancements:
1- Second Stable Android 10 release.
2- It comes with May 2020 Android Security patch.
3- Sim card disabling option is fixed. Source
4- Camera sound deactivation works now. Source
5- Fixed! Uninstalling an huge app&game freezes the whole phone for a while. Source - Still same
Battery Life:
- One Sim,
- 2G only,
- Mobile Data off,
- Wifi,
- Brightness Auto,
- Battery Saver enabled at %10
- Adaptive Battery disabled
It gived 12 hours SOT. Check the SS's. Pretty much same as v11.0.4
Notes:
This is the second stable Android 10 update for Xiaomi Mi A2 Lite. There was a March 2020 Security patch in the first stable Android 10 update. Arrived 42 days later after v11.0.4
3DMark Test Results: (v2.0.4661)
Slingshot Extreme OpenGL ES 3.1 - Overall score 465
Slingshot Extreme Vulkan - Overall score 516
It will be beneficial to restart your phone after the first installation.
If you want to improve the performance of your phone tap here.
I will constantly update this topic.
perfect_ said:
Android 10
Release date: Tuesday, May 26th, 2020
Build Version: QKQ1.191002.002.V11.0.5.0.QDLMIXM
Kernel Version: 3.18.124-perf-g6d04eb4a
#1 Mon May 18 22:15:26 WIB 2020
Bootloader Version: MSM8953_DAISY2.0_20200518220803
Baseband Version: 953_GEN_PACK-1.202044.1.240106.1,953_GEN_PACK-1.202044.1.240106.1
Android Security Patch Version: May 2020
Please report bugs via Xiaomi's Feedback app.
How to Generate Bug Reports
Bugs:
1- [email protected] fps Video Recorder doesnt work on OmniVision OV12A10 Camera sensor.
2- Still no way to discard Setting app suggestions.
Missing features:
1- There is no Equalizer.
Enhancements:
1- Second Stable Android 10 release.
2- It comes with May 2020 Android Security patch.
3- Sim card disabling option is fixed. Source
4- Camera sound deactivation works now. Source
Battery Life:
N/A
Notes:
This is the second stable Android 10 update for Xiaomi Mi A2 Lite. There was a March 2020 Security patch in the first stable Android 10 update. Arrived 42 days later after v11.0.4
It will be beneficial to restart your phone after the first installation.
I will constantly update this topic.
Click to expand...
Click to collapse
Is third party launcher supported now?
Using gesture screen options.
gusbalaa said:
Is third party launcher supported now?
Using gesture screen options.
Click to expand...
Click to collapse
No.
-Facebook applications can't record video (Video capture fail error)
-------Found problem--------
The only system wide equalizer system that still works (the one explained here) on our device is causing the problem related to recording video in Facebook/Facebook Messenger/Instagram. Force closing the app now enables the video recording and as soon as the app is restarted the problem occurs again. And that's weird because the DSP isn't supposed to mess up the microphone or whatever facebook finds faulty and cancels the recording... Weird... Will look this up and update if solution is found.
Going back to the PRO version of that app now totally ignores the volume control of the device, which means in this .5 built the audio paths were modified. With pro version video recording is still failing. This is not a fix from xiaomi, this is an internal workaround, which is bad!!!
Even clearing the system, problem still persists. Checked permissions, checked storage writing, all is working, except video recording.
--------End of edit--------
-Sim settings does not respect system theme (only white)
--------Lazy modding from Xiaomi, this is the same dual sim controller app you had in Android Pie, just thrown in the Q environment--------
-Refreshing external device problem still persistent, new data copied on to the device only visible after reboot.
--------Not the only one with this problem, this is basically related to having huge folders on your SD card. I have a folder with >15k files in it)--------
-Sometimes some large games force close, but are fine after restarting the app (only sometimes - Only applicable on Gameloft ones - Totally unimportant)
What was fixed:
-Video record sound can now work with Google Voice turned on
-Ram management works fine for me (4/64)
??? Questionable effects:
-Lock screen sounds work for me (testing after a reset, still working just fine)
-Charging/USB sounds seems too low for me (problem persists, the vibration of the device is actually covering the sound)
Other than this, everything else remained the same as per what I wrote in my previous replies.
Qualcomm's app for data collection is still there, so this may be another partial release. They fixed something but the broke something else in another place.
Another lazy update, the battery is draining much faster than on .4 version, waiting for calibration. I'm starting to get sick over their incompetence to test and deliver a good end user experience.
OTA Link: https://bigota.d.miui.com/V11.0.5.0.QDLMIXM/miui_DAISYGlobal_V11.0.5.0.QDLMIXM_4e152f6600_10.0.zip
Let's not conclude quickly that the memory leak has benn fixed. I am trying to trigger it.
edit:
The device did not wake up from sleep, I got a random reboot.
magisk works as it should.
I install the update OTA this morning from official pie, the phone work well, the phone signal is a bit weak but all works well. No gesture in smart Launcher 5, i have fluid gesture for this feature.
Inviato dal mio Mi A2 Lite utilizzando Tapatalk
TeoXSD said:
-Facebook applications can't record video (Video capture fail error)
-Sim settings does not respect system theme (only white)
-Refreshing external device problem still persistent, new data copied on to the device only visible after reboot.
Click to expand...
Click to collapse
- Facebook and Messenger works fine with Camera.
- Sim settings same (only white)
- I am using Cx File manager works fine
Screen Lock/Unlock sounds work fine for me!
key-ancel said:
Screen Lock/Unlock sounds work fine for me!
Click to expand...
Click to collapse
Mine doesnt work.
perfect_ said:
Mine doesnt work.
Click to expand...
Click to collapse
Mine doesn't work too.
It began after upgrading to Q.
Also did two reset through settings, but nothing changed, still missing.
Have you maybe tried to flash fastboot image ?
srepole said:
Mine doesn't work too.
It began after upgrading to Q.
Also did two reset through settings, but nothing changed, still missing.
Have you maybe tried to flash fastboot image ?
Click to expand...
Click to collapse
I upgraded through ota from 10.0.18 to 11.0.4 and then i did Factory reset;
- New Charging sound was gone
- Lockscreen sounds doesnt work neither v11.0.4 nor v11.0.5
Anyone else getting super slow charging with this update? This is my first attempt to upgrade from Pie, and I've gone from 23% to 25% in almost an hour on standby...
- Direct share is still not available.
Please what do i do?
My phone is stuck with boot loop after upgrade to android 10.
how can i downgrade?
hi all!
face unlock function is gone completely, but after poking around I found that is the 'feature' and requirement of android 10 due to google's security concerns. ok...
but the problem I am facing is of a different nature. After update, I did factory reset but did not remove fingerprints prior to that operation. Now fingerprint enrolment fails every time I attempt to add another fingerprint. I was doing some digging around before posting this, and I already did try some of the solutions suggested for some other models which I have found scattered across XDA / so I already did boot twrp and erased via twrp file manager some of the files in /persist/data but that did not help.
any suggestions that could help, please?! thank you!
also, did anyone find a way to get rid of CUSTOMIZE PIXEL message?
Matty Watty said:
also, did anyone find a way to get rid of CUSTOMIZE PIXEL message?
Click to expand...
Click to collapse
Yes: -
1. Sell Mi A2 Lite
2. Buy a Pixel
Seems bizarre that the Pixel would not force this message on you and the Android One phone would but at the point this phone is exactly that, just a bizarre curiosity. Bye bye Xiaomi.
Matty Watty said:
also, did anyone find a way to get rid of CUSTOMIZE PIXEL message?
Click to expand...
Click to collapse
You've got to hand-exit the XML file in the settings suggestion data folder. You'll need root. Or you could boot (not install) TWRP and edit from there.
If your bootloader is locked, there doesn't seem to be any way to stop it. You can clear data on settings suggestions but the suggestions will come back and can't be dismissed.
a1291762 said:
You've got to hand-exit the XML file in the settings suggestion data folder. You'll need root. Or you could boot (not install) TWRP and edit from there.
If your bootloader is locked, there doesn't seem to be any way to stop it. You can clear data on settings suggestions but the suggestions will come back and can't be dismissed.
Click to expand...
Click to collapse
thanks. my boot loader is unlocked so I can boot easily into twrp. But I am not sure what do you mean with hand-exit and which exactly folder that xml file is in? thanks again.
Matty Watty said:
thanks. my boot loader is unlocked so I can boot easily into twrp. But I am not sure what do you mean with hand-exit and which exactly folder that xml file is in? thanks again.
Click to expand...
Click to collapse
From here...
https://support.google.com/android/thread/24667791?hl=en
This happened to me after upgrading a Xiaomi Mi A2 to Android 10 from Android 9.
Might be related to the "/data/data/com.android.settings.intelligence/shared_prefs/suggestions.xml" file not updating some values properly, since some users with rooted systems have changed manually this values to "true":
<boolean name="com.google.android.gm/com.google.android.gm.setup.AccountSetupFinalGmailSuggestions_is_dismissed" value="true" />
<boolean name="com.android.settings/com.android.settings.notification.ZenSuggestionActivity_is_dismissed" value="true" />
And the suggestions don't appear to them anymore.
I had to do this a few times, as new things popped up.
Hi!
I have installed Resurrection Remix 8.6.4 GSI on my SM-T590.
After a few hours of testing, seems like all the functions I need are working except one, the automatic brightness setting. The sensor (CM3323E) is detected in sensor testing apps, also they can read the light value. Automatic brightness icon shows up next to the brightness slider, but it doesn't do anything, no new logcat messages are produced when I tap the icon.
Also, I have issues with WiFi and Bluetooth quick setting toggles. If the status bar icon shape is set to circular, and I tap one of them, SystemUI crashes because of a Resources$NotFound exception. I think this isn't related to the brightness sensor, more like a ROM bug, but who knows.
Where should I start debugging? I'm relatively new to Android development.
UDPSendToFailed said:
Hi!
I have installed Resurrection Remix 8.6.4 GSI on my SM-T590.
After a few hours of testing, seems like all the functions I need are working except one, the automatic brightness setting. The sensor (CM3323E) is detected in sensor testing apps, also they can read the light value. Automatic brightness icon shows up next to the brightness slider, but it doesn't do anything, no new logcat messages are produced when I tap the icon.
Also, I have issues with WiFi and Bluetooth quick setting toggles. If the status bar icon shape is set to circular, and I tap one of them, SystemUI crashes because of a Resources$NotFound exception. I think this isn't related to the brightness sensor, more like a ROM bug, but who knows.
Where should I start debugging? I'm relatively new to Android development.
Click to expand...
Click to collapse
How dit u get gsi's to work on the sm-t590?
Tab a 10.5 right?
Mikxx said:
How dit u get gsi's to work on the sm-t590?
Tab a 10.5 right?
Click to expand...
Click to collapse
Yea, I have Tab A 10.5 (2018), SM-T590.
Basically I installed TWRP from here: [RECOVERY][ROM][ROOT][UNOFFICAL] TWRP 3.3.1-0 + Lineage [SM-T590/SM-T595/SM-T597] | XDA Developers Forums (xda-developers.com)
Then I just downloaded some GSIs and flashed them to see which one works, with some changes to the original post. I may create an updated guide for installing GSI ROMs using MrHomebrew's TWRP without having to mess with SD cards, etc, but you can follow the original guide to have a mostly working system.
You can download ROMs from here: Generic System Image (GSI) list · phhusson/treble_experimentations Wiki · GitHub
I'm still not sure about how that A-only / AB thing works, if you have updated to Android 10 on stock system, AB ROMs with A64 binder will run.