yashsingh1/xdaforums huggingface dataset:
[myTouch 3G Slide General] DenominatorX:
I work for T-Mobile. They will definitely try to get this phone back to the owner. This would make someones day - do the right thing and PM me if you have any questions.
[myTouch 3G Slide General] parmijo11:
T-Mobile

I work for T-Mobile Android/BB/PDA support and we can track down who the owner is regardless if its locked or not. You think your mobile number or IMEI are the only ways we can look up your account?.?
[Vibrant General] aliensite:
³ (cubed) player still sees it even though it was deleted with Samsung player. The playlist is empty if selected.
[Vibrant General] splat matt:
Rescan the media (or just turn off and on the phone)
[XPERIA X10 Themes and Apps] lorius:
I'm sorry I have one stupid question.

Is there any chance to change the color of bottom leds between menu and back buttons ?

Thanks in advance
[XPERIA X10 Themes and Apps] james_2k:
yes someone did it. but it involves hardware modifcation.

he talks about it in this thread: http://xdaforums.com/showthread.php?t=668132
[XPERIA X10 Themes and Apps] lorius:
:)

Thanks a lot ;)
[XPERIA X10 Themes and Apps] james_2k:
no problemo!
[Captivate General] jedens:
okay so i've seen where you use the volume up + down + power to go into downloading mode but how do i get to the little digger guy with the shovel? because using odin i dont know if i need to be on the screen with the shovel guy or on the screen where i have the option to reinstall packages, reboot the phone can someone help me?
[Captivate General] designgears:
http://xdaforums.com/showthread.php?t=731989

reading the stickies is a good place to start :)
[Captivate General] jedens:
but i've followed that thread step by step and i cannot for the life of me get odin to work
[Captivate General] jedens:
every time i do the volume up+down+power it goes into system recovery mode
[Captivate General] Zilch25:
If your phone functions you can use adb to get in there too. From your SDK tools folder just type "adb reboot download" and it'll send you directly to download mode
[Captivate General] jedens:
its not the recovery mode i have the problem getting to but when i do get there odin wont recigonize my phone and i need to reset to the stock rom which is why i have a feeling i need to get to the android guy with the shovel
[Captivate General] Zilch25:
Follow these steps exactly:

Close odin (if it's open)

Unplug phone from USB

Remove SIM/SD card

Remove Battery

Open Odin

Put battery back in

Plug in USB

Hold both volume keys THEN hold power

Continue holding all 3 keys, the screen will come on, DO NOT LET GO

The screen will go black, then turn on again- as soon as it turns off for the second time let go of the power button but continue holding the volume keys.

In a couple seconds you should get the download screen
[Captivate General] Colton5419:
I understand the frustration, there are a lot of stickies currently and numerous pages to browse to find information on entering download mode.

Try this:

1.) Remove the Battery, SIM card and micro SD Card.

2.) Reinstall the Battery. (DO NOT TURN ON THE DEVICE)

3.) Hold ONLY the volume buttons down and then insert the USB cable.

This should bring you into download mode (The android guy/shovel and will say "downloading....")

You do not need to press the power button at all for this method. Also, be sure to have installed the drivers for the device.
[Captivate General] joeybear23:
Yes, this is what I did and it works like a charm.

ONLY hold in the Vol-Up/Vol-Down buttons while plugging in the USB cable.

DO NOT press the power button.
[Captivate General] jedens:
thank you so much colton!!!! that worked so easily
[Captivate General] designgears:
haha, I see, you were using the directoins for getting out of the cell-!-cpu screen...
[Captivate General] jasonyump:
This is posted in the wrong section

Next time if you have a question that's unrelated and not a.topic of android development, can you please post in the general section? This is not the only forum people read and people will respond.

Thanks
[Vibrant General] Creamybrown:
Hey guys I've read about another serious issue plaguing the Vibrant and unfortunately it has been affecting mine too. It's with the Music player. Every time I play a song, there's a lag or a stutter in the song.

Regardless of what song is playing, there's a serious stutter, and it takes away from the music experience.

At this point I'm ready to refund this baby back to bell and unfortunately am considering the Iphone.

I really don't want to but the phone is kinda laggy and with the gps + stuttering problem it's getting quite annoying.

Anyone else have this experience while listening to music? Or is it just mine? It's unfortunate cause the screen is quite nice and responsive at times.

