yashsingh1/xdaforums huggingface dataset:
[Droid X Android Development] Zaphod-Beeblebrox:
This created several problems for me.

First, the build.prop file is a read-only system file and doing a push did not work for me.

I had to copy it to my sdcard and then in shell:

su

mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system

cp /sdcard/build.prop /system/build.prop

mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system

reboot

This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.

When I activated wi-fi, it worked fine, and did let me into the market.

I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.

Update:

restored my build.prop and still no go.

update2:

tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.

I'm starting over with SBF, update, FROYO, etc.

I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions :)
[Droid X Android Development] elkniwcire:
Found a fix

I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
[Droid X Android Development] LexusBrian400:
Firstly, I figured ppl would know how to use adb.

if you cant push the file, use "adb remount" and it will work.

Secondly,

Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.

I posted over at another thread, and it worked for everyone.

Check it.

http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
[Droid X Android Development] titos1997:
yes this worked for me aswell thank you
[Droid X Android Development] thedimachka:
Yes this method definitely works. I have market working now and can search for protected apps etc.
[Droid X Android Development] LexusBrian400:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.

Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
[Droid X Android Development] thedimachka:
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
[Droid X Android Development] tx3kgtman:
I just used the root explorer meathod and now it wont boot.

I downloaded the file.

renamed my build.prob to build.prob/bak

placed the new build.prob in the system folder

rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back

Edit Delete Post: Im just retarted haha .prop not .prob :/
[Droid X Android Development] GotChanged:
Could you plz give us some details on doing this with root explorer. Thanks

Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
[Droid X Android Development] Zaphod-Beeblebrox:
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.

While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.

Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?

As for the Eris file, I did download that and all seems to be OK right now.
[Droid X Android Development] Tim.Smith:
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
[Droid X Android Development] zanix:
Yes, it requires an edit to a file that you can only be edited when rooted
[Droid X Android Development] inzandity:
This works for me...thanks!
[Droid X Android Development] LexusBrian400:
OP has been updated with original build.prop
[Droid X Android Development] will2live:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
[Droid X Android Development] LexusBrian400:
Just use the non-stagefright one.

Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop

Use the =false version for better stability.
[Droid X Android Development] will2live:
Thanks for the reply.
[Galaxy S I9000 Android Development] ykkfive:
I know that many people worry about frequent reads/writes will damage the NAND, so I began a new test days before without using the NAND

this time, I switched from rfs to ext2, with some mods to the kernel to load the ext2 partitions, no OC

note that this is only serve as a real case to show u ext2's performance and to prove that rfs is one of the problem areas. u guys can implement it your ways with further improvements, perhaps with ext3, ext4, yaffs, etc

EDIT: 21AUG 2018HKT

- some ppl said that it is easy to cheat the score obtained in quadrant by moving around the quadrant's data files. yes, i agree that. but it wil be much easier to edit it in photoshxp for even 30k score. and although some ppl said the score itself is meaningless, which i agree with it also, but it provides a mean to let u know how ur phone is performed. it is not an indicator for whether ur videos or sounds can be played smoothly since it depends on a lot of things as well

- also note that if u formatted the /sdcard in different file format, some of the recovery mode functions wont work since it will only mount rfs/vfat, so u have to modify the stock recovery or rom manager's recovery manually, or by mounting the partitions via shell
[Galaxy S I9000 Android Development] daijirok:
so this will lead to a whole new type of lagfix?
[Galaxy S I9000 Android Development] toca79:
So this is the base for the ultimate lagfix?
[Galaxy S I9000 Android Development] ykkfive:
well, I dono. let you guys decide
[Galaxy S I9000 Android Development] mbr01:
Nice to see the score split up in the different parts. It shows that the inital I/O of GS wasn't really that bad. Also i guess we can expect about 750 points of CPU score with Froyo (looking at the Nexus), so maybe a 3000 score is within reach :).
[Galaxy S I9000 Android Development] ykkfive:
i dono think so, more to come i think
[Galaxy S I9000 Android Development] ykkfive:
right, i saw one with 27xx or something already with old tricks. so 3000 should not be a problem with 2.2
[Galaxy S I9000 Android Development] toca79:
Great work anyway!!
[Galaxy S I9000 Android Development] g00ndu:
ykk_five, first, many thanks for the tip. The score of 2711 was done during your first initial suggestion, where the fix was temporary. In additional, I happen to have the overclock kernel (by raspdeep) installed. Hence, I just ran it to see how much mileage we can get from the SGS.

