Develop Bugs

[IDEA] View all apps in the Marketplace

So, I have read that it's an issue with all Froyo ROM's on the EVO... You can't see paid/protected apps in the Marketplace; supposedly, the apps not showing are not verified to work on Froyo.
Could someone just patch the build_prop like they did on the Nexus One before Google released the official fix?
N1 Fix Thread for Reference: http://forum.xda-developers.com/showthread.php?t=693102
If anyone wants to tackle it, the dev of the N1 fix explained what needs to be done here: http://forum.xda-developers.com/showthread.php?t=693102
I don't have an EVO, nor am I much of a developer; but I just rooted my friend's EVO and was looking for a fix for him when I realized that the N1 had a very similar issue when it was running leaked versions of Froyo.
Just throwing it out there... I could be way off.

I think this should be easy to do. Theoretically you should be able to take buildprop swticher v0.3.1.zip and replace /buildprop/build.2.1 with the build.prop from stock and /buildprop/build.2.2 with the build.prop from CM6 and then follow the directions from that post.
I'm about to test it out myself and see if it works...

Let me know... If it does, could you post the build.prop files that you used?
EDIT: Awesome to see another SC member!

Okay, first attempt boot looped. I think build.2.1 needs to be a 2.2 build.prop modified to look like 2.1 because the stock 2.1 build.prop won't work with 2.2. Should've looked at that more instead of rushing Going to see if I can find the lines to change real quick, gotta go back to work in a few minutes...
It also cleared my Google Account settings haha... trying a new modification but may not be able to upload anything until tonight!

Thanks for your help... Can you post your build.props before going back to work? If so, I will try to work on this more if you aren't able to get it before going back.
Thanks

Just printed and compared the build.props for the N1 fix and see that there are only 2 lines that were changed. If someone wants to provide me with a 2.1 build.prop and the CM6 build.prop, I might be able to get this working.

Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6

Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
I was just about to post saying what I tried didn't work and I was hoping you'd pop in here. I was thinking about digging into it more this weekend but if you haven't been able to get anywhere I doubt I could either.

Well... that blows... Sorry guys
Wish I could've been of more help!

Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data

Geniusdog... what all does the ro.build.fingerprint line do?

spiicytuna said:
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Click to expand...
Click to collapse
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version

Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
We need a setting like most of the android browsers to allow us to spoof ourselves as stock 2.1 EVO.

Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet

ok this is what we did on the Hero when we was with 1.5 and got the leak of 2.1 the market didnt show all the apps so we just change it with the nexus one, so i am guessing maybe we can get a 2.2nexus one build.prop and push it to the Evo, make sure to clear the market chache though , it took like 5-6hours for the apps to start showing up on the Hero!! just an Idea

jabbawalkee said:
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
Click to expand...
Click to collapse
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.

datajosh said:
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
Click to expand...
Click to collapse
bootlooops
Edit: nvm, was incomplete.

Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
It takes some changes to get the phone to boot with them, or to get radio access with them.
I've already tried a stock Nexus fingerprint, but it still doesn't give access. Like I said, I even pushed the file before even booting the phone (I.E, wipe, flash CM6, push file in recovery, then reboot) and it still didn't work.

Ava's build prop comes up, but no Market. Something else is going on.

Geniusdog254 said:
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
Click to expand...
Click to collapse
Duh, forgot it was Sense for a minute there. I feel like looking into it more but I'm not sure if anyone's going to find a solution.

[Q] change build.prop

Hello.
Can you help me how to change build.prop to bypass activation screen?
cmlusco mention that it is possible to do it.
Thanks
P.S.
cmlusco if your online please help me

gaiger said:
Hello.
Can you help me how to change build.prop to bypass activation screen?
cmlusco mention that it is possible to do it.
Thanks
P.S.
cmlusco if your online please help me
Click to expand...
Click to collapse
I have absolutely no experience with that however, I did a search on Google and this thread popped up. All I searched for was "how to edit build.prop":
http://forum.xda-developers.com/show....php?t=1236732
Anyone feel free to verify/correct me as I have never edited my build.prop before and I don't intend to. This is for anyone who may be looking for an answer. I won't say it is the answer as I've never done this before but hopefully this helps someone get on the proper train of thought.

if you're rooted try removing or renaming the phone.apk in /system/app. Make a copy of the ROM .zip to flag the original first in case something doesn't work ans definitely a backup in cwm. This should disable the activation nag and data phone capabilities. Not a good idea if you want to use it as a phone.
Sent from my Galaxy Nexus using Tapatalk

