yashsingh1/xdaforums huggingface dataset:
[Off-topic] avgjoegeek:
Real Dev's code in Python (j/k) ;)

But they all stated good things - pretty much pick a programming language and start from there. If it's Android development it is going to be Java (ugh).

If your serious about wanting to develop? I would recommend C++ as the language to get involved with. From there it is easy to branch off to other languages.

There is a TON of free material on the internet (that isn't pirated even) to help you get started. Compilers, code samples, documentation.. there is virtually no limit to the amount of data that is out there.

The trick is... A) to figure out what you want to do and B) remained focus on your goals and keep working at it. Coding is NOT easy (I can't code my way out of a wet paperbag - but I understand it) but can be very rewarding both personally and financially :D

So good luck!
[Off-topic] girinovey:
Nah, I code for years and didn't get any of those rewards.. just lame jobs and no life!
[Captivate Q&A, Help & Troubleshooting] d1g1talphyre:
well, there is a free sim unlock tool in the android development section of the forums.

Then you could flash stock (seeing as the phone doesn't require a sim card to turn on and function), then sim unlock.

Then do as you please with it.
[Captivate Q&A, Help & Troubleshooting] dgemhsu:
I actually tried that when I first hot the phone before I gave it back to the cell phone shop to unlock and unfortunately it didn't work.

And the phone storage and text message thing happened again today and all I have done w the phone since yesterday was pair it w a blue tooth headset. Again the phone storage full notification popped up first and then the text message full notification popped up right after. I ended up installing the rest of the apps and still only have about 240mb of internal phone storage! Then the text notification also went away.
[Captivate Q&A, Help & Troubleshooting] SuperKeeper:
I'm having this problem as well so do you think that it is a simple internal phone storage shortage? I have only 165mb free and I KNOW for a fact that it is stopping me recieving texts as I get text notifications when someone tweets me and I have stopped recieving them, instead getting notifications that my text memory is full. Furthermore, I deleted a thread with over 400 messages in it to no avail so I shall get rid of some programs/move them to SD card until the memory full error goes.

SORRY I POSTED THIS IN THE WRONG DEVICE SUB-FORUM! MY APOLOGIES!
[Galaxy Tab General] Jeepsdaddy:
Can someone explain the whole bootloader issue to me in plain english? (The for dummies version)

If my current bootloader is unprotected

What can I do?

What should I watch out for?
[Galaxy Tab General] foxmeister:
Let's just say you drive a Ford car.

At the moment, you can buy original Ford parts, or you can go out and buy patent parts which are essentially doing the same job, but are not made by Ford (and usually cheaper). You can put any compatible spark plugs, oil, antifreeze in the car - it doesn't matter.

Now, say Ford introduce an "upgrade" - this upgrade changes your car so that now you can only put Ford parts on the car - you can only put Ford sanctioned plugs, oil, antifreeze etc in the car.

That's like a signed bootloader - essentially if you have signed bootloader you cannot change the firmware in your Tab to any other firmware that hasn't been digitally signed by Samsung.

Regards,

Dave
[Galaxy Tab General] quattr0:
Here is my limited knowledge so you could get an idea

Every OS needs a bootlader so it will load the kernel and boot up the system. You could think the kernel like the engine and the bootloader like the ignition/starter.

There are firmwares that include checksum capability in the bootlader so it will check the kernel for signature. If the kernel is not signed/protected, it won't load.

In the tar file that you load/specify in the PDA box when flashing to a different firmware, it includes zImage. This is the kernel that bootloader will load.

You should be happy that yours is unsigned. Don't load any firmware that listed as signed/protected bootloader or you might stuck with these firmwares only.

In theory, you could flash a different bootloader (the unsigned one) so it won't check for signature in the kernel and you could freely flash other things but it's been awhile that I've messed w Linux and not sure why Chainfire has such an issue with it.
[Galaxy Tab General] Jeepsdaddy:
Great explanation!...

So maybe you can help me with what I am looking for. When I flashed Roto's JME v4 (no signed bootloaders) on my Tab I ended up with no boot screen just a white line (rom works fine). For aesthetics and possibly trying to return to stock at&t (if warranty exchange is needed) how can I go about fixing the boot screen? Is this something I cannot do at the moment?

Can I go through this process here http://www.theandroidsoul.com/make-calls-with-att-galaxy-tab-full-guide/ although I've already flashed Roto's rom?
[Galaxy Tab General] Chainfire:
The secondary bootloader provides download mode. A signed SBL won't let you flash an unsigned one. That's the issue.

We have a workaround now, though, which replaces the bootloaders again with unsigned ones. That by itself isn't that much of an issue once you have it working, but getting it to work / testing was the problem. Because if it doesn't work, you have a true brick.

All of this is documented in the thread, so not sure why you still think you can just flash an unsigned bootloader.
[Galaxy Tab General] quattr0:
Ah must have missed that. Sorry & thanks for the expl.
[G2 and Desire Z Q&A, Help & Troubleshooting] andymyrick:
I'm currently running CM7 n7 and I was wondering there was a way for me to be able to set keyboard sounds like on the iphone? Not for the physical keyboard but for the actual on screen keyboard. Im using the gingerbread stock keyboard and was wondering if this was possible.
[G2 and Desire Z Q&A, Help & Troubleshooting] bahmanxda:
Im not sure if you want to enable the sounds or change them?

if you want to enable it settings>language & keyboard >android keyboard

and for changing the sounds i cant find any options

but if you know what you want you can find the files for it, and adb push it

something like

adb push <name of the file>.ogg /system/media/audio/ui

EDIT: two files you wanna replace are KeypressStandard.ogg and KeypressSpacebar.ogg
[Nexus One Android Development] RunTimeWorld:
I uploaded 2.2.2 aka FRG83G (google ota from FRG83D to FRG83G) to shipped roms, not sure how long it takes till they made it public.

http://0c0.co/fICEZj
[Nexus One Android Development] mgorman:
do you know what was changed?
[Nexus One Android Development] galaxys:
What does it do...besides unrooting you?
[Nexus One Android Development] RunTimeWorld:
I'm the wrong person to ask, it is the way it is, not a cooked ROM but a simple upgrade, i assume superboot from modaco would still work since boot.img doesnt seem to be changed.

I'm just sharing, not supporting.
[Nexus One Android Development] RunTimeWorld:
I assume the reported sms bug .. as written in my first post, haven't had the chance to test it yet.
[Nexus One Android Development] Turbocom:
Either Google pulled the file or the service really is unavailable either way its not accessible.
[Nexus One Android Development] mkrmec:
First... you CANNOT brick a phone with ROM update unless it has a radio update!!

Second... posting a untested link??
[Nexus One Android Development] MATPOC:
Get request to install this update by OTA. Waiting for rooting.
[Nexus One Android Development] RunTimeWorld:
Never mind...
[Nexus One Android Development] death1246:
f this Im going to 4chan
[Nexus One Android Development] Androith:
Suicide is
[Nexus One Android Development] wdfowty:
You should make a a stop by kingxklick.com while your at it. Good laughs there, too ;)

:D
[Nexus One Android Development] marcelol:
doubt that

he'll be back.....
[Nexus One Android Development] wdfowty:
f this I'm playing Black Ops

lol
[Vibrant Q&A, Help & Troubleshooting] ndwgs:
"@androidcentral: Nexus One Android 2.2.2 update pushing out -- Build FRG83G http://bit.ly/gQaj1l"

Dev's, there is a download link at that androidcentral site. Official leak from what I saw, or maybe?

Check it out!

Sent from my SGH-T959
[Vibrant Q&A, Help & Troubleshooting] Master™:
and... wrong section. lol
[Vibrant Q&A, Help & Troubleshooting] ndwgs:
Lol, dang, I realized that... Clicked on the wrong section on my phone.

MODS, please move this thread to the General Section, I meant to put it there, so sorry!

Sent from my SGH-T959
[Vibrant Q&A, Help & Troubleshooting] ndwgs:
Thanks for the catch Master. I was wondering why I saw my post on the Developer section. Im on myhone doing this, thats why....

Sent from my SGH-T959
[Vibrant Q&A, Help & Troubleshooting] krylon360:
and wrong device?
[Vibrant Q&A, Help & Troubleshooting] ndwgs:
Well, this is for porting purposes... From the looks of it, Nex 1 will also see this update soon, from the forums I read..

I don't know. I'm just wondering if we could port this...

Edit: thanks got the catch, again. Hey, I'm doing this on my phone, lolol...

Sent from my SGH-T959
[Vibrant Q&A, Help & Troubleshooting] masterotaku:
And why exactly would the Nexus S see a downgrade to 2.2.2?? LOL
[Vibrant Q&A, Help & Troubleshooting] VICosPhi:
Cant wait for Vibrant to get this update if it fixes the SMS bug
[Vibrant Q&A, Help & Troubleshooting] Master™:
He said Nexus One.. not Nexus S
[Vibrant Q&A, Help & Troubleshooting] ndwgs:
Swype-poed

Sent from my SGH-T959
[Vibrant Q&A, Help & Troubleshooting] masterotaku:
He said..in reply to another post...

Wrong device, wrong section, wrong assumptions, and an apparent inability to realize that 2.3 > 2.2.2.... :)

