So this morning I was checking around the news sites and I saw the iPhone now gets Google Wallet and we do not, I was pissed.
I just decided to install Google Wallet....it worked....I signed right in. I am currently running CleanROM 1.6.5. In the past when I tried to install it I always got a message saying "blah blah blah blah, you shall not pass". It is possible Scott did something to the CleanROM but I believe I tried it once before.
Can anyone else please confirm?
kainu7 said:
So this morning I was checking around the news sites and I saw the iPhone now gets Google Wallet and we do not, I was pissed.
I just decided to install Google Wallet....it worked....I signed right in. I am currently running CleanROM 1.6.5. In the past when I tried to install it I always got a message saying "blah blah blah blah, you shall not pass". It is possible Scott did something to the CleanROM but I believe I tried it once before.
Can anyone else please confirm?
Click to expand...
Click to collapse
Use this link here
http://forum.xda-developers.com/showthread.php?t=
Follow the directions and profit
From my Hyper drive powered S4 OC with ktoons
Obsidian_soul said:
Use this link here
http://forum.xda-developers.com/showthread.php?t=
Follow the directions and profit
From my Hyper drive powered S4 OC with ktoons
Click to expand...
Click to collapse
Link does not work
Just go to the market and down load google wallet its free and we do get it
Sent from my SCH-I545 using Tapatalk 4
It came out for Android just before the iOS version (hours). Note, that Google did not fix the code to access the secure element so NFC payments (tap-to-pay) are disabled for Verizon, AT&T and T-Mobile users.
I think you should have posted this in the "Verizon Samsung Galaxy S 4 Q&A, Help & Troubleshooting" section. This is more of a question then "general, tips & tricks, etc.".
Obsidian_soul said:
Use this link here
http://forum.xda-developers.com/showthread.php?t=
Follow the directions and profit
From my Hyper drive powered S4 OC with ktoons
Click to expand...
Click to collapse
Here is a working link
http://forum.xda-developers.com/showthread.php?p=42029814
From my Hyper drive powered S4 OC with ktoons
I've been getting crappy performance with google wallet v2 NFC
muyiwafly said:
I've been getting crappy performance with google wallet v2 NFC
Click to expand...
Click to collapse
Use v1 for right now
Sent from my BNTV250A using xda app-developers app
Its not Google that needs to fix any code. Its ATT, T-Mobile and Verizon that have to allow the app to work correctly. They block the app from working correctly to promote their own app. Old news.
Sent from my SPH-L720 using xda app-developers app
eskomo said:
Its not Google that needs to fix any code. Its ATT, T-Mobile and Verizon that have to allow the app to work correctly. They block the app from working correctly to promote their own app. Old news.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Actually, that's incorrect, and widely know, although normally incorrectly reported.
Google must update wallet to access the secure element on these phones in order for it to tap to pay. They're welcome to do so, as Verizon has stated many times.
chamberc said:
Actually, that's incorrect, and widely know, although normally incorrectly reported.
Google must update wallet to access the secure element on these phones in order for it to tap to pay. They're welcome to do so, as Verizon has stated many times.
Click to expand...
Click to collapse
Unfortunately you are incorrect, the tap to pay works fine on Sprint and it works fine when you change your build prop to a non big 3 phone during the set up. This is how the old mod works in conjunction with the xposed framework that removes the root check and region check. Verizon has deliberately blocked access to promote Isis which is their version of Google wallet.
From my Hyper drive powered S4 OC with ktoons
Sorry, that's incorrect. You're also discounting the fact that the Sprint phone is a different phone, and that the minute you alter the Verizon/Att phones they're no longer bound by the carrier rules.
Again, the simple fact is, all Google has to do is alter wallet to access the secure element, as is required. This a long debated issue, and widely misunderstood. It's google, not the carriers, period.
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Sorry, that's incorrect. You're also discounting the fact that the Sprint phone is a different phone, and that the minute you alter the Verizon/Att phones they're no longer bound by the carrier rules.
Again, the simple fact is, all Google has to do is alter wallet to access the secure element, as is required. This a long debated issue, and widely misunderstood. It's google, not the carriers, period.
chamberc said:
Sorry, that's incorrect. You're also discounting the fact that the Sprint phone is a different phone, and that the minute you alter the Verizon/Att phones they're no longer bound by the carrier rules.
Again, the simple fact is, all Google has to do is alter wallet to access the secure element, as is required. This a long debated issue, and widely misunderstood. It's google, not the carriers, period.
Click to expand...
Click to collapse
I hate to do this but you are in fact wrong. The phones are very very close to being the same. Only main differences have to do with radios, Freq's and such. The problem has been confirmed to be on Verizon's end. The Wallet apps are the same and work the same on all devices. Its what the carriers allow that is the problem. Wallet on ATT and Verizon access the SE fine, but its blocked from doing anything at that point. Obviously there is a work around but this does not involve the code in the app being fixed.
Why would Google block these 2 carriers considering they are larger than Sprint? More people using the service is a good thing. Wallet was blocked on the S3 and Note 2 on Verizon and Google had nothing to do with that either. It IS on the carriers end. They have their own service that they want to push instead. Therefore the block is in place.
Background info:
Using Safestrap, I downloaded the Google Play OS onto rom slot 4. (slot 1 is my primary OS)
I followed this procedure (using the non touchwiz links) yet couldn't get tap and pay to work. Is it a wallet problem (with the new update) or a user problem (because I suck and have only had a few experiences flashing zips/roms) Thanks for a reply!
John
Sent from Verizon GS4 running the GPE OS.
Related
Tired of waiting....
Stupid Verizon.
StreetStrip01 said:
Tired of waiting....
Stupid Verizon.
Click to expand...
Click to collapse
Plus one. At least give us a competing product. I feel like I'm renting my phone from them, the way they exert control over their customers is unreal.
I doubt it will ever be enabled. They will be using ISIS believe.
We may have to wait til we get AOSP based roms. I've tried multiple things to get wallet to work. Not going to lie, this is one reason I bough this phone was to use google wallet.
bb12489 said:
We may have to wait til we get AOSP based roms. I've tried multiple things to get wallet to work. Not going to lie, this is one reason I bough this phone was to use google wallet.
Click to expand...
Click to collapse
You bought a phone that doesn't support google wallet to run google wallet?
beaups said:
You bought a phone that doesn't support google wallet to run google wallet?
Click to expand...
Click to collapse
I'm guessing he didn't know it wouldn't be supported beforehand. Probably just saw that it had nfc capabilities and assumed it would be.
Sent from my HTC6435LVW using xda app-developers app
klarson said:
I'm guessing he didn't know it wouldn't be supported beforehand. Probably just saw that it had nfc capabilities and assumed it would be.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Verizon has been vocal about not supporting wallet on their devices. Heck, I think sprint is the only one of the big 4 that actually allows it.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Verizon has been vocal about not supporting wallet on their devices. Heck, I think sprint is the only one of the big 4 that actually allows it.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Oh I know. They're trying to push isis.
Sent from my HTC6435LVW using xda app-developers app
I am afraid they will never be available.
greenyoga said:
I am afraid they will never be available.
Click to expand...
Click to collapse
I would say it's not going to be too long before Google waps them upside the head with a suit. Verizon said no NFC mobile payment system, then releases Isis in certain markets claiming Isis uses a "secure element" and Google Wallet does not.
My guess is that Google will have a petition for injunction with the court shortly and VZW will be forced to share the requirements that allowed Isis to be used, then GW will be changed and when VZW refuses to allow it to be used again, Google will have a field day with VZW in the legal system.
One could only hope Google sues them.
It feels like I bought an Apple with all the stuff I can and can't do.
I made a topic on the Verizon website. Let's see what they come up with. Please feel free to post. Voice your opinions:
https://community.verizonwireless.com/thread/791536
I was a big Google wallet user when I had my nexus. Verizon is NOT blocking Google wallet. The problem is somewhat complex, but simplisticly speaking, to make it work, Google needs help from Verizon to use the secure element, Google can't do it on there own. Verizon will NOT help and the reason isn't totally clear, as originally Verizon said they couldn't help Google because they had a CONTRACT with Isis, and could not violate the contract. They have since not been hiding behind that reason, but with the threat of Isis sueing them, Google wallet is hands off.
The good news (or better anyway) that just because Verizon won't help, developers can. With other Verizon phones, ROMS have in fact supported it and make it work.
Earlier I said complex issue, and the complexity is that to PROPERLYmake wallet work and be A SECURE system with all the versions of android etc is not easy.
Google could easily make it work, but it can't be a success if it isn't safe and secure and would be a theft target in this form.
So our hope to see it work on this phone, is left up to the development community.
Last thing to think about is if the secure element gets changed, it will have to be dealt with again, and the developers are again the only hope for Google wallet.
Hope that clears some of it up.
Sent from my HTC6435LVW using xda premium
bigpapax said:
I was a big Google wallet user when I had my nexus. Verizon is NOT blocking Google wallet. The problem is somewhat complex, but simplisticly speaking, to make it work, Google needs help from Verizon to use the secure element, Google can't do it on there own. Verizon will NOT help and the reason isn't totally clear, as originally Verizon said they couldn't help Google because they had a CONTRACT with Isis, and could not violate the contract. They have since not been hiding behind that reason, but with the threat of Isis sueing them, Google wallet is hands off.
The good news (or better anyway) that just because Verizon won't help, developers can. With other Verizon phones, ROMS have in fact supported it and make it work.
Earlier I said complex issue, and the complexity is that to PROPERLYmake wallet work and be A SECURE system with all the versions of android etc is not easy.
Google could easily make it work, but it can't be a success if it isn't safe and secure and would be a theft target in this form.
So our hope to see it work on this phone, is left up to the development community.
Last thing to think about is if the secure element gets changed, it will have to be dealt with again, and the developers are again the only hope for Google wallet.
Hope that clears some of it up.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sorry to tell you sir but you are wrong. verizon has always requested that this app is blocked with google and the software they approve per device. plus the nexus did not work unless you side loaded the app
Spider210 said:
sorry to tell you sir but you are wrong. verizon has always requested that this app is blocked with google and the software they approve per device. plus the nexus did not work unless you side loaded the app
Click to expand...
Click to collapse
Not sure which part I am wrong in, however you are correct in the fact that they requested the app not be available in Google because they did not support it. That is why I said this is complex, but if that is what you call blocking then I guess (in its rawest form) you are correct and consider it blocked on the surface, however if you side loaded it it did work, and was not blocked from working. (just maybe a definition of blocked) is our arguement. I have a nexus too and Google wallet works perfect everytime not blocked.
The big question regardless of this, is then for the DNA users as follows: you can go to playstore and download Google wallet and no matter what you do, it does not work? Why you ask? Is Verizon blocking it? Depending on your definition of blocked then the answer is maybe? I say they are not blocking it from working on the network. Is it fair to say they are blocking it by not supporting it?
Not to make this any more unclear, but there is apparently discussion as to whether the nfc specs for the DNA can commuicate properly for Google wallet anyway. I wouldn't put it past Verizon to cripple the hardware.
Sent from my HTC6435LVW using xda premium
I don't think we will ever have Google wallet. This is a response from DSB9938, reply 84 on his system write kernel.
Besides the fact that this is not a Wallet thread, our phone has no secure element.
D
Click to expand...
Click to collapse
Google wallet in its current form needs secure element. So unless Google changes that... we are SOL
The reason we can get it on the store is because Verizon lost a case in court and was forced to allow it, so now this is their plan b.
Have spent a fair amount of time on google (and and ddg and bing, just in case google's contractually bound to stfu or anything) searching for a way to circumvent the gestapo tactics employed by at&t to filter us in to being thrilled that they will one day come out with an equivalent system to what google wallet has been offering since 2011, and i haven't found anything for this phone except for 2 people that swore it'd be done that never responded. I want to post this here, where people that tinker thrive.
I realize google wallet isn't a hot issue for most of us.. but for those of us that would like to have it and to get that experience in while the 0$ fraud liabillity extends to cards stored on our phones' memory, i'd like to ask once and for all..
is there a way to get google wallet working on an AT&T htc one? i have seen conclusive accounts of people with other phones having it working.. but through everything except having this number active on another carrier and bringing it over, i have personally not found positive results. in the three days i've been trying, i HAVE gotten gwallet force closing, getting the 'unfortunately, wallet has stopped', message, or getting bored after 5 minutes and doing something else on my phone to see the gwallet has stopped message.
if there's a guide, please post it. otherwise, if anyone has actually gotten gwallet working on AT&T's network (or off with an unlocked number and have goteen it working with at&t) please share it here.
To be honest, it's like at&t has absolute control over what goes through this phone, even when on wifi. at the very least the goal of this thread is to find out conclusively that my data isn't filtered by some master at&t .hosts file somewhere in texas ,but i'd definitely prefer to leave with a working wallet app, so chime in if you know something i dont
always overly appreciative and way too damn generous with the thanks,
me
Wrong thread sorry
KAsp3rd said:
Wrong thread sorry
Click to expand...
Click to collapse
says the first poster in an unedited post in an undefined thread
show me the way sir
also, thanks. very helpful post.
Here is what I meant to link. And actually I did edit the post http://forum.xda-developers.com/showthread.php?t=2326959
[Q]: Google Wallet on the One
Sent from my HTC One using Tapatalk 4 Beta
I havent even gotten the phone yet, it's in the mail. Thankfully i came in here to read and now i know to block ota if i want any hope of getting root.
But it leaves me wondering why do they hate rooting so much? Wireless tether is legal on Verizon and most anything else i can think of would hurt google and app devs before verizon...
Sent from my SPH-L900 using xda app-developers app
it's not just verizon. the sprint s4 has the same going on. at least according to someone i know that has one. it supposedly has something to do with the knox crap and possibly the lojack stuff they're trying to add to the phones.
i haven't bothered to confirm any of this. just got it from a bit of skimming. work's picking up a bit so i haven't been able to read as much.
It is all about security. Rooted phones do not work well with secure environments. I mean if you really think about it. With the right set up any app can be given root permissions without the user even knowing.
Wayne Tech Nexus
It also voids warranty. If I were selling a product and the consumer rendered the device useless through mods and what have you, I wouldnt want to warranty it either. One of many reasons.
SCH-I545 using Tapatalk 2
I can totally understand it---there could be a lot of headaches for the carrier. That said, I wish Verizon would not block it so much as give the user a Verizon-approved way to root with copious warnings about all the terrible things that can happen. It seems to me that would be sufficient.
Macknzie said:
I can totally understand it---there could be a lot of headaches for the carrier. That said, I wish Verizon would not block it so much as give the user a Verizon-approved way to root with copious warnings about all the terrible things that can happen. It seems to me that would be sufficient.
Click to expand...
Click to collapse
Yeah but that brings its own worries. They did give at least an option. The Dev Edition.
zelendel said:
Yeah but that brings its own worries. They did give at least an option. The Dev Edition.
Click to expand...
Click to collapse
Very true, and it's pretty clear from the name that you're getting something different.
It also presents a problem with technical support. A standardized system is far easier to troubleshoot than one wroth dozens of unknown variables.
Also, the OP is only partially correct regarding wireless tether. While Verizon cannot block users from using third party tether apps, they also have the FCC's explicit blessing to require a separate tethering fee for unlimited plan holders
Sent from my Nexus 7 using Tapatalk HD
HTC lets you unlock the bootloader via a code on their website specific for the individual phone's serial number. One clicks to waive the warranty to get the unlock code, and anyone can boot the phone into bootloader mode to see "unlocked" or "tampered" displayed. That means no warranty.
Verizon was OK with it for HTC phones.
$$$$
Its all about the money they lose so much money as a company.. even though they make billions monthly they still are all about making the consumers pay more
For the s4 its all about security. Samsung is trying to get into the corporate phone market. They released this new locked down bootloader to make companies feel all warm and fuzy. My company allows me to access my work email on my phone but to do so I have to have the phone encrypted with no root.
Sent from my SCH-I545 using xda app-developers app
onfigTr which
help...
Verizon Blocks Users from Root
Yeah, I'm having that issue myself. I have rooted my previous devices but just purchased a Motorola Turbo from VZW which is LOADED with bloatware that won't go away. So, I thought I'd go the "decent" route and see if they may be nice in return and help me unlock my phone. Holy cow, you'd think I was trying to hack Fort Knox or the Fed! The Mod at the Verizon Community Website summarily deleted my question regarding this. Well, admittedly, I probably was stupid for doing that but, again, I thought I would be "nice" about it but they decided to get nasty and tried scaring me by tell me I was "in violation of FCC regulations and my terms of service" if I even attempted to root my device and he was going to "open an investigation into my "hacking" activities." Wow, talk about a Mod with delusions of god-hood! Okay, illegal to root MY phone, which I PAID for. So, I called VZW CS (I hate talking) and explained my issue and got a complete dolt (as expected) who didn't have a clue even what the Verizon Community Website was...fact is, my only desire is to remove the damn bloat-ware, ads, etc. and increase the battery life. This phone has such potential and they lock it down to such extremes, it's really disappointing. Finally, I got fed up and asked for her supervisor, who was not much better. Supposedly, she is escalating this to Tier 3 Support. Permission to have root access to MY own phone. I was a sys admin for 25+ years and never had to ask permission for root access for my computers...
Suggestions?
qballrail said:
Suggestions?
Click to expand...
Click to collapse
Buy a Nexus 6p or 5x.
A little late for that.
I thought the new Droid Turbo just got root and bootloader unlock... I think it was RootJunky or DroidModderX who just put up a video on that...
That said, like smitchell said, it's Samsung trying to capture the corporate market from Blackberry, and Verizon wanting money from users, combining to screw over people like us who want to flash custom software.
qballrail said:
A little late for that.
Click to expand...
Click to collapse
No. They're still being sold.
mike.s said:
No. They're still being sold.
Click to expand...
Click to collapse
You misunderstand, Friend. I meant that I had purchased my Motorola Turbo too recently, so the prospect for purchasing another would be impossible at this time.
---------- Post added at 09:22 PM ---------- Previous post was at 09:20 PM ----------
XxD34THxX said:
I thought the new Droid Turbo just got root and bootloader unlock... I think it was RootJunky or DroidModderX who just put up a video on that...
That said, like smitchell said, it's Samsung trying to capture the corporate market from Blackberry, and Verizon wanting money from users, combining to screw over people like us who want to flash custom software.
Click to expand...
Click to collapse
From what I've read, Verizon has made it impossible to do, unless you want to pay $20 for mofo, and that's no guarantee. Where is this video?
Thanks!
Verizon is evil. I have a Galaxy Note Pro from them that I can't even put linux on due to the locked bootloader and kernel without chroot. It's a sad state of affairs. The government should have laws for giving consumers rights to use their devices as they wish
Sent from my SCH-I545 using Tapatalk
qballrail said:
You misunderstand, Friend. I meant that I had purchased my Motorola Turbo too recently, so the prospect for purchasing another would be impossible at this time.
---------- Post added at 09:22 PM ---------- Previous post was at 09:20 PM ----------
From what I've read, Verizon has made it impossible to do, unless you want to pay $20 for mofo, and that's no guarantee. Where is this video?
Thanks!
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ZnfCtvYawVc
http://www.droid-life.com/2013/10/2...:+DroidLife+(Droid+Life)&utm_content=Facebook
Sent from my SCH-I535 using Tapatalk
Just a company who thought they could add Google play without permission. Google will shoot down their request and people will have to sideload like we do on gg
Sent from my SCH-I605 using Tapatalk
...you're on XDA. And you're worried about play store access.
I reiterate...
...you're on XDA? And worried about play store access?
I'll make something that roots the device and sideloads the app store and google services all in one button. Don't worry your pretty little head. If that's the only thing they get wrong, then it's still the best device to date.
ClearD said:
...you're on XDA. And you're worried about play store access.
I reiterate...
...you're on XDA? And worried about play store access?
I'll make something that roots the device and sideloads the app store and google services all in one button. Don't worry your pretty little head. If that's the only thing they get wrong, then it's still the best device to date.
Click to expand...
Click to collapse
That's not my point! They lied to the consumer and cannot be trusted as a whole. They have been funded on kickstarter based on a lie, not just a small lie, but a giant fraudulent, refund my $ you bastards sized lie.
Root or no root, they sold it as a Google Play store accessible device. And it isn't!
Sent from my SCH-I535 using Tapatalk
kevinb77 said:
That's not my point! They lied to the consumer and cannot be trusted as a whole. They have been funded on kickstarter based on a lie, not just a small lie, but a giant fraudulent, refund my $ you bastards sized lie.
Root or no root, they sold it as a Google Play store accessible device. And it isn't!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
They're still working on it, actually, and my understanding is that no 240x240 screen sized device will be capable of supporting it under android 4.3, so they may have it out when they update to 4.3, pending Google's say-so.
So a device that does not have certification for a version of Android that doesn't even exist yet is a fraud?
As far as it not coming on the Android 4.2.2 version, that was public knowledge back in early September.
Oh BTW
"While all efforts are made to ensure timely completion of software functions, software development too can have unforseeable delays which may result in software functions being delivered in an update after a product has shipped."
On the Omate KS page since Aug 21st 2013
Hell. At least they updated you about it vs threatening folks publicly when ever anybody brought up any real issues.
BAWWWWWWWWWW QQ more. This isn't new knowledge and you're an idiot for thinking a company is a fraud because they hit a hiccup they didn't count on when bringing their product to the US.
This is XDA. You're complaining in the wrong place.
Sent from my Galaxy Nexus using Tapatalk 2
kevinb77 said:
That's not my point! They lied to the consumer and cannot be trusted as a whole. They have been funded on kickstarter based on a lie, not just a small lie, but a giant fraudulent, refund my $ you bastards sized lie.
Root or no root, they sold it as a Google Play store accessible device. And it isn't!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Are you serious?!? Name at least one crowdfunding campaign that treated their backers with as much respect, which had as many detailed updates, which had stayed on schedule, which has worked so hard around the globe? They came up front about Play store hiccup and even offered an alternative of another on-line store until they will resolve licensing issue with Google (which btw they are working on actively).
I don't understand everyone defending this "upfront" action they decided to take after a Google exec put the kabash on the Play store on this device last week. But I work for a manufacturer of medical devices and if we advertise something to be in our product it has to be there or we would get our assess sued into bankruptcy. My point was that they should have never advertised the device as a Google Play store capable device if they didn't have all their ducks in a row. Business wise, it's unethical and in other markets even criminal.
Sent from my SCH-I535 using Tapatalk
Probably because we aren't assholes.
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Probably because we aren't assholes.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No need for name calling man. I'm just trying to wrap my head around this situation.
Sent from my SCH-I535 using Tapatalk
I wasn't calling you one. I will say none of your posts indicated you were trying to understand this so much as belittling those who don't agree with you.
If you want to discuss it, let's discuss it. Don't patronize people.
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
I wasn't calling you one. I will say none of your posts indicated you were trying to understand this so much as belittling those who don't agree with you.
If you want to discuss it, let's discuss it. Don't patronize people.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I certainly was not trying to belittle anyone in the XDA universe.
But the solution of sideloading the Play Store apk is unsettling to me. I own an OUYA and was an early adopter of one of the first Android tablets, the Viewsonic G-book. I have also been rooting and roming since the DROID 1. While ROMS and sideloading is great, it's just unstable and in some situations becomes a full-time job of keeping up with updates and fixes.
I love messing with my devices as much as anyone else here, but for once I'd like to just buy an Android device that I didn't feel the need to have to change in someway, and spending upwards to $300 on an Android device in 2013 with its fair amount of promises should deliver on them.
Sent from my Nexus 10 using Tapatalk HD
I agree with you completely and feel the same way but we need to draw the line here at calling it fraud.
I'm comfortable enough with side loading that it isn't an issue but the developer model is what is being discussed. November 30th is a long ways away in shipping terms and until they definitively say no I just think it's better not to get up in arms about it. Let them do their thing. Believe me when I say that if they screw this up they will sink.
Sent from my Galaxy Nexus using Tapatalk 2
kevinb77 said:
I don't understand everyone defending this "upfront" action they decided to take after a Google exec put the kabash on the Play store on this device last week.
Click to expand...
Click to collapse
ORLY. AGAIN, the play store (Google Services) issue was a matter of public knowledge for over a month.
kevinb77 said:
My point was that they should have never advertised the device as a Google Play store capable device if they didn't have all their ducks in a row. Business wise, it's unethical and in other markets even criminal.
Click to expand...
Click to collapse
Should they have removed the mention of Play Store being included back in early Sept? In my opinion yes. The release that recently came out should have also been done back then as well. "unethical"? Maybe. Criminal? No. The disclaimer that was a the bottom of their KS since day one covers their ass. Period, end of story, thanks for playing.
kuronosan said:
I agree with you completely and feel the same way but we need to draw the line here at calling it fraud.
I'm comfortable enough with side loading that it isn't an issue but the developer model is what is being discussed. November 30th is a long ways away in shipping terms and until that definitively say no I just think it's better not to get up in arms about it. Let them do their thing. Believe me when I say that if they screw this up they will sink.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
All the KS units are in the clear. The pre-orders may be another matter.
In my book, the campaign of AI Watch is fraudulent. Regarding Omate, I have a pretty good feeling that even if they would have published this disclaimer while campaign was active - they still would have gotten as much supporters/backers because for a lot of the people not including Google play store is not a show stopper. With a ways around it (sideloading), and alternative store, and active updates about working with Google to resolve this officially, I still say they built a strong community trust.
Btw, with Google planning to release their own smartwatch and probably a pressure from tanking Gear, something tells me there are political reasons for Google to continue delaying their decision. Just my conspiracy theory
vectron said:
In my book, the campaign of AI Watch is fraudulent.
Click to expand...
Click to collapse
At least Omate have admitted that Google Play support won't be there out the box, unlike AI Smartwatch, which is in the same position. They are still giving the impression it comes with Play store.
ClearD said:
...you're on XDA. And you're worried about play store access.
Click to expand...
Click to collapse
I think its really funny how people are complaining so much about it. i mean i am disappointed my self as its part of why i've pre ordered the 8gb 1gb omate truesmart but it wasn't the main reason the main reason is because its the best smart watch there is so far. I'm no programmer but I can still install apps etc so it wont be too hard for people to install them, them self's once someone provides us with them to install.
as for no smart watches coming with play store i have the omate prototype on my wrist right now (re-branded as simvalley aw-414.go) and it has play store built into the rom. i know because i factory reset it and it was still there. that being said i hope they make an update for the one I'm wearing right now as it has some terrible bugs on the ui that make it not so good for using some apps show multiple copy's of their icons and you can not remove any of them without uninstalling said apps, after you put so many apps on it some start to vanish and can only be seen if you search for them, it looks like they tried hybrid the app drawer and the home screens as their is no home screens so no widgets or only showing apps you want to see. it also has folders but their useless as you can only put 3 apps in them. it becomes useless if i install a different launcher to fix the other issues. do you think omate firmware would work on it ? because the firmware thats on it says omate_hw2.0_20130923.1 and the model number says omate too.
if someone releases firmware for it that works properly it would be not so bad and very similar to the lower spec omate internals wise? as it seems to be reasonable for its specs if you ignore those software bugs that should have been fixed before release.
NachTSS said:
I think its really funny how people are complaining so much about it. i mean i am disappointed my self as its part of why i've pre ordered the 8gb 1gb omate truesmart but it wasn't the main reason the main reason is because its the best smart watch there is so far. I'm no programmer but I can still install apps etc so it wont be too hard for people to install them, them self's once someone provides us with them to install.
as for no smart watches coming with play store i have the omate prototype on my wrist right now (re-branded as simvalley aw-414.go) and it has play store built into the rom. i know because i factory reset it and it was still there. that being said i hope they make an update for the one I'm wearing right now as it has some terrible bugs on the ui that make it not so good for using some apps show multiple copy's of their icons and you can not remove any of them without uninstalling said apps, after you put so many apps on it some start to vanish and can only be seen if you search for them, it looks like they tried hybrid the app drawer and the home screens as their is no home screens so no widgets or only showing apps you want to see. it also has folders but their useless as you can only put 3 apps in them. it becomes useless if i install a different launcher to fix the other issues. do you think omate firmware would work on it ? because the firmware thats on it says omate_hw2.0_20130923.1 and the model number says omate too.
if someone releases firmware for it that works properly it would be not so bad and very similar to the lower spec omate internals wise? as it seems to be reasonable for its specs if you ignore those software bugs that should have been fixed before release.
Click to expand...
Click to collapse
I'm sure if it doesn't work right out of the box, we can make you a rom from the Omate that will work quite easily.
Sent using XDA-funded carrier pigeons
ClearD said:
I'm sure if it doesn't work right out of the box, we can make you a rom from the Omate that will work quite easily.
Sent using XDA-funded carrier pigeons
Click to expand...
Click to collapse
It does not sadly. I mean its still useable but the issues it does have make it not very good to use so it really needs a rom that works properly.
the rom thats on it is custom build version: OMATE_HW2.0_20130923.115849 and the model number is listed as OMATE.
but yeah I'd be really grateful if someone does make a custom rom for it that works properly and tells me which google play store version to install and were to get the apk etc, I'm also guessing they would need to make a rooting app for it too so it could be flashed tho right?
http://www.verizonwireless.com/dam/support/pdf/system_update/galaxys4.pdf
I woke up this morning and on my phone was a request to update from Verizon, it was an official update.
I haven't seen anything anywhere and I can't believe that I am one of the first on XDA to get this;
I go first!
Lol :laugh:
Lol, spam is spam!
Sent from my SCH-I545 using Tapatalk
No offense, but you are a little late to the party. The update has been out for a week now.
See these threads:
http://forum.xda-developers.com/showthread.php?t=2731099 - Thread created on first rollouts
http://forum.xda-developers.com/showthread.php?t=2658480 - Discussion thread
The only nice thing is that VZW finally released info on the update.
Omega360 said:
No offense, but you are a little late to the party. The update has been out for a week now.
See these threads:
http://forum.xda-developers.com/showthread.php?t=2731099 - Thread created on first rollouts
http://forum.xda-developers.com/showthread.php?t=2658480 - Discussion thread
The only nice thing is that VZW finally released info on the update.
Click to expand...
Click to collapse
I didn't think I was the first but I haven't been following lately so I didn't see anything. How do you get rid of that constant nag?
What is so exciting about an update that essentially kills write permissions to the SD card and adds more bloat? Not being sarcastic. Just do not see the benefit. S4 seems fine, pre update.
JMO
rushless said:
What is so exciting about an update that essentially kills write permissions to the SD card and adds more bloat? Not being sarcastic. Just do not see the benefit. S4 seems fine, pre update.
JMO
Click to expand...
Click to collapse
Didn't add more bloat. Please explain in detail what bloat you are talking about. Most bloat can be turned off. As a matter of fact, one of the best parts of the update is the ability to disable bloat from the app drawer. Also, 4.4 added the framework for Tap to Pay. There are plenty of reasons to update. Kit Kat runs better for me and has features I find very useful.
Sent from my SCH-I545 using XDA Premium 4 mobile app
MedleHed said:
Didn't add more bloat. Please explain in detail what bloat you are talking about. Most bloat can be turned off. As a matter of fact, one of the best parts of the update is the ability to disable bloat from the app drawer. Also, 4.4 added the framework for Tap to Pay. There are plenty of reasons to update. Kit Kat runs better for me and has features I find very useful.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe you can disable KNOX(crap) without root. There are probably a few other verizon apps that cannot be disabled without root.
Knox? I haven't had a problem with it... It does nothing on my phone. Can you please explain what your problem is with Knox?
Sent from my SCH-I545 using XDA Premium 4 mobile app
You CAN disable knox....The only thing I wish I could disable that u can't is the stupid security update notifications
Sent from my SCH-I545 using xda app-developers app
It's not that it's a bad update by any means, 4.4 code has a lot of efficiencies over 4.3, but with as long as the wait was i guess people over hyped it and expected more new end-user features.
Sent from my SCH-I545 using XDA Premium 4 mobile app
My phone didn't show the update till a few hours ago. At first I was semi excited, then I remembered I still plan on rooting the crap out of the thing..... Verizon and their slow nonsense don't sit well with me sometimes.
D3Seeker said:
My phone didn't show the update till a few hours ago. At first I was semi excited, then I remembered I still plan on rooting the crap out of the thing..... Verizon and their slow nonsense don't sit well with me sometimes.
Click to expand...
Click to collapse
If you want the update and be rooted, go here --> http://forum.xda-developers.com/showthread.php?t=2726868
rushless said:
What is so exciting about an update that essentially kills write permissions to the SD card and adds more bloat? Not being sarcastic. Just do not see the benefit. S4 seems fine, pre update.
JMO
Click to expand...
Click to collapse
Honestly, the SD card "issue" is so overblown its not funny. It doesn't kill write permissions... what it does do, is make it so that apps don't have the right to go willy nilly across you card, to folders it shouldn't have permission to (unless you agree that a random app you download should have the ability to muck with other programs folders).
I made the jump on my phone more than a month ago, and my day to day impacts are NILL. Poweramp still plays all my music just fine, and not one program has had a FC or any other issue. In fact, had i not read articles from other people about the sky falling, i would have never known anyway....
Divine_Madcat said:
Honestly, the SD card "issue" is so overblown its not funny.
Click to expand...
Click to collapse
It's an unexpected, undocumented change. That you don't run applications which get broken doesn't mean that others aren't hurt by it.
Google is the new Microsoft - they think because they're successful they can do no wrong, but in reality they're clueless about a lot of things. Big enough to not care, and it's the users who get hurt.
Adding *nix permissions to a vfat volume is the right thing to do (short of requiring a modern file system on an SD card), but they're doing it wrong by not phasing it in so apps can accommodate the change.
Well, fill me in. What broke? What app needs to write willy nilly to folders it shouldn't be in that is now no longer working?
For all the moaning people give, i seem to have trouble finding REAL problems...
Divine_Madcat said:
Well, fill me in. What broke? What app needs to write willy nilly to folders it shouldn't be in that is now no longer working?
For all the moaning people give, i seem to have trouble finding REAL problems...
Click to expand...
Click to collapse
Subsonic is one example. Here's a detailed explanation with another example.
Your Google-fu is weak.
mike.s said:
Subsonic is one example. Here's a detailed explanation with another example.
Your Google-fu is weak.
Click to expand...
Click to collapse
At the end of the thread, its reported fixed, and your other article is from 2012 and has nothing to do with any of this.
Keep trying....
As it is.. apps may write to any folder they own, and may read from every folder. Unless the app is badly written, this change should honestly be a non issue.
Divine_Madcat said:
Honestly, the SD card "issue" is so overblown its not funny.
Click to expand...
Click to collapse
I agree 100%
Divine_Madcat said:
At the end of the thread, its reported fixed, and your other article is from 2012 and has nothing to do with any of this.
Keep trying....
As it is.. apps may write to any folder they own, and may read from every folder. Unless the app is badly written, this change should honestly be a non issue.
Click to expand...
Click to collapse
LOL. It was "fixed" by manually changing things in the application, fortunately the app had a setting where the storage path can be configured by the user, many don't. KitKat broke something which worked before because it introduced new restrictions with no prior warning to developers.
The linked article is about this issue, exactly. You didn't read the comments, did you? Or try searching ? The change has been around for a while (back to Honeycomb), but manufacturers worked around it for most devices. Now Google seems to be enforcing it as a requirement with KitKat (or Samsung decided to not do the work-around anymore, we'll see). Maybe it's not causing you problems, but it is causing problems for people.