yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] kpjimmy:
So does this version keep connection? The original one kept getting discoed and pretty much a waste of mass lol. I have the pebble on order but because I backed the grey one, that color will most likely be last in being produced. I'll probably get it by xmas :p
[Nexus 4 Q&A, Help & Troubleshooting] DowntownJeffBrown:
It hasnt so far but I'll update u after I use it for a day or so. How often did your disconnect? How could u tell if it did? Mines charging I only played with it for about 20 min

Sent by my Kitteh eating my muffin head (Im chocolate chip) via my Sexy Nexi 4 using Tapatalk
[Nexus 4 Q&A, Help & Troubleshooting] DowntownJeffBrown:
@kpjimmy

So I can affirm that after a couple days of nonstop use my Bluetooth connection has stayed strong and not dropped once. Everything seems to work perfect and extremely snappy (instantaneous) and I'm very happy. The only thing I have found is that if u try to change the default stock weather app location its has a connection issue. From what I have read though its due to the most recent firmware update a week or so ago. But that's fixable and I'm sure Sony is well aware of the problem. Overall I'm very happy and would recommend these to anyone looking for this type of product (toy).

Sent by my Kitteh eating my muffin head (Im chocolate chip) via my Sexy Nexi 4 using Tapatalk
[Nexus 4 Q&A, Help & Troubleshooting] ShinTenken:
How did you get it to pair? I've owned the Sony Smartwatch for a while. It worked flawlessly with my Galaxy Note, but it REFUSES to see my Nexus 4. Could you provide detailed pairing instructions, please? The Sony website is useless, as they still have the very old instructions utilizing apps that do not even exist anymore. Thank you ahead of time.
[Nexus 4 Q&A, Help & Troubleshooting] marcars:
it is queit simply. Turn off your smartwatch. Enable Bluetooth in your N4 and make your self visible. Turn on and hold Power button befor you will see sync icon. Than you should see a new device in N4 like smartwatch. Just pair it and that's all.
[Nexus 4 Q&A, Help & Troubleshooting] Johmama:
Stumbled upon this thread while browsing the forums and I have to say, I haven't even thought of getting a Smartwatch until seeing this thread. After doing 15 minutes of research, I really want to pull the trigger on one on Amazon and get it before my big vacation later this week (thank goodness for Prime). I have a few questions though.

Basically, compatibility. I see there are a few posts in this thread saying it works and everything. Anyone else have any issues? I'm using Paranoid Android and the Franco kernel, anyone have issues while using them?

This is probably a stupid question, but how exactly does it notify you? Does the watch have a vibration option or a ringtone or anything? I wouldn't be surprised if it didn't notify you, because your phone would be ringing so you would hear your phone and look at the watch.

What's the functionality of it in terms of text messages? Does it just say you have a text message and who it's from, or does it show part of the message or the whole thing? I assume it doesn't let you text back on the watch, simply because a keyboard on that small of a screen seems very hard to implement.

Oh, one last thing. How is the Sony Smartwatch vs any other smartwatch? Is the Sony one the way to go, or are there better ones that people have found?

Any other info or observations anyone else has, I would be more than happy to read them. I am seriously considering buying it right now.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] sumikari:
my screen on my tab 2 7 works almost perfect, except when I draw diagonaly, it wiggles tons. the screen is clean amd it has done this sonce i first opened it. It does this regardless of if I use a stylus or my fingers, and it does the same on my sisters tab of the same kind. Is it fixable? or is ia just a hardware problem? Im an artist so this is getting really annoying, since it wont draw curves or circles because of this D:
[Galaxy Tab 2 Q&A, Help & Troubleshooting] BigBot96:
Mine's done it since day 1 also, and as far as I know, it's a common "issue" with the digitizer. Basically, the digitizer cheap. Only way I've found around it is to apply more surface area with your finger.
[Verizon Samsung Galaxy S III] MR-OZ:
I made the mistake of not meeting at the Verizon store and bought a Galaxy S3 off Craigslist. It has a clean esn but it won't read the 4G sim card. I found out it was flashed to Cricket so I used Odin to flash it back to the original rom that came with the version of the phone which changed it to Baseband version: I535VRLEC but this still won't work it still has the same problem reading the Verizon 4G Sim.

