How to get MORE incompatible apps to work with the vivid. - HTC Vivid, Raider, Velocity

Ok, well a while back i found a post somewhere in the forums that showed me how to get incompatible apps to work with our vivids (involved changeing stuff in build.prop from holiday to pyramid). Well, some apps were STILL incompatable/not showing up in the marketplace. (ex. Galaxy On Fire 2) So, this should help you guys out.
Change:
ro.product.model=HTC PH39100 and the one that says HTC Holiday
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
ro.product.manufacturer=HTC
ro.build.product=holiday
TO:
ro.product.model=GT-N700
ro.product.brand=samsung
ro.product.name=GT-N700
ro.product.device=galaxynote
ro.product.board=MSM8960
ro.product.manufacturer=samsung
ro.build.product=galaxynote
stole from ONE X forums
http://forum.xda-developers.com/showthread.php?t=1714298

Related

Favorite keyboard?

I'm curious about how people type on their tablets. I tend to use mine in portrait mode with Swype. I've seen a lot of people talking about the Gingerbread keyboard and wonder if it (or another offering) would be better. Before I go getting FCs or spending on the paid ones, what are people here using for keyboards?
-=Sent from my ViewSonic G Tablet (VEGAn) using Tapatalk=-
I've been trying several, including Ultra and Smart. Ultra wasn't bad, but support seems slim. I do like Smart (using it now ), and they have a support forum, etc.
Jim
i
I use thumb keyboard. They have a layout option just for tablets that's awesome.
I found it by searching " tablet" on appbrain app. The apps is not free, cost 1 euro well worth it.
popezaphod said:
I'm curious about how people type on their tablets. I tend to use mine in portrait mode with Swype. I've seen a lot of people talking about the Gingerbread keyboard and wonder if it (or another offering) would be better. Before I go getting FCs or spending on the paid ones, what are people here using for keyboards?
-=Sent from my ViewSonic G Tablet (VEGAn) using Tapatalk=-
Click to expand...
Click to collapse
I finally gave up on trying swype a couple of weeks ago after hours of aggravation. How did you get it loaded? I originally did the Rothnic, buil-prop edit and lib core copy with the adb sywpe push. I've tried a few dozen different times but finally gave up. Haven't tried it on the VegaN yet. What did you do?
it2steve said:
I finally gave up on trying swype a couple of weeks ago after hours of aggravation. How did you get it loaded? I originally did the Rothnic, buil-prop edit and lib core copy with the adb sywpe push. I've tried a few dozen different times but finally gave up. Haven't tried it on the VegaN yet. What did you do?
Click to expand...
Click to collapse
What firmware were you running when you tried? Was it TNT or TNT lite?
Jim
it2steve said:
I finally gave up on trying swype a couple of weeks ago after hours of aggravation. How did you get it loaded? I originally did the Rothnic, buil-prop edit and lib core copy with the adb sywpe push. I've tried a few dozen different times but finally gave up. Haven't tried it on the VegaN yet. What did you do?
Click to expand...
Click to collapse
I keep the Swype files on my Tablet. Every time I flash a new ROM, I copy the app and lib files and change permissions on them to rw-r--r-- using Root Explorer. Then I copy the Rothnic text from a text file and replace the appropriate text in build.prop again using Root Explorer. Reboot, go to a text field, long click and select Swype.
I've done the above on tech VEGAn beta and it works like a charm. Of course, if I could just buy Swype I would... or something better, hence my post.
-=Sent from my ViewSonic G Tablet (VEGAn) using Tapatalk=-
popezaphod said:
I keep the Swype files on my Tablet. Every time I flash a new ROM, I copy the app and lib files and change permissions on them to rw-r--r-- using Root Explorer. Then I copy the Rothnic text from a text file and replace the appropriate text in build.prop again using Root Explorer. Reboot, go to a text field, long click and select Swype.
I've done the above on tech VEGAn beta and it works like a charm. Of course, if I could just buy Swype I would... or something better, hence my post.
-=Sent from my ViewSonic G Tablet (VEGAn) using Tapatalk=-
Click to expand...
Click to collapse
wait, there is a way to use swype? are the instructions in a thread somewhere? been trying to get swype to work for the longest.
SlideIT
Although it takes up a huge amount of real estate on the screen, I'm kind liking SlideIT, which is a poor man's Swype clone (I use my beta Swype access on my evo). You should be able to dl from the market and apply without any hassle.
Xander Crews said:
Although it takes up a huge amount of real estate on the screen, I'm kind liking SlideIT, which is a poor man's Swype clone (I use my beta Swype access on my evo). You should be able to dl from the market and apply without any hassle.
Click to expand...
Click to collapse
yea i was using slideit. sucks that it takes up the whole screen and the letters are just insanely huge on the screen in landscape mode.
on that note, ultra keyboard is much better. the keyboard is small in landscape (although its stuck on the left side) and it doesn't take up the whole screen. also it recognizes more words (like curse words) without having to add them first. score for me. lol
gotwillk said:
wait, there is a way to use swype? are the instructions in a thread somewhere? been trying to get swype to work for the longest.
Click to expand...
Click to collapse
+1! Been looking for a working Swype on this thing since the day I got it!
gotwillk said:
wait, there is a way to use swype? are the instructions in a thread somewhere? been trying to get swype to work for the longest.
Click to expand...
Click to collapse
Yes, there is, but we aren't -supposed- to talk about it. I believe we had a howto thread early on and Swype asked xda to yank all hacking threads, so they did.
If you Google it, you should find a howto on the tegratab forums. That's how I found out how to do it.
I personally don't care what Swype says, I got it on my Droid 2 and don't use it there, so I "moved" it from the Droid 2 to the GTab.
jonagpa said:
I use thumb keyboard. They have a layout option just for tablets that's awesome.
I found it by searching " tablet" on appbrain app. The apps is not free, cost 1 euro well worth it.
Click to expand...
Click to collapse
I can second that. Using it now
GB
I really love using the Gingerbread keyboard on my Gtab. I've always used the stock Android keyboard since I got my N1 so I'm used to the layout, plus I like having the emoticons.
Whenever I switched to different roms, like an HTC Sense rom, etc., I always hated the other keyboards. I could never get used to Swype either.
popezaphod said:
I keep the Swype files on my Tablet. Every time I flash a new ROM, I copy the app and lib files and change permissions on them to rw-r--r-- using Root Explorer. Then I copy the Rothnic text from a text file and replace the appropriate text in build.prop again using Root Explorer. Reboot, go to a text field, long click and select Swype.
I've done the above on tech VEGAn beta and it works like a charm. Of course, if I could just buy Swype I would... or something better, hence my post.
-=Sent from my ViewSonic G Tablet (VEGAn) using Tapatalk=-
Click to expand...
Click to collapse
I'm running VEGAn Beta 3 and got Swype installed using the rothnic reference on tegratab, but when changing to Swype input received the message:
"The Swype package you installed is configured for another device and will operate with limited functionality."
So the typing part of the keyboard works, but not the "swyping" part. I'm thinking there must be something in the build.prop that still doesn't look like the Samsung Galaxy Tab. This is the top of my build.prop. Do you have something different in your build.prop on VEGAn to get Swype working?
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF91
ro.build.display.id=harmony 2.2 FRF91 20101123.172729
ro.build.version.incremental=20101123.172729
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Tue Nov 23 17:28:06 CST 2010
ro.build.date.utc=1290504486
ro.build.type=eng
ro.build.user=root
ro.build.host=Sprint14
ro.build.tags=test-keys
ro.product.model=SPH-P100
ro.product.brand=sprint
ro.product.name=SPH-P100
ro.product.device=SPH-P100
ro.product.board=SPH-P100
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SPH-P100
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=harmony-eng 2.2 FRF91 20101123.172729 test-keys
# ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
# end build properties
nochancenine said:
So the typing part of the keyboard works, but not the "swyping" part. I'm thinking there must be something in the build.prop that still doesn't look like the Samsung Galaxy Tab. This is the top of my build.prop. Do you have something different in your build.prop on VEGAn to get Swype working?
Click to expand...
Click to collapse
On my VEGAn, I did this:
Code:
# begin build properties
# autogenerated by buildinfo.sh
[b]ro.build.id=FROYO[/b]
ro.build.display.id=harmony 2.2 FRF91 20101123.172729
ro.build.version.incremental=20101123.172729
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Tue Nov 23 17:28:06 CST 2010
ro.build.date.utc=1290504486
ro.build.type=eng
ro.build.user=root
[b]ro.build.host=Sprint14[/b]
ro.build.tags=test-keys
[b]ro.product.model=SPH-P100[/b]
[b]ro.product.brand=sprint[/b]
[b]ro.product.name=SPH-P100[/b]
[b]ro.product.device=SPH-P100[/b]
[b]ro.product.board=SPH-P100[/b]
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
[b]ro.product.manufacturer=samsung[/b]
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
[b]ro.build.product=SPH-P100[/b]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=harmony-eng 2.2 FRF91 20101123.172729 test-keys
# ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
# end build properties
and it works.
DanielNTX said:
On my VEGAn, I did this:
Code:
# begin build properties
# autogenerated by buildinfo.sh
[b]ro.build.id=FROYO[/b]
ro.build.display.id=harmony 2.2 FRF91 20101123.172729
ro.build.version.incremental=20101123.172729
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Tue Nov 23 17:28:06 CST 2010
ro.build.date.utc=1290504486
ro.build.type=eng
ro.build.user=root
[b]ro.build.host=Sprint14[/b]
ro.build.tags=test-keys
[b]ro.product.model=SPH-P100[/b]
[b]ro.product.brand=sprint[/b]
[b]ro.product.name=SPH-P100[/b]
[b]ro.product.device=SPH-P100[/b]
[b]ro.product.board=SPH-P100[/b]
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
[b]ro.product.manufacturer=samsung[/b]
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
[b]ro.build.product=SPH-P100[/b]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=harmony-eng 2.2 FRF91 20101123.172729 test-keys
# ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
# end build properties
and it works.
Click to expand...
Click to collapse
and you got swiping to work?
DanielNTX said:
On my VEGAn, I did this:
Code:
# begin build properties
# autogenerated by buildinfo.sh
[b]ro.build.id=FROYO[/b]
ro.build.display.id=harmony 2.2 FRF91 20101123.172729
ro.build.version.incremental=20101123.172729
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Tue Nov 23 17:28:06 CST 2010
ro.build.date.utc=1290504486
ro.build.type=eng
ro.build.user=root
[b]ro.build.host=Sprint14[/b]
ro.build.tags=test-keys
[b]ro.product.model=SPH-P100[/b]
[b]ro.product.brand=sprint[/b]
[b]ro.product.name=SPH-P100[/b]
[b]ro.product.device=SPH-P100[/b]
[b]ro.product.board=SPH-P100[/b]
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
[b]ro.product.manufacturer=samsung[/b]
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
[b]ro.build.product=SPH-P100[/b]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=harmony-eng 2.2 FRF91 20101123.172729 test-keys
# ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
# end build properties
and it works.
Click to expand...
Click to collapse
Thanks! This is the one last line I needed to change in my build.prop from FRF91 to FROYO:
Code:
ro.build.id=FROYO
Now both typing and swyping works!
undyingsum said:
I really love using the Gingerbread keyboard on my Gtab. I've always used the stock Android keyboard since I got my N1 so I'm used to the layout, plus I like having the emoticons.
Whenever I switched to different roms, like an HTC Sense rom, etc., I always hated the other keyboards. I could never get used to Swype either.
Click to expand...
Click to collapse
How does the Gingerbread keyboard look on your tablet? I loaded it on mine and my Droid 2, and it looks squashed on both devices.
KnightCrusader said:
How does the Gingerbread keyboard look on your tablet? I loaded it on mine and my Droid 2, and it looks squashed on both devices.
Click to expand...
Click to collapse
isn't that normal though? because the buttons are like half sized on mine. its much smaller than in portrait mode. but i thought that was by design so you get more screen space.
Seriously, guys - if you like the Gingerbread keyboard, have a look at Thumb Keyboard.
It's only €1 and really worth it - there's a "Gingerbread" theme and a 10in tablet mode - it really does make the perfect keyboard for the size of the device.
Don't go on the pictures on the Market listing - give it a go!
You can also get a refund if you're quick!

