Database Info

Guide to remove Moxier mail and replace with new version

Hi
This is for those who actually use Moxier mail to get that needed exchange fix!
I use exchange for my job, so I needed this one badly, and I would like the newest one with nice little widgets. Unfortunately this can not be done out of the box, because when you try to install the newest version, the installer still detects the old one.
The problem is that the package information is still present in the package.xml file.
To fix this, you need to have completed to rooting guide!
http://forum.xda-developers.com/showthread.php?t=711907
Remember also to see post number two inside that thread, since su needs to be working properly. I can also recommend to download the latest version of busybox inside the Android Marked, this will provide you with mere unix/linux basic commands.
Another tool I use is SciTE, this is for editing the xml file, notepad will do, as long as you make sure to save as ASCII.
http://prdownloads.sourceforge.net/scintilla/Sc212.exe
Ok, now for the guide.
Go into your step4 folder from the ROOT folder (see root thread)
run the following commands.
**UPDATE**
In case moxier still exist more actions is needed, this is now included in this one! Also added backup of the original files both moxier and packages.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell
su
mkdir /sdcard/backup
cp /system/app/moxiermail* /sdcard/backup
rm /system/app/moxiermail*
Code:
adb pull /data/system/packages.xml .
You will now have a file named packages.xml inside your working folder.
Open this file inside you editor.
search for com.moxier.mail
delete the following content
Code:
<package name="com.moxier.mail" codePath="/system/app/moxier.apk" system="true" ts="1277719108000" version="2153" userId="10019">
<sigs count="1">
<cert index="61" key="long key number here!" />
</sigs>
</package>
Save the file.
Now We need to get the file onto the device.
Run
Code:
adb push packages.xml /sdcard/packages.xml
adb shell
su
cp /data/system/packages.xml /sdcard/backup/packages.xml
cp /sdcard/packages.xml /data/system/packages.xml
chown system:system /data/system/packages.xml
chmod 664 /data/system/packages.xml
rm /sdcard/packages.xml
reboot
Now you are free to install Moxier from market or from the official website, finally we can get the newest version instead of SEs old version.
** UPDATE 2 **
If moxier report an error with install after this, install the version from the /sdcard/apps/moxiermail.apk (from the root) or /sdcard/backup, then uninstall, this can now be done, since we removed the package from packages.xml as a system application. You should now be able to install moxier from market.
Feel free to ask any questions.

Just out of curiousity, does this allow you to upgrade the moxier client that came free on the phone, or just allow you to uninstall that and purchase a newer version of moxier for 30 bucks?
Sent from my X10a using XDA App

uabtodd said:
Just out of curiousity, does this allow you to upgrade the moxier client that came free on the phone, or just allow you to uninstall that and purchase a newer version of moxier for 30 bucks?
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Unfortunately it is not possible to update the one provided by SE, even if you reinstall the application after the fix.

does it update to the lastest with step4 v2?

robbyf66 said:
does it update to the lastest with step4 v2?
Click to expand...
Click to collapse
No, you have to get the latest Moxier from moxier.com, Android Marked or from another source if you already have paid for the application on another phone.
This method cleans the X10 from any moxier reference, so that the application can be installed in the user domain instead of a system app (where we can't update the applications without SE).

I had thought that changes firmware version to R2BA020 included updated moxier?
I'll try to steps after my 4th root. lol. I need exchange for work.

I'm on the stock firmware(with Rogers in canada.. don't remember what its called) and exchange works fine for me on Moxier... use it regularly at work so its pretty useful
Edit: Sorry, misread your post. The new version has widgets? Coool

robbyf66 said:
I had thought that changes firmware version to R2BA020 included updated moxier?
Click to expand...
Click to collapse
SE only included a small updates version 2.1.58.3, this one is from February 17th, the newest version is 2.7 and is from May 26.
pngface said:
I'm on the stock firmware(with Rogers in canada.. don't remember what its called) and exchange works fine for me on Moxier... use it regularly at work so its pretty useful
Edit: Sorry, misread your post. The new version has widgets? Coool
Click to expand...
Click to collapse
Yeah, the widget came in 2.5 (finally)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I can afford to pay 25 for the extra features.
Should be able to upgrade via market imo
Sent from my X10i using XDA App

