yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] eyespunker:
ditto. No problems here on any rom yet as far as capacitive lights or flashing a rom. hboot.33 Just as a test maybe somebody with the problems as far as lights go could try to revert to hboot .33 just as a test to see if it fixes the lights and other possible problems. Might still be h/w related but it's worth a shot.
[Android Software/Hacking General [Developers Only]] toca79:
Hope this is the right forum, i would like to know if there is a project trying port webos on andorid devices.

I think android is really a great os, but webos is still better, sadly pre and pre plus are really rubbish, while android devices are top class now.

Hope to see this happen soon.
[Desire Q&A, Help & Troubleshooting] Tander_ZA:
Howzit guys,

I would like to know if it is possible to create and edit documents on this phone? I have quick office which allows me to open documents, but not edit them? Or am I missing something here?

Is there a free app in the market place for this?

Many thanks!
[Desire Q&A, Help & Troubleshooting] bharris25:
Documents to go costs 15$ but its decent, haven't tried any of the free apps.
[Desire Q&A, Help & Troubleshooting] Tander_ZA:
Problem I have with paid apps is I am in South Africa and it doesn't seem to be supported here. Is there anyway around it?
[Desire Q&A, Help & Troubleshooting] foxmeister:
You can either use a Market Enabler (for rooted phones) to enable the Market in your area, or you can buy direct from Dataviz.

It's a great application and well worth the money.

Regards,

Dave
[Desire Q&A, Help & Troubleshooting] Tander_ZA:
I will have a look for Market enabler.

Many thanks!
[Desire Q&A, Help & Troubleshooting] Tander_ZA:
Cannot find Market Enabler. Where would I be able to get the .apk for it?
[Desire Q&A, Help & Troubleshooting] tudork:
I am also from a country where you cannot buy from the Market so I bought directly from the developers' site. Very easy to do.
[Desire Q&A, Help & Troubleshooting] foxmeister:
Google Android Market Enabler, and you will find it.

Regards,

Dave
[Galaxy S I9000 Q&A, Help & Troubleshooting] AndyCr15:
I'm using JM7, with Tayutama 1.2 and Voodoo 4 beta.

Can anyone tell me why I seem to have lost all base when playing music?

Is there a Graphic Equalizer I can use to turn it back up?

Thanks.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sturmeh:
You haven't 'lost all bass' you are hearing the natural music without any distortion.

Voodoo lag-fix removes the infamous EQ filter Samsung enables when you plug in a Head-set.

Use the Samsung EQ if you want to mutilate your music again.

EDIT: The eq is in the music player, press Menu and options, then look for EQ settings.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AndyCr15:
Erm, I'm not pluging in a headset. Yes I am losing base, but I think it was more on the car stereo side as I've made some adjustments and I have base again.

Thanks.
[Desire General] zukers:
Is any way to remove boot splash to have a view of all android boot process?
[Desire General] EddyOS:
Not yet, perhaps with S-OFF you might be able to do this...
[Galaxy S I9000 Themes and Apps] milkaa13:
Hi, have been using stock sgs camera. Its okay.. but was wondering if there's a better camera app out there.

When I had my HTC magic, camera 360 really improved the quality of the photos.

