yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] Crypto_ahash:
What!? Sound/Mic/WiFi fixed!?? Very nice work there Riemer :)
[Hero, G2 Touch Android Development] NervGaz:
If memory serves me Desire uses BMA150 as well, might be worth checking the bravo board files for hints on that one.
[Hero, G2 Touch Android Development] petsasj:
Nexus One does, too.
[Hero, G2 Touch Android Development] Wupper:
I don't know if you have enough bandwith, otherwise I will mirror it at my server :).
[Hero, G2 Touch Android Development] rionline:
i am really really impressed!!!!
[Hero, G2 Touch Android Development] vido.ardes:
Thanks for putting all your time and effort into this man, nice to see someone finally get stuck into the problem (I took a look myself but it went straight over the head of this humble .NET dev :D)

I would open your own thread and start fresh now you have a working kernel to push out, 'cause you know the most important thing is comming up with a snappy name for it :p
[Hero, G2 Touch Android Development] thantos2024:
I just thought I would let you know that this kernel doesn't seem to work on any of the 2.2 sense rom's atm.

Wouldn't by any means expect you to even consider looking at this atm with so much left to look at but thought I'd mention it to save other people headaches if they try to flash it.

Excellent to see people attempting to move this port forward, something I don't have the technical ability to do myself, hopefully if your to complete it to a fully working kernel it will work towards our heros being kept alive that while longer.
[Hero, G2 Touch Android Development] Crypto_ahash:
Did you even rip out the zImage out of the boot.img and put it in a froyo boot.img?
[Hero, G2 Touch Android Development] erasmux:
Did you even check how the kernel was packaged?

It has no boot.img and will use the ramdisk of the currently installed ROM....
[Hero, G2 Touch Android Development] Crypto_ahash:
lol ouch. I should check first before posting :)
[Hero, G2 Touch Android Development] thantos2024:
Erm, even that is above my head, as I said I don't have the ability to even try messing with kernels, rom's etc. Which is why I leave it to people more experienced than myself and tend to keep quiet. (No point me trying to comment on things I know nothing about. :-) )

Although now I have linux installed on my VM, I am considering delving into the world of Rom development, so who knows, maybe one day I'll release my own kernel.
[Hero, G2 Touch Android Development] erasmux:
Working on my .35 port, I suddenly noticed that the .34/5 use the new yaffs driver. I have considered porting this to flykernel a while back. The reason I did not is:

If you want to use the new .34/5 kernels your ROM must have been flashed with RA recovery 1.7.0.1. If not, you will need to install RA recovery 1.7.0.1, do a full wipe and then either restore a backup (I hope it works, don't think I tested this) or reinstall the ROM. I do not know if there is a clockworks version which uses the new yaffs.

P.S. thantos2024, could this be the reason it didn't work for you?
[Hero, G2 Touch Android Development] thantos2024:
Yes Erasmux, it could be, my 1.7.0.1 got down graded recently when I flashed VR12, and have been to lazy to upgrade again. Will upgrade to 1.7.0.1 later today and try it again. Will post results after.

Although you had said would have to reflash rom, on old ra, I found that it Hung for a while on first boot screen then just rebooted into recovery where I just flashed your latest kernel and all was fine, would this not work on ra 1.7.0.1 (assuming it was successful).
[Hero, G2 Touch Android Development] riemervdzee:
Will do later. First party, then I'll work on a better version and open one up ;)

I noticed there is a strange battery problem. It seems it doesn't really charge the battery, when plugged in usb or wallcharger.

Thanks for the headsup. Might be the 1.7.0.1 ra erasmux is stating. I'm currently at the latest ra aye, with cyanogen 6.1 running. Got no problems with flashing .34 or .35 kernels.

I'm using koush anykernel. It basically generates a boot.img based on the new zImage (kernel) and the current ROMs boot.img. Really nifty tool :)
[Hero, G2 Touch Android Development] erasmux:
In honor of the new year, I would like to give you a taste of things to come - here is my latest progress on the 2.6.35.9:

erasmux-2.6.35.9-pre0

(Generic update should work on any ROM flashed with 1.7.0.1 - see a couple of posts up)

This version is still very raw, and I assume the list of things that work/don't work should be pretty close with riemer's .34. Notably I just fixed the battery driver (which I think doesn't work on his version).

One of the main reasons I am releasing this, is that enthusiasts and flash junkies might post a list of whats working / not working, so later when I do more fixes and code cleanups we can track if I break stuff already working.

EDIT: It appears I only tested this with charger connected, and like riemer commented about his version the lights or something is causing spontaneous reboots. I guess this version is still way too raw to be actual useful for something. If you still want to give it a try keep it connected to usb (possibly AC charger also ok). I'll post another version when I have something more mature.

Sources:

https://github.com/erasmux/cm-kernel

And most importantly:

Happy New Year to all !!!
[Hero, G2 Touch Android Development] riemervdzee:
Nice, however is that .29 rpc stuff really required to get sound working for .35?

Anyway I think of switching to .35 as well aye :) Would be a better base to get stuff working on it...

How does qdsp5_comp work btw? Does sound input work on it at .35? (probably not)
[Hero, G2 Touch Android Development] erasmux:
The mic works in phone calls. Is that what you mean sound input?

The main problem with switching to my .35 (development-wise) is that once I get it a bit more stable I might see fit to do a code cleanup. Might also lazy out on this....
[Hero, G2 Touch Android Development] erasmux:
I am getting a problem, with Riemer's .34 version for example, that after the phone suspends (turn off screen without charger connected ), it will wake up - very slowly but eventually wake up - and become unresponsive. It seems system_server is taking up all the cpu. This does not happen when charger is connected or if I use a .29 kernel.

Riemer, or anyone else, do you also get this? Any leads on whats causing it?
[Hero, G2 Touch Android Development] brokentoaster24:
You should collaborate with deca over on the cdma side, you'll find plenty of testers over there ;)
[Hero, G2 Touch Android Development] erasmux:
Heroc is a different device, hence a totally different port.

Also it seems my .35 version is messed up beyond repair and totally unstable. Note that I also find Riemer's .34 unstable on my device - although I didn't investigate the issues with his version enough. I might return to this if I ever have more free time to devout to android development.
[Hero, G2 Touch Android Development] Crypto_ahash:
Nope dont have this issue. Only issue I am having is when phone goes to sleep and I wake it up the RIL disappears.
[Hero, G2 Touch Android Development] riemervdzee:
Thanks you mention him, I still need to message him about some stuff.

One user had the same tbh. It goes into flightmode then, right? haven't had time to track it down, it seems some lib doesn't get loaded or something. Maybe you can give me a logcat?
[Hero, G2 Touch Android Development] riemervdzee:
*grumble grumble*

Currently got a .35 build as well, loosely based on erasmux's work. However it performs quite slow on my phone, neocore is 22fps with sound off and linpack scores are something not to write home about.

Also got annoying wakeup issues sometimes, which causes a lag of 5 sec to unlock and then it performs 20 sec at "something". It occurs less at erasmux's first build, but still...

Anyway, it doesn't put a smile on my face yet :P nor I can recommend anyone using it for a while. Hope to have something more useful later.
[Hero, G2 Touch Android Development] riemervdzee:
Just to keep you lads updating, Elemag and I fixed the lag problem :) seemed a driver didn't went into suspend mode, now we use one which is more like the htc hero device.

Maybe we'll release a flashable soon if no big stuff arises.

Its functions should be nearly as the one of .34. Including the battery charge
[Hero, G2 Touch Android Development] elelinux:
Absolutely wonderful waiting with great anticipation to your results :D
[Hero, G2 Touch Android Development] rdejager:
Your not the only one Ele :D
[Hero, G2 Touch Android Development] sibbor:
Guys, brilliant stuff! I just knew there was still some time left for my device to live ;-) With .35 I do believe a lot of great things will be coming our way.

Oh, yeah. Same here - and longing for your ROMs based upon it ;-)
[Hero, G2 Touch Android Development] sibbor:
That's just sick. Thanks so much for your contributions! Been running your kernels for... ever (it feels like).

Gonna sit this one out for a couple of days though, than I'm ready for some testing!
[Hero, G2 Touch Android Development] android167:
So, what is working now? and what not?
[Hero, G2 Touch Android Development] SwatMaster:
With the loss of erasmux, we lost a talented dev, unfortunately.

Keep up with your work, our Heros just need people like you! Expecially now!
[Hero, G2 Touch Android Development] kiljacken:
What do you mean??

