I figured i just make a new post since i tried searching and I'm getting no luck either that or not entering the right search info. Is there a game like Crash Bandicoot Nitro Kart 3D (the one that is on the iPhone and Ipod touch) doesn't have to be the exact racing game just uses the same controls using the g-sensor ex. tilt phone forward is the gas, tilt phone right vehicle goes right and so forth. I know there has to be one with all the other g-sensor games out there. If there isnt then whats taking so long!
So I've heard that Lenovo Moto Z is the new daydream ready phone. Have you tried using it with daydream view? How is the performance? I also heard that this phone tends to overheat. Is it a problem when playing in VR?
I know the Pixel phones have been producing a lot of heat while using daydream. The reason for the heat is the amount of power required to run VR which causes the phone to throttle from all the heat being produced. You can expect about the same amount of heat considering the specs of the phone. I could imagine the Moto Z would perform about the same as the Pixel considering the Pixel only has a slightly over clocked version of the Snapdragon 820 used in the Z. Since people have just started receiving the Android N update for the Z more people should be able to comment on actual performance soon. Hope this somewhat helped.
I have the Moto Z and the daydream headset is on the way. I'll give a review on what I think when it arrives in a few days. And how long it takes to overheat (get the on screen overheating message). Anything else you want me to check out on it?
The daydream headset is good on the moto z. The biggest annoyance is that the headset allows some light to come in on the side. I imagine this will vary for each person based on head/face shape. I've played with it multiple times for 30+ minutes. I never got the message about getting too hot. But every time I took it out the phone was way too hot to hold. I mean it would probably burn your hand if you held onto it. Which kind of worries me. But I would set it down and not use for for 15+ minutes and it would be back to normal. The headset/remote is better than a google cardboard. But the app/game selection is not as good and the samsung gear vr. But may get there over time. There is very few apps/games available. I did see both netflix and hulu are on it but didn't try either one yet. The battery usage was less than 10 percent for the 30 minutes or so I used it for.
If google keeps pushing it. It will be a worthwhile purchase in 6 months to a year. But if you buy one now just expect a better google cardboard experience.
I agree, daydream app is very buggy due to heat issue. I used youtube app for vr and the phone was normal, but using youtube vr app inside daydream for 30 minute causes extreme heat that can burn your hands! I highly not reccommend using daydream app for now bc it could cause serious damage to the battery.
I have tried, I feel that it's zoomed in too much.
For example in netflix, I almoust don't see the the whole tv. But also in other apps some menus is partly outside the view.
I made a post about it on reddit in the daydream forum (not allowed to post links here, so you have to find it your self, title is "Daydream on Moto Z too zoomed in")
Yeah, the heat issue was very scary. I've never had a phone get that hot in such a short period. I didn't know if the hardware is just getting pushed too hard or its a software problem. I'm hoping for the latter.
And if/when google comes out with a new version of the daydream view headset. They need to make it not so much "one size fits all". I have a cheap plastic cardboard that was only 15 bucks and has better adjustments and fit than the daydream view. I could stand it with the cardboard since it was so cheap.
But I will say the controller is very good. But it needs a button or two on the bottom/top edge. Or games are going to be very basic and probably not catch on. Unless they add the option to use a second daydream controller. Then oculus rift/htc vive style games can be made for it.
Strange, I have upgraded to Nougat on my Moto Z bit the Daydream app is still "incompatible with my device". Anyone know what's going on?
Thanks
Ken
I have a daydream headset lying around. Used it 2-3 times on my z force and now it's gathering dust... Novelty at best. It did work well with the phone though. Only issue I found was the mask's strap was hard to adjust so it would stay put.
I have Moto z and daydream . It gets hot but have never gotten the overheat warning. Use it while wife sleeps with Bluetooth headphones to watch Netflix or Hulu . And ignore the guy who says it's too zoomed in. You can adjust it within each app. For Netflix just look up at the ceiling and a menu allows size adjust for screen , and to let you move the screen so you can lay on your back while watching . Can do similar on Hulu . I recommend opening the apps separate without going through Google daydream though maybe that's the heating issue. But yea I've used daydream app for 5 hours strait and my phone didn't over heat.
Did anyone tried to use it with a custom rom or are you all talking about stock experience?
rionline said:
Did anyone tried to use it with a custom rom or are you all talking about stock experience?
Click to expand...
Click to collapse
No one has any experience with custom roms and daydream?
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Kazz5 said:
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Click to expand...
Click to collapse
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
I read this reply via email before taking the time to come here and I just want to say thanks for such a thorough sharing of your experience and perspective! You made it clear to me that ordering a Shield was the right thing to do in my case. Interestingly, my Nexus 9 did the squeal/crash in another app soon after I posted this.
My Shield came in, upgraded painlessly, OTA, to 7.0.0 and seems to run much smoother than the Nexus 9 in every way. Yes, the screen is a bit smaller. But, frankly, I'm seeing less pixelation - I have to assume - due to the smaller screen size. The Shield runs cooler (I used to blow on the hot end of the Nexus 9 when holding it in my hands, in it's case, for longer periods of time) and the battery definitely lasts longer.
I will finish moving everything over to the Shield in the coming few days and make up my mind what I want to do with the Nexus 9. With it's large size and 4:3 aspect ratio, I may relegate it to electronic magazine reading - of which I have a few. I saw a reference to running some flavor of *nix on it. That could be interesting. A touch panel for security cameras is a thought, if do-able, as well. I'm sure more thoughts will come up, including getting a more stable Android installed on it.
Please keep me/us posted on your experiences with the Fire-Ice kernel! And thank you again!
GedBlake said:
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
Click to expand...
Click to collapse
I wanted to follow-up with you on an experience. I moved to the Shield K1 and have been using it since May. Something's happened with it's charging (I suspect the mini-USB port's connection as it seems to be a weak spot for many). In a pinch, to keep playing my game of choice, I picked up my Nexus 9 and gave it a full charge. I was thrilled since it was working so well. But once it hit 58% charge the weird screen and shrill shrieking returned. Now cornered, I did my best google-fu and uncovered a couple of threads that claimed I could fix my Nexus 9!
It seems many people were having success with removing the back panel (easy), gently prying a small, metal cover off of the battery's connection at the circuit board, unplugging the cable, cleaning connections with isopropyl alcohol, and re-assembling. I found a Youtube link (ifixit, I think?) there that showed how to disassemble the Nexus 9 and I was off! It seems some folks have had this clear up the problem for months and some have had it recur, fixing it again with the same procedure.
I've been using it for days in all states of charge with no return of the problem so far. It's given me plenty of time to get my warranty-replacement Shield enroute. The Shield is still much quicker. But I'm thrilled that there's not some odd gremlin with the Nexus 9. I knew I needed to track this post and your reply down in order to let you know. I hope it helps you and/or someone else!
And thanks again!
Just wanted to bump this thread as I am having the same problem with my N9 and it is steadily getting worse. When this problem first started, it would happen once every 2-3 weeks, usually when I was in Instagram. Now it is happening daily, or multiple times in a day, and sometimes it occurs right after reboot.
I have gotten frustrated enough that I am going to do a clean (reflash) of Pure Nexus, ElemX, etc and see if that has any effect.
Did you read my reply? Cleaning the connector to the battery has fixed my issues - which were constant - for weeks now!
I just got one of these Nexus 9 32GB giving to me by a family member as they upgraded to something else due to the issues with the Nexus 9 . It had the whole deal going on with the white pixelated screen freezing followed by a loud ear busting screeching noise at roughly 50% and 20% battery. I factory reset the tablet and cleaned the cache in recovery then popped back off the tablet and disconnected battery for a min or two, hooked it back up and it runs like butter so far for the last week through the whole cycle of the battery without freezing or screeching. Strange indeed but that fix works for whatever reason.
The way the bug works is that when playing on a poco f1, when you try to turn around or look around without using the dedicated shoot-whileturning buttom, the game decides to freeze for a short second before actually looking towards the desired direction. I do not knoe if this glitch is exclusive to the poco f1 however I have played on a Samsung S8 before and the bug does not seem to be present. Overall it makes the gane feel choppy despite the SD 845 processor I have. Just now its 1 question, is it solvable?
i play with a controller and don't have this problem... maybe it's touch-related?!?