tiny4579 said:
if you're rooted try removing or renaming the phone.apk in /system/app. Make a copy of the ROM .zip to flag the original first in case something doesn't work ans definitely a backup in cwm. This should disable the activation nag and data phone capabilities. Not a good idea if you want to use it as a phone.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
if you mean i'm using my phone for text and call because i can't use them here in ph. there is no verizon carrier here in ph. sir tiny may i know what will disable after i edit the phone.apk?
Sent from my MT11i using Tapatalk

gaiger said:
if you mean i'm using my phone for text and call because i can't use them here in ph. there is no verizon carrier here in ph. sir tiny may i know what will disable after i edit the phone.apk?
Sent from my MT11i using Tapatalk
Click to expand...
Click to collapse
If you can't use your phone for text,data,and talking, you can disable it as it essentially disables the ROM's use of the cell's radio (wifi should still work).
Couple ways to do it:
1. remove the phone.apk from the zip and transfer new zip to sdcard and wipe system in recovery and re-flash rom.
2. Using root explorer or some kind of app that can write to /system, delete or rename the Phone.apk found in /system/app and reboot. If you get force close messages, just battery pull and boot the phone up again.
And, no there's no editing of the file itself just making the android system not able to find it. Not officially supported by devs to disable the radio but if you're having struggles to skip activation it is definitely worth a shot.

tiny4579 said:
If you can't use your phone for text,data,and talking, you can disable it as it essentially disables the ROM's use of the cell's radio (wifi should still work).
Couple ways to do it:
1. remove the phone.apk from the zip and transfer new zip to sdcard and wipe system in recovery and re-flash rom.
2. Using root explorer or some kind of app that can write to /system, delete or rename the Phone.apk found in /system/app and reboot. If you get force close messages, just battery pull and boot the phone up again.
And, no there's no editing of the file itself just making the android system not able to find it. Not officially supported by devs to disable the radio but if you're having struggles to skip activation it is definitely worth a shot.
Click to expand...
Click to collapse
this would be my last resort. im getting fraustrated because its almost a month finding a solution how to bypass this activation screen. thanks sir tiny you're a great help for me
hmmm... for some reason can i change the phone.apk to default setting?
Sent from my MT11i using Tapatalk

I believe if you just press the home button a TON then it should work
Sent from my ADR6425LVW using XDA App

You're talking about the screen that comes up when you first turn the phone on after you first buy the phone?
There's a way to do it without changing the build.prop, I'll look for it. I actually did it when j first got my phone.
Some people have said if you tap the top left, top right, bottom right, and bottom left corners in that order it bypasses it.
It works for some, the way I did it involved dialing some **number and changing somethings to 0000000
Sent from my ADR6300 using XDA App
---------- Post added at 05:10 PM ---------- Previous post was at 04:36 PM ----------
Here I found a link to where it says how to tap the corners
http://www.androidcentral.com/bypass-activation-screen-your-android-device
And I found the way I was talking about when you call **778 and change the settings
1. Select emergency call and dial ##778.
2. Select edit and enter service password 000000.
3. Select NAM Settings.
4. Change Mobile Directory number to 0000000000 (Ten digits).
5. Change MIN1 to 0000000 (Seven digits).
6. Change Mobile Country Code to 000 (Three digits).
7. As you back out "Commit the Change".
8. The phone will auto reboot in 10 seconds.
#2 works permanently as I remember and it's pretty easy to do.

[App] Fix S-Voice Network Error W/ Download Link (Root Explorer Fix)

USE AT OWN RISK
Download S-Voice - not modded apk
download and install like you would any other app
Fix S-Voice Network Error
After installing the S Voice app, use a root explorer app to edit your build.prop
Change...
ro.product.model= ( your Phone )
To
ro.product.model=GT-I9300
and also change
ro.product.device=GT-I9300
HowTo Manually Edit your build.prop File.
Open Root Explorer
Scroll down to your /system directory and tap on it.
At the top of the screen tap the button that says 'Mount R/W' (it will change to 'Mount R/O')
Long press on your build.prop file and select 'Open In Text Editor'.
Your build.prop file is now fully editable, please pay attention to what you are changing!
Make Changes
Hit back twice, Root Explorer will ask you to save it. Tap 'yes'.
Reboot
Root Explorer (File Manager) - Android Apps on Google Play

It works but what about everything you want it to do locks up? Set alarm..lock up. Maps, lock up. Lol does anything work?
sent from Transformer Prime cranking it out with WSG customs.