But when I compare the photos I took on my sgs from the stock camera app vs camera 360, I kinda prefer the stock camera colours.
[Galaxy S I9000 Themes and Apps] doop:
Have you tried Vignette.It has loads of different settings.
[Galaxy S I9000 Themes and Apps] milkaa13:
I've only tried the demo version of vignette. And that does not allow the 5mpx resolutions to be used. Besides the array of settings, does vignette actually improve the quality of the photos taken? Thanks.
[Galaxy S I9000 Themes and Apps] Lepaz:
The full version of Vignette does indeed take better quality images, but it takes significantly more time to process the photos.
[Galaxy S I9000 Themes and Apps] ta7seen:
i just tried vignette and the quality was near enough the same .. refunded it cos it wasnt worth the money :(

the camera is the only thing i dont like about this phone
[Galaxy S I9000 Themes and Apps] stickfinger:
Have you tried the Photoshop app? Its not exactly a camera application but it has lots of settings for touching photos up afterwards. Maybe one of the filters will give you the effect you require
[Galaxy S I9000 Themes and Apps] opensourcefan:
I too would pay for a real pro app. Something that will take higher res panorama shots and something with a real HDR function. By real I mean not a simulation and not tone mapping from the gallery pics. There's a app for the iDevices that works wonders on the iP4. Tried everything so far, still waiting.
[Galaxy S I9000 Themes and Apps] kalki:
Try: camera 360 pro
[Galaxy S I9000 Themes and Apps] opensourcefan:
360 pro simulates HDR and simulates a lot of other stuff, we need a app that actually takes better shots etc. At least that's my experience with it.
[Galaxy S I9000 Themes and Apps] vlad11:
The camera apps on the android market are really sub-par.

I don't use the camera much to begin with, but an app as good as Hipstamatic or Camera Pro like on the iPhone would be great.

Vignette has an ugly interface and has average picture quality, and Retro Camera has horrible picture quality.
[Galaxy S I9000 General] bilboa1:
http://github.com/wesgarner/GalaxyS_kernel/commit/072287938eb28fbc3b2174e97cbcab33c111c501

That's commited by wes garner yesterday for galaxy's 2.6.29 kernel and it reads:

keeping in mind that VFS is the virtual file system switch. don't know if it boost RFS performance enough, but it should boost performance of every fs anyway.

here's some benchmarks and they're impressive:
[Galaxy S I9000 Android Development] Stefanauss:
I would have thought this has been done already. xD

Extremely helpful and insightful, thanks mate =)
[Galaxy S I9000 Android Development] miki4242:
Of course I searched, but couldn't find anyone who has done this and actually published the findings, that's why this thread exists :)
[Galaxy S I9000 Android Development] miki4242:
Bump, updates and cleanup.
[Galaxy S I9000 Android Development] oswade:
Great stuff! bumping this thread so more developers can see it ;)
[Galaxy S I9000 Android Development] sirphunkee:
Stickied. Thanks for the efforts miki, the mods agreed that it looks great just the way it is, and we appreciate that you're keeping it updated.
[Galaxy S I9000 Android Development] KeesKaas:
tv-out drivers, now we only need a adapter

micro usb->hdmi cables are only a few dollar
[Galaxy S I9000 Android Development] RyanZA:
The tv-out is for the headset jack. Although I'm sure it would be possible to modify the code, if it doesn't already work. ;)
[Galaxy S I9000 Android Development] miki4242:
Thanks! I'll do my best to update it. I hope the kernel hackers and ROM chefs out there have good use for it.
[Galaxy S I9000 Android Development] zygame:
I'm sorry,but if this meaning that possible to port an official AOSP 2.6.34/35 kernel to SGS just for AOSP build or CM6?
[Galaxy S I9000 Android Development] miki4242:
Sure! But I think you will need quite a lot of experience with doing complicated Git rebase merges. The difference in kernel versions is quite big (you did bring your seven mile boots did you?) but nothing is impossible, ask Linus :)

I find Samsung's changes quite clean (not too many arbitrary tweaks scattered all over the place), so it is doable. I've seen many miracles worked by the XDA people, so I would say: go for it!

Another fly in the ointment is the drivers/media/video stuff, which comes from a snapshot of the Video4Linux project. I'll see if I can find a nice point in (Git repo) history to stick that onto the AOSP tree (or separate out Samsung's patches to that entirely) and redo the patchset.
[Galaxy S I9000 Android Development] miki4242:
Update: added battery measurement driver, Maxim voltage regulator drivers.

Update: added sensors: accelerometer, compass and proximity sensor.

Update: added Flash drivers: TinyFSR, Flex-OneNAND and LinuStoreIII.

Update: added USB Gadget driver.

Update: added display panel (including mDNIe) drivers.

Update: add FAT FS (hide /sdcard/sd) mod.
[Galaxy S I9000 Android Development] xan:
This looks like a beginning of something BIG :D
[Galaxy S I9000 Android Development] Phlogiston:
If we have the kernel running with samsung patches it should be not that much work to get a rom running. But we really should keep contact with the cm guys or the work will be done twice... :o
[Galaxy S I9000 Android Development] miki4242:
Agreed! :)
[Galaxy S I9000 Android Development] Phlogiston:
There is some interesting stuff here:

http://github.com/wesgarner/android_device_samsung_vibrant forked from:

http://github.com/CyanogenMod/android_device_samsung_vibrant

Anyone tried to let run cm on top of the stock .29 kernel? Any reason this would totally fail?

PS: Maybe we should create a new thread about kernel hacking for cm here? Who would jump in?
[Galaxy S I9000 Android Development] cantIntoCode:
Agreed again!
[Galaxy S I9000 Android Development] Mithent:
That's what I'm wondering - I've always thought that it really shouldn't be that difficult (conceptually speaking) to get AOSP running given that we have the source for Samsung's modifications.

