Related
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.
So, I know this title seems odd; I changed the resolution of my Phone with ADB to maybe get a 18:9 screen ratio but with more sharp edges since I really dislike how the 7 Pro has such round edges that just look terrible in some app's overlay, bc they weren't built for that in mind.
however, I found out that that won't help me with my problem. I thought the Screen Corners were just a hardware thing, but it turns out its actually on software as well. Does someone know how to potentially remove these? (it will probably not have these software added notches in custom roms, but i'd prefer using the default/openbeta rom from oneplus directly)
try this. the instructions are for a google pixel 3, but hopefully those settings exist for the oneplus.
disable rounded screen corners on pixel 3
altwu said:
try this. the instructions are for a google pixel 3, but hopefully those settings exist for the oneplus.
disable rounded screen corners on pixel 3
Click to expand...
Click to collapse
thanks for the answer, it doesnt work like that for the oneplus 7 pro, but i will look into stuff like this and reply again if i found out how to do it <3
Not sure what you expect to accomplish. The rounded corners are the physical edge of the display. You can see this in TWRP or any non-black boot animation.
Dungeon47 said:
Not sure what you expect to accomplish. The rounded corners are the physical edge of the display. You can see this in TWRP or any non-black boot animation.
Click to expand...
Click to collapse
as i said i wanted to reduce the vertical size of the screen and disable the software rounded corners. i only found out that there are software edges BECAUSE i changed the resolution of the display via adb.
Hello, are you talking about this broken corners thing ? Because whenever I install a custom ROM, the corners are very pixelated, which doesn't happen in Oxygen OS. Also, still concerning OOS, I tried to modify the overlay with the adb overscan thing and I was able see the rounded overlay moving, so it's definitely related to the software.
Also I managed to get a picture of the same problem on a OnePlus 6T. You can clearly see the pixelated corners.
I truly hate how there isnt an option for this. You can use "adb settings put secure sysui_rounded_size X" on Android 9, but not on Android 10. There doesnt seem to be a way to do it. I've used a Substratum theme (Curve) to temporarily (for a second) disable the rounded corner overlay but it doesnt stick, and there is nothing I've found over 3 days of intense searching for hours and hours. Custom ROMS have the option (Havoc 3.1 has a rounded-corner radius slider setting but changing it has no effect, even after rebooting).
Please tell me there is something someone has come up with. Its so annoying to have an ugly af rounded corner. I am using adb to reduce the display height to create a "software bezel" and want to reduce the rounded corner radius so it looks much less rounded. I can do it on Android 9, but the nav bar doesnt work well on it, and much prefer Android 10.
To ellaborate, the "adb settings put secure sysui_rounded_size X" setting DOES work properly on OOS, but not on anything beyond Android 9. You likely wont notice on Android 9 unless you set the display height smaller than what stock is. "adb shell wm size 1440x2990" is the best size I can say that fits well with sysui_rounded_size of 25 or 30.
Is there an update to this?
have anyone solved the prob?
I know you said something about wanting to be on OOS, but I've found a setting on Resurrection Remix that allows you to change the size of the rounded corners.
I got back on this topic today.
I got it working by using apktool on the ODMOverlay-OPSystemUI.apk and removing the pathData from rounded_bottom.xml and rounded_top.xml. then used rootbrowser to overwrite the original. I assume this could be done using a magisk module, but i couldn't get it to work properly.
Ixaruz said:
.... I got it working by using apktool on the ODMOverlay-OPSystemUI.apk and.... I assume this could be done using a magisk module, but i couldn't get it to work properly.
Click to expand...
Click to collapse
That app seems specific to OnePlus devices. Have you had any success with making a Magisk module yet? And, could that work on other devices also? My device is Poco X3 Karna running AICP (Android 12.1) rom. I am very much interested in this; I prefer 'rectangular' screenshots. Please reply. Thanks.
Hello,
I have tested multiple Custom ROM's and I feel like the Pixel Experience ROM is the best Performing + Looking and Battery Life extending one.
But there is one Problem: The Hardware Navigation Keys aren't supported. (Home, Back, Recent Apps)
I would like to know if there is any modified Pixel Experience ROM, which has the Navigation Keys supported.
I imagine it can't be that difficult if the Fingerprint Sensor (inside the Home Button) is already supported.
I've searched about 2 hours and didn't find any useful information.
Thanks in Advance.
luigicon said:
Hello,
I have tested multiple Custom ROM's and I feel like the Pixel Experience ROM is the best Performing + Looking and Battery Life extending one.
But there is one Problem: The Hardware Navigation Keys aren't supported. (Home, Back, Recent Apps)
I would like to know if there is any modified Pixel Experience ROM, which has the Navigation Keys supported.
I imagine it can't be that difficult if the Fingerprint Sensor (inside the Home Button) is already supported.
I've searched about 2 hours and didn't find any useful information.
Thanks in Advance.
Click to expand...
Click to collapse
AFAIK you have to flash another custom rom with physical navigation button support. I guess it has something to do with the Android version on which the rom is based on, as Google has changed navigation in its OS.
Hey, I just tried out several Q and 11 based custom roms with my SGP771.
Most of them have problems with the BKB50's navigation keys, they are not working at all under some roms.
I managed to reassign the nav bar drop-down key with key mapper's help, but nav keys seem to be dead under pixel experience 10 plus edition e.g.
Furthermore none of the roms I checked supports multitouching the trackpad.
Does anyone has a fix for this? I really would like to go on using this keyboard together with android Q or 11 and move on from ancient stock rom.
I checked AICP, Pixel Experience and Lineage of course.
Device is Redmi Note 9 Pro (joyeuse).
Have been using MIUI on Android 10 for some time after buying device.
After unlocking bootloader have flashed Android 11 ROM - CrDroid. There has been several ROMs before that.
Flashed MIUI on Android 11 by xiaomi.eu team. Started bootlooping.
Flashed CrDroid again. Newest version now - 7.12.
Noticed the lack of vibration. Tried different versions of MIUI (official and not). None of them were working for different reasons: bootloops, stuck on loading animation, or bootloop even before the loading animation.
Flashed newer recovery. Now vibration is gone for recovery as well. Can't remember if there were vibration in bootloader.
Started flashing official MIUI ROMs with Fastboot instead of recovery. None of them loading correctly. Can't confirm they have installed as they were supposed. Loading animations are different for different versions. But each one is stuck on that animation or just bootlooping in bootloader, before that animation.
In the same time, any other custom ROM is working just perfect, with no vibration. Any other hardware is working.
Flashed the very first official MIUI ROM - 11.0.1. Then cleared several partitions and flashed this ROM again. Suddenly, vibration appeared. But MIUI still wasn't loading.
Flashed newer rom on Android 10 - 11.0.3. It was working. Vibration kept working everywhere.
Flashed usual CrDroid. It was working, vibration as well. Flashed GAPPS - vibration gone again.
Tried step 9 - no success. Tried same ROMs and actions in different ways and combinations. No vibration, MIUI ROMs not working.
Tried different ways of flashing ROMs in fastboot: .bat files for CMD in Windows and MiFlash. Same ROM with MiFlash results in infinite loading screen, while .bat file bootlooping in bootloader, before the loading animation. None of these ways are showing any error or mistakes.
I can still use any custom ROM. But i want vibration working, and there may be some mistake in the future that will be resulted by the strange System condition.
Device supports Project Treble. My best quess is, that some partition is not being rewritten by any of my actions. Where are the files in the system, that are meant to make vibration working? Vendor and VBMeta? What files do i need to flash there? VBMeta has two files in the ROM's zip file, but i am note sure about what files are for Vendor.
Presumably, i have screwed it up with OrangeFox recovery, which has settings like "Unmount Vendor/System before installing zip file".
Problem solved. There are three metal gaskets on camera module. One of them is shifted left or right, causing loopback on circuit. The one in bottom side.
Disassemble device; cut it, glue it or just take it out of there; glue back the lid.
That will solve the problem of any MIUI not loading and different hardware errors (vibro in my case, may be different though).
This video is in russian, but the guy just show the cause and it's location in short, 1.5 minute video.
Andthenagain said:
Problem solved. There are three metal gaskets on camera module. One of them is shifted left or right, causing loopback on circuit. The one in bottom side.
Disassemble device; cut it, glue it or just take it out of there; glue back the lid.
That will solve the problem of any MIUI not loading and different hardware errors (vibro in my case, may be different though).
This video is in russian, but the guy just show the cause and it's location in short, 1.5 minute video.
Click to expand...
Click to collapse
I am also facing the same problem. Custom Rom is just working fine without Vibration. I tried to flash stock rom via fastboot mode but bootloop.
Andthenagain said:
Problem solved. There are three metal gaskets on camera module. One of them is shifted left or right, causing loopback on circuit. The one in bottom side.
Disassemble device; cut it, glue it or just take it out of there; glue back the lid.
That will solve the problem of any MIUI not loading and different hardware errors (vibro in my case, may be different though).
This video is in russian, but the guy just show the cause and it's location in short, 1.5 minute video.
Click to expand...
Click to collapse
Please give me the video link that solved your problem.
You should disassemble the device. Back lid can he heated, that is where the glue will melt and soften. There are videos on disassembly of this phone. Just be careful, as back lid is made of glass and it may shatter if you will act too fast and with force. That is why i recommend any phone repair. They have tools, they are experienced and they will not look for the problem if you will tell what is the problem is. All operation takes about 10 minutes total.
BUT, FIRST!!!!! You should be sure that this is the problem:
1. You can install MIUI, but it is not loading. Other ROMs may work just fine.
2. In my case there was a problem with vibration. It was not working in recovery, rom itself. Everywhere.
3. Pressing area under the camera could help the situation for a short time. Or gentle knocking that place. It is the most precise indicator, that you have the same issue i had. Just like many other people.
4. In other ROMs some hardware not responding well. I have forgotten the code, but it was the vibration and some other thing, i believe.
Solving the issue:
1. Disassemble the phone to you can take off main 4 camera module.
2. You will see some metallic element on the camera module. In the lower part. If it is shifted, then is was the problem you have been looking for. On the photo you can see silver thing is shifted. That is the problem.View attachment 5575933
3. Now, there are 3 options:
a. Take it off. Not recommended, as that element presumably working with static electricity. Just some kind of failsafe. Don't know for sure.
b. Cut it, so even shifted, it will not touch CMD elements near it. I did that, and it helped. It had it own, weak glue, but it could easily keep that thing in place after i cut it, and used only one half.
c. Glue it normally. But the glue should not prevent flowing power through that metallic element. And heat resistance would be great. As well as not causing problem even after accidentally touching other elements.
There is a video, in russian. Auto translation of subtitles into english works about well. It helped me fix my phone. It is very short, and showing nothing but the source of the problem. It will help for sure.
Hello friends
, please post the video link to solve the problem of the Redmi Note 9 Pro vibration,
thank you