yashsingh1/xdaforums huggingface dataset:
[TG01 ROM Development] dinhy34:
i use Eng ROM, i installed the htc keyboard i like but can i also install other versions? like Compact QWERTY, Phone keypad?
[TG01 ROM Development] mirolg:
htcKeyboard2.1 is one in all cab. All tree keyboards is installd. but you can´t select the others.

Install this two cabs (is im miROM9)

then you have to possible select QWERTY, COMPACT AND PHONE KEYBOARD
[TG01 ROM Development] dinhy34:
i believe the notification issue deals with the ROM since i uninstalled CHT...just running normal HTC SENSE and still no notification shows up in Sense bar, Wondering if you can make a version of miROM9 but with sense. or any 6.5+Sense+htc special
[TG01 ROM Development] mirolg:
yes. with this f.... htc messaging i lose my nervs, really.

miROM8/miROM9 as 6.5 ROM is good- but i have one bug in htc sense. I make on weekend a bug-free update.

BUT one i don´t understand. miROM8 is downloaded over 200x and no one give me detailed feedback- (only you)
[TG01 ROM Development] drupad2drupad:
I would love to leave you feedback for this rom as I am one of those who downloaded this and immediately removed and use some other rom.

the reasons I removed it:

1)it is hybrid rom - don't like the way it uses my memory

2)it is sense rom - problem with htc messaging gets on my nerves too, and there is issue with notifications as well -which basically stops all sense rom based phones -working as phones. you can't get notifications and cant send messages unless you go back to ugly winmo messaging!

3) after using miROM5 and miROM4 - all others roms for me are just roms loaded with looooooads of things and my phone feels very heavy to me! So I love miROM5 and flashed my phone back to miROM5 and waiting for ENG miROM9/10

Good work Miro, sorry couldn't give you much feedback on this particular rom, I hope the ones who downloaded it do come and give some feedback so that it helps you to improve this rom :)
[TG01 ROM Development] Kilihari:
Other Virtual Keyboards.

Hello my friends!,

I use many different virtual keyboards, but they all don't work anymore, only the keyboards that MIRO has included with this ROM seem to work. Especially CE-Star, my Japanese input program, I desperately need to know how to get it to work, I tell you first person who figures this out, I will buy a bottle of really good Japanese sake and ship it to you for free. Again, CE-Star runs on all ROMSs except for MIRO's ROMs, I really want to use this ROM, so I am hoping someone can help me. I don't want to push MIRO too much, he is such a nice person and I don't want to be bothersome so if someone can help me, that would be so nice! :D

-Kilihari.

CE-Star's Trail can be installed for 15 days, so testers who want to help me out can do so by downloading the program either from CD-Star's website located here

http://www.ce-star.com/products/CE-Star.php, or you can directly download the newest version of CE-Star from MegaUpload here http://www.megaupload.com/?d=9FTAZUE1.
[TG01 ROM Development] christianceval:
How to watch youtube in landcape mode????
[TG01 ROM Development] Kilihari:
I will send anyone an easy $20.00USD Dollars!

Hello my friends!,

Anyone helps me with this problem, I will send you 20 bucks :D and you will have my many thanks! I use many different virtual keyboards, but they all don't work anymore, only the keyboards that MIRO has included with this ROM seem to work. Especially CE-Star, my Japanese input program, I desperately need to know how to get it to work. Again, CE-Star runs on all ROMSs except for MIRO's ROMs, I really want to use this ROM, so I am hoping someone can help me. I don't want to push MIRO too much, he is such a nice person and I don't want to be bothersome so if someone can help me, that would be so nice!

Basically, I install CE-Star v2.8 R3c, and I will then select it from the sip menu, and a green keyboard should then appear, but it doesn't. I need to get that green keyboard to appear. Now, everything else works fine, like the keys are there, they are just invisible. I can type on my invisible keyboard but it is hard. I am sure this problem is relatively simple to solve, but it is beyond my skill level. Basically, CE-Star works, but the graphic that used to be the keyboard doesn't show up. So if anyone can get this and Swype working, I will send ya 20 bucks immediately!

-Kilihari.

CE-Star's Trail can be installed for 15 days, so testers who want to help me out can do so by downloading the program either from CD-Star's website located here

http://www.ce-star.com/products/CE-Star.php, or you can directly download the newest version of CE-Star from MegaUpload here http://www.megaupload.com/?d=9FTAZUE1.
[TG01 ROM Development] Lifthr4sil:
No T9 in miRom8 ...

Hi Miro, and all others,

