yashsingh1/xdaforums huggingface dataset:
[HTC Excalibur] somecuitears:
according to my personal experience it is because ur battery is not holding charge any more... it happens with most of the batteries..i had same problem. my battery would require 5 to 6 hours to charge and it would b empty with in 1 hour..it was in the beggining later my battery would not even open my phone without connecting it to AC adaptor.. So you can now buy a new battery.. increase the life of ur battery by doing following things:

* when u buy ur battery charge it to at least 8 to 10 hours

*do not use ur device when it is charging.

*do not use Internet sharing with ur new battery.

*do use ur old battery if u r sycn ur device with PC for long period of time.

* Use Omap clock to reduce the overclocking.. it provides bit long battery life..

hope this helps...
[HTC Excalibur] zackwz:
Thanks. Where would be the best place to buy the battery?
[HTC Excalibur] somecuitears:
search for "extended battery for htc s620" or "batteries for htc s620" on amazon.com or ebay.com...
[HTC Excalibur] zackwz:
Thanks. there are batteries for $2+$3 shipping or $9+fs. Hmm, decisions... Should i trust these?
[HTC Excalibur] tobbbie:
Why don't you measure the capacity of your batteries? It is easy - lookup the thread in my signature.

For the Excalibur the battery drain with full lit display (all radio parts off - keyboard lights off) is 98mA. So roughly 10 hours will it last until the battery is flat. I had measured 2 different batteries in my device and their data has produced the attached chart in Excel.
[Galaxy S I9000 Android Development] supercurio:
Hi there!

First, i probably need to reassure people who were scared by my posts: no there is no risk this corruption makes your phone die. It"s just about the state of the filesystem.

So, what triggers the corruption ?

Mounting any RFS filesystem without check=no

How is the filesystem corrupted ?

There are several symptoms:

Directory names gets CAPSED: Example: /system/bin becomes /system/BIN

files becomes unreadable, or directories becomes unlistable

user.log is created (seems it could be created in other situations)

Unfortunately, these errors are random.

I made previously an attempt of auto-detection + correction for Voodoo lagfix but didn't succeed because the filesystem errors seems to vary at each mount.

The more you write on a non-check=no mounted RFS, the more the corruption grows.

This is valid not only for /system but for any RFS.

I use a kernel which you say creates corruption but everything works! Are you a big fat lier who wants me to use Voodoo instead?

Hehe, I read that :D

Lots of things are strange about RFS and i hit several bugs during Voodoo 5 development, which is able to converts /system back to RFS

This is just another example of an RFS inconsistency. Why the hell should all filesystem be mounted only with -o check=no ?

Good question, this is absurd ^^

However, a RFS filesystem mounted without check=no stay usable as long as you continue to mount it without check=no. This is why sztupy and a lot of people didn't noticed it.

But I'm sure a few people had the issue after re-flashing another kernel and thought they made a mistake.

Official Samsung kernel don't boot, or boot but the /system has errors. Missing media files (sound?) or binary ? Yes, this is the cause.

Is this corruption report your personal interest ?

Yes, because it prevents migrating from an old ULF kernel to a Voodoo kernel.

But it's also the case with every other kernel except ULF based ones (not corrected in git ATM)

I lost a lot of hours because of this issue ^^

You know, it's just a bug. Needs to be corrected, that's all.

If the filesystem works fines on ULF kernels, why call this corruption?

Because it only mount properly on ULF kernels.

It does not work on every other including official Samsung ones.

Reaction of hardcore, Speedmod kernel's author:

In second post: how to correct the issue.

Big thanks to lots of people that took time to send the log helping understanding this issue during the development of Voodoo.
[Galaxy S I9000 Android Development] supercurio:
Howto correct the /system RFS corruption issue

2 methods available

And mine:

Okay!

My fully-automated solution attempt is ready.

Backup first.

Introducing Voodoo /system RFS fixer

Download: http://project-voodoo.org/downloads/voodoo-system-rfs-fixer-kernel-2.tar

Flash without repartition.

What does it do?

This kernel boots and detects current filesystems.

- If there is a RFS /system, this filesystem will be mounted with corrupted-compatible mount options

- A internal backup to the sdcard is made

- /system is formatted as RFS with fat.format using adequate parameters

- the backup is restored on the fresh /system mounted with correct options

After that, your all refreshed /system should free from corruption (if the source /system was)

Do I need this fix ?

If you plan to continue using the same kernel without changing in the future, no. Forget about it.

If you use an ULF-based kernel except Speedmod kernel from hardcore starting with K9, you should consider it before switching to a standard kernel.

