Audio Latency - Nexus 7 Q&A, Help & Troubleshooting

could someone with a nexus 7 run some audio latency test, im planing on porting the pulse audio driver as it has been confirmed the nexus 7 uses linux alsa so the port will be fairly straight forward, it has been proven to provided better battery life (only marginally) and use less cpu. By taking fixing the re sampling between 48 k and 44k of the tegra 3.

Don't yet have the N7, but I've been running JellyBean on my Galaxy Nexus for 2 days, and can confirm the audio latency is MUCH lower than when it was running ICS. Before, when using synth/music apps with keyboards like Caustic2 there was noticable lag between the time I'd tap a synth key, and the sound would come out. The delay is gone now.

I can confirm that there is no perceptible delay.
http://www.youtube.com/watch?v=iRa-XES-31c

zaventh said:
I can confirm that there is no perceptible delay.
http://www.youtube.com/watch?v=iRa-XES-31c
Click to expand...
Click to collapse
I can still hear a delay. the goal is to have no (tap)(sound)
probably about 80ms lag

For those german readers:
http://www.androidnext.de/news/jelly-bean-google-geht-in-die-audio-offensive/
shortened:
ICS: >100ms
JB: 12ms
iOS: 5,8ms

zaventh said:
I can confirm that there is no perceptible delay.
http://www.youtube.com/watch?v=iRa-XES-31c
Click to expand...
Click to collapse
Thanks for the video, but that is definitely too latent to do any recording/studio work with. At least for me.
Sent from my HTC One X using xda premium

tylerwatt12 said:
I can still hear a delay. the goal is to have no (tap)(sound)
probably about 80ms lag
Click to expand...
Click to collapse
Technically that video is illustrating touch latency+app latency+audio latency+sample ramp-up

SilentMobius said:
Technically that video is illustrating touch latency+app latency+audio latency+sample ramp-up
Click to expand...
Click to collapse
Very cool. I't always good to see an 'engineering type' thinker. Hmm, wish the OP ( programmer ) would respond. Butter made it eight times quicker ? But I guess he's waiting for h/w like most of us are.

if its true that latency is 10- 12ms ( i presume thats app>audio out not audio in>audio out, not sure at this time) then that should be acceptable for playing instruments and real time monitoring for recording.
for Latency snobs, 12ms equates to the delay standing 12ft from the source - alternatively, i remember reading the original Hammond Organ, due to its electronics, had a latency of 13ms and people didn't get too upset!
good news as do hope to get some audio use from the nexus, but have to wait for worthwhile apps, ios miles ahead in that area at the mo.

The audio latency is 72ms according to Caustic. That's still pretty bad. It's definitely perceptible.
A user named Windows X created a mod for the Nexus S that lowered audio latency significantly (see here), and then vonVideo created a mod for the GSM Galaxy Nexus that brings it down to around 20ms (see here), perhaps someone could have similar success with the nexus 7.

Related

another disappointing device from htc?