I'm not experienced with Android or Linux development myself, but I hope someone can do it - would love to see AOSP running, because it would give me confidence that we don't need to rely on Samsung for future updates. There was some previous received wisdom that SGS ROMs had to come from Samsung because of "encrypted drivers", but as pointed out here, there's only two kernel modules that are even binary.

(The whole "encrypted drivers" thing never made sense to me.. it would be way against the GPL, and CPUs don't run encrypted code, so it would have to be decrypted before use anyway? I've always been confident that someone was confusing "precompiled drivers" with "encrypted drivers" because they weren't human-readable.)
[Galaxy S I9000 Android Development] bilboa1:
It would be neat to compile linux-zen.git with these patches for a try (as zen now includes long due linux latency patches which might just fix some of the lag issues on the sgs - even with ext4/what-not)

I'm wondering if it would work however, it seems to me Samsung hacked up the kernel a lot and forgot proper locking, memory allocs. Changing most significant options in 2.6.29 = kernel panic on boot... like SLUB or preemptive kernel..
[Galaxy S I9000 Android Development] Evans_Prophet:
Battery current support?

Nice work there. I just wonder whether there is any manner to measure the current drawn at a specific moment from the battery (in other androids it is possible and there is even a widget for that).

This would allow us to optimize battery usage by identifying app increasing the consumption.

Just check here: http://xdaforums.com/showthread.php?t=723217&page=8
[Galaxy S I9000 Android Development] miki4242:
If the info is available (depends on hardware support), I think you will be able to get it into an app by reading from the files in /sys/class/power_supply/battery on the phone (no root required).

Note (a gotcha): When testing, you may need to unplug the phone from USB and run adb over the network or use a terminal program on the phone itself, because it may not be possible to measure current draw while charging at the same time :)

From a quick glance I couldn't identify anything indicating current draw, but there's adc values in there which you may be able to crunch into something like that using Ohm's Law and power estimates.

The kernel drivers for all this are in:

GalaxyS/linux-2.6.29/drivers/power/fuel_gauge.c

GalaxyS/linux-2.6.29/drivers/power/s5pc110_battery.c

GalaxyS/linux-2.6.29/drivers/power/s5pc110_battery.h

Hope this helps.
[Galaxy S I9000 Android Development] TDO:
I think he means

+#ifdef __CHECK_CHG_CURRENT__

+	SEC_BATTERY_ATTR(batt_chg_current),

+#endif /* __CHECK_CHG_CURRENT__ */

in kernel_common_drivers_power_s5pc110_battery.c

The vibrant kernel has it included the SGS not.
[Galaxy S I9000 Android Development] miki4242:
Aha, interesting! Maybe it's time to start comparing diffs of different SGS variants using `interdiff` (wow, how's that for a tongue-twister).

If I have some time, I'll look into it, small problem is that my poor hard drive is already groaning under the load of so many kernel trees, dissected firmwares etc :)

Edit: I'll post a small howto on how I made the patchset (it's not hard at all) so people can help with creating them for the different models.

(dreaming) Maybe one day we can have one big fat Git repository with branches for all the SGS models. That would be cool!
[Galaxy S I9000 Android Development] Evans_Prophet:
Current draw support in SGS

When I had checked I couldn't find anything as regards current. If we can find it (or copy it from Vibrant if possible) then we could implement the power current widget in SGS as well.

I am really interested in measuring current, since this would allow me to reach some exact conclusions as regards the power consuming services / applications (afterall, this would be the more reliable manner to check whether a battery is faulty or it is just some stupid application draining the battery like crazy. Just checking battery percentage is not very helpful or accurate for this kind of things).

This would also be helpful for ROM developers as well as ROM testing / comparison (e.g. check default average current between two newly installed roms).
[Galaxy S I9000 Android Development] supercurio:
I started to study Kernel differences between I9000/Vibrant/Captivate but I think this is already totally superseded by the work done here.

Count me in to work on an up-to-date and higher quality kernel and code Voodoo's changes for it ! :)
[Galaxy S I9000 Android Development] miki4242:
Thanks for volunteering!

I'll sit down now and add a small howto to first post on how to do the patchsets. Then it will (hopefully) be a matter of sucking down all the relevant source zips from opensource.samsung.com and running a simple script.

Once you have the (single or multiple) patch file(s), it's just a matter of running `interdiff patch1 patch2` to see difference between variants.
[Galaxy S I9000 Android Development] miki4242:
Updated: Added HOWTO to first post.
[Galaxy S I9000 Android Development] trancelated:
Dont you think that the forensics has something to do with samsung's inbuilt phone tracker?