finally i also give miRom8 a try i installed it yesterday and since then i nearly have no problems. But i got no T9 support for E-Mail, SMS, or anything else? All set up correctly but no wordst were sugested? Any hint? And BTW the link in your first post for the alarm fix is wrong can you correct it? I found the file in your miRom7 thread but im not sure if its right, manila_ring_alarm_fix.rar? And if yes what to do with the manila.exe (EDIT: ok found ... end Sense and copy to Windows folder, but that didnt change anything) inside to fix the bug? Hopefully someone can enlight me =)!

greetz Lif

P.S.: After set up the lock of the telefon i see in your first post it should be removed??? Is this true? I have no problem (until now with) the basic windows lockscreen??
[TG01 ROM Development] drupad2drupad:
Hi!

Have you tried this regedit - http://xdaforums.com/archive/index.php/t-358846.html

It might be that pre installed keyboard could be playing up. I am going to download the trial and see if I can test it on my miROM.

Update you soon.

Good luck
[TG01 ROM Development] drupad2drupad:
Have you tried installing any other keyboard? i.e. Resco/Toshiba/HTC? Some keyboards might struggle with T9 support. In miROM1, there is an HTC keyboard which works fine with T9 support. I am going to try alarm fix on my rom, so will update you soon if that works on mine (it's same cab install by miro).

The lock screen tip was only if following case is true:

You have winmo lockscreen installed (with pin lock) and you try to activate CHT lockscreen - this will make your phone unusable till you hard reset or flash your phone again. (it's incompatibility issue). This also happens when you have your CHT lock enable and then you install exchange settings that will enforce you to have pin lock - this will make your phone restart and you can never go beyond lock screen unless you pin flash the phone.

Good luck and will update you soon with alarm fix
[TG01 ROM Development] Kilihari:
Thank-you drupad2drupad ...

I will check this out right now, if I have success, you will be 20 bucks to the betta! :D hehehehe.

Thanks so much,

-Kili.

[UPDATE] Ok, so I did the regedit, I restored the original windows keyboard, it is now set to default, and the HTC keyboards are non-existent now, so I will install CE-Star and hopefully will have good news, will report back soon.

[UPDATE2] AWE, SO CLOSE but yet... no change... no green virtual keyboard. Keep trying, we are so close.. i can taste it hehehe.
[TG01 ROM Development] drupad2drupad:
Oh so sorry it din't work! I am surprised, this particular keyboard better be an awesome software, else it's too much hardwork! :)

I will update my results from test in a few minutes! :rolleyes:
[TG01 ROM Development] Kilihari:
If somone fixes my damn phone I will be your best friend, ... and 20 bux.

Man.... I am so frustrated... like .... if i bring up the old crappy windows virtual keyboard, then i bring up ce-star, which doesn't show a graphic, I can then type because the old windows keyboard has the same shape and dimensions as the ce-star keyboard, but .. it is a crappy work around.... i just can't understand how only miro's roms don't work with this keyboard, i just .... ahhhh going crazy.... between this and my stupid phone rebooting upon boot, cycling and then rebooting 2-3 times before loading up any rom, i am going to go crazy. But soometimes my phone is ok, but .. most of the time, it is not.

OHH i better goto sleep, i feel crazy.

-Kilihmessedup.
[TG01 ROM Development] drupad2drupad:
any chance of having this keyboard at .cab?

I am a linux user and can't run .exe as I don't have mobile device center to activesync my phone. The link you gave for megaupload has .exe file. I am struggling to open the other link,but hoping it might have .cab file!
[TG01 ROM Development] drupad2drupad:
Looks like you have done plenty of rom flashes on your phone. But I will still ask, when you flashed miROM did you do a hard reset immediately i.e. volume up+camera button+power button and then - yes, yes to next two dialogues?

This has solves maximum of my problems while flashing!
[Galaxy S I9000 Android Development] bilboa1:
Since I installed JPK on a test phone after claims that the RFS related lag has been fixed.. well.. I'd like to share my impressions:

- I have installed approx 100 apps after the flash (flashed / wiped / factory reset btw)

A this point, the phone while slightly slower than one with Voodoo is pretty fast

A few days later, it's still good enough.

- 5 days later, lag starts to be felt, and it's stronger every next day until it becomes annoying to use

That's exactly the same experience as I had on various Eclair roms without any lag-fix. I also had this on JP3 (early Froyo).

So yeah. I looked into the /init binary from samsung and it's supposed to make some file system checks from time to time when you restart the phone, but it does not appear to really carry on with that.

So I ran the checks myself:

- you need a rooted phone, and adb or a terminal

- find all RFS partitions:

$ su

# mount|grep -i rfs

- kill all processes, go flight mode and remount them read-only

$ su (if you're not root.. not going to repeat it again for subsequent commands)

# kill -9 <pid> of anything that use the patrition

# mount -oremount,ro /dev/block/....

- check the RFS filesystem and correct errors

# /system/bin/fsck_msdos -p -f /dev/block/....

Surprise, a million of RFS errors fixed such as:

/path/to/file starts with free cluster FIXED

Cluster XXX continues with cluster XXX in FAT 0 but is marked free in FAT 1 FIXED

Detected cluster chain loop head XXXX for p XXXX FIXED

FSNext block XXX is correct NumClusters XXX FIXED (weird one)

No LOST.DIR FIXED

Lost cluster chain at cluster XXX YY clusters lost FIXED (prolly lost files/data here!)

Repeat for each partition

reboot the phone at the end

SURPRISE! It doesn't lag much anymore.

Use the phone an hour, do the check again and you will see it's already full of errors.

Conclusion:

RFS is bugged (we knew that didn't we) but it looks like it's fixable, if ever Samsung figures out what is corrupting the file system exactly (it's closed source so we can't really find out easily)

It might be possible to figure it out by looking at VFAT sources too.

I would be very interested to see if that fixes the lag for everyone or if i'm an isolated case and all my RFS partitions are on bad hardware or if it's really software corruption as I am guessing

Small disclaimer:

im not responsible for any data loss etc. no warranties etc. fixing file system even readonly might cause data loss due to the bugs in RFS. you've been warned lol.
[Galaxy S I9000 Android Development] ragin:
My God,

I think a lot of eyes will be on the BOUNTY :)
[Galaxy S I9000 Android Development] INeedYourHelp:
Could someone just create an app that does this?
[Galaxy S I9000 Android Development] RyanZA:
VOLD is what does the RFS check at boot. It seems to run, although maybe it fails? It definitely does run though, you can check it running using 'ps' on phone boot. Maybe it's only cleaning up /sdcard though.

At any rate, running the disk check does help with speed, but it doesn't help that much. It's still slow. I think if you want to stick with RFS, you need to do a defrag as well as the filesystem check. After some use, RFS must be very very fragemented on most people's phones.

Even in perfect condition though, RFS still has some very nasty properties such as locking the entire disk when a write occurs, not doing buffering, etc etc.
[Galaxy S I9000 Android Development] RyanZA:
An app can't do this, since the app would have to be running off RFS and would crash/have to be killed to perform the FS checks. It could be done on boot using some trickery and the playlogos / replace binary trick. Or it can be done by replacing the init script with some kernel hackery. But at that point, you might as well just use a real filesystem. ;)

I guess a PC .bat file could be made that uses adb to do this for you and then reboot the phone... Doesn't seem worth the trouble though!
[Galaxy S I9000 Android Development] andrewluecke:
RFS is journelled. You sure the filesystem doesn't do the journaling properly?
[Galaxy S I9000 Android Development] dakine:
Nice job figuring this out. Is someone forwarding all these findings to that Samsung dev?
[Galaxy S I9000 Android Development] bilboa1:
It's not about RFS vs the other filesystems. I'm well aware of the performance of RFS. But it's decent enough when it's working properly. It's not nearly as fast as ext but fast enough that you don't get annoyed.

Thus fixing RFS would make the life of many people who aren't technically inclined better. If the RFS do get all corrupted everywhere, and Samsung figure that out and fixes it, it means a good thing for most people.

The rest of us will end up on ext anyways

And yeah I think the fscheck at boot fails, it must fail actually, i don't see how else it would happen.
[Galaxy S I9000 Android Development] RyanZA:
What firmware did you test on, btw? I've noticed that JPK does seem to take longer on the FS checks, so maybe they have it fixed already (doubt it though)?
[Galaxy S I9000 Android Development] bilboa1:
on JPK actually

im going to flash JM8 to see if its the same in fact, but i expect so
[Galaxy S I9000 Android Development] hardcore:
I think VOLD only does the checks for the Internal SD and External SD, not the RFS partitions.

Interesting find though, about the FS errors.
[Galaxy S I9000 Android Development] sargasso:
I’ve been wondering why the lag appears after a couple of days. I suspected corruption in one way or another myself, as it stays after a reboot it could not have been RAM and there are no signs of running out of space. Thanks for your research and I hope it will lead to new fixes. Sad but true my fix is to reflash my phone almost weekly.

I run Doc's JPK super slim ROM which is really nice but still it lags, even with OCLF installed.

Yesterday I take my phone out of my pocket to take a quick photo. My phone wakes up and I sweep the glass. Halfway through the sweeping the animation stops. I wait patiently for a second or three and there my home screen is. (No widgets, no animations, just a single home screen with 12 icons on it of the applications I actually use). I click on the camera icon and I wait another 5 seconds for the camera to realize it is not supposed to sleep on duty. I make a photo, the actual moment is already gone by now but hey I have the thing in my hand. It just takes another 5 seconds to store the photo.

It is like being in a hurry with a toddler with you. You want to go quicker but you can’t get angry cause the little thing just can’t go faster. It has to stop and wonder about life every once in a while.

I like my phone and I am sure it will grow up.
[Galaxy S I9000 Android Development] borchgrevink:
Very interesting findings! Sure hope Samsung sees this or this is forwarded to some Samsung techs.
[Galaxy S I9000 Android Development] dakine:
Maybe move this to the development forum then it might get more traffic from people that can actually help.
[Galaxy S I9000 Android Development] matty___:
do you really think Samsung is reading every thread here on XDA?
[Galaxy S I9000 Android Development] borchgrevink:
No need to be uppity my friend ;-)
[Galaxy S I9000 Android Development] RyanZA:
Some further info on possible RFS fixes here:

http://xdaforums.com/showpost.php?p=8445244&postcount=143

With the sync issue fixed, and corruption fixed with checks, RFS might just work 'okay'! It won't be as fast as EXT, but it should still work fine if we can sort out all the bugs! And we have a much better chance of getting Samsung to include these fixes in a new firmware too.

If we could get hold of Samsung somehow, and manage to convince them that they should

1) disable the always sync behaviour

