Database Info

Enable Superuser.apk & Enhance ROSIE UI FOR HERO ROM [Re-Updated FIXED]

Hello Guys!!!
Sorry for the problems caused There Were More Two Widgets Missing Other Than Messaging widget to be coppied to Internal Memory Namely The Clock & Contact Widgets, So They Are Added In The Re-Update, The Whole .exe Is To Be Downloaded Again, Sorry For This.
Even The superuser enabler package(.exe) is fixed...But If U already Have the old .exe , just get the attached script & replace it with the old one...
Be Tuned For Apps2Sd & An Rom With At-least 30 MB Of Free Internal Memory Build....M Currently Initializing Source Code So That Will Help Me With Some Stuffs Like Update-Script & Some Stabilization Of ROM...
SUPERUSER ENABLER
Thers no SuperUser Apk Working On Haykuro's Hero Rom, So to get It Working, Only Installing Is Not Enough So I have Got It Working, Follow This Steps...
Note: To Test, Just Try Using CPU Overclocker Widget(Its Free) From The Market Before & After Using This... u ll Notice the Change
Steps:
1. Download The Install-Enable-SU-By-Sangeet.exe & Extract Any where By Double Clicking It.
New Fixed Download Link: http://android-latest-build-images.googlecode.com/files/Install-Enable-SU.exe
2. Connect Ur Phone Via USB Cable
3. Run The Install-Enable-SU .bat File.
4. Choose Appropriate options..
5. Rebooting Not Recommended...(UR WISH)
Rosie UI Enhancer/Optimizer
Note: U Must not Be Using Apps To SD Other Than The Default app_s folder
Means U must Not Have /Data/app Moved to /System/sd/app
The Rosie UI Dosent Need The Launcher.apk, So This Script Removes It.
This Script Moves/Installs Rosie Application To Internal Memory...
MoreOver, The Rosie UI Uses The HTC Widgets Which Are Seperate Applications, So Even If The Rosie Loads Fast, The Widgets Make It Slow...
So This Script Even Moves/Installs The HTC Widgets To Internal Memory...
Steps:
1. Download The Fixed-Rosie-UI-Optimizer.exe & Extract Any where By Double Clicking It.
Download Link: http://android-latest-build-images.googlecode.com/files/Fixed-Rosie-UI-Optimizer.exe
2. Connect Ur Phone Via USB Cable
3. Run The Optimize_Rosie.bat File.
4. Choose Appropriate options..
5. Reboot The Phone (NEEDED)
Dex-Optimizing
After All That, The Widgets Would Take Some Internal Memory, So I Would Recommend Using The Dex Optimizer...
Steps:
1. Download The Dex-Optimizer.exe & Extract Any where By Double Clicking It.
Download Link: http://android-latest-build-images.googlecode.com/files/Dex-Optimizer.exe
2. Connect Ur Phone Via USB Cable
3. Run The DEX-OPTIMIZER.bat File.
4. Choose Appropriate options..
Credits: buttkicker (optimization script),
I Dint Know Hod to make such scripts with options Learned from HTC Hero Speedup vXX by tehseano so credits to him too...
If Any one else left inform me i ll add..

Please add this to the wiki and PM me the url so I can add it to the roundup thread.
Only post problems with the above thread. Do not go off topic.

ryanmo5 opened this thread saying it didn't work and it messed up his home screen.
Thank you ryan for trying this out and letting us know.

i tried this and it says no such file or directory on all files. And then it says it cant find .apks for all files to install. Ok i didnt even look at my home screen all my widgets are gone except the clock. When i try to add the htc widgets im left with only 4 widgets.

Also the Install-Enable-SU.bat did not work for me. Was stating batch was inoperable.

Yeah, the UI tweak totally borked my phone. It locks up at the HTC logo. I went back to ion till tomorrow.

WEE!!!
AWESOME. This is fantastic. Thank you for your hard WORK!! much appreciated! Seems to have worked like a charm for me and i can really notice a huge speed boost especially when going back to the home screen.
I have found my HEROOO!
Oh and btw, when you do the part to optmize for Rosie, the folder that contains the apks should be renamed from Rosie to Files. That will make things work. It did for me.
I miss the Rosie UI lock screen though... its gone?
But wow incredibly speedy and even a lot more stable? Thank you sangeet.003 and all the other FANTASTIC developers on this forum who keep me and my G1 busy with fun goodies.

Here is a oddball question, couldn't someone just create a update.zip with all this done? I'm not familiar with signing pkgs and what not. So I'm not 100%.

