Google Search by Voice v1.4.1 install fails - myTouch 3G, Magic Android Development

Searched the forum and wiki and can't find anything on this.
Trying hard not be a 'compleet newb'....
Problem: I've tried to download and install the latest update (v1.4.1) to Google Search by Voice. It fails saying it is not correctly signed. I am not able to uninstall it via the Market software. The existing version is present and still works.
I was thinking of manually uninstalling it and then attempting a re-install from the market. Has anyone had any success getting this update to install on CM 4.2.7.1?
I'm running Cyanogen 4.2.7.1 on my HTC Magic 32B, applied over the flashed and clean-installed 1.6 rooted base - no CM Updater. (Seems to give a better, more stable result - may affect the behaviour of the update).

this stupid error happens because of the test keys or the userdebug keys thay cyanogenmod uses. I would download it somewhere online and use adb to replace the old one wiht the new one. It should work.

Yes I have the same problem with same model phone etc. etc.
I understand the workaround will be the same as Google maps 3.2.1 update but I cannot find up to date "Google search by voice" apk. I was wondering if anyone knows a source that mirrors up to date apps, or could even link a tut about how to get apk's copied out of the phones /tmp folder?

Thanks
I'll check out the package name in the Applications settings and see if I can find it anywhere or somehow capture it. Later....won't have any time until this evening.

linuxluver said:
I'll check out the package name in the Applications settings and see if I can find it anywhere or somehow capture it. Later....won't have any time until this evening.
Click to expand...
Click to collapse
That's great I didn't think of that, ill whip out those quotation marks and asterisks for google too. Also later...... 00:20 is not the right time for this....... so tempted......!!!

I fixed the maps.apk problem by going into adb and uninstalling maps.apk and then removing all traces of it. Then I went to marketplace and i downloaded it as normal and it now works perfectly.
Try that with voice search

Do we know what the package name is? Usually something like "com.google.android.apps.xxx" Could try uninstalling through adb. Then re-download from the market?

hello, could u plz share the installer? its not available on the marketplace in my country.
thanks very much

