yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] MSRemmert:
All this news of a stock rom is excellent and has come an awful lot sooner than I expected it to. Most impressed.

I'd love to help out but I'm still learning about all this stuff (I've only owned an Android device 2 weeks!)

Like a few others I'm a little unsure about trying an alpha rom on my phone simply because I need the phone for work on a daily basis (and plus I have this thing exactly the way I want it) but once we hit beta I'll be more than happy to sign up my device in the name of science, experimentation and fannying around! :)
[Galaxy S I9000 Android Development] kgk888:
Have to agree. While nice it seems like it might be a futile effort if the 2.2 update is released by Samsung right as these guys finish getting stock 2.1 polished.

Although the work they put into the vanilla'ing of 2.1 on the Galaxy S may come in handy for the same process with 2.2, so who knows. But making a "consumption ready" vanilla build of 2.1 is probably not as useful with the Samsung 2.2 weeks from release (allegedly)

Such intelligent discourse
[Galaxy S I9000 Android Development] jodue:
when we get 2.1 aosp running it will of course help a lot for 2.2.
[Galaxy S I9000 Android Development] daenney:
I was wondering about something I can't seem to find a good answer to: is there some security in place preventing AOSP builds?

The thing I can't get my head around is why no-one tried this sooner? I seem to remember someone claiming something about Samsung having a way of preventing non-TouchWiz roms to run but that sounds awfully strange to me.

Is there anyone who can clarify this? Is there indeed something in place to prevent some community hocus-pocus or building for the SGS?
[Galaxy S I9000 Android Development] cantIntoCode:
I think it's all to do with this :

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

Not 100% sure though...
[Galaxy S I9000 Android Development] daenney:
Right, so it seems I just picked something up from an idiot confusing binary code with encrypted code, good to know :)

Curious to see how this evolves and what the 2.2 release is going to bring with it.
[Galaxy S I9000 Android Development] marty1976:
I know it might be a bit of an awkward question, but what does AOSP stand for?

If I get it straight, the effort is to put a vanilla Android on the Galaxy S.

That's something I have hoped for to arrive, that would literally be my dream.

How can I help? 10+y of Linux experience, embedded programming (tomato on Linksys routers), might donate hardware, storage, what do you need?
[Galaxy S I9000 Android Development] OrionTC:
android open source project. google is your friend:)
[Galaxy S I9000 Android Development] dingdonghei:
Give this guy some info! =) Would be awesome to have AOSP.
[Galaxy S I9000 Android Development] marty1976:
Googled around but did'nt find it, used wrong search terms instead of just "AOSP" and nothing else...

Anyway, OMG. Could have thought of that, thank you.
[Galaxy S I9000 Android Development] jodue:
AOSP=Android Open Source Project, here (first hit for the search term "aosp" in google for me) where you can find sources and documentation.

no samsung has no security restrictions what so ever, which is a good thing for rom development. i'd love to have a vanilla rom on my sgs but sadly there is none at the time. it looks like noob_nl is working on a cm-rom for the epic (which is already booting) which may be the best chance atm as we could easily port that to the i9000. i guess having the sources for 2.2 from samsung would help a lot, we will get them when they release their froyo-firmware.

if any other people want to start a aosp rom on their own, i'd like to help. i'm quite familiar with linux development but i can't/won't do it alone ...
[Galaxy S I9000 Android Development] moosamm:
Mine is stuck on first boot screen. Any ideas??
[Galaxy S I9000 Android Development] jodue:
it's deodex-ing @ 1st boot so give it some time (up to 5 min). also you should have a 2.1 kernel...
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Greetings fellow Galaxyenz,

I have a Galaxy S that worked all ok with JF5 stock ROM, paired with my car for phone audio, using bluetooth. Never had a disconnect...

Then I applied the procedure in order to get the HackEclair ROM 1.0.4 (flashed JM5 through ODIN, then recovery and applied update.zip). After that, i applied OneClickLagFix 2.0.

##EDIT## I'm currently on JM7 + Tayutama rom and it still exists.....

At the end my phone flies like a Concord, and it performs 2200 on Quadrant =)

My only problem right now is that Bluetooth connections to the Car audio, only last for 30 seconds.

