Just upgraded from a Mi 9 Lite (and before that Redmi Note 5 Pro) to a Poco X3.
I am finding the vibration strength extremely weak, maybe 30% the strength of the previous phones. It is so weak that I do not notice it in my jeans pocket.
Anyone else having this problem? Thanks.
For me, it's actually quite the opposite. I was looking for ways to decrease the overall vibration intensity. There's an options menu in accessibility called "Vibration & haptic strength" but it only provides the option to turn vibrations off, not decrease nor increase its intensity.
I browsed around a bit trying to find a possible solution and it seems to have to do more with the kernel than anything for most phones. Not sure if there are any root solutions, but I couldn't really find anything immediately available. Hopefully someone else will have more insight to share on this topic than me.
Warrimonk said:
Just upgraded from a Mi 9 Lite (and before that Redmi Note 5 Pro) to a Poco X3.
I am finding the vibration strength extremely weak, maybe 30% the strength of the previous phones. It is so weak that I do not notice it in my jeans pocket.
Anyone else having this problem? Thanks.
Click to expand...
Click to collapse
I don't have this problem, but that's a personal preference. You have two solutions to your problem (kinda?):
1- You don't feel adventurous enough and wait for a custom kernel (when and if device sources are released) or i.e a custom ROM with this option.
2- You feel very adventurous and don't mind reflashing if something goes wrong, in that case, you can try editing vendor props with some experimenting. I have made a guide on how to edit props with magisk props config.
Regarding the editable props, I have pulled these from MIUI stock that are related to haptic feedback:
Code:
sys.haptic.motor=linear
sys.haptic.down.weak=0
sys.haptic.down.normal=2
sys.haptic.down.strong=5
sys.haptic.down=5,2
sys.haptic.tap.normal=3,2
sys.haptic.tap.light=5,2
sys.haptic.flick=5,2
sys.haptic.flick.light=5,2
sys.haptic.switch=9,2
sys.haptic.mesh.heavy=8,2
sys.haptic.mesh.normal=8,2
sys.haptic.mesh.light=8,1
sys.haptic.long.press=0,1
sys.haptic.popup.normal=6,2
sys.haptic.popup.light=6,1
sys.haptic.pickup=0,2
sys.haptic.scroll.edge=5,0
sys.haptic.trigger.drawer=2,0
sys.haptic.hold=6,0
sys.haptic.runin=13
You will have to figure out yourself what the parameters are, which does what and what works or not. Good luck
Slim K said:
I don't have this problem, but that's a personal preference. You have two solutions to your problem (kinda?):
1- You don't feel adventurous enough and wait for a custom kernel (when and if device sources are released) or i.e a custom ROM with this option.
2- You feel very adventurous and don't mind reflashing if something goes wrong, in that case, you can try editing vendor props with some experimenting. I have made a guide on how to edit props with magisk props config.
Regarding the editable props, I have pulled these from MIUI stock that are related to haptic feedback:
Code:
sys.haptic.motor=linear
sys.haptic.down.weak=0
sys.haptic.down.normal=2
sys.haptic.down.strong=5
sys.haptic.down=5,2
sys.haptic.tap.normal=3,2
sys.haptic.tap.light=5,2
sys.haptic.flick=5,2
sys.haptic.flick.light=5,2
sys.haptic.switch=9,2
sys.haptic.mesh.heavy=8,2
sys.haptic.mesh.normal=8,2
sys.haptic.mesh.light=8,1
sys.haptic.long.press=0,1
sys.haptic.popup.normal=6,2
sys.haptic.popup.light=6,1
sys.haptic.pickup=0,2
sys.haptic.scroll.edge=5,0
sys.haptic.trigger.drawer=2,0
sys.haptic.hold=6,0
sys.haptic.runin=13
You will have to figure out yourself what the parameters are, which does what and what works or not. Good luck
Click to expand...
Click to collapse
Thanks, I am aware that there are rooted solutions to this, unfortunately I am in the position where I cannot root or bootloader unlock the phone. Hopefully MIUI 13 will introduce vibration adjustment and solve the issue.
Slim K said:
I don't have this problem, but that's a personal preference. You have two solutions to your problem (kinda?):
1- You don't feel adventurous enough and wait for a custom kernel (when and if device sources are released) or i.e a custom ROM with this option.
2- You feel very adventurous and don't mind reflashing if something goes wrong, in that case, you can try editing vendor props with some experimenting. I have made a guide on how to edit props with magisk props config.
Regarding the editable props, I have pulled these from MIUI stock that are related to haptic feedback:
Code:
sys.haptic.motor=linear
sys.haptic.down.weak=0
sys.haptic.down.normal=2
sys.haptic.down.strong=5
sys.haptic.down=5,2
sys.haptic.tap.normal=3,2
sys.haptic.tap.light=5,2
sys.haptic.flick=5,2
sys.haptic.flick.light=5,2
sys.haptic.switch=9,2
sys.haptic.mesh.heavy=8,2
sys.haptic.mesh.normal=8,2
sys.haptic.mesh.light=8,1
sys.haptic.long.press=0,1
sys.haptic.popup.normal=6,2
sys.haptic.popup.light=6,1
sys.haptic.pickup=0,2
sys.haptic.scroll.edge=5,0
sys.haptic.trigger.drawer=2,0
sys.haptic.hold=6,0
sys.haptic.runin=13
You will have to figure out yourself what the parameters are, which does what and what works or not. Good luck
Click to expand...
Click to collapse
Hello, I faced the same problem with Mi10Tpro device - when updating from MIUI 12.0.1 to 12.5.2 the haptic feedback has become weak and less distinct. What I would like to do is to pull prop values from 12.0.1 and add them to 12.5.2 Could you please share the way of pulling current values? Thank you very much in advance.
Just upgraded from Redmi note 7 to Poco x4 pro 5g, vibration is hardly noticeable. Have tried all settings but believe it's a bug. Xiaomi needs to fix this urgently. Anybody know their support email?
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:
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.
I just flashed the new Android 11 beta on my Pixel 4 to just check out what's new and thought we could have a little discussion about some of the bigger changes and opinions. The changes I immediately am excited about are:
1) Finally added a pause/play gesture to project Soli!! (Works fantastic)
2) In the display settings, there is now a toggle to increase display touch sensitivity for screen protectors
3) Added a new qs icon for the built in screen recording
While testing the new Soli pause/play, I also immediately noticed how much more improved all of the hand gestures are. Not just the new pause, but also the skipping forward and backwards are so much more accurate and successful for me. It's an extremely welcome change and while Soli always worked decent for me, on the 11 beta I'm getting about 95%-99% success on all hand gestures compared to my about 80% on Android 10.
The screen sensitivity is another welcome addition for me personally. I have a glass screen protector and with the new option enabled, I can absolutely feel a difference in display response. I will admit that before updating, I hadn't had any screen responsiveness complaints but now that there's an option to improve it, I am very pleased with the results. If anything, it may be a tiny bit too responsive. While typing this post out, Gboard seems to occasionally hit a letter before I actually make contact with the screen. Other than that, it's fantastic. My back gestures seem to be the most beneficial from this.
The screen recording qs icon is a cool new addition, although I had native screen recording enabled on Android 10, there was no super quick way to start a recording session.
Lastly, I noticed a few new things in developer options but as I'm no Dev, I really don't know what they do. Oh, they did add a screen frame-rate overlay so you can see the current refresh rate of your screen.
I will be running this for a few days to see if and how battery life is affected and I'll post my findings here. Feel free to comment additional findings or opinions on the new Android 11 beta!
Here are some screenshots of my findings so far.
1dopewrx05 said:
I just flashed the new Android 11 beta on my Pixel 4 to just check out what's new and thought we could have a little discussion about some of the bigger changes and opinions. The changes I immediately am excited about are:
1) Finally added a pause/play gesture to project Soli!! (Works fantastic)
2) In the display settings, there is now a toggle to increase display touch sensitivity for screen protectors
3) Added a new qs icon for the built in screen recording
While testing the new Soli pause/play, I also immediately noticed how much more improved all of the hand gestures are. Not just the new pause, but also the skipping forward and backwards are so much more accurate and successful for me. It's an extremely welcome change and while Soli always worked decent for me, on the 11 beta I'm getting about 95%-99% success on all hand gestures compared to my about 80% on Android 10.
The screen sensitivity is another welcome addition for me personally. I have a glass screen protector and with the new option enabled, I can absolutely feel a difference in display response. I will admit that before updating, I hadn't had any screen responsiveness complaints but now that there's an option to improve it, I am very pleased with the results. If anything, it may be a tiny bit too responsive. While typing this post out, Gboard seems to occasionally hit a letter before I actually make contact with the screen. Other than that, it's fantastic. My back gestures seem to be the most beneficial from this.
The screen recording qs icon is a cool new addition, although I had native screen recording enabled on Android 10, there was no super quick way to start a recording session.
Lastly, I noticed a few new things in developer options but as I'm no Dev, I really don't know what they do. Oh, they did add a screen frame-rate overlay so you can see the current refresh rate of your screen.
I will be running this for a few days to see if and how battery life is affected and I'll post my findings here. Feel free to comment additional findings or opinions on the new Android 11 beta!
Click to expand...
Click to collapse
Were you able to complete the face unlock enrollment?
dave5777 said:
Were you able to complete the face unlock enrollment?
Click to expand...
Click to collapse
Yes it didn't give me a single issue. Are you not able to?
1dopewrx05 said:
Yes it didn't give me a single issue. Are you not able to?
Click to expand...
Click to collapse
Nope, not able to
Ashray_Vk said:
Nope, not able to
Click to expand...
Click to collapse
Strange, I haven't heard of this being an issue for anyone else yet. I even dirty flashed the 11 beta, didn't erase my userdata so I was expecting issues and it's been flawless. Try re-flashing the Android 11 factory image, that we almost certainly fix your issue.
1dopewrx05 said:
Strange, I haven't heard of this being an issue for anyone else yet. I even dirty flashed the 11 beta, didn't erase my userdata so I was expecting issues and it's been flawless. Try re-flashing the Android 11 factory image, that we almost certainly fix your issue.
Click to expand...
Click to collapse
It's a fresh installation with all data wipe . Strange. Maybe I should try the OTA method.
Ashray_Vk said:
Nope, not able to
Click to expand...
Click to collapse
I have the same problem. And there are more people with this.
Is there HDMI out support on Android 11?
1dopewrx05 said:
Yes it didn't give me a single issue. Are you not able to?
Click to expand...
Click to collapse
No luck, I'll probably go back to rooted stock 10. I can't use the phone without root and Fingerface.
Once we get root for this then i will try it out
Does it break Google Pay?
dave5777 said:
Were you able to complete the face unlock enrollment?
Click to expand...
Click to collapse
Face unlock working fine here too, only issue I had was I didn't extract the zip into its entirety of the platform tools folder. That took me 2 hours to figure out how to flash without error.
Luxferro said:
Does it break Google Pay?
Click to expand...
Click to collapse
Yeah, Google pay does not work on it. I received a pop up about it earlier this morning.
For those having face unlock setup issues: Factory reset your phone either in recovery or the settings menu. This happens when you don't clear face unlock before flashing a factory image with the -w option.
(Also, finally hitting my 1000th post with this 10 years later... Can't believe it's been that long)
AwkwardUberHero said:
Yeah, Google pay does not work on it. I received a pop up about it earlier this morning.
Click to expand...
Click to collapse
Hmm. Was afraid to read that. So if we are able to use Google pay we have to wait until Google ads the preview to safely net to pass i think... So i wait... G-Pay is evident to me.
Joolz03 said:
Is there HDMI out support on Android 11?
Click to expand...
Click to collapse
Nope, unfortunately the Pixel line will most likely never have hardware HDMI out capability due to the Chromecast's existence. I have a Chromecast and still would love to have HDMI over usb-c, it's just not going to happen.
How's this running for everyone? Phone and messaging work no issues?
the.emilio said:
How's this running for everyone? Phone and messaging work no issues?
Click to expand...
Click to collapse
Running good for me. Only thing I see is Google assistant won't use the new assistant keeps reverting to old.
Installed on my carrier locked TMO phone no issues. Working great so far.
Hey guys!
I'm currently on ArrowOS 07.09 build with firmware 12.5.1. In the last 2 weeks I got ghost touch issues quite frequent. The phone starts to recognize touches crazy fast without me touching it and doing random things. I have to lock the phone with the power button to make it stop.
Does anyone else have or had the same issue? Is it a hw or sw related issue in your opinion? Any tips, ideas, working methods are welcome to make it stop.
Thank you!
It's mostly a SW issue , but it can also be a hardware issue(extremely rare),change the room to pixel plus UI 3.7 most stable(tested by me).
edit: also less bugs than others and very fluent.
I had the same problem. The solution is to turn off the Game Turbo app. Your problem will be solved.
Mine problem is solved by send it to service center. They replaced screen module.
Reporting.
For anyone facing heavy ghost touch issue, you might want to try indonesian miui 12.5.2 rom (rjuidxm)
Previously I got ghost touch on xiaomi.eu 12.0.4, 12.5.1, 12.5.2 to 12.5.4, few arrow OS version, to the point that I got tired of testing backing up restoring and doing clean flash everytime, because this is my primary phone I use for daily driver
But now I have used miui 12.5.2 ID for 9 days and haven't faced any ghost touch.. I also always turned on show taps on dev options so that I'll know if theres any ghost touch, and theres none so far (I have 6/128 unit with tianma panel)
But there's huge performance drop in this rom, game that I play (PGR) have noticeable frame drops where theres none before, others also reported lower performance on genshin impact
i dont have such issue
at least i dont notice it responding to "something" when i just leave it on table
btw, clothing contacts are also contact
Antonio7489 said:
It's mostly a SW issue , but it can also be a hardware issue(extremely rare),change the room to pixel plus UI 3.7 most stable(tested by me).
edit: also less bugs than others and very fluent.
Click to expand...
Click to collapse
sw?
Skytsengel said:
sw?
Click to expand...
Click to collapse
software?
runfox said:
software?
Click to expand...
Click to collapse
software
Skytsengel said:
sw?
Click to expand...
Click to collapse
software my friend , i write it fast
For me, it has helped now to set the refresh rate and the screen to 60 Hz. We'll see for how long. All other activities did not help, including the game turbo exclusion.
Unfortunately, but with the 60 Hz refresh, the touch has gone crazy once, but it probably happens less often
well it depends on what screen you have, if it's tianma the ghost touch is "normal" and will only get worse because is hardware related, if it's Huaxing it's probably software related or (very bad luck) defective screen...
you can know your screen:
If you are on a Custom ROM or have installed Magisk:
1. Download Device Info HW application
2. Tap on 3 dots in the right corner of the application
4. Restart the app
5. Check LCM (above touchscreen)
dsi_j20s-42-02-0b <- CSOT/Huaxing
dsi_j20s-36-02-0a <- Tianma
If you are on MIUI without root:
1. Open your dialer and enter: *#*#284#*#*;
2. Open a File Manager, go to ~/MIUI/debug_log/ directory, you should see an archive named bugreport-yyyy-mm-dd-HHMMSS; (Date and time when bugreport was created)
3. Extract that archive, then extract another archive which was in bugreport zip, its name should look like this - bugreport-vayu_global-RKQ1.200826.002-2021-05-27-13-32-52.
4. In bugreport-vayu_global folder open dumpstate_board.txt and type in search tianma. If it's found, you have tianma, otherwise huaxing.
Thanks. I checked my tianma. I found such a coincidence "MDPPLATFORM_PANEL_TIANMA_NT36672C_J20S_LCD_VIDEO" How do you think to advertise the phone?
Well there is many reports that it fixed with MIUI 12.5.5.0 global latest update. ( confirm it, please!?)
For me never happened "tianma".
Regards
Jestem na miui 12.5.2.0 EEA i nie ma jeszcze aktualizacji do 12.5.5.0
Update to miui 12.5.5
Antonio7489 said:
software my friend , i write it fast
Click to expand...
Click to collapse
ok thanks for be clear XD
Abdullah.Csit said:
Well there is many reports that it fixed with MIUI 12.5.5.0 global latest update. ( confirm it, please!?)
For me never happened "tianma".
Regards
Click to expand...
Click to collapse
yes my phone update the MIUI to 12.5.5.0 and everything its good and smooth but I'm a little scared, if another update ends up breaking the device. On the other hand, I activated the option, to see the touches on the screen through the developer options, and detect that when I use YouTube and try to put a video in landscape using the button in the video, a single ghost touch appears in the middle of the screen, it does not affect at all apparently, but it seems to me that the ghost touches were not corrected correctly or in its entirety.
I warmly greet. Please I need help. After installing Pixel experience Plus 13.0 in 2022, I marveled at the snappy ROM. After the initial setup I wanted to connect George from online banking but it broke. I am not receiving a confirmation SMS from the bank. Another problem was the distorted ringtone. Sound in games didn't work either. If these bugs were fixed - it's the best ROM ever. Xiaomi 12
Benoni1 said:
I warmly greet. Please I need help. After installing Pixel experience Plus 13.0 in 2022, I marveled at the snappy ROM. After the initial setup I wanted to connect George from online banking but it broke. I am not receiving a confirmation SMS from the bank. Another problem was the distorted ringtone. Sound in games didn't work either. If these bugs were fixed - it's the best ROM ever. Xiaomi 12
Click to expand...
Click to collapse
Well I'm also using pixel experience 13 on Xiaomi 12 I downloaded from droidwin I think, if the distorted sound is in every app , try going to setting,go to trebble settings, Qualcomm features, then toggle off if it's on, I had few issues I fixed a lot but a few left if y'all can help me I would be grateful,
Issues I had
1.sound distorted,I switched off an option in phh trebble in settings, Qualcomm features, then there was a option toggled on, I disabled it
2.120 Hz wasn't working, there isn't an option in setting,I saw a video, just the beginning steps can fix prblm,now screen is always at 120hz
3 camera app was bad can't use different lens slow app,I used gcamator
Remaining problem
1.cant use in display fingerprint, when I go to setup it says press the fingerprint sensor,but its under display and the area doesn't light up
Thread closed since the topic already exists here.