Hi!
First of all, I buy 2 days ago a Touch HD (im getting this week), but all the more I read, my thinks are that HD is not a great device finally.
Pros
- Big screen
Cons
- GPS Lag (ultra important)
- Video doesnt play smooth (80 90%) on coreplayer and have lag
- Camera lag and bad quality photos.
- No [email protected] videos
- Lot of devices with dead pixels
So, why buy this device instead staying on a Diamond/pro or buying a X1? If I stay, I only lose a bigger screen that not cost 600€ for me (usb from the diamond have adapters to 3.5 minijack), and if you buy a X1, only lose the big screen but wins all of the cons of HTC devices plus more ram and better battery.
So, what are your reason to buy the Touch HD? Im thinking on cancel my order on monday.
yes, cancel your order and buy an iphone , this solve all probs about camera , recording , gps lag etcetc
kersh said:
Hi!
First of all, I buy 2 days ago a Touch HD (im getting this week), but all the more I read, my thinks are that HD is not a great device finally.
Pros
- Big screen
Click to expand...
Click to collapse
I doubt this ... because:
I am not sure that this big screen is effective enough. For watching movie and video, yes it is. However, for browsing the internet, without a doubt, you can see more content compare to 2.8" screen ... but is it directly readable without zooming? I dont think so ... Still nice though.
kersh said:
Cons
- GPS Lag (ultra important)
Click to expand...
Click to collapse
I dont think so, the first 2 owners from The Netherlands confirmed that the GPS Lag does not exist in this device.
But, again, no more report from other owner ...
kersh said:
- Video doesnt play smooth (80 90%) on coreplayer and have lag
Click to expand...
Click to collapse
I saw couple of examples from YouTube, I think it plays quite well. I dont see lag nor delay.
Oh yeah, it does not play 720p nor 1080p
kersh said:
- Camera lag and bad quality photos.
Click to expand...
Click to collapse
Agree, I think the camera still sux ... or worse (more shutter-lag because of the 5 MP?)
kersh said:
- No [email protected] videos
Click to expand...
Click to collapse
Which Windows Mobile phone can do that?
For sure, iPhone cant do that.
kersh said:
- Lot of devices with dead pixels
Click to expand...
Click to collapse
This is bad ... probably we need to start counting how many percent have dead pixel. Poll anyone?
kersh said:
So, why buy this device instead staying on a Diamond/pro or buying a X1?
Click to expand...
Click to collapse
Touch Diamond + Pro ---> GPS Lag
X1 ---> Slow performance???
kersh said:
If I stay, I only lose a bigger screen that not cost 600€ for me (usb from the diamond have adapters to 3.5 minijack), and if you buy a X1, only lose the big screen but wins all of the cons of HTC devices plus more ram and better battery.
So, what are your reason to buy the Touch HD? Im thinking on cancel my order on monday.
Click to expand...
Click to collapse
My reason? I dont know ... probably I will stick with my Kaiser ... and wait the next 3.8" WinMo ...
Or probably wait WinMo 6.5? Probably this can add some more functionalities.
Well right now i want a WinMo device and i want it with a 3.5mm audio jack, so that leaves me with two options:
X1 and Touch HD
Since X1 doesnt have an acclerometer (which WinMo7 is going to use heavily), has a recessed screen and TouchFlo doesnt play nice with it yet and since i can't use the keyboard fully in my language, i'd rather go with Touch HD's bigger screen.
GPS and camera aren't so crucial for me (for 3 years on my old nokia, i've used the camera ~10 times, haven't had a GPS and don't imagine i'll need it much (though its nice to have)).
Devices with dead pixels are covered by warranty, so that shouldnt be a problem.
And the only other argument you have is video doesnt play smooth, which isnt that good, since i plan on using it a lot, but when i asked here http://forum.xda-developers.com/showthread.php?t=443245 the guy says that non-AC3 movies from the net play ok and on one review, the reviewer was playing an ep of House on it and it looked OK to me, so i guess it'll do for me.
I am not sure that this big screen is effective enough. For watching movie and video, yes it is. However, for browsing the internet, without a doubt, you can see more content compare to 2.8" screen ... but is it directly readable without zooming? I dont think so ... Still nice though.
Click to expand...
Click to collapse
Actually it is. Played for 30 mins with one at a shop the other day and zoomed out everything was perfectly readable for me (though i'm young and don't use glasses, don't know about old folks (a lady at the Xperia forum returned it for that very reason)) the only thing that bugged me is that you can't click links directly from a zoomed out standpoint, first you have to zoom in, but that's Opera's fault, not Touch HD's. The guys at Opera should fix it
Which Windows Mobile phone can do that?
For sure, iPhone cant do that.
Click to expand...
Click to collapse
X1 can and it haa pretty much the same specs as Touch HD, except for the camera, maybe that's the problem.
Also Nokia N95
iPhone might as well not have a camera
its a nice phone but not the killer device it was hyped up to be, but i hope it will improve god willing when the developers have a go at it.
...Frankly speaking, you should have waited if you had been disappointed by the HTC devices in general. If you don't like to fiddle with your telephone, suffer for improvements, contribute to it and refresh your OS every week - then an HTC is probably not the better choice, many other companies make good telephones and similar sexy toys. The touch HD is, in my opinion, the most innovative personal platform which has appeared in the last years - it just misses Linux which will arrive soon...
i think that HTC telephones are a technology platform to have fun, like PCs 20 years ago.
If you were expecting an "out of the box" apple performances and finished ergonomics there is no need of investigating: i would suggest to cancel your order and buy an I***** (...oops, i cannot even write it....maybe an allergy? )
BTW, i have a touch HD already and i have been driving at least two hours with it and i continously hear about the GPS lag: WHICH GPS lag? If it is a 20 m lag, at which speed you drive?
Since there is a lot of speculation, shouldn't everybody clarify if they heard/read about a problem from internet, or they had/saw the problem themselves?
pzucchel said:
BTW, i have a touch HD already and i have been driving at least two hours with it and i continously hear about the GPS lag: WHICH GPS lag? If it is a 20 m lag, at which speed you drive?
Click to expand...
Click to collapse
What speeds do you drive at?
For the ones that say that I need and i****, I am not gonna buy and apple device in my life, but is frustrating seeing the same errors on every new device of HTC.
playbacks issues, gps lag, bad sound quality, etc etc
And the touch hd who can be the perfect model if they fix this, now is the same with a bigger screen, thats the problem, they sell the same again and again.
And the gps lag is not only 20 metters it is maybe more than 40 50 in some situations and the gps lag of the diamond have made me to skip a lot of detours and streets, it is a BIG issue.
gogol said:
I dont think so, the first 2 owners from The Netherlands confirmed that the GPS Lag does not exist in this device.
Click to expand...
Click to collapse
Others confirming that big gps lag exists, reviews included.
gogol said:
I saw couple of examples from YouTube, I think it plays quite well. I dont see lag nor delay.
Oh yeah, it does not play 720p nor 1080p
Click to expand...
Click to collapse
In youtube you cant see much, you need to use coreplayer benchmark or so and that have about 80%, that it is 20fps instead 25 on videos, so not smooth video playing
gogol said:
Which Windows Mobile phone can do that?
For sure, iPhone cant do that.
Click to expand...
Click to collapse
X1 can do and really great
gogol said:
Touch Diamond + Pro ---> GPS Lag
Click to expand...
Click to collapse
yes, same **** that hd touch, very important issue on latest htc's
gogol said:
X1 ---> Slow performance???
Click to expand...
Click to collapse
x1 slow performance? It have better performance, more ram, no video issues.
compared with the touch pro, the touch hd is a big improvment. Battery life seems increadable - with the same use the touvch pro would have died hours ago and i still have 50 % left!1 Gps sensitivity is as good as my old kaiser - the touch pro could never get a lock indoors.
Not sure what htc have done, but its all good.
Coreplayer says 80% so the video playback is bad?
...
lol
Ok.
TonyPlayer says 100.5%.
All these reports of crappy video playback are starting to worry me, that's one of the main reasons why i'm buying it...
Why do you use CorePlayer when WM6.1 comes with Windows Media Player ?
kersh said:
For the ones that say that I need and i****, I am not gonna buy and apple device in my life, but is frustrating seeing the same errors on every new device of HTC.
playbacks issues, gps lag, bad sound quality, etc etc
And the touch hd who can be the perfect model if they fix this, now is the same with a bigger screen, thats the problem, they sell the same again and again.
And the gps lag is not only 20 metters it is maybe more than 40 50 in some situations and the gps lag of the diamond have made me to skip a lot of detours and streets, it is a BIG issue.
Click to expand...
Click to collapse
Dear Kersh,
i don't understand what is real and what is speculation: which sound quality? which lag? which playback issues? which etc.etc.?
I have been driving with it on highways, city and walking my dog. I couldn't see any lag. If the diamond had a lag (i don't know) you should not extrapolate that the touch HD behaves in the same way. Please let me know of a conclusive and quantitative test you'd like to see and I'll try it out.
I have one and i am very happy. At the same time, software improvements on such a machine can make it improve even further and extend the satisfaction of owners for years. In my opinion, this device offers the best performances which are available on the market today.
My old trinity improved a lot with time - thanks to the people here trying hard to improve these devices!
By the way, I don't believe that Iphones are bad at all - simply they are like Apple PC: good for my mother and my wife - but i want to be at the frontline and contribute to it.
All the Best,
Let's make it clear iGO v8.3.1.57021 corrects the lag ! and many more improvments
pzucchel said:
Dear Kersh,
i don't understand what is real and what is speculation: which sound quality? which lag? which playback issues? which etc.etc.?
I have been driving with it on highways, city and walking my dog. I couldn't see any lag. If the diamond had a lag (i don't know) you should not extrapolate that the touch HD behaves in the same way. Please let me know of a conclusive and quantitative test you'd like to see and I'll try it out.
I have one and i am very happy. At the same time, software improvements on such a machine can make it improve even further and extend the satisfaction of owners for years. In my opinion, this device offers the best performances which are available on the market today.
My old trinity improved a lot with time - thanks to the people here trying hard to improve these devices!
By the way, I don't believe that Iphones are bad at all - simply they are like Apple PC: good for my mother and my wife - but i want to be at the frontline and contribute to it.
All the Best,
Click to expand...
Click to collapse
Dear pzucchel,
as u mentioned in the second paragraph,would u be kind enough to do some simple test for the gps lag issue.can u drive at a speed of 80 to 100 km/h,when you physically reach a junction or an interchange ,where is the current location(i.e car icon or triangle) of your device showing? if its exactly parallel to the junction or interchange,than there is no lag..the difference between your physical location and your device location is the actual lag.Another simple test is when your car has physically turn into a junction,how long would the device take to show you are now driving on a new road and direction.and if you could be kind enough to specify what navigation program you used for the test..that will be wonderful.
Thanks in advance for your help
I've been looking forward to the touch hd for a bit now, and I still plan to get it. If there is anything i have learnt from these forums is how a lot of problems is software based.
Anyway, one main reason i'm getting it is that chance to have android on it when it gets ported on.
kersh said:
Others confirming that big gps lag exists, reviews included.
Click to expand...
Click to collapse
It depends on the software you use.
I have tried Garmin XT and iGO 8.3.1 on my HTC Trinity.
The Garmin was always a little bit behind, where iGO was always on spot!
And guess what:
I have tried both on my Touch HD, and have exactly the same findings!
I too like Android OS on the cell phone. I have been trying to tolerate the Sammy i760 I am now using, but the HD and the Omnia 16gb both look good. I also am thinking of the Invidia Tegra 600 series as it WILL play at 30fps. Would this be the "one" to wait for? or is it in something and I don't know due to all the Dr's I have to see and travel too? Thanks, JASTECH
NVIDIA Tegra 650 also features:
• All-day media processing, for 130 hours audio, 30 hours HD video playback
• HD image processing for advanced digital still camera and HD camcorder functions
• Optimized hardware support for Web 2.0 applications for a true desktop-class internet
experience
• Display support for 1080p HDMI, WSXGA+ LCD and CRT, and NTSC/PAL TV-Out
• Direct support for WiFi, disk drives, keyboard, mouse, and other peripherals
Tegra 650
* Processor and Memory Subsystem
o ARM11 MPCore @ 800 MHz
o 16/32-bit LP-DDR
o NAND Flash support
* HD AVP (High Definition Audio Video Processor)
o 1080p H.264 decode
o 720p H.264 encode
o Supports multi-standard audio formats, including AAC, AMR, WMA, and MP3
o JPEG encode and decode acceleration
* ULP GeForce
o OpenGL ES 2.0
o Programmable pixel shader
o Programmable vertex and lighting
o Advanced 3D/2D graphics
* Imaging
o Up to 12 megapixel camera sensor support
o Integrated ISP
o Advanced imaging features
* Display Subsystem
o True dual-display support
o Maximum display resolutions supported:
+ 1080p (1920x1080) HDMI 1.3
+ WSXGA+ (1680x1050) LCD
+ SXGA (1280x1024) CRT
+ NTSC/PAL TV output