I have to completely disable and enable Bluetooth on the phone in order to get the audio working again... for 30 more seconds... =(

Although the phone rocks with this ROM, having no bluetooth system in the car because of this ROM, is a no-go for me.

Thanks for you time. This forum has a great helping initiative.. It's precious, let's keep it :)

Cheers

Phk

EDIT -- Developed a dirty fix. Works OK for me now!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Just to make this thread complete, i've found the bug is related to some configuration desynchronization between car and mobile.

So android bt stack must be reseted.

I've developed my first app for this, so that i can reset confs with one click :)

thanks to every1 at XDA, you guys rock =)

http://www.multiupload.com/KI0WJ2RKZB or Check attached!

Cheers,

Phk
[Galaxy S I9000 Q&A, Help & Troubleshooting] ickyboo:
Good work! Finaly someone fixing stuff on own. You sir are all class
[Galaxy S I9000 Q&A, Help & Troubleshooting] miki4242:
Word!

10cc
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Thanks miki :)

The app is now on the Market, and i've realized that my car picks up the device faster if it has a new name after the fix, so i will implement a random "Android-XXXX" name for each time you click "Fix" =)

Install it from the Market to make sure you receive updates.

I'll also try to perform these steps, as they as what i really to:

- turn off bluetooth

- run this apk

- press fix

- turn on bluetooth

- change name

- reboot

Cheers!
[Galaxy S I9000 Q&A, Help & Troubleshooting] distortedloop:
Cool to see you addressing this with your own fix, but JM5 did have buggy BT with my car as well. Never a problem with JM6, JH1 or JM7. Maybe the better fix is to just get one of those firmwares, which don't have the problem you describe, and also drastically improve GPS (really, they do - for me anyways) and also are much less "laggy" even without fixes.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Hey distorted... Sorry to disappoint you, but I have JM7, and yes, the problem is still there :( That's why i've built up the tool, i have to use it every 2 days (more or less)

Anyway thanks for the thumbs up! =)

Cheers
[Galaxy S I9000 Q&A, Help & Troubleshooting] distortedloop:
Disappoint me? LOL, not at all. I don't have the problem since moving on to newer leaked firmwares than JM5. I definitely had the problem on JM5, though.

Perhaps you should rename the thread, then, if it's not specific to JM5.

Additionally, your OP says nothing about different firmwares other than no problem on JF, but the problem on JM5, maybe you should include that the issue is there on JM7 also.

And finally, if you're still running RyanZA's lagfix, and/or the HackEclair ROM, how do you know they're not the real root of your BT problems?

Coincidentally, I was also on OCLF hack and JM5 when I had BT problems. Maybe it's the OCLF that's the problem, since I am on JM7 and don't use OCLF any more, and don't have the problem, but you do(?).
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Yes, i might change the thread name :)

I'm on JM7 now with OCLF, but there's absolutely no reason for OCLF being the root of the problem.. Have you checked the full source code? I've read it line by line...
[Galaxy S I9000 Q&A, Help & Troubleshooting] distortedloop:
Full source code? Do you mean the scripts it runs? Of course I have. I manually ran them one by one to install OCLF on my phone since the batch doesn't work on Macs, and I generally want to know what exactly some script is doing to my phone in case I have to undo the steps if the script borks my phone.

Perhaps there's no reason OCLF (or Hackclair) would cause this problem, but lets look at the little bit of known data we have between the two of us:

Me: JM5 + OCLF = buggy BT

Me: JH1 + voodoo = working BT

Me: JM7 + voodoo = working BT

You: JF3 + nothing = working BT

You: JM5 + Hackclair + OCLF = buggy BT

You: JM7 + OCLF (+ Hackclair??) = buggy BT

The only common elements to EVERY scenario that has buggy BT that we have specifics to so far include OCLF.

