[BETA] build.prop Editor - Rooted Spica Only

[eViLrAcEr]

Can anyone confirm whether changing the device id to another device allows the new features of Google Maps to be enabled, specifically the vector map rendering?

no, it doesn't.

[saturnreturn]

no, it doesn't.

How are we gonna enable it then? I can't believe that Spica funning Froyo cannot render the vector graphics in 2D (3D buildings are not important, but 2D vector maps are!)

[saturnreturn]

Can anyone confirm whether changing the device id to another device allows the new features of Google Maps to be enabled, specifically the vector map rendering.

See - Google updates - for a version with it enabled

[cygnus]

OK, Update.

1) New release, a little clean up really. It's a mess anyway so it doesn't matter. http://www.damiensturdy.co.uk/bpm2.zip
2) Source code!: http://www.damiensturdy.co.uk/BPM_Source.zip

Forgive the source- remember the whole application is a hack, and was my first foray into Android coding- I went in blind, so this is the result.

I'll look into setting up a code page for it if it's wanted.

I've also found the reason that the "Open market" hack doesn't work- the original hack worked because the DroidX wasn't activated on the market, so by default saw everything. Now, it is activated so it cant see everything either. It does make a difference, but we'll have to find a new hack if we want to completely open the market. Plus we'll never COMPLETELY open it- apps are also filtered by screen size, so HDPI apps will not ever show on the Spica- the screen size seems to be sent from the app, not a config file, so we can't hack it. :/

[iMarcus]

Let me just say that if you change your default screen density from 160 to 200 you cant get past your boot screen, Thx i now have to go find a usb cable to reflash my Froyo t my gt i5700, if anyone else wants the files i can give you my own links but you have to message me, it includes the full Froyo nothing dosn't work, and multitouch works along with all features!!!

Just PM me and ill give em to you because there on my desktop

FROYO FTW!

---------- Post added at 10:30 AM ---------- Previous post was at 10:28 AM ----------

Also the DroidX is actually really usefull, do not use screen density 200. not tried 180!, would recommend you to fix this so we only select what is possible without f**king things up.

[cygnus]

You could just go into recovery and move the backup you created (right?) back into the Android filesystem?
Even if you didn't create a backup (you plonker.... lol.) you can grab the file from your packaged ZIP file and push that to your device, a reinstall is not necessary.

That said, I have used 200 without problems. Can anyone else kindly confirm this is an issue? Naturally if there are any cases where the app is causing issues I will try to block them from happening. As always there are risks with modifying system files!

[cygnus]

OK, I've found the problem.

My advice for the moment is: give the application time to do its job- let it load, wait for it to get superuser permissions, then make your choices.

If you try to do things too quickly, it seems to spit out a 33byte file, which prevents device boot.

I'll try to work this out over the weekend.

[cygnus]

Oh, do I love Linux coders!

I've just been shown a terminal command that will shrink my code to about 33% of it's current size. Lovely. It will also fix the apps occasional build.prop corruptivity. :-)

I'll grab my source and expect an update soon. I've now got quite a few things to add!

[Frazer]

This seems to work well for me, thanks for the work. Its nice to change the screen to 120.

[slimito]

If I change the density of the screen I can take screen shots?

Right now is on 160, 24bpp kernel and I do not work any application screenshots to make me work.

Can this help me?