2) do full filesystem checks at boot up (or provide a utility to do the checks)

then RFS should be A LOT more usable! :D
[Galaxy S I9000 Android Development] woeds:
Could someone perhaps turn this into a .bat-file?
[Galaxy S I9000 Android Development] bilboa1:
That quite right, I noticed the sync issue also.

As for the corruption, 2 things should be fixed:

- fsck from init should actually fsck the partitions properly on boot (we can sort of fix that by calling it in a script again)

- corruption should in theory not even happen so Samsung would have to work on RFS for that one :P

I ran JM8 for 2 days now and my rfs partitions are full of errors, like in JPK, just for confirmation if there needed to be one.

In fact it's still running fsck on /system as I'm writting and issues are filling the terminal .. its been running for 30s already lol :(
[Galaxy S I9000 Android Development] bilboa1:
I haven't tried that but it might be easier to enable adb over usb (in development settings) then .. make sure you are rooted, type that:

> adb shell

$ su

#

<prompt on the phone for root, click allow>

reboot into recovery

> adb shell

$ su

# mount -oremount,ro /dev/block/stl9

# mount -oremount,ro /dev/block/stl10

# mount -oremount,ro /dev/block/stl11

<for safety i'm not including stl3 it's the EFS)

if there's any error due to "filesystem busy" them stop there, it means it doesn't work :P