Scuddster said:
It works but what about everything you want it to do locks up? Set alarm..lock up. Maps, lock up. Lol does anything work?
sent from Transformer Prime cranking it out with WSG customs.
Click to expand...
Click to collapse
From what JC tested on Venum Ice, that's kind of what it only does... Lol
Sent from my SPH-D710 using xda premium

i used the command navigate to (Location)
and it worked
i believe the alarm part does not work cause it depends on the clock from gs3

you should try the modded apk then cause not having any of those issues with that apk.

but u have to force install that apk file by coping it to system and changing permissions
that is to hard for some people

Es file explorer, super manager are easy to use not hard at all

if you want to post the file link to the other apk and detailed instructions i will add it to op

is the link in the OP the modded apk?

no

changed post to reflect not modded apk

htls said:
changed post to reflect not modded apk
Click to expand...
Click to collapse
thats what im saying.. when modded apk is posted id try that. i had it but uninstalled already and didnt back it up. but it is good to have two options.. if its too hard to set permissions they can take your route .. i personally only used it to check weather lol.. and i did ask this:
Sent from my SPH-D710 using XDA

Beware anyone changing their build.prop. Some apps wont run like mobile odin and some other apps may not install, just saying. AND WHATS UP Rob. I hope you and your family are well man!!!
Sent from my SPH-D710

Will this work on gb, blazer 4.1?

your stupid fix ****ed up my phone. i rebooted it and now it only goes past the "boot" screen and goes black and that's it. it wont boot at all... just great! :0/.

draconx said:
your stupid fix ****ed up my phone. i rebooted it and now it only goes past the "boot" screen and goes black and that's it. it wont boot at all... just great! :0/.
Click to expand...
Click to collapse
You do know every thing we do in here is at your own risk. You could of said hey I am running blah blah blah rom and did the fix but it wont let my phone boot up. So that others reading this would know that there are even more risks... Jus' Sayin'
Hope you get back up and running

wow .. it works ... thanks buddy .. last day i installed SVoice but frustrated bcz it didnt work .. now it works ..

playya said:
You do know every thing we do in here is at your own risk. You could of said hey I am running blah blah blah rom and did the fix but it wont let my phone boot up. So that others reading this would know that there are even more risks... Jus' Sayin'
Hope you get back up and running
Click to expand...
Click to collapse
your right, i apologize, I'm on CM9 alpha 4. epic 4g touch. and i did this "fix" and it wouldn't let me boot my phone so i had to re insatll the CM9 rom through odin to get it to boot again.
try it out if you guys want but make sure you have odin and whatever rom your currently on.

draconx said:
your stupid fix ****ed up my phone. i rebooted it and now it only goes past the "boot" screen and goes black and that's it. it wont boot at all... just great! :0/.
Click to expand...
Click to collapse
Hahaha couldn't help but laugh. Playya is right OPs are not responsible for what happens to your phone.

Should I revert back to the old build.prop before flashing a different rom?
Edit: So I did some reading and figured it out. Sometimes it's better to look for the answer on ur own. Ignorance is not bliss!

[Q] AOKP mms.apk on Stock 4.0.4

I know it isn't possible to copy and paste the apk from AOKP to Stock 4.0.4 rooted due to some sort of signature. My question is, how can I make it happen? Any all input of helping, non-sarcastic manner will be much appreciated.