I allready removed the Moxierfolder and tried to install 2.5 but it's still a system application. Your walkthrough doesnt work here because of that. What can I do?
I editted the packages.xml file by copying it to my sd card en editting it on the computer. When i want to replace the original xml file can i use the following code?
Code:
cp /sdcard/packages.xml /data/system/packages.xml
chown system:system /data/system/packages.xml
chmod 664 /data/system/packages.xml
rm /sdcard/packages.xml

Erwinn said:
I allready removed the Moxierfolder and tried to install 2.5 but it's still a system application. Your walkthrough doesnt work here because of that. What can I do?
I editted the packages.xml file by copying it to my sd card en editting it on the computer. When i want to replace the original xml file can i use the following code?
Code:
cp /sdcard/packages.xml /data/system/packages.xml
chown system:system /data/system/packages.xml
chmod 664 /data/system/packages.xml
rm /sdcard/packages.xml
Click to expand...
Click to collapse
Yes you can, as long you are root on your phone. After this, install the OLD version of moxier and uninstall it again, this will update all the phones databasen and you can now install the newest moxier.

What do these commands do?
chown system:system /data/system/packages.xml
chmod 664 /data/system/packages.xml
Cant I not just edit the file and then overwrite the old one with the new editted one using a file manager like Root explorer? Or do these commands do something to the file as well?

this sets the file permissions for the file, and yes, you need to set them in order to get it working.

rofl, anybody needs moxier-mail? Noooo...

QuentinCosta said:
rofl, anybody needs moxier-mail? Noooo...
Click to expand...
Click to collapse
Yes it's actually a pretty good application for exchange users. Probably better than any I have used in the past.

Candy[MAN] said:
What do these commands do?
chown system:system /data/system/packages.xml
chmod 664 /data/system/packages.xml
Cant I not just edit the file and then overwrite the old one with the new editted one using a file manager like Root explorer? Or do these commands do something to the file as well?
Click to expand...
Click to collapse
You should do:
chown system.system /data/system/packages.xml
if you do chown system:system /data/system/packages.xml it will return:
"No such user system:system" as it won't detect the : as a separator between user and group.
Hope this helps some of you!

Speaking of the Moxier, do we actually need them? How do I remove / delete them? I tried, but couldn't, for some reasons.

If u don't use it then u don't ready need it. Your phone needs to be rooted in order to remove it!
Sent from my rooted 026 X10i using swype via Xda

Hi
can anyone make a script in .exe for dummies.
i dont understand all that stuff about programming.
anyone??
Singh

Q: How could you guys access the control prompt panel? Or the code panel, whatever you called it nowadays?

[HOW-TO] Stock Apps for All!

