yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] techgov8:
All I did was change my build.prop to htc_jewel and flashed

SGS3-TW-US_variants-lib_nfc-fix.zip and then this com.google.android.apps.walletnfcrel.magn2o.1.5-R75-v6-1.zip the set my cards up and changed my build.prop back to my original verizon s3 and all has been working well since I found this mod when it first came out

Tap'n
[Verizon Samsung Galaxy S III] hyunge:
First two transactions completed at McDonald's this morning!!! Only problem is that it won't let me go back to Verizon build prop (SCH-I535), I had to leave it on Sprint build prop for it to
[Verizon Samsung Galaxy S III] jy3ng4:
Could you guys give me a little help with this? What is the Sprint edit? Is there a noob friendly tutorial anywhere?

So does it matter whether you use the htc_jewel or the Sprint build.prop edit?
[Verizon Samsung Galaxy S III] techgov8:
It doesn't matter which build you use. Your just tricking your phone into thinking its another phone so you can register and add the cards. Once you do that you can change back to your original build. I've used both the jewel and sprint s3 builds to get it up and running

Tap'n
[Verizon Samsung Galaxy S III] SMR-DINO313:
Um need to keep it on the Sprint edit. With the build prop to keep wallet working if u revert build prop From Sprint to verizon wallet will stop working..

Sent from Land Line using pay phone
[Verizon Samsung Galaxy S III] Marcismo55:
Yup...I've noticed this has only been an issue as of late because of the Wallet updates.

BTW..if anyone wants to use the Sprint build.prop info here it is:

Sprint GS3 build.prop edit for wallet

ro.product.model=SPH-L710

ro.product.name=d2spr

ro.product.device=d2spr
[Verizon Samsung Galaxy S III] techgov8:
I've never had to switch it back before. Since the first time I installed wallet I've always reverted back to my original build

Tap'n
[Verizon Samsung Galaxy S III] hesh.monster:
FWIW I've left mine on the Sprint edit and have had no issues with anything Verizon-wise. There's really no need to switch back as far as I can tell
[Verizon Samsung Galaxy S III] techgov8:
There is because for every app your phone is going to be recognized as the sprint s3. Wont that mess with titanium backup?

Tap'n
[Verizon Samsung Galaxy S III] hesh.monster:
Don't know really, i never restore data with titanium anyway. Too flaky imo
[Verizon Samsung Galaxy S III] dbow32:
I hate leaving the Sprint edit on, but my wallet always works.
[Verizon Samsung Galaxy S III] tonu42:
Check my thread out in development section. I include scripts to edit build prop to galaxy nexus and after you setup wallet you can revert it using another script included.
[Verizon Samsung Galaxy S III] Beemer533:
Same here; I used the sprint build prop edits and just left it.... I haven't had any issues.
[Verizon Samsung Galaxy S III] techgov8:
You don't need to keep the build edited. You can change it back to your original. The app doesn't need to use your build to make a payment its only to setup the cards.

Tap'n
[Verizon Samsung Galaxy S III] Marcismo55:
I think this

WAS

the case but now when I try to change mine back I get and erroer stating "your device is not supported" (or something to that effect). Leaving the device as d2spr certainly does not do anything and is what I have decided to do as well.
[Verizon Samsung Galaxy S III] techgov8:
Many people get that. You can still use the app its just because your rooted

Tap'n
[Verizon Samsung Galaxy S III] Marcismo55:
I think we are speaking of two different things. The "Unsupported Device" warning at the top of the app still allows you to use wallet. Which is this the first image

However, I am speaking of the error you get when trying to change you reboot after the build.prop has been changed back to stock (d2vzw). Once you do this, the wallet app throws and error and then kicks you out.

The second image is what wallet looks like after I've changed my build.prop back to d2vzw

EDIT: For pics
[Verizon Samsung Galaxy S III] techgov8:
Understandable I apologize. You are correct. That's weird cause I've never had that on my phone after switching my build back to original Verizon