If your trying to transfer the AOKP version of MMS app to the stock 4.0.4 then you better make sure that they are compatible!!
Certain apps need certain things in the ROM system to run it. And the stock may not have that. You could try it though (its not gonna hurt your phone) it just will probably force close. If you want to know how to get it then this his how!
Step 1: Get apk file!
Step 2: Connect phone to computer
Step 3: Transfer APK to phone
Step 4: Disconnect phone
Step 5: Open ES File Manager (Get if from Play Store if you don't have it)
Step 6: Find your apk (make sure Unknown sources is enabled)
Step 7: Install it!
And thats it. I hope this helps out a lot!!

Cant be done. You can push it to system/app fix permissions but will not send the text. FC after.. Opening it, going to settings works but not sending. It relies on framework i believe.. Neither cm or aokp mms.apk wont work.. You could use the market ones but one has ads and the other mms is broken..

noodles2224 said:
Cant be done. You can push it to system/app fix permissions but will not send the text. FC after.. Opening it, going to settings works but not sending. It relies on framework i believe.. Neither cm or aokp mms.apk wont work.. You could use the market ones but one has ads and the other mms is broken..
Click to expand...
Click to collapse
Correct... due to framework restrictions it will not work properly but quite sure you can find a ROM with AOSP parts that's stock based
Sent from my SGH-T989 using Tapatalk 2

playya said:
Correct... due to framework restrictions it will not work properly but quite sure you can find a ROM with AOSP parts that's stock based
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Interesting, so it can work if you find THE ROM?? which one?

[Request] Secret Flag Modified Google Search Apk

Question is, can someone modify the apk as below???
http://www.androidpolice.com/2013/0...-enable-voice-prompt-in-search-results-video/
Turns out, there's a secret flag within Search that lets you use the hotword, set by default to 'Google,' anywhere in search results instead of just the home Activity. By default, Search will let you say "Google" to activate voice input only in the main Search screen, after which you'd have to tap the Back button in order to use it again. It's nice, but it's not very fluid, as you have to keep touching your device.
The secret flag enables it in search results, so you can perform search after search after search without ever touching your phone or tablet.
As for the technical details, the flag is located in res/values/bools and is called hotword_from_results. To activate it, one would flip it from false to true, like so:
<bool name="hotword_from_results">true</bool>
Sent from my Nexus 4 using xda app-developers app

Wezi said:
Question is, can someone modify the apk as below???
http://www.androidpolice.com/2013/0...-enable-voice-prompt-in-search-results-video/
Turns out, there's a secret flag within Search that lets you use the hotword, set by default to 'Google,' anywhere in search results instead of just the home Activity. By default, Search will let you say "Google" to activate voice input only in the main Search screen, after which you'd have to tap the Back button in order to use it again. It's nice, but it's not very fluid, as you have to keep touching your device.
The secret flag enables it in search results, so you can perform search after search after search without ever touching your phone or tablet.
As for the technical details, the flag is located in res/values/bools and is called hotword_from_results. To activate it, one would flip it from false to true, like so:
<bool name="hotword_from_results">true</bool>
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I decompiled, made the above changes, recompiled with no errors, and got it to install but it force closes every time i try to open it. Maybe someone else can provide some insight. I used AutoAPKTool to make the edits

Cans someone resolve this? I'd do it myself but having tons of trouble getting my device to show on adb (after many tries, different methods)

I tried to make an Xposed module to patch it on the fly, but it is not working:
Code:
resparam.res.setReplacement("com.google.android.googlequicksearchbox", "boolean", "hotword_from_results", true);
upon starting the module, I get "Resource$NotFoundException", I tried other forms of the setReplacement method but none worked. I am still new to Xposed, so maybe I am doing this in a wrong way, attached are the sources of the Eclipse project in case someone can make it work.

If someone have the source of google now apk i can do something
I don't know if it's available, or also can be made from decompiling and recompile

firetrap said:
If someone have the source of google now apk i can do something
I don't know if it's available, or also can be made from decompiling and recompile
Click to expand...
Click to collapse
no you dont need source, just decompile. change the value, recompile. replace it
done.

Yes I know it's just iam working right now in my app and for me it's much easier to have the source I only had to import to eclipse than playing with apk tool etc in a few hours I will do that
Sent from my Nexus 4 using xda app-developers app

firetrap said:
Yes I know it's just iam working right now in my app and for me it's much easier to have the source I only had to import to eclipse than playing with apk tool etc in a few hours I will do that
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
you dont need to import to eclipse, all you do is just decompile it and change false to true.
you're making it so complicated on your part. i already did it, going to test it now it literally takes 30-45 seconds to do.

zephiK said:
you dont need to import to eclipse, all you do is just decompile it and change false to true.
you're making it so complicated on your part. i already did it, going to test it now it literally takes 30-45 seconds to do.
Click to expand...
Click to collapse
Yes but i was in the company desktop and here i don't have acess to apktool just because my company restricts the download site as dev host rapid share etc. now at home i had decompiled changed from false to true and recompiled and signed etc etc.. so i tested and the behaviour is the same are you guys sure that it's only change to do?! i think i had all perfect if you want i can upload the "modded apk"
EDIT: it doesn't work i don't know why here is the decompiled files and its true, i recompile sign and check manifest and all ok, but after install the behavior its the same
https://mega.co.nz/#!KZlVkIgS!FVLyrUXwtI4w5NHX22u7bWMcWZpEr5-7SydfU_fYX6M
Here the recompiled file i made you can test:
https://mega.co.nz/#!yJUjmYCC!fancLR6DwIlQHxYmX9JmNzCJEPBmpLgkIFsTFw4e_jw
Maybe the guy from the "30-45" seconds have more time to debugg this

I just modded this and got it running w/o issue.
I'm on CM 10.2 so I had to do some adjusting as there was an update installed to /data/app, with the original in /system/app.
I just uninstalled the update via the Play Store, and then moved the original (for CM it's QuickSearchBox.apk to QuickSearchBox.apk.bak), and adb pushed the newly modded apk (attached), to /system/app.
After doing all that, BOOM goes the dynamite.
Works for me, YMMV.
Hotword Quick Search

JsChiSurf said:
I just modded this and got it running w/o issue.
I'm on CM 10.2 so I had to do some adjusting as there was an update installed to /data/app, with the original in /system/app.
I just uninstalled the update via the Play Store, and then moved the original (for CM it's QuickSearchBox.apk to QuickSearchBox.apk.bak), and adb pushed the newly modded apk (attached), to /system/app.
After doing all that, BOOM goes the dynamite.
Works for me, YMMV.
Hotword Quick Search
Click to expand...
Click to collapse
Any way to do this without using ADB? (Having tons of trouble getting my SGS3 to be recognized). Tried installing the apk by itself but the installation fails.

trein91 said:
Any way to do this without using ADB? (Having tons of trouble getting my SGS3 to be recognized). Tried installing the apk by itself but the installation fails.
Click to expand...
Click to collapse
Are you rooted? I needed to make this a system app, as mentioned, to avoid signature conflicts, etc.
If so, I can make a zip to install to /system/app for you. I don't think it will work (as you have discovered), if you try and install as a standard app to /data/app, which is what clicking the download link and attempting to install is doing.

JsChiSurf said:
Are you rooted? I needed to make this a system app, as mentioned, to avoid signature conflicts, etc.
If so, I can make a zip to install to /system/app for you. I don't think it will work (as you have discovered), if you try and install as a standard app to /data/app, which is what clicking the download link and attempting to install is doing.
Click to expand...
Click to collapse
Please make a flashable zip, would love to try it
Sent from my Nexus 4 using xda app-developers app

OK. So I didn't have any files in data/app so I went ahead and just made quixksearchbox a .bak, and pushed new one after renaming it and setting permissions. Its working great.
I'm on PA
Sent from my Nexus 4 using Tapatalk 4

Here's a flashable zip. Though, because it has to place the APK in the /system/ folder (partition), the zip (out of the box), is only likely to work on the Nexus 4, since mount points are going to differ by phone. Any other phone you'll have to modify the script.
As mentioned previously, if you want to try and flash, FIRST, be sure to uninstall 'Google Search' from the play store.
Since I don't think there is a way to move a file in edify, and I'm too lazy to include a shell script to run a move command, I instead delete QuickSearchBox.apk if it is in your /system/app/ folder (instead of backing it up if you want to restore later), and then copy over qs.apk (the modded version).
I restored to original, ran the above process on CM 10.2, and got the results expected / desired (i.e. the attached zip is confirmed working in my setup).

It works on PA 3.99. However you'll need to set voice to US English or it won't work.
Sent from my Nexus 4 using Tapatalk 2

Anon87 said:
It works on PA 3.99. However you'll need to set voice to US English or it won't work.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Would be nice if this could be activated with any language.
Is it possible by changing any other flag?

JsChiSurf said:
Are you rooted? I needed to make this a system app, as mentioned, to avoid signature conflicts, etc.
If so, I can make a zip to install to /system/app for you. I don't think it will work (as you have discovered), if you try and install as a standard app to /data/app, which is what clicking the download link and attempting to install is doing.
Click to expand...
Click to collapse
Good Afternoon,
I am getting FCs after flashing the app. I am using a stock rooted ROM
I removed Google Search< restarted the phone<verify Googgle search was removed< flashed zip<rebooted phone<open app<set up account<FCs
anyone got a suggestion to get it working,

Lento10 said:
Good Afternoon,
I am getting FCs after flashing the app. I am using a stock rooted ROM
I removed Google Search< restarted the phone<verify Googgle search was removed< flashed zip<rebooted phone<open app<set up account<FCs
anyone got a suggestion to get it working,
Click to expand...
Click to collapse
Is the ROM odexed?

jarjar124 said:
Is the ROM odexed?
Click to expand...
Click to collapse
Deodex stock rom
Sent from my Nexus 4 using XDA Premium 4 mobile app