Related
or the lack of it.
I see Google employees posting on google forum, but all of them dont even answer the real questions. In fact I've notice that they bump up the threads where people (or maybe the same google employees) write how they love their N1 and how its so much better then iPhone.........
WTF ???
notice the first person who responded
http://www.google.com/support/forum/p/android/thread?tid=0a5521b9ffa4c7a7&hl=en
http://www.google.com/support/forum/p/android/thread?tid=6c7fd11a4225cbb5&hl=en
just go to HTC if your having phone issues, and Tmobile if your having network issues. Think of Google as a retailer. for the most part phone, or warranty issues will be handled by the manufacturer, and network, by the network.
^ +1
Google will likely expand their support if they want to continue selling directly to the public. I think they underestimated mob mentality with the logic that HTC would support the phone, and the carrier would support the services. However, this is like Microsoft selling you a computer directly (via a hardware partner). There's a knowledge base and multiple forums support venue's and while Google lacks a phone number to call, and Microsoft has this, MS will also bill you for your phone support request.
Apple works a bit differently, they build the hardware in house and support it directly. They've also been doing this for years so the structure is in place already. Google doesn't want to build hardware, they just wanted to get phones out without being as reliant on the hardware makers to push updates to the handsets released (combating the stagnation of the current phones).
Wow, someone get's around
bofslime said:
Wow, someone get's around
Click to expand...
Click to collapse
A hard reset will probably solve that.
HTC Provides support for the Nexus One. http://www.htc.com/www/support/nexusone/.
kozm0naut said:
HTC Provides support for the Nexus One. http://www.htc.com/www/support/nexusone/.
Click to expand...
Click to collapse
If you take another look at the links on the site you posted, all the help links link to Google's N1 "help" forum. HTC is not providing help for the N1 and from what I've seen, neither is Google. That's why I will flash Cyan's ROM when he releases one and will use XDA for support as I've always done (even when I used WinMo). LOL.
Out of interest does anyone know if the Nexus 4 will support HD voice? Is it a feature that requires baseband support or is it implemented in the system software?
r3loaded2010 said:
Out of interest does anyone know if the Nexus 4 will support HD voice? Is it a feature that requires baseband support or is it implemented in the system software?
Click to expand...
Click to collapse
Good question. I've currently got it on my Samsung Galaxy S3.
For it to work, you need all of the following:
- A handset that supports it (hardware-wise)
- A network that supports it (such as 3 Mobile in the UK)
- Software that supports it (The official 3 Mobile Samsung ROMs for the S3 support it, and CM10 supports it for the S3, but I don't know whether this was added in or part of Android 4.1.X natively)
- The call needs to be between two devices that meet all of the above.
HD voice is very impressive, though. It's like having the person stood next to you talking in your ear (which may or may not be a good thing, depending who you're talking to!).
I hope the Nexus 4 has it, it might possibly even be a deal-breaker for me if it doesn't.
Well, the baseband is a Qualcomm MDM9615 which should definitely support AMR-WB (the codec needed for HD Voice) so that's one part of the puzzle solved. Three definitely support it on their network, so the only question now is whether the phone's software supports it.
ja i have also tried to google that info... guess we have to ask the real google ^^ or LG?
really hope tht it will support HD Voice
r3loaded2010 said:
Well, the baseband is a Qualcomm MDM8215 which should definitely support AMR-WB (the codec needed for HD Voice) so that's one part of the puzzle solved. Three definitely support it on their network, so the only question now is whether the phone's software supports it.
Click to expand...
Click to collapse
Looks like the Optimus G also has it..?
So hardwarewise we are safe to go? CM 10 also does support it if i am not mistaken? would be strange if Android would not?
Also tried to contact LG but that did not help much. ( They at least assured me it is voice enabled and has got google now *facepalm*)
r3loaded2010 said:
Well, the baseband is a Qualcomm MDM8215 which should definitely support AMR-WB (the codec needed for HD Voice) so that's one part of the puzzle solved. Three definitely support it on their network, so the only question now is whether the phone's software supports it.
Click to expand...
Click to collapse
Forgive me if I am wrong, but isn't it the DSP that needs to support it? The QDSP6 does appear to support AMR-WB anyway, I just didn't think the baseband had anything to do with it, have I misunderstood?
l0st.prophet said:
Forgive me if I am wrong, but isn't it the DSP that needs to support it? The QDSP6 does appear to support AMR-WB anyway, I just didn't think the baseband had anything to do with it, have I misunderstood?
Click to expand...
Click to collapse
The DSP responsible for implementing the codec is integrated within the MDM baseband chip, and from what I've gleaned the baseband does support it.
Still nothing on that?
Neither google nor LG replied..
Well I've got my Nexus 4 now, so I rang my wife on her Samsung Galaxy S III (we're both on the 3 network in the UK) and the call was in HD.
So the Nexus 4 does support HD voice!
I just posted a reply to another thread that I'm getting HD voice on my N4 as well.
http://forum.xda-developers.com/showthread.php?t=2032737
T-Mobile HD Voice
I can't wait to see if it works on the Nexus 4 over T-Mobile in the US. They recently announced support but neglected to list the Nexus 4 on their supported devices, even though they sell the device in stores.
http://www.tmonews.com/2013/01/t-mo...e-network-dramatically-improves-call-quality/
Let's hope they have a firmware update for the upcoming LTE network too.
sjgore said:
Well I've got my Nexus 4 now, so I rang my wife on her Samsung Galaxy S III (we're both on the 3 network in the UK) and the call was in HD.
So the Nexus 4 does support HD voice!
Click to expand...
Click to collapse
Please how can you check whether the call is in HD?
PieWai said:
Please how can you check whether the call is in HD?
Click to expand...
Click to collapse
It sounds like you're stood next to the person rather than being on the phone.
Technically, I don't know how you'd check in-call, there's no indication or notification or anything like that.
Reference code dot google dot com # 42255
My BT headset is a Sena SMH10 (BT 2.1 spec)..non upgradeable. Since I bought the Nexus 4 in late January, I haven't been able to use my SMH10 as it would not recognize voice input from the Nexus 4. I applied the latest 4.2.2 upgrade to my Nexus 4 yesterday and now the only way that the Nexus 4 will connect to my headset is after a complete reboot...and then only for the duration of that "session"...usually for about 5 min..then it borks again. I honestly don't know which state is worse.
Google tech support today told me this:
1. No OS supports devices "forever" (or two years back it seems). Contact your device manufacturer and ask them for an update. Since my device can't be upgraded, I'm SOL.
2. They admitted there was nothing on the Play store that stated that the Nexus 4 "might" not work with older BT devices. They admitted there was nothing on the PlayStore stating that Android does not support 2 years old devices. If you consider 2.1 to be an old spec.
3. They said they would forward my "request for refund" to their billing dept. However, since "James in tech spt" terminated our call after I called BS on his scripted lines about backward compatibilty and hung up...WTF knows if he will follow through or not.
4. "Eric" the floor supervisor, also parroted the same comments about how "nobody supports backward compatability with devices 3-4 years old" in spite of being told it was only 2 years old.
5. Google is no help and like all clones in tech spt "will talk reeeeely fast and try to drown you in word if you question them.." meh.
6. Ultimately, it's not the headset...it's the device. It's faulty and Google won't acknowledge it as such.
Just an FYI and not much help I'm afraid. Just a warning I guess...
Beware.
Soo..RMA time
Called back. Spoke to more reasonable hoomans who said an RMA was the next best option. They did point out that a refund was out of the question. ?
We'll see.
WA state Atty General. BBB. Internet. Reddit. XDA. Maybe...just maybe...
what?
why is this in the S4 forum? xD
Deekenhoof said:
Reference code dot google dot com # 42255
My BT headset is a Sena SMH10 (BT 2.1 spec)..non upgradeable. Since I bought the Nexus 4 in late January, I haven't been able to use my SMH10 as it would not recognize voice input from the Nexus 4. I applied the latest 4.2.2 upgrade to my Nexus 4 yesterday and now the only way that the Nexus 4 will connect to my headset is after a complete reboot...and then only for the duration of that "session"...usually for about 5 min..then it borks again. I honestly don't know which state is worse.
Google tech support today told me this:
1. No OS supports devices "forever" (or two years back it seems). Contact your device manufacturer and ask them for an update. Since my device can't be upgraded, I'm SOL.
2. They admitted there was nothing on the Play store that stated that the Nexus 4 "might" not work with older BT devices. They admitted there was nothing on the PlayStore stating that Android does not support 2 years old devices. If you consider 2.1 to be an old spec.
3. They said they would forward my "request for refund" to their billing dept. However, since "James in tech spt" terminated our call after I called BS on his scripted lines about backward compatibilty and hung up...WTF knows if he will follow through or not.
4. "Eric" the floor supervisor, also parroted the same comments about how "nobody supports backward compatability with devices 3-4 years old" in spite of being told it was only 2 years old.
5. Google is no help and like all clones in tech spt "will talk reeeeely fast and try to drown you in word if you question them.." meh.
6. Ultimately, it's not the headset...it's the device. It's faulty and Google won't acknowledge it as such.
Just an FYI and not much help I'm afraid. Just a warning I guess...
Beware.
Click to expand...
Click to collapse
Deekenhoof said:
Called back. Spoke to more reasonable hoomans who said an RMA was the next best option. They did point out that a refund was out of the question. ?
We'll see.
WA state Atty General. BBB. Internet. Reddit. XDA. Maybe...just maybe...
Click to expand...
Click to collapse
Honestly, who gives a crap buy another bluetooth set. Also try posting in the right thread k thxs bye
You miss the point old boy. It's a Nexus error vs a Device error first and foremost . The Nexus 4 refuses to initialize a BT connection.
Do you know how to read a diagram?
Deekenhoof said:
You miss the point old boy. It's a Nexus error vs a Device error first and foremost . The Nexus 4 refuses to initialize a BT connection.
Do you know how to read a diagram?
Click to expand...
Click to collapse
Do you know how to read the section your posting in and the box of your device?
Hey MAN THIS IS THE WRONG SECTION AND I LIKE TO TYPE IN CAPS BECAUSE THIS IS COOL
Post here : Nexus 4 Q&A, Help & Troubleshooting
Beside this being in the wrong forum , the bluetooth 2.1 spec is 5 yrs old. The device may only be 2yrs old to you, but it's tech was already 3yrs old when you bought it and is now 5yrs old.
word of advice do not buy anything with 3yrs old tech and expect it to work with everything. In this fast moving world of tech 3yrs is an eternity 5yrs is Extinct
"The Nexus 4 refuses to initialize a BT connection." This is by design, in the latest bluetooth specs the phone is hidden by default you have to manually change this to allow for pairing . Then once pair all other connections are initiated by the device not the phone and the phone will again by default be hidden and only accept request from already paired devices.
Hi everyone, I have a quick question and haven't been able to find the answer anywhere.
I just got the update to 4.3 last night on my Nexus 7. I forgot to check about Miracast support. I usually leave it at home for my wife and daughter and take my Nexus 10 to work.
I know the Nexus 10 got Miracast support with 4.3, but I need to know about the Nexus 7 and don't have it here to check. Can someone let me know?
Trying to swing by Best Buy on the way home and pick up the Netgear PTV3000
Thanks.
drgonzo712 said:
Hi everyone, I have a quick question and haven't been able to find the answer anywhere.
I just got the update to 4.3 last night on my Nexus 7. I forgot to check about Miracast support. I usually leave it at home for my wife and daughter and take my Nexus 10 to work.
I know the Nexus 10 got Miracast support with 4.3, but I need to know about the Nexus 7 and don't have it here to check. Can someone let me know?
Trying to swing by Best Buy on the way home and pick up the Netgear PTV3000
Thanks.
Click to expand...
Click to collapse
Only Nexus 4, Nexus 7 (2013), and Nexus 10 have Miracast Support.
https://support.google.com/nexus/7/answer/2865484?hl=en
Deeco7 said:
Only Nexus 4, Nexus 7 (2013), and Nexus 10 have Miracast Support.
https://support.google.com/nexus/7/answer/2865484?hl=en
Click to expand...
Click to collapse
That's some BS. Do you know of any mods or ROMs that have added the support yet?
There is already a working Miracast rom, but people/dev don't seem to be interested, so I don't think this rom will be include it to the other popular rom out there for the Nexus 7 (2012).
Original thread:
http://forum.xda-developers.com/showthread.php?t=2348991
I think some one got it working on PTV3000, if you read the Youtube comment.
http://www.youtube.com/watch?feature=player_embedded&v=KNEmaIr3FEg
Here is a 3D gaming I asked him to test out, just in case some one wanna know.
http://www.youtube.com/watch?v=20s567tzTdM&feature=player_detailpage&t=316
Here is the rom site for it:
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/Ota-packages
I don't have a Miracast receiver to test it out, but people who do can test it out.
drgonzo712 said:
That's some BS. Do you know of any mods or ROMs that have added the support yet?
Click to expand...
Click to collapse
It's not BS, because I answered your question with quotes. You didn't mention custom roms in OP.
Deeco7 said:
It's not BS, because I answered your question with quotes. You didn't mention custom roms in OP.
Click to expand...
Click to collapse
Hahaha. I wasn't saying your answer was BS. I was saying that Google not including it in the 4.3 update for the N7 was BS.
There is already a working Miracast rom, but people/dev don't seem to be interested, so I don't think this rom will be include it to the other popular rom out there for the Nexus 7 (2012).
Click to expand...
Click to collapse
This I never understood, why is that? I would have thought developers would have been right on to this. But kensuke has shown it is possible.
And watching the videos I think it's fantastic. Yes the gaming one had a bit of latency, but it looked minimal. Afaik, other devices (n4, n10) that officially support miracast have similar latency so I don't see why the n7 wasn't officially supported. I'm way more excited about this than chromecast which everyone seems to be freaking over.
I had a look at kensuke's page hoping for news on this being in 4.3 and saw this:
""Remove all traces of wifi display sink implementation and supporting code." "
Sink implementation means that a miracast device can act as a host. So you could miracast from one nexus 7 device to another.
But google has removed sink implementation in 4.3 source! Why would they do that?
Not that I would use the sink feature al the time, but it could be cool where you are trying to demo something to someone, they could just connect to your device and show them. I could think of lots of cool features with that, but for whatever reason, google has removed that code.
Yes the code is there in 4.2.2 but I imagine trying to put old code back can be difficult.
I read that from here:
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/Android-4.3
I hope he's successful in getting miracast to work in 4.3 and I also hope he can reimplement the sink feature but again, I understand that may be difficult because of google removing it.
When I saw the gaming video here:
http://www.youtube.com/watch?v=20s567tzTdM&feature=player_detailpage&t=316
I noticed how good the picture was. It made me wonder if there was anything in the miracast spec on performance/quality settings. When miracasting a movie I'd want the highest quality and wouldn't mind latency, but with a game or any realtime app, the less latency the better. I wonder if encoding at a lower bit rate would help tackle the latency? Maybe not as it's hardware encoding the steam and it's the onboard encoder chip and not the settings that would influence latency.
Thanks to kensuke for his efforts. I'm still somewhat surprised that it's taken this long for a developer to attempt to tackle this.
And I really hope other devs would show interest and incorporate this into their roms.
Im really surprised to see that no developer other than kensuke is interested about miracast support in nexus 7. This would be the best Customization ever done for nexus 7. A lot of people would be loving to have this feature yet there is only one rom which kensuke made for only miracast test purposes. It can not be ported to 4.3? - dont mind using 4.2.2 until i upgrade to 2013 nexus 7.
Devs hear us out!
Hi guys. Yesterday i bougth SONY TV with miracast feature. Can i use mentioned ROM to mirror screen of my N7 to SONY TV. I am still using Parandroid ROM(v.3.60) based on JB 4.2.2. Do i need to flash whole new ROM or there is any script or application that i can use?
aLPaSLaN07 said:
Im really surprised to see that no developer other than kensuke is interested about miracast support in nexus 7. This would be the best Customization ever done for nexus 7. A lot of people would be loving to have this feature yet there is only one rom which kensuke made for only miracast test purposes. It can not be ported to 4.3? - dont mind using 4.2.2 until i upgrade to 2013 nexus 7.
Devs hear us out!
Click to expand...
Click to collapse
He talks about the sync issues at Github.
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/Android-4.3
Also:
http://forum.xda-developers.com/showpost.php?p=44703331&postcount=57
Hi everyone,
I saw some people saying that if we flash the decrypted ROM we will lose our warranty. I was worried about that and I decided to contact Google. They told me that if I flash a custom ROM this will not void my warranty.
Here is what they answered me (It is a long answer because I asked about the availability, advantages of purchase through Play Store and, of course, warranty):
Hello Alexandre,
Thank you for contacting Google.
I see you are very interested in purchasing the Nexus 6 from Google Play. I understand it has been very hard to order currently. The demand for the Nexus 6 has been higher than we anticipated, and we have not been able to receive enough stock from the manufacturer, HTC. We are attempting to have more inventory available on Wednesday mornings every week. However, when we see them go available, they are again sold out after 30-60 seconds. Not a typo on my part, it is sold out in 1 minute.
Purchasing a smartphone from Google Play does allows your device to be a pure Android experience. This will come to you with Google apps, allowing you to download any other apps you would like, when you would like. You will also be the first to receive updates directly from Google. A smartphone purchased from Google Play also comes unlocked. This allows you to go to any carrier that supports the Nexus 6.
With your inquiry towards the encryption of a Nexus 6. Your Nexus 6 will come encrypted. The encryption is for locking your screen to prevent unwanted users to access for device. This does not impact the performance of your Nexus 6. If you Flash or Root your Nexus 6 so there is no encryption, this will not void your warranty. However, before we can look into troubleshooting steps or warranty options, we need your smartphone to be back to factory settings. This is in case your different operating system is causing the issue you are having.
If you have any further questions, please feel free to respond directly to this email. You may also call 24/7 at 855-836-3987.
Thanks,
Steven
The Google Support Team
Click to expand...
Click to collapse
I also contacted them through chat, they answered me the follow:
06:27:25 Mark F: No you would't loose the warranty however if there was a issue with he device you would have to factory reset the device before sending the device back to us to ensure it is set back to Factory standards.
Click to expand...
Click to collapse
Due to I be very insistent, I asked him to confirm this information:
06:31:02 Mark F: No you would not Loose the warranty however you would have to unroot the device before sending the device back to us.
Click to expand...
Click to collapse
I hope this helps to clarify for those who were feared of lose the warranty.
P.S.: I'm still learning English, so sorry if I made any mistake.
It concerns me that the representative thinks the manufacturer is HTC.....but I do appreciate the information.
D
DatDude123 said:
It concerns me that the representative thinks the manufacturer is HTC.....but I do appreciate the information.
D
Click to expand...
Click to collapse
Agreed... It bothers me every time I see CSR's from massive companies, sending emails or responses that are full of grammatical errors and obviously incorrect information. One would think that Google had slightly higher standards than this.
jjhiza said:
Agreed... It bothers me every time I see CSR's from massive companies, sending emails or responses that are full of grammatical errors and obviously incorrect information. One would think that Google had slightly higher standards than this.
Click to expand...
Click to collapse
Lol, Rogers was confused when I said Motorola Nexus 6 as they all thought it was LG Nexus 6. They kept telling me there was an LG Nexus 5, and an LG Nexus 6. So you guys can all enjoy your Motorola Nexus 6 I'm going to enjoy my LG Nexus 6. Lol.
But yeah my order is a Motorola Nexus 6, Rogers just had it named Wrong in their system.
I have sent quite a few devices back for warranty and have never had an issue with software modifications. I imagine it's not that rigorous. Simply want to make sure the device is lacking water damage and major physical damage i assume. I recently exchanged an AT&T htc one m8 for a replacement. Sent it back unlocked, rooted, s-off, and with a custom ROM. Do this for most of my phones and never had a problem. Even have a co-worker that sent a bricked device back lol
The chat rep doesn't know the difference between "lose" and "loose" - shoot me.
If you need to use your warranty, flash the stock image first. I've had 20+ android phones (all rooted and molested) and I've never had a warranty claim rejected.