Having said that, RyanZA and Chainfire had implemented excellent lagfixes. With your latest test, I'm really not sure how much more improvement we can get. Many of us are now very happy with what they have, and I am not sure if there are anymore juice to be squeezed out from this.

Let's hear it from the more experienced users, and perhaps this latest discovery might be as exciting as your first. :)

Greetings from Singapore. :)
[Galaxy S I9000 Android Development] ykkfive:
thx a lot, i really hope that u guys will enjoy it!
[Galaxy S I9000 Android Development] Frostfree:
I have a consistent score of 990+ without any lag fix on a froyo ROM. Previously I used a lag fixed JM5 which score 2000+, however with everyday use the froyo ROM seems snappier. Good to see all efforts to speed things up and eliminate the lag, but I'm not sure higher benchmarks score translate to a better user experience.

What I'm hoping for now is a fix than enables smooth scrolling of contacts & call logs seen on the desire.

Good work though!
[Galaxy S I9000 Android Development] ykkfive:
u can compare the IO stat, although it's a roughly comparison
[Galaxy S I9000 Android Development] toca79:
This kind of solution should be a lot better as it doesn't use any space (or so i undertand).
[Galaxy S I9000 Android Development] ykkfive:
pls read my newly added comments at the 1st page

EDITED 21AUG 2018HKT
[Galaxy S I9000 Android Development] bub181:
So what exactly did you do to get these new scores? Did you format the /data partition as EXT2 to get these scores?
[Galaxy S I9000 Android Development] fantacies:
I understand someone may not like to spend time to answer noob's questions. But what is the point to show just the Quadrant score and then tell others you have done something in this Development board? Should it be presented in a more technical way?
[Galaxy S I9000 Android Development] bub181:
Yes please give some more details on what exactly you did.
[Galaxy S I9000 Android Development] Tyxerakias:
I wonder if Froyo will bump this score even higher.

I just performed a test on the HTC Desire, with newly installed Froyo (2.2). On the scale above, it scores between the Nexus and the Droid, but closer to the Droid. What intrigued me is that the reason the score was lower than the Nexus, was the CPU score. The other colours were about the same as the Nexus One. The CPU part was still bigger than anything else (up to the 1/4 of the green part on the droid below it) but about 4/5 that of the Nexus. Sorry I couldn't post a screenshot.

Which is really weird, since the two devices share the same CPU. (are the reference scores accurate?)

EDIT: I tried running it again, and I got a higher CPU score this time, so now it almost matches the Nexus (up to 1/2 of the green part on the Droid) Overall score 1301. So scratch the above comment, I guess the reference scores are the highest you can get.

Now in the picture of the Galaxy above, the biggest part is the IO score, which is logical because of the modification, but the CPU score is very small. So assuming that Froyo will bump up the cpu part like on the Nexus and the Desire, we'll be looking one hell of a record score, right?

Has anyone with a JP firmware tried this lagfix?
[Galaxy S I9000 Android Development] OrionBG:
The better CPU scores on FROYO are due to the JIT Compiller! The JP firmwares Have JIT but it is not active still! Or atleast not to the point it is on the N1! I hope that the final firmware will have full speed.
[Galaxy S I9000 Android Development] distortedloop:
@ykk_five - I'm not really sure what NEW point you're making, but I love that you're still working on this!