Reply from Keith Nowak about the 30FPS issue

About a week ago, I sent an email to all the HTC brass inquiring about the 30FPS cap that most of us are familiar with. An hour later, I received a "canned response", from one of their customer service reps assuring me that this was done "on purpose" to maximize battery life as well as enhance the user experience.
Story short, Keith Nowak, presumably a high ranking HTC exec, sent me back an email with a lengthy explanation of why the cap was in place. I was originally going to write a story about it for the blog I work for, however, it just doesn't seem worth it now since the information he's given me is basically the same thing that some of us have speculated. Interestingly enough however, he did retract the battery saving and user experience comments that I was first given.
Anyways, check it out:
Hi Adam-
My apologies for the delay in responding, we were investigating this issue, and I wanted to be sure I understood all of the facts before I responded.
Regarding the 30 FPS limitation on the HTC EVO 4G. This is simply a limitation of the hardware used in the device. The HDMI output that delivers HD content is, as you would expect, very resource intense, and as such, puts a limit on the output that can be used for the main display. However, even though there is a 30 FPS limitation, this is roughly equivalent to what most video content (TV and movies) is filmed in (24-30 FPS), meaning that in the vast majority of cases, this is not going to pose any issues for end users.
We have seen reports of a hack that purports to “fix” this, but after investigation, it turns out that this hack is simply allowing data to be pushed through the display interface at a higher speed than it can reasonably handle – resulting in, as you would expect, a choppy, unacceptable image of very poor quality.
I am not sure where information regarding “enhancing the user experience” or “maximize battery life” – but if it came from HTC, please let me know, and we will address the issue, as this is not correct information.
Best-
Keith Nowak
HTC
infamousjax said:
Hi Adam-
My apologies for the delay in responding, we were investigating this issue, and I wanted to be sure I understood all of the facts before I responded.
Regarding the 30 FPS limitation on the HTC EVO 4G. This is simply a limitation of the hardware used in the device. The HDMI output that delivers HD content is, as you would expect, very resource intense, and as such, puts a limit on the output that can be used for the main display. However, even though there is a 30 FPS limitation, this is roughly equivalent to what most video content (TV and movies) is filmed in (24-30 FPS), meaning that in the vast majority of cases, this is not going to pose any issues for end users.
We have seen reports of a hack that purports to “fix” this, but after investigation, it turns out that this hack is simply allowing data to be pushed through the display interface at a higher speed than it can reasonably handle – resulting in, as you would expect, a choppy, unacceptable image of very poor quality.
I am not sure where information regarding “enhancing the user experience” or “maximize battery life” – but if it came from HTC, please let me know, and we will address the issue, as this is not correct information.
Best-
Keith Nowak
HTC
Click to expand...
Click to collapse
That is a downright lie. It is something he is simple overemphasizing about vsync issues with the Epson panel, which will be fixed because the devs here are hard at work.
Sure, it is a dirty hack, but the current method works fine. Completely, smooth and superb 'image quality,' and it makes it LESS choppy.
Hmm, they should just release all their sorce code so the devs here can tear it apart.
..yeahhh..i'm not one to be quick to call bs, but come on! I'm running ffolkes Novatek kernel on Fresh 0.5.3 and again, maybe it is just some "hack"..but bottom line is the difference is night and day! The response time is outta this world!
Sounds to me like he has no tech background, and that response was something that he was told to say. I wouldn't imagine at his position he would know the insides of phones and how they work or can be manipulated.
OP, you should reply back asking why use/waste all the resources on a feature that won't be used on a daily basis (maybe once or twice a month, if at all).
OP, if you do reply back. Consider including a link to this video:
http://www.youtube.com/watch?v=cAjTo602sQM
That is nothing but improvement in display quality right there.
Video is from this thread: http://forum.xda-developers.com/showthread.php?t=713311
infamousjax said:
We have seen reports of a hack that purports to “fix” this, but after investigation, it turns out that this hack is simply allowing data to be pushed through the display interface at a higher speed than it can reasonably handle – resulting in, as you would expect, a choppy, unacceptable image of very poor quality.
Click to expand...
Click to collapse
Bull****. I made the video proving it: http://www.youtube.com/watch?v=cAjTo602sQM
Tell Keith to salvage his credibility he needs to produce an honest answer. Ask him if he wants to see my run Youtube, or an mp4 video, or anything else, to drop me a line. I'll be happy to continue demonstrating how wrong he is.
The topic on HTC's forum is on page 10. Let's make sure it stays on the front page so support realizes it's a huge customer issue.
http://community.htc.com/na/htc-forums/android/f/94/t/3186.aspx
c'mon, lets not start grilling and roasting htc execs. These people are trying to help us and have been very informative on assisting us with this NEW device.
chances are, like said above, he probably forwarded the email directly to the engineering department (probably to someone we cant directly connect with) and got this answer.
i say, to knock it off with all the pushing and shoving of the FPS issue, and lets not end up on their bad side. Theyve been doing a great job so far. If the devs simplify and figure out a better way for us to maximize FPS, then so be it... Its not worth calling people liars and dishonesty.
This makes me sad:
http://www.youtube.com/watch?v=ilx_cpGZczM
TorxT3D said:
c'mon, lets not start grilling and roasting htc execs. These people are trying to help us and have been very informative on assisting us with this NEW device.
chances are, like said above, he probably forwarded the email directly to the engineering department (probably to someone we cant directly connect with) and got this answer.
i say, to knock it off with all the pushing and shoving of the FPS issue, and lets not end up on their bad side. Theyve been doing a great job so far. If the devs simplify and figure out a better way for us to maximize FPS, then so be it... Its not worth calling people liars and dishonesty.
Click to expand...
Click to collapse
Really? Are you being serious? They are trying to help us, how? First, according to them, they are tying up all the resources due to HDMI, which may be a great feature, but is not going to be used by many at all. Second, yeah, they have been doing a great job so far, RIGHT. I guess that's why the Evo had the light leaks, screen separations, other issues as well with the phone so far like bad wifi signal and poor battery.
If they really want to help, they would have released the source code already.
KERKEDAGAIN said:
..yeahhh..i'm not one to be quick to call bs, but come on! I'm running ffolkes Novatek kernel on Fresh 0.5.3 and again, maybe it is just some "hack"..but bottom line is the difference is night and day! The response time is outta this world!
Click to expand...
Click to collapse
where can i get this "hacked" kernel from and will it kill the camera ?
The last HTC rep I spoke to has assured me that they're working on a fix for the 30FPS cap.
TorxT3D said:
c'mon, lets not start grilling and roasting htc execs. These people are trying to help us and have been very informative on assisting us with this NEW device.
chances are, like said above, he probably forwarded the email directly to the engineering department (probably to someone we cant directly connect with) and got this answer.
i say, to knock it off with all the pushing and shoving of the FPS issue, and lets not end up on their bad side. Theyve been doing a great job so far. If the devs simplify and figure out a better way for us to maximize FPS, then so be it... Its not worth calling people liars and dishonesty.
Click to expand...
Click to collapse
+1
I am all for better FPS - but even with 30 fps can you honestly tell me you can tell the gears moving better? I can't tell. I have tried both. I went back to another ROM and its not enabled. I can't tell. I get smooth movement. I am not overclocked and my quadrant on 2.1 with no JIT, etc. is around 590.
I get 30fps on gears and 25.1FPS on NeoCore but without seeing those numbers I could not tell the difference between the two in regards to better frames. I have ran both. The only difference for me is the Froyo 2.2 EVOA which is smoother in screen transitions and can multi-task much better in regards to updating and installing severals apps at a time. Otherwise video has yet to create a margin that is noticeable to me.
It has nothing to do with gears moving faster and if you had applied the 30 fps breaking kernel you would see that everything in the os is snappier including scrolling, touch lag etc..
you could just try to play a simple game like doodle jump and you'll notice the difference immediately
jblazea50 said:
you could just try to play a simple game like doodle jump and you'll notice the difference immediately
Click to expand...
Click to collapse
Works just fine on the new OTA...
jblazea50 said:
If they really want to help, they would have released the source code already.
Click to expand...
Click to collapse
Seriously. We need to just stop asking for a 30FPS cap fix and just keep asking for the source code because honestly, with the source code the devs could just fix most, if not all of this crap already.
jblazea50 said:
you could just try to play a simple game like doodle jump and you'll notice the difference immediately
Click to expand...
Click to collapse
I do - I enjoy that game for a while now. I have it loaded on every ROM along with Robo Defense.
What is the BIG difference?
I notice little things about everything so when improvement is made I make comments. But there hasn't been much improvement in that area.
The camera much snappier and the pictures are much better in daylight. I took some great pictures to test at High Resolution and I am impressed with the camera. Before it was just so-so but now some of the pictures of the same images are greatly improved upon for sharpness and color saturation.
See so I do notice differences - perhaps not in the FPS but in other things

