Build.prop Finger Print Question

[BlackMarket]

If I change my build.prop line:
"ro.build.fingerprint=verizon/voles/sholes/sholes:2.1/ESE18/45394:user/release-keys"

as seen in my LithMod ROM

and change it to read as follows:

ro.build.fingerprint=verizon/voles/sholes/sholes:2.2/FRG22D/50454:user/release-keys

What would happen?

[Abe21599]

it would make the market believe you have FRG22D.

[BlackMarket]

And thats it? no adverse effects?

[BlackMarket]

figured **** it... I did it... no problem on reboot.

sorry for the n00b question.

[log]

It'll also make Verizon think you already have FRG22D so you won't get the OTA update notifications.

[LexusBrian400]

It'll also make Verizon think you already have FRG22D so you won't get the OTA update notifications.

Thats actually not true at all.


Its just a market fingerprint. Not a system key.

[meishkov]

It'll also make Verizon think you already have FRG22D so you won't get the OTA update notifications.

Thats actually not true at all.


Its just a market fingerprint. Not a system key.

That's not true. I'm using SS 4.7 and I had to do this because my phone kept downloading the 77mb update over and over and there was nothing I could have done about it until I found out about editing that line in the build.prop file.

[mrpotatohead99]

It'll also make Verizon think you already have FRG22D so you won't get the OTA update notifications.

Thats actually not true at all.


Its just a market fingerprint. Not a system key.

That's not true. I'm using SS 4.7 and I had to do this because my phone kept downloading the 77mb update over and over and there was nothing I could have done about it until I found out about editing that line in the build.prop file.

Just as a double confirmation LexusBrian is in fact wrong. Changing the fingerprint in the build.prop as stated in the OP will in fact stop the OTA update from downloading to your phone. It essentially works as a fingerprint indicating what phone you have and what ROM version you have. Therefore, if you update your build.prop fingerprint to the fingerprint of the latest OTA you won't the OTA, saving you battery and preventing related overheating issues as well. Also, you could trick Market into thinking you have a Droid X and download apps that only appear for the Droid X. Finally, the issue above will be fixed in SS 4.8 as Chevy updated the build.prop fingerprint. Hope that clears everything up.

[LexusBrian400]

Thats actually not true at all.


Its just a market fingerprint. Not a system key.

That's not true. I'm using SS 4.7 and I had to do this because my phone kept downloading the 77mb update over and over and there was nothing I could have done about it until I found out about editing that line in the build.prop file.

Just as a double confirmation LexusBrian is in fact wrong. Changing the fingerprint in the build.prop as stated in the OP will in fact stop the OTA update from downloading to your phone. It essentially works as a fingerprint indicating what phone you have and what ROM version you have. Therefore, if you update your build.prop fingerprint to the fingerprint of the latest OTA you won't the OTA, saving you battery and preventing related overheating issues as well. Also, you could trick Market into thinking you have a Droid X and download apps that only appear for the Droid X. Finally, the issue above will be fixed in SS 4.8 as Chevy updated the build.prop fingerprint. Hope that clears everything up.

Okay, that may be true for your phone, but its not for mine. I have a droid x now, but when I had an eris, the market fingerprint had nothing to do with our OTA updates. In About Phone, the system build was the same so we still kept getting the notification. Market fingerprint had nothing to do with it on that phone. So no, I'm not wrong. Maybe in the case of your phone type, but not all.

I'm guessing Moto and HTC do things differently All we had to do on Eris is remove OTACerts.zip, and we never got a notification again. No battery drain like you guys report from doing that either. In fact, its how all Eris ROMS are made - They just remove OTACerts.zip

So I may have been wrong pertaining to Moto phones, but I'm not wrong pertaining to ALL phones

Build.props is what I do. If you have a Droid2 or DroidX, look in Rom Manager and you'll find Beesley's Build.props.

I'm Beesley

I should have checked that this was the droid section before answering the question that was sent to me. My mistake...

[mrpotatohead99]

Okay, that may be true for your phone, but its not for mine. I have a droid x now, but when I had an eris, the market fingerprint had nothing to do with our OTA updates. In About Phone, the system build was the same so we still kept getting the notification. Market fingerprint had nothing to do with it on that phone. So no, I'm not wrong. Maybe in the case of your phone type, but not all.

I'm guessing Moto and HTC do things differently All we had to do on Eris is remove OTACerts.zip, and we never got a notification again. No battery drain like you guys report from doing that either. In fact, its how all Eris ROMS are made - They just remove OTACerts.zip

So I may have been wrong pertaining to Moto phones, but I'm not wrong pertaining to ALL phones

Build.props is what I do. If you have a Droid2 or DroidX, look in Rom Manager and you'll find Beesley's Build.props.

I'm Beesley

I should have checked that this was the droid section before answering the question that was sent to me. My mistake...

Interesting Beesley! Well technically changing the fingerprint should work with any phone. To clarify that means all build/hardware/model etc fingerprints need to be updated in the build.prop as there are multiple areas that specify different values. You would have to update all of these to reflect another phone in order to see it's apps in Market. As for the OTA issue with the Droid I say only change the
ro.build.fingerprint because all the ROMs I know of have all the other values correct for the latest OTA. In other words, I'm assuming ro.build.version.release, ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.board, etc all have properly assigned values for the latest OTA.

P.S. Just re-read your post and realized you said build.props are your thing so you probably already knew all the above.