The latest Voodoo lagfix converts /system as Ext4, that's why it's sensible to /system corruptions. But maybe you would not notice by yourself some missing media file or a strange crash because a lib was corrupt.

Is it 100% reliable?

Unfortunately it's not, and it cannot. I have reports of a small % of failures, that's why i don't recommend running it if you don't need it, and also doing backup of your /system if there is something interesting here.

Is it a lagfix?

No, it's based on Voodoo lagfix code but not a lagfix.

You cannot use it as a real Kernel, the conversion RFS<->RFS is run at each boot.

How much time does it take?

About 3 minutes with a standard system. Smaller roms takes less time.

You'll hear step1 step2 and it will boot.

3 minutes? nope, it takes forever

Sorry, this automated fix is unable to repair your /system.

Now you can try another method or quick: flash a stock kernel.

Are my personal data modified?

No.

Only /system is modified.

If something goes wrong, you can simply reflash a ROM or only a system using Odin.

Are my personal data modified?

What about backups ?

You can make/restore backups booting into recovery.

Default recovery is CWM Recovery, and when you boot in recovery there is no conversion involved.

Standard boot triggers the conversion/un-corruption.

I have a problem

This is young code. Tested but still young.

You can help by sending or joining your sdcard/Voodoo/logs directory zipped here.

Full source of the solution used :

https://github.com/project-voodoo/lagfix/tree/system-rfs-fixer
[Galaxy S I9000 Android Development] dckiwi:
Damn it... I've been CAPSED!
[Galaxy S I9000 Android Development] supercurio:
/system # ls
ls: ./FONTS: No such file or directory
ls: ./MEDIA: No such file or directory
ls: ./XBIN: No such file or directory
ls: ./APP: No such file or directory
ls: ./USR: No such file or directory
ls: ./ETC: No such file or directory
ls: ./firmware: No such file or directory
ls: ./BIN: No such file or directory
ls: ./user.log: No such file or directory
build.prop default.prop lib lib

Trying to restore a CWM backup from a non-corrupting kernel don't work.

The RFS /system needs to be reformatted entirely.

A few minutes later:

ls -l
drwxr-xr-x 1 root root 0 Nov 23 00:40 APP
drwxr-xr-x 1 root shell 0 Nov 23 01:07 BIN
drwxr-xr-x 1 root root 0 Nov 23 01:00 ETC
drwxr-xr-x 1 root root 0 Nov 23 00:39 FONTS
drwxr-xr-x 1 root root 0 Nov 23 00:39 MEDIA
drwxr-xr-x 1 root root 0 Nov 23 00:40 USR
drwxr-xr-x 1 root shell 0 Nov 23 00:39 XBIN
-rw-r--r-- 1 root root 1956 Nov 23 01:10 build.prop
-rw-r--r-- 1 root root 0 Nov 23 01:10 default.prop
drwxr-xr-x 1 root root 0 Nov 23 00:40 firmware
drwxr-xr-x 1 root root 0 Nov 23 01:10 lib
drwxr-xr-x 1 root root 0 Nov 23 01:10 lib
-rw-rw-rw- 1 root root 552 Nov 23 01:00 user.log
[Galaxy S I9000 Android Development] supercurio:
After formatting system in official CWM:

~ # ls system
ls: system/lib: No such file or directory
[Galaxy S I9000 Android Development] supercurio:
I think i'll build a custom kernel using Voodoo 5 guts to repair /system ;)
[Galaxy S I9000 Android Development] gpnda:
Hmm so there is no way to fix it beside a complete reflash?:(
[Galaxy S I9000 Android Development] supercurio:
Not yet.

My current recommendation is :

- make a CWM backup of your running working without problem system

- flash a stock firmware

- flash a non-affected kernel with CWM support (K9, Voodoo 5 snapshot)

- restore
[Galaxy S I9000 Android Development] betoNL:
Ok.. I got lost over there.....too many posts per hour or shall I say , per minute?

@ SUPERCURIO...

I flashed SpeedMod K8 300hz 341 MB ram this morning and evrything is working pretty fine .... iGo Motonav voice instructions dont stutter anymore. Wifi , Games, evrything smooooooth.

But about the file system corruption thing:

I didnt apply any lag scheme, only the tweaks...That means I am safe right?

Or those extra 40MB Ram took some bribing as well??

Hardcore brought up the K9...what's different? changelogs? details??

Thanks in advance....

Btw.....is there a tweak to improve sgs's FM sound quality?;)
[Galaxy S I9000 Android Development] jjwa:
My personally preferred alternative method (because it's all in CWM :P).

- make a CWM backup

- Use CWM to format .system & wipe the dalvik-cache.

(You may need to unmount /system before it can format /system)

- flash a non-affected kernel with CWM support (K9, Voodoo 5 snapshot)

- use CWM for Advanced restore -> system [/QUOTE]
[Galaxy S I9000 Android Development] DamianGto:
I don't us that initramfs in my kernel. I hope that would be safe then.

But i get some question that people can't leave speedmod kernel and flash my kernel. It won't work, but if they flash back speedmod kernel it works. Maby it something else..

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
[Galaxy S I9000 Android Development] betoNL:
Never mind, got some answers already. I disabled all tweaks, wiped dalvik cache and flashed K9 300hz....

« »
[Galaxy S I9000 Android Development] specialex:
user.log is created in /system

so i need to reflashing to stock rom and use K9 kernel, right?
[Galaxy S I9000 Android Development] lpy:
Refer to FM discussion thread http://xdaforums.com/showthread.php?t=709599
[Galaxy S I9000 Android Development] fuze_freak:
Ok so I notice that I have the "user.log.old"

everyone is talking about user.log but mine says "user.log.old" what does it means?

update: I checked the day in the details of that user.log.old and it says november 22, 2010 yesterday....

update2: I have the user.log also

another question can I instal k9 without flashing a stock ROM, just on top of doc's ROM ?

thanks

user.log content

----------------------------------------------------------------------------------

mount: mounting none on /acct failed: Device or resource busy

mount: mounting none on /dev/cpuctl failed: Device or resource busy

/sbin/post-init.sh: cd: line 219: can't cd to /sbin/init.d

Mon Nov 22 10:45:05 AST 2010 USER EARLY INIT START

Mon Nov 22 10:45:05 AST 2010 USER EARLY INIT DONE

Mon Nov 22 10:45:05 AST 2010 USER INIT START

Mon Nov 22 10:45:05 AST 2010 USER INIT DONE

mount: mounting /dev/block/stl9 on /system failed: Device or resource busy

----------------------------------------------------------------------------------
[Galaxy S I9000 Android Development] Adevem:
never though that my "not applying of lagfixes" since froyo, will come such a long way! lol.

glad to know my /system is safe.

edit : well just found that there's -

/system/user.log

/system/user.log.old

does that mean my /system is corrupted? i don't see any unusually caps'd folders. i guess the only way to find out is to flash voodoo/speedmod k9, hmm...
[Galaxy S I9000 Android Development] hardcore:
user.log created in /system does not always mean your /system is corrupted. Backup first, then try K9, hope it works. If it boots you should be fine (maybe have to reinstall superuser).

But if it doesn't boot with K9 it means your /system is corrupted enough.

Then you should try the procedure u mentioned -flash stock ROM/PDA and then K9.
[Galaxy S I9000 Android Development] roxaim:
i got user.log.old on /system

but I already flashed to k9, so i guess my /sistem not corrupted ?
[Galaxy S I9000 Android Development] hardcore:
For kernel makers: If you don't wan't to edit the initramfs yourself, here is the initramfs I use for SpeedMod K9.

It fixes the /system mount, and also updates ULF to 0.4-pre, and has bootanimation support.

Be careful if you use it though, a lot of users from older ULFK-based kernels will not be able to boot from the new mount options, but it should prevent future corruption of /system.
[Galaxy S I9000 Android Development] supercurio:
I'm testing the /system RFS fixer special kernel.
[Galaxy S I9000 Android Development] jimpsar:
Hello,

I ve darkys 4.1

Tried to apply this fix though odin but odin stayed at initialization for 20mins

As nothing happened i took it off usb.cant boot cant enter recovery.there is an icon of phone and pc showing only with exclamation mark

I can enter download mode but doenst proceed furher to initialization.

Can u plz help??What can i do?

Thank you
[Galaxy S I9000 Android Development] andyhan:
The fix doesn't work for me. My device stop after Step 2 for over 30 minitues.
[Galaxy S I9000 Android Development] kalpik:
People on Doc's ROM can follow these instructions: http://xdaforums.com/showpost.php?p=9388152&postcount=8896

You will not loose and data/apps and you won't need Odin :)
[Galaxy S I9000 Android Development] dckiwi:
Edit: deleted my earlier comments as they are not helping the situation. Sorry if I offended you (or anyone).
[Galaxy S I9000 Android Development] pele78:
Deleted as serves no purpose but only to further distant from the topic which is not good lol

No hard feelings :)

Sent live and direct using XDA APP, from my GT-i9000, United Kingdom, GMT+0.
[Galaxy S I9000 Android Development] pele78:
Mate we all fly off the hook sometimes, were only human. Its just a frustrating situation that's all and even more frustrating for those trying to help those who really need the help.

I think things are starting to be resolved now.

No hard feelings :)