success
Ok, I managed to get Google Search by Voice updated to 1.4.1. I'm no pro and it took ages but it works.
Could a mod advise whether I am allowed to post a link to the apk?
I would be happy to post the steps i took but its not something i have done before and worse still, i used cmd not putty (noob error #1!). So the commands and the order i used them in are lost.
Should have used ubuntu..............
the concept consisted of updating the app and simultaneously using this command while it was downloading
Code:
cp /cache/downloadfile-9.apk /sdcard/download
"9" is only because it is the 9th apk i have downloaded and once the install fails the OS deletes the apk.
(for anyone else it would be different. go into /cache and type ls at the prompt to see what your next number will be)
then rename downloadfile-*.apk to VoiceSearch.apk, remove the original in the phone using adb and replace with the updated app.
I will post again tomorrow with clearer instructions but would much rather post a link to the apk I got, if it is permitted

hmmm. doing an 'adb shell rm /system/app/VoiceSearch.apk' and reinstalling from the market still gives you the unsigned error?

jayzusfk said:
hmmm. doing an 'adb shell rm /system/app/VoiceSearch.apk' and reinstalling from the market still gives you the unsigned error?
Click to expand...
Click to collapse
yes it will still give an unsigned error.
that is why you need to copy the apk which android market downloads to /cache before it deletes it, i copied it to /sdcard/download. then install via adb afterwards.
you have to manual install the apk to avoid unsigned error, once you have done this any future updates through market will be fine. Maps updated fine to 3.3 after i manually installed 3.2.1

How?
anthortic said:
yes it will still give an unsigned error.
that is why you need to copy the apk which android market downloads to /cache before it deletes it, i copied it to /sdcard/download. then install via adb afterwards.
Click to expand...
Click to collapse
Any advice on how you did that? I can imagine sitting with finger poised over the enter button in an adb shell.......is that what you did? Or is there a more certain, simple way?
Thanks.

linuxluver said:
Any advice on how you did that? I can imagine sitting with finger poised over the enter button in an adb shell.......is that what you did? Or is there a more certain, simple way?
Thanks.
Click to expand...
Click to collapse
lol that is exactly what i did. up, enter, up, enter, up, enter until the shell spat out that "downloadfile-9.apk does not exist" or however it puts it.

anthortic said:
lol that is exactly what i did. up, enter, up, enter, up, enter until the shell spat out that "downloadfile-9.apk does not exist" or however it puts it.
Click to expand...
Click to collapse
heyb buddy, i have been expecting you for the whole days, would plz share the apk file. thank you lol

themaskfly said:
heyb buddy, i have been expecting you for the whole days, would plz share the apk file. thank you lol
Click to expand...
Click to collapse
Can a mod please advise? I'm not out to break google's copyright, they know where i live! they know e-v-e-r-y-t-h-i-n-g!

anthortic said:
Can a mod please advise? I'm not out to break google's copyright, they know where i live! they know e-v-e-r-y-t-h-i-n-g!
Click to expand...
Click to collapse
well actually its pretty safe to share the google apps, since its free.
the link is for ur reference
http://forum.xda-developers.com/showthread.php?t=596281
http://forum.xda-developers.com/showpost.php?p=5098879&postcount=10

thank you much appreciated themaskfly
for my reference
http://www.mediafire.com/?sharekey=c2bec0e7155dcbb5ab1eab3e9fa335ca9bf4984cd4e3a7d4
a link to the folder containing google search by voice 1.4.1 (VoiceSearch.apk) as well as the original taken from Cyanogen 4.2.7.1 (VoiceSearch.apk.bak)
However it will not install using android interface, adb only.
Its been a pleasure to help, I have been using this site as reference for ages and it is nice to give something back

anthortic said:
thank you much appreciated themaskfly
for my reference
http://www.mediafire.com/?sharekey=c2bec0e7155dcbb5ab1eab3e9fa335ca9bf4984cd4e3a7d4
a link to the folder containing google search by voice 1.4.1 (VoiceSearch.apk) as well as the original taken from Cyanogen 4.2.7.1 (VoiceSearch.apk.bak)
However it will not install using android interface, adb only.
Its been a pleasure to help, I have been using this site as reference for ages and it is nice to give something back
Click to expand...
Click to collapse
thx for the sharing, u r AWESOME

Where id VoiceSearch.apk come from?
anthortic said:
yes it will still give an unsigned error.
you have to manual install the apk to avoid unsigned error, once you have done this any future updates through market will be fine. Maps updated fine to 3.3 after i manually installed 3.2.1
Click to expand...
Click to collapse
I downloaded the VoiceSearch.apk file and adb pushed it into /system/app on my phone and it works perfectly. The market sees it as installed and valid.
But I inspected my "normal" load phone (which has voice search) and nowhere could i see anything resembling "VoiceSearch.apk".
Where is this file on an un-rooted phone?

anthortic said:
yes it will still give an unsigned error.
that is why you need to copy the apk which android market downloads to /cache before it deletes it, i copied it to /sdcard/download. then install via adb afterwards.
you have to manual install the apk to avoid unsigned error, once you have done this any future updates through market will be fine. Maps updated fine to 3.3 after i manually installed 3.2.1
Click to expand...
Click to collapse
good to know for the future. thanks.

Related

Android Browser build that AutoRotates

Here's a recompiled version of the Browser that supports auto rotate.
Here's the download location for the Browser.apk:
http://www.koushikdutta.com/2008/12/auto-rotate-for-android-browser.html
Run the following from the command prompt to install the new Browser:
Installation Instructions:
adb remount
adb shell rm /system/app/Browser.odex
adb push Browser.apk /system/app/Browser.apk
Now start up the Browser.
You may not have a Browser.odex depending on your phone model.
The change, as I mentioned before, is really trivial. In the BrowserActivity.onCreate, I did the following:
// the next line is the original code
// setRequestedOrientation(mSettings.getOrientation());
// make it use the sensor for orientation instead.
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);
To restore the original Browser, flash RC30 again.
Koush, thanks so much! I have been waiting for this!
i can't get it to install and now the browser don't work and i can't install the back up
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
kron2 said:
i can't get it to install and now the browser don't work and i can't install the back up
Click to expand...
Click to collapse
You can't get it to install? Could you be more specific?
saul972 said:
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
Click to expand...
Click to collapse
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
took a couple of tries but installed now...thanks!
fyi i rebooted phone to initially install the new Browser. I first got errors w/o rebooting so that may fix the problem
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Koush said:
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
Click to expand...
Click to collapse
Not sure.
Here's the message
failed to copy 'Browser.apk' to 'system/app/Browser.apk' : no space left on device
SGTDavePwnage said:
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Click to expand...
Click to collapse
Will I need to start the process again?
saul972 said:
Will I need to start the process again?
Click to expand...
Click to collapse
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Henchman said:
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Click to expand...
Click to collapse
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
SGTDavePwnage said:
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
Click to expand...
Click to collapse
Obviouse to em...
But probably not to everyone.
And you know the old saying. When you Assume...
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
SGTDavePwnage said:
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
Click to expand...
Click to collapse
Finally got it!!! Thanks for your help
kron2 said:
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
Click to expand...
Click to collapse
Place it in the tools folder of the SDK folder on your PC
thx joshoowa i installed it finally i did have it in the tool folder but would not install but after several tries it did i was starting to think i was installing it wrong
I've deleted most of my .ogg audio related tones in the /media/audio folder but i still get no space left. what else can i delete?
btw i'm using adb shell rm /xxx/xxx/xxx/xx.ogg to delete. is that right?
Hey Hey!!!...
Had to free up some room, but it works great..
Thanks..