It seems perfectly reasonable to assume that OCLF (and/or Hackclair if you're running it in your current buggy BT configuration) are part of the problem (edit: unless of course you just have buggy hardware).

With that in mind, a reasonable troubleshooting step would be to uninstall both OCLF and Hacklair and see if you have issues on stock JM7. If you don't, then we know that one of those modifications are the problem.

Since you've found for you what is an acceptable workaround, it's probably more effort than you're interested in doing to test that out, and I'm not interested in breaking what is a perfectly working combination of firmware/lagfix on my phone to install OCLF to test it out, so we'll probably have to rely on others reporting their configurations that work or don't work.

The only technical reason I might suspect OCLF as the issue is that in my experience, and the reports of others I've read, OCLF starts to lag again after a day or two of uptime on the phone. What if the BT disconnects are related to the system lagging? It's a stretch, I know, but I can't ignore the fact that between the two of us, the only thing we had in common while experiencing BT issues is OCLF. That's significant, in my humble opinion.

All that said, if I start experiencing BT problems out of the blue on any future configuration, I'll certainly look to your app for help! ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Thanks man :) Useful post! I've spoken to RyanZa before implementing this app, to confirm that there were no possible misunderstandings.

About the code: I was refering to OCLF source code (GPLv3) of the Market App

About the lag returning: I reboot my mobile frequently so the 2 day lag-reappear is not the question

Anyway, you are right, there is a common name: OCLF.

I might test this BT with Voodoo. What are the downsides of voodoo vs oclf? oclf is very neat and clean you know... ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] distortedloop:
I don't imagine the apk for OCLF does anything different than the scripts do, essentially make the large data file and then loop mount it. So the end result is surely the same.

I don't really want to pollute this thread with the merits of OCLF vs voodoo, some people get a bit to "religious" or defensive about it and the thread will devolve to being really off-topic if that happens. There are plenty of threads hashing that debate out.

Personally, I think voodoo to be nice and clean as well. Voodoo requires a custom kernel and you install it via Odin. It backs up your data, formats /data as ext4, then restores the data it backed up to it. Simple, clean, reliable, but not as simple as just running an app from the Market. (For the record, Ryan, I'm not saying here that your method isn't reliable. :) )

The primary disadvantage for you to test it out at this point is that the beta1 is no longer available publicly, and the beta2 won't be released until "sometime this week", so really not easy for you to test out.
[Galaxy S I9000 Q&A, Help & Troubleshooting] PlanetJumble:
I am experiencing problems with a Bluetooth car kit as well, but different. Every now and then, the connection hangs. The stereo isn't receiving anything, but displays connection status for phone and media. The Galaxy S displays connection as well, the music player looks like it is working, but no sound can be heard.

When I turn off Bluetooth on my car kit, the Galaxy S still displays connected status. Turning off via status bar shortcut or settings menu makes it stay in "turning off" mode indefinitely. Sometimes I can't even bring down the status bar. And even shutting down the device doesn't work, as it is not completely powered down, I have to force it (10 seconds reset button) anyway. Then boot up and hope it doesn't happen again right away.

I had that problem with JM6 + OCLF and still on JM7 + OCLF, but as far as I can remember, it didn't happen on JF3, where I had OCLF running for quite a while as well. And I use my car kit every working day. I never ran JM6/JM7 without OCLF though, so this may not be related at all.

Getting off topic now, but I noticed something else with OCLF: when it is applied, and I connect the USB cable, it locks the internal and external SD cards even when in menu mode without choosing "mass storage". In that state, I can't access them neither from the PC nor from the phone. I need to select "mass storage" then disable it again (already put it as default because of that), which is also pretty annoying because my car charger does fake a PC connection (probably because some devices won't charge otherwise).

Before OCLF, I could just ignore the popup menu for USB mode. I am just saying that, because it is another side effect of OCLF which can hardly be explained by looking at the source.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Wow, that's a totally uncommon behaviour from SGS!

How do you flash it? Do you use CSC+MODEM+PDA? Re-Partition?

Cheers, good luck!
[Galaxy S I9000 Q&A, Help & Troubleshooting] PlanetJumble:
Yes, on both updates, all in one step.

But the strange USB behaviour was already present with factory firmware JF3 (after OCLF).

BTW: the Bluetooth problem doesn't happen very often, between once and three times a week I'd say.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Phk:
Yes, same as me. I have to use the fixer to restore connectivity... :\

About the USB, change your SGS using warranty....
[Galaxy S I9000 Q&A, Help & Troubleshooting] PlanetJumble:
I don't think so. :)

