yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Hosh0:
Hey all,

Basically I am curious as to how to check if S-On or S-Off cause I want to flash to a different radio and have heard that if my phone is set to S-off I can brick it by flashing the wrong radio?

I read in a lot of places that going to the bootloader will tell you, but I can't see anywhere on the bootloader screen that talks about S-On or S-Off.

Any help is greatly appreciated.

P.S For what it's worth I basically bought a phone from someone and it came with a Madaco ROM and it works fine, however I have since tried AOKP and now a new JB (4.1) ROM and both have had this issue where the signal drops and then reconnects, so I am thinking of flashing the radio to see if it fixes this problem for me?

Thanks
[Samsung Galaxy Nexus] Zepius:
We don't have s on or s off .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ÜBER™:
HAHAHAHAHAHAHAHAHA

Okay sorry.. this phone isnt an HTC. :) there is no S-on or off for this phone. In order flash a radio you can preform this command

fastboot flash radio name-of-radio.img

if cdma

fasboot flash radio-cdma name-of-radio-cdma.img

There you go bud :)
[Samsung Galaxy Nexus] Hosh0:
Ah right that explains it! Thanks was driving me crazy. So then can I flash the radio from clockwordrecovery? Or Should I do it via the command line?
[Samsung Galaxy Nexus] ÜBER™:
boot into the bootloader.. you can do this with command prompt (if you have the android sdk)

adb reboot bootloader

Or power off the phone. Hold the Power Button and both volume keys until the giant android screen appears. Then you can type

fastboot devices

To make sure it detects the phone as a fastboot device.
[Samsung Galaxy Nexus] I Am Marino:
Command line just because it's good to learn it that way personally.
[Samsung Galaxy Nexus] Hosh0:
Okay will do it when I get home tonight. Thanks heaps for all the help!
[Samsung Galaxy Nexus] ÜBER™:
LOL then hit the Thanks button :)
[Samsung Galaxy Nexus] Hosh0:
Ah I just keep making an ass of myself today don't I!
[Samsung Galaxy Nexus] ÜBER™:
LOL nah its alright ;)
[Galaxy S III Q&A, Help & Troubleshooting] CuBz90:
I've noticed talk of different SGS3's in certain countries, sorry if this sounds a bit of a stupid question but I'm confused.

What are the differences between these devices, and why are there differences? Why not just ship the exact same handset worldwide?

Thanks
[Galaxy S III Q&A, Help & Troubleshooting] dr.m0x:
Except for north America they are just different firmware. Hardware is the same.

The reason is different languages, modems and in some cases locked to a certain carrier or with carrier branded firmware.
[Galaxy S III Q&A, Help & Troubleshooting] CuBz90:
The reason I'm confused is because I've noticed some people saying they bricked their phone because they accidentally followed the root instructions for the international version (something like that anyway).

Also I'm sure I read somewhere that the international SGS3 has a different (better?) processor. Is this true?
[Galaxy S III Q&A, Help & Troubleshooting] NatTheCat:
The International version Uses - Quad Core &1GB RAM

The American version Uses - Dual Core & 2GB RAM - Due to LTE being a battery hog - LTE is super fast internet

The Korean Version Uses - Quad Core & 2GB RAM - Don't know why they got that maybe because its Samsung's home town - Brown Nose

Anyway there all the same on the outside. That's all i can tell you but I'm sure somebody else will fill you in

My name is Optimus Prime and I send this message..
[Galaxy S III Q&A, Help & Troubleshooting] HellcatDroid:
Hardware is different - as already stated - so drivers from the international I9300 won't work on those and hence "brick" it.

Firmware / ROM / OS / whateveryoucallit differs a lot on those models too, down to the partition layout. It's a nightmare what Sammy did there this time.
[Galaxy S III Q&A, Help & Troubleshooting] Idan73:
So, no hope for anything resembling, hellraised rom or at least framework for these, right?

Sent from my SGH-I747M
[Galaxy S III Q&A, Help & Troubleshooting] veyka:
NA SGS3's use the qcom S4 over the exynos quad, thus roms and kernels will not work across them, and flashing an international rom on a NA phone will brick it.

