If anyone can help with this, I’d really appreciate it. I have been a little disappointed since plunging into Android that for whatever reason, the email app (not Gmail) doesn’t have a “move to folder” option. I’ve had this option on WinMo and Symbian phones so I found it hard to believe that functionality wasn’t in Android. FYI, I am currently running CM 6.1.1.
Well I bought my wife a Samsung Epic 4G for Christmas and lo and behold, the email app on her device has that option! Her phone is rooted and running the Epic Experience ROM. I have tried, to no avail, to put the email app from her phone onto my N1. I have the apk file, have tried to just install as is, have tried pushing via adb, even tried inserting it into the CM ROM zip file in place of the one that was in there. So far I’m not even close. So here are my questions:
Are there any ROMs for the N1 that have this function included?
If not, is it possible to install this in place of the email app in CM?
I’m rather fond of CM and would rather do the latter if it’s possible. I was able to get as far as getting the file signed, and the closest I got after that, I received the error:
INSTALL FAILED MISSING SHARED LIBRARY
With over 200 lib files in the Epic ROM, I have no idea which one(s) would be necessary to make this work. Both phones have Android 2.2.1.
Again, any help would be greatly appreciated!
No help on this at all? C'mon folks, I know we've got some smart people in here that can make this work!
So when I first got the HTC One (on ATT) I was super pissed to find out Google Wallet or Google Hangouts (the A/V) portion was somehow disabled.
I've wanted to keep my phone stock (or stock-ish) so the most invasive thing I've tried was TrickDroid. Still no dice.
Finally, I figured that the GE edition ROMs would stop this tomfoolery, nope... still blocked.
So my questions are:
1) Are there any (hacky) ways to get this apps working?
2) Via what methods are they being block?
3) If it is truly ATT being the jerks here, does anyone want to help me create a ****-storm about this?
I know carrier blocking apps is old but coming from Tmo, this is really, really pissing me off.
No matter what you do, Google wallet wont work properly, as the One doesnt have the required secure element to run it.
As for hangouts, they are working fine for me, not sure what might be happening there...
cowmixtoo said:
So when I first got the HTC One (on ATT) I was super pissed to find out Google Wallet or Google Hangouts (the A/V) portion was somehow disabled.
I've wanted to keep my phone stock (or stock-ish) so the most invasive thing I've tried was TrickDroid. Still no dice.
Finally, I figured that the GE edition ROMs would stop this tomfoolery, nope... still blocked.
So my questions are:
1) Are there any (hacky) ways to get this apps working?
2) Via what methods are they being block?
3) If it is truly ATT being the jerks here, does anyone want to help me create a ****-storm about this?
I know carrier blocking apps is old but coming from Tmo, this is really, really pissing me off.
Click to expand...
Click to collapse
TheBishopOfSoho said:
No matter what you do, Google wallet wont work properly, as the One doesnt have the required secure element to run it.
Click to expand...
Click to collapse
Blatant misinformation. I know for a fact that you can get Google Wallet to run on the HTC One. Someone mentioned it earlier and took pictures to prove it. He even posted how he was able to do it, but I wasn't interested in rooting my phone, so I didn't look into it any further.
Oh, and as for Hangout, my HTC One came with Google Talk, and after a normal Play Store update, it changed to "Hangout" (Rogers HTC One, not rooted).
cowmixtoo said:
Google Hangouts (the A/V) portion was somehow disabled.
Click to expand...
Click to collapse
I know att announced that the av portion (video chat) will be enabled over the next few months. Starting with unlimited users and going down the line. I think it works for me now as I am on the unlimited data plan.
Also search there is a hack if rooted to allow this now. You have to modify a file.
As far as wallet. Att Verizon and t mobile have rejected wallet for there own proprietary system called Isis. Currently only available in salt lake city and Austin. www.paywithisis.com
It sucks because they have not expanded the system beyond those 2 cities in a long time.
Sent from my HTC One using xda premium
WhatsAUsername said:
Blatant misinformation. I know for a fact that you can get Google Wallet to run on the HTC One. Someone mentioned it earlier and took pictures to prove it. He even posted how he was able to do it, but I wasn't interested in rooting my phone, so I didn't look into it any further.
Click to expand...
Click to collapse
Wohah there. Unless you have a source that isn't blatent misinformation. Google wallet is not offically supported on the HTC One unless you are on the sprint network in the states. Source: http://support.google.com/wallet/bin/answer.py?hl=en&answer=1347934
As the model in question is the AT&T version he is telling the truth. Getting it to work otherwise is a hack.
WhatsAUsername said:
Blatant misinformation. I know for a fact that you can get Google Wallet to run on the HTC One. Someone mentioned it earlier and took pictures to prove it. He even posted how he was able to do it, but I wasn't interested in rooting my phone, so I didn't look into it any further.
Oh, and as for Hangout, my HTC One came with Google Talk, and after a normal Play Store update, it changed to "Hangout" (Rogers HTC One, not rooted).
Click to expand...
Click to collapse
"Blatant" misinformation? Hardly. Try googling it, only Sprint editions of the One support wallet, there are many and varied references to other One versions lacking the hardware to support Wallet in its current incarnation.
How's this?
One thing worth mentioning: The HTC One Google Play Edition doesn't come with Google Wallet -- and the app also isn't available for installation on the device via the Play Store. (Wallet is installed on the GS4 Play Edition.) A Google spokesperson tells me this is due to the One's hardware lacking an embedded secure element that Wallet requires in order to run.http://blogs.computerworld.com/android/22397/galaxy-s4-htc-one-google-play-editions
So there's a hardware deficiency on the GSM version?
Why even both putting NFC on the phone?
BarryH_GEG said:
How's this?
One thing worth mentioning: The HTC One Google Play Edition doesn't come with Google Wallet -- and the app also isn't available for installation on the device via the Play Store. (Wallet is installed on the GS4 Play Edition.) A Google spokesperson tells me this is due to the One's hardware lacking an embedded secure element that Wallet requires in order to run.http://blogs.computerworld.com/android/22397/galaxy-s4-htc-one-google-play-editions
Click to expand...
Click to collapse
cowmixtoo said:
So there's a hardware deficiency on the GSM version?
Why even both putting NFC on the phone?
Click to expand...
Click to collapse
NFC has other uses as well. You can share things easily between phones. Also some places have NFC payments without google wallet. In Canada Rogers and CIBC have teamed up and made NFC payments for the s3 (another phone without google wallet).
Google Wallet is the biggest NFC payment network for a phone. For people coming from Wallet devices (like I had the GN and the N4 before) this is an insane let down.
I would have never bought the HTC Onc and moved to ATT if this lack of functionality was made clear.
bobruels44 said:
NFC has other uses as well. You can share things easily between phones. Also some places have NFC payments without google wallet. In Canada Rogers and CIBC have teamed up and made NFC payments for the s3 (another phone without google wallet).
Click to expand...
Click to collapse
cowmixtoo said:
Google Wallet is the biggest NFC payment network for a phone. For people coming from Wallet devices (like I had the GN and the N4 before) this is an insane let down.
I would have never bought the HTC Onc and moved to ATT if this lack of functionality was made clear.
Click to expand...
Click to collapse
All it took me to look up was a quick google search. And Google Wallet is only the biggest NFC payment system in the UnS. Everywhere else does not have that option. NFC does have other uses, limited yes, but other ones.
Carrier Issue
IMO, this is a carrier's issue or fault, not HTC's.
bobruels44 said:
the s3 (another phone without google wallet).
Click to expand...
Click to collapse
dgtiii said:
IMO, this is a carrier's issue or fault, not HTC's.
Click to expand...
Click to collapse
You're both missing the point. The issue being discussed is a h/w issue where, for some reason, HTC's omitted the secure element in the NFC chip they use that Google Wallet (and any other payment systems) is dependent on. Carrier's block access to Google Wallet but if the phone's properly equipped h/w wise you can work around it. You can't work around the absence of a secure element. If you want to know what the secure element does do a Google search on "Google Wallet secure element."
BarryH_GEG said:
You're both missing the point. The issue being discussed is a h/w issue where, for some reason, HTC's omitted the secure element in the NFC chip they use that Google Wallet (and any other payment systems) is dependent on. Carrier's block access to Google Wallet but if the phone's properly equipped h/w wise you can work around it. You can't work around the absence of a secure element. If you want to know what the secure element does do a Google search on "Google Wallet secure element."
Click to expand...
Click to collapse
For the s3 I was not talking about google wallet there. I was talking about the Canadian variant of the s3. Google wallet is not available up here on any device on any carrier. That's why I was mentioning that. I may be incorect about the hardware component on that variant however my point of there are alternatives in other outcries remains.
So, is the problem with NFC a physical hardware piece, or can it be fixed with software? "Lack of a secure element" is why Verizon blocked Google Wallet on the Verizon Galaxy Nexus but that still ended up working.
dsass600 said:
So, is the problem with NFC a physical hardware piece, or can it be fixed with software? "Lack of a secure element" is why Verizon blocked Google Wallet on the Verizon Galaxy Nexus but that still ended up working.
Click to expand...
Click to collapse
You guys are confused. Here's what a secure element is and does...
If you're not familiar with how Wallet functions, it's a bit odd as an application goes. The Wallet app isn't the only "piece" necessary to get the Wallet service functioning, there are two other parts of the equation. One you're already familiar with: NFC (near-field communication). It's a simple, open wireless standard that transmits data over very short distances. In Wallet's case, it transmits payment data. But there's a third wheel in play that many people aren't aware of, and it's called a "secure element." Without getting too technical (eg, into things I don't at all understand), the secure element's job is to store encrypted credentials (your payment info) and tell the Wallet app "hey, these are the credentials you need to transmit to the payment terminal."
Only one card's credentials are stored on the element at a given time (obvious security reasons), which is why you need an internet connection if you want to switch your active card in Wallet. When you sign in to Wallet or change cards, the Wallet app calls up to the Google server, pulls down your credentials for a particular card, and then writes them to the secure element.
But one does not simply write to the secure element (... or walk into Mordor), it requires special permissions. Google Wallet is doing something few apps do - asking for direct, exclusive access to a secure piece of hardware in the phone. Not only that, once Google takes over the secure element, it wants total control. Because of the security concerns (and related technical difficulties) involved in sharing a secure element, Wallet and only Wallet is able to utilize the internal secure element on a Wallet-enabled device. That means Google is directly managing every layer of the process. http://www.androidpolice.com/2013/0...why-the-carrier-is-still-allowed-to-block-it/
People got Wallet working on the VZW GN by side-loading it; much like everyone else who's running Wallet even though it's not carrier or region supported for their particular device . VZW's beef is that they don't trust third parties to use security-enabled h/w that VZW can't control on VZW-sold devices. When VZW realized people were by-passing the process they, with Google's help, did the following...
So Google Wallet has never officially been available for Verizon, on any smartphone. However for months now users have been able to side-load Google’s awesome Wallet app for mobile NFC payments using the web store, or installing a custom ROM. Today however it appears that Google’s pulled the backend plug. http://androidcommunity.com/google-wallet-gets-pulled-from-verizon-galaxy-nexus-20120914/
If the VZW GN didn't have a secure element Wallet would have never worked. The only two phones I've heard about without a secure element are the DNA/Butterfly and the One (except apparently for Sprint).
BarryH_GEG said:
You guys are confused. Here's what a secure element is and does...
If you're not familiar with how Wallet functions, it's a bit odd as an application goes. The Wallet app isn't the only "piece" necessary to get the Wallet service functioning, there are two other parts of the equation. One you're already familiar with: NFC (near-field communication). It's a simple, open wireless standard that transmits data over very short distances. In Wallet's case, it transmits payment data. But there's a third wheel in play that many people aren't aware of, and it's called a "secure element." Without getting too technical (eg, into things I don't at all understand), the secure element's job is to store encrypted credentials (your payment info) and tell the Wallet app "hey, these are the credentials you need to transmit to the payment terminal."
Only one card's credentials are stored on the element at a given time (obvious security reasons), which is why you need an internet connection if you want to switch your active card in Wallet. When you sign in to Wallet or change cards, the Wallet app calls up to the Google server, pulls down your credentials for a particular card, and then writes them to the secure element.
But one does not simply write to the secure element (... or walk into Mordor), it requires special permissions. Google Wallet is doing something few apps do - asking for direct, exclusive access to a secure piece of hardware in the phone. Not only that, once Google takes over the secure element, it wants total control. Because of the security concerns (and related technical difficulties) involved in sharing a secure element, Wallet and only Wallet is able to utilize the internal secure element on a Wallet-enabled device. That means Google is directly managing every layer of the process. http://www.androidpolice.com/2013/0...why-the-carrier-is-still-allowed-to-block-it/
People got Wallet working on the VZW GN by side-loading it; much like everyone else who's running Wallet even though it's not carrier or region supported for their particular device . VZW's beef is that they don't trust third parties to use security-enabled h/w that VZW can't control on VZW-sold devices. When VZW realized people were by-passing the process they, with Google's help, did the following...
So Google Wallet has never officially been available for Verizon, on any smartphone. However for months now users have been able to side-load Google’s awesome Wallet app for mobile NFC payments using the web store, or installing a custom ROM. Today however it appears that Google’s pulled the backend plug. http://androidcommunity.com/google-wallet-gets-pulled-from-verizon-galaxy-nexus-20120914/
If the VZW GN didn't have a secure element Wallet would have never worked. The only two phones I've heard about without a secure element are the DNA/Butterfly and the One (except apparently for Sprint).
Click to expand...
Click to collapse
Wow. Thank you for that reply. Just one thing I'm confused about. Last year, the Galaxy S3 did not have a secure element, but the Sprint version did, so people were taking some lib files from the Sprint version, putting them on their S3s, and getting Google Wallet to work. With that in mind, does this mean that the secure element is software that could potentially be added on afterwards by, possibly, a third party source like someone on XDA, or does it have to be built into the phone initially?
dsass600 said:
Wow. Thank you for that reply. Just one thing I'm confused about. Last year, the Galaxy S3 did not have a secure element, but the Sprint version did, so people were taking some lib files from the Sprint version, putting them on their S3s, and getting Google Wallet to work. With that in mind, does this mean that the secure element is software that could potentially be added on afterwards by, possibly, a third party source like someone on XDA, or does it have to be built into the phone initially?
Click to expand...
Click to collapse
+1. Really great explanation of secure elements but I also agree. I had the galaxy s3 to mobile edition and all files, libs and what not where pulled from the sprint version and made flashable to all s3s.
Sent from my HTC One using Tapatalk 4 Beta
TheBishopOfSoho said:
"Blatant" misinformation? Hardly. Try googling it, only Sprint editions of the One support wallet, there are many and varied references to other One versions lacking the hardware to support Wallet in its current incarnation.
Click to expand...
Click to collapse
I'm glad someone already posted that link about people getting it working before I came back to check this thread. Stop misleading people. I already told you previously that I understood the lack of a secure element, but that it was still possible (at least at one point) to get it working. There's no need to put down others just because you feel so sure about your own knowledge. -.-
dsass600 said:
Last year, the Galaxy S3 did not have a secure element, but the Sprint version did, so people were taking some lib files from the Sprint version, putting them on their S3s, and getting Google Wallet to work.
Click to expand...
Click to collapse
All Samsung's NFC-equipped devices have a secure element (which is h/w). What you guys are talking about is missing s/w necessary to provide access to it. I'm guessing in the cases you're mentioning they were carrier SGS3's and the missing s/w was a carrier-requested "enhancement" specific to their SGS3. It's kind of like carrier's pulling the FM radio s/w but leaving the h/w which allows people to later get the functionality back.
http://nfctimes.com/news/samsung-embed-secure-element-galaxy-s-iii-other-nfc-phones
In the case of the DNA/Butterfly and non-Sprint One’s the physical secure element has been omitted and no amount of s/w can reverse that.
This is a pure guess on my part but HTC not providing a secure element is probably because they don't want to deal with the administration of it. Much like MAC addresses, secure elements are serialized and need to be tracked on a per-device basis which means maintaining a database and supporting Google in dealing with borked secure elements (which happens a lot). And that includes replacing the NFC chip if the secure element gets borked which would/could be a warranty claim. With so little carrier support for Wallet it's not a bad strategy as outside XDA people wouldn't miss access to it. And as far as I know Wallet's the only app that currently requires the presence of a secure element.
I finally got around to installing the Lollipop OTA update yesterday and I've been going through some articles looking for new features. One awesome-looking feature is the guest user feature. The only problem is that I can't seem to find a menu item for this in the settings, nor is there the user icon next to the settings icon in the notification tray. Am I missing something or is this not a feature that is included in the Sprint version?
Perhaps a more relevant question would be, for those of you that have lollipop installed on your Sprint HTC One, do you have access to the guest users feature?
A simple yes by at least one person would let me know that it is a problem with my phone and not an oversight by Sprint.
Thanks!
I just talked to Sprint customer service and I was assured that the user account feature is supposed to be in this release. I was told to go to Settings -> Device -> Users. Unfortunately, there is no Device menu in Settings on my phone. Can some of you respond if you are seeing the same issue? Sprint is opening a ticket but I'd like to tell them that this isn't just affecting me, if that is the case.
I'll keep everyone updated.
Same deal here. I just installed the update and I can't find the multi-users feature anywhere. I have the M8 HK Edition
HTC does not include multiuser on any sense Rom. It's is included on the GE edition and u can use it in any lollipop Aosp and some KK Aosp toms.