[Updates] JACHero / TwistedZero Co-Op OTA Updater (6/27/09 - 2:33AM EST)

After painstakingly researching into jfupdater, fixing a bad adt and sdk installation, and realizing that both the 1.1 and 1.5 sources could not coexist in one project, it is done. This program will work for JACHero 1.7 / TwistedZeroP and later builds. Due to the pre-work nature of TwistedZero, this will ensure that at least one of the system.zip archives is on the ext partition (it may not provide the most updated programs, but it will at least allow the update to be installed) You have the option to poll all updates, just JACHero, just TwistedZeroP or just TwistedZeroM. So far, only JACHero's updates will download because I am still working on getting mine on a dedicated server. I will try to keep as up to date as possible with download availability. Anyway, without any further stalling:
http://twistedumbrella.googlepages.com/heroupdater.ui.apk
Updating to the latest *working* version
You will need to have transferred the build.prop file to the /system/ folder of the phone for this to work.
They are available through my site's main page for my builds, and for now on my google code for JACHero until I get a new page coded for that.
Currently working on getting my builds program ready. Default update type is TwistedZeroP (can be changed in menu). Program is now a free download on market. Hero Update.
Very nice......
great job man
Freakin Sick Just used it and it was awesome! It still displays downgrades buts thats fine! I love it!
kickfliprock13 said:
Freakin Sick Just used it and it was awesome! It still displays downgrades buts thats fine! I love it!
Click to expand...
Click to collapse
It will display downgrades if you either have a version it cannot detect that is compatible with the updates or haven't gone to the configuration menu and unchecked display downgrades
ace. i thought all the hero roms required a wipe before each upgrade so this comes as great news.
thanks
thefunkygibbon said:
ace. i thought all the hero roms required a wipe before each upgrade so this comes as great news.
thanks
Click to expand...
Click to collapse
You're still gonna get wiped depending on the build.
it told me error while downloading what am I doing wrong...?
Very nice . This will truly make things easier. Nice work Twisted and Jac =).
So..I get a message when using update. The update app says "Your system is running an unsupported OS. (Version unknown) Please manually upgrade to JACHero 1.7 / TwistedZeroP or later and try again"
I understand its still a work in progress..just reporting my experience with the process.
Is "M" not a newer version than "P"?
I would assume, that even if the updater could not find an update for M, that M would still be a supported version and that it would just give me an error of not able to find an update for it or something. Not that M is unsupported.
FYI for all..I downloaded the files via the phone, installed linda file manager, android .Zip app(AndroZip) and AppsInstaller app. I Extracted the build.prop with and androzip, moved the file to /system/ on the phone with Linda, installed the HeroUpdater.ui.apk with Appinstaller. And then I get that message about an unsupported OS.
Great idea, thank you Twisted & JAC!
How do I use it? It shows me TwistedZero 1.7P as an update - can I just download it and then it will be installed?
No wipe or something like that?
an error occured while downloading 1.7P ?!
tep065 said:
Very nice . This will truly make things easier. Nice work Twisted and Jac =).
So..I get a message when using update. The update app says "Your system is running an unsupported OS. (Version unknown) Please manually upgrade to JACHero 1.7 / TwistedZeroP or later and try again"
I understand its still a work in progress..just reporting my experience with the process.
Is "M" not a newer version than "P"?
I would assume, that even if the updater could not find an update for M, that M would still be a supported version and that it would just give me an error of not able to find an update for it or something. Not that M is unsupported.
FYI for all..I downloaded the files via the phone, installed linda file manager, android .Zip app(AndroZip) and AppsInstaller app. I Extracted the build.prop with and androzip, moved the file to /system/ on the phone with Linda, installed the HeroUpdater.ui.apk with Appinstaller. And then I get that message about an unsupported OS.
Click to expand...
Click to collapse
Did you reboot after copying the build.prop? Rebooting did it for me (seems like this file is read when the system comes up).
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
jawash22 said:
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
Click to expand...
Click to collapse
Yes, the idea is that you replace it. The only difference between both files is a new reference to the build name (so the apk can tell what version you are on). Nevertheless it's always a good idea to back things up before you overwrite any files (learned the hard way throughout the years . So simply do something like 'cp /system/build.prop /sdcard/build.prop.old' from the terminal or 'adb pull /system/build.prop' from your computer before actually replacing the build.prop file.
Configuration menu
jawash22 said:
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
Click to expand...
Click to collapse
Ok, I just did an overwrite of my existing build.prop and it shows me the twisted 1.7 update, but I am on JAC 1.8. Hitting Menu does not bring up configuration menu...what's wrong?
Backup
DanOtero said:
Yes, the idea is that you replace it. The only difference between both files is a new reference to the build name (so the apk can tell what version you are on). Nevertheless it's always a good idea to back things up before you overwrite any files (learned the hard way throughout the years . So simply do something like 'cp /system/build.prop /sdcard/build.prop.old' from the terminal or 'adb pull /system/build.prop' from your computer before actually replacing the build.prop file.
Click to expand...
Click to collapse
Thanks alot..I should know by now about backing up system stuff. Anyways, I still can't get the Menu and at the bottom it says "Running Version:unknown". I used the JAC 1.8 build prop also. I'll leave it alone for now and see if anyone else on JAC reports bugs....thanks again Twisted! You are appreciated.
man! cyan needs one!
DanOtero said:
Did you reboot after copying the build.prop? Rebooting did it for me (seems like this file is read when the system comes up).
Click to expand...
Click to collapse
Yah...i didnt reboot after...just rebooted and i had an update available thanx..gonna run the update while watching transformerrss in imax theater
where's the file?
"They are available through my site's main page for my builds, and for now on my google code for JACHero until I get a new page coded for that."
That would spare 20minutes of timewasting
How do you transferred the build.prop file to the /system/ folder of the phone? thanks in advance.