Tap'n
[Verizon Samsung Galaxy S III] Marcismo55:
No worries. It may be the Wallet version too...I am using 1.5 r79 v5
[Verizon Samsung Galaxy S III] techgov8:
Im using the same version as well

Tap'n
[Verizon Samsung Galaxy S III] weizilla:
I have the exact same problem. What are the repercussions to leaving the build.prop file in a d2spr state?
[Verizon Samsung Galaxy S III] tonu42:
You get sprint apps in play store and you also loose the right to see any verizon app I believe.
[Verizon Samsung Galaxy S III] P2o8wer:
Mine is working fine.. Aokp jb build 4
[Verizon Samsung Galaxy S III] digitalsynner85:
mine still works using Galaxy Nexus as the tag, yakju and modaco as device modifiers on jellwiz rls8.....made a payment 15 mins ago at mcdonalds
[Verizon Samsung Galaxy S III] edjm711:
I never updated mine. I used yukju build.prop edit, then switched back to i535 Verizon s3 stock build.prop no problems.
[Verizon Samsung Galaxy S III] SMR-DINO313:
Same thing using the nexus yakju maduco trick. Reverted back to stock prop and just used it in the gas station worked like a charm
[Verizon Samsung Galaxy S III] onyx_64:
Did you try rebooting after changing the prop? i cant access google wallet after changing the build.prop too.. after rebooting.

ps: i am using the GW app from Market. not custom.
[Verizon Samsung Galaxy S III] SMR-DINO313:
Im guessing u cant access gw no more since u updated it from the market. U need to stay on custom to keep it working after reverting to stock build prop
[Verizon Samsung Galaxy S III] techgov8:
You have to use custom. And dont install update from market. Just change build flash hacked wallet then set it all up. Change build back and your good to go

Rooted, Unlocked, & Tap'n
[Verizon Samsung Galaxy S III] onyx_64:
that figures.. thanks! will try the custom!
[Verizon Samsung Galaxy S III] digitalsynner85:
if people have issues w/ accessing GW after updating and changing their build.prop back to normal, they can just do the build.prop edit and it works fine again, my phone is seen as a nexus device but i really could care less about that, no apps i use are phone specific lol
[Verizon Samsung Galaxy S III] Peterpark:
My card seems to not be registering. Anyone know why?
[Verizon Samsung Galaxy S III] Sinker1345:
The cards take a while to register, also I believe you can set up your cards online, I haven't tried that so I can't actually confirm it will work.
[Verizon Samsung Galaxy S III] limeionqc:
I was not able to find an answer to this anywhere else. So, I have a Verizon S3 running the Slim Bean ROM 2.7.0 and the NFC options are available on the more menu. Then after I try and install the Wallet ZIP and go through the set up procedure in Wallet, it says to enable NFC. Then when I go to that menu to do so, the options are completely gone... Any ideas? please help... Thank you.
[Verizon Samsung Galaxy S III] digitalsynner85:
clean flash slim 2.7.0, don't flash the wallet zip, use root explorer to go to system and modify your build.prop and change ro product model to Galaxy Nexus, ro product name to yakju, and ro product device to maguro, it has worked across multiple devices for me.....that should work
[Verizon Samsung Galaxy S III] limeionqc:
Then just flash the wallet zip again as norma, I would assume? Also do I need to leave the prop. information that way or change it back to nomral for Verizon? Thank you again...
[Verizon Samsung Galaxy S III] limeionqc:
That all worked perfectly. Am I able to safely put the build prop back to the vzw settings as before? Thank you again.
[Galaxy S III Q&A, Help & Troubleshooting] setspeed:
Don't want to add to Omega ROM's 2000+ page thread.

I've been running the last few Omega JB ROMs and they're very decent speed-wise, however my battery life has basically gone to hell compared to the ICS ROMs. Are all JB ROMs like this? Can you suggest a different JB ROM?