It just seems like Samsung hasn't really fixed any of the bugs plaguing the phone.
[Vibrant General] layzer253:
What are the specifics on your media? Bitrate/encoder/file type? Are you playing off the internal or external sd?
[Vibrant General] Creamybrown:
The encoders are all across the platforms. I have .mp3's to .Wma's. Every song has a time where it stutters.

When I had my g1 this stutter and pause in the music happens when I recieved a text message.

It's just a really fast little pause and it really disturbs the music.

I'm using internal memory.
[Vibrant General] LiquidCool1:
Same problem here . . .

I am using the internal SD card as well

mp3s

196kbps fixed

44.1 khz

basically as vanilla as you can get. . .

I tried airplane mode, just in case it was a sync issue, no luck
[Vibrant General] PathogenX:
I just put a few songs on the 2gb sd card that came with the phone and I tried to play a song and the screen went black and my touch sensitive buttons were light up lol and it restarted itself.

Going back to my Zune HD/iPod lol. oh well. When it comes to media the iPhone takes the cake. Android is more nerdy and customizable.

Doesn't bother me too much. I would have personally like to have an all in one device but dont have the money for ATT's plan and prefer androids customization over iPhones.
[Vibrant General] Creamybrown:
The Galaxy S Vibrant is supposed to be the best android phone for music on the market. Why should you cough up the dough and then go back to listening on another player?

It's not right. I'm beginning to think it's a software issue.
[Vibrant General] deviusdragger:
I've had no problems at all with the music player. Music in mp3 format at 320kbs.
[Vibrant General] tengtengvn:
I have about 8GB of MP3, WMA and 4GB of FLAC songs on a class 4 microSD card. I don't have any issue as you describe. Try to reset your phone first.

iPhone and Zune only play few formats. Drag and drop FTW. What a PITA when I have you sync everything to my iPhone using that stupid iTunes. To be able to play my song/movie without converting it to another format FTW too.:cool:
[Vibrant General] phantomzer0:
Ive noticed this issue as well. The best way to describe it, is like a cd skipping real fast. It's less than a second long, and it's literally a skip in playback.

I initially suspected it was a small lag spike from the screen shutting off, but Ive had it happen twice in a row after the screen is already off.

There must be some process running in the background that is causing this to happen, because it's totally random. It does happen after the screen shuts off though.
[Vibrant General] jayzusfk:
I've been using mine with a class 2 card and about 14 gb of music of mostly mp3s. I get an _occasional_ skip but nothing more than I would get with any other music player. Haven't noticed anything else going on at the same time though.

I think it's your device, though IMO if that's enough to make you want an iphone then you're probably missing the point of android in the first place.
[Vibrant General] zerosource:
This happen to me too. The stock music player. Though, I have no problem with other music player apps eg. 3(cube), mixzing.
[Vibrant General] heygrl:
It's likely to be a widget. For me it was Gauge Battery.
[Vibrant General] smashpunks:
Im not getting any type of stuttering.... This plays music flawlessly...

Theres got to be something going on with your device. Also I would have heard about this issue alot more if everyone was experiencing it...
[Vibrant General] bdveteran18:
Agreed. I don't have this problem either or have never noticed it. The only time I noticed skipping, it was a singular song I had on the device. Not a random occurrence as explained.

That makes issue 3 for the Vibrant that I don't have
[Vibrant General] infinityhombre:
The same goes for me. No problems with any other music player only the stock. It's not even close to bad enough to switch from this device only happens once every so often.
[Vibrant General] LiquidCool1:
Ok tried simply music app and playing from a class 6 card. Still getting the stutter. I am using beautiful widget weather app, will disable it and try again. . .

Sent from my SGH-T959
[Vibrant General] mi4kidzmom:
I have about 5G of music from itunes on my vibrant. I used isync app from the market to get the music from my itunes to my phone, I have had the phone 3 weeks and have experienced ZERO lag, stutter, or skipping...but my uncle who got the phone the same day from the store (i received mine through mail) had the same problem with the stock player. I think its because he used widows media player.
[Vibrant General] Relikk356:
I have the studder issue. Uploaded through windows media player. It seems to happen when i load the first song, and happens more if I'm listening to music while I search through the the music lists. When the screen is inactive it works perfectly unless its the first song. I have almost 8 gigs of music
[Vibrant General] LiquidCool1:
It was the weather widget that was causing the problem, thanks heygrl.

Sent from my SGH-T959
[Vibrant General] PathogenX:
Sorry for hijacking kinda

