How to replace build.prop on the 1st gen Scroll - NOT Excel

[Warpedflash]

build.prop should not cause launcherpro to go into a force close loop.

Standard stuff
Make sure the new build.prop is there and its named build.prop (not build.prop.txt or anything)
Changed your launcher to either the standard or adb and see what it does?

[Fraz]

Build.prop will NOT affect LP or any launcher, can you please try to locate the original b.p file before replacing it with the updated version, as per previous posts it can be found at system / (scroll right down , it should be here )

[slarti99]

OK thought I had got everything back but encountered the ADW Force close loop again. I wiped the cache (twice) but that had no effect so I did a wipe data/factory reset. Now I have slowly got most things back after going through the Android set up ("Set up your unknown" Android says !) apart from the market. When I use the market I get a server error - Retry or Cancel. Retry does not work even though I have a wifi connection (maps work). Any help ? I have no data on it to loose anymore.

Thanks

[JimmyW]

We're currently testing Steve's nice and lovely working 2.2 in irc slarti, So expect a release very very soon (unless you want to come in irc and test with the rest of us)

[slarti99]

I'll be a Guinea Pig if you need one !

[Kommander]

Possibly a random query, but if anyone knows an answer, it'd help greatly.

Installed build.prop v3 140 and already noticing the benefits. I realise that the screen density has changed, however, is there a way to change the width of the lock screen overlay (where you drag your finger over the screen to unlock the tablet) so that it's not missing the edges of the screen in landscape mode?

It's the only thing that's bugging me!

[Charlie]

@Kommander

ummm, that is strange - i have build.prop v3 and do not have the same issue you are having - it does seem random.

[Kommander]

I'll switch back, then try again, see if that solves it.

It definately happened before I did the clockwork mod, that was done last. Are you using 140 or 160? I'm wondering if screen density / width has been hard coded for that component.

[Charlie]

@Kommander - I have it set as 140

[Kamikaze-X]

i want to enable hardware accelerated 3D... is editing the build prop the only way to do this atm, as i don't really want to ruin my pretty much perfectly running scroll atm.