Related
Does anyone know how I might be able to port the desire hd browser? I love the pinch to bring up windows feature. I'm currently running Skyraider 3.3. I tried extracting it from the sense hd rom and moving it to system/app but that wouldn't install. I'm sure I'm approaching it from a way too simplistic angle. Any help would be much appreciated.
Thanks
I'm not sure if you could do this...
The Desire is running the new sense, so this could be a problem?
Maybe if IncDoes chimes in he would know, or if you want to get ahold of him
Let us know how this goes!
how did you move it to your skyraider rom? if you used root explorer then you need to change permissions and then do a reboot.
jasonb1985 said:
how did you move it to your skyraider rom? if you used root explorer then you need to change permissions and then do a reboot.
Click to expand...
Click to collapse
Yeah I used Root Explorer. I changed permissions to read/write, moved out the old browser, moved in the new browser, changed permissions back, and finally did a reboot. No browser was recognized so I actually went in and hit install but it said install unsuccessful.
any luck with this?
Try this one. It is from the latest leak and does have pinch.
It is for only a deodexed ROM not stock and will work if pushed to /system/app/ with adb.
NilsP said:
Try this one. It is from the latest leak and does have pinch.
It is for only a deodexed ROM not stock and will work if pushed to /system/app/ with adb.
Click to expand...
Click to collapse
How did you port it?
Sent from my Incredible using XDA App
jdkoreclipse said:
How did you port it?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Wasn't ported. It is directly from the latest HTC Incredible leak.
NilsP said:
Wasn't ported. It is directly from the latest HTC Incredible leak.
Click to expand...
Click to collapse
It doesnt work...fc right away
Sent from my Incredible using XDA App
doesnt work for me either, thanks for that attempt tho
wowthatisrandom said:
doesnt work for me either, thanks for that attempt tho
Click to expand...
Click to collapse
Worth a try. I guess it is dependent on something else in the leaked version.
NilsP said:
Try this one. It is from the latest leak and does have pinch.
It is for only a deodexed ROM not stock and will work if pushed to /system/app/ with adb.
Click to expand...
Click to collapse
Well it took me a while to figure out how to push with adb. I didn't know you just do it in the tools folder, I thought you ran adb shell first.
I appreciate your help, but it didn't work just immediately force closes.
Thanks anyways.
Unfortunately, I'm not going to be much help, but maybe I can offer a little explanation as to why it wont work..
From what I can tell, most if not all the HTC stuff (widgets, apps, whatever) rely on some values from /system/framework/com.htc.resources.apk. Basically it is all intertwined into a giant mess. As far as I can guess, the only way to get it to work would be to figure out what values the HD browser is looking for but can't find in the stock Inc framework. Then the stock framework would have to be edited, presumably using values from the HD framework. And as you probably guessed, just trying to run the HD framework on an otherwise stock Inc rom will send you into a never-ending boot loop.
I could be way off base, but that's my understanding of it at least.
RdBrd83 said:
Unfortunately, I'm not going to be much help, but maybe I can offer a little explanation as to why it wont work..
From what I can tell, most if not all the HTC stuff (widgets, apps, whatever) rely on some values from /system/framework/com.htc.resources.apk. Basically it is all intertwined into a giant mess. As far as I can guess, the only way to get it to work would be to figure out what values the HD browser is looking for but can't find in the stock Inc framework. Then the stock framework would have to be edited, presumably using values from the HD framework. And as you probably guessed, just trying to run the HD framework on an otherwise stock Inc rom will send you into a never-ending boot loop.
I could be way off base, but that's my understanding of it at least.
Click to expand...
Click to collapse
You are on the money. On top of resources, I believe there may be a few framework classes required to get the new functionality working properly. This will be a cat and mouse game for a while. Certainly not just an apk push. You will need to make a change, log the failure, find out what its looking for, add said resource/class, rinse, and repeat.
deficitism said:
You are on the money. On top of resources, I believe their may be a few framework classes required to get the new functionality working properly. This will be a cat and mouse game for a while. Certainly not just an apk push. You will need to make a change, log the failure, find out what its looking for, add said resource/class, rinse, and repeat.
Click to expand...
Click to collapse
I tinkered with it last night on my 2.2 ROM and there are dependencies all over the place. I think I will just move forward with the leaked ROM and tinker in my spare time.
Hello. Hopefully someone can help me with this.
I have created an Elite themed Launcher Pro (based on Koni's Elite series I rom). I have all the framework modified and the apk ready to flasha gain.
I started by using the zip from the Myn's Rom launcher pro and replaced the framework files. i flash it and it does place the apk in data/app however the phone doesnt recognize that it is present. Nothing shows in applications under settings and cant get it to "run".
When i move the apk to system/app it works perfectly.
anyone have any ideas on what might be causing this. I am sure i probably just missed something silly but i cant seem to get it going for the life of me.
omegasun18 said:
Hello. Hopefully someone can help me with this.
I have created an Elite themed Launcher Pro (based on Koni's Elite series I rom). I have all the framework modified and the apk ready to flasha gain.
I started by using the zip from the Myn's Rom launcher pro and replaced the framework files. i flash it and it does place the apk in data/app however the phone doesnt recognize that it is present. Nothing shows in applications under settings and cant get it to "run".
When i move the apk to system/app it works perfectly.
anyone have any ideas on what might be causing this. I am sure i probably just missed something silly but i cant seem to get it going for the life of me.
Click to expand...
Click to collapse
Only thing I can think of is when modifying it got signed as system file maybe? Not too sure cause I modified the original LP apk and reinstalled from SD root like normal app. Seems this would be easier than having to flash it but just my thoughts.
Also, why not just leave in system/app?
The main reason for not leaving it in system/app (and also for the flash) is because it doesnt put the dock background on by default. Those who would like to use it have to go and set it them selves. Which isn't a huge deal by itself but trying to make it as easy as possibe for the users.
Sent from my PC36100 using XDA App
I've managed to extract an apk of a (free) application that is restricted to the Galaxy S3. Unfortunately, when I try to install this apk on my Galaxy Nexus, it says 'application not installed'. I'm assuming this is because the S3's device ID is integrated into the apk file, which is why the apk installs fine onto the S3 that it was extracted from.
How does one get around this? Surely it's possible, as applications such as Google Wallet are extracted and shared for all devices on the internet within hours of an update. Could somebody give me a guide on how to do this?
Just a thought, install on your s3, titium back up , copy the backup to your GN and install
Sent from my Galaxy Nexus using xda premium
qtwrk said:
Just a thought, install on your s3, titium back up , copy the backup to your GN and install
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It's my mother's S3; I can't root it.
Add her email account then go to play store menu and click her email under accounts and her play suite will be on there. Just make sure you don't sync when setting it up or will get all her emails. Then remove her account. app will still be installed and will update. If you flash you'll have to do it again
LoveNFC said:
It's my mother's S3; I can't root it.
Click to expand...
Click to collapse
Is yours rooted? If so, did you try adding into the system apps folder? Make sure you make a backup too
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Don't need root. Just add her under accounts on phone. I did it once. My friend had tmobile. I'm sprint. Apps are tied to email account. All you do is switch user in the store and hers will be there and yours won't until you switch back. Get app. Switch back to yours. Go back to phone settings and remove her account.
JediNinjafication said:
Don't need root. Just add her under accounts on phone. I did it once. My friend had tmobile. I'm sprint. Apps are tied to email account. All you do is switch user in the store and hers will be there and yours won't until you switch back. Get app. Switch back to yours. Go back to phone settings and remove her account.
Click to expand...
Click to collapse
Thanks for the suggestion, I've just tried it now. Unfortunately, even though the app did show up in the list, I'm getting "your device is not compatible with this version".
What app? just curious.
LoveNFC said:
Thanks for the suggestion, I've just tried it now. Unfortunately, even though the app did show up in the list, I'm getting "your device is not compatible with this version".
Click to expand...
Click to collapse
Lame. I don't know how they Decompile either.
Mach3.2 said:
What app? just curious.
Click to expand...
Click to collapse
It's an NFC payment application for my country.
Any new ideas?
Is it even possible to pull files from system folders via ADB command without root?
Isn't there some Apps that can temporary root your device withou actually touch system to root it?
Or why don't you root it and then afterwards unroot it?
Sent from my Galaxy Nexus using xda premium
I think you will be able to pull this off in a custom recovery.
Beamed from my Maguro
OK, so I've realised that the apk that I've pulled from the S3 works fine. I had an online friend install it on his phone and it installs perfectly. I then tried installing it on a Galaxy Note and Galaxy S2. Both of those threw up the same error: 'application not installed'. This has lead me to conclude that the apk, and the application, have device checks built-in. It won't install on anything other than an S3.
Does anyone know how to decompile apks to remove these device checks? I know it's possible, but how complicated is it?
This brief guide is to help others get Google Wallet working on AOSP based ROMs. There are guides already by Dafoxs and Antiochasylum but they are apparently for Samsung based ROMs and the lib files, etc are incompatible with AOSP based ROMs. Personally, I tried several times and the NFC setting kept getting wiped out so I had to do restores. These instructions are what ManelScout4Life posted and the thread is at his request. All the credit goes to the DEVs that made this possible - I am NOT a developer - Seriously... Lastly, the typical disclaimer applies - I take no responsibility for bricking your phone, etc. I highly recommend making a nandroid backup before any mod like this. These instructions worked on JellyBAM 3.2 compiled by ManeelScout4Life - http://forum.xda-developers.com/showthread.php?t=2069164
1) The lib files should not be modified like the posts for the SamSung based ROMs. However, you will need the modified Google Wallet .apk that is included in the zip you can download from their threads. I used the attached file that I downloaded from this thread - http://forum.xda-developers.com/showthread.php?t=2037372&highlight=google+wallet
2) I already had NFC enabled so ensure it is on in settings if you haven't already.
3) You need to modify /system/build.prop. I used Root Explorer (remember to change to RW) and you have to modify three lines. I made a copy of the existing build.prop before editing because you will revert to the existing file once complete to match your actual device.
3a) ro.product.model=Galaxy Nexus
3b) ro.product.name=yakju
3c) ro.product.device=maguro
4) I then rebooted before installing Google Wallet from the Play store. I then opened the app and performed the setup. The other guides mention getting FCs on NFC and to continue on but I never had any and the setup completed. YMMV.
5) Once the setup is complete with the version of the app from the store, you need to replace the app with the modified version that you downloaded in step 1. I used TB to force stop the app before I deleted it from /data/app.
6) I then use Root Explorer again to place the attached apk in /system/app (remember RW). I checked permissions and removed the group write check but again am not certain if that was necessary.
7) I then changed the build.prop.bak file to build.prop so it is back to before you started.
8) Reboot and hopefully it will work.
Hopefully, this helps and is clear.
Note: I see a prompt in the app shown in the attached pic but it will still work. It is really just a warning about a rooted device.
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
capite said:
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
Thanks for this!
Sent from my Samsung Galaxy Note II
Yes
Sent from my SGH-I317 using xda premium
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
told me to reset the app...and its hanging at 98%...thoughts?
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
crisis187 said:
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I assume the reason for the modified app is for it to continue working after you change the build.prop back to an unsupported device. I guess on AOSP ROMs where S-pen apps don't work, then the proper build.prop isn't as important. You will lose access to external sd card possibly and other issues possibly.
Sent from my SAMSUNG-SGH-I317 using xda premium
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
How about if you complete the instructions above - adding the modded app, changing permissions, deleting the downloaded app, etc?
Sent from my SAMSUNG-SGH-I317 using xda premium
RichMD said:
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
MonsterBandit said:
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
Click to expand...
Click to collapse
With the Galaxy Nexus build.Prop and Google wallet downloaded from the store, the setup needs to complete before you move to the next steps of reverting the build.prop and pushing the modded app. Those steps are to keep the app working without having issues due to a Galaxy Nexus build.prop. I would delete the app, and start over. I assume you never got an email stating you activated wallet.
Sent from my SAMSUNG-SGH-I317 using xda premium
Also, did you ever use the steps/zip posted by dafoxs or the other thread (forgot the name)? If so, your NFC setting might be gone or you have incompatible lib files, etc. I would revert to the nandroid backup if you made one before following those procedures which are for Samsung based ROMs rather than AOSP/CM10
Sent from my SAMSUNG-SGH-I317 using xda premium
crisis187 said:
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Wait. You installed multi window support on jelly beer!?
ManelScout4Life said:
Wait. You installed multi window support on jelly beer!?
Click to expand...
Click to collapse
LOL!
Modified build.prop and now my phone won't turn on. Any help?
---------- Post added at 02:37 PM ---------- Previous post was at 02:30 PM ----------
Took out battery, replaced it. Boot to recovery and restored Nandroid. Not sure what went wrong but I think I'll give up hopes of Google Wallet. Made me a little skiddish now.
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
bofhemeritus said:
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
Click to expand...
Click to collapse
Thanks,
I can't confirm this works on 10.1 (Android 4.2.x) - only confirmed on 4.1.x even though I expect Google Now, etc will be fine after reverting your build.prop. I'm "assuming" Google Wallet will work as indicated in these steps but Google Now, etc may have problems while the bulld.prop stilll indicates the wrong device - temporary until your wallet is working.
However, were you able to get Google Wallet to setup properly?
If you did get it working, did you try changing the build.prop back to original? I don't know if that would solve the Google Now but your steps listed don't indicate that you finished reverting the build.prop.
Please reply with your results for others.
Hello -
I did actually revert the build.props file to the original settings, and Google Now continued to give the same error. I'm about to test it without opening Google now until after the revert and reboot.
Thanks for your help!
If you like my work, donate to the Juvenile Diabetes Research Fund.
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