yashsingh1/xdaforums huggingface dataset:
[Desire Themes and Apps] zHk3R:
There's Where to Buy button.
[Desire Themes and Apps] jmonfu:
oh, so its not a downloadable file

Ok I thought you purchased online
[Galaxy S I9000 Q&A, Help & Troubleshooting] davanw:
Back when I was a Blackberry fanboy *ducks* here is basically how OS updates would happen:

1. RIM would release the OS update 'candidate' to all the major service providers who carry the specific phone - Bell, Telus, Verizon, whoever.

2. The provider would then test the OS.

3a. If it passes their testing, they would make their changes, patches, install their bloatware, etc. And then release it to the public.

3b. If it fails, back to RIM.

So essentially, it's the providers that everyone waited on for updates, not the hardware manufacturer.

Is the world of Android any different? Are we blaming Samsung for not releasing Froyo, but really we should be questioning our service providers?
[Galaxy S I9000 Q&A, Help & Troubleshooting] davanw:
anyone????
[Galaxy S I9000 Q&A, Help & Troubleshooting] Darkimmortal:
Right now it's up to Samsung.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
it is released via Kies
[Galaxy S I9000 Q&A, Help & Troubleshooting] mstrandbo:
And for this forum, this phone, it's up to Samsung more or less. No carriers. The NA-variants on the other hand, it's up to the carriers after Samsung releases it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] davanw:
Ok so I'm confused then, if Samsung directly releases the OS to the consumers, how does Bell or Verizon or whoever get their bloatware built-in?

*edit* sorry I didn't see the last part about North American carriers. So Samsung has to release the OS to the carrier, and then the carrier does their thing with it. Correct? So even if Samsung releases the OS, Bell isn't necessarily going to get the update to me in a timely fashion... ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
no need to complicate things

if you want the official release, just keep checking Kies on a daily basis

if you hit firmware on Kies and it tells you new update is available, get it

if not, then just go on with your daily business

it will show up when either bell / samsung are done with what they need to do with it before it gets released

but if you really want release X from build X you can simply change the registry to hack it to let you download the release for model X

but of course.. if your phone dies, then it's not Bell's problem

luckly enough so far Samsung has been pretty amazing in accepting all the failed flashes by end users without charging us a cent

don't want to jinx it, but if they get too much trouble they might start doing that.
[Galaxy S I9000 Q&A, Help & Troubleshooting] foxbat121:
Here is how it works:

1. Google releases new OS versions

2. Hardware manufacturers get the OS source code and add their own drivers as well as customizations to build a ROM image.

3. Manufacturer tests and then releases directly to customers if it is not carrier branded.

4. If it is a carrier branded phone, Manufacturers will need to bake in carrier specific customization and bloatware. And send to carriers for testing and validation.

5. If it passes carrier testing, the firmware will be released to customers via either OTA or Kies.

It will be a significant delayes between a new Android OS releases by Google and a new firmware contains the new OS to end users. More so than your old Black Berry OS updates.

Froyo was released in early summer 2010 and eariliest Froyo ROM updates for Android phone occured in August. And most happened in late August and sept. Our Galaxy S is further delayed until mid to late Oct because Samsung just can't get their act together to release a quality build.

It's quite a nightmare. No better than the old Windows Mobile updates.
[Sony Ericsson XPERIA X10 Mini] gabbio:
I noticed in my init log this line (with a simple "dmesg" from the shell):

init: cannot find '/system/bin/playmp3', disabling 'bootsound

anyone fixed this?

I imagine this is needed to hear some music during the boot, maybe while viewing the boot animation.

It would be nice to activate this feature on our phone, we could use for example the Desire bootsound (available in this thread "[Req] Original bootsound" in the Desire Themes and Apps).
[Sony Ericsson XPERIA X10 Mini] TF85:
Hello,

Have you find the playmp3 ?

I need it for boot sound.

I seach it in several custom ROMs, and Google without results.