There is no foreseeable way to simply and easily port roms across (aka nothing as easy as hellraising).
[Verizon Samsung Galaxy S III] Immolate:
http://www.androidcentral.com/samsung-offer-hacker-friendly-developer-edition-galaxy-s-iii

Bit late for lots of folks and $599.
[Verizon Samsung Galaxy S III] jmacko:
Three cheers for Samsung doing the right thing, about a month late.

A better choice would of been, a developer portal website, where we send you our IMEI, you mark our warranty as invalid should we brick our phone, and then give us a file to unlock our bootloader. I'd even pay a reasonable, less than $50 processing fee, for your effort.

Earlier on a conference call with Verizon and Samsung, the following happened.... ( For the Verizon and Samsung suits, the below is satire, if I got it right, it's a coincidence...)

Samsung: Verizon, we told you that you were going to piss off the tech influncers, they're going to badmouth the S3 on your network and people will consider other carriers. Your dumb ass move of locking the bootloader is now costing us support calls, as we try to explain your poor decision. The right thing to do, as we told you earlier was not to lock it.

Verizon: Heck no, we're not doing it. We don't want the warranty and support headaches, besides they're all just a bunch of hacker thieves who will destroy our network, break their phones and cry to us when they brick.

Samsung: Your dumb move is hurting our brand and your brand too. (Thinking: But you're too stupid to see it.) What if we made you a limited quantity of S3's of of the S3's on your network without locking the bootloader.did a developer phone. You could sell it to a limited customer base for a small up-charge and make everyone happy. This way you could limit the amount of so called "hacker thieves" while keeping the influncers happy and give us a consistent message where we don't have to lie.

Verizon: We're not selling it.

Samsung: You'd be able to make peace with the influencers, you know that group that is all excited about our products, and convinces their friends to get it on your network. They'd love you for it.

Verizon: We're too big to have a different process for the phone same phone. We'd have mass confusion everywhere, support, service, retail and we'd loose money on it.

Samsung: You need to do something about this. It's only going to get nastier as you deliver more phones. All the other carriers didn't lock, and you simply look stupid for doing it. Your confusing message sounds like paranoia mixed with PR lies. Nobody is believing you, and you make us look bad.

Verizon: We're big enough. We don't care. Let them whine, they'll quiet down in a while.

Samsung: We'll if you're not going to do anything at least let us do something. Let us build a model with an IMEI which you'll allow on your network, which doesn't have a locked bootloader. We'll sell it, support it, and handle warranty. We'll call it a developer phone.

Verizon: Grumble Grumble.... Fine. This issue is over and the last we'll talk about it. Goodbye. Click. Those Samsung guys need to grow a pair. <Laughter>

Samsung: What a bunch of morons in suits.
[Verizon Samsung Galaxy S III] DarkManX4lf:
Well this is good for those who want to install roms and what not. It sucks for those who are trying to get the Sgs3 as an upgrade on Verizon.
[Verizon Samsung Galaxy S III] dannieloco:
this is awesome thanks! I woulda never though samsung would do this.
[Verizon Samsung Galaxy S III] DarkManX4lf:
They also do not say if you are paying $599 to get the 16gb version or 32gb.
[Verizon Samsung Galaxy S III] Smac7:
so its essentially the sprint version except it works on Verizon.
[Verizon Samsung Galaxy S III] kova05:
http://www.engadget.com/2012/07/28/atandts-garnet-red-galaxy-s-iii-for-vampires-we-go-hands-on/
[Verizon Samsung Galaxy S III] racer38:
So are there actual hardware differences in the Version S3 and the Developers version or is it just in the firmware ??:confused:
[Verizon Samsung Galaxy S III] xsteven77x:
I pray to God their isn't and we can just Odin their firmware.
[Verizon Samsung Galaxy S III] abissel22:
Taxing Developers?

So now verizon and samsung decide to tax us for being developers? No one needs to buy this. Kexec the verizon version untill we can crack the bootloader!
[Verizon Samsung Galaxy S III] Neverendingxsin:
At this point i doubt many people will be purchasing this phone. Had samsung released it a few weeks ago then i bet more people would have bought it, but they've waited too long now.
[Verizon Samsung Galaxy S III] xsteven77x:
yep is gonna be a failure. And the dev community is gonna be non existent cause no one will have it. All that is gonna be good for is hopefully we can steal their bootloader and such.
[Verizon Samsung Galaxy S III] neyenlives:
if the bootloader on the dev phone is usable on the locked handsets...thus unlocking them....then the development for this phone will become bigger than ever....
[Verizon Samsung Galaxy S III] cshort0982:
I plan on buying one when it is released in spite of Verizon.
[Verizon Samsung Galaxy S III] pyrostic:
When you do I hope you rip what we will need as a community for development.
[Verizon Samsung Galaxy S III] JBO1018:
I hope to hell it's as easy as you guys are thinking it will be. Unfortunately I would NOT count on it.
[Verizon Samsung Galaxy S III] meishkov:
haha that would be hilarious and so awesome at the same time if the whole unlocked bootloader stock image could just be flashed in odin to bypass everything else. I was sayin the devs in charge of the $3k in donations to the bounty for unlocked bootloader should just offer that money to somebody at Verizon...like somebody should email one of the execs, not CEO, but a little lower, execs are ALWAYS lookin to make some extra bucks. Or at Samsung, I'm sure there's some software that can unlock that they possess. I came from the OG and have only this for like 4 days, and I'm extremely missing the freedom I had. It's like moving to North Korea or Cuba, naw more like North Korea:eek:
[Verizon Samsung Galaxy S III] greevedogg:
^^you had me laughing at that!

....North Korea!
[Verizon Samsung Galaxy S III] piiman:
We can use it to point out to the fcc that vzw's excuse for locking the bootloader on a block c device is bull crap.
[Verizon Samsung Galaxy S III] abissel22:
They really are trying to tax us now. This prooves they only care about money, not improoving their products..

http://m.samsung.com/us/mobile/cell-phones/SCH-I535MBDVZW
[Verizon Samsung Galaxy S III] aaCharley:
The only thing actually released about the Developer Edition of the Samsung Galaxy SIII has been two web pages. One for the 16 Gb model and one for the 32 Gb model.

It cannot be difficult to cut some junk encryption feature out of the phone and let it out the door. Delay is further evidence of Verizon defrauding customers but using Samsung to get the job done with fewer finger prints.
[Nexus One Q&A, Help & Troubleshooting] kendoori:
I ordered the new Galaxy Nexus HSPA+ but am having 2nd thoughts because of size. I rather like the N1 forum factor, but would like a newer device with more memory and faster processor. What are the options? I'm currently running CM 7.2 on my N1.
[Nexus One Q&A, Help & Troubleshooting] taodan:
Maybe Nexus S or Galaxy S
[Nexus One Q&A, Help & Troubleshooting] m2xtreme:
Do you live in an area that doesn't have 4G LTE yet or something? If not, why would you buy a faux-G HSPA+ phone? They way I see it, your best bets for LTE are the HTC One X or the SG III. The One X sucks because it doesn't have an sdcard slot, but it has a button layout closer to the N1. The SG III isn't my style, but to each his own. If you're feeling crazy you could get a Galaxy Note, but it's huge. Or if you buy into the rumors, wait for the Galaxy Nexus to be released with LTE (supposedly AT&T is testing it, but who knows...).

Regardless, you won't find a pure android LTE phone of small screen size with a trackball for AT&T that's better than the N1. And that is such a shame!
[Nexus One Q&A, Help & Troubleshooting] XeloOw:
I suggest you the htc One V
[Nexus One Q&A, Help & Troubleshooting] Iperzampem0:
I'd have bought a grey HTC One S, it's very similar estethically to our N1 and it's beautifully fast :)
[Nexus 7 General] MikeMurphy:
Just saw this. Anyone rec'd the update yet?

http://www.engadget.com/2012/07/10/nexus-7-tablet-now-receiving-android-4-1-1-update/
[Nexus 7 General] FrayAdjacent:
I wonder how long until the CDMA version gets it. It seems the CDMA GNex is the bastard child, and doesn't get the same attention.

You GSM GN owners can get the nice pogo pin dock off the Play store for $55. Us CDMA GN owners gotta go directly to Samsung and pay $90 for basically the same thing.

That's one of the major reasons I'd love to go get an SIII right now. All of the accessories work with all of the carrier's versions. Making the GN different was a mistake.
[Nexus 7 General] MikeMurphy:
Oops. Fixed. Had the wrong forum.
[Nexus 7 General] fixyourtech:
Ya the cdma versions aren't really true Nexus devices :cool:
[Nexus 7 General] 18t:
Want my cdma jb update. 4.04 made my gn laggy.
[Nexus 7 General] WinDroidGuy:
Here is the update

http://xdaforums.com/showthread.php?p=28577629#post28577629
[Nexus 7 General] colonel187:
you can thank Verizon for that.
[Nexus 7 General] bso44:
If I take this OTA out of the box, will it prevent me from unlocking the bootloader and rooting?
[Nexus 7 General] tomh1979:
it's a nexus device, of course not since they are technically considered a developer's device, unlocking the bootloader is pretty much a standard feature.
[Nexus 7 General] bso44:
Gotcha....thanks. This will be my first Nexus device so I wasn't sure.
[Nexus 7 General] clockcycle:
OTA just gave me Build Number JR003D
[Nexus 7 General] big samm:
Should I update or not?

View attachment 1204653

Sent from my Nexus 7
[Nexus 7 General] Shano56:
Yes
[Nexus 7 General] sirdevinster:
Yes, I updated the system today when I received it.
[HTC ChaCha] adlx.xda:
Hi,

This is a dev thread about the fight for the camera in ICS on the HTC Chacha.:cowboy:

I'm trying to load the libcamera.so and liboemcamera.so from a STock Sense Chacha rom (Gingerbread).

This afternoon I managed to fix the linker errors so camera.chacha.so loads libcamera.so.

I/CameraHAL( 98): camera_get_camera_info: id:0 faceing:0 orientation: 90

I/CameraHAL( 98): camera_get_camera_info: id:1 faceing:1 orientation: 270

V/CameraHolder( 1213): open camera 0

I/CameraHAL( 98): camera_get_camera_info: id:0 faceing:0 orientation: 90

I/CameraService( 98): Opening camera 0

I/CameraHAL( 98): camera_device open+++

I/CameraHAL( 98): Switching to HTC Camera: 0

I/QualcommCameraHardware( 98): openCameraHardware: call createInstance

D/QualcommCameraHardware( 98): createInstance: E

D/QualcommCameraHardware( 98): Storing the current target type as 3

D/QualcommCameraHardware( 98): constructor EX

D/QualcommCameraHardware( 98): startCamera E

E/QualcommCameraHardware( 98): Unable to determine the target type. Camera will not work

E/QualcommCameraHardware( 98): createInstance: startCamera failed!

D/QualcommCameraHardware( 98): ~QualcommCameraHardware E

Now the problem is that it gives an error in QualcommCameraHardware::startCamera: "Unable to determine the target type":silly:

I believe I know why though... I'll test another day.

Here it is:

In libcamera.so:

Failed to set default parameters?!

initDefaultParameters X

ro.board.platform

Storing the current target type as %d

persist.debug.camera.showfps

constructor EX

...

msm7k

qsd8k

msm7x30

...

I believe it uses the parameter ro.board.platform, which is ro.board.platform=msm7x27 in our CM9 to set the target, and that the allowed values are: msm7k, qsd8k and msm7x30.

I'll test altering the build.prop just to confirm it. If that is true, I'll have to find a way to fix that...

Anyway, I'm pretty happy about that, it's a step!
[HTC ChaCha] adlx.xda:
Yes!! I have managed to work around the target error!

DEBUG/QualcommCameraHardware(98): Storing the current target type as 0

Here is a logcat: http://logcat.miui.us/907002

The camera app still crashes... Idk what is the relevant error. I see no preview.

Maybe:

167:	07-11 01:54:31.381: ERROR/mm-camera 7x-vfe(98): Received VFE start ACK!!! This is a user preview start.
[HTC ChaCha] Flexmaen:
Thanks for working on this problem!

I use CM7 and the camera really costs me nerves there. With Pro Paint Camera I found an app that does not crash soo often, but still it is not 100% perfect (as images are 90° rotated and you can't make videos).

So any improvement on that camera issue is good news!
[HTC ChaCha] adlx.xda:
Note to self:

DEBUG/Camera(828): app passed NULL surface

ERROR/mm-camera 7x-vfe(98): Received VFE start ACK!!! This is a user preview start.

Those same messages are shown in with CM9 + Aria's libs (which works OK) and in CM9 + stock libs (which doesnt work), so I guess they are irrelevant.

Logcats of opening the camera:

Chacha CM9 Cam w/ Stock Libs: http://logcat.miui.us/907002 (Preview fails)

Chacha CM9 Cam w/ Aria Libs: http://pastebin.com/sFBWVc8g (Preview ok, pictures OK)

Chacha Stock GB w/ Stock Libs: http://pastebin.com/0A6BmtxQ (Everything works)

DEBUG/CameraSettings(828): Parameters:

Chacha CM9 Cam w/ Stock Libs, Params: http://pastebin.com/uyuKxjds

Chacha CM9 Cam w/ Aria Libs, Params: http://pastebin.com/CXemXgdt

Diff Aria params vs Stock: http://pastebin.com/GbcJB0Qf
[HTC ChaCha] Alex C.:
All I can see from that are the memory leaks starting @ 0x3b2f0.
[HTC ChaCha] adlx.xda:
Wondering if Change I7c0a2976: msm7x30: Camera HAL for HTC Sense devices (3/2) could have anything to do with the issue...

Tried either pref_camera_force_preview_default on and off, the same error.

I have also build and tested https://github.com/commonsguy/cw-advandroid/tree/master/Camera/Preview fails , and it fails too, so the issue is maybe not in the Camera app... (unless it is in the preview part of it)?
[HTC ChaCha] MagicalSword:
On the requested preview size, we get:

118:	07-11 01:54:31.151: DEBUG/QualcommCameraHardware(98): requested preview size 480 x 320

And the Aria libs are clearly substracting from both x and y to take into account the viewport is not as big as the whole screen, as we have to leave some margins to the UI and such, right? Maybe the trick is to adjust this in line 2205 and 2207 in Camera.java via a wrapper function, depending on the optimalSize() returned...

I wish I could set up a working compiling environment to help you, maybe once I'm back from holidays...

Keep it up and thanks for your hard work! Cheers!
[Android Apps and Games] jacari91:
To me, the Craigslist apps for android don't look very good. So I tried my hand at designing one that meets my need.

This is a work in progress, so any critiques are welcomed.

Unfortunately, I don't anything about coding. So this is just a concept for now.
[Android Apps and Games] Aaron78:
I love this. When do you plan on releasing it. I am willing to test it out for you.
[Android Apps and Games] nyydynasty:
when someone can create a craigslist app that I can manage or repost expired posts (that was a weird sentence), I'll be happy.
[Android Apps and Games] Salviikiddd:
That's pretty good, I really like it. I look forward to you releasing it. I'm also willing to test it out for you. :)
[Android Apps and Games] MyNarwhalBacon:
I recommend an inverse colored option. It looks like it's coming around quite nicely! Great Job!
[Android Apps and Games] flamebeats:
Nice. I would like a red version!
[Android Apps and Games] jacari91:
Thanks. Unfortunately, it will probably be a while before its out. Have to lean how to develop an apo first lol

Edit: Also, here's an update on the design. There are still some issues.
[Sony Xperia P, U, Sola, Go] RonGerNer:
Has anyone else that has Studio Beats by Dr.Dre noticed that there cable into the Xperia S keeps pushing itself out? Anytime it even twists a little bit it falls out!
[Sony Xperia P, U, Sola, Go] Sikiduck:
I got the Studio as well, not experience the same problem as you. Maybe there something in the audiojack plug like piece of fabric/dust that makes the Monster plug not going all the way in. :)
[Sony Xperia P, U, Sola, Go] keulieminogue:
I have senheiser hd headphones ans i has to cut some Plastic it Themen Jäckel That helped... Themen problem is the plug... There is no other chance...
[Sony Xperia P, U, Sola, Go] JoelChrist_:
Same over here, just put the phone top down in your pocket, that'll do it
[Sony Xperia P, U, Sola, Go] optik19918:
I have the in ear one and no problems here
[Sony Xperia P, U, Sola, Go] Lord Takyon:
All connections to mine are loose, except the ones that came with it.

Sent from my XperiaS via transwarp conduit.
[Sony Xperia P, U, Sola, Go] neizel:
AKG 530 here, no problems.

Enviado desde mi LT26i usando Tapatalk 2
[Sony Xperia P, U, Sola, Go] SkaterOllie795:
I have the Solo HDs and they fit in really nice and tight.
[Nexus S General] nexom:
Official 4.1 being pushed out to galaxy nexus owners how long before we get it?
[Nexus S General] Kitch16:
Yay. Another completely new and useless thread about a topic that has already been covered in about a thousand other threads.
[Nexus S General] g1user101:
ARE YOU F'ING KIDDING ME? Can't read?
[Nexus S General] .OmEgA:
What's jelly bean?
[Nexus S General] SimDroid:
It's Billie Jean's brother.
[Nexus S General] .OmEgA:
Get out of town! No way that's true!
[Nexus S General] Kitch16:
WOW. First time I've heard anything about Jelly Bean :O
[Nexus S General] sykomaniac:
Jelly bean thought the next android version was donut? Must have missed something

Sent from my Nexus S
[Nexus S General] Kitch16:
Android? What's Android? O.o
[Nexus S General] IRX120:
I think its that new robot the governments building to take out its opposition XD
[Nexus S General] .OmEgA:
Its a turtle you idi0t!
[Nexus S General] albundy2010:
You think this a bad? Just wait until the ota is announced how many stupid threads pop up. How do I get it. It won't install. Need fully stock and locked bootloader. Oh and if you tap on update now 23 times while sitting on the toilet and 235am you will get it. Worked for me!
[Nexus S General] 063_XOBX:
Yeah, updates bring all the truly stupid people out of the woodwork.
[Nexus S General] bravo04:
This is called OTA syndrome.
[Nexus S General] 063_XOBX:
Google has decided to do a social experiment. Once the Nexus S section of the forums goes 24 hours without ANOTHER JB thread they will release it. So I guess the answer is never.
[Nexus S General] slysurfer:
Jelly Bean 4.1 and the Kandy Cane

I installed Jelly Bean 4.1. from http://xdaforums.com/showthread.php?t=1764119 and so far I am really please with this update and i am looking forward to the official rom and then the many variations of the rom, that many developers create - AOKP, CM10 etc.

After I installed this rom, I wanted to bring up the Jelly Beans - go to - settings - about phone - then tap the version 4 times quickly, then up pops the jelly bean View attachment 1190371 - then you just press and hold the bean and then up pops the animated image, with all jelly beans - View attachment 1190345

I did notice a Kandy Cane, floating amongst the jelly beans, I wonder why???????

Can this possibly indicate that the next update maybe - Kandy Kane. Or will we see the next major update around Christmas possibly. I just thought I'd ask what everyone thinks. I am curious :-)
[Nexus S General] .OmEgA:
If the next version is "kandy cane", Google needs to fkucin learn how to spell!!!
[Nexus S General] veyka:
Closed, we have multiple thread on JB, when JB will be pushed via OTA, when JB will do a little dance, we don't need another.
[LG Optimus Black] B1gben:
hi guys, i got this problem, when i connect my phone to the pc, it dosen't find the drivers and i cant update my phone, can u help me? i've have adroid version at 2.2.2 and my software version is V10C. i've already tried a lot of way but no one works...
[LG Optimus Black] tantrums:
Download the drivers and software in LG website. Install it in your PC.