Database Develop

[Q] HDMI problem in CM10?

I'm absolutely delighted with the smoothness and functionality of CM10 as of now. Obviously I've been experiencing the usual problems of immense battery drain and call quality, but I'm sure those will be fixed in the short run.
However, another problem I think that is overshadowed by all the other problems is the HDMI. This is probably because barely any people actually utilise it on a regular basis, but some people do.
The phone connects to the TV and projects the image fine. However, it is ALWAYS shown rotated 90 degrees so that the projected image on the TV is always horizontal. This is quite frustrating when I'm trying to watch downloaded TV shows. I've tried disabling the rotation in settings completely; however, no matter what I do the moment i connect the HDMI and then turn my phone on, the image is always portrait and rotated.
Maybe time will fix this. However, I wanted to post this because I was afraid that this problem would be easily overlooked and never fixed.
Thanks!

It was said multiple times. Do not mind, that if yopu create thread for thios bug it will be fixed.
Cheers

Thread Closed, please use the CM10 thread to ask and search for bugs.
Thanks
The-Hulk

Do you feel Google got this right?

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.

I might buy a MI5, looking for some answers/advice

Hey folks, I am Canadian that is looking to possibly import an MI5 but I figured I should find out a few things from you all that have been living with these phones for a while before buying.
Are there any hardware or software issues with the MI5 that I should be concerned about? I have a sony z3 compact right now and it's been infamous for vibration motors, headphone jacks, and screen failures. It also has no AOSP based daily drivers.
Development seems to be pretty active here, is that actually true? Are developers dropping off from this phone or is there still a steady amount of work being done?
From the lurking I've done it seems that unlocking, rooting and ROM installing is pretty easy. Are there any permanent dangers to doing these hacks (above and beyond the usual)?
I'm aware there is some camera quality issues on non-stock ROMs, is the camera still usable? How is the battery on custom ROMs?
Is there anything preventing this phone from being a daily driver when using a custom ROM like RR? Does the fingerprint sensor work on AOSP ROMs?
I am also aware of the radio bands the MI5 supports, I should be fine with that as my imported Z3 Compact has the same bands (as far as I can tell).
Edit: I was also wondering if the IR blaster works on custom ROMs!
Thanks for reading, answering and putting up with my ignorance. I'm just looking for some answers I couldn't find on this forum when I was searching yesterday.

Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.

xdadevet said:
Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.
Click to expand...
Click to collapse
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?

TheHow7zer said:
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?
Click to expand...
Click to collapse
It's a pleasure
Well then it's good to know they run brilliantly on the Mi5 (buttery smooth UI, and I get good numbers on benchmarks as testament, see attached pics).
CAF is short for Code Aurora Forums, a collection of companies that merge their updated driver code with the vanilla AOSP code from Google.
I don't know if the IR blaster works on AOSP as I currently don't have any devices on me to test it with. I could try this weekend when I get home.
Edit: I've since arrived home and can confirm the IR blaster works on AOSP. I used Anymote if you're interested.

Low / Bad video audio quality in certain apps.

Good day everyone,
I've been doing some searching and haven't found anything (outside of some threads in their support site).
I've noticed that when using the rear camera in some applications (i.e - SnapChat, Instagram) that the volume of the video is subpar...almost muffled sounding.
Some people in the support forum have suggested to the Motorola team to look into issues with audio cancellation, but I've yet to find a fix.
Anyone else have thoughts as to what to look at, or if there is some sort of fix out there?
I was a long time user of a OnePlus One with SultanXDA's Lineage OS Rom, Is this also an issue in custom roms? If not, then I may consider going that route instead of waiting on the vendor for a fix.
Thanks!

Its gonna be year, heck what i m saying is even all new g6 also been launched .I think moto/Lenovo has 'moved on' about update as seem by the launch of its successors. While we will be getting patches and waiting for our oreo update , Google will official launch its new Android .

Question [HELP]Fingerprint hardware not available

Initial Problem​The issue arose after having been on Pulkit's LineageOS (unofficial) for weeks. One fine morning i get the following message on my lock screen: Fingerprint hardware not available. To respect the rules of the forum and since I had already gone into detail about it here and found a temporary fix for it, I refrain from reiterating the same.
TLDR​The fingerprint hardware issue came up abruptly, wasn't fixed with changing kernels. Switched to a miui 14 port for a week, everything was working fine, switched back to an aosp rom (Voltage os), runs fine for a day and on the second half of the second day, the fingerprint sensor stops working again.
Help?​I've scoured through the forum in search for a solution to this but seems like it's a truly unique problem x | Has anyone encountered something like this? Were you able to solve it or was there any permanent fix to this? I really don't want to have to use miui if I can help it and after having been on aosp roms for almost a year now, I absolutely can't daily drive miui T.T
Any advise or suggestions on the matter are really welcome!
Attaching the lock screen screenshot...