He's still with us AFAIK ...
[Hero, G2 Touch Android Development] ZeppeMan:
He's not anymore, look at his threads what he posted.
[Hero, G2 Touch Android Development] riemervdzee:
I think he meant that erasmux is still among the living ;)

not working:

- green/red led and trackball led. Disabled, caused random reboots when blinking (microp driver)

- lightsensor. Disabled, causes the whole system to hang @ boot (microp driver)

- Camera. Preview-mode works, but taking pictures makes the whole thing "hang"

- Bluetooth. No idea on this one...

- all audio jack stuff, H2W is not implemented at all.

- accelerometer (bma150 driver, included but needs updating)

buggy:

- battery driver might be a bit off. Got the feeling it reports different levels than the .29 drivers.

- Sometimes we got annoying wakeup issues. Last for 3 sec but resolves quite quickly. Looks another driver can't get into suspend (could be solved already, but need further testing).

- Had a reboot last night?

- Can't reboot into recovery/bootloader at ROM while using this kernel. nandroid partition?

Need to work on a better list though ;)
[Hero, G2 Touch Android Development] kiljacken:
Exactly
[Hero, G2 Touch Android Development] dkelley:
wait - so then how do you get back into recovery again after flashing this kernel?

Maybe I misunderstood your meaning though...
[Desire Q&A, Help & Troubleshooting] Ghashul:
I think if you download Rom Manager from the market, you can install ClockworkRecovery with it.
[Desire Q&A, Help & Troubleshooting] ComfySofa:
that was the simple yes or no i was looking for - thanks very much!!
[Galaxy S I9000 General] AllGamer:
Thanks! :)

just a minor clarification.

We've done much research and we noticed the 3 button problem can be on any batch of phones, even when they have newer / older IMEI, it's not specific to any date releases.

Because we have and I personally have tested phones from the same batch and some works meanwhile the others doesn't work.

It appears that in samsung's production line, one of their machines loading the firmwares are not configured properly, thus pushing out units with the buttons disabled