Didn't we pretty much already know that rfs was the appaent problem with the i/o? You proved that early on as far as I can tell. Paul O and mimocan assumed it was slow hardware with their fixes, but you showed that a different fs fixed it on the same memory space. Some of us have been clamoring for a reformat of the internal rom space as the solution since you first posted your findings.

What I find more interesting is that the i/o on the stock SGS in Quadrant isn't that bad - it appears comparable to most of the other phones, except the Motorola Droid X! I wonder why it's so fast on that one.

My own earlier READ-speed testing done with reading a 200mb data file from the command line with the dd command showed that read speeds on RFS internal /data partition vs ext4 on sdcard partition were pretty close. Seems like RFS can serve up the reads pretty darned fast (Class 6 speeds or better). Well over 13Mb/s from my post over on Modaco:

BEST SPEED ON EXTERNAL SDCARD EXT 4 = 15.79 MB/S
BEST SPEED ON EXTERNAL SDCARD FAT32 = 15.6 MB/S
BEST SPEED ON INTERNAL SDCARD FAT32 = 13.1 MB/S
BEST SPEED ON INTERNAL ROM AREA = 13.6 MB/S

Since we're now doing the loop mount ext2 on top of RFS fix, I thought I should test the read speeds there. I ran four tests, they ranged from 1.1MB/s to 8.1MB/s:

BEST SPEED ON LOOP MOUNTED EXT2 /DATA/DATA = 8.1MB/S

That's right, it's 50% SLOWER to read files off the ext 2 /data/data partition (with RyanZ's 2-3 method) than just raw RFS on the best read, 1/13th of the speed in some cases!

Seems hard to imagine how this fix speeds things up other than cacheing writes, which shouldn't impact the opening of files, unless the lag in the first place was some sort of delay reading the files while other things were written to the disk.

With that in mind, apparently the Quadrant speedup is in the WRITE part of the i/o tests, wouldn't you agree? That would be because of the cached writes ext2 does vs RFS?

If this is the case, then high Quadrant scores aside, none of these fixes should really do much to improve the normal look and feel of using the phone, as you alluded to with your comment about playing back videos/music. RFS or ext will serve up the data at more than we need it.

It makes me wonder why so many of us assert that the phone is indeed much snappier on opening apps and stuff. I'm sure it's not a placebo for me, the phone definitely feels faster with any of the lag fixes we use.

What we really need is to see a breakdown in Quadrant's i/o benchmark that distinguishes between the read and writes.

I really don't like that with all these fixes, no one really knows why they speed the phone up.

I'm tempted to go back to just stock JM5 and see what happens.
[Galaxy S I9000 Android Development] andrewluecke:
Speeding up I/O might reduce the problem. But because your benchmark shows the Nexus one has lower stats and doesn't suffer lag, then the Galaxy S shouldn't either.

So, once again, what is ACTUALLY needed is profiling tools to look at the system environment. Because there is probably something else dodgy going on..
[Galaxy S I9000 Android Development] distortedloop:
Makes me wonder if morfic's more on the right track with his scheduling theories.
[Galaxy S I9000 Android Development] ykkfive:
yes, sdcard as well
[Galaxy S I9000 Android Development] ykkfive:
same reason for my 1st trick, I don want ppl just follow my steps to do it since, unless u know what u r going to do, i do not recommand u to do it in command line urself coz even a typo may brick ur phone

therefore, I'd rather leave it to the experts here to provide painless solution for u guys, if they think this mod is useful.
[Galaxy S I9000 Android Development] ykkfive:
what i want to show is, even without the need for ext-sd or nand, ext2 alone should be good enough, and this should fit those worry about freq nand accesses and those prefer the ext-sd to be portable

but of coz, ppl differs and have different explaination in what is "good enough"
[Galaxy S I9000 Android Development] RyanZA:
Nice testing! :)

The results were pretty obvious before you did the test though, if you stop to thank about it! ;)