If you're gonna call me out on a quote, at least read it first? :)
[Vibrant Q&A, Help & Troubleshooting] jellette:
Regardless of all that..

It's only a 500kb bugfix, so you have to already be on 2.2.1 to get it to bring you to 2.2.2, will check it out anyway - Thanks!
[Vibrant Q&A, Help & Troubleshooting] r0man:
Let us examine this thread:

Is it development related?: No

Is it about the Vibrant?: No

Is it about a device similar to the Vibrant (Galaxy S/Nexus S)?: No

Is it in a section where it doesn't belong?: Yes
[Vibrant Q&A, Help & Troubleshooting] ndwgs:
Thanks for the catch Masterotaku. Just typo...

And I meant to post it to the ' General' section, and I do know that it is the wrong device, I meant to post for PORTING purposes. :)

Sent from my SGH-T959
[Vibrant Q&A, Help & Troubleshooting] ndwgs:
Lololol... Let the flames begin!

@ Jellette, yes, you have to be at 2.2.1 in able to see this big fixes, based on what I've read thru forums. And from what I gather from them, they started to integrate it to 2.2.1 for Galaxy S I9000.... But who knows?

Sent from my SGH-T959
[Android Software/Hacking General [Developers Only]] kmulliger:
My wife just got a Citrus (CDMA) and I was able to root it, but she wants Froyo. It shipped with Eclair and I knew finding a Froyo upgrade would be a tall order, but, has anyone seen or heard about a Froyo ROM for the Citrus (aka Ciena)? I figure if I am going to get any answers, it will be here. Thanks to any and all that can provide some insight.
[XPERIA X10 Q&A, Help & Troubleshooting] sinkster:
Ok, no comment.
[XPERIA X10 Q&A, Help & Troubleshooting] PollPixx:
You can read others in at least 300 other threads, even on this first page, but it seems popular to start up the same discussion over and over and over again...
[XPERIA X10 Q&A, Help & Troubleshooting] batman_112:
PLEASE CLOSE THREAD. REPEATED A MILLION TIMES!! SEARCH PEOPLE PLEASE!!
[XPERIA X10 Q&A, Help & Troubleshooting] Buddha:
This has crossed all borders.
[Nexus S General] deeren:
Just created the new thread so that the url does not get lost in the android 2.3.2 thread with all the comments.