Thanks
[Sony Ericsson XPERIA X10 Mini] x10man:
I'm sure there are tutorials from ages ago about it. I remember in owain94's CM7 on one version it played DROID really loudly. Scared the living daylights out of you on a random reboot!

X10man
[Droid Incredible Themes and Apps] ogkhaze:
Can anyone get the Splash Screen and Boot Animation from the EVO?

Thanks!
[Droid Incredible Themes and Apps] cassidyjames:
I can look at grabbing it off my EVO for you. Do you just want it raw or reformatted for the Incredible or something?
[Wildfire General] spanta:
My phone doesn't make calls and I need to go to the Vodafone Store this afternoon. I'm root so I tried to install a Vodafone Spain RUU but I can't because my bootloader is highter.

Have you got a RUU for my Wildfire or an unrooted nandroid backup? It's the new model, made in May '10 I think.

Thank you all, I don't wanna change my phone because of calls...
[Wildfire General] GKMUTHA:
shipped-roms.com/shipped/Buzz/

find your rom and flash,..
[Wildfire General] bluedragon1982:
here its is:

http://shipped-roms.com/shipped/Buz...45.55.24_3.35.15.31_release_130867_signed.exe
[Wildfire General] spanta:
I've downloaded this one but it doesn't work. It says there is an error with the bootloader.
[Wildfire General] bluedragon1982:
Try it with an GoldCard - you can find my guide all needed files here:

http://bluenazgul.blogs.blapkmarket.com
[Wildfire General] rolks:
u need downgrade you hboot to same or lower version
[Wildfire General] bluedragon1982:
I think using the goldcard method should also work, please feel free to correct me if iam wrong.

Btw:

Is there also an *.nbh (or are other file(s) needed?) file for the wildfire like G1/MT3g has, to complete factory default your device using the goldcard way?
[Wildfire General] rolks:
yes for wildfire is 4 files needed, pc49diag.zip, pc49diag.nbh, pc49img.zip, pc49img.nbh, i have searched from net this files, but no luck so far. if anyone find them then feel free to share with other wildfire users
[Wildfire General] adrienlm:
I might I've found pc49img.zip rapidshare.com/files/419254202/PC49IMG.zip ; i'm downloading it and testing right the way !!!

from this forum : 4pda.ru/forum/index.php?showtopic=181736&st=220

Edit : it's shows :

:s

But the PC49IMG passed the check :)
[XPERIA X10 Themes and Apps] azian_advanced:
I just recently installed ADW and I really love it. But my original lockscreen doesn't work anymore and causes the phone to send e-mails, etc. by itself and drain the battery. I would like to get the old lockscreen back if possible, otherwise, what would be a good lockscreen that works with ADW?

I would like one that doesn't activate the screen unless i press the power button at the top.
[XPERIA X10 Themes and Apps] azian_advanced:
i just realized that No Lock somehow is incompatible with ADW so i uninstalled it and my original lockscreen is back.
[XPERIA X10 Themes and Apps] SXUsr:
So it wasn't due to ADW then, the issue is with Nolock.
[XPERIA X10 Themes and Apps] DaveHTC200:
I've got no problems with "no lock" and I'm using adw
[XPERIA X10 Themes and Apps] qwer23:
same with me, no issues at all.
[Galaxy S I9000 Android Development] sztupy:
For those who cannot choose between the two, here are some of the differences: (these are only based on diffing the files inside the two ROM, no actual flashing was done. If someone has some better comparisons, feel free to post them)

kernel:

The size of both decompressed kernel are the same, the initramfs part is actually identical (except the order of the files). Inside the decompressed kernel there are a lot of 1-byte length parts that are different, but only 3 major chunks that are quite different.

The first of these chunks is the cpio's initramfs part, which is actually identical at the file level, but the files are in a separate order inside the cpio archive, that!s why the difference.