After two days of fumbling around with adb, numerous nandroid backups, and ultimately wiping my system, I, with the help of my friend Kiraly (his xda username), have successfully installed the stock Messaging, Clock, Calculator and Browser apps onto my phone.
The Messaging app was of particular interest to me because I hate how the HTC Sense Messaging app always loads briefly when you enter a thread of messages, no matter how many messages are in the actual thread. Also, the stock Android Messaging app has a feature similar to BBM in that an icon within the thread notifies you when a message has actually sent.
By following the instructions contained hereunder, you agree to indemnify and hold harmless the original poster (the "OP"). I hereby disclaim all warranties and liability for any harm that may result by following the aforementioned instructions.
Installing these apps was fairly easy once we found out how it needed to be done. You will need the following:
A. Minimal knowledge of adb, or rather knowledge of how to copy and paste adb commands.
B. You will need full root (root and nand unlocked)
C. 1.47 kernel with the modified default.prop file http://forum.xda-developers.com/showthread.php?p=7138666
D. The Root Explorer app (this can be purchased in the Android Market)
E. You will need the following .apk files from BuglessBeast. They are the only apps that I have been able to successfully install. http://forum.xda-developers.com/showthread.php?t=700175
-Mms.apk
-Browser.apk
-DeskClock.apk
-Calculator.apk
STEP 1
Perform a nandroid backup.
STEP 2
Plug your phone into your computer via USB and mount the sd card.
STEP 3
Download the 1.47 kernel with the modified default.prop file. The stock kernel is also contained in the following link, and you can always revert back to it if need be. http://forum.xda-developers.com/showthread.php?p=7138666
STEP 4
Flash the modified 1.47 kernel .zip file to the root of your sd card (for all you rookies out there, simply drag the .zip file onto your sd card).
STEP 5
Reboot into recovery and install the kernel you just flashed. Then, reboot the phone.
STEP 6
Download the BuglessBeast ROM http://forum.xda-developers.com/showthread.php?t=700175
STEP 7
Unzip the BuglessBeast file. Open the unzipped file. Find the folder labeled "System", and open it. Then, find the folder labeled "App", and open it. Find the files labeled Mms.apk, Browser.apk, DeskClock.apk and Calculator.apk. Drag those files to your desktop.
STEP 8
Download and open the Root Explorer app. Scroll down to the bottom and click on the folder labeled "System." Then, at the top of the app, click "Mount R/W." After you click that, open the "app" folder. Each application has two files you need to delete. Do not delete any of the clock files. You will need to delete the following files and then quit the application when you have finished:
-Browser.apk
-Browser.odex
-Mms.apk
-Mms.odex
-Calculator.apk
-Calculator.odex
STEP 9
Open the Command Prompt if you are a Windows user or the Terminal application if you are a Mac user and navigate to the tools folder of the Android SDK. Do not boot into recovery.
STEP 10
Type the following commands in order. We will use the Browser.apk as an example, and I will assume the file is on your desktop:
Code:
adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Code:
exit
Code:
adb push C:\Users\YourUserName\Browser.apk /system/app
Code:
adb shell
Code:
chmod 6755 /system/app/Browser.apk
Code:
exit
Code:
adb reboot
STEP 11
Rinse and repeat!
Thanks to frankenstein\ for the kenel, laydros for getting me started in the right direction, BuglessPete for the .apk files, and most importantly to Kiraly for all his assistance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

<3
10 char

I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.

kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.

neckface said:
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.
Click to expand...
Click to collapse
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.

kpoz said:
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.
Click to expand...
Click to collapse
Yup, same with Linux.

Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.

kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.

tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
Glad it worked for you! Thanks for attaching the Mms.apk.
I'm glad that slow, unresponsive Sense Messages app is long gone. You know there is something wrong with your app (*cough, HTC, *cough) when you get a "Loading" message when opening a thread, regardless of how many messages are in said thread.

initial said:
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.
Click to expand...
Click to collapse
Thanks for confirming.

tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.

initial said:
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.
Click to expand...
Click to collapse
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.

kpoz said:
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.
Click to expand...
Click to collapse
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.

initial said:
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.
Click to expand...
Click to collapse
Originally, Kiraly and I tried pushing these files and then using a shell to install them, but it resulting in a ton of force closes. We couldn't open any of the apps.
Regrettably, I'm not savvy enough to attempt to fix this issue for you if you are running a ROM like DC, especially a deodexed ROM. Best of luck to you.
Maybe the install command will work for you where it failed for me.
Try the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
exit
adb push :\Users\YourUserName\Browser.apk /sdcard
adb shell
install /sdcard/Browser.apk /system/app
exit
adb reboot

[How-To](UPDATED 11/1/10)Working Marketplace in 2.2 Emulator (no system.img)(ROOTED)