With EXT2+RFS, when you are doing a large file read, you are requesting a file from EXT2, EXT2 then requests the file from the loopback interface in the kernel, which when requests the file from RFS, which then gets the file from the actual disk. All data is then piped back through all these layers, lowering throughput a lot!

As a side note, trading EXT2 for EXT3/4 makes this a lot worse, since EXT3/4 is much much heavier than EXT2.

So why does the EXT2 make everything on the phone seem faster? RFS blocks ALL read/writes whenever a write is being done. RFS does zero buffering at all! So if you change your test to doing the following:

5 threads. 4 threads are reading, 1 thread is writing. You will see that whenever the 1 thread is writing anything, the other 4 are starved completely when running on RFS. When running on EXT2, the other 4 threads will be able to read a bit.

This 5 thread example is a far better indicator of actual phone use, than simply reading a large 200mb file. (Unless you dropped your phone to single user mode, and didn't write any data while reading -- which is what FAT32/RFS were originally designed for with DOS. Obviously, an Android phone is nothing like this.)
[Galaxy S I9000 Android Development] ykkfive:
agree, fat/rfs are old fs, and should not be used on todays' hardware, not limited to android
[Galaxy S I9000 Android Development] vitalij:
So to summarise, you have formatted /data partition as ext2. And modified some initialisation files to load it as ext2.

Am I right? And have you reformatted /dbdata as well? How the phone feels after that - are lags completely gone?
[Galaxy S I9000 Android Development] ykkfive:
i did not reformat dbdata (keeping nand intact), i also reformated internal sdcard

about the lag thing, as i said, it depends on how u define it. for me i didnt see any lag so far, even i kept forwarding/backwarding when i played a mp4 movie
[Galaxy S I9000 Android Development] ykkfive:
and, again, this is "just a test" demonstrating that no nand nor ext-sd is not a must for lag fix
[Galaxy S I9000 Android Development] xan:
Well thats great, but u being so mysterious about all of that.

The REAL lagfix would be wiping RFS part from our devices and replacing it with EXT2 (or higher - comparison tests needed).

One of major drawbacks when using current lagfixes is flushing buffers to RFS, which creates lag. This happens for example when u install an app through market. My device suffers severe lag after downloading and installing large apk file (around 3-5secs/1mb). I believe it is related to flushing buffer to RFS.

Guess flushing our 'buffer' is:

1) CPU and I/O expensive

2) RFS limited ofc.
[Galaxy S I9000 Android Development] sunwee:
is this similar to what is being proposed by Supercurio here - http://xdaforums.com/showthread.php?t=761537

same question, why don't you consider using YAFFS2 (also used in Nexus one)? there must be a reason why google themselves chose this FS for their flagship (now became developer) phone.
[Galaxy S I9000 Android Development] ykkfive:
just read that post, a new one posted today

yes, very similar, but he try to use ext4 instead

the reason for not using yaffs2 is, i couldnt find one for i9000
[Galaxy S I9000 Android Development] ykkfive:
yes, i did wiped the rfs and reformated with ext2, for /data and /sdcard
[Galaxy S I9000 Android Development] distortedloop:
Excellent description of what's going on. The results weren't obvious to me before starting, but that's because you guys are working on a level I've not yet reached! Thanks for the education. :)

I posted some information in the mimocan thread about the logcat of the phone during a shutdown. I'm curious how we can be sure the ext2 on the loop is being cleared before the phone cuts power. Is it just automatically done so as part of normal housekeeping, or part of clearing the caches in RFS?
[Galaxy S I9000 Android Development] distortedloop:
Agreed, kind of annoying that the sdcard on all Androids is FAT32 to begin with, it prevents us from using symlinks on the i9000 to send stuff that's hardcoded by apps to /sdcard to the external sdcard...