but I am about to retry it once again. I don't have a SD card other than the 2gb that came with the phone should I put the music on the phones internal and see if I get studdering again?
[Vibrant General] LiquidCool1:
@pathogenx

The card did not make a difference for me, but the weather widget was updating the time every minute and that seemed to cause the stutter.

Sent from my SGH-T959
[Vibrant General] neronz:
i am having the stutter lag in between music too. this is very irritating. it the same experience with the stock music player or 3rd party music player like poweramp.
[Galaxy S I9000 Android Development] raspdeep:
Here is the kernel with yaffs2 and MTD block support, I am missing some mtd util tools like nandwrite so i cannot continue. Those that have the tools like mkyaffs2image, nandwrite, flash_eraseall can try to create an image and mount it

here are the steps that i think should work:

# mknod /dev/mtd0 c 90 0

# flash_eraseall /dev/mtd0

# mkyaffs2image /data/data yaffs2.img

# nandwrite -p /dev/mtd0 yaffs2.img

# mkdir /data/data2

# mount -t yaffs2 /dev/mtdblock0 /data/data2

If you have the tools, please attach so we can continue.. Its getting late so I am going to bed, have fun

Download

yaffs2_support.tar
[Galaxy S I9000 Android Development] darksnarfer:
Oh my god! I was just about to post similar findings, what a coincidence! :)

I just had compiled a kernel with yaffs2 support. My idea was to modify /init.rc in the kernel to mount the partitions with yaffs2 instead of rfs. Problem: we can't just change the filesystem without backing up and restoring all the files inside. My idea was to do that inside the recovery. Mount a mountpoint, backup with tar to /sdcard, unmount, format with dd (in theory a partition filled with 0's is ok for yaffs2), mount again with yaffs2 and restore from tar.

I'm stuck at the point that I can't seem able to mount any partition with yaffs2 previously formatted (with /system/xbin/busybox dd if=/dev/zero of=/dev/block/stl10). If I mount (/system/xbin/busybox mount -t yaffs2 /dev/block/stl10 /dbdata) there is always an "Invalid argument" error. It happens with /dev/block/stl*, /dev/block/bml* and /dev/block/mmcblk*

I'm no kernel expert, neither I know a lot about yaffs2, but I think I read you can't mount a yaffs2 partition anywhere, it has to be an MTD flash device.

Anyway, I'm going to try with the tools you said. Wish me luck.
[Galaxy S I9000 Android Development] bub181:
Thanks for your work rasdeep! Is it only YAFFS2 and MTD support that you added? Because the kernel already had support for EXT2 and EXT3.

Does the kernel that rasdeep posted load the existng flash devices/partitions as MTD devices?

I think as a start you only have to worry about formatting the /dev/block/mmcblk0p2 device which is mapped to the /data directory. With the new lag fix we are only moving directories stored in /data and that is what gives a big performance improvement. RyanZA did tests and found that the /dbdata partition was already quite fast and I don't think we have to worry about the /system partition etc. because we don't really write to them.

I think after a new firmware flash the /dev/block/mmcblk0p2 (mounted as /data) will be safe to format into YAFFS2 without loosing anything important.

I think these are the steps we can do:

1. Flash new firmware with repartition option on to erase everything.

2. Boot into recovery and format /dev/block/mmcblk0p2 as YAFFS2 filesystem.

3. Copy on new a init.rc script which will mount /dev/block/mmcblk0p2 to /data as a YAFFS2 filesystem and not a RFS filesytem to get much faster speeds.
[Galaxy S I9000 Android Development] darksnarfer:
Just checked, there isn't any /dev/block/mtd* so I guess the kernel still can't see them as mtd.
[Galaxy S I9000 Android Development] ivanmmj:
/data is on the internal SD not in NAND so will we be able to use yaffs2 at all? I was working on formatting to EXT4 and adding the init.rc to match as well as compiling with EXT4 support, but if yaffs2 works, I'm fine with that.
[Galaxy S I9000 Android Development] raspdeep:
modifying the init.rc is secondary because that is easy.. the main problem now is to be able to manually setup yaffs2 to mount properly.. if everything works like it should, init.rc can be change in matter of seconds :)

its funny now u said mtd not found.. i know we can mknod /dev/mtd* but there should be /dev/mtdblock* when booting with kernel right? hmm.. something to investigate further..

keep suggestions and finding coming, we may hit something that i've missed