i'm a mac user.
but i kind of smart when it comes to these things so i got it to work.
but for other mac users do you think you can just up load the files and post the
adb commands.

kronosx1 said:
Here is a oddball question, couldn't someone just create a update.zip with all this done? I'm not familiar with signing pkgs and what not. So I'm not 100%.
Click to expand...
Click to collapse
I think i read somewhere that it wouldn't be possible because of how big the update.zip would be which is why when flashing Hero, you need the ext2 to store the apps_2
the great thing is, if you just keep testing, reading and messing around with running everything from roms, scripts, commands and tweaks, you eventually get things to work and and you find a huge satisfaction and semi-understanding of it all and you find yourself appreciating the developers here for their work.
Wow its four in the morning and i think im on a strong sugar high because i never post.

so changing the folder from rosie to files worked for you

ynghova187 said:
so changing the folder from rosie to files worked for you
Click to expand...
Click to collapse
yeah rename "Rosie" to "Files"

well did a refresh of Hero and applied all the tweaks here (after renaming the folder as well) and all is wel. thanks a ton for this!

I was wondering if you could use app2sd after using this mod, or will this disable apps2sd?

Ok i did it and it works but there is a slight problem the messaging widget dosent show up. its completely gone. i read the batch file and its missing from the batch file. If you could re write it with the htc messaging app included then this app would be perfect. Or does anyone know how i could get the htc messagine widget back by myself

ynghova187 said:
Ok i did it and it works but there is a slight problem the messaging widget dosent show up. its completely gone. i read the batch file and its missing from the batch file. If you could re write it with the htc messaging app included then this app would be perfect. Or does anyone know how i could get the htc messagine widget back by myself
Click to expand...
Click to collapse
I think if you placed the "Files" folder onto c:/android (or wherever you put adb) and then:
adb push files/htcmsgwidgets.apk /data/app
that *might* work, not sure because I haven't tried it myself.

sangeet.003 said:
Hello Guys!!!
SUPERUSER ENABLER
Thers no SuperUser Apk Working On Haykuro's Hero Rom, So to get It Working, Only Installing Is Not Enough So I have Got It Working, Follow This Steps...
.
Click to expand...
Click to collapse
That is weird because i have super user and terminal working on mine just fine from JF previous install

a few widget's were missing..
clocks & contacts
also in the batch file, the msg widget was not reinstalled onto internal memory(probably just forgot to add that line)
so I redid his batch file to include the 2 missing widgets as well as adding the line for the msg widget and changed the folder to files
cause I know how lazy most of you are
http://hotfile.com/dl/4938120/a4a6fc0/Rosie_UI_Optimizer__ALLwidgets.zip.html
and for the mac user's
just open the .bat file in text editor (.bat files are nothing more than text anyways) in there you can see each command that is run and do it yourself manually,...
yeah it's a ***** but I'm not about to figure out how to write a shell script for OSX on XP just to appease my old brethren, maybe pickup a copy of BBcode and insert the commands, don't know it that would even work, just a thought heh.
---credits to sangeet.003 for goin' through the trouble to make this batch files, I'm just an "editor"

everything worked perfectly and 20 times faster not exact but i see a huge difference just now noticed that the messages widget was missing so bout to add that thanks to all developers working hard im sticking with hero i know people love it as much as I do so it has to keep getting better

mpeezay said:
a few widget's were missing..
clocks & contacts
also in the batch file, the msg widget was not reinstalled onto internal memory(probably just forgot to add that line)
so I redid his batch file to include the 2 missing widgets as well as adding the line for the msg widget and changed the folder to files
cause I know how lazy most of you are
http://hotfile.com/dl/4938120/a4a6fc0/Rosie_UI_Optimizer__ALLwidgets.zip.html
and for the mac user's
just open the .bat file in text editor (.bat files are nothing more than text anyways) in there you can see each command that is run and do it yourself manually,...
yeah it's a ***** but I'm not about to figure out how to write a shell script for OSX on XP just to appease my old brethren, maybe pickup a copy of BBcode and insert the commands, don't know it that would even work, just a thought heh.
---credits to sangeet.003 for goin' through the trouble to make this batch files, I'm just an "editor"
Click to expand...
Click to collapse
Thanks I will Be re updating & uploading Both The exe Files...

[SCRIPT] Random Boot Animations v1.3 (Updated 2010-04-20, works on CM 5.0.6-5.0.8)