otherwise:

#/system/bin/fsck_msdos -p -f /dev/block/stl9

#/system/bin/fsck_msdos -p -f /dev/block/stl10

#/system/bin/fsck_msdos -p -f /dev/block/stl11

# reboot
[Galaxy S I9000 Android Development] woeds:
Doesn't seem to work
[Galaxy S I9000 Android Development] Hyperion82:
good job !

................................................................................................................
[Galaxy S I9000 Android Development] bilboa1:
Enabled usb debugging? I was pretty sure adb was started in recovery but I might just be wrong. As I said, didn't try it.

Instead you can just kill most running apps until it stops complaining (don't kill adb..) in "normal" mode as per first post
[Galaxy S I9000 Android Development] vM00:
No problems here, works just fine....I can confirm your findings bilboa1, there were a lot of errors.
[Galaxy S I9000 Android Development] woeds:
It's enabled. I can trigger reboot while in recovery through adb, but shell doesn't seem to work. I tried doing it while the OS is running, but even after killing a huge list of processes, the /dbdata partition is still in use.

[edit]

Nevermind, just had to wait 10 secs after booting into recovery :) found/fixed lots of errors
[Galaxy S I9000 Android Development] distortedloop:
I wouldn't be surprised if at least someone, unofficially, from Samsung peeks in here from time to time.