problem is im lacking those tools that will do write to flash directly.. for example nandwrite.. anyone has that can share so i can try more stuff?

also, are my steps for "preparing" yaffs2 partitions/image correct? if anyone familiar with yaffs, please give some insight :)
[Galaxy S I9000 Android Development] bub181:
Do you need to recompile the kernel to modify the init.rc? If not could you post some instructions on how to do it please? I would like to try some things in there before /data gets mounted as a RFS filesystem.
[Galaxy S I9000 Android Development] raspdeep:
i'm afraid so for now until someone found a way to extract the initramfs from later kernel and restore it back after modification..
[Galaxy S I9000 Android Development] ivanmmj:
I think it would be easier to start out with EXT2 since we can easily format that. Just as a proof of concept. I'm planning to do so tonight. Then I'll add support for EXT4 formatting and try that.
[Galaxy S I9000 Android Development] bub181:
Have you seen these pages rasdeep? They seem to describe how to create the YAFFS filesystem. Also, are there any /dev/mtdblock* devices using the kernel that you created? According to what I read elsewhere it is supposed to create both /dev/mtd* and /dev/mtdblock*. I think we have to use /dev/mtdblock* to create the new filesystem.

http://processors.wiki.ti.com/index.php/Create_a_YAFFS_Target_Image

http://processors.wiki.ti.com/index.php/MTD_Utilities

http://processors.wiki.ti.com/index.php/Put_YAFFS_Image_to_Flash

Also, I know that the Nexus One uses YAFFS2 for its internal filesystem. Maybe someone has worked out a way to write a new image file for that and we can use what they have learnt?
[Galaxy S I9000 Android Development] Daemos:
Can we potentially use this kernal (with the right tools) to format the NAND in YAFFS2 instead of RFS? Then still have way of flashing firmware onto it?

If so, that would be awesome and it would seem to have the least draw backs.

Currently the A2SD lag fix requires an external microsd card, and the one click lag fix, mounts a EXT2 image ontop of the RFS NAND, and that could drastically affect NAND life.
[Galaxy S I9000 Android Development] Hyperion82:
This is great !!!

Thank you raspdeep and all the devs here, this is one step closer to a stable kernel and a permanent genuine solution for the lag problem as far as a n00b like me understands :)

cheers !
[Galaxy S I9000 Android Development] mekwall:
Not if we can't mount the NAND as a MTD-device instead of STL-device.

Say what? /data/ is mounted on the internal SSD, not the NAND. /dbdata/ is however mounted on the NAND. Just do a df -h and you can see all the mountpoints.

Also, mounting and using a ext2-image that reside on an rfs-partition will not damage your drive. The rfs filesystem is still the one used to store the image itself (the ones and the zeros), even though you write it inside an image that uses another filesystem.
[Galaxy S I9000 Android Development] mekwall:
I stumbled upon these documents while Googling for STL-devices:

http://www.samsung.com/global/busin...y/downloads/LinuStoreII_GPL Compliance_10.pdf

http://www.samsung.com/global/busin...ionmemory/downloads/RFS_130_Porting_Guide.pdf

I haven't had the time to read them through yet. But if there's a porting guide, there must be a way to reverse it ;)

Go go reverse engineers!
[Galaxy S I9000 Android Development] woeds:
Is it really necessary to format the NAND with another filesystem? /dbdata seems fast enough as it is. Wouldn't it be enough (and easier?) to only convert the internal SD to yaffs2?
[Galaxy S I9000 Android Development] darksnarfer:
Quote from someone that knows a lot more than I do:

http://twitter.com/wesgarner/status/20805997718

So right now we have /data that is mounted in the second partition of the internal sdcard (mmcblk0p2), where all the critical files are stored (data, dalvik-cache, etc..) but we can't use yaffs2 there because it's not MTD.

We could, however, format and mount the other partitions (/system, /dbdata, /cache, etc...) with yaffs2, but that might not help because there isn't many heavy read/write there. And we should figure out how to make the kernel see them as /dev/block/mtdblock* instead of /dev/block/stl*.

rasdeep, can you share the .config for the kernel you used? I managed to get some mtd devices (atleast in /proc/mtd) but they were virtual devices. Maybe we need some more options enabled in the kernel.

Also, anybody knows why there are /dev/block/stl* and /dev/block/bml* they seem the same though.
[Galaxy S I9000 Android Development] igniztion:
According to http://www.samsung.com/global/busin...ducts/fusionmemory/Products_XSR_Brochure.html

