Hey Everyone,
I was able to get all Pixel features like photos unlimited, call screen, hold for me in OOS using this Magisk Module.
But upon installing, the brightness of the device is set to low and completely broken so it doesn't change. Did anyone able to run it and fix this?
I was able to use it by going in to fingerprint and click add fingerprint which brings the brightness back to normal and quit the fingerprint by swiping in notifications and the brightness presists but that's not usable in long term
Edit1: Seems like I was wrong. All the features are getting turned off one by one.
Writing here for anyone who wants to get pixel features in oxygen os rather than AOSP.
I was able to solve the issue. All I had to do is delete the system.prop file from the module and install it. Now the photos shows unlimited uploads and I don't have the brightness issue.
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
As stated, removing the "system.props" from the module breaks the feature of the module
5ud0 said:
Edit1: Seems like I was wrong. All the features are getting turned off one by one.
Writing here for anyone who wants to get pixel features in oxygen os rather than AOSP.
I was able to solve the issue. All I had to do is delete the system.prop file from the module and install it. Now the photos shows unlimited uploads and I don't have the brightness issue.
Click to expand...
Click to collapse
I have same issue... I got call screening Pixel feature in Oxygen by changing device fingerprint but have same screen brightness problem.
Can you please some detail of how to delete the system.prop file in the module and then install it.
5ud0 said:
Hey Everyone,
I was able to get all Pixel features like photos unlimited, call screen, hold for me in OOS using this Magisk Module.
But upon installing, the brightness of the device is set to low and completely broken so it doesn't change. Did anyone able to run it and fix this?
I was able to use it by going in to fingerprint and click add fingerprint which brings the brightness back to normal and quit the fingerprint by swiping in notifications and the brightness presists but that's not usable in long term
Click to expand...
Click to collapse
Inervo said:
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
As stated, removing the "system.props" from the module breaks the feature of the module
Click to expand...
Click to collapse
sjgoel said:
I have same issue... I got call screening Pixel feature in Oxygen by changing device fingerprint but have same screen brightness problem.
Can you please some detail of how to delete the system.prop file in the module and then install it.
Click to expand...
Click to collapse
I actually have a *partial* solution to this. If you are changing the fingerprint to enable call screening or call recording in Google Phone, then the solution is to use Google Dialer Mod instead. It's a root app that has toggles which literally allow you to turn on Call Screening, Call Recording, and pretty much any other Google Phone feature you'd want to enable. No fingerprinting necessary. If you were trying to get other pixel mods, unfortunately I have no answer to that.
Related
I normally use a Macro in Macrodroid to activate Speakerphone when I am on call and phone is away from my ear. This help me do multitasking, easy way. I can manually activate and deactivate Speakerphone, but it slows down my regular working while on phone.
However, this is not working in Oneplus 6. I also tried Tasker profile, but it is not working as well. Does anyone have any idea how this will work on Oxygen OS? I looked in to Oneplus Forums and can see many users facing this issue with earlier OP devices as well.
P.S. I tried Auto Speaker app from play store and it did not work as well.
I do believe this may be achieved by Gravity Box, but I am not inclined to install Xposed as of now.
Update: some people on OP forum said that problem could be dialer. So I installed Google Dialer as default but It did not work as well.
samrat_castle said:
I normally use a Macro in Macrodroid to activate Speakerphone when I am on call and phone is away from my ear. This help me do multitasking, easy way. I can manually activate and deactivate Speakerphone, but it slows down my regular working while on phone.
However, this is not working in Oneplus 6. I also tried Tasker profile, but it is not working as well. Does anyone have any idea how this will work on Oxygen OS? I looked in to Oneplus Forums and can see many users facing this issue with earlier OP devices as well.
P.S. I tried Auto Speaker app from play store and it did not work as well.
I do believe this may be achieved by Gravity Box, but I am not inclined to install Xposed as of now.
Update: some people on OP forum said that problem could be dialer. So I installed Google Dialer as default but It did not work as well.
Click to expand...
Click to collapse
Why not have speakerphone on always, but deactivate it when the phone is near your ear?
nabbed said:
Why not have speakerphone on always, but deactivate it when the phone is near your ear?
Click to expand...
Click to collapse
Same principal is used in the macro, profile and app. It's not working.
That's Automation.
Any help?
Still haven't found a solution for this either.
samrat_castle said:
Any help?
Click to expand...
Click to collapse
I'm looking for this feature too... In resurrection remix 7.1.2 on nexus 6 the dialer has the option to activate the loudspeaker with proximity sensor, you could even set the reacting time. This feature is present even on pure nexus 6.0.1 but it's no more present since Oreo. Don't know why . Every option o app or trick I tried to emulate this feature is not working as good as the integrated one . We should try to dump the phone app , it's almost a replica of the Google one . I really miss this feature, because when I work on smartphone repair over a microscope, I could answer with my android wear and my smartphone over the desktop answer the call in loudspeaker mode
We should use this thread to discuss about the official Android 9 update for the Mi A2 Lite!
Cool, but many didn't get the update yet...
It has dark mode?
I am on Havoc OS 2.0, but it hasnt update... Maybe I will return to stock...
iniro said:
It has dark mode?
I am on Havoc OS 2.0, but it hasnt update... Maybe I will return to stock...
Click to expand...
Click to collapse
I thought it has the dark mode, but it hasn't. You can find it in the settings but if you activate it nothing happen..
I noticed that the performance is slightly better than Oreo. The phone runs faster and there are much fewer lags!
First I thought the battery drain got heavier, but after the second day it reached the normal drain, which we know from Oreo
Also I love the new stock launcher. It's like the Pixel-Launcher with the "at a glance" feature, just as the new navigation-gestures which we also know from the Pixel-devices.
00norman00 said:
I thought it has the dark mode, but it hasn't. You can find it in the settings but if you activate it nothing happen..
Click to expand...
Click to collapse
It has a dark mode but it's very limited. When you activate it the quick settings in the notification area and some colour accents on the home screen and app list will become dark. It will not, however, change any other colours in the OS.
I'm experiencing some serious lag at moments.
On oreo I barely experienced lag at all.
Any advice?
I'm having lag/stutter in recent tasks... It was way faster in Oreo and I preferred the vertical layout.
Sent from my Mi A2 Lite using Tapatalk
agamotto said:
I'm having lag/stutter in recent tasks... It was way faster in Oreo and I preferred the vertical layout.
Click to expand...
Click to collapse
If you have root, you can disable the StockLauncher and download another launcher from the PlayStore. Then you will have the vertical layout.
Updated mine in Austria by following the VPN method.
On first boot I face WiFi connection issues and also Bluetooth is not working fine. - resolved by the first reboot
I face a poor call audio distortion.
Videos, Music, etc. that uses the other loudspeaker is working fine but in phone calls using the other speaker I face massive saturation effects even with small volume.
I also tried to manufacturing reset my phone, without success.
best regards,
Mario
Correct. I updated mine yesterday and can confirm, poor call audio distortion. That thing drives me nuts.
The arrows on the network and wifi icons on notification is also a thing to remove, or at least give us the chance to remove it.
Besides that, i didn't see to much cases.
sandman01 said:
Updated mine in Austria by following the VPN method.
On first boot I face WiFi connection issues and also Bluetooth is not working fine. - resolved by the first reboot
I face a poor call audio distortion.
Videos, Music, etc. that uses the other loudspeaker is working fine but in phone calls using the other speaker I face massive saturation effects even with small volume.
I also tried to manufacturing reset my phone, without success.
best regards,
Mario
Click to expand...
Click to collapse
This is a widely seen bug for Pie which I personally find not acceptable in 'stable' release. Couldn't do a calls due to sound quality and reverted back to Oreo.
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you clear the Data of the Google Apps?
itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you clear the Data of the Google Apps?
streetspy said:
This is a widely seen bug for Pie which I personally find not acceptable in 'stable' release. Couldn't do a calls due to sound quality and reverted back to Oreo.
Click to expand...
Click to collapse
Can you detail how to revert to Oreo?
Sent from my Mi A2 Lite using Tapatalk
itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you remove sim card and wipe all the things?
00norman00 said:
Did you clear the Data of the Google Apps?
Click to expand...
Click to collapse
I did.
itwasmistake said:
I did.
Click to expand...
Click to collapse
Mhmm, it only work for me when I used the CyberGhost-VPN-App (free trial). ExpressVPN or something else didn't work for me
Okay. So doing factory reset fixed the lag in recent apps.
But I did an antutu benchmark and the performance has dropped significantly from 78232 to 67477.
Anyone else can confirm this?
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.
I have a rooted Indian version of OnePlus 8T.
Everytime I try to change my device props to Pixel props via directly flashing the pixel props file or using "Magisk Hide Props" module - the display brightness breaks.
While the lock screen is still okay and the brightness behaves normally but as soon as you unlock the phone it goes too dim. Sliding the brightness panel doesn't do anything and neither does disabling adaptive brightness. I've stumbled across months old posts about someone having the same issue with Oneplus 8 Pro but didn't find any solution there either.
Please, anyone let me know if you can somehow get around those problems?
Thank you!
Hi,
Did you find any solution. It seems that it breaks the highest available brightness on the device . I am not sure how to enable that
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
Removing the "system.props" from the module breaks the feature of the module
Inervo said:
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
Removing the "system.props" from the module breaks the feature of the module
Click to expand...
Click to collapse
Hi, Did you find any solution? I have same problem.
sjgoel said:
Hi, Did you find any solution? I have same problem.
Click to expand...
Click to collapse
I actually do have a *partial* solution to this. If you were changing the fingerprint to enable call screening or call recording in Google Phone, then the solution is to use Google Dialer Mod instead. It's a root app that has toggles which literally allow you to turn on Call Screening, Call Recording, and pretty much any other Google Phone feature you'd want to enable. No fingerprinting necessary. If you were trying to get other pixel mods, unfortunatley I have no answer to that.