froyo quickoffice problem

Upgraded to froyo from stock rom. I had quickoffice,which was free with the first att update. Now the icon is frakked and it says "this file is read only". The actual program seems to work fine, but i cannot fix the icon and quickoffice does not show up in the uninstaller. On the android market it does not recognize my phone having it installed, and i cannot get it free anymore (says $9.99). Anyway to fix this?
I had the same thing happen. I went to the quickoffice website and submitted a trouble ticket for it. May not help, but it was worth a shot.
same here, app works fine, just the icon is screwed up
mine shows in the app market, but as already installed and unable to locate on the phone to uninstall it
It's not that big of a deal to me
kb0npw said:
I had the same thing happen. I went to the quickoffice website and submitted a trouble ticket for it. May not help, but it was worth a shot.
Click to expand...
Click to collapse
I submitted a trouble ticket and got the following back as a response:
The thing is that due to OEM decision the version you have now installed may be shipped with a limited number of features.
You may wish to purchase the full version of Quickoffice that support this feature. You'll be able to cancel the purchase within 24 hours, in case the app doesn't meet your requirements.
Click to expand...
Click to collapse
After a factory reset, Quick Office functions fine again and the icon is back to normal.
I think I'll just live with a messed up icon rather than a factory reset.
Does anyone have a link to the appropriate QuickOffice APKs with install instructions? I just installed Cog4.1 which is great but Quickoffice isn't there and the Market doesn't seem to know that we get it with our Captivates for free. It used to on other Froyos and Eclairs but not this one.
ianwood said:
Does anyone have a link to the appropriate QuickOffice APKs with install instructions? I just installed Cog4.1 which is great but Quickoffice isn't there and the Market doesn't seem to know that we get it with our Captivates for free. It used to on other Froyos and Eclairs but not this one.
Click to expand...
Click to collapse
If you read a few posts above yours, a ticket was sent and they replied. It looks like the captivate no longer gets the full version for free any more
zelendel said:
If you read a few posts above yours, a ticket was sent and they replied. It looks like the captivate no longer gets the full version for free any more
Click to expand...
Click to collapse
I saw that but it sounded very much like a canned answer. And it doesn't really make sense bcuz...
Didn't AT&T promote the fact that QuickOffice came with the phone? That and most of us have had several pre-release versions of Froyo already on our phones and were still able to download it. And finally, AT&T has already paid for my license (as have I by buying the phone). Seems more likely that AT&T forgot to flip a bit somewhere.
Or maybe that's just my own rationalization bcuz I don't want to shell out $10 for it.
ianwood said:
I saw that but it sounded very much like a canned answer. And it doesn't really make sense bcuz...
Didn't AT&T promote the fact that QuickOffice came with the phone? That and most of us have had several pre-release versions of Froyo already on our phones and were still able to download it. And finally, AT&T has already paid for my license (as have I by buying the phone). Seems more likely that AT&T forgot to flip a bit somewhere.
Or maybe that's just my own rationalization bcuz I don't want to shell out $10 for it.
Click to expand...
Click to collapse
Yes at first they did, but the last I heard before I stopped working for them was that with the new batch that came with 2.2 already we were not supposed to say that it came with it, but hey we all know AT&T.
pietro_spina said:
I think I'll just live with a messed up icon rather than a factory reset.
Click to expand...
Click to collapse
Well I just couldn't live with the busted icon.
So I pulled the Quickoffice.apk out of the /system/app folder and reinstalled it... Now it has it's lovely icon back and still works fine.
Code:
adb pull /system/app/Quickoffice.apk
adb install -r Quickoffice.apk
(the "-r" means reinstall)
you can also get the app out the factoryfs.rfs in this copy of the official froyo update
If you run linux just mount the .rfs (see command below) browse to the /system/app folder in your favorite file navigator and copy the file out. If you don't run linux.... why not?
Code:
sudo mount -o loop factoryfs.rfs /mnt
pietro_spina said:
Well I just couldn't live with the busted icon.
So I pulled the Quickoffice.apk out of the /system/app folder and reinstalled it... Now it has it's lovely icon back and still works fine.
Code:
adb pull /system/app/Quickoffice.apk
adb install -r Quickoffice.apk
(the "-r" means reinstall)
you can also get the app out the factoryfs.rfs in this copy of the official froyo update
If you run linux just mount the .rfs (see command below) browse to the /system/app folder in your favorite file navigator and copy the file out. If you don't run linux.... why not?
Code:
sudo mount -o loop factoryfs.rfs /mnt
Click to expand...
Click to collapse
It's actually in the Cognition 4.1 zip so I assume it came with the leaked ROM. Re-installed it with ADB and all is good again. Thanks.
The response was incorrect. You have 15 minutes to cancel and get a refund, not 24 hours.
Plus, the update broke the icon. They should fix the icon instead of playing the blame game.
My problem isn't just the icon...it appears to be totally gone and I can't redownload it from the market as it is a paid app...how do I get it back?
garak0410 said:
My problem isn't just the icon...it appears to be totally gone and I can't redownload it from the market as it is a paid app...how do I get it back?
Click to expand...
Click to collapse
It is contained in the ZIP of the Cognition 4.1 ROM if that is what you are using. Once you have located the APK in the ZIP, copy it to your PC and then you can reinstall it using ADB from the command line as was suggested earlier:
Code:
adb install -r Quickoffice.apk
You might be better off to do a clean reset with Odin 1 click, and then a clean update to 2.2. I have Cognition 4.1 and my Quickoffice seems to be working fine after the update.