The other two chunks (around 0x75F90A and 0xA68F5D) are probably some part of the kernel don't know which part, and what they actually do.

Conclusion: although there are differences, the two kernels seem to be mainly the same, their decompressed sizes are actually equal, and the initramfs part is the same too.

CSC

The JPM variant has the usual multi-CSC's: CPW,DBT,KOR,XEO,XEU, and nothing else

The JP6 variant has only one CSC: XEE (nordic), but features Swype with 14 languages.

Conclusion: the CSC part with the added languages for swype is better in the JP6 variant.

FactoryFS

I only did a diff if the file sizes are different. The following files are changed:

- build.prop

- almost all files inside /system/app (minimal changes in filesize (few bytes), probably only because of signature changes except for Maps, Emaill, Gmail, DialerTabActivity, and the followings)

- AxT9IME is much larger in JPM (probably more languages(?))

- Swype is much larger in JP6 (and JP6 has a separate swype inside the CSC too)

- flash_player is larger in JP6

- VoiceSearch is much larger in JP6

- NOTICE.html.gz

- almost all files inside /framework, but only a few bytes changed, except for framework-res.apk. framework-res.apk is much larger in JP6

- libSwypecore.so and libXt9Core.so. libXt9core.so is much-much larger in JPM!

- libspeech.so is only in JPM. libvoicesearch,so is only in JP6

Conclusion: JPM seems to have a better xT9 support, but JP6 seems to have newer applications (if newer means larger...)

EDIT: in the JP6's framework-res.apk the translations are changed, and are much-much more complete! (for example in hungarian language in JPM the name of dates are not translated, but in JP6 they are)
[Galaxy S I9000 Android Development] supercurio:
Thank you for this analysis sztupy
[Galaxy S I9000 Android Development] ginkage:
Larger may as well mean additional (e.g. debug) info...
[Galaxy S I9000 Android Development] Mycorrhiza:
Thanks alot for this!

Seems like JP6 will be the way to go. Just hope the kernels get adapted to OC and Voodoo quick.
[Galaxy S I9000 Android Development] kalpik:
+1

10char
[Galaxy S I9000 Android Development] yaocheng:
thanks for the info
[Galaxy S I9000 Android Development] qsec:
Nice explanation!

Do you know if the kernel activates the 3 button combo?

/qsec
[Galaxy S I9000 Android Development] sztupy:
True. I think I'll check what the differences in framework-res are. Everything else seems to be the same.
[Galaxy S I9000 Android Development] sztupy:
that depends on the boot and spl. Neither JP6 nor JPM changes the boot or spl.
[Galaxy S I9000 Android Development] dutchcow:
Very interesting. Thanks for the info. Let us know when you know if the bigger files contain debug symbols or if it's just newer (version wise).
[Galaxy S I9000 Android Development] Madic:
Sorry, but size does say nothing about the version nor the functionality.

You need to compare Hex- or bitwise.

And even so in most cases you can't tell what function has changed.

It could be new functionality, an unused function, a completely new function or just debug code.