And before anyone makes suggestions, thank you, but I have already done all the usual checking to make sure it's not my apps causing the problem.
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Are you sure you haven't got the media scanner problem?
[Galaxy S III Q&A, Help & Troubleshooting] setspeed:
The media scanner problem? Please enlighten me :)
[Galaxy S III Q&A, Help & Troubleshooting] VulguM:
Media scanner goes crazy keeping the device busy, like... at full 1,4GHz speed for long periods of time, some people reported about an hour of this behavior.

The easy way around is disabling it with Rescan Media Root

You can identify this issue using BBS, look for partial wakelocks.
[Galaxy S III Q&A, Help & Troubleshooting] setspeed:
Don't think I'm suffering from that. Since boot 10h 41m ago my biggest partial wakelock is Google Maps NetworkLocationLocator 25m 50s, 4% of my battery. Thanks for suggestion, hadn't heard of that issue.
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
The Google maps thing is related to Google now I'm pretty sure, it adds a bit of drain but imho worth it for the usefulness of it, downloading bus timetables is a thing of the past now :D
[Galaxy S III Q&A, Help & Troubleshooting] d4fseeker:
No JB rom, be it AOSP-based like Cyanogenmod or Samsung-created, are out of dev-preview/beta so give it some time to mature and get better.

ICS battery life has greatly improved from the first ROM, you cannot expect Jelly bean to be at that point just yet.
[Galaxy S III Q&A, Help & Troubleshooting] setspeed:
So basically they're all pretty bad on battery life then? That's fine, all I needed to know - I'll not waste my time flashing loads of different ROMs, and just stick with Omega for now :)
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
just had 18+ hours up and 7+ hours screen on time of the jb I'm running...I'm ok with that
[Galaxy S III Q&A, Help & Troubleshooting] setspeed:
I'm getting less than 4hrs screen-on time, and limp to about 14hrs between charges, compared with almost 6hrs/20+hrs on ICS on the exact same usage.
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Fyi....I'm running siyah on rgui,, all Samsung cr*p frozen, JD running, auto synch on, location services on for Google now
[Galaxy S III Q&A, Help & Troubleshooting] avdaga:
Omega was horrible for my battery, then I switched to wanamlite.

In the meanwhile i cleared my user data and performed a heavy cleaning of the rom by means of ROMCleaner and removing even more stuff than mentioned in the ROMCleaner thread.

Therefore I cannot guarantee whether it is a problem in omega's rom or in my data.

After a night the results were satisfactory, as shown in the screenshot. Soon I will start a thread to explain my approach.
[Galaxy S III Q&A, Help & Troubleshooting] setspeed:
Maybe I'll give Wanamlite a try then...
[Galaxy S III Q&A, Help & Troubleshooting] ikarus17:
Hi Guys,

You might wana use the Better Battery Stats XDA version. you will see what's eating your battery.

http://xdaforums.com/showthread.php?t=1179809
[Galaxy S III Q&A, Help & Troubleshooting] jankro:
On my phone battery life went down from 20+ hours on stdby to 8 hours on stdby with JB update!

I'll go back to ICS.

-J-
[Galaxy Note 10.1 General] Alabama978:
Trying to find out if the note 10.1 is nfc capable?

I've tried a couple of apps on my 16gb wifi but they did not appear to read any data.
[Galaxy Note 10.1 General] Nefariouss:
Nope
[Galaxy Note 10.1 General] ultramag69:
The buggers at samsung decided its not needed on a tablet, be bloody handy though... :crying:
[Galaxy Note 10.1 General] antique_sonic:
yeah... too bad don't have.

perhaps later on the LTE version around end of year.

For current note 10.1", perhaps the current content is too pack alrd till they don't know where to put the NFC chip.

:cyclops:

Sent from the corner of this rounded earth.
[Galaxy Note 10.1 General] dr.m0x:
Would have been nice for s-beam alone.
[Galaxy Note 10.1 General] ultramag69:
All the ads and little videos go on about the connectivity of their devices and samsung leave out this lovely new piece of tech that they talk up on the SGS3... Would be nice if most of their flagship phones and tablets had the same connectivity so if you owned them or had friends with these devices its easier to stay connected...