This all started out as an experiment to get my nandroid system.img file running in the adb emulator. Well sadly I haven't been able to do that (yet) but I have found something useful. I've Seen several people all over asking how to get a working marketplace app in 2.2 on the adb emulator. After a lot of researching (and trial and error) I've managed to get one. Here are the steps I've taken. (Steps 5 and 6 optional, you can just use the included build.prop if you prefer)
1) Create an avd running 2.2 (froyo,plenty of places explain how to do this so I won't)
2) Download the file (attached below, root files included)
3) Unzip to a location that's easy to remember and find.
4) Load your emulated phone (allow it to load fully)
5) enter this command in a command prompt/terminal window (make sure you "cd" to the directory where you extracted the files)
Code:
adb pull /system/build.prop
6) Remove or comment "ro.config.nocheckin=yes" (no quotes, might be able to just change it to "no" but I haven't tried it that way)
7) enter these commands
Winblows (I mean windows)
Code:
adb remount
adb push build.prop /system/build.prop
adb install GoogleServicesFramework.apk
adb install Vending.apk
adb install Gmail.apk (optional but sometimes signing in here lets the market sign in)
adb shell rm /system/app/SdkSetup.apk
Linux
Code:
adb remount
adb push ./build.prop /system/build.prop
adb install ./GoogleServicesFramework.apk
adb install ./Vending.apk
adb install ./Gmail.apk
adb shell rm /system/app/SdkSetup.apk
8) Sign in. If it works you're done if not reboot and try again, sometimes it takes 3 or 4 reboots to set. If your emulated phone has a data signal from your computer (you'll see a 3G and network icon in the notification area) just wait for it to sign in. The cancel button should grey out within a minute. If it says it can't connect restart the emulator and try again, be patient.
There is a known bug that not all apps show up in the marketplace. I'm not sure why so if someone here knows how to fix that by all means leave a post and let me know. If I see it I'll add it to the first post (provided it works of course )
Edit: Working on getting root on the emulator (just for the hell of it). So far I have su in the xbin directory and superuser.apk installed. Not 100% sure what else I need to do to get the su requests to go through though, I'll probably PM a more experienced member and post back when I have more. Got root? I do (got it working.) Here are the steps you need to take.
Rooting the standard android image on the emulator
1) Open a command prompt (cd to the directoy where you extracted the files)
2) enter these commands
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
adb push su /system/xbin/su
adb shell chmod 06755 /system
adb shell chmod 06755 /system/xbin/su
adb install superuser.apk
That's it! You now have a rooted, market-enabled android emulator.
New! N00b-friendly method
1) create your avd
2) download the emulator files archive attached to this post
3) extract somewhere easy to find
4) open command prompt/terminal and cd to the extracted location
5) start your avd
6) Run your script (windows.bat or linux.sh)
7) sign into market and enjoy root!
Note:
You may have to chmod su again upon restarting the emulator.
To get root back simply run the re-root script for your OS (bat for windows,sh for linux)
To install busybox simply run the re-root script, it will automatically install if you're using the script to install on a new avd.

Post 2
[reserved for updates, explanations, pictures, present/future tweaks in progress, etc]
Pictures:
Superuser list,Marketplace (I like solitaire><), Terminal with su permissions, and re-rooted Terminal​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tweaks:
1: root (done!)
2: busybox (done!)

Wow nice....

Thank you the root resets after reboot, working on making it stick but its not hard to do it again, just start with the "-wipe-data" command and redo the root, market works after reboot though. Still working on getting a dumped system.img to boot, ill post that in its own thread when i get it. Glad you like this.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Edit: see first post on how to get root back,no data-wipe!

so cool!! Good job man!

Thanks ^_^ let me know if you find any problems that I haven't already mentioned and I'll see if I can fix them or if they're just an emulator quirk.

Sorry for the double post but I wanted to let you all know busybox is now included! Installation can be performed through scripts (included in the "Emulator Files.rar" archive) or manually. If you wish to do it manually simply open the script in a text editor to see what's going on and enter the commands in a command prompt/terminal window.

I'm not able to make this work, not with a toolkit downloaded yesterday anyway.
Pulling of build.prop works, but pushing fails with a directory related error.
"adb shell" followed by "cd /system" and "ls -l" gives a list of files that does not include build.prop, neither as a file nor as a directory.
"ls -l build.prop" works though, and lists a file with 0644 permissions.
Install of all apks different from Gmail fails, with an error that says that those apks are already installed. Uninstalling them through adb doesn't work, netting instead a simple generic error.
Does anyone know whether I'm doing something wrong or Google has modified the emulator images so to render the Market workaround unusable? If so, where could I download an earlier version of the 2.2 system image?
Many thanks
Rocco

I actually had this issue as well. Try re-making the avd, worked for me. You could also try running the scripts to install, might work. If it doesnt post back and ill post the system.img from my sdk.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

I have the same problem as ropi. Remade the avd several times with different properties, still no go.
I would really appreciate it if someone could upload a fully set-up avd somewhere.

I'll try again late this afternoon (I'm on CEST). Hope it works. If not, I'd be happy too if some kind soul would upload a link to a working avd
Thanks for the kind help
Rocco