But nevertheless, thank you for your effort.
[Galaxy S I9000 Android Development] sztupy:
For the applications that!s true, but most of the changed applications are actually from google and adobe, which I don't think contain debug information. And the libxt9.so is actually larger because it contains more languages (dictionary is compiled in in these files). For the other files the small differences are mostly because the date changed or the framework-res.apk changed and the files are odexed.
[Galaxy S I9000 Android Development] dutchcow:
Since the JPM source is out, I will stick with that for now. So when voodoo has been ported I can easily add it.
[Galaxy S I9000 Android Development] sztupy:
New info: The framework-res.apk in JP6 is more complete translation wise!
[Galaxy S I9000 Android Development] phpcool:
Nice thanks for the info!
[Galaxy S I9000 Android Development] Bandis710:
The csc codes are confusing .. The dutch one does not exist anymore (xen) so i do not know which one to choose ..I flashed jp6 and my csc is now xee , but my apn settings where filled in automaticaly.. Does that mean xee is the correct csc for me ?
[Galaxy S I9000 Android Development] BronzedDroid:
If it works there is no reason to change, but XEE is really Nordic Countries/Scandinavia.
[Galaxy S I9000 Android Development] Bandis710:
Ok. Maybe richthofen knows which csc to choose ? The netherlands (DUTCH)	isn't listed with any.csc
[Galaxy S I9000 Android Development] zilvesta123:
Why don't you flash the csc back to a Dutch one?
[Galaxy S I9000 Android Development] Bandis710:
There is no dutch csc ! For the 2.1 releases someone made a dutch csc but i doubt thst can be used on froyo
[Galaxy S I9000 Android Development] tommy34:
it doesnt matter, dutch is supported for the system and swype in both releases. The only thing you miss are 2 apps and the apn config file.
[Galaxy S I9000 Android Development] cantIntoCode:
Looks like I'll be flashing JPM when my phone comes back! Thanks for the broken down analysis :)
[Galaxy S I9000 Android Development] sturmeh:
Remember we have the sources for JPM so if anything we know it inside out.

I'm going to go with JPM for Voodoo compatibility sake. :)
[Galaxy S I9000 Android Development] Prankey:
Me too. I appreciate the analysis, however I don't believe larger files mean ANYTHING! It could just be unoptimized OLDER code or probably more language info which could unnecessarily hog memory and processor if you use just one language (English). Hence I would rather flash a firmware optimized for English rather than the one which has all sort of languages which I dont need. Unless there is a good reason to flash JP6, I would rather stick to JPM.
[Galaxy S I9000 Android Development] worms:
What are the Buildtime of this two version?
[Galaxy S I9000 Android Development] x3gypxtianx:
They're a day apart, JM6 being the newer one. You can see the info that's been pulled from the build.prop

http://xdaforums.com/showthread.php?t=807351
[Galaxy S I9000 Android Development] sztupy:
From the other side, more language info is highly useful if you're not from the US/UK...
[Galaxy S I9000 Android Development] bloodrider:
You can use this method, http://xdaforums.com/showthread.php?t=787163

it works on Froyo.
[Galaxy S I9000 Android Development] _JKay_:
Swype in JP6 is Version 2.6.47.11856 (its actually located in CSC_I9000XEEJP4)

Swype in JPM is Version 2.1.41.10155

Regards,

JKay
[Galaxy S I9000 Android Development] Kockowan:
If flashing JM8 >> JPM/Pit-803 to a german not branded Galaxy, lockscreen language is in English.

If flashing JM8 >> JP6/Pit-803 to a german not branded Galaxy, lockscreen language is in German.

Any explanation about this behaviour :confused:?
[Galaxy S I9000 Android Development] MCOGW:
I just would like to go a little deeper into this. I think you just have to compare a few more values from build.props to be sure.

Just to look at the build.date doesn't really tells us very much.

Here are a few values that are suitable for a comparison.

And imo one of the most important there is "ro.build.changelist".

I9000XXJPK

ro.build.date=2010. 09. 21. (x) 14:13:05 KST

ro.build.date.utc=1285045985

ro.build.host=sep-51

ro.build.changelist:584433

I9000XXJPM

ro.build.date=2010. 10. 06. (x) 14:10:05 KST

ro.build.date.utc=1286341805

ro.build.host=sep-42

ro.build.changelist: 615847

I9000XWJP6

ro.build.date=2010. 10. 07. (x) 12:55:58 KST

ro.build.date.utc=1286423758

ro.build.host=SE-S608

ro.build.changelist:618121

and btw:

Galaxy Tab

P1000XXJI5

ro.build.date:2010. 09. 12. (x) 05:47:00 KST

ro.build.date.utc:1284238020

ro.build.host:sep-56

ro.build.changelist:562468