Sent live and direct using XDA APP, from my GT-i9000, United Kingdom, GMT+0.
[Galaxy S I9000 Android Development] jimpsar:
anyone plz??

EDIT:Reinstalled Kies .flashed K8 kernel and everything works now!
[Galaxy S I9000 Android Development] madfix:
Why K8 ?

Almost every posts here told you to flash K9.

Kalpik has posted this workaround, also working for Darky's Rom.
[Galaxy S I9000 Android Development] pele78:
Edit

Lol nvm, a had a dumb moment then

Sent live and direct using XDA APP, from my GT-i9000, United Kingdom, GMT+0.
[Galaxy S I9000 Android Development] j0ep0:
Thanks for the advice, but it didn't help. My phone was bricked after flashing this fix. Didn't get into recovery or download mode afterwards, even the battery charging animation was hanging while I was loading the battery. I sent the device to Samsung for repair. The bricking of the phone was probably phone/hardware related. Samsung already informed the service centre about possible issues with upgrading trough Kies, so my guess is that flashing/upgrading in general is risky on the i9000. The service center was instructed not to repair the device, but replace the device with a new one. Unfortunately, there is a prcedure attached to this that is going to take about 2-3 weeks. That's a bit more waiting than the usual 3 days for repair.
[Galaxy S I9000 Android Development] Adevem:
I'm sure and hope if not, that Supercurio does not bother about them.

I'm not trying to suck up to anyone, I'm just saying; my phone is better than it was out of the box before, much better.
[Galaxy S I9000 Android Development] xdaShex:
Where do I download this K9 CWM? is the Download: http://project-voodoo.org/downloads/voodoo-system-rfs-fixer-kernel-2.tar the kernel the guides talking about ?

And one more question can someone explain how to "open terminal" so i can check if i really need to flash this fix :confused:
[Galaxy S I9000 Android Development] Goldie:
http://xdaforums.com/showthread.php?t=822756

Any of the bottom 3.

If you were on an older kernel based on ULF then you would need to fix. Either the way described with k9 and docs rom or with supercurios fix kernel.
[Galaxy S I9000 Android Development] sharky34:
where do you see that you are affected?
[Galaxy S I9000 Android Development] kraksen:
The missing check=no.

Or have i missunderstood?

*EDIT* Ahh.. after rereading, i understand now.. my system is not mounted as rfs, but ext4. Sorry. *EDIT*
[Galaxy S I9000 Android Development] kiwijunglist:
Seems to be conflicting statements, should be cleared up or explained more in original post.
[Galaxy S I9000 Android Development] Larteas:
Hi, I've Darky's too, with that steps, I'll loose everything in the phone?

Thansk in advance!
[Galaxy S I9000 Android Development] Larteas:
I've done this but using Darky's ROM and althought it boots i've lost everything I have installed...

How can I confirm that K9 Kernel was installed all right?

Thanks again
[Galaxy S I9000 Android Development] igniztion:
Cheers! This worked like a charm.

Had properly corrupted /system, but now back on Docs with K9 kernel and all apps/data/settings intact.
[Galaxy S I9000 Android Development] Goldie:
Settings ->About phone->Kernel version.

Should say k9 somewhere.
[Galaxy S I9000 Android Development] curl66:
my /system is corrupted,too.

explains some strange behavior of the phone. incoming call fails soemtimes.

but anyway, since i have nothing to lose i like to reflash the whole phone.

have done a titanium backup so i am fine with the apps.

is this the right way?

1) disable lagfix

2) flash a stock rom (repartition needed ?)

3) flash a custom rom from here including the kernel K9

4) do a wipe / factory reset ?