If not actual Samsung engineers, maybe those who are friends with or somehow connected and report back findings. I've always suspected that Richthofen is an actual Samsung employee or contractor...
[Galaxy S I9000 Android Development] g002ahe:
I cannot mount - when i try i get a message telling me

# mount -oremount,ro /dev/block/stl9

mount -oremount,ro /dev/block/stl9

Usage: mount [-r] [-w] [-o options] [-t type] device directory

Maybe someone can help?

Also I cannot navigate to stl9 using cd ( i can get as far as /dev/block of course)
[Galaxy S I9000 Android Development] TheNikkoMan:
Place a space between -o and remount on both commands. Love the direction this is headed :D
[Galaxy S I9000 Android Development] g002ahe:
Thanks but had already tried that -

# mount -o remount,ro /dev/block/stl9

mount -o remount,ro /dev/block/stl9

Usage: mount [-r] [-w] [-o options] [-t type] device directory

#

any other ideas?
[Galaxy S I9000 Android Development] RyanZA:
busybox mount -o remount,ro /dev/block/stl9
[Galaxy S I9000 Android Development] dakine:
I'm convinced that several members here work for Samsung.
[Galaxy S I9000 Android Development] edmondt:
I just want to modify the typo from the post, which works for me...

adb shell
su

(Hit Allow on the phone to Grant Superuser Permission)

- find all RFS partitions:

mount|grep -i rfs

I have the following:

stl9 on /system

mmcblk0p2 on /data

stl10 on /dbdata

stl11 on /cache

stl13 on /efs

reboot recovery

adb shell
su

I do this just to check what's available once more:

more /proc/mounts|grep -i rfs

Now do the checks and stuff... Which should be done every few days I think...

mount -o remount,ro /dev/block/stl9
mount -o remount,ro /dev/block/stl10
mount -o remount,ro /dev/block/stl11

/system/bin/fsck_msdos -p -f /dev/block/stl9
/system/bin/fsck_msdos -p -f /dev/block/stl10
/system/bin/fsck_msdos -p -f /dev/block/stl11
reboot
[Galaxy S I9000 Android Development] TheBeano:
I get "permission denied" at this point (after rebooting into recovery), which root mod are you using? I am using CF-Root kernel.

Here's a command you can use without rebooting into recovery or remounting to check for problems in all rfs mounts without changing anything:

busybox mount | busybox grep rfs | busybox sed 's/\([a-z0-9/]*\).*/fsck_msdos -p -n \1/' | busybox sh

I did get a lot of errors but they all seemed to be FAT mismatches, are we sure that rfs actually uses two copies of the FAT? I haven't seen many lag problems since I upgraded to JPK.
[Galaxy S I9000 Android Development] HelloH:
A closed-source filesystem that corrupts itself... I am coming from linux land, and I would recommend to FLEE, RUN, RUN AS FAST AS YOU CAN to ext2 or BTRFS (with it's native SSD support)... and never look back.
[Galaxy S I9000 Android Development] RyanZA:
You said it! :D
[Galaxy S I9000 Android Development] ashwinds:
LOL - i am convinced several developers here are doing Samsung's work - not quite the same as working for them :))
[Galaxy S I9000 Android Development] bilboa1:
BTRFS is not even stable, please don't use that yet lol. Rather use that unjournaled EXT2! Or just EXT4. For now at least.

Thanks for the typo corrections.
[Galaxy S I9000 Android Development] HelloH:
Please note, that some ppl here are performance addicts ;)

BTRFS is ok, as long as one does his homework (regular and automated backups). It is nowhere as stable as ext2 is tho...

So IMHO bleeding edge should be BTRFS (and almost everything here in xda is bleeding edge!!!!!), and yes, stable should be ext2 (as opposed to ext4, which - compared to BTRFS - is not YET optimized for SSD).
[Galaxy S I9000 Android Development] StNickZA:
+1

Any ideas? I can't mount the two /data partitions when the phone has booted.
[Galaxy S I9000 Android Development] ewok666:
What? You can't mount them at all or you cannot remount them ro?

I used the 2e recovery with clockwork mod but now I put the stuff into a userinit.sh script that is called from playlogos1 so it can run the check during a reboot without a computer required.
[Galaxy S I9000 Android Development] galaxoid:
I did the check for /cache and /system (stl9 and stl11) few days ago. My phone was starting to be very slow before doing this and surprisingly it seems to have helped. Could be also the reboot too but I did reboots earlier and I don't think I got this big difference.

JM7 rooted no lag-fix installed.