unfortunately this is not something their QA department checks (it's so obvious) so in the same batch of phones you'll have a mix of good and bad ones.

so, the only way to really find out if it work, is to test it first before you pay for it.
[Galaxy S I9000 General] SUNNY911002:
i had the three button problem on my galaxyS

and i tried to give it back to optus

but they said they can't change for me because it is not what samsung prefer user to use and that will void the warranty.

i bought it for 8days already and what do you prefer me to do?

use the accc law or just use the galaxy without 3 button.

As a international student, i don't know too much on the law

please give me a suggestion.
[Galaxy S I9000 General] miki4242:
I find that very strange, as I know for a fact that Kies supports this very procedure (well, actually several variants of it, depending on device type) when it detects a problem during flashing. It even has a guide showing you how to switch the phone to Recovery Mode using that Vulcan nerve pinch we all know and love, and then reconnect it to attempt recovery (note that box under the device list in the firmware updater that says "List of Devices Requiring Firmware Recovery"?).

So I am quite sure this IS the official way to recover your phone from a misflash (I'll leave it up to you to define 'misflash' :) ) and I believe Optus are just scaremongering and/or trying to sidestep replacement costs and effort.

I would say: go for a replacement, and if the rep asks why, you can quote me on this. Just don't mention Download Mode 'cause that ISN'T covered...
[Galaxy S I9000 General] shanghai01:
Hi Sunny,

Miki is correct. It is a basic recovery procedure that is hardcoded into phones for a purpose that is within the scope of end user day to day use. It is a function that is expected to work and hence the money you pay for it gives you the right to access and utilise said feature.

1. Demand that they replace it with one that has this function. Tell them you risk bricking your phone when upgrading firmware through KIES (Samsung Software) without this feature. They are inexplicably forcing you to never upgrade your phone software in the future because you risk critical data loss by bricking. Tell them that.

2. If they continue to refuse tell them to call up Samsung and find out themselves. Tell them, you don't want to take this route but if necessary you will take it up with the ACCC.

3. If they still refuse, Go to ACCC website or call them and go to the "For Consumers" area and find the lodging a complaint form. Write up a short and detailed letter in the complaint and give evidence of other SGS that do come stock with this function. You paid for the same right and you were misled by the retailer. Since this function cannot be 'fixed' into the device, you demand a replacement.

You can go as far as to say that everyone else who bought this phone stock has this function and its discriminatory for them to not allow you to exercise the same right.

3a. Photocopy your letter along with the complaint forms and fill it out with the retailer details. Take it in and let them know that you will send it in and see them at Tribunal Hearing if you have to unless they replace it for you.

4. Most retailers are like you and me and will definitely give in by now, but if not, then go and send it in and wait to hear from ACCC.

I can't stress to you how important it is to be aggressive especially when you are not in the wrong.

Good luck Sunny.
[Galaxy S I9000 General] tmj12:
How do you find out for sure whether the phone has got this recovery mode enabled? My IMEI number is not one of those within the range numbers you mentioned. It's a stock phone and I haven't done any firmware upgrades thus far.
[Galaxy S I9000 General] SUNNY911002:
THANKS A LOT

I bought it for 10 days already and can i still return it to optus?
[Galaxy S I9000 General] shanghai01:
TMJ: use the three button method and attempt to boot your phone into recovery mode. If you succeed, then you are fine. If not, you may have one of the bad batch. I confirmed and explained the steps to enter Recovery Mode using three button method in the first post.

Sunny: Usually, there is a 14 day policy regarding goods deemed unfit or 'problematic' and you can get a replacement with RETAILER. After those 14 days, the responsibility lies with the manufacturer and you must chase up Samsung instead. Your retailer I'm sure will be aware of this. My advice is to act fast and as soon as possible.

Since the problem cannot be induced by user carelessness or intentionally, theoretically you can still chase up the retailer after 14 days, but since you do not have statutory backing, it may be more difficult.

Hope it works out for you
[Galaxy S I9000 General] SUNNY911002:
To shanghai01, i bricked my phone yesterday and i give it back to optus which i said i dont know what happen. they help me to send it to samsung and check for it. If there is any problem, they will change a new one for me.

Will I be charge for any fee, because i purchase it within 14 days. i should have the right to change it, is that right?
[Galaxy S I9000 General] bhermans:
I'm trying to find some offical Samsung documentation that shows how to access the recovery mode.

Mine doesn't respond to the three button method and my retailer won't replace it, saying it's not a supported feature.
[Galaxy S I9000 General] krisz222:
same problem after JP3 v2

I had the same problem after flashed the JP3 Rooted Clockworldmoded V2 ROM.

The download mode not work but from adb shell i was able to reboot into it.

I decided to flash eclair.

It worked, flashed the device. After that i used the one click root for i9000, it rebooted into recovery and stucked. Cannot apply update.zip, no reboot. There was no way out. If i removed the battery, after rebooted into recovery again. With adb i was able to reboot into bootloader mode, but i dont have ROOT, Recovery and Download mode!

Phone works, but what can i do to Root, or to get into download mode?

Because its not rooted adb shell do not allow any reboot commands.

How can i resolve this problem?
[Galaxy S I9000 General] shwan_3:
samsungs sync or update program should be able to that there is a way you maybe can check http://xdaforums.com/showthread.php?t=766589
[Galaxy S I9000 General] shanghai01:
Sunny, it should be covered as part of Early Life Failure.

You should not be expected to pay any kind of fee.
[Galaxy S I9000 General] chryssa33:
Hello,

A perhaps rather silly question...After you test the 3 button method and it works, how do you end it? Since I just want to test not change anything....

Chryssa
[Galaxy S I9000 General] andybak:
Is this firmware fixable?

Is this firmware fixable?

I would assume it's a feature of the firmware in some way (rather than being a hardware issue).
[Galaxy S I9000 General] shanghai01:
I'm sure you've worked it out by now Chryssa, but you use the volume up and down button to select reboot now and then press the middle home button. It will auto reboot and bring you back to android.

Mate far as I can tell from my research the problem cannot be reprogrammed by end users or actually so far there has been no documentation observing any success with fixing this problem. To be honest I'm not sure if we have the means to modify firmware and if we did it is definitely out of the scope of our warranty. That is, it would definitely void our warranty
[Galaxy S I9000 General] tholus:
Would be really very useful to find some Samsung official reference to the Recovery mode feature.

Some dealers just tell the excuse "this is not an official feature documented in the manuals" and refuse to change the phone.

So far I have not been able to find it in any official document or reference on Samsung website.

Anybody can help?
[Galaxy S I9000 General] AllGamer:
this is something very userful

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

i encourage people from Australia, UK, NZ, and any other nations having problem with Galaxy S to post on the facebook walls of your respective countries
[Galaxy S I9000 General] REAVER117:
Has anyone tried this method?

1. Take out your sim card, sd card, battery and open Odin3.

2. Put the battery in.

3. Plug in USB. (the phone will power on to that screen)

4. Hold down both Volume keys, and then push power. Hold it and dont let go.

5. Wait for it to go black.

6. When it goes black the 2nd time release power and keep holding the Vol Down and Vol Up.

or even just Power + Vol Down?
[Galaxy S I9000 General] davidke:
"Official" recovery mode instructions

I found "official" samsung download mode instructions. Feel free to tattoo it to the face of whomever told you it wasn't a "supported" feature.

This is a screen shot from the Samsung Kies Firmware Restoration panel.

It comes up like this in the very rare circumstance where a previous firmware update has failed.

*Note: My phone is one that cannot do the 3 button combo. BUT, when I got this panel in Kies it finally worked. Just that time. Though kies failed to recover my firmware, Odin 3 did. After recovery, I can no longer go into recovery or download.

*Note2: The screen shot says to switch to "recovery mode", yet the instructions it gives are for "Download mode". Probably a typo...
[Galaxy S I9000 General] AllGamer:
even when your phone is ON

holding those 3 buttons will take you to the yellow download screen

you just need to hold them firmly for about 5 sec

it will go to a black screen and come back with the yellow android under construction sign (download mode)
[Galaxy S I9000 General] bhermans:
thx man! This is exactly what I was looking for!
[Galaxy S I9000 General] Devhux:
My Galaxy S does have the issue regarding recovery mode, although I've somehow managed to get into download mode twice while playing with it. I wish I could figure out exactly what I was doing differently when it did work, as I've done everything listed on this site so far.
[Galaxy S I9000 General] pgn:
i'd really appreciate if you could try and reproduce entering recovery mode and maybe document it here :-) unless it was from the debug tool distributed with the sdk, which will only work with a fully booted device on usb (?)

i'm caught up in the unfortunate decision of a couple incompetent suits (i had other words on my mind to describe these people) in Proximus to cook a few horribly ugly (low res and all) and dysfunctional "Proximus applications" into the firmware and (according to samsung) deny factory firmware updates to be installed on the device.
[Galaxy S I9000 General] icejagans:
I think you can download an app called rom manager from the market. The app allows the recovery mode to be selected. However the phone has to be rooted first to use the app.
[Galaxy S I9000 General] pgn:
Thanks, really.. but we don't want to enter recovery mode just for the fun of it ( its easy to boot into recovery from an already booted device via the SDK tools, and it requires no extra app nor rooting ), we need it to be available when booting the device, by pressing a combination of ( hardware ) keys so if/when ( more like WHEN ) a flash attempt goes south, we can still fall back to a different image.. and that seems to be blocked on some I9000s

I'll just get the latest available samsung image from here with the 512.pit file, flash away and if it becomes a brick, return it and just tell them to enter recovery per the samsung documentation..
[Galaxy S I9000 General] pgn:
I just got word from Sammy customer support that the lack of recovery/download boot from hardware key combinations is indeed intentional because "people were mis-using it"

I find this disgusting and it totally goes against the open platform that is Android. **** you, Samsung.
[Galaxy S I9000 General] bigl666:
Right from the facebook page:

"Samsung Mobile: Canada Some of you have reported to us that there is an intermittent software issue affecting the Galaxy S and “recovery mode” functionality. We’ll be announcing a downloadable software update shortly. Thank you for your patience."
[Galaxy S I9000 General] Tyxerakias:
The fact that davidke could enter the 3 button download mode during a Kies upgrade ONLY, and then couldn't do it again, points to software, not hardware. Which means it's potentially fixable.
[Galaxy S I9000 General] miki4242:
Probably by sending a 'hidden', undocumented command using adb or some kind of fastboot protocol. HTC tweakers here will probably have heard about the many "fastboot oem" commands out there.

Sad but true: using a mobile phone means that you carry a piece of telco equipment in your pocket. The fact that you paid dearly to own 95% of it doesn't change the fact that the telco's and the manufacturer think the other 5% is to be off-limits to us...