I have no idea why people are having so many problems :/. I had the problem and once I remade the avd it went away. Try starting with the -partition-size 96 option and see if that helps. If not here are the files, just extract to your avd directory, it has the ini and img files you need and it's already setup. Just run re-root to get root back and sign into market and you're good to go.
http://hotfile.com/dl/79959332/3efbade/froyo-avd.rar.html
Edit: I just downloaded the latest revision and everything seems to be working fine :/ As I've said before try starting with -partition-size 96 and also try using the scripts I've provided. That should fix the issues, but if it doesn't there's always the hotfile link I've provided (or if you're just lazy lol)
Edit 2: also,just thought of this, make sure before you push the build.prop you adb remount. Pulling will work fine without doing that but pushing won't. No one said if they had done this and still received the errors so I'm trying to cover all bases. If remount fails try the adb shell mount command posted on the first page.

Thanks dbzfanatic, that avd worked great.

Glad it worked for ya. Let us know how everything works.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

A lot of apps can not be found in the Market ... I cannot find Lookout....

Yeah, I've mentioned that,firs post. It's a known bug. Nothing I can do to fix it at the moment. You could download the apk on your phone then pull it then install it in the emulator. Bit of a roundabout way of doing things but it's all we can do on the emulator for the time being, at least from what I know.

Ok after a bit of poking around (sorry it took so long) I found out a bit about the market. It seems it's not just your region that it uses to show apps but things like your carrier, presence/absence of a SIM card, Android version, etc. It uses the filters to choose which apps to show and which to exclude (not showing an American user Japanese apps, not showing someone on Verizon T-Mobile apps, etc) so this explains part of the problem. I also found out that the SIM card and IMEI numbers were(are?) hard-coded into the emulator binary, changing these may allow us to see a few more apps. I looked through the binary file a bit and didn't find anything but I'll look more closely in a bit (new job, yay <- read as "groan"). I don't know how to emulate or spoof a carrier so that will still cut us back on some of the apps being seen. If anyone knows how to do this please post here and let us know! It would also be beneficial if a user who has already modified their IMEI and SIM numbers in the emulator to compare the apps list to the one you see in the standard, non-modded emulator binary and let us know if there is a difference or not. The more apps we can see in the marketplace the better!

Just wanted to confirm that I've tried Market Enabler a few days ago and it doesn't seem to work.

Alright thanks for the feedback. Ill keep working on it.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

Despite several tries, I've so far been unsuccessful in using this method to install the marketplace on a 2.2 avd. Many thanks for having provided ready-made avds, then!
I've been able to install marketplace on the Galaxy Tab images provided by Samsung, though!
Keep up the good work

[Q] Nexus S voice/sound recorder hidden and not installed?

Hi,i was searching for the stock voice recorder in Ice Cream Sandwich,but i did not find it...
So I've searched into phone memory (root /system/app) and i found Soundrecorde.apk ,bu if i try to install it,installation aborts saying "This application cannot be installed".
Why?

No one use voice recording on Ics?
Neo on Nexus S with Tapatalk®

bump?.......

.:Crack:. said:
bump?.......
Click to expand...
Click to collapse
???
Neo on Nexus S with Tapatalk®

..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
There is not much compatibility for this kind of apps and Ics...
Stock Sound recorder was perfect for me on Gingerbread,i don't understand why it's not compatible anymore...
Neo on Nexus S with Tapatalk®

not sure how you tried to install but you cant install system apps like other apk you have to sign it first....anyways i signed it and installed fine but dont give an option to open after install and still don't see it
edit
just for future reference if you edit an apk or want to install a system app like a normal apk
download Sighnapktic from the market its free and it does it right from your phone really easy to use
https://market.android.com/details?id=com.stericson.signapktic&hl=en

i used Sanity with gingerbread, but I don't know if it still works with ICS
https://market.android.com/details?..._result#?t=W251bGwsMSwxLDEsImNyaS5zYW5pdHkiXQ..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.

XK72 said:
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.
Click to expand...
Click to collapse
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®

..

(THE REAL) Neo said:
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Correct.
Election Day said:
Probably yes. I'm trying to modify the xml's at the moment, but I can't get any usable output.
If I can get it to work I'll post the modded apk here.
Click to expand...
Click to collapse
Directly after this line:
Code:
<action android:name="android.intent.action.MAIN" />
Add:
Code:
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />

..

You also just can use anycut from market and create a homescreen shortcut to soundrecorder.apk

Election Day said:
I guess this should be it. I unpacked the apk with apktool, added the lines, packed it again, unzipped it, added META-INF and rezipped it.
You can flash it with "adb push SoundRecorder.zip /system/app".
Click to expand...
Click to collapse
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®

(THE REAL) Neo said:
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®

jitzbox said:
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied
Click to expand...
Click to collapse
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
(THE REAL) Neo said:
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.

XK72 said:
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.
Click to expand...
Click to collapse
Using this apk,the phone shows me an app called "Recorder" in the app drawer,but i can't tap it,and all the icons showed in the same page of the app drawer.If i change page,icons of other pages are selectable...weird thing...
Now i'm rolled back to previous apk file and everything works...so scary...
Neo on Nexus S with Tapatalk®

[DIY-TUT/HOW-TO] Debloat and Save Battery

Note: This is not a ready made script that will do things for you. If you are looking for a script/tool to debloat your phone head here. This is a very basic guide, many of you might be aware how to do it already. This is for the absolute newbies like me who like learn by doing it themselves. So lets start!
First, What is Debloat? What are the benefits?
Ans: A new device (except the nexus family) always comes pre-loaded with a lot of manufacturer apps. Most of the times these apps are utterly useless to the end-user considering that there are better alternatives available on the play store. Such apps constitute the phone bloatware. Often these apps are part of the system partition on your phone ie they are system apps and cannot be uninstalled or removed like normal apps. The process of removing these apps is called as debloating!. Savvy?
Fine, Moving ahead. Whats more problematic about these apps is that many of these apps load at system start-up and keep running in the background using precious cpu and other resources apart from eating up memory. This often leads to poor performance and battery life. So once you get rid of these apps you will start experiencing better performance AND AN AWESOME BATTERY LIFE(personal experience)
Wow, I want to get rid of those stubborn apps...show me how to do it.
Sure
PRE-REQUISITES:
1. You should be rooted
2. Your phone should have the ClockWorkMod (CWM) Recovery installed.
3. You should have adb up and running
4. Turn on usb debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OPTIONAL:
1. You may want to create a Nandroid Backup through CWM before doing any of the steps listed below.
2. Install abdb insecure by chainfire to run adb commands as root(insecure boot image). This will allow you to boot in to recovery through adb. Once installed the app should look like this
The PROCESS:
1. Ensure that the pre-requisites are met.
2. Connect the phone to the computer through the USB cable
3. To check whether you have properly installed adb do this
Open a command prompt window (start>run>cmd) and type this
Code:
adb devices
If adb is set up and running it should list your device in the list of attached devices some thing like this
Code:
List of devices attached
42801c7449ff097 device
4. Now use the following command to make a backup copy of all the system apps on your phone
Code:
adb pull /system/apps C:\* destination of your choice *
This will ensure that you can install back any app that you remove using this process and also it serves as a reference to the list of system apps. Look at the apps and make a list of apps that you want to get rid off. This (thanx to winwiz for compiling it)might help you to decide which one's are important and which are not, which one's can safely be gotten rid of and which should not be touched. Play carefully. Here is a list of apps that I have safely removed with great benefits to boot-up time, battery and overall performance.
Dlna.apk
Dlna.odex
BuddiesNow.apk
BuddiesNow.odex
Days.apk
Days.odex
Email.apk
Email.odex
EmailWidget.apk
EmailWidget.odex
GameHub.apk
KiesAir.apk
kieswifi.apk
kieswifi.odex
Kobo.apk
MusicHub_N1.apk
MusicHub_U1.apk
PressReader.apk
ReadersHub.apk
ReadersHub.odex
SamsungApps.apk
SamsungAppsUNA3.apk
SamsungIM.apk
SamsungWidget_News.apk
SamsungWidget_News.odex
SamsungWidget_StockClock.apk
SamsungWidget_StockClock.odex
SevenEngine.apk
SnsAccountFb.apk
SnsAccountFb.odex
SnsAccountLi.odex
SnsAccountTw.odex
SnsAccountLi.apk
SnsAccountTw.apk
SnsDisclaimer.apk
SnsDisclaimer.odex
SnsImageCache.apk
SnsImageCache.odex
SnsProvider.apk
SnsProvider.odex
SocialHub.apk
SocialHub.odex
Zinio.apk
Click to expand...
Click to collapse
You may want to add/remove apps to/from this list.
5. Moving on, Once you have decided the apps to remove reboot into CWM recovery. Use this command to do that through adb.
Code:
adb reboot recovery
Note: You must have an insecure boot image for this to work (See point number 2 in optional points)
else
use any of the common methods to boot into recovery. Use key presses or CWM Manager or do whatever, just get in to that ******g recovery.
6. Next, Once you are into the recovery type this command in the command prompt
Code:
adb shell
This will get you into the linux shell on your android device so that you can use all the linux shell commands like in a regular linux shell
7. You must now see a # or $ at the prompt (doesn't make a difference) indicating that now you are into the linux shell. Type the following command in the prompt.
Code:
mount /system
This will load the system partition into memory so that you can play around with its contents.
8. Now to the most important step. Removing the apps. Use the following command in the prompt
Code:
rm /system/app/****.apk
or
Code:
rm /system/app/****.odex
Replace **** with the name of the apk or odex file that you want to remove.
Repeat the command for all the files that you want to get rid off.
Note: Remember to press enter after each command
9. Once you have finished removing all the bloatware just type
Code:
exit
in the prompt. Thats it.
Reboot! (You may use
Code:
adb reboot
for that purpose).
You will now be greeted with a faster performing, responsive, battery conserving and most importantly a bloatware free phone.:good:
10. Thank me if this helped and don't hesitate to ask questions.
As a supplementary note I would like to recommend this app [Requires Root]. Once installed use its corpse finder feature to eliminate all the left over files belonging to the bloatware apps that we just removed. It is as easy as Search and Clean. This will free up more space in your system partition.
Troubleshooting:
Q. I removed Kies Air using the method above but it is still present in the app drawer. What to do?
Ans: This happens if you have updated Kies Air through the play store.
Go to Settings>Applications>Manage Applications
Scroll down to Kies Air --> Select it ---> Uninstall updates
Reboot!. Thats it. Kies Air is gone for good.
A Very Important Note:
I haven't tried it on a Non-Rooted phone. But I think it should work as far as you have adb working and can boot into the recovery(Stock recovery in case of Non- Rooted phones) by some means you are good to go from step number 6.. Have a list of apps to be removed before hand, speeds up the process.
Battery Saving Tips:
Coming Soon.....!

RESERVED!!

Buddy we are already having automated tool for removing bloats ...

mj.vikram said:
Buddy we are already having automated tool for removing bloats ...
Click to expand...
Click to collapse
I'm aware of that buddy. I have even mentioned it in my post.:good: As I said this method is for people who would like to understand whats happening behind the scenes...rather than just flashing a script package.

The-Droidster said:
I'm aware of that buddy. I have even mentioned it in my post.:good: As I said this method is for people who would like to understand whats happening behind the scenes...rather than just flashing a script package.
Click to expand...
Click to collapse
Thanks for taking time and writing this :good:....
Nice guide and just one more alternative for user's if you feel this is difficult process for you, using Root explorer or similar app's got to /system/apps/ and delete the required file's (as mentioned by The-Droidster in the above) and restart the mobile...

What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
ICS = I SEE ASS Lol
++##» GALAXY R «##++

gitanshu said:
What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
Click to expand...
Click to collapse
its same buddy, both are same but this for the people who want to learn how to use ADB they can use this because this very well explained :good: ....

gitanshu said:
What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
ICS = I SEE ASS Lol
++##» GALAXY R «##++
Click to expand...
Click to collapse
I don't see any problem in doing that....but you may experience force closes if you do this when the system is online because the apps that you are removing are still running in the background. So it is better if you do it by mounting the system through recovery.

if uu have rooted phone than u can remove bloat using titanium backup or rom toolbox pro

+1 for using Adbd insecure. It's a great debugging tool on stock roms.
Sent from my GT-I9103

Adam77Root said:
+1 for using Adbd insecure. It's a great debugging tool on stock roms.
Sent from my GT-I9103
Click to expand...
Click to collapse
Yeah its like unleashing a new side of adb. Makes it all the more valuable