I guess my question is... if there is a different rom I should flash it too? Or is it that once it has been flashed from Verizon to Cricket it can't flashed back to be used on Verizon again?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I would just get a new sim card from Verizon, that may resolve your issues. A few questions:

1) Does it still make calls and texts? The main issue is it doesn't connect to LTE? Maybe I'm not understanding your issue entirely.

2) Does the phone have your phone number and matching IMEI (labeled on the retail box) listed in Settings/About Phone?

You could Odin the stock image VRALF2, VRALEC was a pre-release image. Do not accept the OTA then dial *2767*3855# to reprovision the sim card. Maybe see if this resolves your issues.
[Verizon Samsung Galaxy S III] MR-OZ:
Well when I brought the phone in the first time to get it activated I was switching from a Droid X so they gave me a new 4G Sim card. But yeah it won't make calls or texts and it won't connect to there 4G data network or pick up the sim.

So are you saying changing it from VRALEC to VRALF2 might fix it?
[Verizon Samsung Galaxy S III] MR-OZ:
Oh yeah and I don't have the box it came in but my phone number did show up in the Settings/About Phone

And at the store they told me it was picking up the Verizon network it just wasn't connecting I guess? so it wouldn't get on the internet or make calls or texts
[Verizon Samsung Galaxy S III] SlimSnoopOS:
What I was saying is that normally people Odin to VRALF2 or VRALG1 then reprovision their sim card. That code will work on VRALEC but I was just trying to put you on a common starting point since we here don't really use the VRALEC stock tar in Odin. Primarily what you'll find in the stickies are VRALF2 and newer images. VRALF2 was the "store bought" earliest software version of the Verizon GSIII from the summer. Its worth a try but consider the following first.

Since you said it doesn't call/text then I think you lost your IMEI. Could you check for me under Settings/About Phone? It should be 15 random numerical digits if I'm not mistaken. If its not 15 digits, it will be 0 or several 0's. Don't post the exact number if it is 15 digits, but tell me what you see.
[Verizon Samsung Galaxy S III] MR-OZ:
No I didn't lose the IMEI it's still there, all 15 digits.

So is it possible to flash a Galaxy S3 from Verizon to Cricket. Then back to Verizon? Is it just a matter of changing to the right software?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Honestly I know nothing about flashing to another carrier. It's not something that I have a reason to research so I'm not knowledgeable in that area. My suggestion still is to run that reprovision code since you've already Odin flashed to VRALEC.

EDIT: To clarify, my suggestion is Odin VRALF2 then run the dialer code.

Just as a precaution, you should write down your IMEI, ERI, and maybe even your MIN and PRL version and store them somewhere on your computer. Since you don't actually have the retail box, this should be kept safe if we can't get this current situation straightened out. My reasoning is if you do somehow lose these before you're 100% fixed, having them written down may help you if you need to use one of the IMEI or ERI tools in the dev section.
[Verizon Samsung Galaxy S III] HHF2:
Did you try flashing a Verizon radio?
[Verizon Samsung Galaxy S III] MR-OZ:
Yeah I did it switched my Baseband version from VRBLK3 to VRLEC
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Let's see what happens when you follow section 5 of this thread:

http://xdaforums.com/showthread.php?t=1762709

Use the official VRALG1 4.0.4 firmware, don't accept the OTA prompt, then try the reprovision code.
[Verizon Samsung Galaxy S III] MR-OZ:
Hey that did the trick problem solved!

Thank you for taking the time to help me!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Great, I'm happy to help! So calls, texts, and data work? And are you staying stock or are you rooting/unlocking?
[Verizon Samsung Galaxy S III] MR-OZ:
Yeah.. Data, calls, text it's all working..

And yeah I planned on rooting it I'm just looking at what the best rom would be to flash it to.. any suggestions?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ahh, great! When you do just make sure to root, unlock your bootloader, make a nandroid backup in CWM or TWRP recovery, then use the "Comprehensive IMEI /EFS Backup" thread to properly backup your IMEI.

I encourage you to flash roms until you find something you like. I'll suggest that you stay with touchwiz roms then see whether sticking with Samsung's software in its various forms is good enough for you. If not, there's plenty of AOSP to go around!
[Verizon Samsung Galaxy S III] nintari:
So you just followed step 5 on the link above and it worked? (flashing with 4.0.4 ROM)

