Just installed TSM Resurrection 1.0 today on my VZ Fascinate, no other custom stuff yet. Works great except I can't restore or install my purchased Touchdown for Exchange license key. When searching the Market on the device, it doesn't come up at all. When I search on the Market website, it shows that the License is incompatible with my device, which is now listed as a "Mid-Tex Cellular Samsung SCH-i500".
I assume Mid-Tex is where the kernel or radio is from...but is there any way to force compatibility, or change the device string, or otherwise get this key installed?
I know others were having issues with Verizon apps that weren't installing on the previous TSM...but their problems seem to have gone away with this version while this one remains.
I would post in the dev section under the appropriate thread but I don't have enough permission yet.
Thanks!
UPDATE: after emailing the dev, they issued a registration code in lieu of the key app.
Related
As topic states Im having trouble with a program called Navizon. I have tried uninstalling and reinstalling numerous times, including removing all registry entried for navizon. each time it installs fine, however when I go to start the program I get this:
Navizon.exe - Native Exception
A Native Exception Occurred.
ExceptionCode: 0x80000002
ExceptionAddress: 0x00e28328
OK to terminate
CANCEL to debug
hitting cancel and ok both boot me back to programs list
I have a post on navizons tech support forum, and there have been two people with advantages who have successfully installed and ran the program...as far as I can tell the only difference is our roms. Of course im running the greatest ever, AP Dual Black 3.0 rom. Do you guys have any advice as to what could be causing my error? If you want to check out my post on their tech support forum, heres the link.
http://www.navizon.com/phpbb2/viewtopic.php?t=1658
just an update, did a hard reset, and installed Navizon works great, had to be a scummy program conflicting
I thought I was having a Cyanogen issue, but it turns out this is happening with every rom I've tried. I'll get the rom(Cyanogen 7 stable, latest nightly, Vegan Ginger edition, Calkulin's) and when I try and download a rom, it begins the download then stops, telling me "download was unsuccessful, please try again". I used to be able to get twenty or so apps installed before this became an issue, but now it starts right out the gate. I've NVFlashed a couple of times, still get this happening. I've partitioned the memory(2048/0 I believe), so that's not the issue. Also tried clearing market data, etc, nothing. I'll try another NVFlash tonight, but does anyone have a simpler solution?
Have you tried TNT 4.4 yet?
I love the ability to push from my PC's browser Market and with my TNT 4.4 ROM, it recognizes as Malata TNT Lite 4.4 and works perfectly.
After 3 weeks of flashing/reflashing, I found TNT 4.4 is the most solid, stable ROM and worth to use.
I really enjoy my tablet with TNT 4.4 now rather than flashing...flashing. The part I love the most is my Gtablet TNT 4.4 Market fully functional so I can make the software purchase from my PC browser and push from there....
Good luck!
No, it's not a rom specific issue, it's a problem with my tablet. I cannot download anything from the market with my main Gmail account. Read a post from another forum member with the same problem, and he found something interesting.
tvguyjohn said:
*UPDATE 4/18/11 - On a whim, I decided to use ClockworkMod to reset my User Data, and signed my tablet in under another Google account I had. As I type this, I'm downloading all the apps that I was unable to download with my "usual" account. So maybe there's a bug on Google's side? How would I even go about fixing that?
Click to expand...
Click to collapse
I signed in with a different Gmail account, and sure enough I can download anything with that, just not my "main" Gmail account. I guess I could go on with a different Gmail account for my tablet, but I have so many paid apps that I'd like to use on my G-Tab.
In my last post, I mentioned I purchased a Chines copy Iphone running Android 2.3 which is suffering the inability to download apps (stuck on download started). I contacted google and their response was :
Thanks for your message. According to our records, the device you're using isn't supported for use with Android Market at this time. For additional details, please see this complete list of supported devices:
http://source.android.com/compatibility/index.html
My previous device, a ZT 180 , Im sure was also not on this list but App store works fine.
My phone will sync with Gmail and Talk easy, I have wiped all caches.... what is the missing link with the App store recognising the phone is not compatible and how do I bridge it? Have tried downloading various vending and market apk's but none will succesfully install. Any ideas?
Even it is open source, the phone manufacturer also need to buy license from Google in order to run android os in their device. This applies on Android 2.3 and above. If you are running on a china made product, you probably won't get it work unless you do some trick to let it work.
Sent from my Nexus S using xda premium
Thanks for that - Can I reflash back to 2.2? Is there a generic ROM to use for this?
Not sure how I would trick it....sounds like I would need to root it to do so.
Yes you would need to root it and flash a custom rom that makes it look like a different device.
I have the VZW VS985 and I was happily running CM11 for a while. I decided to take CM12 for a spin, found that Lollipop is not quite to my liking and (already knew that) doesn't support Xposed Framework because of ART.
Unfortunately, all links to the CM11 ROM have vanished. Not even CyanogenMod hosts the files anymore and I can't find where I downloaded the .zip to. So I'm stuck on Lollipop.
But here's the kicker. I need to be able to access my corporate email, which requires that the phone be encrypted. In the past, on devices that fail to encrypt the workaround has been to simply use the "Exchange Security Bypass" module for Xposed Framework on JellyBean and later KitKat. As I no longer have this option and I'm stuck on CM12, but I'm still in need of access to my corporate email my only choice is to encrypt my phone. The problem is, every single time I try to encrypt, it silently fails and immediately reboots, occasionally boot looping and requiring a factory reset to restore functionality.
So if ANYONE has a copy of the latest CM11 nightly (i think its a few months old now) or knows how to get the VS985 to encrypt on CM12 any help would be appreciated.
N00b-un-2 said:
I have the VZW VS985 and I was happily running CM11 for a while. I decided to take CM12 for a spin, found that Lollipop is not quite to my liking and (already knew that) doesn't support Xposed Framework because of ART.
Unfortunately, all links to the CM11 ROM have vanished. Not even CyanogenMod hosts the files anymore and I can't find where I downloaded the .zip to. So I'm stuck on Lollipop.
But here's the kicker. I need to be able to access my corporate email, which requires that the phone be encrypted. In the past, on devices that fail to encrypt the workaround has been to simply use the "Exchange Security Bypass" module for Xposed Framework on JellyBean and later KitKat. As I no longer have this option and I'm stuck on CM12, but I'm still in need of access to my corporate email my only choice is to encrypt my phone. The problem is, every single time I try to encrypt, it silently fails and immediately reboots, occasionally boot looping and requiring a factory reset to restore functionality.
So if ANYONE has a copy of the latest CM11 nightly (i think its a few months old now) or knows how to get the VS985 to encrypt on CM12 any help would be appreciated.
Click to expand...
Click to collapse
Have you tried some of the other roms based off of CM11. I have a link below that I have always found to be my fav on AOSP based KK roms
http://forum.xda-developers.com/verizon-lg-g3/development/rom-liquidsmooth-v3-2-vs985-11914-t2934897
agreed, you can put me on the list of "not a fan of 5.0" I prefer xposed modules. I too have been looking for a pure cm11.zip and their homepage has deleted all of them. Perhaps we could place a request for re-build of the latest cm11?
There may be hope yet. Over the weekend, it was reported that Xposed for lollipop was released. People are reporting mixed results. Seems like people running Official lollipop firmware on Nexus devices have working Xposed on Android 5, but many people are reporting that it isn't working on most other devices. The VS985 running CM12 being among those not working yet. I tested it myself and can confirm that Xposed is not working yet on CM12 for the VS985, but I'm sure that will change in the coming weeks. Interestingly enough, within hours of the release of Xposed for Lollipop, there was a new Exchange Security Bypass module released specific to Lollipop, presumably because Exchange accounts are now being handled by the Gmail app. The functionality has been stripped from the AOSP mail app, which I have mixed feelings about.
I am not a diehard FOSS guy, I am more of a pragmatist. I use what works. But on some level, it is alarming that you have to agree to Google's EULA and flash GAPPS in order to gain access to functionality that used to be baked into one of the AOSP core apps. It's almost as if we are seeing some schism withing Google, between the Android (AOSP) team and the team in charge of the "Google" experience on top of Android.
I for the most part use GAPPS versions of things like Calendar, Camera, etc. Simply because I like them better. But starting way back with Android 2.1 on my LG Optimus T P509, I made a habit of uninstalling the GMail App with TiBackup and strictly using the AOSP mail app. Now, as I said I am a pragmatist and this was at first, simply because Gmail only allowed you to connect it to Gmail accounts, but this has changed with the release of Lollipop. So do I stop worrying and learn to love the bomb? Or should I be alarmed by the closed sourcing of core functionality on Android?
Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.