BTW: I moved from OCLF over to Voodoo (and to JM8). And it did solve nearly all problems. Bluetooth never crashed since (also didn't in a few days of Voodoo on JM7). Also now USB connection doesn't automatically lock the SD cards anymore.

And I noticed something else: OCLF prevents fonts from being rendered bold on certain web pages like Google Reader. Missed that before but I thought maybe Google removed the bold fonts to save space. I like it better with bold fonts though, glad to have them back.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Prof Yaffle:
Ongoing BT and OCLF Issues...?

Not sure if this is relevant, but I'll post anyway just in case it is and it gives someone else a eureka moment.

I'm on a stock Eclair ROM - JM2, I know, I've re-flashed it several times now...! - and have had no end of troubles with some combination of root, OCLF and/or the other XDA kernel mods that come with OCLF. I've ruled out the last of these by not changing scheduling or anything else from defaults; I doubt it's the first of them because I've tried a couple of different root methods. So it's probably OCLF itself, I just don't have the appetite yet to re-install everything only to screw it up again "to see if" ...

Anyway, rSAP carkit - pair, connect, everything is fine. Install OCLF, and within a day or two (and *perhaps* related to having to remove/reinitiate the ext2 partition because of the Kies sync issues), I get:

1. Carkit unable to see the 'phone at all (rare, may be unrelated)

2. Carkit sees, connects, but tells me there's no signal (dashboard shows blank signal bars, RNS510/Columbus head unit tells me there's no network) - but I can still make calls

3. Carkit sees, connects, but tells me there's no signal as above but genuinely means it: any attempt at calling gives a network error (most common)

4. Carkit and 'phone won't disconnect properly, so the 'phone is locked out of the network until you reboot it (rSAP borrows the SIM identity of the 'phone for the car, so if it doesn't give it back then the 'phone can't reconnect to the network - the handset thinks it has no SIM card). (every time)

I'm just rebuilding the handset (again) without any mods to see if the problem goes away, but I can't imagine it's related to any other application that I have installed.

Pity me and my poor, laggy handset.... if I find out more, I'll report back. I might have a look at the BT fix posted here (thanks in advance!) to see if that helps if the problem does reoccur... or try Voodoo, so long as I can do it without my wife spotting that I'm in the process of breaking that very expensive 'phone again :-)
[General Questions and Answers] AOmega41:
Hi to all,

I have an Acer betouch e200. it has a physical keyboard, and we are supposed to be able to write text messages and email with it.

The problem is that it only writes numbers. I can not type letters.

on the web, i've read that it's supposed to work with the XT9.

And here again, I don't have it in my options.

Is it possible to install the XT9 separately ? do I have to change something in the registry to make it work ?

Acer hotline is so bad, they told me to reinstall the device, i've done it twice and i still don't have the keyboard.

I use the original ROM without Orange customizations. It's clean.

it's Windows Mobile 6.5 French.
[HD2 General] WoodbineG:
Howdy!

I happen to be the proud owner of an USDM HD2 and also a proud member of such a great community wow GO XDA! :D anyways its been about a week since I got the device as I upgraded from my trusty Dash 3G aka Snap. Well I have done about 15 full battery charge/discharge cycles and I still dont seem to be achieving maximum battery performance. I leave home everyday and ride the train to work for about 25 minutes in that time all I do is listen to music while the phone has data connection turned off and by the time i get to work my battery percentage has dropped by about 15% what the hell! So fa r i have not been able to go about my very simple day withouth the phone dying on me... so its my battery bad or do i still have more cycles to run tru?

Another quick issue is that my phone absolutly pauses when i get a text message: nothing scrolls, music pauses, keyboard freezes and all for about a second!

Ideas? Thoughts? Please let me know and happy Tuesday to all.
[HD2 General] samsamuel:
there are loads of threads about battery, and i'm not gonna start talking about the myriad potential culprits, but i just wanted to say regarding the charge discharge cycling to get max battery performance......... that was for nickel metal halide batteries,, these lithium ion batteries don't require it. that being said, the circuits that monitor battery level do need a cycle or two for accuracy.
[HD2 General] narathip:
When I first got the phone, it practically never functioned properly. Like you said, glitches/lags everywhere, especially from texting, the music player, the keyboard, etc. Couldn't really find a "fix" and was frustrated for a while...

Then I flashed the Energy ROM and... voila! Everything was silky smooth like how it should've been in the first place.

