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.
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.
i was browsing the desire forums and i found this : http://forum.xda-developers.com/showthread.php?t=686567 i was thinking this would probably work for our Droid Incredibles but i wasnt sure. anyone want to clarify this?
to get the vanilla lock screen on sense rom, simply delete or move, HtcLockScreen.apk and it will come up.
as for the rotary lock screen, id kill for that on the inc lol
but when i remove htclockscreen.apk i get this. (attached)
avenator14 said:
but when i remove htclockscreen.apk i get this. (attached)
Click to expand...
Click to collapse
which rom are you running
oh damn, my bad man, what rom is this on?
I have no expierience with .jar files I wish I could help to know if those would would, I would say make a nand back up and try it out, the worse that will happen will be a need to pull the batt and do the nand... not too mention id really like to know if that rotary lockscreen would work lol
i have a nandroid backup i made right before i did this. i always make one before i do something through adb (im a noobie). and im running the stock 2.1 update1 rom with root and S-OFF.
avenator14 said:
i have a nandroid backup i made right before i did this. i always make one before i do something through adb (im a noobie). and im running the stock 2.1 update1 rom with root and S-OFF.
Click to expand...
Click to collapse
ahh 2.1 thats why. 2.2 if you remove the lockscreen apk you just get a straight up vanilla lockscreen, no mod required. on 2.1 youre better off getting widgetlocker or something off the sort as a lockscreen replacement.
i have seen mentions of widgetlocker, i will get this app soon. thanks for the help
Wait. There is a file you need and then it'll work on 2.1 - I'll post as soon as I'm back at my computer.
Ok found it! Download this file and use recovery mode to apply it.
http://forum.xda-developers.com/attachment.php?attachmentid=362754&d=1279498582
Although the above post will work to fix the lock screen, seeing as it's 2.1, the lock screen will have the option to unlock and science the phone, but not vibrate, as that is on the 2.2 only. Just an fyi
-------------
Just My II Sense
How do I remove the lockscreen apk? I am rooted using 2.5.2 skyraider. Can I delete the htc.lockscreen.apk from root explorer and if so where s it located? Will this work on skyraider?
Sent from my HTC Incredible using Tapatalk
I believe you can use root explorer, however I have not used that, I did it through adb. It is the htclockscreen.apk and .odex files. However, I would not remove them as you might want to put them back on at a later date. Use the mv command to either rename out something you will remember like htlockscreen.apk.bak, our move or to another directory. And it should be located under /system/apps.
-------------
Just My II Sense
has anyone got this working on froyo????? if so please help....i as well would kill for the rotary LS
Easy way is install unrevoked forever
Then use root explorer to rename
Htclockscreen.apk to .Bak.
Don't forget to reboot after you rename it.
Sent from my ADR6300 using Tapatalk
A few things to note: this will not change the slider on the incoming call screen. Also, I've heard of issues silencing an alarm with the HTC lockscreen APK missing.
has anyone found a way to get this to work and NOT have problems with the alarm clock?
edit: i found my answer
rusty2663 said:
has anyone found a way to get this to work and NOT have problems with the alarm clock?
edit: i found my answer
Click to expand...
Click to collapse
Sharing is nice
•Sent from my HTC Incredible, 2.2 Froyo
This has been discussed many many times...but you will have to use the vanilla clock app to use the alarm. If you try to use wprldclock or setting worldclock through the sense widget you will have to do a battery pull to silence
sent from my Dink
I don't mean to bump this back up, but I'm running into an issue. I'm running SR 2.5.2 with s-off, and when I try to rename htclockscreen.apk to .bak it wont let because its read only. I can copy the fie elswhere but can delete the original. Using root explorer, thanks in advance for the help.
atomicroach said:
I don't mean to bump this back up, but I'm running into an issue. I'm running SR 2.5.2 with s-off, and when I try to rename htclockscreen.apk to .bak it wont let because its read only. I can copy the fie elswhere but can delete the original. Using root explorer, thanks in advance for the help.
Click to expand...
Click to collapse
Thanks OP!
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?
Has anyone been able to get the 4.2 camera on the Dinc? I've been trying to get it to work on mine but I have had no luck. If anyone has, would please show how you got it to work? thanks!
ck04 said:
Has anyone been able to get the 4.2 camera on the Dinc? I've been trying to get it to work on mine but I have had no luck. If anyone has, would please show how you got it to work? thanks!
Click to expand...
Click to collapse
When I saw this, I though, "Your'e crazy!" But I tried it anyway...yeah, I'm crazy too...Amazingly, it actually works!! It's pretty slow (and the camera preview goes wonky just like the stock JB camera app), and video recording is broken on this ROM currently (Pons CM10-Unofficial-11-01). But the 4.2 camera actually works.
I copied the files over manually and fixed permissions (I used X-plore, but Root Explorer or adb would work as well), that way I could back up all the files I was replacing in case things went ugly. I quickly found:
The Problem. There's not enough room on the system partition for this newer (bigger) camera app and for the extra libs it requires. SO it will fail if you just try to flash the .zip. The easiest way to get it to work is to use Titanium Backup to uninstall some stuff. First to go is Gallery (we're replacing that), then I uninstalled Email, Exchange Services, Setup Wizard, Google One Time Init, and Trebuchet (make sure you have another launcher installed before you remove Trebuchet). THen, it was just a matter of copying the new files into place, fixing their permissions, and rebooting. But if you clean up some space on /system, you should be able to install the .zip from recovery and be good to go.
musical_chairs said:
When I saw this, I though, "Your'e crazy!" But I tried it anyway...yeah, I'm crazy too...Amazingly, it actually works!! It's pretty slow (and the camera preview goes wonky just like the stock JB camera app), and video recording is broken on this ROM currently (Pons CM10-Unofficial-11-01). But the 4.2 camera actually works.
I copied the files over manually and fixed permissions (I used X-plore, but Root Explorer or adb would work as well), that way I could back up all the files I was replacing in case things went ugly. I quickly found:
The Problem. There's not enough room on the system partition for this newer (bigger) camera app and for the extra libs it requires. SO it will fail if you just try to flash the .zip. The easiest way to get it to work is to use Titanium Backup to uninstall some stuff. First to go is Gallery (we're replacing that), then I uninstalled Email, Exchange Services, Setup Wizard, Google One Time Init, and Trebuchet (make sure you have another launcher installed before you remove Trebuchet). THen, it was just a matter of copying the new files into place, fixing their permissions, and rebooting. But if you clean up some space on /system, you should be able to install the .zip from recovery and be good to go.
Click to expand...
Click to collapse
I did exactly what you put and it WORKED!!! you have no idea how excited I am thank you so very much!
Just by way of confirmation, it does work (and is easier) to install the 4.2 camera this way:
1. Install your favorite JB ROM and gapps; boot the phone.
2. Using Titanium, uninstall gallery, and a few other things as mentined in post #2.
3. Boot into recovery again and install the 4.2 camera zip. (the one that's patched to work on non-nexus devices, procured elsewhere)
4. Boot the phone again and enjoy the goodness!
If anybody figures out a way to get anything useful out of photosphere on this phone, let me know.
musical_chairs said:
Just by way of confirmation, it does work (and is easier) to install the 4.2 camera this way:
1. Install your favorite JB ROM and gapps; boot the phone.
2. Using Titanium, uninstall gallery, and a few other things as mentined in post #2.
3. Boot into recovery again and install the 4.2 camera zip. (the one that's patched to work on non-nexus devices, procured elsewhere)
4. Boot the phone again and enjoy the goodness!
If anybody figures out a way to get anything useful out of photosphere on this phone, let me know.
Click to expand...
Click to collapse
All good advice, and uninstalling unneeded system apps is prudent with JB Roms. But to short circuit all this - I simply use the Camera360 app, which I find to be much better than the native camera app.
CyanoLou said:
All good advice, and uninstalling unneeded system apps is prudent with JB Roms. But to short circuit all this - I simply use the Camera360 app, which I find to be much better than the native camera app.
Click to expand...
Click to collapse
Except this thread is about the 4.2 camera which has Photosphere it in, not the stock app itself.
Well photosphere seems to be pretty much a functional failure on the Dinc, but the new gallery app is pretty cool. It's fast (it took some time to 'settle in'), plus the photo editing features are pretty neat. I'm liking it!
do you have a link where the 4.2 camera zip is? I've been looking for days to find a way to get the camera working on this dinc running tinys cm10. if there is another thread with a detailed walkthrough or if you could maybe post one to help those like me looking for this camera fix it would be much appreciated. desperately need to get this monkey off my back so I can pass this phone on. thanks!
Sent from my XT875 using xda premium
homeskool said:
do you have a link where the 4.2 camera zip is? I've been looking for days to find a way to get the camera working on this dinc running tinys cm10. if there is another thread with a detailed walkthrough or if you could maybe post one to help those like me looking for this camera fix it would be much appreciated. desperately need to get this monkey off my back so I can pass this phone on. thanks!
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
The 4.2 camera being discussed in this thread had been ripped from the Nexus 4 and patched by Android Police (I believe) to work on other phones. I don't have the link handy, but I'm not sure it would do you any good anyway. What are you trying to fix? The camera (except for video recording) works on tiny's CM10, works better than the 4.2 camera actually because the camera preview goes nuts sometimes on the 4.2 camera, and tiny's CM10 uses the legacy (ICS) camera which does not have the preview issues. If you really want the 4.2 camera, an easier way to get it is to flash tiny's CM10.1, but like I said, this will have the preview issues. The only difference between the default CM10.1 camera and the patched 4.2 camera is Photosphere, which does not work on our phones anyway.
If you're looking for a camera 'fix' for CM10, the only thing that needs fixing is the camcorder, and for that you have two options:
1. Low-quality video recording with VideoCam Illusions, free on the Play Store
2. Use a Gingerbread (or older) ROM.
sorry for misunderstanding, I've been looking everywhere to figure out the issues I'm having with this dinc. I can't get the camera working or Netflix running tinys cm10. I don't think it's the Rom but I can't figure out where I've gone wrong. I've been lurking these forums for a while and have been able to troubleshoot the three other devices pretty good with the amazing info on here, but this one is getting the best of me at the moment. bought this dinc reconditioned, it was running 2.3.4 and I followed a tutorial to downgrade to 2.2 and root and get s-off with cwm. I upgraded to the latest cwm recovery and have flashed this rom 3 times trying to make sure it was clean. just keep getting a black screen when I try any camera app until it force closes. when I play a movie on Netflix everything works but the video is a black screen, even the sound plays. I realize this is in the wrong place but I can't post in dev yet, maybe I should start a new thread?
Sent from my ADR6300 using xda app-developers app
homeskool said:
sorry for misunderstanding, I've been looking everywhere to figure out the issues I'm having with this dinc. I can't get the camera working or Netflix running tinys cm10. I don't think it's the Rom but I can't figure out where I've gone wrong. I've been lurking these forums for a while and have been able to troubleshoot the three other devices pretty good with the amazing info on here, but this one is getting the best of me at the moment. bought this dinc reconditioned, it was running 2.3.4 and I followed a tutorial to downgrade to 2.2 and root and get s-off with cwm. I upgraded to the latest cwm recovery and have flashed this rom 3 times trying to make sure it was clean. just keep getting a black screen when I try any camera app until it force closes. when I play a movie on Netflix everything works but the video is a black screen, even the sound plays. I realize this is in the wrong place but I can't post in dev yet, maybe I should start a new thread?
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Netflix is broken on this device past gingerbread. I've yet to hear a single user report video on Netflix as working.
Do you remember having a working camera when you first started using it? It could be hardware failure for the camera. Also which gapps file did you flash? If you flashed the wrong one it could cause funkiness. If you didn't flash any, the camera should be working. I know that doesn't make sense but try to answer these questions as best as you can.
I followed the link to the gapps from tinys cm10 thread and downloaded jb 20121011 signed. I'll try without gapps tomorrow to see what that does. I hadn't begun to look into the Netflix issue yet so thank you for saving me the time on that. if that's not the right gapps then I'll try another, I appreciate the help, thank you. thanks for an awesome Rom btw, I have yet to find one this nice for any other device I'm using. Happy New year!
Sent from my ADR6300 using xda app-developers app
I'm going to start a new thread since I need help figuring this camera problem out and I've already derailed this thread enough. any mods feel free to delete my posts in here if you see fit. thanks!
Sent from my XT875 using xda premium
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