I also noticed that the format of "ro.build.host" seems to be "sep-xx" on every samsung mobiledevice which has an official firmware.

Not sure what exactly the number after "sep" means but I'm very excited about what these two values (ro.build.host and ro.build.changelist) will look like in the "real final official froyo release". I'd bet ro.build.host will be < 42 ;)
[Galaxy S I9000 Android Development] MCOGW:
Same here,but I flashed from JPK

At JPM I don't have to choose my language.

At JP6 I have to choose it manually after first boot. Maybe that's the reason?
[Galaxy S I9000 Android Development] jurguh87:
Hi guys,

Can somone tell wich is better in noob langauge jpm or jp6 for use in the nl

Thanks
[Galaxy S I9000 Android Development] sztupy:
JPM is the classic KOR version. If your sales code is not in the list, you'll autmotacially get KOR. The same happened with JPC too. JP6 is not multi-csc.
[Galaxy S I9000 Android Development] dutchcow:
I'm using JPM because it has my product number and it has the sources online. Seems the best choice for me.
[Galaxy S I9000 Android Development] stassano:
does that reflect on the android market in any way or do both unlock the full market?
[Galaxy S I9000 Android Development] nandihno:
Jpm has all my apps in the market and didn't need to run market fix

Just make sure to clear cache and data from download manager and market and then reboot the phone this has worked for me since jpc
[Galaxy S I9000 Android Development] stassano:
Thanks, will it be the same for JP6 you recon? I am more interested because JP6 runs Swype 2.6 whereas JPM runs Swype 2.1... and being the big Swype fan I am I think I will like JP6 more ;-)
[Galaxy S I9000 Android Development] drasifriaz:
Hi guys which version will work in england Jpm of jp6, thanx
[Galaxy S I9000 Android Development] flypubec:
Can someone please check if slovenian is in JPM or JP6 ?
[Galaxy S I9000 Android Development] johoe:
Yep, is there in JP6

johoe
[Galaxy S I9000 Android Development] BOTICSELLI:
Hungarian Samsung keyboard

Good morning Gentlemans!

Can someone please check if hungarian T9 is in JPM or JP6 ? (Samsung keyboard)
[Galaxy S I9000 Android Development] stassano:
Both work in the UK... however JP6 is a Scandenavian version from JPM as I read (and Swype is a bit newer)... JPM has more CSC's so more standard EU... I'd go JPM if I was from the UK.
[Galaxy S I9000 Android Development] jurguh87:
I"am now on JPK and my code is also KOR and no problems at all so i'll check JPM first because of the online source code and then JP6

thanks stupzy for your answers
[Galaxy S I9000 Android Development] vali_ics:
can anyone extract the new swype from jp6? thanks.
[Galaxy S I9000 Android Development] miro666:
Ok,was somebody ask,and i ask too: Wich have Croatian, Slovenian and Serbian language JPM or JP6 ? Im really cofused about wich is for my device, im on Stock Eclair PDAI9000XXJF3, CSC I9000XAJF3, PHONE I9000XXJF3. Product code is I9000HKDDBT. Whar is better for me ended, JPM or JP6 ?

Thanks forwarding on members opinion.

Regards.
[Galaxy S I9000 Android Development] Cartier23:
JP6 is what you should use :)
[Galaxy S I9000 Android Development] miro666:
Thanks Carier23,i think i will JP6 flasing because mobilx from Serbian think too, it is better than JPM for our region.

Best regards Ljubljana :)

and Thank You.
[Galaxy S I9000 Android Development] ad_insane:
It is better, at least if I compare it to JPM XEU version. On JP6 Serbian and Croatian language are available for Samsung keyboard and for Swype as well. It is possible to have menu on SER or CRO language too. I´ll stick to JP6 at the moment.
[Galaxy S I9000 Android Development] francoml:
I use JP2.. JP6 is the best choice? Do I really need to update? Thanks
[Galaxy S I9000 Android Development] roymustafa:
DEAR SUPERCURIO which firmware do you use at the moment and with what did you root?
[Galaxy S I9000 Android Development] stassano:
Supercurio uses many (if not all) firmwares and roots all of them... that's what developers do :-)

