• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Model number: SPH-M820 vs SPH-M820-BST

hagabaka

Newbie
I have a samsung galaxy prevail from boost, and I rooted it using "FA19 Gingerbread Rooted Image with CWM5 by Koumajutsu", and then installed "CyanogenMod 7 Unofficial Beta 5". Everything works fine, but the Android Market/Google Play website has been listing two devices, one with model number SPH-M820, which is what my phone currently says, and the other SPH-M820-BST, which I assume was the original model number. Today I came across app Proboards which is listed as compatible with only the -BST phone. I purchased the app, but the market could only send it to the -BST phone which doesn't exist. Can app compatibility be based on model number, or are there actually more substantial differences introduced by the mods which make this app incompatible?

Here's what the Devices section in Google Play site says

Nickname Visibility Maker Model Carrier Last Used Registered On
Unnamed Device Shown in menus Samsung SPH-M820 - March 14, 2012 March 2, 2012 Edit›
Unnamed Device Shown in menus Samsung SPH-M820-BST Boost Mobile March 2, 2012 March 1, 2012 Edit›
 
CM 7 is not the same build as stock or CTMod . Both stock and CTMod will register with the -BST on the end of the ID . As you can see , CM7 does not . Maybe the app is not compatible with the CM7 build . :)

If you want to test it out and see if it will work with CM7 , you will need to do a CWM backup then flash to either stock or CTMod , download the new app from the Market and do a Titanium Backup of the new app . THEN restore your CWM backup and try installing the app from the Titanium Backup that you made . KEEP IN MIND that if it does install , the app may cause instability issue with CM7 .
 
They are pretty much the same device. The only thing the BST does is prevent you from installing some apps on the market.
 
They are pretty much the same device. The only thing the BST does is prevent you from installing some apps on the market.

They are the same device, however, programmed differently, will not run the same...

And if u read the post, its the opposite happening... The bst phone will allow the app while the non bst will not....
 
Different builds mean some apps will work on one where they will not on the other . CM7 is a prime example . There are a lot of apps that will run on CM7 that won't run on stock or CTMod . Evidently it's the same way with apps for stock or CTMod . Some apps will run on those builds were as they won't with CM7 . Makes sense to me .
 
I appended -BST to the model number in build.prop, rebooted, and cleared data and cache for Google Play Store. The app is still not listed when I search on the phone, and my device listing in Google Play website doesn't change. I also tried replacing the lines in build.prop with the ones for Nexus S from Install Incompatible, UnSupported Apps from Android Market, and get the same result. The phone's about screen shows the models I changed to, but Google Play doesn't seem to care.

Does this trick to install incompatible apps no longer work, or am I missing a step? Does the app show as compatible for anyone using stock? Where could I find a stock build.prop for Prevail?

Edit: Actually changing the model to "Nexus S" allowed me to install the app, and it works.
 
Back
Top Bottom