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?
Related
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.
(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 .
I am new here so cant post on the Development forum.
I just wanted to know if anyone has experienced the GPS stop working. It used to work under R23, but then stopped under R26, R28 and R29.
I even went back to 23 and it worked ok again.
I do a full wipe and clear or all the caches as recommended in between each reflash.
Does anyone know if it just needs a tweak.
I have used the AGPS patch as well with no effect.
My problem is the GPS not coming on at all, NOT just taking ages to find satellites.
Ant help appreciated
Thank you
Try going to menu>manage apps and clearing data and cache for it then try to restart it.
Sent from my Desire HD using xda premium
GPS Configuration
TheJackal69 said:
I am new here so cant post on the Development forum.
I just wanted to know if anyone has experienced the GPS stop working. It used to work under R23, but then stopped under R26, R28 and R29.
I even went back to 23 and it worked ok again.
I do a full wipe and clear or all the caches as recommended in between each reflash.
Does anyone know if it just needs a tweak.
I have used the AGPS patch as well with no effect.
My problem is the GPS not coming on at all, NOT just taking ages to find satellites.
Ant help appreciated
Thank you
Click to expand...
Click to collapse
Are you still using R23 as your ROM?
If so - Using a file explorer go to /etc and find a file called gps.conf
- Copy this file onto your SD card and then you can upgrade to R29 and then just copy 'gps.conf' back to /etc and hopefully that should fix your gps problems.
If not - open the zip file for R23 and find the gps.conf file in there and copy it to /etc on your phone.
Hope it helps
Cool, that sounds good will try that.
Thanks
Will I need to set any permissions (I havent had to do that before) or just copy it in and thats that?
TheJackal69 said:
Cool, that sounds good will try that.
Thanks
Will I need to set any permissions (I havent had to do that before) or just copy it in and thats that?
Click to expand...
Click to collapse
As per my experience copy file will work, no need to set permissions.
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
OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a
tygray6 said:
OK, so this may not even be the result of running a custom rom because it hasn't worked with any of them. When I click on Voicemail which isn't setup yet by the way, all it does is send me to my messaging app. It gives me no options to set it up, or check voicemail.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Running bonestock 1.0a
Click to expand...
Click to collapse
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip
Okay, thanks
Sent from my HTC6500LVW using XDA Premium 4 mobile app
OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
tygray6 said:
OK, so I downloaded the bloat zip and extracted the vvm.apk it gives me the install option but says install failed every time. Any ideas?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
are you using my empty flashable.zip..?
just pull vvm.apk and put in system/app
Once I get my phone back, and or you have S-OFF this won't be an issue.
Aroma will solve a lot of these types of issues as well.
Okay, I put it in place of the null file in the app folder in your flashable zip and after re zipping it it failed when flashing
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Sent from my HTC6500LVW using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Don't unzip then rezip. Use a tool like 7zip and drop it into the zip. It failed because by unzipping, you broke the signature
Click to expand...
Click to collapse
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)
andybones said:
exactly what Ty said.
I am expecting my phone back today, and my first project is Aroma..
so bare with me.. (not you Ty)
I will be getting the ROM to where I am comfortable with calling it a full non beta release.
Only reason it's beta is because I don't have Aroma set up yet, once that is set up, it's game on.
you will be able to re-flash the ROM.zip pick "MOD only" and then select JUST the .apk you want (NO you can't remove apps, use root explorer for that, I think S-OFF takes away write protection but I have no idea yet, if not, then, well, we will need to get used to that .zip that deletes files (it's quite easy, once you try it out and everything)
Click to expand...
Click to collapse
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app
tygray6 said:
I forgot to come back and post a thank you, it worked great after I placed the apk into the zip and flashed. By the way, I've run every rom available now for the phone and keep coming back to yours, I appreciate your work.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey man thank you very much, it really does mean a lot to me!
and you're very welcome
andybones said:
I removed the Visual Voicemail application. It can be added back.
The icon for Visual Voice mail is tied to the Messaging app.
I need to edit the messaging app to rid that icon. for now just use the feature to "hide" it in the app drawer.
of it you want the app, pull it outta the bloat.zip
Click to expand...
Click to collapse
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone
carm01 said:
Have you had any luck ridding the VVM icon and whatever else from the messaging app yet. I had a nasty issue related to the new VVM.
I will spell it out here in case anyone else has this issue.
So i like always update my phone when updates come out.
The new VVM has some addition network elements tied to it on the back-end.
Long story short this 443 update has created randomly dropping my mobile connection. I tried re flashing the radios, the stock rom, going back one radio version, etc. I mentioned this in a post in this thread:
http://forum.xda-developers.com/verizon-htc-one/help/wifi-bluetooth-mobile-data-wont-off-t2883253
I don't believe it is anything we have done in here, but the issue was with exclusively mobile data where it would disconnect but still show 4g, anyways back to the VVM
I had to revert to 442 stock rom as it didn't have the disconnecting issue
Since i already ran the newest 443 VVM app with those additional features, the 442 VVM fails with error code 2004 when on a 442 ROM
So i had to be coy when calling VZW to get them to reset this. Lucky they didn't ask SW/HW versions, so basically they had ' reset the network elements ' associated with the newest version. WORKED!
So if this happens to you , all i said was it came down as an update, i didn't like it, and reverted back and now it does not work, etc.... I tried to find the newest update again but cant find it.
I was wondering how the VVM icon still there after removing the APK, that answers that. I tried to load the newest VVM on 442, and epic fail lolz
Just providing some info for everyone
Click to expand...
Click to collapse
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...
andybones said:
Foolish me, this is so very simple, I just forgot that you have to do it on a 100% clean flash, you can't use a flashable.zip as it is an .xml system edit.
system/customize/resource/allapplication.xml
basically you edit this .xml just search for "voicemail"
you will find this line of code
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]0[/COLOR][/B]" />
change it to
Code:
<item type="application" packageName="com.htc.sense.mms" className="com.htc.sense.mms.ui.VoiceMailTabActivity" display_order="200" display_hide="[B][COLOR="Red"]1[/COLOR][/B]" />
to be quite honest though to save yourself A LOT of time, just hit the menu button in app drawer click hide apps and hide it, that is what this MOD does anyway...
Click to expand...
Click to collapse
I will give this a try sometime; kudos