This script has only been tested with CM ROM, I cannot guarantee that it will work with other ROMs.
DESCRIPTION
I couldn't decide on one single boot animation to use on my phone, so I thought, why not start every boot with a random animation?
I threw together a simple script that will randomly choose a boot animation zip file from a directory and copy the file to /data/local. The script defaults to using /sdcard/bootanimation as the directory to store all the animations.​
INSTALLING THE SCRIPT
Extract 09bootanimation from the zip file, then type the following from your command prompt:
Code:
adb remount
adb push 09bootanimation /system/etc/init.d
adb shell chmod 750 /system/etc/init.d/09bootanimation
If you are using CM 5.0.6 - 5.0.8, you will need to do an additional step. The fstab file is missing, so extract fstab from the zip file and execute the following:
Code:
adb remount
adb push fstab /system/etc
Thanks to godsfilth for figuring out the fstab problem. =)
If you are not using CM ROM, you may have the init.d directory in a different location.​
Reminder: Because the script is installed in the system directory, you need to redo all the installation steps after upgrading your ROM.
INSTALLING BOOT ANIMATIONS
Create a directory called bootanimation in the SD card root directory, and put all your animation zip files in the directory. The script will only choose from zip files in the directory.
If you want to change the default directory, just change the variable in the script.
Thanks to godsfilth for getting it to work with SD cards! =)​
SELECTING A SPECIFIC ANIMATION
If you want to view a new animation, instead of rebooting repeatedly and hoping that it will be selected at random, you can use the following method.
Create a file called bootanimation.use in the bootanimation directory where you have placed all the zip files. The file should contain a single line with the filename of the boot animation, without the directory path. For example:
Code:
bootanimation-prash.zip
When you want to go back to random animations, simply delete bootanimation.use from the directory.​
HELP! I CAN'T GET THIS TO WORK!
If you have problems getting the script to work, grab the logcat of the startup process and post it to pastebin. You can get the logcat output by rebooting the phone and then immediately running
Code:
adb logcat > log.txt
Once the boot animation has started you can press Ctrl-C to stop the log collection. Please include in your post the ROM that you are running.​
SAMPLE LIST OF BOOT ANIMATIONS
For those who are looking for some boot animations to choose from, here's a small list of animations from other XDA threads. Feel free to recommend animations, and I'll update this list.
Prash's CyanogenMod 5.0
Qteknology's Nexus animations
Nighthound's Win7 Nexus
Nighthound's BSOD
Nighthound's Qteknology's Splash Inverted
nmeofdst8's Nexus One Red Flame Edition
iDance°-->ra1n's Ubuntu Nexus and Tiesto animations
Droid Eris thread with lots of cool boot animations​
FUTURE CHANGES
Eventually I might get motivated enough to write a simple program to simplify the entire process. It would be great if someone has the spare time to do so. ​
CHANGELOG
Version 1.3
Updated to work with CM 5.0.6 (push fstab to /system/etc) [thanks godsfilth again]
Added option to specify boot animation to use
Added logging output
Version 1.2
Changed filename to 09bootanimation to work with CM Apps2SD.
Version 1.1
Enables storage on SD card [thanks godsfilth!].
Added error checking for no animation files.
Version 1.0
Initial release.

Nighthound said:
I couldn't decide on one single boot animation to use on my phone, so I thought, why not start every boot with a random animation?
I threw together a simple script that will randomly choose a boot animation zip file from a directory and copy the file to /data/local. The script defaults to using /data/local/bootanimation as the directory to store all the animations.
Installing the script
Extract the script from the zip file, then type the following code:
Code:
adb remount
adb push 10bootanimation /system/etc/init.d
adb shell chmod 750 /system/etc/init.d/10bootanimation
Note that I'm running CM5, your ROM may have the init.d directory in a different location.
Installing boot animations
Do this once, the very first time you're using this:
Code:
adb shell mkdir /data/local/bootanimation
After that, use this to copy your animations:
Code:
adb push [i]animation-filename.zip[/i] /data/local/bootanimation
If you want to change the default directory, just change the variable in the script.
My knowledge of the Linux system is limited and I couldn't figure out how to access the sdcard during boot up, so unfortunately all the animations will have to reside in the data partition for now. Would be great if someone could help out with that.
Click to expand...
Click to collapse
Exactly what i was looking for thanks!!!!!!

Anyone else gonna touch this to get it to work off the sdcard?? That would make this so sweet!

good stuff! I altered this a bit to work from the sd card.
edit: I see godsfilth did too...nice

i got it working don't know if theres any negative side effects everything seems to work fine just delete the bootanimation.tmp file when you add new animations
installation is the same as before except I have the boot animations going to /sdcard/bootanimation so put them there
might want to nandroid before installing i did but im paranoid about things like that.
also im not responsable for anything that happens if you flash this file everything runs fine on my phone so i think its stable but all mods run some form of minor risk
also not responsible for worn out sdcards or missed calls/sms sue to the constant rebooting of your phone to show off the animation