I'm going through a similar issue and been having a hell of a time getting mine to work. Mine was flashed to work on nTelos which is a CDMA provider in my area. I have flashed to just about everything possible (except 4.0.4) and haven't had any luck.

I went to the Verizon store and they tried to activate the phone but they couldn't but game me a sim to use and told me to call back if and when I could get it flashed back.

I tried at one point to take a working sim from another phone but it will not activate..... will not make calls, will not get data etc etc. when I dial 611 it still goes to ntelos.

Someone suggested putting Phone info on and setting the Phone to RUIM but I could not find that setting in Phone Info (even on the correct phone info, after time I found out the original phone info was pulled from the play store and I had to manually download it.

Anyway with the SIM I have and following section 5 as suggested mine does not give the option to accept or deny the OTA so I can try to enter the re-provision code. Should I get hold of the known working SIM to attempt this?
[Verizon Samsung Galaxy S III] nintari:
THANK YOU SO MUCH!!

The key to this however is to have a working SIM (the only one in our workplace was from an iPhone 5), I fashioned a nano SIM to mini SIM adapter and got the info on to the phone then my phone could finally be activated however the nano SIM I used got tied to my phone and couldn't be put back to the iPhone 5 it came from lmao... so I had to run to the Verizon store to get my co-workers phone re-activated.

But going down to the 4.0.4 and VRLEC modem then inserting the active sim, reprovision once it activates (it didnt give me the option to not allow it to do anything), then insert the mini sim, call Verizon they got it activated, I just now updated back to 4.1.1 (need to get 4.1.2) and everything is working wonderfully!!
[Verizon Samsung Galaxy S III] harvis912:
All of this info is extremely refreshing to hear since I have the same problem with one exception. My s3 has a bad charger port. Sent it in for warranty repair and Samsung said it was moisture damaged and corroded and is not covered under warranty (lies). But that is beside the point and another subject.

My question is, can all of this stuff be done through the sd card and not through the USB? I know it is a long shot but any help would be greatly appreciated.

Thanks!
[Verizon Samsung Galaxy S III] savoxis:
I know this thread is a little old but I just wanted to say thanks, the exact same thing happened to me (phone was previously flashed to cricket but i was unaware until AFTER purchasing and trying to activate)

ODIN Flashing the OMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar.zip package then reprovisioning with the *2767*3855# worked like a charm, I was sweating for a while as the deal was from craigslist

So far as i can tell to do this you NEED to use the VRAL as I tried a few other (newer) stock files and this was the only one that worked

THANKS AGAIN!

Keywords to help other people find this post:

fix radio

verizon from cricket

flash back to verizon

reprovision sim

odin flah back to stock
[NFC Hacking] ajpettit:
so as those of you watching ces coverage might have seen a few manufacturers are using nfc in their bluetooth speakers to link them up to phones tablets etc.

NFC-enabled Bluetooth accessories

So why not do this with existing bt speakers by using a tag?

So at the moment I've got a tag on my speakers that will enable bluetooth so that the phone (n4) connects to the speaker (they have previously been paired) and phone and media audio gets piped to the speaker (speaker also has hands free function Gear4)

So what I'd like to be able to do is

1. tap the tag while the speaker is in pairing mode.

2. have the device turn on bluetooth

3. search and pair with the speaker

4. output media (but not phone) audio to the speaker

is this even possible? how would i go about it? I've been using NFC Task Launcher but don't seem to be able to mange to do it within this app.

cheers in advance

a
[NFC Hacking] krohnjw:
There is a specific NDEF Message containing the MAC of the BT device that you can write to pair. However this precludes using NFC Task Launcher or other apps to perform other actions. This is only supported in JellyBean and up from an Android side.
[NFC Hacking] plaisthos:
Sony Android 4.0 supports this too.

If you a tag with the special NDEF tag it will do everything you want. I think news version of TagWriter can do this. If phone is routed to the external BT device depends if the bt speaker support headset or not
[NFC Hacking] hollywoodfrodo:
Here's a video review/demo of an app I use called BT Tag Writer: http://youtu.be/u1z6-pa_1Wc

Just have the andytags nfc sticker on my BT media receiver. When I tap it, it turns on my BT on my phone and then automatically connects to the media receiver.
[NFC Hacking] mtmerrick:
Thanks for this. Have now upgraded my Phillips Fidelio dock to NFC tap-to-pair! Goodbye horrible Phillips app!

Also, this works just fine with Samsung TecTiles. :)
[Galaxy S III General] Glebun:
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
[Galaxy S III General] thekoRngear:
Yank's kernel has the fix too, I think.

