I got an older version of the Gear V R which is for the Note 4 from Ebay, and the seller has been very responsive with me, saying he tried it and tested it with his Note 4, before shipping and it worked perfectly. I installed the Oculus soft ware and it's up grades successfully, after connecting the phone to the head set. But when I put the phone in to get to the Oculus menu, I get a black screen, with a little message popping up saying that the Oculus run time has unexpectedly closed, that hangs for a few seconds, but the black screen stays. I do get to a V R Oculus menu occasionally, but it stays visible for about 10 seconds, then it goes back to the black screen and doesn't come back again
I am in the United Kingdom (London ) , but I have an American version of the Note 4 with AT&T soft ware built in. I am also still on Android 5.1.1 , as I can't upgrade the American version of the Note 4 because of regional differences. The soft ware upgrade version is greyed out
Could the soft ware up date be an issue? Or is there some thing else?
Thanks
Related
I own a Tmobile Note 4, I installed all the Occulus Apps after it was all completed i put the glasses on and its just a solid blue screen, anything i need to change to fix this? besides a restore?
*UPDATE*
I have reflashed Nk4 and still all i get is the blue screen, i see notifications but the occulus store never opens , what am i doing wrong?
I had that happen to me as well. I flashed the newest stock samsung rom with odin (leaving data intact) and things reverted to normal with oculus working
Indeed that worked perfect I just used my vr on my last flight n it was heavenly with my noise canceling headphones
So I just got the galaxy gear vr for s6 and it overheated after about 20 minutes two run throughs of the cirque show. After that I couldn't get the main menu to load, it would stutter then go blank. Same result all night even factory reset my phone and it still wouldn't load. (this may be an unrelated software issue) the premenu warni g works fine and tracks perfectlt.... this morning the next day it all worked again. I am at a loss and so I am wondering if the gear electronics severely overheated because maybe my fan isn't working...
So I ask can anyone tell when their fan is running? Does it run all the time when the phone is plugged in?? I can't hear or feel it at all.
Thanks
Happened to me as well. It was all stutter and sluggish when I first used it. I couldn't even go pass the home screen because the cursor was jumping around and when I panned my head, the screen was loading square by square. I tried restarting my phone, but didn't help. But it was working just fine the next day.
Earlier this month I got a Samsung Gear VR (2016 R323)
My phone at the time, Samsung Galaxy J7, was not compatible - and so I bought a Samsung Galaxy s6 Edge... I plugged it in and installed the necessary software (Oculus and Gear VR services and apps etc.)
But now when I insert my phone into the headset, the screen turns black, with a small white cross in the corner (like one you'd click to exit). This appears for about 3 seconds, then I am back to my home screen with the message at the bottom that reads "Unable to use Gear Vr. Check mobile device properly inserted in Gear VR."
Any suggestions?
I've tried:
rebooting
uninstalling VR updates
installed software updates
generally screwing around with the detachable port, ensuring it's on properly etc
I haven't resorted to factory resetting yet
First things first, grab some PopCorn. Now, here's is my story between me and Samsung
Day 28/04/2018 - The beginning
Well, on 28/04/2018, my tablet went to warranty because it could not charge. It when't with the version T810XXU2DRB1 (latest official version of Android to this model on my region) .
The days have passed....
Day 19/05/2018 - Tablet arrived
On 19/05/2018, I received my tablet back. Samsung said that they replaced the main board the updated the software.
After I receive, immediately made the setup. I updated every single app and installed Instagram, Facebook, and PubG (because, why not). Then, I checked the software version and it was T810XXU2DRB1. So, after it was setup completely, I went to sleep...
Day 20/05/2018 - The heartbreak day
In the next day, I played PubG to test if the tablet performance was still the same before going to warranty. Well, it was a total disaster. The tablet (with the same firmware version before going to warranty), was slower after going to Warranty. Every single app was freezing. The settings app of android was also freezing. Well, I thought "this is the setup, in the beginning is slower because is setting up the android and its apps".
Well, things got worst. Facebook was lagging, Instagram app was getting everything black on the screen (the screen was completely black, with the exception of the android top bar that was on the screen) and the screen was not responding sometimes. Also, when I was installing the apps from Play Store (the Facebook, Instagram and PubG app), the Play Store was freezing sometimes, and the screen sometimes was not responding (not even the android top bar). Ohh I forgot, and yes, it had more than 80% of battery and I never put it in power save mode.
Again, before going warranty the device only had the charging issue, the play store and the other apps didn't freeze.
Then I saw device information on settings app. After some time, the battery reached 10%.
While on Instagram and after the battery reached 8%., it started to show on the screen some vertical lines and each line with a single color, and the lines had different colors. Then, the screen stopped responding until I pressed the power button to lock the device and then unlock it (and it made the lock sound). After that, passed some seconds/minutes, the device made the same thing again and again.... :crying:
Then, passed some minutes, the screen was getting black and not responding. Again, I tried the same trick and the screen worked for some seconds before getting black. While locking the device with the screen black, again, I could hear the locking sound effect. Then, on the day 20/05/2018, I sent back to warranty because the device was worst after going to warranty.
Day 24/05/2018 - The Call
Today, they called me to go to the Samsung Store tomorrow to "demo" what’s happening on my tablet. What can I do about this situation? The tablet warranty is finishing this year on the summer (July or June maybe).
Stay tuned to this story between me and Samsung
What is your opinion? Don't forget to comment below ZenJB
as far as i know, in Indonesia, Samsung is quite famous for its service center.
btw, good luck, hope they will replace yours with a new one
@ZenJB just turn on logcat and you will see what is problem here.
Hello everyone.
I was using UleFone Power 3 (Android 7.1.1) with my RCD330+ without any problems (on VW Golf Mk6 2011 year).
However, phone became old and started developing issues, so I was forced to buy new one.
A few weeks ago I purchased Realme GT Master Edition which runs Android 11.
However, now I am having problems since day one with the phone and RCD330+.
When using Waze, the display on RCD completely freezes for 30-40 seconds every 3-5 minutes. You can pass a few intersections with Waze still showing you frozen far behind. Everything is frozen - map, speed display, etc.
After ~30-40 seconds, it unfreezes and is displayed all fine again for next 3-5 minutes where it freezes again and all repeats.
Could anyone please help me toubleshoot where the problem is?
Only the phone has changed, no configuration changes were done in RCD330+, USB cable also remained the same.
RCD330+ firmware version 5614
Android Auto version 7.6.621703-release
Waze release 4.82.5.1
Another question - what's the best tool to use to switch off Bluetooth after device is being disconnected from USB?
Thank you
I'm having the same problem and I managed to reduce a little bit the freezing. And don't know if it'd work for you.
Enable developers options and go almost to the bottom, under applications there's an option called "Limite de procesos en segundo plano" which might be something like "Limit backgroud processes" and set it to MAX 4 instead of Standard.
It helped quite a bit. Please let me know if you find something else.