STL and BML are independent layers for managing I/O to the NAND devices

STL manages the sector translations while BML manages the invalid blocks (whatever that means)
[Galaxy S I9000 Android Development] Chainfire:
Did any of you notice that in init.rc there are many references to yaffs2 ? Perhaps in engineering Samsung did use it ?
[Galaxy S I9000 Android Development] darksnarfer:
Yeah, I think they are just android standard (maybe they took them from a template) and commented to use their better(?) filesystem.
[Galaxy S I9000 Android Development] woeds:
Ok, so what filesystem does the internal SD use currently? Would it help if we change that to EXT4? That would emulate the current mimocan fix, but without having to use an external SD card.
[Galaxy S I9000 Android Development] mekwall:
I don't think we should stare ourselves blind on yaffs2 support.

The best working lag-fix so far has nothing to do with the NAND but with the internal SD. We should be looking at replacing the internal SD's file system from RFS to ext2.

Lately i've been reading up on SD-cards and file systems and come to the conclusion that ext2 is the best choice. yaffs2 is engineered for NAND-drives and should not be used for SD-cards. We already got the tools to create, mount ext2 partitions so we just have to find out how to replace the internal SD-partitions.

An idea is this:

* Create temporary partitions on external SD-card and remount these to replace the internal SD-card mounts

* Unmount the internal SD-card and reformat the partitions to ext2

* Redo the first step but the other way around, kinda...

I dunno if we will be able to unmount the internal SD partitions while the device is running, but it's worth a try. Otherwise we will have to use some kind of recovery image with access to busybox to be able to do this.

After we've managed to replace the file system on the internal SD-card we can see if there's a solution to replace RFS on the NAND with yaffs2.
[Galaxy S I9000 Android Development] woeds:
But doesn't ext2 have problems with possible data corruption?
[Galaxy S I9000 Android Development] darksnarfer:
You can't unmount anything used while running android, this should be done from recovery.
[Galaxy S I9000 Android Development] mekwall:
SD-cards themselves have problems with possible data loss if there's a sudden power loss, but they also have their own protection against it. The risk of corruption by using ext2 is exaggerated to say the least. ext2 have been successfully used for a long time before journaling file systems saw the day.

I remember when I was playing around with my old linux machine at home. I used ext2 for a long time, and never ever did any corruption occur even though I was treating it really bad. Forced shutdowns, kernel panics etc. I never lost any data.

Also, ext3/4 have many other features that are useless and can degrade both performance and life of your flash drive. So, do you really care more about lowering the risk of data loss by a couple of percent then you care about performance and life expectancy of your flash drive?

From Wikipedia on ext2: "ext2 is still the filesystem of choice for flash-based storage media (such as SD cards, and USB flash drives) since its lack of a journal minimizes the number of writes and flash devices have only a limited number of write cycles."
[Galaxy S I9000 Android Development] mekwall:
So we need a recovery image that can run busbybox through adb. ;)

Any takers?
[Galaxy S I9000 Android Development] Axusuxa:
but if insert a script in init.rc.a convertion process can be done during boot android.
[Galaxy S I9000 Android Development] Daemos:
Shouldn't we be focusing on external cards then? At least external cards can be replaced. I'm not too sure how easy it would be to replace the internal SD card.

The one click lag fix makes a virtual ext2 partition on the internal SD card right? Hmm...but I thought it also affects the NAND, that's my bad. I'd still rather have it on an external card than an internal card as it makes it much easier to replace.
[Galaxy S I9000 Android Development] darksnarfer:
Actually samsung's recovery can run busybox fine.

I tried my method. Compiled a kernel with ext2/3/4/yaffs2 support and modified /init.rc to mount /data with ext2 instead of rfs. Booted to recovery, mounted /data, backup with tar, unmounted, formatted /data with ext2, mounted back, and restored all files from tar.

The partition seems to mount/unmount fine from recovery, but when using my kernel it freezes at boot (when the samsung logo). I don't know what I've done wrong, or if my initram is correct, but I'm stuck right now.

Does anybody know where I can look for logs before adb logcat starts up? Kernel log / dmesg is saved somewhere?
[Galaxy S I9000 Android Development] woeds:
Exactly, which brings us right back to mimocan's lagfix, which is already out (albeit in ext3/ext4 form instead on ext2)