Are we supposed to rename each bootanimation.zip with a unique name, or keep the filenames "bootanimation.zip" and make individual directories? Renaming each bootanimation.zip and placing them in /sdcard/bootanimation is not working for me.
godsfilth said:
i got it working don't know if theres any negative side effects everything seems to work fine just delete the bootanimation.tmp file when you add new animations
installation is the same as before except I have the boot animations going to /sdcard/bootanimation so put them there
might want to nandroid before installing i did but im paranoid about things like that.
also im not responsable for anything that happens if you flash this file everything runs fine on my phone so i think its stable but all mods run some form of minor risk
also not responsible for worn out sdcards or missed calls/sms sue to the constant rebooting of your phone to show off the animation
Click to expand...
Click to collapse

overground said:
Are we supposed to rename each bootanimation.zip with a unique name, or keep the filenames "bootanimation.zip" and make individual directories? Renaming each bootanimation.zip and placing them in /sdcard/bootanimation is not working for me.
Click to expand...
Click to collapse
have you tried deleting the temp file that the script generates? I have all different kinds of names for my boot animations so i dont think it matters as long as there all in the same directory

godsfilth said:
have you tried deleting the temp file that the script generates? I have all different kinds of names for my boot animations so i dont think it matters as long as there all in the same directory
Click to expand...
Click to collapse
Well, there was no .tmp file created, and I was using the /sdcard/bootanimation version, which did not work for me. Using the original version works fine. Thanks
Edit: Although, I'd rather have them on sd...I'll keep trying.
Edit2: Still no go on the /sdcard option...wonder if using Desire Rom or apps2sd messes it up? Doesn't seem like it should. The /sdcard script looks fine. Hmmm...?

overground said:
Well, there was no .tmp file created, and I was using the /sdcard/bootanimation version, which did not work for me. Using the original version works fine. Thanks
Edit: Although, I'd rather have them on sd...I'll keep trying.
Click to expand...
Click to collapse
what ROM are you using i'm running CM's latest if you are running CM then try pushing the script again following the directions in the first post just use the sdcard script instead also
i have no idea why the script Nighthound posted works and my sdcard one does not. all i did was edit his script to mount the sdcard load from /sdcard/bootanimation and then unmount the sdcard literally added for lines of text and edited the load directory
EDIT:so you're using the desire rom where does the desire ROM keep its init.d if its not /system/etc then you will need to push the file to wherever the desire rom stores it plus i think desire uses a different format for boot animation since it has sound too

godsfilth said:
what ROM are you using i'm running CM's latest if you are running CM then try pushing the script again following the directions in the first post just use the sdcard script instead also
i have no idea why the script Nighthound posted works and my sdcard one does not. all i did was edit his script to mount the sdcard load from /sdcard/bootanimation and then unmount the sdcard literally added for lines of text and edited the load directory
Click to expand...
Click to collapse
I know. It looks fine and there's no reason why it shouldn't be working. Right now I'm on Manup's NexDesire. I've been back and forth like 3x now and OP script is the only one working for me. Oh well, not a big deal. When I switch ROM's, I'll try your's again. Thanks for the ideas.
Edit for your edit: init.d in this rom is also in /system/etc

Sweet! The sdcard script worked like a champ! Thanks for modifying that. Now I can just keep adding all the coolness without getting bored!

godsfilth said:
i got it working don't know if theres any negative side effects everything seems to work fine just delete the bootanimation.tmp file when you add new animations
installation is the same as before except I have the boot animations going to /sdcard/bootanimation so put them there
might want to nandroid before installing i did but im paranoid about things like that.
also im not responsable for anything that happens if you flash this file everything runs fine on my phone so i think its stable but all mods run some form of minor risk
also not responsible for worn out sdcards or missed calls/sms sue to the constant rebooting of your phone to show off the animation
Click to expand...
Click to collapse
Thanks for the help! I've updated the OP with the new version. By the way, you don't have to delete the temp file because it is regenerated every boot.

Are we supposed to delete the one we have in /system/media? I haven't actually seen a random change. I've seen the same one everytime I reboot.

Beast84 said:
Are we supposed to delete the one we have in /system/media? I haven't actually seen a random change. I've seen the same one everytime I reboot.
Click to expand...
Click to collapse
I've only got the random changing to work using the original script with folder /data/local/bootanimation. That is working flawlessly, however.