Two questions:

1. When boot into Download Mode- is it safe?

2. Someone said about charging the phone when it is off and off the wallsocket. How about the fix/security then?
[Galaxy S III General] danarama:
Could the failure process already have started? I'll put a caveat next to that....
[Galaxy S III General] theslashy:
As far as i know he had siyah kernel installed
[Galaxy S III General] yahyoh:
BTW cm team add the patch too ;)

http://review.cyanogenmod.org/#/c/29932/
[Galaxy S III General] danarama:
Thanks. Signed off my Andrei today so I assume that appears in tonights nighty?

#

Sorry guys, ran out of thanks today :)
[Galaxy S III General] mjb:
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
[Galaxy S III General] danarama:
That would make sense as its the kernel not the rom that has the fix. Has anyone got a link please?
[Galaxy S III General] danarama:
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
[Galaxy S III General] geus:
Great thread. Hope for news regarding the recovery. :)
[Galaxy S III General] montage mahal:
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
[Galaxy S III General] Phil3759:
PhilZ Touch 4.00-b04

Download:

- odin: http://www.mediafire.com/file/3g6ke58rsvs3j8y/philz_touch_4.00-b04-i9300.tar.md5

- cwm: http://www.mediafire.com/file/m6z7wwrd20pd9ln/philz_touch_4.00-b04-i9300.zip

This version wouldn't have been pushed as I did not plan any updates of the binary before 4.00 Final. But since we needed a repack with XXELLA kernel and the code was ready for these changes, I pushed it.

Changes:
[Galaxy S III General] SotirisBK:
I do not feel like it is so much of a risk to flash via odin. Unless you are a noob. I am a noob but I usually read a lot before doing anything on my device.
[Galaxy S III General] danarama:
Yes indeed but ts a real issue even if you never flash anything.
[Galaxy S III General] mjb:
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".

I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
[Galaxy S III General] danarama:
Yep no worries. I have reworded the OP a little more to reflect. Please feel free to help me phrase it :)
[Galaxy S III General] alkanbw:
I think that best solution is to flash PhilZ Touch 4.00-b04 as is based on XELLA (secure) and using XELLA reom with kernel or Perseus. PhilZ recovery works with exfat - Yank kernel not - so is for me useless
[Galaxy S III General] yuck03:
Great news! I hope with this recovery we can avoid SDS issues!.

Thanks for your help and effort
[Galaxy S III General] Phil3759:
Thanks rootSU for all your support (sorry, out of my 8 thanks as always)

Just an edit to the op: stock recoveries: instead of none, maybe add XXELLA ;)

Bye
[Galaxy S III General] vostikan:
I can't simply make that he asks - I am a newbie ((

tnx a lot
[Galaxy S III General] danarama:
Andrei seems to be saying there are two dates...

1) The firmware date - this is the date the commands execute from the kernel if this date matches. The date of the firmware version

2) The Production date - this is the data the eMMC was physically manufactured, not relevant to firmware version
[Galaxy S III General] qavro:
it means that we can have a VTU00M made in december but it can still be flashed with the doomed 13/04 firmware :(
[Galaxy S III General] danarama:
Yep. It means if you have VTU00M 0xf1, assume you're not safe.
[Galaxy S III General] qavro:
i already assume that. i am assuming i am not safe even when i am leaving my house. But at this moment i am not going to give up to paranoia and i will just wait. My phone works too well to mess with it, and unless my rom does not come with a patched Syiah and a cwm also in one package, i choose not to give a f..ck

if it breaks, so be it.

my brain already hurts after all the fuss on 4 different threads in the last 4 days.

i give up.
[Galaxy S III General] dukdalf46:
My s3 is now 215 days old, and I have the affected chip. Why is mine not dead?

Or do not all s3 suffering sds?
[Galaxy S III General] danarama:
From post 1 ;)
[Galaxy S III General] danarama:
See post 1 to check if you're affected.

If you are affected, I answer your question with another question. How do you put a time frame on data corruption?

:)
[Galaxy S III General] zyclops1:
Yeah official one :o
[Galaxy S III General] MIKEMON:
Especially not to panic, to do what is necessary / recowery, kernel / and nothing more.