or is it ok to just flash a complete custum rom like Doc`s including K9 and do a wipe?

thanks!

special thanks to supercurio for sharing this information!
[Galaxy S I9000 Android Development] Gohst_oc:
Does anybody know which Lag Fixe's are "safe" / "unsafe"?
[Galaxy S I9000 Android Development] jjwa:
All lagfixes have risk. Both if you want the best chance for safety, I would personally recommend you to wait for the stable release of supercurio's Voodoo lagfix (www.project-voodoo.org). It should release somewhere between now and 2 days or so... (It is not the preview you can now see on the website.)
[Galaxy S I9000 Android Development] Gohst_oc:
Yes I just checked out Voodoo and z4mod Lag Fixes at Github.

They are both mounting RFS with check=no (so far I could see).

And another important question:

@supercurio:

You wrote in your first post, it doesn't matter to NOT mount a RFS partition without check=no if the partitions are always mounted this way.

So, per default, Samsung did mount /system

without

check=no.

But at the beginning you say, that mounting

without

check=no triggers the corruption.

So the big question: switching from RFS without check=no to RFS mounted with check=no does not trigger a corrupt FS?

But reversed it could be dangerous? Or what?

Or did I see a discrepance in your post or am I just stupid?
[Galaxy S I9000 Android Development] Phandroid:
Although I haven't been CAPSED I do encounter some strange behavior of my phone. My sms tone won't work. Could that be a warning?

Is there a safe way of telling wether or not the system is corrupted? Also, did I understand correctly that if I flash the K9, for instance, and the phone boots, than everything is OK?

Please give me a short feedback.
[Galaxy S I9000 Android Development] kasper_h:
I also had some strange behaviour after flashing k9. Backing up /system, formatting /system and putting back /system solved these problems....
[Galaxy S I9000 Android Development] Phandroid:
How can I backup and restore /system only? Please enlighten me!

Or maybe I could just CWM everything and then reflash everything back again? Think that might work, too?
[Galaxy S I9000 Android Development] reglaspv:
Quick question please :)

I flashed Friday through Kies, the latest version of 2.2 available official for my operator (JP7) over K9A.

In K9A i used No-RFS Advanced but before that, there wasn't another version of SpeedMod, just another stock kernel, JPA.

Today, suddenly, all my sound settings for calls, sms, mail are missing and the phone is using some random mp3 from sdcard.

There are no CAPS folders, no logs and because I want to use the final Voodoo today, I can't figure if I need to use the fix from this topic or this is some random bug which has nothing to do with the corrupt RFS system.

Please advice. Thank you.
[Galaxy S I9000 Android Development] supercurio:
Hi!

Yes, random or strange sound as notifications happens with missing resources, which means most times in my experience with broken /system.
[Galaxy S I9000 Android Development] compuse:
still no corruption after 2 and a half month(JPK), I did had some data-loss on the stock rom though; mail box empty and contacts missing, .. but no idea if that would have been a "corruption" of the fs too?

all system files still correct after 2 and a half month, maybe cos i've haven't pulled the battery, while operating, enough?

\Great work though and that you're not giving up this easily!
[Galaxy S I9000 Android Development] dogdayfear:
No way to make this work for me. :( :(

After STEP2 sound it hangs with the 'Galaxy S GT-I9000' screen.

Is there any workaround for this?

Thanks in advance.
[Galaxy S I9000 Android Development] KartofeLone:
Sorry for my noobish question, but I have doubts.

I am on stock XWJM2 and stock kernel, no lagfix, no root.

Can my filesystem be corrupted?
[Galaxy S I9000 Android Development] DamianGto:
99% no.

1% yes.

All system can be corrupted.

Stock kernel is very safe.

**Using my own kernel, z4mod, 342MB Ram and ext2 filesystem**
[Galaxy S I9000 Android Development] hensk:
is kernal "hardcore@speedmod-k9a-200hz#189" have implemented fix in it
[Galaxy S I9000 Android Development] zurchpet:
Yes. Every kernel >= K9 from Hardcore is fixed...
[Galaxy S I9000 Android Development] hensk:
10ks m8

but I already flashed .tar file via Odin

only to be sure sure ;)
[Galaxy S I9000 Android Development] dakine:
I'm confused; will flashing JPU with repartition checked fix this if I plan on wiping the device anyway, or is it necessary to flash this kernel first?

Thanks in advance.
[Galaxy S I9000 Android Development] supercurio:
YES ! :)

And that's an interesting side effect for this new release!
[Galaxy S I9000 Android Development] dakine:
Thanks for the lightning quick reply, now I can flash with confidence :)
[Galaxy S I9000 Android Development] Mykron:
Ok, now I am lost too and need some help on this.

I have Docs 7.6.2 JPO (kernal@kernalcompiler #4) and using NO-RFS advanced (all ext4)

How should I update to Doc's JPU?

My way would be:

1. backup with Titanium

2. disable lagfix

3. follow instruction on the first post? (better use K10J??)

4. install DOC's JPU 4.0 nowipe

5. everything is fine and i have all my apps, contacs and kalender entries still on my phone

Would by very nice, if someone could give me a hint, if this is the correct way.
[Galaxy S I9000 Android Development] Mykron:
Nobody? Come on, have a heart!