Hope the devs can tell us what's its all about.

http://android.clients.google.com/p...cd.signed-soju-GRH78C-from-GRH78.353e2673.zip

Update: Rooting is not affected and can be achieved following instructions from this thread for e.g

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

Those having stock ROM, with clockwork recovery, follow this excellent guide thanks to distortedloop.

http://xdaforums.com/showpost.php?p=10811723&postcount=29

those having stock recovery, to update:-

-Download the OTA package here

-Rename it to update.zip, and place it on the root of your internal storage

-Shut down your phone, and reboot into the bootloader by holding volume up and powering on

-Choose "recovery" from the list, and select it with the power button

When you see the red triangle press volume up and choose to update
[Nexus S General] jlevy73:
Nice thanks
[Nexus S General] SupaDupaFly24:
thanks!

10 characters
[Nexus S General] BartT-GSM:
root work after update to 2.3.2 ?
[Nexus S General] deeren:
i didnt update it though. I was waiting to see if a dev could enlighten us but nevermind :)) i'll try to update and try to root n let u know.

cross fingers.
[Nexus S General] ricardo99:
Thanks. Works fine on non-rooted Nexus S.
[Nexus S General] distortedloop:
I posted it over on the other thread just for those following it, gave credit to you.

This one patches everything in the /system/app folder, the /system/frame-works, and a few random files in other sub-dirs.

It also replaces/patches the recovery again and includes the script to re-flash it every time you change it.

Here's the patch script
[Nexus S General] deeren:
Just rooted with new update. so everything is fine. i'll get back to the nightlies then.

cheers
[Nexus S General] Darrien13:
Awesome :D
[Nexus S General] NVMENOR:
Thanks deeren.

Updated through stock recovery and everything’s fine, still rooted. I will have to re-flash clockwork again, but that was expected.
[Nexus S General] Jnowak1981:
Sorry for the noob question, but how do I apply this update? I tried downloading through the browser and the download fails. \do \i donload with PC and put on device manually?
[Nexus S General] meetagrawal:
Can you just put this on your SD card and go to Rom Manager and select Install ROM from SD card while you point it to this zip file?