You don't need to update, you can keep on using whatever feels right for you... if you have a urge to get the latest stuff on your phone and help the community by talking about it or helping it improve (what else would you go and sign up on XDA for) then sure ~ go ahead and flash :-)

I bought my phone in HK with I9000ZSJP2, signed up on XDA because I wanted a better froyo... so I flashed to I9000ZSJP3, had issues getting it rooted and then flashed MoCaDo's I9000XXJP3 (mistakingly thought it was ZSJP3 but hell... no difference for me)... then flashed Doc's JP6, then Doc's JPM/JP6 and then finally Doc's JPA with brut maps...

Now I have the latest and greatest froyo (not official) rooted and with brut maps installed so I have Google Nav worldwide.

You can do it :p
[Off-topic] research2guidance:
A hello across the xda forum,

We're holding a survey on how mobile-app developers market (and monetize) their mobile applications. Its a global survey and focused mainly for app developers. The survey's main purpose is to answer questions like how the mobile apps market is evolving and what will it become in the coming years. This information will help developers better develop, market and therefore monetize their apps.

Would anyone be interested in this kind of research ? :-)
[Galaxy S I9000 General] coradux:
Hi,

It seems that a lot of people with SGS without working 3 buttons combo bricked their phones trying to flash another firmware or trying to fix recovery and download mode. I was one of them. It seems that the only solutions are sending back the phone for warranty purpose, un-bricking with RiFF Jtag or other way. Since all solutions implies time-waste or a lot of money we need a simple solution to un-brick the phones without disassembling the phone. I think this is one, as in attachment. I've searched info about Anyway Jig on web and it seems it's a toolbox for Samsung Services (someone posted here that Samsung Service claimed that changed his phone's motherboard to be able to fix the bricked phone). Also I've found on web that are several boxes that can act as Anyway Jig. So it will be possible for unofficial or small service centers (a lot of people are from areas without samsung support or good service centers) to enter download mode and re-flash a new firmware. I am from Romania and all service centers from my small town claimed that if my phone can't enter download mode can't be fixed. I've send it to Bucharest (I didn't want to send it back to Orange because I have to wait 2 or 3 weeks) to a service center who said that will repaire my phone in 1 day and it will cost me 23 euros. They sent my phone back after a week and after they forced me to pay 55 euros claiming that it was very hard to repair the phone. Couldn't argue them because I want my phone back, and finally it costs me 60 euros and 10 days (repairing and transport taxes). Maybe if I knew about this method I could have my phone repaired in 1 day and with very few money (I have some friends with a small service center but they don't have a RiFF Jtag and didn't knew another method to repair the phone).

I posted here because a lot of people with bricked phones are looking for a solution here, it can be moved in other area if someone thinks so.

And also it would be a good thing if someone can confirm if this method is real.
[Galaxy S I9000 General] nesquix:
WOoow. If someone can make a app with this info to unbrick phone, i'm ready to paid.
[Galaxy S I9000 General] coradux:
I don't think an application can be made because a bricked SGS can't be seen by PC. That's why you need a special box who can connect the phone in this state.
[Galaxy S I9000 General] AllGamer:
According to the PDF, it is via a JIG conexion

which mean you'll need to buy the machine to do it for those without the 3 button modes enabled
[Galaxy S I9000 General] coradux:
Don't need to buy, just find a service center who has one.
[Galaxy S I9000 General] hostdahora:
Unbrick Samsung Galaxy

Hi my friends.

I'm having the same problem and the solution is a technical assistance with the box "Samsung Any Way Jig Box.

This box can indeed put the phone in "download mode" again.

This will cost me 40 USD.

That's my tip to everyone.

Cyah!

Alex