I'm a firm believer that VZN and LG both couldn't get figure out a method to properly secure KK. I think the final OTA will have some method to ruin someone's day. My opinion, VZN is having fits over the old bootstack booting the ROM. I also figure they wanted the root method from ioroot to try to close it as well. Talk amongst yourselves ?
I just can't buy that there was an accidental slip up by both companies. Seems they setup a situation and decompile everything the devs post.
Sent from my VS980 4G using XDA Premium 4 mobile app
Maybe we actually do have a friend inside vzw. Since somehow every phone leaks or finds some miraculous method
Sent from my VS980 4G using Tapatalk
Dri94 said:
Maybe we actually do have a friend inside vzw. Since somehow every phone leaks or finds some miraculous method
Click to expand...
Click to collapse
Definitely a possible... Tho our devs have skills that border on the magical, and the power of collective knowledge is a wonderful thing haha.
But as far as VZW's predicament, I have no doubt that someone watches these forums, and curses over the extra dollars they'll have to spend on keeping their big red fingers locked tightly around our phones. As to whether it actually delays their official OTA, I'm sure they have deadlines to meet (esp. where the bloatware vendors are concerned), but it would be anyone's guess.
I'm just thrilled we have these leaks period. Even if the official OTA seals up security holes, this leak means a big boost to VS980 custom development!
The new KK leak seems odd, especially when some of its not even working correctly. I'm kinda stuck now. Device can get into Download mode but it just locks there.
Jivetime said:
Definitely a possible... Tho our devs have skills that border on the magical, and the power of collective knowledge is a wonderful thing haha.
But as far as VZW's predicament, I have no doubt that someone watches these forums, and curses over the extra dollars they'll have to spend on keeping their big red fingers locked tightly around our phones. As to whether it actually delays their official OTA, I'm sure they have deadlines to meet (esp. where the bloatware vendors are concerned), but it would be anyone's guess.
I'm just thrilled we have these leaks period. Even if the official OTA seals up security holes, this leak means a big boost to VS980 custom development!
Click to expand...
Click to collapse
Yea and how big red and lg both accidently leaked the rom and kernel.
Sent from my VS980 4G using Tapatalk
You ever think maybe they release it so devices get bricked and they gotta pay for new ones?
Well, if we're tossing out ideas...what if it got leaked so vzw could track who has 4.4 installed? Then they can red flag the rooters.
Today, I called to get a replacement. Speaker stoped working... she asked me if it was the original one I bought. I said Ya, then asked if I traded it or rooted it. I was Like, root? Lol...anyways, something on her end was flagging the phone. Of course, at the time of calling my phone was 100% stock. But I DID have 4.4 installed..replacement is in its way but still..more complicated then I expected
Sent from my VS980 4G using Tapatalk
zathus said:
Well, if we're tossing out ideas...what if it got leaked so vzw could track who has 4.4 installed? Then they can red flag the rooters.
Today, I called to get a replacement. Speaker stoped working... she asked me if it was the original one I bought. I said Ya, then asked if I traded it or rooted it. I was Like, root? Lol...anyways, something on her end was flagging the phone. Of course, at the time of calling my phone was 100% stock. But I DID have 4.4 installed..replacement is in its way but still..more complicated then I expected
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I don't really believe it, but I've seen some say VZW knows what apps you've installed. I saw a user once say they told him exactly what root apps he currently had. If that's true, some root app you've installed at some point may have flagged it. Or she was a liar. Lol. To be honest...once it was confirmed that you could downgrade and keep Loki on the other variants, I'm surprised LG didn't pull the Sprint rollout.
When the KK kernel source was "accidentally" leaked early after the devs were having problems with trying to create a zip rom from the KK leak and needed that info, that's is when my eyebrows were raised....lol. I was like, that's too much of a coincident. Somebody" was reading and listening to our cries....lmao. Nevertheless, thank you to whoever it was.
Tinfoil hat, anyone?
Sent from my VS980 4G using Tapatalk
JRJ442 said:
I don't really believe it, but I've seen some say VZW knows what apps you've installed. I saw a user once say they told him exactly what root apps he currently had. If that's true, some root app you've installed at some point may have flagged it. Or she was a liar. Lol. To be honest...once it was confirmed that you could downgrade and keep Loki on the other variants, I'm surprised LG didn't pull the Sprint rollout.
Click to expand...
Click to collapse
Lol, well she was definitely not lying. I didn't want to pry to much on what the issue was. Playing ignorant is sometimes the best rout but my guess is the Mac ids or sns from the day I bought the phone to now changed. She just kept saying "something is preventing me from sending you a replacement, are you sure you didn't trade phones with a friend or something?"
Sent from my VS980 4G using Tapatalk
Serial number is hardware level. Not possible unless you actually were swapped. They don't check it until old one is sent back, which is why you are given a purchase clause on returns. I'll assume your account was a bit jacked up if she wasn't lying, otherwise, liar.
Maybe Verizon wanted to wait for the knock code update to release KK instead of releasing it and then putting out another update right away for knock code.
Sent from my VS980 4G using Tapatalk
imhowie said:
Maybe Verizon wanted to wait for the knock code update to release KK instead of releasing it and then putting out another update right away for knock code.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
This is what I was thinking verizon isn't going to push 2 updates back to back, there going to make us wait for lg to add in knock code the release it
Sent from my VS980 4G using xda app-developers app
R0gersism said:
The new KK leak seems odd, especially when some of its not even working correctly. I'm kinda stuck now. Device can get into Download mode but it just locks there.
Click to expand...
Click to collapse
You said in the other thread that you wiped your Rom in recovery,not really conspiracy related just an accidental goof on your part.happens to the best of us.
Sent from my VS980 4G using Tapatalk
I don't know if it was necessarily a leak; I pulled it off their servers and published the link here one xda like a week back. It took us a few days but @xdabbeb found a way to trick our devices into taking that OTA. One thing I find suspicious is that it hasn't been taken down yet, which means it *might* be our official, it just hasn't had the green light yet. Also, the kernel source is still alive (direct link download) it just has the link removed.
Agreed. At the very least I think it was intended to be the official release. Whether they're holding off on pushing it to everyone because of a last minute issue they found or internal delays is anyone's guess. I tend to believe it's the latter.
Steamer86 said:
Serial number is hardware level. Not possible unless you actually were swapped. They don't check it until old one is sent back, which is why you are given a purchase clause on returns. I'll assume your account was a bit jacked up if she wasn't lying, otherwise, liar.
Click to expand...
Click to collapse
Liar? About what lol what is there to lie about. It was just an interesting conversation that kind of applied to this thread. And by the way, when I said serial number I was referring to the IMEI which, like the mac address is supposed to be unchangeable and yet there have been cases where they changed. But like I said, I don't know what the issue was. And obviously wasn't that big of a deal because my new phone is on its way
Sent from my VS980 4G using Tapatalk
JackpotClavin said:
I don't know if it was necessarily a leak; I pulled it off their servers and published the link here one xda like a week back. It took us a few days but xdabbeb found a way to trick our devices into taking that OTA. One thing I find suspicious is that it hasn't been taken down yet, which means it *might* be our official, it just hasn't had the green light yet.
Click to expand...
Click to collapse
I told ya, you devs are magic! I have been following the progress from day 1, and wondered how xdabbeb got it done.
zathus said:
Lol, well she was definitely not lying. I didn't want to pry to much on what the issue was. Playing ignorant is sometimes the best rout but my guess is the Mac ids or sns from the day I bought the phone to now changed. She just kept saying "something is preventing me from sending you a replacement, are you sure you didn't trade phones with a friend or something?"
Click to expand...
Click to collapse
When I quit working for VZW a couple years ago, the systems we used listed all the software/update/PRL version info of the software you had installed on your phone. It seemed that a lot of that info was based on the updates your phone pulled from the servers, and I never saw anything that actually indicated root status. However, they are constantly updating their capabilities so I wouldn't put it past em. I am of the opinion that most manufacturers don't check all that closely for root, at least if the phone is on a stock rom. I have never actually heard or read online of a VZW customer whose phone got rejected purely because it was rooted.
Jivetime said:
I told ya, you devs are magic! I have been following the progress from day 1, and wondered how xdabbeb got it done.
When I quit working for VZW a couple years ago, the systems we used listed all the software/update/PRL version info of the software you had installed on your phone. It seemed that a lot of that info was based on the updates your phone pulled from the servers, and I never saw anything that actually indicated root status. However, they are constantly updating their capabilities so I wouldn't put it past em. I am of the opinion that most manufacturers don't check all that closely for root, at least if the phone is on a stock rom. I have never actually heard or read online of a VZW customer whose phone got rejected purely because it was rooted.
Click to expand...
Click to collapse
I don't think it was rooting but maybe my update status. Example, my warranty date on the phone 2/4/2014. This is located in hardware information, hardware not software. I'll assume the warranty date is assigned the day you buy your phone. Now, it's changed. Point is, if that's changed what else could have changed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my VS980 4G using Tapatalk
Related
I have RMA'd 8 Nexus 4's. I have used every model except the 210k. I've noticed many improvements in build quality.
With the 302K, we got the little nubs and a more solid feel. Almost all of my Nexus 4's had creaking and build quality issues.
This 303K is perfect. The striping/banding problem with the display has been significantly reduced and the build quality is perfect.
This is the best Nexus 4 I've used. No problems at all. This will be my last RMA. I am keeping this one. :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Glad to hear that. Thanks for the information. Google has been quick and effective. Maybe I will send mine to see if they can replace it...
How many days did it last from u sent the buggy one untill u recieved the new one?
Thank you!
luiseteyo said:
Glad to hear that. Thanks for the information. Google has been quick and effective. Maybe I will send mine to see if they can replace it...
How many days did it last from u sent the buggy one untill u recieved the new one?
Thank you!
Click to expand...
Click to collapse
For me, the RMA's have been extremely quick. They ship me a new device in two days flat.
can i check if your phone is rooted when you RMA? I called the nexus hotline and stupidly tell the officer that my phone is rooted with custom rom.
Initially he wanted to direct me to manufacturer then I told him that I will insist on RMA with play store as I am going to restore it back to stock and relock it.
So now he needs to let his specialist know to see if they can still allow me to RMA it.
mgear356 said:
can i check if your phone is rooted when you RMA? I called the nexus hotline and stupidly tell the officer that my phone is rooted with custom rom.
Initially he wanted to direct me to manufacturer then I told him that I will insist on RMA with play store as I am going to restore it back to stock and relock it.
So now he needs to let his specialist know to see if they can still allow me to RMA it.
Click to expand...
Click to collapse
I always flash to stock to be safe.
I use this tutorial here:
http://forum.xda-developers.com/showthread.php?t=2010312
Rikusaki said:
I always flash to stock to be safe.
I use this tutorial here:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
oh so yr is rooted with custom rom and you reverted it to stock and relock.
They accepted all without any issues? I am worried that they will reject and I end up having 2 devices. Moreover, I am in SIngapore and i have to pay taxes for the faulty phone if play store rejects it.
mgear356 said:
oh so yr is rooted with custom rom and you reverted it to stock and relock.
They accepted all without any issues? I am worried that they will reject and I end up having 2 devices. Moreover, I am in SIngapore and i have to pay taxes for the faulty phone if play store rejects it.
Click to expand...
Click to collapse
Yep. No problems so far. I did the exact same procedure for every device. With some of them, I noticed a problem right away and didn't bother to do anything at all. I just called Google right away.
mgear356 said:
oh so yr is rooted with custom rom and you reverted it to stock and relock.
They accepted all without any issues? I am worried that they will reject and I end up having 2 devices. Moreover, I am in SIngapore and i have to pay taxes for the faulty phone if play store rejects it.
Click to expand...
Click to collapse
Nah, they know what we do with devices... that's why they sell soo much.. phones. Flash to stock, relock BL and send it. Don't worry they won't reject it.
luiseteyo said:
Nah, they know what we do with devices... that's why they sell soo much.. phones. Flash to stock, relock BL and send it. Don't worry they won't reject it.
Click to expand...
Click to collapse
ah thats what I was thinking too.. its a developer device and they expect us not to root?
Was taken aback when the customer service officer says the warranty will be void and blah blah.. Guess I will wait till what the specialist instructs..
my Rev 10 212k powerbutton is failing on me.. zz
Yeah the one I ordered a late march was a 303k version as well, and nothing has gone wrong with mine yet.
ah crap. google play just replied and they are biting on the fact that I had tampered with my phone's software and voiding my warranty. I have written another long email hopefully they can allow me to just rma.
This is plain rubbish. A nexus device but dont allow root.
Does only nexus 4 from USA have this type of serial number?
Sent from my Nexus 4 using xda premium
When I bought my N4 on March 28th, it was also a 303K - and I grabbed it from my carrier rather than through Google Play (didn't want to wait for shipping, and it was only $7 more, so I decided it was worth the convenience). Also, it's one without the new little nubs. Aesthetically and functionally, it was absolutely perfect! Screen was beautiful, especially when using AOSPA with it's nicely tuned kernel. Still fragile, though, as it's first fall less than 2 feet did shatter the screen. To be fair, it hit concrete face-down, so I'm not really surprised it broke... and to answer hoangtungst, I got mine in Canada.
mgear356 said:
ah crap. google play just replied and they are biting on the fact that I had tampered with my phone's software and voiding my warranty. I have written another long email hopefully they can allow me to just rma.
This is plain rubbish. A nexus device but dont allow root.
Click to expand...
Click to collapse
That sucks but to be brutally fair you can't argue really. They make no secret of the fact you void your warranty by rooting.
Sorry
Just out of interest would anyone pay a bit extra for a "true" dev phone in that the warranty remains intact for any software changes?
Thinking about it tho, that would leave lots of grey areas and loopholes, such as turning of thermal throttling and physically damaged the CPU etc.
Mine is a 302k, it doesn't squeak, it does not have nipples, and display is perfect. 303k just means produced in Korea in march 2013. I assume that more important is the hardware rev version, the external parts are subject to modifications without any advertisement, and they are just related to the end of old parts before starting using new ones...
mgear356 said:
ah crap. google play just replied and they are biting on the fact that I had tampered with my phone's software and voiding my warranty. I have written another long email hopefully they can allow me to just rma.
This is plain rubbish. A nexus device but dont allow root.
Click to expand...
Click to collapse
You said that your power button is failing? Just tell them, how does a button failing have anything to do with a custom rom put on the device?
If you fried something in side the phone from overclocking etc then yeh I could get why they'd reject it.
Really 8? Why did you send the last one in? Cause you wanted nubs and a new lens? I highly doubt you got 8 defective units. So stupid
Sent from my Nexus 4 using xda premium
Smallsmx3 said:
Really 8? Why did you send the last one in? Cause you wanted nubs and a new lens? I highly doubt you got 8 defective units. So stupid
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I had the exact same thought. I don't know of anyone who would have gone through the RMA process 8 times for legit reasons. You would move on to a different device long before you dealt with 8 RMA's. Google should have told you to pound sand when you requested the 4th RMA.
kalo88 said:
You said that your power button is failing? Just tell them, how does a button failing have anything to do with a custom rom put on the device?
If you fried something in side the phone from overclocking etc then yeh I could get why they'd reject it.
Click to expand...
Click to collapse
Initially they were okay with rma. Then I mentioned about rooted then the officer started saying about void warranty and ask me to back to LG
mgear356 said:
Initially they were okay with rma. Then I mentioned about rooted then the officer started saying about void warranty and ask me to back to LG
Click to expand...
Click to collapse
Did you try to call back and speak to someone different? Leave out the rooted part this time.
I have been following most of the AOSP threads fairly closely to see people's experiences and I have seen a disturbing amount of people report bricked phones. The odd thing about it is that these bricks didn't occur during the process of flashing a rom. They all happened (or most of them at least) while trying to power on the phone after it was turned off or in deep sleep. Here are links to posts by DIFFERENT AOSP rom users who all experienced similar issues (one of these posts contain links to 3 other posts):
http://forum.xda-developers.com/showpost.php?p=42682374&postcount=78
http://forum.xda-developers.com/showpost.php?p=42654173&postcount=434
http://forum.xda-developers.com/showpost.php?p=42681918&postcount=436
http://forum.xda-developers.com/showpost.php?p=42557657&postcount=417
I personally have run Slim's rom for a good 4-5 hours w/o problems. However, I went back to Sense shortly thereafter. I'm not trying to cause some kind of panic but on the same hand I don't want to see people sitting around with a $500 desk ornament. Bottom line is we are responsible for what we do with our phones and as a result we should do as much research as possible before flashing anything. Look before you leap!
Edit: Here is an additional means to record your brick experience:
smac7 said:
I made this to try to pinpoint the issue. This way we can collaborate with all one owners, not just sprint.
If you have this issue, please add your info.
Here is the form
https://docs.google.com/forms/d/17NmaM3zhWueTxI_y7f1U7N6Er6tprd22I8_f3aIYmCw/viewform
Here is the responses
https://docs.google.com/spreadsheet/ccc?key=0AkLYIbykddrAdF9TMXBXaXZjMFhEczlSYUhoVDNHU1E#gid=0
Let me know if i should add any other crucial questions. I encourage people to post this in other threads when relevant.
Edit: page is open for public sharing
Click to expand...
Click to collapse
Thanks goes out to the user who took the time to do this.
Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTCONE using Tapatalk 2
Alex1123 said:
Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
That's some messed up stuff.... You shouldn't have had to pay since it was a "hardware" issue. It should've been covered under the manufacturers warranty.
Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2
Alex1123 said:
Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I know but whenever i've had a problem like that it's always been a free fix through sprint......
yeah I am in the same boat, I believe I was the first to report this. At first I thought it was just me and I passed it off as nothing. Since I've got my replacement I've watched people starting to trickle in with the same exact problem on AOSP I would definitely avoid flashing AOSP until the cause is narrowed down and solved if possible. As I said before it would be a damn shame not to run AOSP on this mighty device, but I have to stick with sense for now and hope that this problem is squashed soon.
Wow really? How upsetting. I'll have to keep an ear open. If there is any news regarding this issue please share
Sent from my HTCONE using xda app-developers app
Has anyone on a NON AOSP rom run their battery down and had it die? Did it charge? I know on a few other phones it was actually the recovery that had this issue. I would try it myself but as I have my phone through work, replacing it is a bit more complicated.
I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app
That makes sense. Thanks
Sent from my HTCONE using xda app-developers app
socalnative1 said:
I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
you are not able to relock the bootloader. we're talking total shut down, no power, no charge, no recovery, no bootloader, no fastboot adb devices, not a thing period point blank. i have the dead device still, and for the life of me cannot get it to do anything. I have been on my replacement for 2 weeks now running sense. hopefully the cause and solution are near.
Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta
felacio said:
Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm with you on that
Until we get more kernel sources/reliable code out of HTC, playing with AOSP can be a dangerous game. And tbqh, it could well be OP's fault (not saying it is, but it can be). Flashing custom software of any kind is going to give your carrier/OEM an easy way out if anything goes wrong, which everyone really should keep in mind before making the jump.
What recovery are the "bricked" users running. TWRP or CWM?
Yeah I had my battery die completely on a sense Rom, but I was easily able to charge it and turn it back on 2 minutes later.
Sent from My Only "One"
Glad I'm doing a lot of reading before I make the jump back to HTC. Seems like the One is more of a pain in the ass to Develop (safely) for than the GS3. Looks like I'll be sticking to sense for a while.
For once in all of my android ownership, I'm not really pressed to switch to aosp so this isn't a huge deal for me. The phone is already blazing fast and I actually enjoy and use a lot of the features HTC has implemented into Sense 5. And HTC's browser is the smoothest I've ever used. I do hope someone figures out the problem though. Hate to see more people get bricked.
Sent from my HTCONE using xda premium
Kraizk said:
What recovery are the "bricked" users running. TWRP or CWM?
Click to expand...
Click to collapse
So far, only TWRP users have reported this issue.
I don't want to be Mr. Obvious but I'm assuming that you guys have already tried the trick of putting your phone under a bright light, etc etc
http://www.gsmarena.com/android_42_update_rolling_out_for_htc_one_dual_sim-news-6299.php
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess we'll be waiting even longer. Glad HTC has their ducks in a row right now...
You have information that our version hasn't been submitted to Sprint already or..?
Felnarion said:
You have information that our version hasn't been submitted to Sprint already or..?
Click to expand...
Click to collapse
I'm sure it's with Sprint, but they dropped this to the Dual SIM model before the first international model.
eXplicit815 said:
I'm sure it's with Sprint, but they dropped this to the Dual SIM model before the first international model.
Click to expand...
Click to collapse
This really irritates me. HTC yet again can't get updates out in time. Almost 3 months in... Still no update
Sent from my HTCONE
XaoSilentrzk said:
This really irritates me. HTC yet again can't get updates out in time. Almost 3 months in... Still no update
Sent from my HTCONE
Click to expand...
Click to collapse
And with 4.3 on the horizon... I still love HTC, this is just one of those parts about company that worry me.
The good thing is we at least know what we're expected to see with the update.
eXplicit815 said:
The good thing is we at least know what we're expected to see with the update.
Click to expand...
Click to collapse
I've already engaged in a email conversation with HTC Dev and they ensure me that updates are coming soon and they are working on releasing the sources as well soon(sounds like everything else we read but it's nice they are directly communicating with me).
mhsbrian said:
I've already engaged in a email conversation with HTC Dev and they ensure me that updates are coming soon and they are working on releasing the sources as well soon(sounds like everything else we read but it's nice they are directly communicating with me).
Click to expand...
Click to collapse
Only thing missing, time frame. I don't even need an exact date. I just need something from HTC like "Middle of July" or even something from Sprint saying, "Expect it in July".
XaoSilentrzk said:
This really irritates me. HTC yet again can't get updates out in time. Almost 3 months in... Still no update
Sent from my HTCONE
Click to expand...
Click to collapse
It's not HTC. There are many parties involved when an update is released on a Carrier phone as opposed to a unbranded phone.
raptoro07 said:
It's not HTC. There are many parties involved when an update is released on a Carrier phone as opposed to a unbranded phone.
Click to expand...
Click to collapse
So then... What about the International One that still hasn't been updated?
eXplicit815 said:
So then... What about the International One that still hasn't been updated?
Click to expand...
Click to collapse
I appears that this update being pushed to the phones if China Telecom or some other Operators. The rough order is Google releases an update. OEMs get it working on theier hardware and add there stuff to it. Then the OEMs send it to unbranded phones and/or the Operators for them to put their stuff in it and test per thier networks. Then the Carriers push an update.
My guess here is that the Chinese Operators did not care to do much testing or what they did was fine, where as I read HTC was not happy with some of the firmware in the 4.2.2 update and have slightly delayed pushing thier's out. That seems awfully scary if an Operator is rushing something out.
eXplicit815 said:
So then... What about the International One that still hasn't been updated?
Click to expand...
Click to collapse
Seriously... These kind of things make me regret being on sprint. Already our GSM brothers on GayT&T & Fail-Mobile converted their devices to Developer editions & Unbranded devices. We're stuck with stupid CDMA policies
Sent from my HTCONE
XaoSilentrzk said:
Seriously... These kind of things make me regret being on sprint. Already our GSM brothers on GayT&T & Fail-Mobile converted their devices to Developer editions & Unbranded devices. We're stuck with stupid CDMA policies
Sent from my HTCONE
Click to expand...
Click to collapse
You just dissed every American carrier that carries the One.
Even the sprint and Verizon GS4s received GE edition ROM ports, which has me going crazy. I'm seriously considering ditching my ONE for the GS4. Not to mention the signal for LTE on this phone is seriously getting to me in places I had perfect LTE with my GS3
Nobody has patience.... Just live life and let the update surprise you. Too much demanding going on here.
Sent from my S-Off Sprint HTC ONE using xda premium
sailio said:
Nobody has patience.... Just live life and let the update surprise you. Too much demanding going on here.
Sent from my S-Off Sprint HTC ONE using xda premium
Click to expand...
Click to collapse
No demanding. Just frustrated with HTC at this point. 4.2.2 was supposed to be out mid June. It is now July. I had confidence in the ONE but I'm losing it quickly and so are some other people. No projected date, statement, acknowledgment to customers. This is why I left the EVO LTE. I had a soft spot in my heart because of the original OG Evo but it is starting to leave.
Jahspree said:
No demanding. Just frustrated with HTC at this point. 4.2.2 was supposed to be out mid June. It is now July. I had confidence in the ONE but I'm losing it quickly and so are some other people. No projected date, statement, acknowledgment to customers. This is why I left the EVO LTE. I had a soft spot in my heart because of the original OG Evo but it is starting to leave.
Click to expand...
Click to collapse
There was never a time table. There were rumors that 4.2.2 was supposed to hit in June. And this was for unbranded EU handsets not the US ones....
Kraizk said:
There was never a time table. There were rumors that 4.2.2 was supposed to hit in June. And this was for unbranded EU handsets not the US ones....
Click to expand...
Click to collapse
Regardless, it's been too long. Especially not relaying information to your customers. When your competitors updating older devices quicker than your newest device. That's sad.
Jahspree said:
Even the sprint and Verizon GS4s received GE edition ROM ports, which has me going crazy. I'm seriously considering ditching my ONE for the GS4. Not to mention the signal for LTE on this phone is seriously getting to me in places I had perfect LTE with my GS3
Click to expand...
Click to collapse
You've gone too far. Obviously you want the s4. I'll never leave the One for a stupid s4 regardless of OS. That plastic garbage can stay buggy on it's own
Sent from my HTCONE
That blows
Sent from my HTCONE using xda app-developers app
Here's the apk
http://goo.gl/Qal2tm
Download the zip from the link. Extract the apk and install like normal.
Credit to androidpolice for getting it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk 4
It looks exactly like PayPal's new app.
Sent from my HTC One using xda app-developers app
Mine just updated to the new version. But then again im stock and unrooted.
Has anyone been able to get it to work on non-Sense based ROMs? I've seen a few out there that say it will work, but they involve using cracked apks and I just don't feel safe putting my financial information into one of those.
(Edit) I know its still early on with it, just popping the question out there to see if anyone has had success tinkering with it yet.(/edit)
Looks like the same version that is in the PlayStore currently.
im0rtalz said:
Looks like the same version that is in the PlayStore currently.
Click to expand...
Click to collapse
Yes, it is. Keep in mind, however, that this is a staged rollout and as a result not everyone can see it in the Play Store.
I am guessing that the rollout is based on device so I would honestly imagine all Sprint Ones can see it but that is just a complete guess.
Sent from my HTCONE using Tapatalk 4
The update broke the app for me... Went from making nfc payments on the regular to not being able to open the app without it stopping immediately.
{update} uninstalling and re-installing the app fixed the "unexpected stop" issue for me, in case anyone else had the same issue. {/update}
(and shouldn't this be in the apps section?)
Sent from my beige box using xda premium
Am amazed people would trust a random apk on xda-dev for Wallet. Then again, a malicious ROM dev could have back door access to all your accounts, so I guess it's not much different.
Still doesn't seem to allow NFC payments for stock cyanogenmod though. Not a huge deal as I don't need at all though would have been nice if they would enable the NFC payments for all phones too. The app just adds the ability to send money from friend to friend.
gobaers said:
Am amazed people would trust a random apk on xda-dev for Wallet. Then again, a malicious ROM dev could have back door access to all your accounts, so I guess it's not much different.
Click to expand...
Click to collapse
This random apk from a dev on xda is cryptographically signed by Google. It is identical to the one put up in the market.
epyon22 said:
Still doesn't seem to allow NFC payments for stock cyanogenmod though. Not a huge deal as I don't need at all though would have been nice if they would enable the NFC payments for all phones too. The app just adds the ability to send money from friend to friend.
Click to expand...
Click to collapse
Google's explanation for this is that, with a rooted and/or romed phone, they (Google) do not have the same confidence in the security of your banking data. I think it's an ass covering situation so that if something does happen, people can't blame the app (and Google)
Sent from my beige box using xda premium
This is actually a problem not with cyanogenmod but with the HTC one's implementation on cyanogenmod(maybe others). My nexus s running cyanogenmod works with google wallet's nfc perfectly. Usually they just give a warning saying that your phone is rooted that that it might not be secure.
epyon22 said:
This is actually a problem not with cyanogenmod but with the HTC one's implementation on cyanogenmod(maybe others). My nexus s running cyanogenmod works with google wallet's nfc perfectly. Usually they just give a warning saying that your phone is rooted that that it might not be secure.
Click to expand...
Click to collapse
So what you're essentially saying is that it isn't a problem with Cyanogenmod but rather that it is a problem with Cyanogenmod's official builds for the HTC One? It's like saying it's not Steve's fault but that it's actually Steve's fault.
rougegoat said:
So what you're essentially saying is that it isn't a problem with Cyanogenmod but rather that it is a problem with Cyanogenmod's official builds for the HTC One? It's like saying it's not Steve's fault but that it's actually Steve's fault.
Click to expand...
Click to collapse
I'm trying to say its not global to cyanogenmod builds across phones and I don't belive google is actively blocking it for the sole reason it is a aftermarket ROM. From my understanding to get it working the build.prop just needs to be modified to match the original phone, which changing these values in cyanogenmod's code is a design decision/organizational decision causing google wallet to think that its a phone that might not have nfc. I'm sure there is a way for them to detect NFC but they are taking the safe secure road and using some sort of lookup for each phone.
epyon22 said:
I'm trying to say its not global to cyanogenmod builds across phones and I don't belive google is actively blocking it for the sole reason it is a aftermarket ROM. From my understanding to get it working the build.prop just needs to be modified to match the original phone, which changing these values in cyanogenmod's code is a design decision/organizational decision causing google wallet to think that its a phone that might not have nfc. I'm sure there is a way for them to detect NFC but they are taking the safe secure road and using some sort of lookup for each phone.
Click to expand...
Click to collapse
I've gone through pretty much every line where the CM team did something that would break compatibility(such as using m7spr instead of m7wls) and it has never worked for me. They may have removed something from the build.prop that caused it, but I don't really see that as likely. I mean if all that was needed was a slight change to that it would already have been done and merged into the nightlies.
rougegoat said:
I've gone through pretty much every line where the CM team did something that would break compatibility(such as using m7spr instead of m7wls) and it has never worked for me. They may have removed something from the build.prop that caused it, but I don't really see that as likely. I mean if all that was needed was a slight change to that it would already have been done and merged into the nightlies.
Click to expand...
Click to collapse
I tried the same and got nothing. I don't what they're using to verify now.
This post discuses what was done to crack the apk and make Tap-to-Pay work. I don't trust cracked financial apps though, regardless of how open they are about it. Maybe it could lead to a fix for CM10.2?
rougegoat said:
This post discuses what was done to crack the apk and make Tap-to-Pay work. I don't trust cracked financial apps though, regardless of how open they are about it. Maybe it could lead to a fix for CM10.2?
Click to expand...
Click to collapse
Yea that apk worked. The apk was modded to get galaxy nexus as os from whatever phone its installed to. So NFC tap and pay will work but it also need wallets cert keys which cm 10.2 does have so nfc stuff can work. I'm not sure what we can do in rom that's similar. It seems it's not getting info from the build.prop
Sent from my HTCOne using Tapatalk 4
I wonder if a fix for this type of issue is something we can expect as a result of Cyanogenmod going commercial. It may be easier for them to get general approval as a company than it was for them to get it as a bunch of random developers working for the greater good.
Just been on chat with EE for the second time this week. They just confirmed that they will be carrying the nexus 5 from the 28th of this month. They also confirmed that it will be available on both LTE and standard 3G plans here in the UK, they will also be offering the phone on pay as you go contracts at a starting price of £230 for 16GB and £250 for 32GB. I know its not much info but it is confirmed which is nice. Should be able to get hands on with this phone very soon!
Hmmm I winder how much of this is true
Oli1122 said:
Just been on chat with EE for the second time this week. They just confirmed that they will be carrying the nexus 5 from the 28th of this month. They also confirmed that it will be available on both LTE and standard 3G plans here in the UK, they will also be offering the phone on pay as you go contracts at a starting price of £230 for 16GB and £250 for 32GB. I know its not much info but it is confirmed which is nice. Should be able to get hands on with this phone very soon!
Click to expand...
Click to collapse
Pics or it didn't happen...
what does this mean for half life 3 tho?
What about the announcement?
Sent from my GT-I9100 using Tapatalk
i'm not believing anything unless it's from Google directly. carriers (and their reps) are mostly blowhards who have no clue what they're talking about
Ive got a few screenshots but can only release the on I have on my mobile right now. Will do others in around an hour when I get in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lucke said:
i'm not believing anything unless it's from Google directly. carriers (and their reps) are mostly blowhards who have no clue what they're talking about
Click to expand...
Click to collapse
Usually I would agree but ive tried four reps now and three of the four all said the 28th, unfortunately no more comments on pricing.
Uk prices are completely false.
If it's out on the 28th in the UK, I wonder if that means it'll be out in the US sooner
AndreaCristiano said:
Hmmm I winder how much of this is true
Click to expand...
Click to collapse
Pretty true actually The nexus 5 is by far the most leaked android smartphone, with leaks from official partners and Google! Google was the first to leak the nexus 5, in there introduction video of android 4.4, which has now been removed from youtube. Later, about 2 days, KitKat's official FaceBook page added a comment on a post confirming android 4.4. Then Qualcomm confirmed some hardware specs of the Nexus 5, followed by a video of the nexus 5 running android 4.4 (also removed). And just yesterday, Google accidentally post the nexus 5 on there site, which seems a little odd
Honestly, I have a conspiracy that Google is just setting up the android world, and at the Google I/O event (Google's release party) release a totally different phone and a new android 4.4 UI:laugh:
arDroid.99 said:
Pretty true actually The nexus 5 is by far the most leaked android smartphone, with leaks from official partners and Google! Google was the first to leak the nexus 5, in there introduction video of android 4.4, which has now been removed from youtube. Later, about 2 days, KitKat's official FaceBook page added a comment on a post confirming android 4.4. Then Qualcomm confirmed some hardware specs of the Nexus 5, followed by a video of the nexus 5 running android 4.4 (also removed). And just yesterday, Google accidentally post the nexus 5 on there site, which seems a little odd
Honestly, I have a conspiracy that Google is just setting up the android world, and at the Google I/O event (Google's release party) release a totally different phone and a new android 4.4 UI:laugh:
Click to expand...
Click to collapse
What about the FCC certifications? Even if it was red herring, wouldn't we get see some other phone get approval? Do you think Google orchestrated the whole gub'ment shutdown so that they could sneak in a phone for approval and not have the FCC leak it since they were shutdown?
Does this mean I'm not getting a nexus 5???
sent while running with scissors
tosin01 said:
Uk prices are completely false.
Click to expand...
Click to collapse
Deff this. £20 diff between the two models... and it is incredibly low compared to the U.S price.
We UK peeps always get dirtily ripped off in the conversion game. Those prices would not represent that. I suspect something is off.
gee one said:
What about the FCC certifications? Even if it was red herring, wouldn't we get see some other phone get approval? Do you think Google orchestrated the whole gub'ment shutdown so that they could sneak in a phone for approval and not have the FCC leak it since they were shutdown?
Does this mean I'm not getting a nexus 5???
sent while running with scissors
Click to expand...
Click to collapse
Nah, but really confirmation for the Nexus 5 is still unofficial, it might not drop till next year, the only thing google really confirmed was android 4.4.
NinjaKenZen said:
Deff this. £20 diff between the two models... and it is incredibly low compared to the U.S price.
We UK peeps always get dirtily ripped off in the conversion game. Those prices would not represent that. I suspect something is off.
Click to expand...
Click to collapse
Totally agree.
arDroid.99 said:
Nah, but really confirmation for the Nexus 5 is still unofficial, it might not drop till next year, the only thing google really confirmed was android 4.4.
Click to expand...
Click to collapse
Bite your tongue!
tosin01 said:
Totally agree.
Click to expand...
Click to collapse
I agree they seem low, ive only quoted what ive been told. But the 28th is an official release date according to EE and now T-Mobiles support lines. Im just doing the rounds trying to see what info I can get out of them.
Since when do we get official release dates from EE reps, whoever the heck that is.
They should not allow any more new threads to be made in this section until Google officially announces it. These confirmation threads have gotten to be a joke.
[email protected] said:
Since when do we get official release dates from EE reps, whoever the heck that is.
They should not allow any more new threads to be made in this section until Google officially announces it. These confirmation threads have gotten to be a joke.
Click to expand...
Click to collapse
Since EE was the largest network in the UK and since everyone scrambling for all the info they can find.
Maybe if you don't like these threads them simply don't waste your precious time reading and replying in them eh?
Oli1122 said:
Since EE was the largest network in the UK and since everyone scrambling for all the info they can find.
Maybe if you don't like these threads them simply don't waste your precious time reading and replying in them eh?
Click to expand...
Click to collapse
Well, maybe we read these threads because we actually think there is something to read just to find out a customer rep said so.