Also does it disable your root, and then you have to root again?
[Nexus S General] NVMENOR:
Yes, you will have to root again (at least I had to). I used stock recovery because I think that way is safer, i don’t know about Rom Manager.
[Nexus S General] NVMENOR:
Do as follow if you have stock recovery

Edit: *When you see the "white" triangle press power button and volume up, then choose apply update from /sdcard.
[Nexus S General] amjad_2020:
it's work great one my rooted Nexus S
[Nexus S General] jwr2d2:
How do I go from cw to stock recovery without having to do to much

Sent from my Nexus S
[Nexus S General] Jnowak1981:
i boot into recovery i see the triangle and when i press volume up nothing happens...
[Nexus S General] krkeegan:
i believe once you press vol up to move the cursor onto update, you need to press the power button to select update.
[Nexus S General] Jnowak1981:
I dont get the option to update. It just stays on the screen with the android and a triangle with a "!"
[Nexus S General] jaker.the.skater:
same here

10 char
[Nexus S General] Jnowak1981:
nevermind, had to press vol up and power once at the triangle screen
[Nexus S General] jaker.the.skater:
im not getting anything when i do that
[Nexus S General] kenvan19:
If you update this then reflash a custom rom it will just overwrite it anyways. Roms are either built from scratch or on the basis of an update and nothing has been built on this. As I'm running CM7 I'll just sit tight on that. Might flash over to my stock NANDroid and update it but meh...maybe not.
[Nexus S General] jaker.the.skater:
can you tell me exactly what you did? because its not working for me

edit: got it now
[Nexus S General] NVMENOR:
For rooted android 2.3.1 and 2.3.2 (custom roms, different procedure maybe), to go from clockwork to Stock Recovery simply let this script do its job: /etc/install-recovery.sh make sure that the name of the file is exact as stated, use root explorer to properly rename It. Next time you reboot the phone, the script will flash recovery.
[Nexus S General] herman3101:
Hi,

I followed the steps to applying the update using the stock recovery but I never get the red triangle, instead I get a white triangle with a yellow ! and a green droid. I put the zip on the root of the internal sd and tried both keeping the original name and renaming it to update.zip.

I've applied the oem unlock but not done anything else to it.

Any ideas?

Cheers,

Phil

Edit: Figured it out.

For anyone else who has this problem. Once you are at the triangle screen, press and hold the power button and then tap the volume up button. This brings up the menu you need.
[Nexus S General] kramer987:
to all who use black gmail. i couldnt apply the 2.3.2 update until i put my gmail.apk backup back into system/apps. before i did, i was getting a system7 error with some jargon about the gmail.apk md5 not matching.

and to all those that are android challenged like me, this is how i did the update. (i just got my first android device in december so this was kind of a nice refresher course in rooting)

Step 1: i downloaded the zip file on the first post of this thread and renamed it to update.zip. i dont think you even need to do this but i did anyway.

Step 2: i went into rom manager and did install zip from SD card. i hit OK. it took me to a blue recovery screen. i pressed the power button and up and got 3 options. i chose to select the zip file. i selected my zip file and chose to install. it verified some stuff and applied the update and was successful. after this i lost superuser and root and clockworkrecovery.

Step 3: i powered off the phone and powered on into the bootloader. i opened command line and ran fastboot flash recovery recovery.img

it flashed clockwork.

Step 4: i powered off and then back on into bootloader and then into clockwork recovery (which was flashed in Step 3). I then chose the mount and storage option and selected mount system. i then went to install sd from zip and selected my superuser.zip file from when i first rooted the phone back in december. i ran that, it did some stuff and then told me it was done.

Step 5: i powered the phone on and superuser was working and so were all my root-related apps. I opened Rom Manager and flashed the latest clockwork (3.0.0.5). now i'm back to where i was before 2.3.2 came out, except i'm on 2.3.2.

Step 6: my old gmail.apk doesnt work anymore for some reason. it just force closes. not sure why. maybe there's a new one in the app market or something. but i use gmail black so i just copied that back using root explorer and everything is working fine again. if anyone knows why my backed up gmail.apk doesnt work let me know. i hate when little insignificant things dont work.
[Nexus S General] mhaedo:
Confirmed working updating from stock 2.3.1 with paulobrien's insecure boot image and ClockworkMod recovery 3.0.0.5. Still have root.
[Nexus S General] distortedloop:
If you're using stock ROM, CWM and are rooted, a simple way to do this update and maintain root without having to do a couple of reboots and use fastboot to reinstall CWM Recovery would be:

