Database Users

Issue with Pandora confirmed on 2.2 EVO

I have been experiencing some sound quality issues with Pandora 1.3/1.4 where it sounds like a tin can. All peaks are stripped out. like base and treble are all in the negative range. I have to run it in high quality range to get it to sound ok. Wit that said I get more skips and glitches/ interruptions. ;-(
According to Pandora support it is an issue with Froyo and how it handles AAC+ audio. I thought I'd share my findings and in the hopes one of you awesome devs might have a work around/ patch for the EVO.
Email from Pandora Support:
Hi Gregory,
Thanks for writing.
Froyo has a problem processing our AAC+ files. We have confirmed that this is an issue in the OS, and we think they should have it fixed in a future Android release. Thanks for your patience in the meantime.
As far as the error you're getting, sorry you are having problems with this.
My first suggestion is to power down the phone and pull the battery out. Put the battery back in, turn the phone on, and then try launching our app again.
If that doesn't help, try uninstalling then reinstalling the app.
From the home screen, press the menu key and select "Settings" then "Applications". Next select "Manage Applications". Scroll down and select Pandora. Then uninstall.
To reinstall, go to the Android Market and search for Pandora. You should also see it in the most popular apps list.
Let me know if this helps.
Best,
Jed
Pandora Listener Support
*More questions about Pandora? Please visit our FAQ:
http://blog.pandora.com/faq

Neotype33 said:
I have been experiencing some sound quality issues with Pandora 1.3/1.4 where it sounds like a tin can. All peaks are stripped out. like base and treble are all in the negative range. I have to run it in high quality range to get it to sound ok. Wit that said I get more skips and glitches/ interruptions. ;-(
According to Pandora support it is an issue with Froyo and how it handles AAC+ audio. I thought I'd share my findings and in the hopes one of you awesome devs might have a work around/ patch for the EVO.
Email from Pandora Support:
Hi Gregory,
Thanks for writing.
Froyo has a problem processing our AAC+ files. We have confirmed that this is an issue in the OS, and we think they should have it fixed in a future Android release. Thanks for your patience in the meantime.
As far as the error you're getting, sorry you are having problems with this.
My first suggestion is to power down the phone and pull the battery out. Put the battery back in, turn the phone on, and then try launching our app again.
If that doesn't help, try uninstalling then reinstalling the app.
From the home screen, press the menu key and select "Settings" then "Applications". Next select "Manage Applications". Scroll down and select Pandora. Then uninstall.
To reinstall, go to the Android Market and search for Pandora. You should also see it in the most popular apps list.
Let me know if this helps.
Best,
Jed
Pandora Listener Support
*More questions about Pandora? Please visit our FAQ:
http://blog.pandora.com/faq
Click to expand...
Click to collapse
I'm using Pandora on FroYo just fine myself. Actually I remember some tin sounds on 2.1 but since 2.2 I've had a better experience.
It may be a problem in the Kernel which would make sense because I am using the netarchy custom kernel verses the stock one.
Either that or its in the ROM, but I use my own ROM so maybe that's it...
Are you using stock or are you rooted and running custom? If rooted do a nandroid and try Netarchy's kernel (I prefer version 3.7.8b for now)

I have tried the Stock Pre-release Rom and the current Stock Rom. I rooted both. There has been no reason other than this issue to move to a custom Rom on the Froyo since speed and performance for me has not been an issue. I do like the sense interface. (My Hero was a different story, slow and over whelmed.I customized the crap out of it since it needed all the cpu cycles I could get.)
Thanks for the suggestion. I might have to check out some other Roms to see if it is in deed a kernel issue.

There's an update for pandora in the market. Maybe they fixed the issue?

This issue has been addressed several times in this forum. The workaround is performed with adb commands at a Windows Command Prompt.
Temporary fix (no root required):
adb shell setprop media.stagefright.enable-player false
Click to expand...
Click to collapse
The temporary fix revert back everytime you reboot your phone.
For a more permanent fix (requires root and nand unlock):
-adb pull /system/build.prop
-edit build.prop (opens in DOS text editor)
-change (media.stagefright.enable-player=true) to (media.stagefright.enable-player=false) and save and exit editor.
-adb remount
-adb push c:\directory where you pulled the file to\build.prop /system/
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

The issue is with the Stagefright media decoder. All Froyo ROMs and kernels experience this problem.
Sent from my PC36100 using XDA App

There was an update for Pandora this morning. Maybe that corrected the issue?

bpqow said:
There's an update for pandora in the market. Maybe they fixed the issue?
Click to expand...
Click to collapse
Yeap, that is 1.4. This effects all version of the stock build of 2.2.

sombdy said:
This issue has been addressed several times in this forum. The workaround is performed with adb commands at a Windows Command Prompt.
Temporary fix (no root required):
The temporary fix revert back everytime you reboot your phone.
For a more permanent fix (requires root and nand unlock):
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks I'll have to check that out.

Permanent fix: Use the latest CM6 Nightly. Cyanogen pushed the official fix for the Stagefright decoder from Google, and all AAC+ streams sound perfect now.

sombdy said:
Temporary fix (no root required):
Code:
adb shell setprop media.stagefright.enable-player false
Click to expand...
Click to collapse
That does not work on non-rooted phones. THe command executes with no error, but doesn't actually do or change anything (confirm this with a getprop command immediately afterwards).
In short, if you are on the 2.2 OTA you are SOL until HTC releases a fix (Google has already committed their code for it) or someone finds a way to root 2.2 OTA.

sohr said:
That does not work on non-rooted phones. THe command executes with no error, but doesn't actually do or change anything (confirm this with a getprop command immediately afterwards).
In short, if you are on the 2.2 OTA you are SOL until HTC releases a fix (Google has already committed their code for it) or someone finds a way to root 2.2 OTA.
Click to expand...
Click to collapse
That command line does work on a non-rooted phone. The setprop command does not require root access. And as I said in the post, it is not a permanent fix. I know it does not change the build.prop file, but it does change your settings for the current session. If you reboot the phone, the settings return to enable-player = true, hence a temporary fix. Just issue the command again to turn off Stagefright.
So, dude, you are not completely SOL.
Sent from my PC36100 using XDA App

sombdy said:
That command line does work on a non-rooted phone. The setprop command does not require root access. And as I said in the post, it is not a permanent fix. I know it does not change the build.prop file, but it does change your settings for the current session. If you reboot the phone, the settings return to enable-player = true, hence a temporary fix. Just issue the command again to turn off Stagefright.
So, dude, you are not completely SOL.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I know setprop does not require root access-- however, without it it appears to do nothing for the stagefright setting.
Running "adb shell getprop" and looking for the appropriate stagefright setting shows it is still set to true immediately after running the setprop command that is supposed to set it to false.
EDIT-- And a quick soundtest of Pandor/Slacker/Yahoo Radio after running the command shows no discernable difference in sound quality-- still sounds like listening to a low-bitrate stream.

sohr said:
I know setprop does not require root access-- however, without it it appears to do nothing for the stagefright setting.
Running "adb shell getprop" and looking for the appropriate stagefright setting shows it is still set to true immediately after running the setprop command that is supposed to set it to false.
EDIT-- And a quick soundtest of Pandor/Slacker/Yahoo Radio after running the command shows no discernable difference in sound quality-- still sounds like listening to a low-bitrate stream.
Click to expand...
Click to collapse
After issuing the command, be sure to skip foreward in the player so that it buffers a new song. Any previous song that was downloaded before will sound garbled. I experienced this same thing. Trust me. Just let it run for a bit and it will clear up the sound. Skip a few songs and you will hear the difference. Getprop only tells what is in build.prop, but we are not changing build.prop because that requires root. Get it? So of course you will not see a change in getprop. But this does work. You just have to have a song buffered after issuing the command.
Sent from my PC36100 using XDA App

Help getting rid of the system bar (or modify it)

Alright, first of all, this is an internal device, I will not be using these changes on my own device.
We use tablets (previously Galaxy Tabs) in our office for employees to use an internal application. Our application manages its own navigation, and users do not need to access anything else other than the application. I made it a home screen launcher so it's the first thing that loads. On the Galaxy Tab (Android 2.3), I'm also hijacking all the hardware buttons in the device and I can properly secure the device.
However, on Android 3.0, there are no hardware buttons anymore, and you cannot hide the system bar, I have no way to secure the device if the system bar is always there. I understand why it needs to be there, but this is really killing me.
I have 3 options:
Root the device, try to disable the system bar by editing the framework-res.apk --- Already tried this, unsuccesful since I couldn't find anything in there.
Wait for Android 3.0 to drop in AOSP, build my own custom rom which hides the system bar and do my own modifications on it.
Build Android 2.3 from AOSP for the XOOM -- this will be a lot of work, and I would need help, is anyone interested on helping me with this?
Thanks everyone.

velazcod said:
Alright, first of all, this is an internal device, I will not be using these changes on my own device.
We use tablets (previously Galaxy Tabs) in our office for employees to use an internal application. Our application manages its own navigation, and users do not need to access anything else other than the application. I made it a home screen launcher so it's the first thing that loads. On the Galaxy Tab (Android 2.3), I'm also hijacking all the hardware buttons in the device and I can properly secure the device.
However, on Android 3.0, there are no hardware buttons anymore, and you cannot hide the system bar, I have no way to secure the device if the system bar is always there. I understand why it needs to be there, but this is really killing me.
I have 3 options:
Root the device, try to disable the system bar by editing the framework-res.apk --- Already tried this, unsuccesful since I couldn't find anything in there.
Wait for Android 3.0 to drop in AOSP, build my own custom rom which hides the system bar and do my own modifications on it.
Build Android 2.3 from AOSP for the XOOM -- this will be a lot of work, and I would need help, is anyone interested on helping me with this?
Thanks everyone.
Click to expand...
Click to collapse
Downgrading to 2.3 might be your best bet, wish 3.0 AOSP would hurry up, want to get somethings working differently as well myself. Let us all know if you downgrade and how it went! Wouldn't mind trying to sneak the shut off animation onto 3.0 if possible.

kenhunt said:
Downgrading to 2.3 might be your best bet, wish 3.0 AOSP would hurry up, want to get somethings working differently as well myself. Let us all know if you downgrade and how it went! Wouldn't mind trying to sneak the shut off animation onto 3.0 if possible.
Click to expand...
Click to collapse
Yeah, I haven't gotten into it yesterday, but the only thing I'm concerned about running 2.3 on the Tab is the whole issue with Dual-core support, not sure if I would even be able to do it thanks to that, but I'll see. I'm also trying to call a few contacts to see if we can get into some kind of agreement with Moto to try to get the source code early... we'll see...

Have you tried running a different launcher? They allow you to hide system bars on the old android os...might work on 3.0
Sent from my PC36100 using Tapatalk

bwcorvus said:
Have you tried running a different launcher? They allow you to hide system bars on the old android os...might work on 3.0
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yeah, that won't work, the system bar is part of the framework, it's very very low level, you can't hide it since it allows the user to navigate through the device. Before 3.0, devices were required to have hardware buttons, that's not a requirement anymore because of this system bar, it will always always be there.

Atrix runs 2.3 and the same processor

destroyerbmx said:
Atrix runs 2.3 and the same processor
Click to expand...
Click to collapse
True, hopefully they release the kernel source soon so I can take a look and see if I can try to make 2.3 work on the XOOM with the same kernel that's working with 3.0.

here is Tegra 2 with many options running various versions of 2.2 and 2.3.
you should reach out to GoJimi over there.

destroyerbmx said:
Atrix runs 2.3 and the same processor
Click to expand...
Click to collapse
I'm pretty sure atrix is running 2.2.

u can't do anything until source drops. You need baksmali for framework and custom recovery to flash.

I think your best bet would probably be changing the DPI settings somehow (Like they did for the HC build on some phones to get the tablet version) and it would cause you to go into the "phone" version of HC (Doesn't have the system bar) then I would say modify the volume buttons and lock button long presses to recreate the home/back/multitasking buttons if you really want them (such as they have done for the i*hone android ports because ios is dumb and has 1 button). Just a suggestion and honestly I have no idea if this would work.

I'm sure the system bar has a process you can kill with root. I know the status bar can be killed this way on 2.3. Watch logcat and see what you can find. Anyone know more on this?

Porting 2.2 from the g-tab maybe. Similiar hardware I think.
Sent from my Nexus One using XDA Premium App

Just installed lcd denisty on mine and put it at 240 from the default 160...the system bar was gone.

bwcorvus said:
Just installed lcd denisty on mine and put it at 240 from the default 160...the system bar was gone.
Click to expand...
Click to collapse
Glad to see it worked now hopefully the OP sees it. GL to all
Sent from my SCH-I500 using XDA App

Could you please check your /system/build.prop to see whether the lcd density app has added any code?
I usually tweak density directly through this file but the code isnt there atm on my xoom.

I tried changing the density yesterday and was disappointed to discover that the LCD density wasn't in the build.prop. adding the line of code didn't work, either.
XOOM'd from the XDA app.

ftgg99 said:
Could you please check your /system/build.prop to see whether the lcd density app has added any code?
I usually tweak density directly through this file but the code isnt there atm on my xoom.
Click to expand...
Click to collapse
Looking at the date on my build.prop it hasn't been modified. And just to be sure i looked through the file, nothing in there.

Huh, I wasn't receiving notifications on email even though I'm subscribed for instant notifications...
anways, will try the density trick, but that seems like a pain in the butt to redo all the layouts in our app, but that is a very very clever idea, might work.
Update: Yes it works, but only if you use one of those apps, not when editing the system.prop file, anyone care to share what's exactly being edited here?
Thanks again!
Update 2: Actually, I had a typo on the line I wrote on the build.prop, if you write 'ro.sf.lcd_density=240' (or whatever density you want to use), push it and reboot, it does work as it should.

how are u going to press "home" or "back"?
xoom doenst have physical buttons like phones.
how do u get back to home screen if u downgrade to 2.x？

[Q] Netflix on Acer Iconia Tab A500

Hello all, I am new here so I'm sorry if I am ignorent of anything
I have an Iconia tab, and have been patiently for the netflix app to be released. Well it finally seems like it has been done here
http://forum.xda-developers.com/showthread.php?t=1076150
My problem is when I download the apk and try to open it I get the error ''cannot open file''.
Any suggestions? Thanks

Download the apk with Firefox mobile or your desktop PC instead of the default browser. AFAIK, streaming still doesn't work for us, just queue management.

Its not working on the acer yet.
Edit: ninja'd

I think I read somewhere it's a Honeycomb issue, not just an Acer issue.

the device check disabled apk asks you to upgrade to the latest version on the market (which doesn't exist on our device), and the non-check disabled version will let you browse, but if you try to play a video it pops an error saying the device is not supported.
Hopefully we'll get something that works in the near future. Netflix claims to be working on other devices and it looked like tablets were on the list as well.

Thanks everyone for your answers. Any chance we can keep this thread going as an update to everyone wondering when netflix will be brought over so users do not have to scour the web in search of the answer?

Just a bit of a noob question, but what about changing your build.prop?

If I understand correctly, that requires root, and I do not want do downgrade to gingerbread.

Yup..
dkhuizenga said:
If I understand correctly, that requires root, and I do not want do downgrade to gingerbread.
Click to expand...
Click to collapse
I have heard of doing this and am pretty sure root is required.
Such a shame Netflix has not gotten it together for us yet - this screen rocks as a movie player!

dkhuizenga said:
If I understand correctly, that requires root, and I do not want do downgrade to gingerbread.
Click to expand...
Click to collapse
I have my acer rooted, but not well enough it seems. I still run honeycomb, and in fact still get firmware updates from acer. I rooted it so I can setup my two 1tb external hard drives to it lol. just used gingerbreak and a couple other things post root. However, i did try and edit the build.prop but wont allow me to save, just read only. I havent messed with it extensively, but seems like there should be a way.

phoenixbennu said:
However, i did try and edit the build.prop but wont allow me to save, just read only
Click to expand...
Click to collapse
'mount -o remount,rw' ?

phoenixbennu said:
I have my acer rooted, but not well enough it seems. I still run honeycomb, and in fact still get firmware updates from acer. I rooted it so I can setup my two 1tb external hard drives to it lol. just used gingerbreak and a couple other things post root. However, i did try and edit the build.prop but wont allow me to save, just read only. I havent messed with it extensively, but seems like there should be a way.
Click to expand...
Click to collapse
If you use root explorer it will let you mount the file system read-write so you can edit the file.

Alright guys I am not sure if it has been tested but when I get home. I have the lib files that fixed the playback issue on sense 3.0 I will install the deactive device check version and push the lib Files It may actually work!! I just tested on another device that had playback issues worked flawlessly!! Ill let you guys know in like 2 hours or so when I get home.

Right on!
Crsdr37 - sounds promising! Let us know how it goes - since Netflix is totally dragging on getting their software working. My girlfriend's mother uses a HTC Evo 4 from Sprint - netflix support has been broken for weeks for them, and the OTA patch they tried to push out did not work. Total fustercluck

entropy.of.avarice said:
Crsdr37 - sounds promising! Let us know how it goes - since Netflix is totally dragging on getting their software working. My girlfriend's mother uses a HTC Evo 4 from Sprint - netflix support has been broken for weeks for them, and the OTA patch they tried to push out did not work. Total fustercluck
Click to expand...
Click to collapse
I actually just fixed it on my evo 15 minutes ago. When I get out I will pm you and get some information from you on her evo.

Crsdr37 said:
I actually just fixed it on my evo 15 minutes ago. When I get out I will pm you and get some information from you on her evo.
Click to expand...
Click to collapse
Would be most grateful! Take your time, I am out of classes today and girlfriend is working - got all day to geek out

i am very excited to find out on this

Alright guys so after dismantling netflix.apk the latest version the issue is within one of the files called nrdp.js Think of it as the gate keeper to our netflix enjoyment. It checks certain areas of the device here is the list we need to bypass to get the rsa key injected into our devices for access to the netflix servers.
1.Get Model
2.Get Software Version
3.Get Certification Version
4.Get ESN
5.Get ESN Prefix
Those are all the functions it calls for device checking. That I could find. There is also a certificate file ca.pem that controls how long the app works for before you have to get new certificate that is encrypted up the ass so big roadblock..... Sorry I tried and will continue to try but it does not look good... Damn those large companies with their big sticks.

Installed but error connecting after selecting a vid
I have an stock iconia with 3.1 and tonight I installed the apk mentioned in this article:
http://www.androidpolice.com/2011/0...neycomb-devices-and-possibly-most-phones-too/
App runs but when I select a vid I get:
"Sorry, we could not reach the Netflix service. Please try again later. If the problems persists please visit the Netflix website (12001)."
Anyone else getting this? Any workarounds?

ingrouille said:
I have an stock iconia with 3.1 and tonight I installed the apk mentioned in this article:
http://www.androidpolice.com/2011/0...neycomb-devices-and-possibly-most-phones-too/
App runs but when I select a vid I get:
"Sorry, we could not reach the Netflix service. Please try again later. If the problems persists please visit the Netflix website (12001)."
Anyone else getting this? Any workarounds?
Click to expand...
Click to collapse
Same issue.
I wonder if a build prop for 1.3 would work?
Xoom users seem to be having great sucess

How to fake another device in Android Market with root

I'm trying to download a game that Android Market says is incompatible with my device. However, I'll be upgrading later and don't want to miss this sale.
Is there a way to edit a file (I'm guessing the build.prop) to fake another device so that Android Market lets me download the app?

itch808 said:
I'm trying to download a game that Android Market says is incompatible with my device. However, I'll be upgrading later and don't want to miss this sale.
Is there a way to edit a file (I'm guessing the build.prop) to fake another device so that Android Market lets me download the app?
Click to expand...
Click to collapse
change the build.prop look for the line that says 240 dpi. change it to 160 for tabs
need to clear market data via settings > applications > manage applications

synisterwolf said:
change the build.prop look for the line that says 240 dpi. change it to 160 for tabs
need to clear market data via settings > applications > manage applications
Click to expand...
Click to collapse
Unfortunately, that didn't work for me. I tried all sorts of things. Emulating a Nexus S, GT-I9000, HTC vision, none worked.

itch808 said:
Unfortunately, that didn't work for me. I tried all sorts of things. Emulating a Nexus S, GT-I9000, HTC vision, none worked.
Click to expand...
Click to collapse
You need to find the ro.build.fingerprint for a device the app is available for and then switch it out for thr one in your /system/build.prop file. You will also need to wipe cache, dalvik-cache, and clear the market apps data thru the settings-applications menu.

cmlusco said:
You need to find the ro.build.fingerprint for a device the app is available for and then switch it out for thr one in your /system/build.prop file. You will also need to wipe cache, dalvik-cache, and clear the market apps data thru the settings-applications menu.
Click to expand...
Click to collapse
Any tips what I should add?
I'm trying to purchase Asphalt 6 HD from the 10 million for 10 days sale

itch808 said:
Any tips what I should add?
I'm trying to purchase Asphalt 6 HD from the 10 million for 10 days sale
Click to expand...
Click to collapse
Well i checked out the app thru the market to see if any comments stated a working phone model and noticed the reviews are pretty bad, and a lot of people claming it is not working for their newer phones. Im not familiar with the game. Your best bet would be to contact the developer and ask them what newer phones you may upgrade to are supported. Then google "ro.build.prop 'phone model'" and try to find the full fingerprint. Once you find it, replace the one in your build.prop and then try to buy it.

Lol yeah my way is only for simulation of tab vs phone. No clue on a whole foot print change.
Sent from my sexy assistant. (AMOLED HTC Incredible)

This is the fingerprint for the desire hd a supposed compatiabl phone for the game.
Code:
ro.build.fingerprint=htc_wwe/htc_bravo/bravo:2.3.3/GRI40/96875.1:user/release-keys

cmlusco said:
This is the fingerprint for the desire hd a supposed compatiabl phone for the game.
Code:
ro.build.fingerprint=htc_wwe/htc_bravo/bravo:2.3.3/GRI40/96875.1:user/release-keys
Click to expand...
Click to collapse
Tried, didn't work.
I then even tried adding these changes:
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=bravo
ro.product.board=bravo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.build.product=bravo
Rebooted, cleared cache. Still no go.

itch808 said:
Tried, didn't work.
I then even tried adding these changes:
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=bravo
ro.product.board=bravo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.build.product=bravo
Rebooted, cleared cache. Still no go.
Click to expand...
Click to collapse
Did you clear the data from the market? Menu - settings - applications- all tab select market and press force stop and then clear data.

cmlusco said:
Did you clear the data from the market? Menu - settings - applications- all tab select market and press force stop and then clear data.
Click to expand...
Click to collapse
I should've have clarified, when I said "cleared cache", yes I went into applications and cleared all data.
I give up. I guess it can't be done.

Check my thread I created for this kind of issue.
[HOW TO] Play games requiring NVIDIA tegra. ShadowGun, Sprinkle, etc..
You might just need chainfire but read thru the whole thread regardless. Chainfire fixes market settings allowing you to see, purchase, and install the games. You might require the drivers as well. Its all outlined in my thread. Hope that helps. Good luck.

I'm not sure how much help this provides, but it works for me.
I've previously had a Droid X and a Galaxy Tab 10.1 associated with my google account. This allows me to download any app that will work on the Inc, Droid X, or Galaxy Tab. My solution is to navigate to market.android.com and choose the app I want. When I click buy, it asks me what device I want to send it to. If the Incredible is not compatible, chances are one of my other devices are. I can then continue the purchase for a device I don't even own anymore, but now I own the app. I've provided a screenshot to illustrate.
I've been using this method today for all the 10 cent apps available. Now I own them and will be able to download them once I get my Galaxy Nexus and Transformer Prime.

Hi,
although on a different deivce, I got the same issue - so I just "hijack" this thread
I changed the build.prop, wipe cache, dalvik cache, Android Market cache & data, Google Services Framework cache & data.
Now I do get another phone, the SGS2 I was going for (GT-I9100), but I still can't install anything more than before, with my HTC Hero.
I can't use Chainfire, as it's not compatible with my device
Here ist what I changed in the build.prop:
Code:
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=galaxys2
ro.product.board=GT-I9100
ro.product.manufacturer=samsung
ro.build.product=galaxys2
ro.build.description=GT-I9100-user 2.3.4 GINGERBREAD XXKG2 release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:2.3.4/GINGERBREAD/XXKG2:user/release-keys

RamAir02 said:
I'm not sure how much help this provides, but it works for me.
I've previously had a Droid X and a Galaxy Tab 10.1 associated with my google account. This allows me to download any app that will work on the Inc, Droid X, or Galaxy Tab. My solution is to navigate to market.android.com and choose the app I want. When I click buy, it asks me what device I want to send it to. If the Incredible is not compatible, chances are one of my other devices are. I can then continue the purchase for a device I don't even own anymore, but now I own the app. I've provided a screenshot to illustrate.
I've been using this method today for all the 10 cent apps available. Now I own them and will be able to download them once I get my Galaxy Nexus and Transformer Prime.
Click to expand...
Click to collapse
If we had Galaxy Tabs then we wouldn't have this problem.
The problem is that we don't have a compatible device, but want to buy it anyway in case we (a) some day get a tablet, or (b) the developer fixes the apparently crappy compatibility.
I'm also having the same problem with one of today's freebies, NFL Rivals

i'm drawing at straws here, but... anyone try market enabler?
https://market.android.com/details?id=ch.racic.android.marketenabler&hl=en

mercado79 said:
i'm drawing at straws here, but... anyone try market enabler?
https://market.android.com/details?id=ch.racic.android.marketenabler&hl=en
Click to expand...
Click to collapse
This only fakes the network you're on, allowing you to get apps that are normally only available in certain countries or on certain carriers. Not the device though...

Do you have your dpi setting in build.prop something other than stock?

I have been stuck like this a few times when changing device.
To change from HTD Desire to HTC Desire HD:
edit build.prop (copy old first):
change all occurences of bravo to ace
change HTC Desire to HTC Desire HD
change fingerprint to ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys
save build.prop
goto settings,applications find market. stop it, clear all data
clean dalvik cache just to make sure
reboot phone
that worked for me..

Thanks man !!! worked like a charm!!! I'm in the same situation, planning to upgrade the phone on January, but I don't want to miss the $.10 promotions. Now I bought BackStab HD using my Nexus One (was recognized as HTC Desire HD). I lost the opportunity to buy Asphalt 6, but well.... another opportunity

MLB At Bat 12 problem

Hey,
I bought the MLB At Bat 12 app, in order to watch games with my MLB.tv subscription.
The Note is in the compatible devices list, but I can't see the Video option.
Anyone has faced the same problem? Could it be that MLB only supports the AT&T version of the Note?
Thanks!
Edit:
MLB heard us and the International Note, AKA GT-N7000 is now a fully supported device.
Live games are working great.
Cheers!

crizolli said:
Hey,
I bought the MLB At Bat 12 app, in order to watch games with my MLB.tv subscription.
The Note is in the compatible devices list, but I can't see the Video option.
Anyone has faced the same problem? Could it be that MLB only supports the AT&T version of the Note?
Thanks!
Click to expand...
Click to collapse
There is no live feed during spring training, only radio.
Sent from my GT-N7000 using xda premium

You mean on the app?
'Cause they are streaming 150 Spring Training games. As a matter of fact, I'm watching a Red Sox game on my PS3 right now.

Yes on the app. On opening day the app will update and video will be available.
Sent from my GT-N7000 using xda premium

spring training videos are available on the streaming option. it works on my galaxy tab 10. however, I same facing the same problem on my note where there is no video icon to click on. I have already contacted MLB.TV. they say they will look into the problem and then get back to me. I suspect that the galaxy note they have on that list is the American version.

DMax99 said:
spring training videos are available on the streaming option. it works on my galaxy tab 10. however, I same facing the same problem on my note where there is no video icon to click on. I have already contacted MLB.TV. they say they will look into the problem and then get back to me. I suspect that the galaxy note they have on that list is the American version.
Click to expand...
Click to collapse
I have specifically read that you will not be able to watch on cellphones. I'll try to find it for you tomorrow.
Sent from my GT-N7000 using xda premium

I looked around and couldn't find anything saying that. I'll né gratefull if you could fid out querendo you saw that.
I've also contacted MLB suport, but they haven't answered back yet.

mlb on droid
I have a HTC Inspire which I had MLB At Bat 12 installed and it DOES offer games during spring training. I know because I was watching them up until I rooted the phone and installed a custom rom (RCmix), reinstalled mlb at bat 12 and now I do NOT have the video option.

MLB support has been a dead end. They don't even know what I'm talking about.
This is very frustrating, I was really hoping some games when not at home.

I'm having similar issues on both my Asus Transformer and Galaxy SII. Hopefully, as someone mentioned earlier, the video will be available on mobile devices on opening day.

mlb at bat/gummy rom issue
I have been watching spring training games on my paid subscription of mlb at bat on stock rom/rooted droid 4. Since I flashed gummy rom this morning, I get a video error message saying it cannot load the video. I can hear about 3 seconds of announcer audio although the screen is black and then i get the error.
Im assuming its a clash with gummy, but i was wondering if anyone else had this problem, or has a fix to make at bat gummy compatable.
Does at bat video streaming work with other custom roms?
thanks!

Anyone having any luck getting the video icon to show up on a tablet/phone?

nighthawk101 said:
Anyone having any luck getting the video icon to show up on a tablet/phone?
Click to expand...
Click to collapse
PLEASE PRESS THE THANK BUTTON IF THIS HELPS YOU!
YES!! I got this to work last year by editing the build.prop file to make my HTC HD2 running android look like a Nexus S. I even had fun with it so the market reports my phone as an HTC Nexus S.
I downloaded At Bat 12 in Feb. and the spoof still worked.
I just upgraded my phone to an HTC Sensation XE. he video icon was hidden on my new phone because it too is not officially supported.
I edited the build.prop on my new phone similarly and like magic, At Bat 12 shows the video icon now.
Here's how to do it:
0. Go to system settings->applications and clear data for At Bat 12
1. Using an app like Root Explorer, navigate to system->build.prop
2. Make sure you have r/w access and long press build.prop file to open in text editor
3. Scan build.prop file and make:
ro.product.model=Nexus S
(there may be 2 ro.product.model lines that need to be changed
ro.product.manufacturer=HTC
NOTE: These are the most important lines to change. If these don't work by themselves you can also make:
---OPTIONAL---
ro.product.brand=HTC_wwe
ro.product.name=yakjuxw
ro.product.device=maguro
4. Save build.prop file and open again to verify that changes were made. If your changes are not there, check that you are in r/w mode and repeat from step 1.
5. restart your phone, open At Bat 12 and reenter your account details.
Let me know if this helps you. If it does not, let the forum know and we can work out the kinks. This method works for sure... no exceptions.
For those of you who think MLB will somehow rescue your video capabilities on opening day..... IF YOU CAN'T STREAM VIDEO DURING SPRING TRAINING, YOU WILL NOT BE ABLE TO STREAM VIDEO ON OPENING DAY!! I highly recommend editing your build.prop.

blek42 said:
PLEASE PRESS THE THANK BUTTON IF THIS HELPS YOU!
YES!! I got this to work last year by editing the build.prop file to make my HTC HD2 running android look like a Nexus S. I even had fun with it so the market reports my phone as an HTC Nexus S.
I downloaded At Bat 12 in Feb. and the spoof still worked.
I just upgraded my phone to an HTC Sensation XE. he video icon was hidden on my new phone because it too is not officially supported.
I edited the build.prop on my new phone similarly and like magic, At Bat 12 shows the video icon now.
Here's how to do it:
0. Go to system settings->applications and clear data for At Bat 12
1. Using an app like Root Explorer, navigate to system->build.prop
2. Make sure you have r/w access and long press build.prop file to open in text editor
3. Scan build.prop file and make:
ro.product.model=Nexus S
(there may be 2 ro.product.model lines that need to be changed
ro.product.manufacturer=HTC
NOTE: These are the most important lines to change. If these don't work by themselves you can also make:
ro.product.brand=HTC_wwe
ro.product.name=yakjuxw
ro.product.device=maguro
4. Save build.prop file and open again to verify that changes were made. If your changes are not there, check that you are in r/w mode and repeat from step 1.
5. restart your phone, open At Bat 12 and reenter your account details.
Let me know if this helps you. If it does not, let the forum know and we can work out the kinks. This method works for sure... no exceptions.
For those of you who think MLB will somehow rescue your video capabilities on opening day..... IF YOU CAN'T STREAM VIDEO DURING SPRING TRAINING, YOU WILL NOT BE ABLE TO STREAM VIDEO ON OPENING DAY!! I highly recommend editing your build.prop.
Click to expand...
Click to collapse
Was having the same issue, until I found this thread - I haven't been able to test it because there are no games playing atm, however I now have the TV/Video icon

Strange issue has popped up...
For some weird reason, Exchange has stopped syncing after modifying my build.prop
I'm going to delete/add the account to see if this fixes my issue, but be weary for those looking for a workaround.
EDIT:
After removing the Exchange account and trying to re-add it, i get a FC. I reverted back to my original build.prop until someone can find a workaround for both - having exchange working + video on MLB.TV

jaypeezee said:
Strange issue has popped up...
For some weird reason, Exchange has stopped syncing after modifying my build.prop
I'm going to delete/add the account to see if this fixes my issue, but be weary for those looking for a workaround.
EDIT:
After removing the Exchange account and trying to re-add it, i get a FC. I reverted back to my original build.prop until someone can find a workaround for both - having exchange working + video on MLB.TV
Click to expand...
Click to collapse
Exactly what lines did you change from the original build.prop that caused the Exchange errors? The MLB spoof can be done with a single line change for the model ID. This spoof has been known to cause issue with a limited number of apps.
Last year, I know some people ket 2-build.props on their phone and shuttled them in and out of the system folder as needed.... this is not the most optimal solution, but can work.
Let us know if you find anymore out on the topic.

blek42 said:
PLEASE PRESS THE THANK BUTTON IF THIS HELPS YOU!
YES!! I got this to work last year by editing the build.prop file to make my HTC HD2 running android look like a Nexus S. I even had fun with it so the market reports my phone as an HTC Nexus S.
I downloaded At Bat 12 in Feb. and the spoof still worked.
I just upgraded my phone to an HTC Sensation XE. he video icon was hidden on my new phone because it too is not officially supported.
I edited the build.prop on my new phone similarly and like magic, At Bat 12 shows the video icon now.
Here's how to do it:
0. Go to system settings->applications and clear data for At Bat 12
1. Using an app like Root Explorer, navigate to system->build.prop
2. Make sure you have r/w access and long press build.prop file to open in text editor
3. Scan build.prop file and make:
ro.product.model=Nexus S
(there may be 2 ro.product.model lines that need to be changed
ro.product.manufacturer=HTC
NOTE: These are the most important lines to change. If these don't work by themselves you can also make:
---OPTIONAL---
ro.product.brand=HTC_wwe
ro.product.name=yakjuxw
ro.product.device=maguro
4. Save build.prop file and open again to verify that changes were made. If your changes are not there, check that you are in r/w mode and repeat from step 1.
5. restart your phone, open At Bat 12 and reenter your account details.
Let me know if this helps you. If it does not, let the forum know and we can work out the kinks. This method works for sure... no exceptions.
For those of you who think MLB will somehow rescue your video capabilities on opening day..... IF YOU CAN'T STREAM VIDEO DURING SPRING TRAINING, YOU WILL NOT BE ABLE TO STREAM VIDEO ON OPENING DAY!! I highly recommend editing your build.prop.
Click to expand...
Click to collapse
I'm on an international Samsung Galaxy S2 GT-I9100
I only changed ro.product.model from GT-I9100 to SGH-T989 and the TV icon is now available.
I'll test the streaming tonight.

actually, video won't load, circle just spins forever, and upon reboot, it reverts back and I can't get video..
---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------
dag16 said:
can't get it to work with nook color. I did the full Nexus S, no luck. tried the build.prop settings for the Xoom (which is a supported tablet), no luck. even uninstalled and reinstalled mlb lite in case something wasn't erasing properly, but no luck.
Any suggestions?
NM: got it working!!
Thanks!!
Click to expand...
Click to collapse

****novic said:
I'm on an international Samsung Galaxy S2 GT-I9100
I only changed ro.product.model from GT-I9100 to SGH-T989 and the TV icon is now available.
I'll test the streaming tonight.
Click to expand...
Click to collapse
Using ro.product.model=SGH-T989 on the Galaxy S2 GT-I9100 works beautifully.
I can watch the Tigers - Rays game.

Good news, guys.
MLB heard us, and now the GT-7000N is a supported device.
Already watched a game from my Red Sox yesterday, picture quality is great over Wifi.
Thanks for everyone who contacted them and made this happen.