Netflix not showing up in market?

I've tried pretty much every rendition of the build.prop fixes. Changed my foot print 3 times, and still no luck.
My current build.prop looks like this:
Code:
ro.product.name=htc_supersonic
ro.product.device=htc_supersonic
ro.product.board=htc_supersonic
ro.product.cpu.abi=armeabi-v7a
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zoom2
ro.build.sourceversion=full
ro.build.description=1.0.1.278.int.enc.rrdp.s30428
ro.build.fingerprint=sprint/htc_supersonic/htc_supersonic:2.3.3/GRI40/102588:user/release-keys
Any ideas or tips? I want mah nookflix!
Sorry i didn't know technical terms what you are talking about. If Netflix app is not working with your or you are searching for Netflix .apk file its available at http://goo.gl/eFsXZ

8.9 build.prop question

I've got my 8.9 KFHD rooted and installed the Google Play store.
Is there a build.prop edit that will open up the tablet to some of the incompatible apps that won't break stuff like the amazon store, or the kindle reader app?
gunnyman said:
I've got my 8.9 KFHD rooted and installed the Google Play store.
Is there a build.prop edit that will open up the tablet to some of the incompatible apps that won't break stuff like the amazon store, or the kindle reader app?
Click to expand...
Click to collapse
The only workaround I've found so far is to download them on another device, copy the .apk from /data/app or /system/app and side load it. Dropbox becomes real handy for this sort of thing. Of course, not everyone has the luxury of having a second device . . .
Thanks That's what I've been doing. Thanks to a rooted Nexus 7 and a Galaxy S 3
gunnyman said:
Thanks That's what I've been doing. Thanks to a rooted Nexus 7 and a Galaxy S 3
Click to expand...
Click to collapse
Has anyone found a way to mod the build.prop or can somebody please upload the original for me? I tried to make mine into a neus 7 but it no workie.. Also aloty of my apps randomly stopped working. Like Splashtop, epse, asphault 7, etc.
Thanks!
give me a clean 8.9 kindle fire hd build.prop and i m going to modify it, and make a 8.9 tweak post!
Seriously, please guys. I mines broken.
i release a tweak for 8.1.4 8.9 kindle fire hd!. if you want other version give me that version build.prop. search my tweaks in 8.9 develop