If yes, how do you think that it works?
[Galaxy S I9000 Android Development] miki4242:
:D The only meaningful comment I can find is in GalaxyS/linux-2.6.29/kernel/sched.c:

"Add GAForensic init for preventing symbol removal for optimization. (tkhwang)"
[Galaxy S I9000 Android Development] supercurio:
Seems like nobody posted it yet :

Samsung has a git repository at kernel.org.

http://git.kernel.org/?p=linux/kernel/git/kki_ap/linux-2.6-samsung.git

It's not Galaxy S sources, but it looks like their reference source for S5PC110

Could prove useful, it contains lot of their patches for recent kernels ;)
[Galaxy S I9000 Android Development] TMC_Sherpa:
Sweet, someone else is working on this stuff too.

I have a broad listing of whats different between the Samsung phones, it's Captivate centric seeing as that's what I've got but it does get some of the dirty work out of the way.

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

Sherpa
[Galaxy S I9000 Android Development] miki4242:
Very good one, supercurio and TMC_Sherpa! I will add links to the top post.

Now we desperately need a Git genealogist to research the history of all those Samsung (family) trees.

If we can find a common ancestor (besides Linus' grandfather kernel, obviously), it will be much easier to cross-port patches between them. (It's a good thing that Linux kernels don't care about inbreeding :) )
[Galaxy S I9000 Android Development] dalingrin:
Wow, that could be really useful.
[Galaxy S I9000 Android Development] miki4242:
Thanks! Added to first post.
[Galaxy S I9000 Android Development] miki4242:
Update: Change HOWTO to use 'fromdos'.
[Galaxy S I9000 Android Development] darkbyt3:
git rep

found this:

hxxp://git.tarot.com.tw/?p=android-ctc/kernel.git;a=summary

The source code seems to be more complete here(+ other interesting things on this git rep)

I tried to compile some modules (cifs.ko) for kernel 2.6.32 but no luck :( (phone restarting when trying to mount smth)
[Galaxy S I9000 Android Development] Phlogiston:
How did you find that? Looks very promising actually!

Its apparently for this device: http://www.yicsystem.com/contents/english/smdkv210.htm
[Galaxy S I9000 Android Development] darkbyt3:
drivers for SMDKV210 and SMDKC110(i9000) are both in arch/arm/mach-s5pv210/ in kernel 2.6.32
[Galaxy S I9000 Android Development] Phlogiston:
Yes, same processor and arch as on the i9000 ;) I'm almost there with loading a module... :D
[Galaxy S I9000 Android Development] Phlogiston:
My phone does reboot when I try to load the module... any idea?
[Galaxy S I9000 Android Development] Einride:
This looks like it might be for a tablet of some sorts?. One commit changes the resolution in a struct in the lcd driver.

hxxp://git.tarot.com.tw/?p=android-ctc/kernel.git;a=commitdiff;h=6178f482022aefd0e69963bd1e1abc93fdf9f319

There's also a commit earlier where the base memory address is changed, perhaps for reserving memory like on the Galaxy S? There seems to be several different revisions or versions of the S5PC110, with different memory configurations.

hxxp://git.tarot.com.tw/?p=android-ctc/kernel.git;a=commitdiff;h=273697d901ec5d05af0a25b65baf8b3b4a29e2a6

(Sorry, had to butcher these URLs since I'm not allowed to post any links yet.)
[Galaxy S I9000 Android Development] darkbyt3:
Unfortunately we don't have the configuration for the kernel. I tried to copy them from 2.6.29 release but didn't work. (I can now load the module, lsmod works but when I try to use it my phone reboots)
[Galaxy S I9000 Android Development] darkbyt3:
In default kernel(2.6.32) they use SPARSEMEM configuration for SMDKC110, but the kernel from jph is compiled with DISCONTIGMEM. I just don't get it why they commit something in kernel and actually use something else.
[Galaxy S I9000 Android Development] Phlogiston:
Hmm weird, what module did you try? I tried with config.ko and used arch/arm/configs/sec_smdkv210_android_defconfig.
[Galaxy S I9000 Android Development] darkbyt3:
I manually modified the parameters to match those from samsung's release of 2.6.29.

The module was cifs.ko (windows shares)
[Galaxy S I9000 Android Development] Phlogiston:
Hmm, the kernel source of .29 is available completely... did you try to compile full kernel? Ask the voodoo guys
[Galaxy S I9000 Android Development] darkbyt3:
I tried to compile only a module. I think they changed the memory reservations for .32 kernel. I found a new driver which required memory reservation in config(.32) that didn't appear in .29 so maybe this is why the phone keeps rebooting when I try to use the module.

Btw I think we will never have full 512 MB ram available, some drivers reserve 100MB+ (at least in .29)
[Galaxy S I9000 Android Development] andars05:
Do you think that it would be possible to lower the amount of reserved memory from what it currently is?
[Galaxy S I9000 Android Development] miki4242:
That is a very interesting one, thanks!

From some Googling around, this appears to be part of a Froyo port to the SMDKV210, a development board. Link

Since this is cross-posted from the odroid-developer-discuss mailinglist and I've just received my Odroid-T development tablet, this is interesting in more than one way :)
[Galaxy S I9000 Android Development] ttabbal:
Anyone figure out how to use this?
[Galaxy S I9000 Android Development] sztupy:
On the tarot.com.tw git there's actually a kernel that supports DISCONTIGMEM for the S5PC110/SMDKC110, but loading a module (I've tried with jbd2/ext4 and jbd/ext3) compiled that way will still restart the phone.
[Galaxy S I9000 Android Development] compuse:
Aren't these patches a pain in rom development?

Wondering it, so that i won't bother getting into it too much! =/

ty
[Galaxy S I9000 Android Development] mapas:
printk is used to print kernel messages to /var/log/messages when syslog is enabled.
[Galaxy S I9000 Android Development] miki4242:
...or to USB apparently, as implemented in this case.

The device name is /dev/dm , but until we know more about VendorID/ProductID and protocol used, no way to capture the info.

Protocol header is known, defined as:

+/*
+ * Mark for GetLog (tkhwang)
+ */
+
+static struct struct_kernel_log_mark kernel_log_mark = {
+ .special_mark_1 = (('*' << 24) | ('^' << 16) | ('^' << 8) | ('*' << 0)),
+ .special_mark_2 = (('I' << 24) | ('n' << 16) | ('f' << 8) | ('o' << 0)),
+ .special_mark_3 = (('H' << 24) | ('e' << 16) | ('r' << 8) | ('e' << 0)),
+ .special_mark_4 = (('k' << 24) | ('l' << 16) | ('o' << 8) | ('g' << 0)),
+ .p__log_buf = __log_buf,
+};

where GetLog is probably related to an internal tool which Samsung engineers use for debugging. It's certainly not the getlog from the Android SDK, as that simply runs an adb command to pull the logfile from a device.
[Galaxy S I9000 Android Development] xcaliburinhand:
Decided to give compiling a kernel from the tarot.com.tw git a try. Tweaked the config as much as I could to line it up with the I9000 source (correct frame buffers, settings, etc.) but no luck.

Of course I have no debug capability so no clues into what is killing the kernel.

Anyone make any better progress?
[Galaxy S I9000 Android Development] justcme:
Hey guys, just popping in to post a suggestion here, relating to RFS research, and also other changes Samsung might have made:

Have you considered searching in the other sources Samsung has released? (for other devices)

We all know there are RFS documents released by Samsung about how to port it to the Linux kernel (it still uses a binary blob I think, but at least the wrapper for it should be independent of the device and relatively independent of the kernel-version). Naturally you'd expect Samsung to have the required sources and binary blobs online somwhere. Perhaps I was looking in all the wrong places, but as hard as I tried, I was unable to find the sources required for porting RFS - not even on Samsung's own website. They did have OneNAND stuff, but no RFS things.

So I decided to look at the sources at opensourcesamsung, and looked for devices which ran Eclair. Turns out the first one I chose was the the I5500 sources, one of their older Android devices.

Anyway, from the limited amount of time I had to look at it, I saw that Samsung had RFS integrated into the 2.6.29 kernel sources for the I5500. KConfig and all. I think it may be beneficial to take a look at the I5500 sources and report back what the changes are. If everything there is complete, I don't see why we can't port the FS changes back into the I9000 sources, and see if we can figure out why RFS is giving so many problems. :)

I was going to do a lot more delving into the I5500 sources (and other devices too) myself and report back here, but found myself short of time. So I'm posting it here for you guys to explore!

I have only had a brief look at the I5500 sources, so I'm not sure what's available for the other Eclair devices. But I think I5500 is a good start. :D

Gluck guys! I'm keen on seeing if the I5500 sources will be useful or not. :)

Okay, back to forum lurking... ;)