Tegra 3 not so great as they would make us believe

iPad 2 beating it on every front. ICS may fix this but we will have to wait and see on that front.
http://www.anandtech.com/show/5163/asus-eee-pad-transformer-prime-nvidia-tegra-3-review/3
and from a 'somewhat' biased site.
http://semiaccurate.com/2011/11/09/tegra-3-missed-performance-goals-by-wide-margins/
http://semiaccurate.com/2011/04/06/nvidia-in-full-philosophical-retreat-for-tegra-3/
http://semiaccurate.com/2011/10/19/nvidia-tegra-roadmap-slips-a-year/
http://semiaccurate.com/2011/08/04/a-look-at-tegra-3-3-3-and-4/
Bahahahahahahahahaha
ipad2 not so great as they would make us believe ......
Sent from my DROID X2 using Tapatalk
My phone has a single-core processor and my tablet has a dual-core. That's pretty damn good. If I NEED computing power, I have my quad-core i7 rocking, 8 GB puffing, ATI HD5870 running laptop that can do just about anything.
Let me know when Android can run a fully-featured version of Photoshop or something better than iMovie, I'll happy jump onboard the X-core bandwagon. I might even leave Windows behind then...
Let me ask simple question. How did they come up with those numbers? No, it is not a stupid question. Did they use an app to come up with those numbers? Did they hook the devices up to some kind of machine and then did measurements? What did they use?
The point I'm trying to make is since iOS and android are different platforms, if they used an app to do these measurements, they'd have to use 2 completely different apps for 2 completely different platforms. Apple has been exposed to fabricate their signal strength and battery bars count. Their OS also don't show error messages when something crashes. How do we know they didn't fabricate these numbers as well?
goodintentions said:
Let me ask simple question. How did they come up with those numbers? No, it is not a stupid question. Did they use an app to come up with those numbers? Did they hook the devices up to some kind of machine and then did measurements? What did they use?
The point I'm trying to make is since iOS and android are different platforms, if they used an app to do these measurements, they'd have to use 2 completely different apps for 2 completely different platforms. Apple has been exposed to fabricate their signal strength and battery bars count. Their OS also don't show error messages when something crashes. How do we know they didn't fabricate these numbers as well?
Click to expand...
Click to collapse
The software they used is right there...GLBenchmarks and Basemark. It's exactly the same as testing your frame rates for video games that are made for different platforms, ie. Windows and OSX. The games themselves have their own engines that can show you what frame rates you're running at so why should it be any different between Honeycomb and IOS.
It's the same software...
I do remember Apple fabricating their signal bars, but not their battery life. Unlike a certain website, *cough*ENGADGET*cough*, Anandtech is a reputable tech site that is more unbiased than others.
The reasons I can believe it is true?
My iPad 2 plays EVERY single video it can play (no flash of course) without fail. My Transformer? Sometimes (more often than not) it doesn't even play 360P Youtube videos without stuttering. Pathetic if you ask me.
stuckonduhmode said:
My iPad 2 plays EVERY single video it can play (no flash of course) without fail. My Transformer? Sometimes (more often than not) it doesn't even play 360P Youtube videos without stuttering. Pathetic if you ask me.
Click to expand...
Click to collapse
If your Transformer can't play SD YouTube videos, you have a setup problem of some kind. Mine doesn't stutter at all, even on HD YouTube videos. It likewise doesn't stutter at all on high bitrate transfers of my own DVDs, which are well above the resolution and bitrate of SD YouTube vids.
Also note that Anandtech themselves clearly noted that they had problems with their initial test unit, as evidenced by the increase in wifi performance and battery life with their second unit. Until they've had time to rerun all their tests, I wouldn't put much weight in any of their original numbers.
My Transformer struggles with 720p @ High profile. How does the iPad 2 fare?
deadman3000 said:
My Transformer struggles with 720p @ High profile. How does the iPad 2 fare?
Click to expand...
Click to collapse
correct me if I'm wrong..don't think iPad can handle 720p/1080p High profile either
magicpork said:
correct me if I'm wrong..don't think iPad can handle 720p/1080p High profile either
Click to expand...
Click to collapse
iPad2 plays high profile 720p smoothly (B-Frames, cabac, etc). Not with the native player, but with appstore players like AVPlayerHD.
GT 10.1 and other Tegra 2 do, too, with market players like Dice and BS but they stutter on fast action scenes. iPad2 doesn't do that. I did oc my GT 10.1 and set cpu to Interactive and that gets rid of the stutter, but for my particular 10.1 Interactive leaves the tab unstable.
Never tried 1080p high profile on iPad2.
deadman3000 said:
My Transformer struggles with 720p @ High profile. How does the iPad 2 fare?
Click to expand...
Click to collapse
If your struggling playng video, give BSplayer a try ... i tried dice player (as recommended) and NOTHING plays video better than BSplayer
Funny as I have been doing my own research on getting a tegra 3 or Ipad 2 or just nothing. YouTube videos work great for me. I have problems with ESPN videos on Tegra 2 compared to the OG Ipad. For the stutter, I like the close to 200.00, savings compared to the ipad.
Sent from my Transformer TF101 using Tapatalk
i sell and ipad2 before buying transformer.in video playing ipad2 is a bit more fluid,but at high profile 720p it is the same as tf,depend on which software you use for,but 100% lag free video you haven't with ipad2 and you haven't also with transformer.i suppose that tegra 3 chip with neon support included is more powerfull and generate more smooth and fluid videos than ipad2.personally i think that video playing is the only thing where tegra2 might be not exceeding,but not from an ipad2 chip but at least a tegra 3\exynos or newest qualcomm soc (with NEON as well)
correct me if i'm wrong mates...
Lack of NEON is the biggest let down of Tegera 2 IMHO. Reminds me of one of my friends with an aging AMD that had the clockrate but couldn't thunderbird on without newer instruction set extensions some games needed.
Sent from my Transformer TF101 using Tapatalk
goodintentions said:
Let me ask simple question. How did they come up with those numbers? No, it is not a stupid question. Did they use an app to come up with those numbers? Did they hook the devices up to some kind of machine and then did measurements? What did they use?
The point I'm trying to make is since iOS and android are different platforms, if they used an app to do these measurements, they'd have to use 2 completely different apps for 2 completely different platforms. Apple has been exposed to fabricate their signal strength and battery bars count. Their OS also don't show error messages when something crashes. How do we know they didn't fabricate these numbers as well?
Click to expand...
Click to collapse
+1
+1
+1
Sent from my DROID X2 using Tapatalk
colonel187 said:
goodintentions said:
Let me ask simple question. How did they come up with those numbers? No, it is not a stupid question. Did they use an app to come up with those numbers? Did they hook the devices up to some kind of machine and then did measurements? What did they use?
The point I'm trying to make is since iOS and android are different platforms, if they used an app to do these measurements, they'd have to use 2 completely different apps for 2 completely different platforms. Apple has been exposed to fabricate their signal strength and battery bars count. Their OS also don't show error messages when something crashes. How do we know they didn't fabricate these numbers as well?
Click to expand...
Click to collapse
+1
+1
+1
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
It doesn't matter which software/platform. The software just measure how many fps at 720p the tablet can display. I think it's a fair comparison.
Does it matter in normal usage? i don't know. But it shows that the iPad2 GPU is better than the tegra 3 in this case.
deadman3000 said:
iPad 2 beating it on every front. ICS may fix this but we will have to wait and see on that front.
http://www.anandtech.com/show/5163/asus-eee-pad-transformer-prime-nvidia-tegra-3-review/3
and from a 'somewhat' biased site.
http://semiaccurate.com/2011/11/09/tegra-3-missed-performance-goals-by-wide-margins/
http://semiaccurate.com/2011/04/06/nvidia-in-full-philosophical-retreat-for-tegra-3/
http://semiaccurate.com/2011/10/19/nvidia-tegra-roadmap-slips-a-year/
http://semiaccurate.com/2011/08/04/a-look-at-tegra-3-3-3-and-4/
Click to expand...
Click to collapse
Dont forget Honeycomb is software rendering, ICS has hardware rendering (like the iPad).
Spidey01 said:
Lack of NEON is the biggest let down of Tegera 2 IMHO. Reminds me of one of my friends with an aging AMD that had the clockrate but couldn't thunderbird on without newer instruction set extensions some games needed.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Thisthisthis. Most of your media playback issues? This is the reason. Except for the "SD YOUTUBE LAGS OMG SO PATHETIC" guy, which either has terrible internet or is doing something very, very wrong. My TF plays back high prof 720p no problem with Dice. If tegra2 had NEON, we'd have 1080p30f.
tekkitan said:
Dont forget Honeycomb is software rendering, ICS has hardware rendering (like the iPad).
Click to expand...
Click to collapse
That kinda has nothing to do with this...
Sent from my Transformer TF101
deadman3000 said:
iPad 2 beating it on every front. ICS may fix this but we will have to wait and see on that front.
http://www.anandtech.com/show/5163/asus-eee-pad-transformer-prime-nvidia-tegra-3-review/3
and from a 'somewhat' biased site.
http://semiaccurate.com/2011/11/09/tegra-3-missed-performance-goals-by-wide-margins/
http://semiaccurate.com/2011/04/06/nvidia-in-full-philosophical-retreat-for-tegra-3/
http://semiaccurate.com/2011/10/19/nvidia-tegra-roadmap-slips-a-year/
http://semiaccurate.com/2011/08/04/a-look-at-tegra-3-3-3-and-4/
Click to expand...
Click to collapse
Uhm, I like Charlie. I really do.
But sadly, as far as his Tegra stories are concerned, he seems to live in parallel (or maybe even perpendicular) universe.
Tegra2 he ridiculed so much and went as far as to claim that it will not get a single design win ended up cornering ENTIRE goddamn tablet market. Pretty much 100% of Honeycomb devices run on T2 (whether we like it or not).
Same with his "sky is falling, Tegra roadmap slips for a whole year". Well, the roadmap might have slipped (or was that just dumb marketing projections, not the roadmap itself), but the second part of the story is that even after slip, nvidia is still a whole year ahead compared to competition (4 core Kraits are scheduled market introduction Q4Y12).
---------- Post added at 01:21 PM ---------- Previous post was at 01:11 PM ----------
Danny-B- said:
If your struggling playng video, give BSplayer a try ... i tried dice player (as recommended) and NOTHING plays video better than BSplayer
Click to expand...
Click to collapse
Both (newest BSplayer, before ovt'11 release, it didn't even have ahardware acceleration) players are still not prefect and drop frames on panning or action scenes.
They also have bunch of non-performance issues:
-DICE player cannot playback 90% of embedded subs (and for those it can read, it will start showing them only after 30 seconds of movie have passed) out there and has ugly, undocumented GUI.
BSplayer suffers from nasty subtitle desyncing issue and its seeking implementation is utterly dysfunctional (you can only seek in random 15-30 secs jumps)
Oh, and both players suffer performance hit when streaming via SMB.
So yeah, for media consumption device(with 399-499 pricetag!; You could buy two netbooks for that money), Tegra2 tablets ****ing suck.
Of course what the Anadtech seem to conveniently "forget" is that the Transofmers display is much higher resolution than the iPad2 and therefore more pixels to populate...
Perhaps I should make a iPad2 killer tablet that 120 pixels x 120 pixels that downscales 720p video at can play at insane framerates but looks ****. I'm sure the idiots at Anadtech would love it...
CrazyPeter said:
Of course what the Anadtech seem to conveniently "forget" is that the Transofmers display is much higher resolution than the iPad2 and therefore more pixels to populate...
Perhaps I should make a iPad2 killer tablet that 120 pixels x 120 pixels that downscales 720p video at can play at insane framerates but looks ****. I'm sure the idiots at Anadtech would love it...
Click to expand...
Click to collapse
Afaik both ipad and TF simply upscale the games.