[Q] GTA Vice City on the Sprint HTC One?

I'm pretty annoyed at the fact that my Motorola Photon and GS3 both supported Vice City, but my HTC One can't.
I've seen several videos on YouTube of the HTC One running Vice City - I'm not sure which variant of the HTC One, but regardless if it's CDMA or GSM, they essentially have they processing/graphics capabilities.
I've been trying to get it running by following these crappy instructions, but still no luck.
Anybody know why Vice City is still labelled "incompatible" on the Sprint HTC One? Also, has anyone gotten Vice City to run on their HTC One??
I think it's the 1080p screen.
FWP: Screen res too high, can't play games.
sauprankul said:
I think it's the 1080p screen.
FWP: Screen res too high, can't play games.
Click to expand...
Click to collapse
If that were the case, why is it running on the GS4?
Try sideloading it you can get the apk from another supported device and just transfer it
Sent from my HTCONE using xda premium
go into your build.prop and amend the following lines to look like this
ro.product.brand=
ro.product.model=
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
save it, reboot
and youll see it in the market afterwards
after you download it i think you can set it back to what it was before
its all a build.prop thing.

[Q] Watch ESPN App Recognizes HD+ as Phone

I have a Nook HD+ running SlimKat 4.4.4. The WatchESPN app has been running well for the most part. However, the app has a restriction that only allows Monday Night Football to be watched on desktops or tablets - not on phones. The app is recognizing my Nook HD+ as a phone and therefore is not allowing me to watch these certain broadcasts.
Does anyone know how to have my device actually be recognized as the tablet that it is? I have limited knowledge on where to look, but what I found so far that I thought may be relevant is that in the build.prop are the following properties:
ro.build.characteristics = tablet
ro.product.device = ovation
ro.product.brand = Android
ro.product.manufacturer = Barnes & Noble
ro.product.model = BN NookHD+
ro.product.name = slim_ovation
Thanks for the help.
You must backup original build.prop.
And change only model and brand.
Try this.
Galaxy tab 8.4 (wifi)
ro.product.model=SM-T320
ro.product.brand=samsung
com35 said:
You must backup original build.prop.
And change only model and brand.
Try this.
Galaxy tab 8.4 (wifi)
ro.product.model=SM-T320
ro.product.brand=samsung
Click to expand...
Click to collapse
Thank you for the input, I will try this out.

Categories

Resources