Wondering if anyone out there prior to switching over to the ROG Phone has experience on making a non-Daydream device a Daydream device?
I tried one of the modules within Magisk, but it would make the phone crash and reboot (causing AudioWizard to crash).
I just bought a Daydream headset in hopes that I'll find a way to use it with this phone. It seems like it'd be a great mobile VR device. I'm glad I'm not the only one curious.
The phone has the specs. I found this article that might help:
https://www.vrheads.com/how-manually-enable-daydream-phones-google-has-not-approved
ok I got Daydream and Keyboard installed, but I am at work right now and I don't have my Daydream headset here. Will report back how it goes tonight.
unfortunately, after setting up all of Daydream.... as soon as you put the phone in to the daydream goggles, it just goes to a black screen. Had to power off to reboot to get anything working again.
so it looks like its gonna need more than just a few lines insertion to get Daydream working on this phone
Related
Hi
I've recently got one of the EU 1/8 Omate Truesmart watches. To start with it was fine, but after realizing I had missed some calls yesterday I realized that the watch made no sounds and the mic wasn't working either when I made some test phone calls. The vibrate does still work. I've changed the Modes in the Audio Profile but that doesn't seem to have made a difference.
Has anyone else had these problems?
I suspect the mic and speaker are in different parts of the watch, so I'm guessing its a software issue rather than something has shaken loose. I tried to work out how to reset the watch, but so far I haven't worked out how to do that (I haven't patched it yet, so it still has the original version of the firmware etc).
Thanks for any assistance
Somehow I managed to get the sound and mic working again . The last thing I was trying was to turn the watch off and on repeatedly, pressing or holding the two buttons down while it booted. One of the other posts suggested that I could get to a menu to reset the watch this way. Whilst I never saw a menu, on one occasion it did take longer to boot than normal (a few extra seconds) so I may have selected an option with out realising.
I've been reading here for months waiting for my TS to arrive and today it has!
I quickly found that all sound and mic was not working and my heart sank. But reading this question and the poster's own reply, and a hint from elsewhere, I turned off "fast boot" in the accessibility menu, shut down and restarted, and hey presto, sound input and output works fine. The "fast boot off" setting seems to be required in order to make the device really reboot.
Many, many thanks to all here who have been contributing to the knowledge base on this device. Hopefully I can now contribute, if only from the point of view of a non-expert man-in-the-street end user, from time to time.
Hello,
Rather an unusual problem, i dont intentionally want to go the difficult ADB way, being the novice I am. However I cannot access a usual settings in my current favorite ROM, so I need a way to get to it.
I have been using this ROM on my S4 i9500. I am unable to find an option in the ROM for Day Dream. In other ROMs, when on the daydream setting screen, there is option via the menu button, to choose when the DayDream should work "While Charging" or "While Docked" on while on either of them.
In Ozcan 6.3 ROM we can only choose the daydream to be ON or OFF, the menu button does not work to let us choose the conditions for daydream.
In my case I have a Samsung multimedia dock which I normally use for charging as well. So when I dock the phone , it is recognized as "Docked" hence the daydream is never activated. Otherwise if I simply connect a charger to mobile, the daydream starts after a while.
So I need to know is there a way we can change this settings to be able to daydream also when the phone is DOCKED, it serves me well as being a bed side alarm clock.
I guess there should be a way to change this settings directly via the ROM settings files or via ADB. Only need your guidance and support to know how.
Hope I was able to explain my problem.
Thanks.
Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Sleep mode? as in while screen is off? or another mode?
skygear said:
Sleep mode? as in while screen is off? or another mode?
Click to expand...
Click to collapse
Yes. When the screen is locked.
My phone was like that at one point, I am on Pie now and I had to go into the settings and make sure it was set to work even when the screen was off. Took a minute to find, have you checked there?
Settings/Google/Search, Assistant and Voice/Voice/Voice Match
I have. The phone vibrates when the screen is off and I say "OK Google" but is the screen remains black until I press the home button.
I'm thinking now that perhaps it has something to do with security and not with Google Assistant. I'm going to check my security settings. Maybe there's something there.
Come to think of it, I've had that happen before, not now but some time ago. I never sound effects, never really tried, somehow it just seemed to resolve itself after a while I guess. Good luck and keep us posted, you might be right in that it has to do with some security setting or something.
This? Access with voice match?
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
YrrchSebor said:
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
Click to expand...
Click to collapse
I’m sure that’s the option the OP needs to use.
I think it's a common problem with Google assistant and potentially the same as the 'voice unlock paused' issue, I've seen people complaining about both on pixel forums as well as on here (if Google can't get it right with their own phone what hope do we have!!). There were a few steps around deleting the voice model and resetting the smart lock agent (see screenshot). I did this and retrained the voice model in absolute silence which seemed to work for a bit but has since stopped. Annoyingly it doesn't seem to take into account when I'm at home and the phone is unlocked with smart lock!
xc rider said:
I’m sure that’s the option the OP needs to use.
Click to expand...
Click to collapse
OK. Here is my screenshot of the settings that I have on my phone. Access and Unlock with Voice Match are turned on.
Let me reiterate. The phone is reacting to "OK Google" on every screen so the voice match is working.
The problem is that when when I am on the lock screen and I say "OK Google" the phone vibrates, acknowledging that it heard the prompt but it does nothing until I press the home button or power button.
Have a look at this video. (I distorted for privacy reasons the audio because my phone and tablet were reacting when I was playing back the video):
https://youtu.be/fO3nsJ215eo
I have the S9+ on Rogers and thankfully, this feature continues to work flawlessly after the upgrade as I use it often in my daily work..It actually seems to be more responsive after the update.
It can be very frustrating when the feature randomly stops working but it is usually due to an update on Google's end that causes it as I can usually fix it by going through the voice setup steps after an update..
In extreme situations you may want to uninstall and then reinstall the Google app..
Had the same problem myself and fixed it, just go to app info for Google and clear the cache and clear data, worked a treat for me
Roli001 said:
Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Click to expand...
Click to collapse
I'm on an S9+ with Bell in Canada and I can still unlock my device with voice when it's sleeping even though it gave me a notice that I would no longer be able to.
For some reason I've lost the ability to voice control any of my smart devices through Google Home. Seems like a related but different problem.
That, the lack of pro video mode and the brutal battery life have really turned Pie into a nightmare for me..
Hope they release fixes for these issues or I'll have to look at flashing..
Hey there, Loving the Poco so far, except two issues that I would really like to see resolved:
1: I would like to be able to pair my Samsung Gear S3 to the phone. So far I have searched out all sorts of side loaders and custom APK's but I have not been able to get this to work. Has anyone found a solution specific to the Pcocophone running Lineage OS/ PIE?
2: With the phone connected to my vehicle (Kona) it constantly errors out with the message on the Display "Phone has been disconnected". When this happens the audio through the phone continues, and the Google maps is still running (still receiving voice commands), however it boots to the main screen. When clicking Android auto again sometimes it opens like normal, however other times the screens show normally, however the bottom row of navigation buttons is missing, and it shortly crashes. Has anyone else come across this issue, and have any resolutions?
Any help would be appreciated!
Hi everyone,
The touchscreen of my Stratos 3 has stopped working... The buttons do still work and I was able to reboot using the buttons but still no touch. Is there any way to factory reset without touchscreen?
Thanks
kulaki0 said:
Hi everyone,
The touchscreen of my Stratos 3 has stopped working... The buttons do still work and I was able to reboot using the buttons but still no touch. Is there any way to factory reset without touchscreen?
Thanks
Click to expand...
Click to collapse
Install adb/fastboot drivers and use:
Code:
adb reboot wipe
After is done, just turn on the watch and pair with Amazfit app.
Saratoga79 said:
Install adb/fastboot drivers and use:
Code:
adb reboot wipe
After is done, just turn on the watch and pair with Amazfit app.
Click to expand...
Click to collapse
Thanks, I am going to return it. Amazon costumer service offered a full refund even if the return window had closed.
Same issue with my stratos 3
I have the same issue with my stratos3. I rebooted and factory reset using the physical buttons, however it didn't help. Is the adb command doing something different than the factory reset on the menu?
I notice that touchscreen is working in ULTRA mode but not working when I swap to SMART mode.
I does the same. How did you get to do the factory reset without touch?
Click on the scroll up button, then on the top button. Scroll down until "device", top button again and scroll down until you see factory reset.
youtu.be/UHeYx3cv_6E
I hope it helps, on my case touchscreen still not working on SMART mode but works fine on ULTRA mode.
Wahezu said:
I have the same issue with my stratos3. I rebooted and factory reset using the physical buttons, however it didn't help. Is the adb command doing something different than the factory reset on the menu?
I notice that touchscreen is working in ULTRA mode but not working when I swap to SMART mode.
Click to expand...
Click to collapse
This happens to me since last update.
An workaround is to do a single reboot in smart mode and the touchscreen works again.
It happens every time I switch from ultra to smart.
Rebooting or factory reset don't help in my case. How can you switch back to ultra mode when the touch is not working? I have actually never used the ultra mode so I don't think it is what triggered it
Nevermind, I found how to enable ultra mode with the buttons. Indeed the touch screen woks but not at all on smart mode.
This is a terrible sw bug
Same here. No difference with reboot or factory reset. Touchscreen only works in ultra mode.
Hopefully they will fix it in the next software release if we manage to report it to them. I tried contacting Amazfit without luck.
kulaki0 said:
Rebooting or factory reset don't help in my case. How can you switch back to ultra mode when the touch is not working? I have actually never used the ultra mode so I don't think it is what triggered it
Click to expand...
Click to collapse
You can do it with the physical buttons.
In the watchface: press up to settings, then select. Scroll down pressing down until device menu.
Using this, try a single reboot in device menu. It solves in my case.
Hi,
I am another affected of the touchscreen issue. It started yesterday, I believe, but I am not entirely sure as I tend to use the physical buttons a lot. My phone updated to Android 10 (coming from Android 9) just yesterday, so I am not sure if this has any effect on this issue.
Since last time I remember the touchscreen working, these are the things I did/happened:
1. I ran out of battery
2. Next morning I charged it to 100%
3. I used the watch for the whole day
4. Next day my phone updated to Android 10 (Miui 11)
5. That same evening I realised the touchscreen was not working.
I have soft reset the watch without luck, I'll try with a factory reset to see if it works.
Have you tried in Ultra mode?
I reported it to Amazfit and they are looking at it. I hope they find the root cause soon. It is annoying as I bought that watch because of the storage for music but I cannot play music without the touchscreen working and music is not available in Smart mode.
Wahezu said:
Have you tried in Ultra mode?
I reported it to Amazfit and they are looking at it. I hope they find the root cause soon. It is annoying as I bought that watch because of the storage for music but I cannot play music without the touchscreen working and music is not available in Smart mode.
Click to expand...
Click to collapse
You can play music, put music as a widget so you can use physical buttons to play. In my case, I use the buttons on my Bluetooth headset to rise volume and change tracks.
BTW: how did you reach Amazfit?
I think the issue is the same for all, no touch screen in Smart Mode, but working as usual in Ultra Mode...
Btw, how did your problem started? I believe is because I ran out of battery in Ultra Mode, and then I charged the smartwatch and entered Smart Mode automatically. Maybe Ultra Mode turns off when no battery whithout properly save file corruption or something...
Or, it has something to do with Android 10?
lindomaroliveira said:
You can play music, put music as a widget so you can use physical buttons to play. In my case, I use the buttons on my Bluetooth headset to rise volume and change tracks.
BTW: how did you reach Amazfit?
Click to expand...
Click to collapse
I Contacted them via the feedback feature from the App. They replied asking for the same from the watch. I haven't heard back from them since then. Hopefully they have found they issue and they release a fix with the next firmware update. Otherwise it will be my last Amazfit/Xiaomi Device. I am so fed up with so many software issues on their devices.
bigata said:
I think the issue is the same for all, no touch screen in Smart Mode, but working as usual in Ultra Mode...
Btw, how did your problem started? I believe is because I ran out of battery in Ultra Mode, and then I charged the smartwatch and entered Smart Mode automatically. Maybe Ultra Mode turns off when no battery whithout properly save file corruption or something...
Or, it has something to do with Android 10?
Click to expand...
Click to collapse
I don't have Android 10 yet and never used Ultra mode before. And suddenly I got the touch issue
Here is the replied from Amazfit support:
###############################
The tech team just replied that this issue cannot be solved online.
Could you please kindly contact the seller to see if you can return the watch for repairing or replacement according to their warranty policy.
###############################
I have had one redmi note 3 pro , one mi5 ,one Amazfit pace and now the stratos 3. Which is going to be the last Xiaomi device I ever buy. Apart from the pace the rest of devices had hardware defects or software bugs. Xiaomi never again.
Wahezu said:
Here is the replied from Amazfit support:
###############################
The tech team just replied that this issue cannot be solved online.
Could you please kindly contact the seller to see if you can return the watch for repairing or replacement according to their warranty policy.
###############################
I have had one redmi note 3 pro , one mi5 ,one Amazfit pace and now the stratos 3. Which is going to be the last Xiaomi device I ever buy. Apart from the pace the rest of devices had hardware defects or software bugs. Xiaomi never again.
Click to expand...
Click to collapse
So, not a software issue... I hope I can return it and not only get a replacement... I rather look for a different smartwatch, better finished than this.
The touchscreen works on ultra mode so this is deferentially a software bug. That a front line costumer support sugest to return it doesn't make it a hw issue. Said that I have returned mine because it was still possible and I don't know when they will fix it.
No issue yet on the replacement unit