Audio Latency with all Emulators

Hi guys,
I received my Shield this week, I bought it only for RetroGaming. For this reason I already have some android consoles like JXD S7300, Xperia Play, iDroidX360 and Archos Gamepad, I'm looking for the perfect emulation on a portable console .
First thing, the Screen of the Shield is just Excellent ! And controls are top !
But as I feared with some comments, this console has a noticeable audio latency with all emulators...
I tested all emulators (retroarch include) and all have a noticeable audio latency. I compared with my JXD S7300, and the audio latency is unnoticeable on it.
With the .EMU SUITE like Snes9X EX+, NES.EMU etc. I can set the Sound Buffer to reduce the audio latency, but if I set this parameter as minimum I have many sound cracking with frameskip=0 (for constant 60fps), sound cracking I don't have on my 7300 (I tried to overclock and fix the CPU Frequency at maximum with SetCpu and set to Performance, but same thing, even with the 2.55Ghz Kernel).
For the same audio latency as my 7300 I need to set the Sound Buffer at 3 on my Shield and 10 on my 7300, if I set 3 on my 7300 impossible to see any audio latency, on the shield, with the Sound Buffer at 3 I still notice an audio latency...
So my question is, have you an idea of what is the problem on the Shield and if we can resolve it by a custom fix or other if Nvidia won't ? Also a setting on RetroArch to reduce the audio latency.
Thanks for your help.
PS: sorry for my English, I'm French
NgXAlex said:
PS: sorry for my English, I'm French
Click to expand...
Click to collapse
I can't help the audio issues, sorry. But don't worry about your english, its better than alot of actual english people (a lot of morons here).
SixSixSevenSeven said:
I can't help the audio issues, sorry. But don't worry about your english, its better than alot of actual english people (a lot of morons here).
Click to expand...
Click to collapse
:victory: Thanks.
NgXAlex said:
Hi guys,
I received my Shield this week, I bought it only for RetroGaming. For this reason I already have some android consoles like JXD S7300, Xperia Play, iDroidX360 and Archos Gamepad, I'm looking for the perfect emulation on a portable console .
First thing, the Screen of the Shield is just Excellent ! And controls are top !
But as I feared with some comments, this console has a noticeable audio latency on all emulators...
I tested all emulators (retroarch include) and all have a noticeable audio latency, so I compared with my JXD S7300, and the audio latency is unnoticeable on it.
With the .EMU SUITE like Snes9X EX+, NES.EMU etc. I can set the Sound Buffer to reduce the audio latency, but if I set the parameter as minimum I have many sound cracking with frameskip=0 (for constant 60fps), sound cracking I don't have on my 7300 (I tried to overclock and fix the CPU Frequency at maximum with SetCpu and set to Performance, but same thing, even with the 2.55Ghz Kernel).
For the same audio latency as my 7300 I need to set the Sound Buffer at 3 on my Shield and 10 on my 7300, if I set 3 on my 7300 impossible to see any audio latency, on the shield, with the Sound Buffer at 3 I still notice an audio latency...
So my question is, have you an idea of what is the problem on the Shield and if we can resolve it by a custom fix or other if Nvidia won't ? Also a setting on RetroArch to reduce the audio latency.
Thanks for your help.
PS: sorry for my English, I'm French
Click to expand...
Click to collapse
same here....
main reason i bought the SHIELD was for retro gaming, but i have the same audio issues as your having.
i never had these issues on my Xperia Play or SGSIII.
this combined with the weird D-Pad sensitivity (it seems to act more like a analog stick and i have input errors all the time) has me wondering if i should sell this thing on ebay... as it just frustrating to play right now. ive honestly havent played on it in a week and went back to playing on my DSlite.
Yep, me too, if Nvidia in the future won't release a fix and if we can't find a way to fix this issue I think I'll sell my Shield (easy in France lol) for a Wikipad 7 or the new JXD S7800 because I only want use this console for RetroGaming, so if I can't because a sound issue, no way for me...
At this moment I prefer use my PS Vita (with VHBL) for GBC, GG, SMS and Genesis roms because the emulation is very good without any audio lag and the screen is almost as good as the Shield screen.
It is my hope that some of the problems are because the tegra 4 is new and some optimizations will help improve the situations a little bit.
As for the d-pad I found after wearing it in a little bit through playing lots of games it's improved a little bit. It's still not perfect but I barely notice the awkward sensitivity that used to plague me when trying to run and slide in games like Mario lol
HobsonA said:
It is my hope that some of the problems are because the tegra 4 is new and some optimizations will help improve the situations a little bit.
As for the d-pad I found after wearing it in a little bit through playing lots of games it's improved a little bit. It's still not perfect but I barely notice the awkward sensitivity that used to plague me when trying to run and slide in games like Mario lol
Click to expand...
Click to collapse
i hope so too. i really do love this thing. i know its basically still in "BETA", but between the 64gb SD card issues, audio lag and the D-pad im regretting the $300 i spent on this right now...
i feel by the time most of this stuff is fixed there might be another price drop...
ahhh.... the life of a tech addict.... :silly:
FWIW I haven't had any audio latency issues with PCSX in Retroarch.
Android 4.3 had some significant audio latency issues resolved (there's a Google I/O talk on it) so that may take care of your issue when that OTA comes.
Hi guys, I installed Caustic 2 on my shield, it gives a very good idea for audio latency.
Go to the menu and result of latency for the Shield: 128ms ! Horrible lol
My JXD S7300 has 86ms, and the audio latency is unnoticeable, above 100ms it's noticeable.
Some owner of the Nexus 7 with android 4.3 also measured = 40ms.
And on my Xperia Play with old android 2.3.4 only 55ms !
But 128ms for the shield is just too high for a 300$ device...
EDIT: A Wikipad owner told me he has only 47ms ! It's great, and the Wikipad has android 4.1.1, so it's possible even without android 4.3.
NgXAlex said:
Hi guys, I installed Caustic 2 on my shield, it gives a very good idea for audio latency.
Go to the menu and result of latency for the Shield: 128ms ! Horrible lol
My JXD S7300 has 86ms, and the audio latency is unnoticeable, above 100ms it's noticeable.
Some owner of the Nexus 7 with android 4.3 also measured = 40ms.
And on my Xperia Play with old android 2.3.4 only 55ms !
But 128ms for the shield is just intolerable for a 300$ device...
EDIT: A Wikipad owner told me he has only 47ms ! It's great, and the Wikipad has android 4.1.1, so it's possible even without android 4.3.
Click to expand...
Click to collapse
Post your findings on the official Shield forums, NVidia need to fix this.
SixSixSevenSeven said:
Post your findings on the official Shield forums, NVidia need to fix this.
Click to expand...
Click to collapse
I posted many times on Geforce Forum lol
SixSixSevenSeven said:
I can't help the audio issues, sorry. But don't worry about your english, its better than alot of actual english people (a lot of morons here).
Click to expand...
Click to collapse
I resemble that remark.

The source of the problems is likely the Tegra processor.

As someone who has been hunting for a good Android tablet for months now, I read a LOT of forums and user-reviews. One thing that I've noticed time and time again is that devices that are powered with Nvidia's Tegra processors have an unusually large amount of unhappy users, and the complaints are more or less the same.
- Poor wifi strength/speed
- Touch screen input problems
- Random shutdowns/reboots
- UI Lag
- Device heating up when doing things that are not traditionally intensive tasks.
It's not a Marshmallow (or even Android) problem guys. The combination of some/all of the above problems is comparatively unheard of on Exynos and Snapdragon powered devices. I'm not an engineer so I don't know whether it's a problem innate to the hardware or poor driver support or something else, but I'm enough of an Android fan to have seen a really obvious pattern emerging when looking to buy a device and comparing reviews. I've personally experienced these problems on the Nvidia Shield Tablet K1 and there's a whole giant army of unsatisfied Nexus 9 users out there, and now the Pixel C is sounding like a similar story. You'll recall similar stories about the Nexus 7 2012 as well.
I really wish Google would have waited a little longer and used a next-gen Snapdragon chip in this tablet, it would have been great.
Most of those issues would make sense because of poor software that doesn't utilize the Chipset properly. Not because of the CPU/GPU itself.
It would make sense if you were blaming the touchscreen controller and wifi chipset itself.
I myself have few issues with my Pixel C, and the issues I do have are across all my android devices.
All this speculation about the issues of this device are unnecessary. If you have the device then report your issues to Google for the benefit of all.
Sent from my iPhone using Tapatalk
sleepinlight said:
As someone who has been hunting for a good Android tablet for months now, I read a LOT of forums and user-reviews. One thing that I've noticed time and time again is that devices that are powered with Nvidia's Tegra processors have an unusually large amount of unhappy users, and the complaints are more or less the same.
- Poor wifi strength/speed
- Touch screen input problems
- Random shutdowns/reboots
- UI Lag
- Device heating up when doing things that are not traditionally intensive tasks.
It's not a Marshmallow (or even Android) problem guys. The combination of some/all of the above problems is comparatively unheard of on Exynos and Snapdragon powered devices. I'm not an engineer so I don't know whether it's a problem innate to the hardware or poor driver support or something else, but I'm enough of an Android fan to have seen a really obvious pattern emerging when looking to buy a device and comparing reviews. I've personally experienced these problems on the Nvidia Shield Tablet K1 and there's a whole giant army of unsatisfied Nexus 9 users out there, and now the Pixel C is sounding like a similar story. You'll recall similar stories about the Nexus 7 2012 as well.
I really wish Google would have waited a little longer and used a next-gen Snapdragon chip in this tablet, it would have been great.
Click to expand...
Click to collapse
thing is the nvidia tv device does not have the big lines of problems and it is the device closest to pixel c.. i'd guess the magnets are a source of havoc.
I did some digging today in open source repos - all the below are just assumptions, I don't want to be a smartass.
If issues seem to be hardware related, usually it's the kernel, not the actual HW. One thing is sure, Google/Nvidia guys are working hard to get things right.
Some examples:
There are even separate branches in the Chomium kernel repos to stabilize the Pixel C: https://chromium.googlesource.com/chromiumos/third_party/kernel/+refs - search for "stabilize-smaug" here.
This is almost surely the fix for the repeated key issues of the keyboard (was merged in mid-December): https://chromium.googlesource.com/chromiumos/third_party/kernel/+/5e09b5b68e2a09257cad69870989b7977797f09c
If you search for "touch" on the Chromium gerrit, there are literally dozens of fixes, most of them already merged. One that I think is related to the Pixel C, and might be a key one: https://chromium-review.googlesource.com/#/c/320202/
I've also found a change related to the Pixel C that is still under review, Nvidia guys were talking about a deadline of next Thursday (14th January), until they need to fix something: https://chromium-review.googlesource.com/#/c/314327/ - scroll down to the comments.
So, let's hope we'll receive an update by the end of the month. The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.
PS: This is a bit unrelated, but I've found out from the device tree that the Keyboard firmware can be separately updated (the above fix is actually for the keyboard FW). The FW update will be the part of the system update, and after the first boot once you connect the keyboard a notification will appear to ask you to confirm the update. Afterwards it will apply the update via Bluetooth. Code here: https://android.googlesource.com/device/google/dragon/+/marshmallow-dr-dragon-release/DragonKeyboardFirmwareUpdater/
sethyx said:
I did some digging today in open source repos - all the below are just assumptions, I don't want to be a smartass.
If issues seem to be hardware related, usually it's the kernel, not the actual HW. One thing is sure, Google/Nvidia guys are working hard to get things right.
Some examples:
There are even separate branches in the Chomium kernel repos to stabilize the Pixel C: https://chromium.googlesource.com/chromiumos/third_party/kernel/+refs - search for "stabilize-smaug" here.
This is almost surely the fix for the repeated key issues of the keyboard (was merged in mid-December): https://chromium.googlesource.com/chromiumos/third_party/kernel/+/5e09b5b68e2a09257cad69870989b7977797f09c
If you search for "touch" on the Chromium gerrit, there are literally dozens of fixes, most of them already merged. One that I think is related to the Pixel C, and might be a key one: https://chromium-review.googlesource.com/#/c/320202/
I've also found a change related to the Pixel C that is still under review, Nvidia guys were talking about a deadline of next Thursday (14th January), until they need to fix something: https://chromium-review.googlesource.com/#/c/314327/ - scroll down to the comments.
So, let's hope we'll receive an update by the end of the month. The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.
PS: This is a bit unrelated, but I've found out from the device tree that the Keyboard firmware can be separately updated (the above fix is actually for the keyboard FW). The FW update will be the part of the system update, and after the first boot once you connect the keyboard a notification will appear to ask you to confirm the update. Afterwards it will apply the update via Bluetooth. Code here: https://android.googlesource.com/device/google/dragon/+/marshmallow-dr-dragon-release/DragonKeyboardFirmwareUpdater/
Click to expand...
Click to collapse
i'm thinking if a few big issues do not get resolved by next weekend [1/15-1/17] google may experience a large volume of returns prior to the 1-22 deadline for holiday purchases. google may want to put out an ota in hopes a lot of the issues go away. very nice post, btw, i appreciate all the digging.
OP is correct in his assumptions on the tegra processors. There are always issues with devices that have them especially when the device is first released. Usually it takes about 6 months to get rid of the issues with software/UI updates. The tegra k1 devices did not become stable until July 2015; more than 8 months after there release.....
Sent from my iPad using Tapatalk
sethyx said:
So, let's hope we'll receive an update by the end of the month. The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.
Click to expand...
Click to collapse
Thanks for the digging but they have until around Jan. 22nd to get a fix out. I am not going to go on faith that the two major issues will be fixed. (wifi/touchscreen). The fact it was launched with these issues present on most of them is troubling.
dkryder said:
i'm thinking if a few big issues do not get resolved by next weekend [1/15-1/17] google may experience a large volume of returns prior to the 1-22 deadline for holiday purchases. google may want to put out an ota in hopes a lot of the issues go away.
Click to expand...
Click to collapse
That is what I am thinking as well. I think a lot of people do not notice the wifi download issue because they are either close to their router or are not comparing the speeds next to other devices. I noticed it on day 2 when I was viewing my imgur albums and noticed considerable slower page load compared to other devices. That opened up a can or worms right there.
The touchscreen issue is very noticeable though. Hope these get fixed asap.
For what it's worth i'm 2 floors away from my router and on my 2nd Pixel (first one had a dodgy touchscreen) and the speed is completely fine
atg284 said:
Thanks for the digging but they have until around Jan. 22nd to get a fix out. I am not going to go on faith that the two major issues will be fixed. (wifi/touchscreen). The fact it was launched with these issues present on most of them is troubling.
That is what I am thinking as well. I think a lot of people do not notice the wifi download issue because they are either close to their router or are not comparing the speeds next to other devices. I noticed it on day 2 when I was viewing my imgur albums and noticed considerable slower page load compared to other devices. That opened up a can or worms right there.
The touchscreen issue is very noticeable though. Hope these get fixed asap.
Click to expand...
Click to collapse
My speeds compared to my 6 p were virtually identical. Router on another floor some 25 yds away.
bill3508 said:
My speeds compared to my 6 p were virtually identical. Router on another floor some 25 yds away.
Click to expand...
Click to collapse
Must be nice. What router are you using? Are you on wifi AC or N ?
atg284 said:
Must be nice. What router are you using? Are you on wifi AC or N ?
Click to expand...
Click to collapse
This was my post a while back. 4000 sq ft 3 level home. Upstairs router is a Asus rt66, down stairs is a Actiontek or something like that. I have two different providers , one capped and the crappy dsl is not. I live out in the sticks.
http://forum.xda-developers.com/showthread.php?p=64460576
bill3508 said:
This was my post a while back. 4000 sq ft 3 level home. Upstairs router is a Asus rt66, down stairs is a Actiontek or something like that. I have two different providers , one capped and the crappy dsl is not. I live out in the sticks.
http://forum.xda-developers.com/showthread.php?p=64460576
Click to expand...
Click to collapse
Very odd. I have the same router and get noticeably slower download speeds abound 25-30ft from the router. On a different floor but still. I kind of live out in the sticks as well. Both units had the same exact issue. just wish this wasn't a problem.
atg284 said:
Thanks for the digging but they have until around Jan. 22nd to get a fix out. I am not going to go on faith that the two major issues will be fixed. (wifi/touchscreen). The fact it was launched with these issues present on most of them is troubling.
That is what I am thinking as well. I think a lot of people do not notice the wifi download issue because they are either close to their router or are not comparing the speeds next to other devices. I noticed it on day 2 when I was viewing my imgur albums and noticed considerable slower page load compared to other devices. That opened up a can or worms right there.
The touchscreen issue is very noticeable though. Hope these get fixed asap.
Click to expand...
Click to collapse
I love the tablet and really would like to keep it, wifi issues are a deal breaker though, but I'll be happy to wait till the end of the month provided Google officially accepts the issues, confirms they are not hardware related (not sure if the forum post will be enough) and commits to a fix by the end of the month or at the very least extends the return period sufficiently. Just one guy's opinion.
Mine acts weird with the speed test app. It shows slower download speeds than my service provides during a speed test but will max out my service when actually downloading.
rohmbd said:
Mine acts weird with the speed test app. It shows slower download speeds than my service provides during a speed test but will max out my service when actually downloading.
Click to expand...
Click to collapse
I thought the same until I did side by side comparisons with other devices and there is a web based speed test that you can do as well:
http://testmy.net/
I am a bit curious about the noveau driver. I read that its graphics performance isn't very good in comparison to nvidia's own linux driver when testing desktop gpus in Ubuntu. Why, given this information, would Google use noveau? Also, would Google have forked noveau for ryu?
jamesrick80 said:
OP is correct in his assumptions on the tegra processors. There are always issues with devices that have them especially when the device is first released. Usually it takes about 6 months to get rid of the issues with software/UI updates. The tegra k1 devices did not become stable until July 2015; more than 8 months after there release.....
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Did you mean 2016? I'm a Nexus 9 owner and bought it mostly to play Clash of Clans... Yeah, it can be a lame reason to buy a tablet but it is the truth.
When you reach TH8 (Clash of Clans players know what I'm talking about), CPU &/or GPU can't handle the graphics... Well, I guess that it's still missing something to be solved on kernel side or even the bionic for denver still hasn't been optimized enough since using a custom kernel and OCing CPU and GPU makes graphics somehow become more fluid (while in the game) and the constant stuttering that causes the touch screen input problems (huge problems on this part, I have to touch three of four times on the same place for it to recognize what I want to do) or the lags almost disappears.
Now you're gonna say "But Nexus 9 is a beast and I run X game with it and it's fluid!" Yeah, I hear ya and you're right, but something is going on with this tablet and I still can't figure it out what it is... Is it the non-optimized kernel or the non-optimized bionic? Who knows... OCing is just hiding something that needs to be fixed in my opinion... Oh... Did I mention that the kernel defconfig doesn't have multi-core scheduler support activated (CONFIG_SCHED_MC)?
sethyx said:
The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.[/URL]
Click to expand...
Click to collapse
It seems that the WiFi issue was also caused by the kernel... https://chromium-review.googlesource.com/#/c/321155/4
sethyx said:
It seems that the WiFi issue was also caused by the kernel... https://chromium-review.googlesource.com/#/c/321155/4
Not cool, NVIDIA, not cool.
Click to expand...
Click to collapse
This is actually great news as hopefully it isn't the magnets or some other hardware related issue and can be fixed.
sethyx said:
It seems that the WiFi issue was also caused by the kernel... https://chromium-review.googlesource.com/#/c/321155/4
Click to expand...
Click to collapse
Just FYI that patchset has nothing to do with the WiFi

Resources