1) download the update from the link provided earlier in the thread.

2) place the zip in the root of the sdcard, rename it to update.zip.

3) download and place the su zip for root in the same place as the update file.

4) Reboot into Clockwork Recovery.

5) Select the apply sdcard:update.zip option. Let it run completely and you should end up back in the CWM menus.

6) Select the Mounts menu...mount the /system partition then return to main menu.

7) Pick the install zip from sdcard option, and then select the su binary to fix the su/root install (permissions need to be changed back to 6755).

8) Reboot.

You should be golden, but the reboot will have put back the stock recovery via that pesty script they install.
[Nexus S General] distortedloop:
Thanks, but there's already two other threads about this....

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

http://xdaforums.com/showthread.php?t=923860
[Nexus S General] SheerazRaza:
I thought I could just provide a direct link to downloading file.. So I created this, lemme post the links there, or you could just copy the link and tell others about it.
[Nexus S General] distortedloop:
Yeah, it was thoughtful, but both threads already have the links, one of them in the first post.

I suspect the moderator will merge this with one of them. ;)

Take care!
[Nexus S General] nyijedi:
I have clockwork recovery and tried this, but when I try to apply the update.zip file, I get this error message:

file_getprop: failed to start "/system/build.prop": No Such file or directory

E: Error in /sdcard/update.zip

(Status 7)

Installation aborted.

Any suggestions? I'd rather not flash back to stock recovery if I don't have to.
[Nexus S General] distortedloop:
I wonder if your update download is corrupted. I'd try downloading it again to be sure.

Did you try it the other way (selecting it manually with the other CWM option)?

You're going to end up back on stock recovery after the update anyways, no way around it unless you modify the update script to not replace it.
[Nexus S General] kramer987:
make sure its not named update.zip.zip
[Nexus S General] distortedloop:
That's a very good suggestion...I need to remember to remind people of that.

@nyijedi How did you apply root to your current device? There were a lot of Status 7 problems for people who used Paul O'Brien's superboot image method. Check out this thread and see if any of the suggestions in there help you out if nothing else works: http://xdaforums.com/showthread.php?t=885477&highlight=status+7
[Nexus S General] micric100:
I have the same problem, I've tried downloading the file again in case of corruption. It's on my brothers phone and he doesn't have root though, i'm still on stock 2.3. It's an unlocked phone and we're using it on rogers in canada if that makes a difference. I get a bit of a different error though, it sais something about that it cannot verify the file and then error installation aborted. And it's not named update.zip.zip, it's named correctly.

Any ideas?
[Nexus S General] distortedloop:
An uncorrupted download on a stock, unrooted phone with stock recovery should have no problem updating.

Don't rename the file if you're using stock recovery, just navigate to it from the Recovery menu...see if that works.

All phones are unlocked, so that doesn't matter, and being on Roger's shouldn't either.
[Nexus S General] nyijedi:
Thanks for all of the help, everyone. Turns out the problem was a result of using an old version of Clockwork Recovery. Once I updated it to the latest version, it worked fine. I then reapplied the superuser .apk before rebooting, rebooted, renamed the install-recovery.sh file again, and flashed Clockwork Recovery again through ROM Manager. Everything is now working. Thanks!

@micric100: What version of clockwork do you have? The latest version is 3.0.0.5. If you're not running this, flash it via ROM Manager and give the update another shot.
[Nexus S General] distortedloop:
Glad it got worked out for you. Good tip on current CWM; I always assume people have the latest of everything.

Not having to push CWM via fastboot makes it a lot quicker and can be done on the fly without your computer handy.
[Nexus S General] micric100:
I tried that too. I just have the stock recovery btw, I don't have the Clockwork recovery. I just don't understand, I guess i could try rooting it and installing clockwork, but my brother really doesn't want me to do that, so I would prefer not to. It should work anyways

Edit: here's the exact error:

Finding upadte package...

Opening update package...

Verifying update package...

E: failed to verify whole-file signature

E:signature verification failed

Installation aborted
[Nexus S General] distortedloop:
Oh, you know what, I'll bet you're on one of those "debug" phones.

What's the version number of your phone and kernel on the Settings/About screen?

edit: try this thread: http://xdaforums.com/showthread.php?p=10472475#post10472475
[Nexus S General] micric100:
is there a way to get the most up to date CWM without rooting?