Sorry, that last ppart I'm sure I stole from a samsung ad.... :p:laugh:
[7" Kindle Fire HD General] iamz3r0:
Here's the Amazon-provided Kindle Fire HD drivers. This is for anyone having problems finding them. It helped me at least sideload a few apps on this Fire HD. I'm not sure if you can find them anywhere other than using the Android SDK Manager. I figured I'd just make it easier for those who don't have the traditional SDK setup.

You can turn on ADB in Settings>Security>Enable ADB

Attached is the installer from the Amazon repository found using these instructions.
[7" Kindle Fire HD General] reverendkjr:
Perfect. Thanks for this. It was the one piece I was missing. Now my ADB connection works
[7" Kindle Fire HD General] iamz3r0:
No problem. I just figured I wasn't the only one who needed it.
[7" Kindle Fire HD General] reverendkjr:
Now we just need to find a way to root the damn thing.
[7" Kindle Fire HD General] iamz3r0:
This is true.

I'm no developer so all I can do is try methods that already exist. I'd rather not jump off of any cliffs with this HD yet until I can fix my screw-ups. :rolleyes:
[7" Kindle Fire HD General] Gam3r 4 Life:
I was thinking the same thing, but dont want to brick it. I just got flash, you tube, Dolphin, and Netflix working perfect. I love the screen on this thing. Only one thing left to make it perfect. Rooting, then full gapps!!!
[7" Kindle Fire HD General] lhupman:
Thank you. Another alternative is to load apks to box.com and install from there.
[7" Kindle Fire HD General] O_G:
Thread Closed​

We have a existing ADB thread.​
[Nexus 7 Android Development] Kueber:
This is NOT a ROM!

This is for development purposes only.

These are the system files of the latest Nexus 7 4.1.1 build JRO03S which came with my C9O I got yesterday.

Since I have been asked to upload those files I guess it's a good idea to make them available for all developers.

The files have been pulled straight from root/system, kernel as a separate *.img.

DOWNLOAD

If the files aren't reachable please send me a PM.

If the files are already available elsewhere please delete this thread.
[Nexus 7 Android Development] Harry GT-S5830:
Is this just a variant of 4.1.1?
[Nexus 7 Android Development] Kueber:
Another variant, yes - edited OP.
[Nexus 7 Android Development] mwalt2:
Thanks buddy!
[Nexus 7 Android Development] xmoo:
Build date?
[Nexus 7 Android Development] olivercervera:
Aug 21 23:30:33 UTC 2012

ro.build.version.incremental=444012

just read from my Nexus 7 C90
[Nexus 7 Android Development] oldblue910:
Can someone with the JRO03S installed from the factory (NOT someone who just flashed this) please verify that the JRO03S comes from the factory with bootloader 3.34 installed like JRO03D? If you need help getting the bootloader version, just reboot into the bootloader and it'll be right there on your screen.

Thanks!
[Nexus 7 Android Development] sami_22:
Kernel : Not working with Paranoid Android v2.15 :(
[Nexus 7 Android Development] jamesst20:
Doesn't work on my side, the system wont boot. I dont know what is wrong with this but i'm stuck on the boot animation.

Incompatibility with C7O ? or bad backup?
[HTC Inspire 4G] FlyingColors:
I have an HTC Inspire 4G. I got it about 2 weeks ago because I broke my other one, and then a couple days later I updated it to 3.20, which is the latest version from HTC. So I'm pretty sure that it was shipped with Froyo and not Gingerbread.

From the HTCDev website, I downloaded the Cingular USA RUU 2.47.502.7. Now when I open it on my computer, it shows up as version 2.50 and ends up giving me an error saying I need to upgrade to ROM 2.47.502.7.

I dont know what to do! I dont know if this is going to help, but when I got into hboot, this is what it looks like:

*****LOCKED*****

Ace PVT SHIP S-ON RL

HBOOT-2.00.0030

MICROP-0438

RADIO-26.17.14.11_M

eMM-boot

Feb 20 2012,16:03:18

Can someone help me?
[HTC Inspire 4G] marsdta:
Your phone did not come shipped with froyo. I have no idea what your trying to do by flashing the 2.47 ruu. Are you using some guide or something?

You need to read up on the aahk. Just Google attn1 hack kit and you find it. Once you read it a few times you can follow this to root the phone as the 3.20 update has a different process than the 2.47

http://xdaforums.com/showthread.php?p=30828287
[HTC Inspire 4G] bfigb7359:
Yes, I was using this guide: http://xdaforums.com/showthread.php?p=30828287 (Guide on page 3)

Ok, i'll definitely look it up. I've used it before but i'll read over it again and then follow the link. Can I stay in touch with incase I need help?

EDIT: I used the same guide you gave me. Any suggestions?
[HTC Inspire 4G] marsdta:
The guide seems self explanatory. Not sure where your question is

After some more reading I think I might see where the confusion is on the HTC dev site. Further proof of why its sucks compared to aahk. The exe files listed are to just update the hboot to proceed the steps. Those were intended for people who had an old version. But those on 3.20 already have the updated when when you flashed 3.20 just skip that part and continue with the rest of the steps.
[HTC Inspire 4G] FlyingColors:
Im going to tell you what I did step by step and maybe you can help.

Im starting with step 6 "Unlocking Bootloader.

1. Went to HTCDev.com

2. Clicked Unlock Bootloader and chose "HTC Desire HD"

3. I accepted the rules and such

4. Now I'm at a site where it tells me the steps to unlock the bootloader

5. I scroll down and download the "Cingular USA", ROM 2.47.502.7

6. After its done downloading, I click it to open it

7. When it runs it eventually gets to a point where it gives me an error saying I need to update to the latest ROM to download version 2.47.502.7

I have stock version 3.20.#####.

I dont know why I'm getting this error. I have also done everything before this step too, just incase you think I didnt do them.
[HTC Inspire 4G] marsdta:
Skip that part. Just go to the next step. You can look at my previous comment as to why
[HTC Inspire 4G] FlyingColors:
Even when my bootloader is lock?

And skipping it wont brick my phone correct? I've bricked my phone before so I dont want it to happen again.
[HTC Inspire 4G] marsdta:
Skip that step as in skip the step in the HTC dev site to unlock the boot loader. Think of it as a pre step before the actual unlocking happens. You don't need that step as you already have the appropriate hboot version.
[HTC Inspire 4G] FlyingColors:
Thank you man, I successfully rooted it and am now able to install a custom rom. I wish I could repay you but I dont know how and have no money.
[HTC Inspire 4G] ezro:
How did you do it,man? I'm exactly in the same case you were. I would apreciate it a lot!

Sent from my Inspire 4G.

EDIT:

Just rooted and everything is working!!!
[Galaxy S III Q&A, Help & Troubleshooting] hmrc87:
Hi,

I have a GT-I9300 and recently rootet via Odin and CF-Root-SGS3-v6.4.tar. After that, I was properly rootet, but there was no CWM Recovery console, just the regular one.

Then I started Odin again and tried it with recovery-cwm-touch-6.0.1.2-i9300.tar

Now I have the CWM-Symbol on my Drawer but it says, that "This version of CWM MAnager should be used with CF-CWM v.1.1 or newer. It appears you are running a different recovery"

What can I do now?

Thanks for your help in advance!
[Galaxy S III Q&A, Help & Troubleshooting] Domx92:
is this touvh recovery v. 6 ? then it's only for jelly bean. if you are on ics i would try CWM v5
[Galaxy S III Q&A, Help & Troubleshooting] hmrc87:
i uncheked Auto-Reboot and took out the battery after flashing. Now it works!
[Galaxy S III Q&A, Help & Troubleshooting] zoot1:
DO nothing ..that CWM app has some features which are incompatible..just use it to boot into recovery and do whatever you want to do manually..

forget about the error popup..just dismiss it..
[Galaxy S III Q&A, Help & Troubleshooting] hmrc87:
Wow.. I just was in the CWM Recovery console, rebootet into ICS and now I cant get into CWM Recovery again... what the hell is going on?
[Galaxy S III Q&A, Help & Troubleshooting] gee2012:
Just re-root with CF-Root and all should be fixed mate :)
[Galaxy S III Q&A, Help & Troubleshooting] hmrc87:
Thanks, mate. I didn't have the chance to try your solution out. I did the following.

Flash with just clockworkmodrecovery without Autoreboot in Odin.

Take battery out

Boot into recovery with VolUp+Home+Power

CWM Recovery pops up

Installed Resurruction Remix Custom Rom which comes with Touch-Version of CWM

Runs perfect smooth, and super fast! And Ive got the CWM Recovery console.

I should have switched to Android much earlier, coming from iPhone and Blackberries. It's amazing how cool some Custom Roms are :)
[Galaxy S III Q&A, Help & Troubleshooting] irzero:
Can someone with an overclocked S3 1.6ghz or 1.7ghz please run Geekbench?

I want to see the score vs the new A6 which just got featured and i cant run overclocked myself right now.

Thanks
[Galaxy S III Q&A, Help & Troubleshooting] Tomatoes8:
Is Geekbench an accepted Benchmark? How accurate is it? The scores seem to be all over the place with the Nexus 7 with the crappy tegra 3 beating the GS3 in one test while the GS3 beating it in another. Don't really trust it if the results change on the fly like that. haha
[Galaxy S III Q&A, Help & Troubleshooting] xtechx:
For what it's worth here:

http://browser.primatelabs.com/geekbench2/1032744

It was set at 1704mhz

Here is 1600mhz:

http://browser.primatelabs.com/geekbench2/1032776

For gits and shiggles here is 1400mhz:

http://browser.primatelabs.com/geekbench2/1032818

To compare clock for clock I set to 1000mhz, but left at quad core...though not sure it that actually matters...

http://browser.primatelabs.com/geekbench2/1032862
[Galaxy S III Q&A, Help & Troubleshooting] NatTheCat:
2081 you got on 1.7ghz, running ics..

My name is Optimus Prime and I send this message..
[Galaxy S III Q&A, Help & Troubleshooting] AndreiLux:
I posted some scores on Beyond3D:

The A6 clearly and undisputedly has the upper hand here. The score may be lower but we're talking about vast IPC and frequency disparities here. The Cortex's are getting slaughtered in memory bandwidth.

And here's a 1704MHz bench for the hell for it: 2283 score.

Would be interesting if somebody with a Krait phone would run it at 1GHz and stock frequency respectively.
[Galaxy S III Q&A, Help & Troubleshooting] irzero:
I hit 1800 at stock on Jelly bean Omega rom V26.

I might try and clock this phone and see what happens
[Galaxy S III Q&A, Help & Troubleshooting] Fade777:
What a junk benchmark.. kept running It till I got this.. o_O my lowest was 1520.. :confused:
[Galaxy S III Q&A, Help & Troubleshooting] thelestat:
Wanam Lite Stock stock LI1 blows the iphone away, I get 1780.

NOTE: My S3 is not OC'd, this was at the default 1400mhz with stock kernel (3.0.31-111170 se.infra@SEP-85 #1
[Galaxy S III Q&A, Help & Troubleshooting] uberNoobZA:
Any benchmark tool will be 'all over the place' depending on what is running in the background. Yes, you can turn off wireless, BT, data etc., but apps will still be launching and closing in the background which will affect the score. After all, these are supposed to be multitasking devices aren't they ?

Also, it's an inaccurate score if you actually go and forcibly disable system apps that would be running on a stock device, just to get a faster score.

Best way to use ANY benchmark tool is to get the device as near to stock as you can (consider a rom flash / data reset followed by very basic config) and then run the test a few times and take an average score. When I run benchmarks (Antutu, Quadrant, Geekbench), my results are often 'all over the place', so if I go with just one test, it would be luck of the draw really.

That said, my average score on S3 stock, rooted, unclocked in Geekbench 2.3.4 is 1586.

Funnily, when overclocked, the average was 1537