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

Root App Compatibility Issues with Vortex + CM7

Narut0

Narut0

Member
What determines if an app is incompatible with the LG Vortex?

Is there another way to at least TRY to attempt to install it? Was wondering if I found the standalone .apk file and tried to install it, if it would work. I know this question is not directly related to rooting the Vortex, but I felt this section of the forum would have the best minds to ask.

I am rooted with Bobzhome's CM7 mod. I was hoping the upgrade to 2.3 would open up more options for applications but it seems that it hasn't made much of a difference, if any.

Are these applications simply impossible to install without stability issues due to the technology inside the phone?

The most recent app I've come across is the brand new Final Fantasy Airborne Brigade. It's a trading card game... yet is incompatible with the Vortex. Maybe it is the Mobage social software that also runs with it. I can't seem to install other games that run Mobage also.

Thank you for any input you can provide.
 
Here is what I know;

1. You'll see the same APPS in the market regardless of the ROM you are using, this is due too Google Play Market listing apps based on what model your phone is listed as. One thing that may change this, is if your phone is given a different model number via build.props.

2. Running a ROM CAN cause issues with apps, due too the fact, it is unsupported. But, it can also make apps, even though they are not 'technically' supportted, work. Then the issue is how too get them, inwhich you need a provider of the .apk itself.


I hope this helps, and I'll see if I can get an .APK for that game for you. I will test it out first aswell.
 
Thanks Jared, it would be cool if you find it, but don't go out of your way or anything. I just find it strange that a game that doesn't even have SOUND cannot even be attempted to install by normal means.

I've given up on trying to install flash. Nowadays it's not that big a deal anyway.

Also, gonna investigate that build.props idea, have you ever heard of that being effective?
 
Narut0 said:
Thanks Jared, it would be cool if you find it, but don't go out of your way or anything. I just find it strange that a game that doesn't even have SOUND cannot even be attempted to install by normal means.

I've given up on trying to install flash. Nowadays it's not that big a deal anyway.

Also, gonna investigate that build.props idea, have you ever heard of that being effective?
Click to expand...

Yes, a good example would be with the ROM I use for my Kindle Fire. There is an optional zip too be flashed that modifys the part that auto-generates the build.props. It then makes it a 'Galaxy Nexus' which allows a lot more apps too show up in the market, and too be installed. Although, some of them don't work. (One report.) Anyways, I'll see if I can create a .zip like his too modify the build.props.
 
Changed a few fields, but didn't make a difference. The settings did save though. I have tried to attach a screenshot of what my build.prop now looks like, and the fields that I have changed.

To be a little more specific, this is a list of what I have tried:
- Tried a few different devices, changing the 3 fields outlined in the screenshot to match
- Changed ES File Explorer back to Read Only for system memory
- Made sure to clear cache and data from Google Play
- Rebooted phone, tested, still incompatible

I believe it actually worked to fool Play, because whenever I reboot and get back to the home screen, it comes up with 9 new updates to install, which I was not receiving before. For this reason, I am now wondering if it has to do with pixel density or LCD density. A few sites stated that was also an issue with why apps were not compatible.
 

Attachments

  • buildpropfile1.png
    buildpropfile1.png
    59.2 KB · Views: 215
If you change one of these 2 fields to a smaller number, it's like changing the resolution of your PC monitor to a higher resolution.

qemu.sf.lcd_density=160
ro.sf.lcd_density=160

This is what build.prop has by default. I read that changing the second value is what counts....but I didn't notice a difference until I changed the one starting with qemu.

Changed it to 100 and there was definitely a noticeable difference. Too bad our screens are too small to take advantage of this. I will definitely remember this for my next phone though.

Don't forget to back up your build.prop and reboot after you modify it.

Still no solution to the app compatibility issue though :(
 
Just looking at your build.prop, it may have to do with the name, device, board and product, they are all still set to "thunderc", which Google Play will recognize as the Vortex and the Ally, which may be the source of all your problems.
 
Thanks Solid Snake, sneaking in at just the right moment...

This is what I ended up modifying, in red. Not sure if one or all is necessary, but it worked.

Haven't fully tested the app, but the fact that I now have the option to install it is what I was looking for.

If this makes it easier, here are the values I used in each of the fields, so you can copy and paste it in:

SGH-T959
Samsung
 

Attachments

  • buildprop-f.jpg
    buildprop-f.jpg
    170.5 KB · Views: 240
Erm, I thought that you could only change them via a flashable zip... Guess I was completely wrong. Anyways, good too hear the build.prop method worked for you.
 
Jared, it might still be helpful to create that zip file so it can easily be flashed. Reading through the other forums related to this issue, it seems a lot of people got confused while following directions....or worse, changed something they should not have and screwed up their phone.

Creating an easily flashable zip might be a good way for the rest of the community to take advantage of this feature.

Or... if you point me in the right direction I'll see if I can create it myself :D
 
Narut0 said:
Jared, it might still be helpful to create that zip file so it can easily be flashed. Reading through the other forums related to this issue, it seems a lot of people got confused while following directions....or worse, changed something they should not have and screwed up their phone.

Creating an easily flashable zip might be a good way for the rest of the community to take advantage of this feature.

Or... if you point me in the right direction I'll see if I can create it myself :D
Click to expand...

I'll see if I'm able too do so, anyways, Merry Christmas! (If you celebrate that, xD)
 
So, did some research, and I did find some good documentation on how to create flashable zips. I believe I have the basic concept down, but my first few attempts have not produced the results I was looking for.

First few times I kept getting syntax errors while trying to flash it, figured out that...I needed to hit ENTER after the last line (n00b mistake). So it actually went through after I figured that out. But after trying to flash it, and reboot, it'll show the first LG screen, it'll show the second LG screen, but then it reboots into recovery.

I have used both a modified version of the Vortex's build.prop for a Galaxy Nexus (figured that would be the best compatibility), and the one that worked for me in the screenshot above. Both kept rebooting back into recovery. I am thinking that maybe I need some sort of delete line to delete the current build.prop that is in the /system/ folder before it tries to move the new build.prop into its place?

I have uploaded the flashable zip. DO NOT USE IT UNLESS YOU CAN DO A NAND RESTORE. If anyone (Jared!) can take a look at it, would be much appreciated.

Thanks in advance.
 

Attachments

Narut0 said:
So, did some research, and I did find some good documentation on how to create flashable zips. I believe I have the basic concept down, but my first few attempts have not produced the results I was looking for.

First few times I kept getting syntax errors while trying to flash it, figured out that...I needed to hit ENTER after the last line (n00b mistake). So it actually went through after I figured that out. But after trying to flash it, and reboot, it'll show the first LG screen, it'll show the second LG screen, but then it reboots into recovery.

I have used both a modified version of the Vortex's build.prop for a Galaxy Nexus (figured that would be the best compatibility), and the one that worked for me in the screenshot above. Both kept rebooting back into recovery. I am thinking that maybe I need some sort of delete line to delete the current build.prop that is in the /system/ folder before it tries to move the new build.prop into its place?

I have uploaded the flashable zip. DO NOT USE IT UNLESS YOU CAN DO A NAND RESTORE. If anyone (Jared!) can take a look at it, would be much appreciated.

Thanks in advance.
Click to expand...

Ok, I'll look over this after I finish fixing a server for a friend. Anyways, you shouldn't need too tell it too delete the build prop that was there at the time, as my experience with linux is that when you specify a file too move, it will AUTOMATICALLY remove the old version and put the new on their. I think it's just an error in the way you did it, but I shall see later.
 
You must log in or register to reply here.
Back
Top Bottom