Not sure if flashing the ROM is a feasible solution for you, but it was able to solve (almost) all of the problems I had.
[HD2 General] sirphunkee:
I might suggest doing a hard-reset on just the stock ROM, that's been known to clear up a wide range of odd behavior
[HD2 General] mr1ncred1ble:
+1

Energy ftw
[Captivate General] Belaflek:
Mods feel free to nix this if you think its uncouth for me to do this but could I coerce anyone to check my thread on the general forum about my bricked phone that won't even really power on?

I figure I'd just throw it out where the smarter folks reside.

Also...thanks as I'm enjoying blowing up my phone many times a day...seems like this time was permanent.

http://xdaforums.com/showthread.php?t=757293
[Galaxy S I9000 General] airman010:
My friend has a custom Captivate firmware not from AT&T. I was wondering, if there is something similar for the Vibrant? I notice that the T-Mobile really tried to make the Vibrant be an iPhone with their UI. Is there a way to get an original (custom) i9000 firmware with all working buttons and the 3g working? I see there are not as many choices for T-Mobile because of the lack of 3G bands. All the T-Mobile customization with this android phone seems to annoy me, from the T-Mobile boot splash screen to all the bloatware they put on this phone. I also read that I have to ask for the firmware here in the forums since it is T-Mobile USA.
[Galaxy S I9000 General] boomerbubba:
For hacked Vibrant firmware on the XDA site, you need to look in the Vibrant Android Development forum.
[Galaxy S I9000 General] airman010:
I guess the correct term I was looking for is debranding the phone. I'll check out the link. Thanks
[Captivate General] wgarrido:
I was going to exchange my phone for a new one before my 30 days is up which is tomorrow, so I did a factory reset. They ended up not letting me because they knew about the GPS problem and said there is a fix coming. I also had my email disappear and wanted to just get a fresh device before I am stuck for 2 years.

So I wanted to see if anyone else who has done a factory reset has noticed the same or differences from before they reset it.

1. Data icon (3G,E) still shows while WiFi is connected. Before the data icon wouldn't show.

2. Facebook pictures sync works much better and actually sync's pictures. Also its doesn't take 20 clicks to select the contacts to DL.

3. Phone overall doesn't seem laggy as much and much more responsive.

4. When I open messages the first time it keeps asking if I want to set a limit, which I have to say no every time. Very annoying, not sure why it keeps asking,

Note: I haven't rooted this time (I was before) yet and I have less apps installed. I haven't installed the official FB app in case it was conflicting, but I doubt it.

I will add more if I notice anything else. Today is the 3rd day since the reset.
[Captivate General] RootPhisher:
Curious to see what replies you receive. And you're saying AT&T wouldn't return it even though there is a "known-issue" with the phone?
[Captivate General] iceman4357:
Yea, thats BS. if the return policy is 30 days you should be able to return it. And who gives a **** if there is a fix on the way. It doesnt work right now, and you signed a 2-year agreement for a phone to have a working GPS unit which doesnt; breech of contract.
[Captivate General] wgarrido:
They wouldn't let me exchange it, I probably could of returned it, but not sure if I can deal with going back to the Fuze with WinMo. At least I turned the Fuze into a portable Garmin GPS with internet calling via WiFi.
[Captivate General] RexEscape:
(psst. just tell them it shuts down randomly for no apparent reason.)

I exchanged mine for this (real) reason. It was ridiculous. My Captivate continued to shut down at least 2-3 times a day. I even contacted Samsung about this issue and they said to just exchange it.

I did a Factory reset and hoped that it would fix the problem. Three hours after doing so, it shut down on me again. I have had it. I just exchanged it.

Sorry I can't really help you with the different between stock and a factory reset device since I didn't really take notice of it. Although, after the reset, I went to Settings - About Phone - System Tutorial and clicked Begin. Nothing happened. Yesterday, with my new device after the exchange, the Begin button took me to the Tutorial.
[Captivate General] BigJayDogg3:
I had 3G connectivitiy problems before, and after doing the odin restore those problems are gone. It may have been poor network conditions for a couple days, but either way, my problem no longer exists.
[Desire General] slugger09:
Do you have issues? This is my second desire and it has the same issue as the first, reception is dire, unless your stood under the transmitter all I seem to get is static, its a major pain as I still have to take my Sony Ericsson to work to listen to the radio.