Back in 2016, Lollipop (Android 5.1.1) was ported to the Google Glass. As of today, there are four known problems with this project:
Audio currently outputs either the left or right signal
Bluetooth connections cannot be made to various devices
Backlight control does not work
Powered off charging indicator is flakey
If a developer could get these bugs fixed, Android 5.1.1 could run on the Google Glass without any major bugs. Then, theoretically speaking, a Google Glass Launcher could be developed for Google Glasses running Android 5.1.1.
Now, I am not a developer. I am throwing out some shower thoughts that I had.
Google Glass is a failed project by Google but, it is also one of the most unique pieces of hardware ever made. Resurrecting this project (Android 5.1.1 for Google Glass) will resurrect the Google Glass and it will also resurrect the Google Glass Community (kinda active on Reddit).
Seems like it. Have you flashed the final update from Google that was released a couple of months ago? It's supposed to allow side loaded apps to work
Related
Now I know Google has a lot of very smart people, but you would be hard pressed to prove that to me based on some of the rather inexplicable design decisions made for Android Auto, especially when you consider that one of its primary goals is to minimize distraction when interacting with Android.
Let's start with the voice button. I know it is in the top right corner of our phones and tablets, but that is a lousy reason to locate it in the same place on your car's display. For US drivers, it seems the most inconvenient place for it.
Moving on to how messages are handled, it feels as though Google wants your right hand off the wheel, and your eyes off the road. Consider that when a message comes in, Android Auto interrupts your audio to inform you of that. Does it read it to you, or offer to read it to you at that point? No. It expects you to touch the top of the screen, but you better do it quickly as it will be gone in a few seconds. Then you will most likely have to make several taps on the screen to have Android Auto read you the message, and return to the screen you were previously on.
And when it does read you a message, it tells you can reply by tapping the voice button (that one at the far right corner of the screen). Why doesn't it just ask you if I want to reply instead of requiring more physical interaction with the screen?
There are other distractions as well, albeit fairly minor when compared to the above. For instance, when my phone is connected solely via Bluetooth and I am listening to something, when I exit and then return to my vehicle, playback resumes. But if I'm connected to Android Auto, again I am required to interact with the screen. It is the same with navigation... turn off the car for any reason and you will have to reestablish your route again when you startup.
Now maybe it's just me, but having Android Auto for just a week or so, these seem like pretty big potholes on the road of usability, and some seemingly so obvious that I'm was surprised to experience them.
So, is it really just me? How do you feel about Android Auto's workflow? Do you find it unnecessarily distracting? Does it require more of your attention than it should?
AA has many issues that need to be fixed.
But I feel confident that Google WILL fix these things.
Connected cars are and will be BIG business and Google will not abandon it as they've done with some other things.
Consider how much was fixed and improved in Android itself from v1 through to 5.1.
Note that we've all been waiting for decades for something like AA in our cars. Google has been working on AA for years, and it will take years more to work out the kinks.
Plugging a phone into an AA head unit is a model that has problems but is somewhat temporary. Googles goal is to have Android itself running in the car or HU* and this solution will be superior. I think we will hear more about this at I/O; Android 6 allegedly has AA "baked in".
*Many HUs (Pioneer, Chinese) are already running Android and I think Honda is working on this now.
AFAICT, most people who have seen AA and Apple CarPlay prefer AA, so Google has the advantage here.
mikereidis said:
Consider how much was fixed and improved in Android itself from v1 through to 5.1
Click to expand...
Click to collapse
I have... which is a big reason why I bit the bullet. For me, Android was way too rough 'till JB (which is when I switched from iOS). I am hopeful AA's path will be on road with a much higher speed limit.
Quick rant: I purchased a pixel 2 xl and a Pioneer NEX headunit and was very excited to get Android Auto in my vehicle. Since day one it's been a raging dumpster fire. Biggest issue being Android Auto just won't launch on my pixel 2 xl and my wife's pixel 2. However my Nexus 6p works perfectly. Sometimes it launches within a few minutes, sometimes it takes my entire 45 min commute to work and it never launches. It's like it's RNG based. Once connected it stays connected. I'm not going to into all the other frustrating bugs such as volume issues, Assistant coming out of different speakers, hangs, crashes, weather tile is now gone somewhere, and many more smaller gripes.
Now that that's out of the way does anyone make a ROM or unofficial app for Android Auto that works on some of these issues? In the past I relied on the community to fix Google's shortcomings. It may just be that since this only seems to affect the pixel 2 and Android Auto that there are only a few people experiencing the issues I am. With only a few affected there may be no community attention.
Not sure if this is what you are talking about, but there is the openauto project and crankshaft:
https://github.com/f1xpl/openauto
https://github.com/htruong/crankshaft
Since his Nexus 6p is working very well the issue is on the phone end, not the HU. I am having similar issues with a Sony Z3 compact I am playing with to keep AAMirror on. However, other phones running latest version AA 3.1 have no issue at all - Note8 on Oreo, S8 on Oreo, S4mini on Lineage 14.1 all connect ASAP to my Suzuki HU.
I am interested in a buying a 2nd all-arounder phone that mostly ticks all key boxes and found out that the XZ2 is almost there.
As it will be my first Sony I need your experience with the device to decide to buying it or get a different one:
1) are there any serious issues that affect the device, maybe design issues or bad experiences with the device? Maybe display, speakers, or other hardware stuff to concern me?
2) I am interested in root-ability o this phone. Is I saw that there is some development. for this phone and since I am sort of experienced in Custom ROM stuff, I want to know if there are specific rooting issues? Are the valid options for un-bricking it, just in case. Is there a big amount of bricked phones?
3) how's sony with the updates for this device for official firmware updates?
4) is Google Camera functional after rooting?
5) is the phone performance still holding good in late 2019?
I appreciate your responses in any form or shape!
catalindobre said:
I am interested in a buying a 2nd all-arounder phone that mostly ticks all key boxes and found out that the XZ2 is almost there.
As it will be my first Sony I need your experience with the device to decide to buying it or get a different one:
1) are there any serious issues that affect the device, maybe design issues or bad experiences with the device? Maybe display, speakers, or other hardware stuff to concern me?
2) I am interested in root-ability o this phone. Is I saw that there is some development. for this phone and since I am sort of experienced in Custom ROM stuff, I want to know if there are specific rooting issues? Are the valid options for un-bricking it, just in case. Is there a big amount of bricked phones?
3) how's sony with the updates for this device for official firmware updates?
4) is Google Camera functional after rooting?
5) is the phone performance still holding good in late 2019?
I appreciate your responses in any form or shape!
Click to expand...
Click to collapse
I like my still fast XZ2 with OmniROM 9.0
catalindobre said:
I am interested in a buying a 2nd all-arounder phone that mostly ticks all key boxes and found out that the XZ2 is almost there.
As it will be my first Sony I need your experience with the device to decide to buying it or get a different one:
1) are there any serious issues that affect the device, maybe design issues or bad experiences with the device? Maybe display, speakers, or other hardware stuff to concern me?
2) I am interested in root-ability o this phone. Is I saw that there is some development. for this phone and since I am sort of experienced in Custom ROM stuff, I want to know if there are specific rooting issues? Are the valid options for un-bricking it, just in case. Is there a big amount of bricked phones?
3) how's sony with the updates for this device for official firmware updates?
4) is Google Camera functional after rooting?
5) is the phone performance still holding good in late 2019?
I appreciate your responses in any form or shape!
Click to expand...
Click to collapse
1-some devices are affected from bad production including mine, ghosting on LCD below room temperature, horizontal static electric lines appearing after rubbing the screen, speakers may get temporary damage for no reason (can be fixed by opening the sim tray and pulling that paper in there and waiting a little) or can get permanently damaged if you overdrive them with something like xLoud easily, if you dont want a super slippery 200g heavy 1.1cm thick glass brick look somewhere else (buttons are jiggly too)
2-custom roms have problems with audio and camera and it'll take some time to get fixed and at the end there's the possibility of it not being better than stock camera (also typical sony drm stuff will be lost after unlocking the bootloader)
3-device getting regular security patches and will be updated to android 10 in early 2020 (keep your bootloader locked if you want OTA)
4-no, gcam requires full camera2api and raw support which isnt there on stock
5-performance is good probably due to having close to stock android
this is my first xperia and I'd not recommend this phone to anybody unless you are crazy about what is sony doing with their sony open devices project like the guy above martin
Faruk.ErdaL said:
1-some devices are affected from bad production including mine, ghosting on LCD below room temperature, horizontal static electric lines appearing after rubbing the screen, speakers may get temporary damage for no reason (can be fixed by opening the sim tray and pulling that paper in there and waiting a little) or can get permanently damaged if you overdrive them with something like xLoud easily, if you dont want a super slippery 200g heavy 1.1cm thick glass brick look somewhere else (buttons are jiggly too)
2-custom roms have problems with audio and camera and it'll take some time to get fixed and at the end there's the possibility of it not being better than stock camera (also typical sony drm stuff will be lost after unlocking the bootloader)
3-device getting regular security patches and will be updated to android 10 in early 2020 (keep your bootloader locked if you want OTA)
4-no, gcam requires full camera2api and raw support which isnt there on stock
5-performance is good probably due to having close to stock android
this is my first xperia and I'd not recommend this phone to anybody unless you are crazy about what is sony doing with their sony open devices project like the guy above martin
Click to expand...
Click to collapse
I'm sorry to hear that you got a faulty unit.
Did you try to RMA it?
Because I never had such issues, except touch issues in Android 8, which got 90% fixed now (Sometimes while I super fast do swipes on the keyboard it may not recognize only a single swipe at the beginning of the writing).
Camera and Audio are work in progress on the custom roms based on sony open devices project.
SODP is an isolated sony employee team in the sony company + volunteers which need to implement everything by themselves without access to the stock source code (but with access to the closed source Qualcomm source code and documentations).
The camera doesn't degrade on unlock on your stock firmware, so you can freely continue using the stock firmware until the SODP camera reaches a equal or better quality.
(Since SODP supports the entire Camera2API with RAW and GCAM support to raise the quality it may become better than stock.)
And the performance is like stock on SODP.
My benchmark shows the same values like stock, too and you don't have bloat/stock apps preinstalled without the possibility to remove them without root.
PS: The SODP based custom roms are not affected by DRM, since they are a reimplementation of the hardware drivers, there isn't any usecase for DRM keys.
Hello there!
I'm experiencing a weird issue after the latest update from December 2020. Since then, my back button (or technically the lower part of my screen) is very irresponsive and does not register touch input. I uploaded a video on Youtube to showcase the issue:
What you can hopefully see is that the back button is very responsive when it comes to horizontal movement; touching far left or far right of the button is still registered as input. However if I touch just slightly below (or sometimes even on) the icon, it does not register my input. This includes the fact that the system does not register the touch at all (as you can see by the active developer tool). This is very frustrating as it also happens with the other two buttons. It seems as if Google has incorporated a kind of "palm detection" or "accidental touch prevention" on the far edges of the screen.
I already activated the "High sensitivity mode" of the display since I have a screen protector installed. However, before the update the issue was not apparent, so I'm convinced the screen protector is not the issue.
Does somebody also experience the issue or may even have a solution for this?
Cheers!
WookieCookie said:
Hello there!
I'm experiencing a weird issue after the latest update from December 2020. Since then, my back button (or technically the lower part of my screen) is very irresponsive and does not register touch input. I uploaded a video on Youtube to showcase the issue:
What you can hopefully see is that the back button is very responsive when it comes to horizontal movement; touching far left or far right of the button is still registered as input. However if I touch just slightly below (or sometimes even on) the icon, it does not register my input. This includes the fact that the system does not register the touch at all (as you can see by the active developer tool). This is very frustrating as it also happens with the other two buttons. It seems as if Google has incorporated a kind of "palm detection" or "accidental touch prevention" on the far edges of the screen.
I already activated the "High sensitivity mode" of the display since I have a screen protector installed. However, before the update the issue was not apparent, so I'm convinced the screen protector is not the issue.
Does somebody also experience the issue or may even have a solution for this?
Cheers!
Click to expand...
Click to collapse
Yes, I've noticed the same thing. Seems to be only the back button.
This is a widespread issue that has been reported by many. So far there is still no update from Google. I am running November build without any touch issues. Google support forum with lots of people reporting.
same problem for me, I hope it will be fixed soon
Looks like this is fixed in the January, 2021 release that came out today!
This issue was NOT fixed in the January release. I and many others are confirming this. Google has yet to fix a major touch-screen bug, almost 2 months after the issue was brought up.
Mine was definitely better in the January release, but yeah, still having the issue here and there (especially when an app is heavy on the processor). This press release should help out: https://www.androidpolice.com/2021/...ssue-can-make-navigation-buttons-hard-to-use/
Same here. But on another side, why do we have to wait another month for a known issue?
Hello everybody , my name is Chris I live just outside of Joliet IL. My occupation is I'm American board certified laboratory optician basically I'm the guy that fills the prescription and makes the glasses. I came across this site well looking to look looking to rollback my Android operating system to Android 10 the phone is a Moto G power 2020 I've read some of the postings and I'm really new at this so I'm trying to figure out what all the terminology is and what it means. I've been having issues with the phone. I have been able to flash the Android 11 with the Motorola rescue program but that really didn't seem to help . Motorola has been no help whatsoever they told me it's the operating system and call Google???? Some of the issues I've been having are very slow and lagging performance. Websites just closing on their own and the whole Google program shutting down , or Chrome program shutting down/ this started happening around September 15th after Google Chrome update and then a Google update and for some reason I can't turn off the vibration in the Google app and or the Google widget I get a real short vibe when I touch the microphone and a real short vibe when it comes back with results I've tried just about everything and the only way that I found to stop it from vibrating is that uninstall the Google update and turn off auto update, it's just really bothersome to me because I have epilepsy and it trigger something in my body that I don't like. I thought Android 10 was a much better operating system.
caddy4 said:
Hello everybody , my name is Chris I live just outside of Joliet IL. My occupation is I'm American board certified laboratory optician basically I'm the guy that fills the prescription and makes the glasses. I came across this site well looking to look looking to rollback my Android operating system to Android 10 the phone is a Moto G power 2020 I've read some of the postings and I'm really new at this so I'm trying to figure out what all the terminology is and what it means. I've been having issues with the phone. I have been able to flash the Android 11 with the Motorola rescue program but that really didn't seem to help . Motorola has been no help whatsoever they told me it's the operating system and call Google???? Some of the issues I've been having are very slow and lagging performance. Websites just closing on their own and the whole Google program shutting down , or Chrome program shutting down/ this started happening around September 15th after Google Chrome update and then a Google update and for some reason I can't turn off the vibration in the Google app and or the Google widget I get a real short vibe when I touch the microphone and a real short vibe when it comes back with results I've tried just about everything and the only way that I found to stop it from vibrating is that uninstall the Google update and turn off auto update, it's just really bothersome to me because I have epilepsy and it trigger something in my body that I don't like. I thought Android 10 was a much better operating system.
Click to expand...
Click to collapse
Hi Chris,
You have come to the right place and I hope you can find a solution to your problems.
Welcome and have a good time to the forums