Mixzing app won't open

I updated my phone to4.4.1 today and ever since I haven't been able to open my music player 'Mixzing'. When I click on the App icon it goes to a black screen momentarily then back to the home screen without starting the app (this is the only app that it happens on)
I have wiped dalvik ect and deleted any folders that have 'mixzing' on and tried re-installing but nothing has helped.
Any ideas?
anyone?
Same here
I couldn't post my question on the corresponding Dev Thread for CM11 on i9300, but found this post for Nexus 5. Unfortunately without an answer.
I have the same problem (MixZing app doesn't open) on i9300 with CM11 nightly (Android 4.4.2). On CM10.2 (Android 4.3.1) it worked fine.
Have you found an answer somewhere else?
storchp said:
I couldn't post my question on the corresponding Dev Thread for CM11 on i9300, but found this post for Nexus 5. Unfortunately without an answer.
I have the same problem (MixZing app doesn't open) on i9300 with CM11 nightly (Android 4.4.2). On CM10.2 (Android 4.3.1) it worked fine.
Have you found an answer somewhere else?
Click to expand...
Click to collapse
Same here, no solution yet.
I made a modded version of the mixzing app to get it to launch for me:
All I did was replace the following in com.mixzing.android.SdCardHandler.getCardId()
Code:
invoke-static {v10}, Landroid/os/FileUtils;->getFatVolumeId(Ljava/lang/String;)I
move-result v4
with
Code:
const/16 v4, 0xBEEF
You should use your own random number instead of BEEF since this effectively means that you are always returning the same value for getFatVolumeId as far as the app is concerned.
Can you explain this to the developer of MixZing? So they can update the original App.
Would be nice, thanks.
storchp said:
Can you explain this to the developer of MixZing? So they can update the original App.
Would be nice, thanks.
Click to expand...
Click to collapse
They have said that they know about it. They were just taking too long for my taste, so I did it myself instead.
If you can't wait I can post my modded version if you want, but I highly recommend doing the mod yourself rather than simply trusting that my posted version does not contain any malware. It's just a good habit to get into IMO.
Never modded an App. But I'm eager to learn. Any resource (document, blogpost, etc.) I should look into?
storchp said:
Never modded an App. But I'm eager to learn. Any resource (document, blogpost, etc.) I should look into?
Click to expand...
Click to collapse
You can technically use a combination of 7zip (or another zip utility), smali, baksmali, and signapk to do this mod, however this is not the most user friendly way to do it. I would suggest using one of the following:
Here is one way, apktool (Linux, Mac OS, Windows): http://forum.xda-developers.com/showthread.php?t=2195680
The other is Virtuous Ten Studio (Windows Only): http://forum.xda-developers.com/showthread.php?t=1619473
*EDIT*
It is important to note that since this is not a system apk -- I.E. one that comes with the phone -- you will have to re-sign the apk after adding, removing, or changing any of the files inside. If it were a system apk, you could place the classes.dex file directly into the apk (which is secretly a zip file) without re-signing. (VTS does this for you automatically).
Thanks, I'll check it out.
Ok, decompiled it and found the lines you mentioned in a file called SdCardHandler.smali.
Before I change it I want to understand a little bit what I'm doing.
The method getFatVolumeId() returns the Id of a given Mount Point. It's a native method call which I guess causes the trouble here.
If I change it to a static value, does it do any harm? I mean I have an internal and external SD card. Does MixZing check both?
You should use your own random number instead of BEEF
Click to expand...
Click to collapse
Just some hex value I can think of? e.g. AEEF, CEEF, ABCD, ...
Couldn't wait, wanted to try anyway
Did the changes, compiled a new apk, signed it, but it doesn't install :crying:
When installing via the phone itself it just tells me that the App hasn't been installed.
When installing via ADB it get an INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Need to figure out, how to fix this.
storchp said:
Couldn't wait, wanted to try anyway
Did the changes, compiled a new apk, signed it, but it doesn't install :crying:
When installing via the phone itself it just tells me that the App hasn't been installed.
When installing via ADB it get an INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Need to figure out, how to fix this.
Click to expand...
Click to collapse
The problem is that on our devices, that native method does not exist, so we just arbitrarily use a value such that it always returns the same value (I.E. always the same card) As for the error, uninstall any applications signed by the same certificate as Mixzing was or sign your modded copy with debug keys, and it should install just fine.
*edit*
Other fun values:
DEAD, F00D, B00B, BABE, C0DE.
Thanks. A little research brought me to the packages.xml file. In there I found the shared user attribute for the MixZing Upgrader App. I was not sure if I want to edit the file. But after your tip I just uninstalled the Upgrader App and I could install the modded version.
Thanks a lot
Meanwhile they have fixed the App in the store.

Stuck uploading APK to Lineage 18 ROM (read to the end)

Preamble​I oft find in various forums that people are so filled with the milk of human kindness that they just can't wait to help, ( or may gain a few more badges~) ignoring everything but the heading.
And in doing so ask foolish questions.
So, please DO READ to the end.
UPDATE
Thanks to @ jwoegerbauer I now know I can't install the Lantern APK via recovery. I must use ADB which I have previously tried but failed.
Obviously, therefore I do not know what I am doing with ADB.
My tasks focus now is to install Lantern APK via ADB with the devices , tools and systems already mentioned. (below)
Unless someone, somewhere knows where I can find a Lantern ZIP file which I can flash. (seems I am good at that now at least~)
Please DO read everything below ladies and gents, my sense of humour and patience does have a limit~
Mobile Device Details​Samsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in brief​To install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?​During one of my many attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
I am happy with that, seems no big deal for me, I was able to successfully install the new OS + Gapps. And it is one less APP to install
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
thebic said:
Mobile Device Details​Samsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in brief​To install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?​During one of my attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
Seems no big deal for me, I was able to successfully install the new OS + Gapps.
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
Click to expand...
Click to collapse
What recovery are you using? Have you tried different recoveries?
What version of twrp are you running?
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Yeah you could use adb sideload in twrp.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Click to expand...
Click to collapse
Hehe, I can verify your first statement!
Do you have a link you can direct me to please as to how to do it via ADB in Lineage recovery as I did try that (side loading) via TWRP and it threw back an error. I can't recall but I think it was permissions or similar?
Sorry, I forgot to mention that in my post.
Thx for your constructive feedback - much appreciated.
P
Re-read my cited post: I've edited it.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Click to expand...
Click to collapse
Ohhhhh Kayyyyyy - coping.
Just.
You have added code?
Before I go ahead and destroy New York, I use that where?
How?
and errr... why?
I am guessing in Terminal, but I am not really sure what I am trying to achieve here.
Sorry, not arguing or being difficult, I just find it helps me if I know what EXPECTED outcomes are. Just in case it isn't what I should expect. :>(
Thx for your patience.
p
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
jwoegerbauer said:
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
Click to expand...
Click to collapse
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
thebic said:
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
Click to expand...
Click to collapse
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
I seem to be going in ever decreasing circles.
Please help me out- what is protocol.
Do I keep updating my progress - or lack of- here, in this dialogue, or should I continue to update my original post?
Which one best communicates to everyone where I am at?
Cheers
thebic said:
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
Click to expand...
Click to collapse
You forgot to add the exact file directory.
Keno_I said:
You forgot to add the exact file directory.
Click to expand...
Click to collapse
Did it work after adding the file directory?
You are right.
I am not sure how this forum works, so it was more of a post to jwoegerbauer.
Anyway, even opening the folder with terminal and using adb install lantern-installer failed with a CLOSE error message. I guess that meant close as in shut not closes as in almost!
I can, using Lineageos recovery access ADP on my phone with the instruction: " now send the package you want to apply to the device with "adb sideload <filename>"
However that triggers a screed of data in terminal which, frankly, is well beyond my rudimentary level of comprehension.
I have tried following 3 other on line tuts which suggest using ADB on my computer. All goes well until the instruction: <adb devices> which returns:
$ adb devices
List of devices attached
In other words, computer can't find phone!
I initially tried it in DOWLOAD mode, with the usual "download in progress, do not disconnect source."
Then reading the tuts again, none mentioned download mode so I tried with just the device attached to the machine in normal phone usage mode. Checked that SAMSUNG was visible and I could open the folders but again failed. ( sorry I forget what that error message was)
So far the most positive has been the direct ADB via Lineageos, but I have no idea where to go from there.
It is knocking on 37* here, too hot to think so I am taking a break.
Thx for your latest efforts.
Cheers
P
OK Finally!
[email protected]:~$ adb devices
List of devices attached
438f904d device
[email protected]:~$ adb install /home/bicyu/Sam-upgrade/lantern-installer/lantern-installer.apk
Performing Streamed Install
Success
[email protected]:~$
I have read so many posts all end with the <adb devices> and on each one I see zilch.
So, for anyone else in this boat, here is my solution.
In developer OPTIONS on your LINEAGEos device scroll down to
DEFAULT USB CONFIGURATION​Very likely it is set to FILE TRANSFER - mine was.
Change it to USB TETHERING
Then enter < adb devices> in terminal.
You should then see your Android listed.
Proceed with: adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
You should see a SUCCESS flag!
NOTES: This works in Lineageos ROM on Linux, ( Ubuntu / Zorin O/S)
I dunno about others.
You need to have dev options activated.
Change the USB setting back when done, otherwise it tends to mess up your Internet! (did mine anyway!)
This is the best background tut to ADB I found.
He talks about a USB3 bug which, apparently, creates the same problem - maybe THAT is your issue? It was that article which put me on the USB CONFIG train.
Hope this helps someone.
A REALLY HUGE thank you to jwoegerbauer for putting me
on the right track - wrong train, - but right track.
Cheers mate!
Glad to hear you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Yep! Well good luck
jwoegerbauer said:
Glad to here you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Click to expand...
Click to collapse
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
thebic said:
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
Click to expand...
Click to collapse
Aroma File Manager, how nostalgic~
Now to wait till a mod closes this post

Categories

Resources