Search results

rebooting after removing the app is a necesary step.

swype is in a private, closed beta, and for using it legaly (as i do, i just modify them to remove the unnecesary languages, and then remove the need to be licensed, since for the new installer to LICENSE swype, it must be DISABLED, and miui settings ui does not have the option to DISABLE a...

really ? i knew about the theme manager problem, not this. i reverted to the old apk and .so, and i still have the problem, and a friend with 12.3, pack 1b, and the same gigner kb has the ss feature working.

broken, not brocken :P i still haven't figured how i broke it, but since i also installed the gingerbread kb, and that broke the theme system, and going back to a nandroid from before the KB, just to make sure. (poor apps that had been updated :P ) EDIT: since there is a new version tomorow...

it can be done, i guess, but you need to add stuff, lots of stuff, to the framework, and you would need to update that on each release.

its pretty old tho :P IF its ok to post this stuff (swype devs would not agree :P) i have modified 2.10 and 2.15 (this one only for 800x480 devices), i can post those.

if you moved apps (one by one) to the SD, they are in the .adroid_secure folder in the SD card, still in the FAT32 partition, and you have only one partition there (the rom can't create EXT partitions for you). you must be using froyo apps2sd method.

from a terminal app su a2sd reinstall (only if you did not have the ext partition when you installed miui, if you had, you already have a2sd working) a2sd zipaling a2sd cachesd (i think that was the command to move dalvik to the ext partition)

hi people im running the latest miui (12.3) with pack 1d I don't know what i did, but the screenshot feature is not working, SS sound gets played, file gets created, but its an empty file, no image inside. i tried wiping dalvik, running a scandisk on the sdcard, fixin permisions, and i...

i can't provide screenshots cause somehow i broke the ss system from MIUI, i just get black files :( but at least on better terminal emulator (pro ?, dunno, the paid one), i can use a2sd with no problems.

froyos source was not released to AOSP until the nexus one got the "final" 2.2 build, if i remeber correctly, so it might take a week, or a month, who knows :( (for a complete gingerbread based miui or other custom rom to start DEVELOPING)

if you want to accelerate the process, use a switch you want among the first ones "a lot" (the bluetooth and wifi ones are troublesome, you need to wait for bt/wifi to actually turn on), and then lock the phone. when you go back, it will be rearanged XD rinse and repeat.

all the scripts that you have in darcktremors a2sd, are present in miui (its actually just DT a2sd preinstalled, maybe with some tweaks) you have: a2sd reinstall a2sd check a2sd cachesd a2sd cachesdreset a2sd zipalign and all the rest, that i don't remember.

what scripts ? the a2sd scritps are preinstalled on miui. are you using froyos apps2sd? if so, i would either try to NOT do that, or restore everything, and then wait/reboot and wait.

i never found any sense rom faster than other roms, but maybe the build you were using had something special in its build.prop ?

keep rebooting, it will be sorted doing that (also, rebooting will make it happen again at some point :P ) ps: same goes for sound input (throigh any method) ps2: i know, this sucks, theres no way arround it for now EDIT: Full reboots, no hot reboots, or even turing the phone complety off...

as far as i know, manually pain in the as* for settings like haptic feedback that are pretty "deep" in the settings.

get it from the full rom zip maybe ?

the counter appears when you are near the limit, and it tells you how many messages it will be if you go past the limit to.

what bug ? if you are talking about the bug that makes sound (in general) ultra low after a reboot, just keep rebooting untill sound works :P