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.
Related
Un so um jesusfreke if I understand all this and I'm not shure I fully do, but if I take out thr framework-res.apk un pack it edit it pack it all back up and sign it with thr sighnapk.jar utility and throw it back on my phone which has been moded with your boot recovery and update it will work....well at least in theory????? What's the worst that could happen at a failed attemtp do ya think?
worst that could happen?
brick phone. and I dont mean zack morris.
But assuming you know what everything you just typed actually does, should be fine.
VR4Stryph said:
Un so um jesusfreke if I understand all this and I'm not shure I fully do, but if I take out thr framework-res.apk un pack it edit it pack it all back up and sign it with thr sighnapk.jar utility and throw it back on my phone which has been moded with your boot recovery and update it will work....well at least in theory????? What's the worst that could happen at a failed attemtp do ya think?
Click to expand...
Click to collapse
I think you also have to re-sign all the .apk files in the /system/app folder. I just tried this last night and it all worked. I modified the default background in framework-res.apk. So now my phone is using the default background image with ugly black lines that I painted on it in gimp (see screenshot)
The only caveat is that you may have to reset the phone once you re-sign all the apks (alt+w in recovery mode). You will lose all your installed applications and data, and you'll have to re-enter your google account and password when you boot back up.
Try it without reseting, and if your phone acts weird, then try a reset and it should smooth things back out. After that point, you should be able to modify framework-res.apk without having to reset again.
The worst* that will happen is that you can't boot the phone normally. If that happens, put the modified RC30 update back onto your sd card somehow (external reader, another phone that uses miniSD cards, etc), and then boot into recovery mode and re-apply the modified RC30 update.
*I make no guarantees you won't brick your phone of course . But I can't think of anyway you would by doing this.
This isn't exactly skinning but it might help you start:
I modified the Launcher.apk so I could have my own wallpaper in the wallpaper gallery and take out the ugly stuff. Im sure you could change other resources in this and possibly other apk's as well.
I downloaded the android source from here http://source.android.com/download then slightly changed the source for Launcher.apk and recompiled it (make Launcher). My modified Launcher.apk worked fine on the emulator so I remounted my G1's /system partition as rw and replaced /system/app/Launcher.apk with my version and removed Launcher.odex then rebooted (dont forget to save the originals if you try this). So far its been working great in JesusFreke's modified RC30.
A screenshot of the modified wallpaper gallery is here: http://x8x.us/android/device.png
The signed modified Launcher.apk is here: http://x8x.us/android/Launcher_modified_wallpaper.apk
A tarball of the modified source is here: http://x8x.us/android/Launcher_modified_wallpaper.tar.gz
You can browse the modified source directory here: http://x8x.us/android/Launcher_modified_wallpaper/
The only changes I made were to src/com/android/launcher/WallpaperChooser.java and the res/drawable/wallpaper_*.jpg files.
Hopefully this will help you make similar changes on your own, at least until Google comes up with an easier method for changing skins and such. And maybe a wallpaper gallery thats not static!
Being able to do things like this are what I was hoping for when I bought the G1, sucks that they won't allow people to choose to enable root.
I just saw a detailed post from Living_Sword over at modmygphone on how to make the re-signing thing work. Thought y'all might be interested
http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
JesusFreke said:
I just saw a detailed post from Living_Sword over at modmygphone on how to make the re-signing thing work. Thought y'all might be interested
http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
Click to expand...
Click to collapse
Looks alot like the method you described above... umm... there any way to backup text messages yet.. iv'e got a few hundred that i'd like to keep :*(
VR4Stryph said:
Looks alot like the method you described above... umm... there any way to backup text messages yet.. iv'e got a few hundred that i'd like to keep :*(
Click to expand...
Click to collapse
It is. He took my idea and ran with it.
Re: backing up text messages.. not sure. Let me play with it a bit and get back to you
JesusFreke said:
It is. He took my idea and ran with it.
Click to expand...
Click to collapse
lol I never ran away with your idea. I acknowledge it as yours and thanked you for the idea in the original post here.
I know we are all trying to get the best out of our G1 and stealing ideas isn't the right way to go about it. Hope I cleared all misunderstandings
I didn't mean that in a bad way I saw your article and was like "oh cool! He got it to work."
just to clarify...
the default wallpapers you see in the Wallpaper Gallery activity are embedded in Launcher.apk?
i always thought it read some directory of images.
i guess that explains why the process for converting images from the Pictures activity requires crop/resizing and the gallery activity doesn't.
JesusFreke said:
I just saw a detailed post from Living_Sword over at modmygphone on how to make the re-signing thing work. Thought y'all might be interested
http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
Click to expand...
Click to collapse
If i am just modifying a pic (.png) in the apk, does the apk still have to be resigned?
yes, it does need to be resigned.
Modifying Wallpaper Gallery
ive been trying to find a way to add my own wallpapers to the gallery and it seems its no easy task, isnt there a way to redirect the path to make it look in a directory? im a linux noob (especially on devices like this) so if im asking a dumb question i dont know that i am
also.. if the only route is to modify the launcher package, is it possible to add as many as you want? or is there a limit to how many you can put in/replace?
best bet is to modify the apk (i think it's launcher but it may be framework-res) but as far as i know you can only replace the wallpapers there unless you wanna try some hex edits
Apotheo said:
I downloaded the android source from here http://source.android.com/download then slightly changed the source for Launcher.apk and recompiled it (make Launcher).
Click to expand...
Click to collapse
im trying to create my own Launcher.apk so i can include my own wallpapers into the Wallpaper Gallery. Everytime i type "make Launcher" (im in the /packages/apps/ dir) it just says:
make: Nothing to be done for `Launcher'.
so i figured i would try going into the Launcher dir, then trying it... then i get this:
make: *** No rule to make target `Launcher'. Stop.
how do you compile these things? ive also tried opening it in eclipse with the android plugin but when i try to compile it tells me to fix like 300 something errors first.
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.
Myself and apparently many others like the AOSP apps better than the sense apps. I find the interface for the AOSP messaging, calendar, browser, calculator, and dialer/contacts applications to be more attractive and in some cases more usable. I really liked Bugless Beast 0.4 since it featured these applications, but I have had a hard time with the bug that keeps disk drive from working, and there are various reports of some syncing and battery issues. The EVO-NonSense series has been great too, but I use HDMI out sometimes and like having some of the sense stuff installed. Big thanks to both BuglessPete and tjohnsonjr for their AOSP work.
(7/18/2010) I have attached some of the files I have been using, see descriptions at the bottom of the post.
So since it took a little digging for me to figure out how to do this (even though to advanced users this is easy) I thought it might come in handy for other new users. Additionally I'm hoping by posting this someone can help me figure out how to get the dialer/contacts stuff working, I have the others working fine.
I've done the below on DamageControl, and I think another (baked snack maybe, can't remember). I'll probably throw together an update.zip that can patch these in place later, but I'd rather get the dialer/contacts part figure out first.
Setup:
1. You will need a fully rooted (toast root part 2, NAND unlocked) phone, and adb up and running. There are several explanations for both parts, but the ones listed in the "useful threads" sticky are joeykrim's for adb and toast's part 1 and part 2 for root.
2. I have been using the apk's from BuglessPete's bugless beast 0.4 ROM. The thread for it is available here.
Once you unzip the file, you will find the needed apks in the /system/app folder.
Note: Please donate to pete, he doesn't even have an EVO yet and is doing some great work. Hopefully if he has a phone to work on he can get some of these small bugs squashed and keep the development for BB going.
3. Backup your phone. If you don't know how to reboot into recovery and restore from a nandroid backup, you do not want to do this yet, especially if you want to try help me figure out how to get the dialer running. The idea with the dialer is to try different things until something works. In all likelihood you will hit a point where things are FCing so much you can't do anything. You will almost certainly need to restore from a Nandroid backup at some point.
Important: More than likely anything I list here can't break a phone in a way that a nandroid restore won't fix, but I can not and will not be accountable for any problems with your phone.
Which files:
One nice thing about adding files this way is you can pick and choose what to use. If you like the stock messaging but want the AOSP calendar, you can do just that.
Calculator: Calculator.apk
Calendar: CalendarProvider.apk and Calendar.apk
Default "Navigator" application: CarDock.apk <- you can keep both
Internet: Browser.apk and HTMLViewer.apk <- doesn't show previews of each tab, but allows up to 8 instead of 4. There may be other functionality gained or lost, I dunno.
Clock: DeskClock.apk (can exist beside HTC clock, and can be installed without this procedure)
Messaging (SMS, Text): Mms.apk <- Many people have trouble with this one.
####### Not Working! See post #2 ########
# Phone: Phone.apk, ContactsProvider.apk, Contacts.apk
###################################
To install:
I think you can use adb to do this install with the files still on the computer, but I go ahead and throw all the needed apks onto my sdcard, typically in a folder. Also, if you need to be in the Android SDK's /tools directory to use adb (this depends on your configuration) do that. Connect your phone, and make sure it is in "Charge Only" so the sdcard stays mounted. To make sure adb sees the phone properly issue:
Code:
adb devices
and you should get a return listing the device ID. If so we will mount the /system partition as read-write:
Code:
adb remount
Log into the phones local shell:
Code:
adb shell
you are now on the phones command line and file system, not on your local machine. Now we can start installing files. I'll use Calculator in this example, and I have the apk in a folder on the sdcard called AOSP_apks:
Code:
install /sdcard/AOSP_apks/Calculator.apk /system/app
You can do a couple at a time, and you must do more than one at a time when installing a provider like CalendarProvider.apk and Calendar.apk.
Once you are done, exit the phone's shell, and reboot the phone:
Code:
exit
adb reboot
The change may show up immediately, but the phone and applications aren't designed to change these core functions on the fly, so make sure to reboot the phone. Once it reboots you will probably notice the AOSP icon has replaced the former, and you have the AOSP skin and/or functionality.
Post #2 will deal with progress so far on the dialer/contacts.
(added 7/17) Notes on different apks: The BB Launcher2.apk has his skin on the google search widget, or grab the apk from something else like DC for stock. Launcher.apk from BB is the one with the wide drawer and (I think) 9 screens.
Music.apk from DC is the modded music app from Cyanogen. It has some very nice UI tweaks.
Attached:
- Music.apk used in Cyanogenmod from DC
- Calendar, CalendarProvider, Browser and HTMLViewer from BB 0.4
- CarDock, Calculator, and MMS from AOSP EVO-NonSense
Contacts/Dialer Progress: I'm sure some of the more advanced developers know the answer to this, so ideally someone can fill me in. In the meantime I'll report my findings here, and if others can add feedback to the thread on what they have done, I'll update this post. Hopefully in the long run there will be a straightforward explanation for this I can add to the above post.
I have installed the three files listed above (ContactsProvider.apk, Contacts.apk, and Phone.apk) which seems to install the right bits, but I get FCs.
Later on I added Telephony.apk and FutureDialService.apk, which didn't improve anything. Finally I noticed that Bugless Beast didn't have HTCDialer.apk, so I removed that as well. I think this was the point things went from the dialer and contacts applications FCing to non-stop FCs that kept me from doing anything on the phone.
Attached are the three apps I'm sure are involved for the Contacts/Dialer, pulled from tjohnsonjr's AOSP EVO. More files may be needed, but I'm still trying to figure out which.
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
RikusHaven said:
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
Click to expand...
Click to collapse
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
warmachine69 said:
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
Click to expand...
Click to collapse
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
MikeBrWade said:
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
Click to expand...
Click to collapse
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
laydros said:
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
Click to expand...
Click to collapse
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
84th hour of a battery duration test? details please?
MikeBrWade said:
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
Click to expand...
Click to collapse
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
davebu said:
84th hour of a battery duration test? details please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7154719&postcount=993
This is my post talking about it.. I am on hour ~91 of the test.. still running with 8% battery left... BBv3 rocks!
laydros said:
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
Click to expand...
Click to collapse
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
MikeBrWade said:
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
Click to expand...
Click to collapse
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
If you have the AOSP apps available, could you please post them all in .zip folder in the OP?
MikeBrWade said:
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
Click to expand...
Click to collapse
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't run at all . Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
MikeBrWade said:
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't. Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
Click to expand...
Click to collapse
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
I[E said:
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
Click to expand...
Click to collapse
Interesting that you say that, since I had some MMS texts in my cache. Wondering if when the AOSP version couldn't deal with them so it just FC'ed instead.
So I tried that, deleting ALL my texts so it wouldn't have some MMS collision or something. But that didn't work either, HTC Mms.apk works fine.. the AOSP.apk FC's. Could the OP or something with a working AOSP Mms.apk post it maybe it's my copy. Mine has an MD5 of : 441e3b8863bc3ab88ce6ad9bc1671f22
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
I going to upload all the AOSP apks that I include in my ROMs when I get home tonight.
Can you tell us how you got contacts.apk to work? I'm trying with FreshRom and I pulled the Contacts.apk from your Rom and it won't recognize the file when I push it using adbshell. The file is in the app folder but android ignores it.
I[E said:
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Does does your md5 match mine?
How do we hack the Home Screen Tips Widget?
There seems to be one included with a few roms. I'd like to be able to change it so that I can use it to learn Japanese words. Is it just a question of editing an xml file or something? Does anyone know where it is stored? If it is baked in a rom, is it therefore impossible to edit?
Thanks.
Decompile the apk, and inside the /res/values/ directory look at the arrays.xml file
CM source -> HERE
Thanks a lot!
I'll get to it.
I'm unable to get it to work at the moment. I've been following this video tutorial too. Are there any obvious things I could be doing wrong please?
I can decompile the apk and rebuild it after changing it. The apk will run but fail to install. Or if I install it in a zip file and via Recovery it seems to install but doesn't show up in System/Apps. (I'll try pushing it with adb)
How do we disable verification? (10:40)
(I'm using CM7 7.02)
Thanks for any help.
Grant Barker said:
I'm unable to get it to work at the moment. I've been following this video tutorial too. Are there any obvious things I could be doing wrong please?
I can decompile the apk and rebuild it after changing it. The apk will run but fail to install. Or if I install it in a zip file and via Recovery it seems to install but doesn't show up in System/Apps. (I'll try pushing it with adb)
How do we disable verification? (10:40)
(I'm using CM7 7.02)
Thanks for any help.
Click to expand...
Click to collapse
You cannot replace a "system" app with an apk which is not signed as a "system app". I had the same issue when I started fixing the DCIM incompatibility in the stock Camera app.
My question for you is: do you have the arrays.xml file already compiled to suit your needs? What phone do you have (HDPI, MDPI, LDPI)? I can make you a custom widget and send it to you.
That's very kind of you hrk.
The phone is an HTC Desire HD.
I should keep trying to learn to do it myself to be honest because I'll be changing it every couple of weeks hopefully, once I learn certain words etc.
Maybe you could talk me through the steps you take or maybe you use different methods or a different program compared to the video?
Anyway thanks for your kind offer.
Grant Barker said:
the steps you take or maybe you use different methods or a different program compared to the video?
Anyway thanks for your kind offer.
Click to expand...
Click to collapse
I set up a build environment (read "I can cook ROMs"). This way I can modify the original Protips project, and then build the apk with the AOSP signing key. If you are running a Stock ROM or a customROM which has not changed the signing keys (e.g.: CyanogenMod uses the same key AOSP uses), the Protips.apk will work flawlessly.
Setting up a build environment requires a bit of time and around 5 GB of hard disk, but it's something everybody can do. The beauty and winning point of Android Open Source Project.
That's great. Thanks hrk.
I'll follow your advice and set up a build environment..
hrk said:
....
Setting up a build environment requires a bit of time and around 5 GB of hard disk, but it's something everybody can do. The beauty and winning point of Android Open Source Project.
Click to expand...
Click to collapse
It's good fun. I just finished the example project Hello World.
I'm pleased I listened to you.
Grant Barker said:
It's good fun. I just finished the example project Hello World.
I'm pleased I listened to you.
Click to expand...
Click to collapse
That's good to hear, but when I wrote "build environment" I meant the entire platform.
With the Android SDK you can build apps, but you won't be able to properly sign them: you can have your own signature and publish them in the Market, but you can't "re-sign" system apps.
Good work!
Ah. I see what you mean.
Maybe that will be the next step in the near future.
In the meantime I'm inspired to make a similar app/widget from scratch which will do what I need..
Thanks.
Grant Barker said:
Ah. I see what you mean.
Maybe that will be the next step in the near future.
In the meantime I'm inspired to make a similar app/widget from scratch which will do what I need..
Click to expand...
Click to collapse
I've had the same idea for a while now! That widget is pretty nice and could be transformed in something pretty cool
Hi did you manage to edit the homescreen tips widget,
I'm finding all over the internet and can't find a solution
_Sparks said:
Hi did you manage to edit the homescreen tips widget,
I'm finding all over the internet and can't find a solution
Click to expand...
Click to collapse
I have the same problem... im trying to hack it (changed te arrays.xml) but it still needs that damn system signing could anyone help?
Is there any other way than installing 5gb of stuff just to sign one .apk
jazux said:
I have the same problem... im trying to hack it (changed te arrays.xml) but it still needs that damn system signing could anyone help?
Is there any other way than installing 5gb of stuff just to sign one .apk
Click to expand...
Click to collapse
dude could we use apk signer or any other stuff?
_Sparks said:
dude could we use apk signer or any other stuff?
Click to expand...
Click to collapse
I think no because we need the system signing key
Any signer should work. But depending on how you edit and build the apk, you might not be able to "install" it, but have to push it instead
Sent from my HERO200 using XDA App
kyouko said:
Any signer should work. But depending on how you edit and build the apk, you might not be able to "install" it, but have to push it instead
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I decompiled it, replaced arrays.xml compiled it TRIED to sign but i got error "unable to sign system application" or something like that
Hmm, I'll check it out and see..once the power is back on in my area
ComEd said it could be up to two days because of the storms lol
Sent from my HERO200 using XDA App
jazux said:
I decompiled it, replaced arrays.xml compiled it TRIED to sign but i got error "unable to sign system application" or something like that
Click to expand...
Click to collapse
Read my previous posts on this very topic.
You can't sign a system app without using the system key. It can't be easier than that.
I downloaded the netflix.apk that has been floating around, and with a few tweaks to my build.prop, I was able to get it to work on the galaxyXT ROM.
You have two choices, either download the attached build.prop file and stick in into your /system/ directory... or make the modifications yourself. FYI, please make a backup of the original build.prop before you mangle it.
I changed three lines in my build.prop. Just find these lines in your build.prop and change them to this:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2.1/FRF91/277427:user/release-keys
Reboot, and that worked for me! If you have different experiences, please be sure to post them here.
FYI, If you make the changes yourself, make sure they are exact, case and everything. Use Notepad++.
Enjoy!
how/where do you access the /system/ directory? I looked on my SD card but cannot find.
thx
c_urbanek said:
how/where do you access the /system/ directory? I looked on my SD card but cannot find.
thx
Click to expand...
Click to collapse
Not on your sd card.
It is in the /system/ Use Root Explorer or something like it.
It's in the phones internal memory, not on your sdcard. You would either need a file explorer with root access (e.g. Root Explorer) or you need to push it with adb.
tried using root explorer & it says the system files are read only...
Nevermind, clicked the R/W button & it allowed...
I'll try Netflix now after a reboot.
At the top of window while in root explorer you'll see a MOUNT R/W button, you need to toggle on read / write access.
Wow! Works Beautifully!
Wow! Works Beautifully! Thank YOU!
Work on Dexter's 1.3 too!
Sorry for the ignorance but what is it?
Streaming movie/TV service. Not everybody has it, but its a big deal for Android phones to FINALLY get it since iphone and Windows 7 phones have had it for a while.
I'm not sure, but there are several apk XDA of netflix, and other folders, I can not understand yet. Apk is installed, replace the buildprop and that would be enough? You may be able to give us the link to the apk please because in my market does not appear.
For the payment of subscription must be from the website or can be within the application?
The truth was unaware of this application, it looks very interesting. Thanks for sharing.
can someone share here the apk..tq
This is where I downloaded it from
3rdstring said:
This is where I downloaded it from
Click to expand...
Click to collapse
Thanks for posting that. I couldn't remember where in the forums I had found it.
Hey I'm running stock 2.1 rooted on the xt720. I swapped out the build.prop you supplied in the .zip and installed numerous versions of the netflix clients to see if any would work. The apps installed fine but when I tried to open them (every single one) just opened to a black screen, then it force closed with a bunch of Japanese lettering. Any suggestions? Thanks.
donovanx3 said:
Hey I'm running stock 2.1 rooted on the xt720. I swapped out the build.prop you supplied in the .zip and installed numerous versions of the netflix clients to see if any would work. The apps installed fine but when I tried to open them (every single one) just opened to a black screen, then it force closed with a bunch of Japanese lettering. Any suggestions? Thanks.
Click to expand...
Click to collapse
Unfortunately
"Latest version: 1.2.0 build 819145-1.2.0-102 (for Android version 2.2 and higher)"
I got Netflix installed and everything seems to work. But when I hit play, it starts to load and says that I don't have a Netflix ready device. I have Dexter Froyo v1.3 on XT720. Anyone have this problem?
see 1st post in this thread....
ErnFuggit said:
I got Netflix installed and everything seems to work. But when I hit play, it starts to load and says that I don't have a Netflix ready device. I have Dexter Froyo v1.3 on XT720. Anyone have this problem?
Click to expand...
Click to collapse
once you install the apk, you need to do the hack rev explained in the 1st post.
New APK
Has anyone tried the new "stock" Netflix apk with the XT720?
I running the 1.20 APK, haven't seen an apk for the 1.21 yet, though I haven't gone looking yet either.