Related
Does anyone know what would need to be done to port this keyboard or make a flashable zip?
I pulled the HTC_IME.apk and Clicker.apk from the Desire HD port that is being worked on right now for the EVO. However, it wont simply install on my phone. I tried removing the Stock HTC_IME and Clicker via Root Explorer. Did a reboot and tried installing the Desire HD apks but it would just say 'Application not installed'.
I pulled the apks from v2 in this thread
http://forum.xda-developers.com/showthread.php?t=790838
Thanks in advance
Bump
Sent from my SUPERSONIC
Have you tried adb push? I'm not any kind of expert but that usually works when I am trying to install apps that won't install.
I'll give that a shot tonight. Thanks for the input.
Sent from my SUPERSONIC
[EDIT] Adb push didnt work either. Touch Input doesnt even show up in Language & Keyboard. I'm guessing something needs to be changed within the apks.
Well wish I could help then. Not good at doctoring apks.
SITH16 said:
Well wish I could help then. Not good at doctoring apks.
Click to expand...
Click to collapse
That's cool. I dont really know where to start. Appreciate the input though.
dglowe343 said:
Does anyone know what would need to be done to port this keyboard or make a flashable zip?
I pulled the HTC_IME.apk and Clicker.apk from the Desire HD port that is being worked on right now for the EVO. However, it wont simply install on my phone. I tried removing the Stock HTC_IME and Clicker via Root Explorer. Did a reboot and tried installing the Desire HD apks but it would just say 'Application not installed'.
I pulled the apks from v2 in this thread
http://forum.xda-developers.com/showthread.php?t=790838
Thanks in advance
Click to expand...
Click to collapse
Did you change the permissions to match that of the original keyboard. I recently got the 5MP camera working on my Android HD2 by simply changing the permissions using Root Explorer. Just long press the files and tick the appropriate permissions. Hope it works!
Knowledge0417 said:
Did you change the permissions to match that of the original keyboard. I recently got the 5MP camera working on my Android HD2 by simply changing the permissions using Root Explorer. Just long press the files and tick the appropriate permissions. Hope it works!
Click to expand...
Click to collapse
Didn't work. Oh well. Thanks for the help though.
Sent from my SUPERSONIC
Bump. Totally looking for this to happen.
i want this too. ive tried theming the current htc keyboard for the evo but cant seem to get it working. what else has changed besides button colors?
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.
(BackStory)
This is how I installed the Vanilla Mms App on my G2 Running Desire Z ROM. No risk if you back up your ROM using ROM Manger,
there are many guides on how to do this.
THIS WORKS ON ANY ROM
Hey guys! I was just looking at the "HTC Sense" Messaging App for the Desire Z ROM and basically I noticed.. it sucks..
Its really bulky and some parts of it don't fit on the screen... (Although the Desire Z ROM Is the GREATEST!)
I wondered if it was possible to extract the "Vanilla" Mms.apk and install it on the Desire Z ROM... So I booted up Vanilla on my G2 and did the work.
This IS possbile! And It works GREAT!
Apps Needed:
Mms.apk (Download Link below)
Android Mate/Root Explorer/File Manager/Linda Explorer, (Pick your Favorite)
Terminal Emulator, you can alternatively use adb shell
Obviously, a rooted phone
Installation: (Fool Proof)
Download my Link Down there, Mms.apk
Plug your phone into the computer and tranfer the file on the root of your SD card
You will now be removing your Mms.apk app from your ROM; Back up if you think you're gonna mess up;
Preform A Nandroid backup using ROM MANAGER, there are many guides on doing so, find them.
Go into Terminal Emulator and type in the following:
**note in some ROMs it will be called "com.android.mms.apk" so check what the name is before you type that in**
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
rm /system/app/Mms.apk (or com.android.mms.apk)
If your Text messaging app is running, it probably will force close.
After uninstalling, reboot, if F/C occurs, do a simple battery pull.
When your device reboots, it should no longer have the "Messaging" app installed!
Through your favorite file manager, move "Mms.apk" to /system/app/
Now, go through the installing procedure like you would any app.
It should now be installed, reboot the phone, CONGRATULATIONS
Taddaa!! The next step is to enjoy your new Vanilla Mms on Htc Sense (or any rom)
You may tweek the app how you want; change the color through settings by pressing menu on the Messaging app.. etc..
Disclaimer, I am not the person who hurt your phone if you mess up, you are. Do a back up, nothing can be harmed unless you delete other files besides the Mms.apk.
This Mission was success!
The APK File that is attached IS Working as of NOVEMBER 21 2010; It has been fixed!!
***ATTENTION: THANK YOU TO WHEELIEST FOR GETING A BETTER APK***
Ignore every comment that says Force/Closed, the APK Attached has been fixed and works perfectly!
Nov/20 WORKING! Good to go!
This works Seamlessly! Everything works and It looks perfect!
*Don't Forget To Do A Battery Pull after Uninstalling and After Installing The MMS.APK
Awesome...thanks so much!!
Keeps forcing closed... had to restore backup..
wrichards2009 said:
Keeps forcing closed... had to restore backup..
Click to expand...
Click to collapse
try what OP stated?
It Force Closed my Messaging App. (If It doesn't, even better)
After Un-Installing, do a simple battery pull and reboot your phone.
When your phone starts, the Messaging app should no longer be there. Good.
Click to expand...
Click to collapse
followed directions and installed, force closes right after i send a msg. did this install right after a fresh rom install
akagoffer said:
try what OP stated?
Click to expand...
Click to collapse
the Vnilla Mms.apk keeps force closing is what he means
are you suppose to move the Vanilla Mms.apk into system/app then find it / install it either via root explorer or ADB?
Not Working?
Hey Guys! Sorry its not working for you I uninstalled it to see if it was tainted, but I can install it and send/receive messages perfectly.
As far as I know, there are no changed settings on my phone. Sorry. I don't know what can be done... Everything I did was right in the directions. Try contacting a more experienced person to this Thread to see if they know whats going on.
Sorry Again..
When you go to install the mms.apk it says that its version 2.1 android. That might be the problem.
works great
thanks alot
If you just place the mms.apk in the system/app/ folder it will work with no problems.
oh, thats right, my version is 2.2 on vanilla rom.
Working?
UnSungHERO420 said:
If you just place the mms.apk in the system/app/ folder it will work with no problems.
Click to expand...
Click to collapse
Hey, UnSungHERO, are you saying it works with MY Mms.apk and with my method?
I already have it, but can you clarify for my and all of us on how to do it?
Thanks. Did you delete the originally Mms.apk file that came with the phone? Or did you place it in the folder and overwrite it?
Does it recieve/send Sms/Mms successfully?
i tried it as it was instructed. Mms.apk installed and worked but would force close after sending and receiving texts. I deleted that apk pulled the MMS.apk from CM and that works fine. Give it a try....more options to boot
Hah, the messaging app is one of the things that I didn't like about the DesireZ Sense ROM. Oh well, I'm not happily running CM! Glad there is a way around it though, thanks for posting!
Nice that was one of the things I disliked about sense. Can this be done with the dialer/contacts
Brazildiogo732 said:
Hey, UnSungHERO, are you saying it works with MY Mms.apk and with my method?
I already have it, but can you clarify for my and all of us on how to do it?
Thanks. Did you delete the originally Mms.apk file that came with the phone? Or did you place it in the folder and overwrite it?
Does it recieve/send Sms/Mms successfully?
Click to expand...
Click to collapse
Sorry for the vague post. But yes, I was referring to your method. You should definitely delete the stock sense mms.apk beforehand. I actually haven't sent any messages since replacing the apk. I just tested it and found that the app force closes when I attempt to send messages. SMS messages are sending still with the FC and MMS are not. I'm going to try the CyanogenMod mms.apk since it was mentioned.
UnSungHERO420 said:
Sorry for the vague post. But yes, I was referring to your method. You should definitely delete the stock sense mms.apk beforehand. I actually haven't sent any messages since replacing the apk. I just tested it and found that the app force closes when I attempt to send messages. SMS messages are sending still with the FC and MMS are not. I'm going to try the CyanogenMod mms.apk since it was mentioned.
Click to expand...
Click to collapse
Um yeah I already wrote a tutorial here...
http://forum.xda-developers.com/showthread.php?t=834106
gravis86 said:
Um yeah I already wrote a tutorial here...
http://forum.xda-developers.com/showthread.php?t=834106
Click to expand...
Click to collapse
Thanks but I didn't need a tutorial. Just stating what happened with the stock android mms.apk. The CM mms.apk works fine with my sms but does not send mms .
The app keeps force closing after I updated to 7.1. More specifically, Wifi Calling works normally, but if I use LCD Density (220) it force closes. How can I fix this?
Sent from my HTC Vision
I take it you've run Fix Permissions already from Clockworkmod?
Yes, I have.
I think you also had the problem with Swype... edit your build.prop as described in your other thread.
Sent from my HTC Vision using XDA App
spare parts > enable compatibility mode
see if that helps.
It doesn't help. Any other methods? If not, can someone provide a thorough walkthrough of what I need to change in my system files for it to work? Wifi calling is a biggie for me!
Sent from my HTC Vision
mapheG2 said:
It doesn't help. Any other methods? If not, can someone provide a thorough walkthrough of what I need to change in my system files for it to work? Wifi calling is a biggie for me!
Sent from my HTC Vision
Click to expand...
Click to collapse
The build.prop edit did not work? Or the other suggestion above your last post?
If you want to try to edit the build.prop, open your file manager and navigate to /system folder. Scroll down to build.prop.
Long press > Open As > Text
Change this:
ro.product.model=HTC Vision
ro.product.brand=htc_wwe
To this:
ro.product.model=T-Mobile G2
ro.product.brand=tmobile
If I misunderstood and you've already tried this, then please disregard.
No, you understood me correctly. I checked the other thread and downloaded ES File Explorer and did what I was told. My build.prop files now contains all the changes that you told me to make, yet my WIFI Calling is still force closing. Any ideas from here??
mapheG2 said:
No, you understood me correctly. I checked the other thread and downloaded ES File Explorer and did what I was told. My build.prop files now contains all the changes that you told me to make, yet my WIFI Calling is still force closing. Any ideas from here??
Click to expand...
Click to collapse
Logcat please! Wifi calling should work perfectly out of the box on CM7.
I will provide you that once I get back home to my system that has ADB and everything else. For the time being, I don't know if you can find out the problem with this error message.
"The application Wi-Fi Calling (process com.android.kineto) has stopped unexpectedly. Please try again."
There is so much stuff. How am I supposed to copy and paste from the CMD terminal?
mapheG2 said:
There is so much stuff. How am I supposed to copy and paste from the CMD terminal?
Click to expand...
Click to collapse
adb logcat > logcat.txt
ctrl+c when you're done capturing data. this will dump the logcat into 'logcat.txt'. paste it into www.pastebin.com and reply back with the link.
just for kicks, i'd recommend redownloading the CM7.1 package and reflashing it. don't wipe anything, just flash it right over top of your current setup. (it's also always advised to check the md5 key to ensure your download isn't corrupt)
Ok, so I reflashed it without wiping anything and that didn't fix my problem. I'm wiping cache, fixing permissions, and reflashing the ROM now just to double check. If that doesn't work, I'll post my logcat.
Here you go: http://pastebin.com/PzsmyuCB
Hopefully you can tell me whats wrong
Anyone can help??
mapheG2 said:
There is so much stuff. How am I supposed to copy and paste from the CMD terminal?
Click to expand...
Click to collapse
Download alogcat from the market, launch it, launch wi-fi calling, pause alogcat once you get the error and save it.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
Download alogcat from the market, launch it, launch wi-fi calling, pause alogcat once you get the error and save it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks, but I already provided the logcat. Could you please help me from there?
changing LCD density can cause lot of weird issue for some apps, this only happens when you change the LCD density correct?
Have you tried doing a full Superwipe+ and fresh install of CM7.1? Wifi calling has worked flawlessly for me since CM7 (with 200 density, if the changing the density seems to break stuff).
You can always do a full backup with CWM and revert to your current state if it doesn't fix it.
EfemaN said:
Have you tried doing a full Superwipe+ and fresh install of CM7.1? Wifi calling has worked flawlessly for me since CM7 (with 200 density, if the changing the density seems to break stuff).
You can always do a full backup with CWM and revert to your current state if it doesn't fix it.
Click to expand...
Click to collapse
This isn't a bad idea. Just make sure you use the SuperwipeG2+ext4 located here so that you don't lose your 4 ext partitions. This assumes you're already converted to ext 4. If not, I recommend it. It consolidates internal memory space and has been said to improve speed (slightly).
By wiping, I will lose my data on my phone, right? I don't wish to do that, because I don't like putting things back into place (icons on homescreen, widgets, etc.). Anyway I can remove the WIFI calling app and have someone upload the app for me to reinstall?
Yes, this only happens when I change LCD Density. By messing around with the build.prop file, I can now change my LCD Density WITHOUT using the LCD Density app, but still doesn't fix the problem. Wifi Calling works when I'm at the default 240 but I'm too accustomed to 220 nowadays. It worked just fine in previous CM.
And I have no clue in regards to that whole 4 ext things?
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