Question re: formatting the /sdcard as ext2: Does this impact mounting the sdcard on your computer at all? Won't this prevent non-linux OS from mounting the /sdcard on the computer? I don't use Windows, but I'd be surprised if it can read ext2. I know Mac users would need to install Fuse or another Ext2 filesystem extension.
[Galaxy S I9000 Android Development] ykkfive:
i don think a normal windows can read ext2, and actually i don care. i can do it with adb and i have a linux box as well
[Galaxy S I9000 Android Development] distortedloop:
Right, just something people need to be aware of before trying this on their own.
[Galaxy S I9000 Android Development] ykkfive:
that's why i prefer not to post a step by step guide, coz there r too many things need to be awared. so i still think it's better to let ppl here to automate it rather than typing the commands themselves
[Galaxy S I9000 Android Development] fantacies:
That's fine to have you unveiled what have you done finally. Don't need to be paranoid, people following your thread should not be laymen. Anyway, thanks for sharing your tests.
[Galaxy S I9000 Android Development] distortedloop:
Agreed, and agreed.
[Galaxy S I9000 Android Development] ykkfive:
sorry about that, and, thx so much
[P3400 General] Jackell:
Hello Guyz,

Can any one please please let me know how to enable Threaded SMS in my P3400i as I have Windows Mobile 6.0 & tried all patches & tricks to enable it but still no luck :-(

I will be grateful if any one let know how to do this or its not possible in P3400i

Thanks in advance.
[Touch Diamond, MDA Compact IV General] cdbucuresti:
Hy,

to all the helpers that post a message to help me.

I have a Touch Diamond (GSM) and it had this configuration:

WINDOWS MOBILE 6.1 PROFESSIONAL

CE OS 5.2.19965 ( BUILD 19965.1.2.3 )

2008

ROM VERSION : 1.93.479.3 WWE

ROM DATE : 07/25/08

RADIO VERSION : 1.00.25.05

PROTOCOL VERSION: 52.29.25.12W

ORIGINAL BOOTLOADER :

DIAM100 MFG 64M

SPL-1.40.OLINEX

MICROP-DIAM (LED) V11

SPOC-DIAM STAGE_PVT V0X30

I flashed 1.93 olinex from pc, and Gen.Y D2 R5.5 WWE-ROM (GSM)from internal

storage , after a few days I started to notice that my battery(1800) won't last more than a day and when I connect to pc using Disk Drive and try to copy a file in the internal storage(4 Gb) I reiceive an error and try again.

So I looked at the bootloader screen and noticed this:

DIAM100 64M (MFG-MISSING)

SPL-1.93 OLINEX

MICROP-DIAM (LED) V11

SPOC-WRONG PLATFORM V0X0 (???)

And from there I tried to change it back to stock - original rom,radio,bootloader,etc

But no effect.

I tried to write even with MTTY- no succes

Changed the Hspl version to:

DIAM100 MFG 64M

SPL-1.30.OLINEX

MICROP-DIAM (LED) V11

SPOC-WRONG PLATFORM V0X0

-(signed, unsigned-and many other hspl sign,unsigned)-no succes

Can anyone tell me what is wrong and how to fix?

Thank you for your time and help.
[Wildfire General] chrisandchips:
Has anyone got root explorer running on their wildfire? Whenever i search android market it can't find the program so I was wondering if anyone else has been able to find it and get it going.

Any help would be much appreciated, thanks.
[Wildfire General] rxxt:
Yes I got it, work fine. I could't find it on market to, so i find and 'apk' on google.
[Wildfire General] chrisandchips:
Ah right ill have a look then. Cheers!
[Android Software/Hacking General [Developers Only]] crustyz:
Some time ago i parted my sd card (2gb/Tattoo) for app2sd, but i discovered that this program doesnt work for my phone... but my memory card is still parted and i can access ony 1.3GB from the sd card memory.

How can I get back SD card in original condition? :confused:
[Android Software/Hacking General [Developers Only]] radite:
http://rs567.rapidshare.com/files/390053643/Paragon_Partition_Manager_9.0_Professional.7z

try to use that software bro....

sent from indonesia
[Android Software/Hacking General [Developers Only]] crustyz:
Big thanks to you!

works! :)