DistortedLoop

Members
  • Content count

    603
  • Joined

  • Last visited


Community Reputation

0 Neutral

About DistortedLoop

  • Rank
    Addict

Contact Methods

  • Website URL http://
  • ICQ 0

Previous Fields

  • Your Current Device(s) GalaxyNexus, HTC One X, SGS2
  • Your Twitter username distortedloop

DistortedLoop's Activity

  1. DistortedLoop added a post in a topic late to the party?   


    There's always a "better" Android device/phone just around the corner.

    The Moto X in a few weeks. The Galaxy Note 3 in a month or two. The HTC One with a 5" screen, Butterfly 2 soon. The Nexus 5 in a few months.

    If you're always waiting for the next best phone, you'll never buy a new one, or you'll end up waiting to see what next month's hot announcement is, and then end up getting the HTC One or whatever else you put off, only a month later.
    • 0
  2. DistortedLoop added a post in a topic MoDaCo.SWITCH for the HTC One Beta signup   


    I'm very happy with the Sense version of the phone (Nova Launcher on top of it), but will be interested in testing out the GPE version using Paul's switch method.



    Why are you frustrated? If you're on T-Mobile US, you should buy the T-Mobile version of the phone, end of story.

    It's the only penta band version of the phone and that means it will work with LTE on both T-Mo and ATT, as well as T-Mo's ultra fast dual channel HSPA+.

    I bought for cash from T-Mobile, saved $20+ compared to HTC dev and play editions. I paid $3 on eBay for an unlock code, then did S-Off, and super cid hacks. Now the phone is any version I want on any network, with full network support.

    The only reason not to go that route for a T-Mobile user or network switcher is if you just have to have a 64gb model.

    • 0
  3. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   

    Paul tweeted the other day that he was having trouble with Wallet himself, and that he would patch it on Monday.
    • 0
  4. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   

    Hey this is weird. I woke up this morning to a notification that Google Wallet had updated (despite auto-update on it being turned off, and despite having just used TiBu to detach it from the Market). This happened before with the latest version, blast it. How the heck does that happen? Really annoying.

    When that happened, Wallet wouldn't even open past the splash screen. I had to wipe it from the phone and reinstall the MoDaCo version.

    Here's the really weird part: I tried opening Wallet, and it worked. Entered my PIN, and everything's there; Prepaid card w/proper balance, all my credit cards, etc. I went to App Settings on the phone, and it shows Wallet as updated to r-79-v5 and has the uninstall updates available. TiBu also reports it as updated.

    What the heck could be going on; as mentioned, when this happened a few weeks ago, the app wouldn't even open, now it updates and works fine (well, I haven't tried making a payment anywhere).

    Has anyone else had this happen? Anyone willing to try to update via the Market to test for same results?

    I wonder if this will survive a reboot.

    Any suggestions at this point?


    • 0
  5. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   

    <deleted> Tapatalk mutilated the message. :(
    • 0
  6. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   


    But Paul's version you can change back to proper device identifiers?

    I've got issues with other apps not wanting to install because they think my device is not supported while using the Wallet-friendly build.prop
    • 0
  7. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   


    Ah, that's good to know. I'd asked Paul about this a while back, but didn't realize he'd fixed it.

    That might explain why my HTC One X asks to update; it's using the original apk - and I used the same apk off my sdcard to reinstall. My SGS3 I downloaded a fresh copy to use to install. I'm not sure which version my VZW Galaxy Nexus has on it.

    I'll probably wait to reinstall when the latest version gets hacked.
    • 0
  8. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   

    @Paul- Your app on the Nexus or Galaxy S3 doesn't appear to be linked to the Market, but on the One X it is. One X is only phone that I have that keeps getting messages to update Wallet when a new version comes out. Any ideas why that would be?
    • 0
  9. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   

    Ugh, this is frustrating. Way too much time screwing around with this to be able to use my phone instead of the actual card at the precious few places that take Wallet to begin with.

    Was working perfectly until as previously mentioned the damned market auto-updated the app.

    Try to wipe and install again:


    E/DeviceCapabilityManagerImpl( 6289): OperatorName=AT&T, Operator=310410, Product=htc_jewel, Model=htc_jewel not supported

    Okay, change it to Galaxy Nexus, yakju and maguro per the SGS3 hack. Don't get the "not supported" any more, but perpetually stuck at "adding account".

    Force stop, clear data, reboot several times. Repeat. Restore data only from TiBu (didn't work). Force stop, clear, reboot again. Finally, took a very long time, but appears to be installed again.
    • 0
  10. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   


    Yeah, and damned Market auto updated mine, breaking it of course. I thought I had that feature turned off.

    Tried uninstalling updates, which wiped out my data as well...didn't think it would do that.

    Guess setting up fresh is safer than restoring from TBU at this point.
    • 0
  11. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   



    I absolutely hate it when a manufacturer (and they all do it) releases **different** pieces of hardware under the same marketing name. It leads to this kind of confusion.

    You're both correct, of course. The original "Galaxy SII" (ie., the i9100 released internationally, but not in the US) does not have NFC. Some (all?) of the US "Galaxy SII" variants do have NFC, some of them it works, some of them it's been disabled by the carriers.

    I had an international i9100, my friend has the TMobile version, both are called Galaxy SII by the owners, but they are nothing alike, inside or out; they don't even have the same size screen.

    From an XDA post on the subject, here's a breakdown of which S2 models have NFC and which don't:


    • 0
  12. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   



    Paul- I know it's working on your HTC One X from the first post, but if you've patched out the device check, why are we having to edit our build.prop files to say ro.product.device=htc_jewel to get this to work now? What's your build.prop say?

    See above post of mine where logcat shows Wallet failing at device check with "HTC One X not supported."

    The carrier being AT&T didn't matter.

    Anyways, despite the new hoop to jump through, once again, THANKS for making this possible.
    • 0
  13. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   

    EDIT: Got it working, thanks. My custom ROM's build.prop had the "ro.product.device=HTC One X" line in it in two different places. I changed the second one to htc_jewel and it works now. Wallet up and running, all my credit cards showing again, prepaid card w/balance back. I hope changing from endeavoru doesn't screw up other apps.



    Thanks for the response.

    I am activating over WiFi.

    I saw the One X not supported comment, but my build.prop has the changes in it.

    Here's a copy of the relevant section of the build.prop file where I changed as you suggested:


    #ro.product.model=EndeavorU ro.product.brand=htc_europe #ro.product.name=endeavoru #ro.product.device=endeavoru ro.product.model=htc_jewel ro.product.name=htc_jewel ro.product.device=htc_jewel

    I've previously tried it without leaving the remarked lines in the file. Same result.

    If Paul disabled the device check, why is this necessary? Strange.
    • 0
  14. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   


    It says "Model=HTC One X not supported" but my build.prop says ro.product.model=htc_jewel. Also, I thought one of Paul's three hacks was to remove the device check.

    I'm on a Tegra 3 european HOX, with an AT&T sim. Prior versions of Paul's Wallet apk worked, but after trying to use this one, even old ones won't activate.



    I/InitializerTaskManagerImpl( 5433): submitted [CHECK_DATABASE_AND_SECURE_ELEMENT, IDENTIFY_SECURE_ELEMENT, CHECK_CPLC, INITIALIZE_MIFARE_FORCED, SCHEDULE_MAINTENANCE_SERVICE, EXPIRE_PIN, MARK_BOOT_TASKS_COMPLETED, CHECK_BOOT_TASKS_COMPLETE, CHECK_REQUIREMENTS, GET_ENVIRONMENT_INFO, START_PREFETCH_IMAGE_SERVICE, INITIALIZE_MIFARE_IF_NEEDED, INITIALIZE_SHARED_PREFERENCES, START_ACCOUNT_VERIFICATION, ENABLE_CARD_EMULATION, SYNC_WALLET, INITIALIZE_BOTNET, START_BALANCE_FETCHER, SCHEDULE_TSA_C2DM_REGISTRATION_SERVICE, GAIA_ACCOUNT_MISSING_CHECK, SCHEDULE_WALLET_C2DM_REGISTRATION_SERVICE] I/InitializerTaskManagerImpl( 5433): CHECK_DATABASE_AND_SECURE_ELEMENT: starting V/NfcManager( 5433): constructor D/NfcManager( 5433): got mAdapter I/NfcExecutionEnvironmentManagerImpl( 5433): Wakelock WakeLock{40df1380 held=true, refCount=1} acquired 1344834111401 ms I/ActivityManager( 314): Start proc com.skcc.gtec.otaproxy for service com.google.android.apps.walletnfcrel/com.skcc.gtec.otaproxy.StartService: pid=5524 uid=10363 gids={3003} D/NfcService( 822): NFC-EE OFF D/NfcService( 822): NFC-C ON E/DeviceCapabilityManagerImpl( 5433): OperatorName=AT&T, Operator=310410, Product=htc_jewel, Model=HTC One X not supported E/TsaRegistrationImpl( 5524): Invalid state: Attempting to re-register. E/DeviceCapabilityManagerImpl( 5433): OperatorName=AT&T, Operator=310410, Product=htc_jewel, Model=HTC One X not supported I/NfcExecutionEnvironmentManagerImpl( 5433): Wakelock WakeLock{40df1380 held=false, refCount=0} released 1344834111699 ms V/NfcManager( 5524): constructor D/SyncManager( 314): setIsSyncable: com.google, provider com.google.android.apps.wallet -> 0 D/SyncManager( 314): setIsSyncable: already set to 0, doing nothing D/SyncManager( 314): setSyncAutomatically: , provider com.google.android.apps.wallet -> false D/SyncManager( 314): setSyncAutomatically: already set to false, doing nothing I/NfcExecutionEnvironmentManagerImpl( 5433): Wakelock WakeLock{40df1380 held=true, refCount=1} acquired 1344834111707 ms D/NfcManager( 5524): got mAdapter D/NfcService( 822): NFC-EE OFF D/NfcService( 822): NFC-C ON I/NfcExecutionEnvironmentManagerImpl( 5433): Wakelock WakeLock{40df1380 held=false, refCount=0} released 1344834111991 ms D/SqliteDatabaseCpp( 5433): DB info: close db, path = /data/data/com.google.android.apps.walletnfcrel/databases , key = sYlletDYtYwt, handle = 0x15db5f0, type = w, r/w = (0, 0) D/SqliteDatabaseCpp( 5433): DB info: open db, path = /data/data/com.google.android.apps.walletnfcrel/databases , key = sYlletDYtYwt, flag = 6, cannot stat file, errno = 2, message = No such file or directory D/SqliteDatabaseCpp( 5433): DB info: path = /data/data/com.google.android.apps.walletnfcrel/databases , key = sYlletDYtYwt, handle: 0x155e830, type: w, r/w: (0,1), mode: delete, disk free size: 712 M E/DowngradeSafeSQLiteOpenHelper( 5433): old version: 0 new version: 20 I/SqliteDatabaseCpp( 5433): sqlite returned: error code = 17, msg = statement aborts at 12: [SELECT id, proto FROM credential] database schema has changed I/SqliteDatabaseCpp( 5433): sqlite returned: error code = 17, msg = statement aborts at 12: [SELECT id, proto FROM credential] database schema has changed I/SqliteDatabaseCpp( 5433): sqlite returned: error code = 17, msg = statement aborts at 12: [SELECT id, proto FROM credential] database schema has changed I/SqliteDatabaseCpp( 5433): sqlite returned: error code = 17, msg = statement aborts at 12: [SELECT id, proto FROM credential] database schema has changed E/DeviceCapabilityManagerImpl( 5433): OperatorName=AT&T, Operator=310410, Product=htc_jewel, Model=HTC One X not supported I/NfcExecutionEnvironmentManagerImpl( 5433): Wakelock WakeLock{40df1380 held=true, refCount=1} acquired 1344834112190 ms E/DeviceCapabilityManagerImpl( 5433): OperatorName=AT&T, Operator=310410, Product=htc_jewel, Model=HTC One X not supported D/dalvikvm( 822): GC_CONCURRENT freed 1046K, 25% free 3486K/4643K, paused 1ms+2ms D/NfcService( 822): NFC-EE OFF D/NfcService( 822): NFC-C ON I/NfcExecutionEnvironmentManagerImpl( 5433): Wakelock WakeLock{40df1380 held=false, refCount=0} released 1344834112316 ms D/StateMachine( 314): handleMessage: E msg.what=131155 D/StateMachine( 314): processMsg: ConnectedState D/WifiStateMachine( 314): ConnectedState{ what=131155 when=-3ms arg1=1 } D/WifiStateMachine( 314): fetchRssiAndLinkSpeedNative RSSI = -76 D/WifiStateMachine( 314): fetchRssiAndLinkSpeedNative send RSSIChange intent, SameSignalLevelCount =2 D/StateMachine( 314): handleMessage: X D/NfcService( 822): NFC-EE OFF D/NfcService( 822): NFC-C ON E/TsaRegistrationImpl( 5524): Invalid state: Attempting to re-register. E/TsaRegistrationImpl( 5524): Invalid state: Attempting to re-register. E/DeviceCapabilityManagerImpl( 5433): OperatorName=AT&T, Operator=310410, Product=htc_jewel, Model=HTC One X not supported E/DeviceCapabilityManagerImpl( 5433): OperatorName=AT&T, Operator=310410, Product=htc_jewel, Model=HTC One X not supported D/skia ( 5433): notifyPluginsOnFrameLoad not postponed
    • 0
  15. DistortedLoop added a post in a topic XMOD: Region / Device / Root patched Google Wallet   


    AT&T blocks traffic to Money Network. You need to be on WiFi or VPN account that bypasses AT&T to get it to work.

    Once setup is complete, you don't need to be on WiFi or VPN to use the phone to pay.
    • 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.