Yet.
[Galaxy S III General] \m/aximuS:
I dont have warranty. I am so scared to loose my phone :(
[Galaxy S III General] dukdalf46:
I read somewhere it should happen between 150 - 200 days.
[Galaxy S III General] danarama:
It's not possible to reliably estimate when dodgy firmware will cause a data corruption. Its circumstancial not on a timer
[Galaxy S III General] quebec1:
i installed omega rom with its kernel stock (xxella) and PhilZ Touch recovery v4.00-b4. I'm good like that?

sorry for my english
[Galaxy S III General] Matthousef1:
Just checked my S3 with eMMc check and it turns out that I have Date 04/2012 / Type: VTU00M / FwRev: 0xf1, so I am basically the "target", but I am not going to sweat just yet..I am on Omega V36 with XXELLA, I have Perseus 31, the latest bootloader and what more can I do ? If it goes, it goes, nothing I can do about it..I would be angry, look at it, realise I can't do jack s*t about it and I will have to bring it to Samsung Repair Center..s*t happens...
[Galaxy S III General] danarama:
IF the fix is complete and working, to say you can't do anything about it would be inaccurate. But yeah, it's not the end of the world if it happens
[Galaxy S III General] Matthousef1:
Well ofcourse I hope the fix of Perseus helps..better to prevent s*t happening ofcourse, then to loose it all and be sad about it..but a lot of people are all going Maya-end-of-the-world crazy about it and I think it's still a piece of hardware that can break in 10 more different ways then only the SD issue..don't get me wrong, the S3 is the best phone I ever had, at least in my opinion (and I came from a iPhone), but in the end of the day it's just a machine which makes life only a little bit easier..my life is not depending on it ;)
[Galaxy S III General] danarama:
Totally. I've had mine die and I knew that it would be repaired. Its almost a bit "get over it" but I did hate the blackberry I used while being repaired.

Whats the warranty period on Samsung btw? My HTC desire was 2 years
[Galaxy S III General] Matthousef1:
It's 2 years..I think it's standard in Europe that they have to give you a 2 year period warranty, so I am not scared, I had mine since August last year, so warranty is still valid and I am basically in the "150-200 day period" now, so fingers crossed ! :p
[Galaxy S III General] Kjc99:
Re: [Important] Sudden Death Fix - Are you covered?

If you search you can find a zip to flash XXELLA bootloader in CWM very easy to do...
[Galaxy S III General] Kjc99:
Re: [Important] Sudden Death Fix - Are you covered?

I'm having a dilemma I'm reading a lot of bad things about XXELLA on the freezing threads and people are saying to avoid this kernel I am running this on my phone and also my brothers we have no freezing problems.... Yet So my question is (maybe directed towards Rootsu) is there any difference from XXELLA To XXEMB1 kernel / Rom? I know they are both based on the update 7 sources or if it's working don't mess with it...... Opinions?
[Galaxy S III General] kadopt:
Re: [Important] Sudden Death Fix - Are you covered?

Mate XXEMB1 is a leaked rom and may not work properly, so if you have the safe rom and kernel and have no issues it's Ok. You can also use perseus kernel that is also safe and has tweaks and optimizations. Also the freezing may be the rom fixing issues with the emmc.

Cheers

[EDIT] I confused xxemb1 (4.1.2) with xxufmb3 (4.2.1), sorry! Flash at will! :) [/EDIT]
[Galaxy S III General] Kjc99:
Re: [Important] Sudden Death Fix - Are you covered?

Are MB1 and LLA pretty much the same kernels since they are from the same update 7 sources I'm using Omega Rom and I like to stick with the stock kernels to much optimization in the others why would some people in freezing thread say to stay away from XXELLA and move onto MB1?(not experiencing any problems with freezing or rebooting)
[Galaxy S III General] diegoviola:
But should I upgrade to XXELLA? I'm reading lots of people saying that they have upgraded to XXELLA, and then they say that they are going back to ICS bootloader. What's the deal here?

Does XXELLA fixes the SDS issue in the bootloader/download mode? And does it cause other issues?

Please advice, thanks.
[Galaxy S III General] danarama:
Re: [Important] Sudden Death Fix - Are you covered?

The issue with the new bootloader is that it sets your custom flash counter up every boot so if you have custom kernel etc, it will show in download mode that you are modified.