overground said:
I've only got the random changing to work using the original script with folder /data/local/bootanimation. That is working flawlessly, however.
Click to expand...
Click to collapse
I got a different animation the first time I booted & now I only see one everytime I boot. I have the stock, cyanogen, win7nexus & both QTeknology's white & black animations but all I see is the win7nexus.

Beast84 said:
Are we supposed to delete the one we have in /system/media? I haven't actually seen a random change. I've seen the same one everytime I reboot.
Click to expand...
Click to collapse
Which version of the script are you using (v1.0, godsfilth's version or v1.1)? And where are you putting the animation files?
overground said:
I've only got the random changing to work using the original script with folder /data/local/bootanimation. That is working flawlessly, however.
Click to expand...
Click to collapse
Are you using any custom ROM?

Nighthound said:
Which version of the script are you using (v1.0, godsfilth's version or v1.1)? And where are you putting the animation files?
Click to expand...
Click to collapse
I'm using 1.1 and all my animations are in /sdcard/bootanimation. Is there a difference between godsfilth's & your 1.1?

Beast84 said:
I'm using 1.1 and all my animations are in /sdcard/bootanimation. Is there a difference between godsfilth's & your 1.1?
Click to expand...
Click to collapse
The only difference is I added an error check in 1.1. Other than that the sdcard mount procedure is the same. From your earlier description, you said that the script copied the animation to /data/local once, and then didn't work again after that? Did you chmod the script after copying it into /system/etc/init.d ?

Nighthound said:
Are you using any custom ROM?
Click to expand...
Click to collapse
Yes, as I mentioned earlier in the thread, I'm on Manup's NexDesire 1.2, which may or may not be the culprit. Was suggested earlier that because the Desire ROMs sometimes call a boot sound in addition to bootanimation, this may screw with it. I haven't really looked into it, but this ROM has no boot sound. I don't know if it is because it is
1. removed the .mp3
2. the portion of the script that calls it is commented out
3. both 1 and 2
I hope 2 or 3 is true, because that would be cleaner.
I'll check it out further when I get a chance.
In the meantime I suggest posting both versions of the script, so it can work for everyone. Thanks Nighthound

Nighthound said:
The only difference is I added an error check in 1.1. Other than that the sdcard mount procedure is the same. From your earlier description, you said that the script copied the animation to /data/local once, and then didn't work again after that? Did you chmod the script after copying it into /system/etc/init.d ?
Click to expand...
Click to collapse
I can't get adb to work properly on my laptop so I actually made an update.zip to get the file in system/etc/init.d. Shouldn't that get it working properly without having to chmod anything? If not, would be nice enough to give me the commands to chmod from terminal? I know it can't be too different from the adb commands but I just wanna make sure I do it right

[APP] Droid X Keyboard Port **HOLY CRAP ITS HERE!!1!** [updated 8/13]

After seeing the sweet sweet multi-touch I went looking and found the droid x dump over on android central. Only issue is droid x dump is 2.1 and i just updated to 2.2 frf83. Can anyone repack or resign or do whatever magic needs to be done to get this out to work with froyo?
Its the LatinIME.apk in the app folder.
http://www.4shared.com/file/m8pSCMvI/droidx.html
[UPDATE 7-10]-------------------------------------------------------------------------
Unfortunately Daneshm90 isnt able to work on the Froyo port of this keyboard. If anyone is interested in helping bring this to Froyo, it would be much appreciated, and im sure you'd prob grab a few bucks in donations too.
To make the thread easier to navigate I will be posting all new info on the keyboard here as it is posted throughout the thread. AND REMEMBER ALL GLORY GOES TO DANESHM90, THE ACTUAL DEV DOING THE WORK. THANKS DANESHM90!
DESCRIPTION:
The Droid X Keyboard features full multi-touch. This is different from the multi-touch currently enabled on 3rd party keyboards-the Droid X has the capability to hold down shift and press a letter to make a capital, ie it can do more than one key stoke at once like a physical keyboard. Pretty nice.
LINKS:
2.1 Eclair-based Roms:
only thing not working is auto-captilization,auto-correct errors. Dictionary works, NOW WITH VIBRATE!! Doesnt seem to work on HTC Hero GSM or CDMA...
http://www.mediafire.com/?lumzzhdjnij​
2.2 Froyo-based Roms:
All thats not working on eclair + can't type anywhere it tries to suggest words, like the messaging body. Also voice doesnt work.
http://www.mediafire.com/?rmqzyo0ifzk​
FUTURE FIXES:
• Froyo or Bust
INSTALLATION:
To install this app, you will need a file manager of your choice. Find the apk on your sd card with your file manager and install it. From there go to your system settings-->language and keyboard--> and make sure Multi-Touch Keyboard is checked. Go back to your home screen and find a text field. Long Press and hold until the pop-up menu appears, and select "input method". Choose Multi-touch keyboard. Thats it! To disable simply long press again, select input method and choose a different keyboard. Now you know, and knowing is half the battle
Screenshot of Droid X Keyboard by Andonnguyen. &Amp has been fixed in the apk, but not in this image.
================****UPDATE 8/13/10****
Ok all you multi-touch fanatics...invisiblek over on the incredible forum has ported this to work on a variety of roms, including CM6. Find instructions and DL the files here: http://forum.xda-developers.com/showthread.php?t=753156
If you dont know ADB well, as I dont, you will be able to install this through Root Explorer, the excellent root only file manager. Basically to do this just DL the files, copy them to the appropriate places (LatinIME.apk goes in system/app, libjni_latinime.so goes in system/lib). Be careful as the .so file sometimes DL's as a .txt file, and needs to have both the extension and file name renamed to be correct before installing. It is also a great idea to rename your original LatinIME.apk to something like LatinIME.apk.bak, as well as the lib file, in case anything F's up. As a matter of fact it may even be a good idea to do a Nandroid BU, because you never know what might happen, and its prob been a while hasnt it...
Ok, so you copied them in the right places, now press and try to install your new LatinIME.apk. The first few times I tried to install this, it didnt work. However after remounting my /system as Read Only inside Root Explorer the install worked.
Thanks Invisiblek! Send this guy some donations if you can, we've been waiting for a long time on this one.

Mm, does the keyboard work on a Nexus One that's still running on 2.1, I wonder? Going to give it a try.

Here try this. Its working for me on cyan 5.0.8 on a 32a magic. I just removed the shared uid and resigned with testkeys.
Link

Brilliant, you're a gem. Thank you. Works perfectly.

doesn't work with MCR r18 (FRF72). It installs but force closes once you try to select it.
Will try when MCR r19 (FRF83) hits but I doubt that will work either.

K can u gimme the log ? thnx
Also from ur current build can u gimme ur libjni_latinime.so which can be found under /system/lib/

not the most advanced user here... tell me what to do and I'll do it.

Ok you have adb working right ?
K go start -> cmd -> adb logcat
now leave that window open and try to open swype on ur phone. Then right click the log window click select all, then press enter. Paste in this thread wht u have.
As for the lib its just adb pull /system/lib/libjni_latinime.so <wherever on ur pc>

Cant do that right now... at work. I can when I get home in a few hours.

K cool Np ill try n get vibrate working

Thanks u for great port It work well on Cyanogenmod 5.0.8

smalldroid said:
Thanks u for great port It work well on Cyanogenmod 5.0.8
Click to expand...
Click to collapse
Np. Does vibration work for u ? Doesnt for me Voice to text does though

Vibration doesn't work but I dont need vibration

force closes for me on frf83

force close on FRF72
this is the Log
http://pastebin.com/rHjF6UVn
thanks

Yeah doesn't work on stock frf83-just fc. Any way of fixing?

It seems to be the lib file. K here try this its w/o it forcing it to pull one from ur /system/lib folder
Link

I dunno if this makes a difference or not, but i completely removed the stock keyboard before installing this, i never use the stock keyboard.
These r the steps to do so
adb remount
adb shell rm /system/app/LatinIME.apk
adb shell rm /data/dalvik-cache/*Latin*
adb shell rm /cache/dalvik-cache/*Latin*
adb uninstall com.android.inputmethod.latin

I dunno if this makes a difference or not, but i completely removed the stock keyboard before installing this, i never use the stock keyboard.
These r the steps to do so
adb remount
adb shell rm /system/app/LatinIME.apk
adb shell rm /data/dalvik-cache/*Latin*
adb shell rm /cache/dalvik-cache/*Latin*
adb uninstall com.android.inputmethod.latin

Daneshm90 said:
It seems to be the lib file. K here try this its w/o it forcing it to pull one from ur /system/lib folder
Link
Click to expand...
Click to collapse
Still getting force closes on it. Can't get log since I'm at work.
Note: running froyo, using rodigezstyle's ROM

[HowTo] Odex FRAMEWORK, all Android versions may apply.

Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
This method should work on all Android devices.
------------------------------------------------------------------------------------------------------------
First of all, what is odex? Something you should know about classes.dex.
Odex stands for Optimized dex. I'm not gonna explain a lot because I'm not sure if I'm right. First of all, in typical apk files, when you open it with WinRAR or something like that, you can find a file called "classes.dex"(this type of apk is deodexed). This file is the key. It contains the core codes of the apk. However the other type of apk comes with an *.odex file and doesn't have classes.dex inside the apk file. This is odexed apk. There are 2 types of ROMs here, odexed and deodexed. Odexed ROMs' classes.dex are already out of the apk files, while deodexed ROMs' classes.dex are still in the apks. When Android executes an apk, it has to extract the classes.dex out and execute it. So when you flash an deodexed ROM, the first boot takes a long long time since the Android system needs to extract all the classes.dex into dalvik-cache(it shows "Optimizing apks" on the screen for 4.0 ROMs, shows boot animation on screen for 2.3 or below ROMs). However for the odexed ROMs, because the classes.dex are already out there, the system just grabs them and use them, without wasting time and storage space extracting classes.dex out.
Why odex framework?
It can boost your device a little by odexing your framework. Your phone can run more efficiently. Although it's a complicated process, but trust me, it's worth it.
What is so special about odexing framework files? What's the difference?
Odexing an app is very easy, and I believe everyone knows how to do it. But odexing framework is really annoying. Why? Because apps and more like stand-alone things, they are not a part of system. You delete it, nothing bad happens, your phone still boots, you just get endless FC if you delete the wrong one, or missing status bar, that's all. But framework files you cannot mess around. They are parts of the system. They have to match the system's codes precisely, without any error, even the order of files(keep this in mind, very important). So for every ROM, the framework initialize codes are different(same RUU or other ROM based ROMs count as its base ROM), and you must modify the odexing binary to make it odex for you properly, or you can sit and watch the beautiful bootloop.
What's the relationship between odexing apps and odexing framework?
Simple, but important. If you odexed apps, you cannot touch the framework. Framework always goes in the first place. If you wanna odex both, you must odex framework first. Or... "The Tragedy of App and Framework"...
So what do we have to keep in mind before we start?
Keep your mind clear, prepare a bag of ice in case you feel dizzy with the codes, and MAKE ENOUGH SPACE FOR FRAMEWORK ODEXING. I would prefer you remove a few useless apks in /system/app first to make more room in system partition. Failing odexing may brick your device forever! Nah just kidding it will only cause you to bootloop. No big deal. Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
What tools do you need?
Notepad++ and a magical rar that contains all you need to success.
Let's get started.
------------------------------------------------------------------------------------------------------------
1. Use your file manager to find init.rc at the very root directory of your phone and copy it to SDCard for later code editing, or you simply adb pull it out and skip the coping step. (If you know how to compile boot.img it is even easier, just unpack boot in Android Kitchen, look for line "export BOOTClassPATH". I'm not gonna introduce that method since most people can't. Silly me, didn't I just intoduced that? XD)
2. Connect USB, set mode as disk drive so you can access your SDCard. Copy init.rc into your computer. Open it with notepad, and find where it says "export BOOTClassPATH", create a new file and copy line "export BOOTClassPATH" into the new file. For example:
Code:
export BOOTCLASSPATH/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
3. Open dexopter in the rar you downloaded with Notepad++. Find the lines that show the similar contents to the things after "export BOOTClassPATH". It is Line 21 to Line 35 on my laptop. Edit them according to the things you just copied out of init.rc. For example, if the first file is "X.jar", then you will have to edit the line into "dexopt-wrapper/system/framework/X.jar /system/framework/X.odex". Then repeat until you finish with all the files that are listed in the long list you copied out of init.rc. File order DOES MATTER. Use the bag of ice I told you to prepare eariler to make you sober if you feel dizzy with the codes. The lines may be more or less after you edited them, doesn't matter.
4. Copy "dexopter" and "dexopt-wrapper" into /system/bin and set the correct permissions. Make sure they have enough permission to change your system files. Restart your phone.
5. Go to CMD and lead it to where adb.exe is(included in the rar). Type these in order:
Code:
adb shell
su
cd system/framework
dexopter fr
Then the codes will run crazy in your cmd window... The odex process has begun!
6. If the odex process completed without error, you are half way there! Well it doesn't mean you have to stare at your screen during the process. It's about time we figure it out! The phone will automatically reboot once it's finished. If it doesn't and you are sure all are done, reboot manually.
7. If you can't boot properly, go back and check everything carefully. If you can, then open your file manager and copy the entire framework directory into your SDCard. You can still adb pull and skip the next coping step.
8. Mount SDCard. Go into framework directory on your computer. Open every file that has an odex file with it, delete the classes.dex inside. WinRAR is okay. The files may seem ridiculously small after you delete the classes.dex, but don't worry since classes.dex are already pulled out and turned into odex files.
9. Copy the whole framework folder into the folder where adb is at. Use adb to push all the files back into /system/framework.
Code:
adb root
adb remount
adb push framework /system/framework
adb shell
su
chmod /system/framework xxx (xxx is a permission code, depends on your ROM. They should be the same as the old deodexed framework files. Use Google to find out how to use the permission codes.)
10. After all the files are pushed in, reboot your phone.
11. If it still boots into the system, congratulations! You've successfully odexed your framework! If it doesn't, then go back and read everything carefully. The most common error occurs when you are editing the dexopter code. You will have to redo everything again.
Done! Everything is ready to go!
You can directly grab the files you've odexed and put it in your custom ROM(must be the same base), just don't forget the odex files.
------------------------------------------------------------------------------------------------------------
Okay, hmm, what to say now? Still, I would be glad if you donated me, but if you don't it's okay, just reply and hit thanks .
Oh almost forgot, the magical rar: http://d-h.st/tYi
------------------------------------------------------------------------------------------------------------
Big thanks to Scott, see him in #3. He explained why some files aren't odexed and provided a easier method(but they all get you dizzy )
Big thanks to JSLEnterprises, see him in #4. He provided a newer busybox for Scott's method.

If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2

BreatheHT said:
Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
Click to expand...
Click to collapse
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott

If anyone finds this to be too much work... dont worry... it only unpacks the classes.dex once. It will only need to unpack a dex if original file has changed (changed entries need to propogate). That's why all the consecutive boots are back to a 'normal' span of time.
re-odexing your roms IS recommended if either A) you're anal-retentive/have OCD or B) propogation ("Android is Upgrading...") happens every time you reboot your device (it happens sometimes)
If you're going to use the tool scrosler linked to, replace the busybox binary with the one inside the attatched zip (this is busybox 1.20.1). The one that come with the tool is pretty dated.
:good:
Update: Busybox 1.20.2 has been released (though not compiled for android use yet)

Great stuff guys.

scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
hehe yep I know the adb pull command, I thought about it and I didn't put it in...

theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You confused bro?

Thanks. Even though I won't ever be doing this, it's good to know what's going on.

This is awesome. Thanks so much for this. I wanted to know how to odex and deodex roms.
Sent from my HTC One XL using xda app-developers app

scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yep Android Kitchen can do it.

Hopefully this will help to see more odex ROMs

This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2

superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Most official ROMs are odexed.

BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2

superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Nah carrier doesn't matter.

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions

BreatheHT said:
hehe yep I know the adb pull command, I thought about it and I didn't put it in...
Click to expand...
Click to collapse
Yeah, I like to do it better that way. Dont have to move my hands from the keyboard and mouse. Makes you more efficient :good:
BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
I think all?
superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Carrier is irrelevant. Most people dont know how to work with ODEX files so they go with de-odex. Its mroe challanging but provides a better experience.
techlogik said:
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..
Click to expand...
Click to collapse
No he is asking to go the other way from odex to de-odex.
BreatheHT said:
Yep Android Kitchen can do it.
Click to expand...
Click to collapse
JSLEnterprises said:
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yep, I love that script. I was the one that sent him the mnt point file for the HOX :highfive:
I am going to talk to him about bringing in "official" support for the Asus TF300T. I got the boot.img fiugred out this morning! Woot. **** is about to get real with the Asus!

superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
its a good final touch when cook done with smali tweaks.
another benefit is sorta kang-protection

Modyfying existing ROM

Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!

michalurban said:
Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!
Click to expand...
Click to collapse
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up

anerik said:
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up
Click to expand...
Click to collapse
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).

michalurban said:
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).
Click to expand...
Click to collapse
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way

anerik said:
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way
Click to expand...
Click to collapse
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?

michalurban said:
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?
Click to expand...
Click to collapse
Put faux's boot.img on the rom first, then on updater script go to the line that refers to extracting boot.img (should be like the last one) and replace that with the command on faux's updater script. That means it will extract it in that directory, nothing else. Be sure to copy modules aswell and set the perms

Q&A threads should be created in the Q&A forum... not the Development forum.
Thread moved.

One more question - is there a special way how to pack the ZIP file? Cause I unpacked a ROM, added some apks, packed it but it didnt work (no error, just ended at "opening rom" or what the CWM message is) ... but when I modified existing ZIP it went fine ...