On my esteem I would just go to application manager - user apps. But on this phone I can't find it at all. I need to save the google maps .apk to my sd card because slim rom doesn't let u download maps from the market (unsupported device) so I wanted to just open the .apk once I saved it. Thanks in advance
I want to know the answer to your question aswell but i think I know a solution to your problem: modded playstore apk
Some roms that change dpi and stuff need a modded apk that will ignore the change in dpi. I'm not completely sure but I think that's your solution
Just put it on the sdcard, use file manager and navigate to it. Make sure you have the option to install from unknown sources. Should be in security in settings.
I have an app named "Apk Manager Plus." It lets you save all of your apk files from all of your apps to back them up. There is another app named "Apk Share" that lets you send the apk files where you want.
^^ that and ya will only be allowed to move/copy/delete/rename only if ya rooted so with that being said use a file manager such as es file manager for ya free app users. if not use either root explorer or root browser those are the best for me.
^^ that and ya will only be allowed to move/copy/delete/rename only if ya rooted so with that being said use a file manager such as es file manager for ya free app users. if not use either root explorer or root browser those are the best for me.
Maybe I am reading wrong but he can't download it from the market so no, it would not go to that location on his phone. He is asking how to install it from his sdcard.
so meaning he hasnt downloaded it yet but thanks for pointing that out maybe we can upload it the file here for him.
lol its a lil confusing we dont know if he needs help saving it or downloading it or finding the app on his phone but either way lets see what we can do to help him.
yea he said on the last sentence so meaning he hasnt downloaded it yet but thanks for pointing that out maybe we can upload it the file here for him.
lol its a lil confusing we dont know if he needs help saving it or downloading it or finding the app on his phone but either way lets see what we can do to help him.
yes they do but perhaps whats not being edited and ive seen this in many ported roms is the ro.product.model= in build.prop
for example ive tried some of the ported roms such as the jellybean wicked rom or whatever its called and the model was left as the sprint's variant model which starts with sph- whatever and again i im not saying this could be the obsolute prob but its a good bet to test with. also edgeeze zip can replace the build.prop and other files to fix such issues. but i guess for those of ya using ported roms ya will need to find ways to work around it and trouble shoot such issues.
yes they do but perhaps whats not being edited and ive seen this in many ported roms is the ro.product.model= in build.prop
for example ive tried some of the ported roms such as the jellybean wicked rom or whatever its called and the model was left as the sprint's variant model which starts with sph- whatever and again i im not saying this could be the obsolute prob but its a good bet to test with. also edgeeze zip can replace the build.prop and other files to fix such issues. but i guess for those of ya using ported roms ya will need to find ways to work around it and trouble shoot such issues.
Yeah. Sounds like an incomplete build.prop. If anybody uses edgeez zip, it will boot and have the correct id, but they may lose or gain tweaks specific to their roms. Might be good or bad it's a crap shoot. Lol
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
ro.config.vc_call_vol_steps=7
# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# System property for cabl
ro.qualcomm.cabl=1
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048
[HIGH]
ro.product.model=SCH-R530M
ro.product.brand=samsung
ro.product.name=d2mtr
ro.product.device=d2mtr
[/high]
These values help apps figure out what device you have (by spoofing these is how most people got the 50GB's from box.net thanks to LG) and while they do help the market..
its these bad boys that tell teh google play store what device you have and what version. they might seem overwhelming at first but they can be broken down to easy to read parts.
[high]ro.build.description=d2mtr-user 4.1.2 JZO54K R530MVQAMB2 release-keys
ro.build.fingerprint=samsung/d2mtr/d2mtr:4.1.2/JZO54K/R530MVQAMB2:user/release-keys
[/HIGH]
ro.build.description= - This is the value we are setting d2mtr - the device we have user - this is a user build as opposed to engineering, this is what should be publicly available (note you can still have user builds that are in testing just shouldnt ever have eng builds that go public) 4.1.2 - cmon, if you cant figure this out you just need to leave JZO54K - this is the build number of the 4.1.2 source samsung used to compile this rom for our device R530MVQAMB2 - R530M is our model, VQA appears to go along with it (perhaps a carrier code?) and MB2 means that it was built on febuary 2nd 2013. Release keys means that they are keys signed off by google to be (hopefully) final versions of teh software, as every single software version needs to be approved by google as well. yea by every carrier and every android device... otherwise you arent getting into the google services.
i dont have a build.prop of the afflicted roms but im sure if you looked you should be able to see what the issue with them might be
keep in mind unless you have a "key" exactly the way its supposed to be then it will break the entire thing (as that isnt what google approved access to). so mixing and matching the keys will cause issues, you can use any devices you want though. i used to use the froyo froyo key on my old htc hero with cm6 to be able to get all teh new froyo apps since we didnt have froyo and thus didnt have a froyo key
edit: alrigth so i downloaded teh rom in question and looked in the build.prop
now basing off what i explained above can anyone see what MAY be cause the issue? im saying may as it could be completely unrelated you would need to have someone else test teh rom and see if it was one person or if it has been afflicting everyone with that rom.
No need for anyone to judge, this stuff doesnt just get learned overnight. unfortunately you are incorrect though, i could put teh build.prop in alphabetical order and it wouldnt matter it loads them all within a nano fraction of a second of each other and then boots the rom
now imagine how many people will read this post and learn what you just learned, you may have helped teach 6 or so people this tidbit that didnt know before, the only bad question is the one left unasked. as you never learn from that one
No need for anyone to judge, this stuff doesnt just get learned overnight. unfortunately you are incorrect though, i could put teh build.prop in alphabetical order and it wouldnt matter it loads them all within a nano fraction of a second of each other and then boots the rom
now imagine how many people will read this post and learn what you just learned, you may have helped teach 6 or so people this tidbit that didnt know before, the only bad question is the one left unasked. as you never learn from that one
anyways i was talking more of if you compare teh google versions and build id it says LJ1 which was teh launch firmware, so google play is getting told its a 4.1.2 device that is running 4.0.4 anyways ive msged the rom op and gave him a qucik fix on it all
Haha damn guys! The first reply answered my question but thanks for all the help that buildrop trick is cool, I didn't know about that. Thanks again guys
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
