What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[New!!!][ROM] D1-MIUI-1.1.7.0

is there a way to get rid of the new MIUI search? it doesn't work, and I'd rather use the Google search for default search button.

Sent from my Droid using DroidForums App

I went to the market and installed Google Search and that did it for me.

I've done that already and can't seem to make Google search the default action when you push the search button. can I?

Sent from my Droid using DroidForums App

Weird, I was in the middle of typing that it worked for me without doing anything special, but I decided to go ahead and check. Sure enough the miui search is back, but yesterday, just after re-installing Google Search from the market, I pressed the search button and got Google. Today it is back to miui. Shoot!
 
I can't get swype to work properly, I completely uninstalled it then downloaded the installer from the e-mail, and when it installed it worked but once I rebooted the phone it doesn't work anymore. It shows the path that you are tracing, but then it just gives you an error beep when you finish.
 
I can't get swype to work properly, I completely uninstalled it then downloaded the installer from the e-mail, and when it installed it worked but once I rebooted the phone it doesn't work anymore. It shows the path that you are tracing, but then it just gives you an error beep when you finish.

I've had that happen with swype before and it was easy to fix.

Their help page says that this happens because swype thinks that it is not authorized for your phone. It says that you should be able to uninstall everything and reinstall from scratch then re-activate your phone and it should start working.
 
You need to delete all old swype and swype installer from your SD card then start from the email.

Sent from my Droid using Tapatalk
 
The launcher is fcing pretty frequently now. I will be on the browser and not even doing anything launcher related and it will fc.

I did a acatlog and here is the lines when it closed. Let me know if you want the whole log
01-12 11:56:36.140 E/AndroidRuntime( 5416): at dalvik.system.NativeStart.run(Native Method)
01-12 11:56:36.155 W/ActivityManager( 1113): Force finishing activity com.android.launcher/com.android.launcher2.Launcher
01-12 11:56:37.093 D/dalvikvm( 3876): GC_FOR_MALLOC freed 11609 objects / 1005960 bytes in 38ms
01-12 11:56:40.046 I/Process ( 5416): Sending signal. PID: 5416 SIG: 9
01-12 11:56:40.194 I/ActivityManager( 1113): Process com.android.launcher (pid 5416) has died.
01-12 11:56:40.194 I/ActivityManager( 1113): Low Memory: No more background processes.
01-12 11:56:40.288 D/dalvikvm( 6399): GC_FOR_MALLOC freed 15237 objects / 1091120 bytes in 58ms
01-12 11:56:41.657 W/KeyCharacterMap( 6399): Can't open keycharmap file
01-12 11:56:41.663 W/KeyCharacterMap( 6399): Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65538.devname='qtouch-touchscreen'
01-12 11:56:41.663 W/KeyCharacterMap( 6399): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
 
Last edited:
contact app looks fine. everything synced once and looks fine, no duplicates. When you go to editing mode>menu>add>shortcuts>direct dial there are some contacts that have multiple enteries. And I don't mean one entry for each of their numbers (cell, home work,etc), I mean multiple as in 7 entries for the very same number. This was not there in builds 12.31 and 12.24.

I think it happened when I made my Yahoo Mail App from market sync contacts. Strange thing is that phone or Google contacts (on PC) do not show these multiples. Oh ya, some of these multiples can't pull the pics either, some do.
 
The launcher is fcing pretty frequently now. I will be on the browser and not even doing anything launcher related and it will fc.

I did a acatlog and here is the lines when it closed. Let me know if you want the whole log
01-12 11:56:36.140 E/AndroidRuntime( 5416): at dalvik.system.NativeStart.run(Native Method)
01-12 11:56:36.155 W/ActivityManager( 1113): Force finishing activity com.android.launcher/com.android.launcher2.Launcher
01-12 11:56:37.093 D/dalvikvm( 3876): GC_FOR_MALLOC freed 11609 objects / 1005960 bytes in 38ms
01-12 11:56:40.046 I/Process ( 5416): Sending signal. PID: 5416 SIG: 9
01-12 11:56:40.194 I/ActivityManager( 1113): Process com.android.launcher (pid 5416) has died.
01-12 11:56:40.194 I/ActivityManager( 1113): Low Memory: No more background processes.
01-12 11:56:40.288 D/dalvikvm( 6399): GC_FOR_MALLOC freed 15237 objects / 1091120 bytes in 58ms
01-12 11:56:41.657 W/KeyCharacterMap( 6399): Can't open keycharmap file
01-12 11:56:41.663 W/KeyCharacterMap( 6399): Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65538.devname='qtouch-touchscreen'
01-12 11:56:41.663 W/KeyCharacterMap( 6399): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

This is why i switched away for now. Too many Launcher FC's when not even doing anything. Previous version never did this. Will be watching to see if there is any resolution to this. May wait for next update to try again. 12-3 was rock solid for me - the others since then have been iffy. (for me).
 
Anybody else notice that not all widgets are accessible. I installed google search but I can't access the widget. Same is true for Mint and i'm sure some others.
 
The launcher is fcing pretty frequently now. I will be on the browser and not even doing anything launcher related and it will fc.

I did a acatlog and here is the lines when it closed. Let me know if you want the whole log
01-12 11:56:36.140 E/AndroidRuntime( 5416): at dalvik.system.NativeStart.run(Native Method)
01-12 11:56:36.155 W/ActivityManager( 1113): Force finishing activity com.android.launcher/com.android.launcher2.Launcher
01-12 11:56:37.093 D/dalvikvm( 3876): GC_FOR_MALLOC freed 11609 objects / 1005960 bytes in 38ms
01-12 11:56:40.046 I/Process ( 5416): Sending signal. PID: 5416 SIG: 9
01-12 11:56:40.194 I/ActivityManager( 1113): Process com.android.launcher (pid 5416) has died.
01-12 11:56:40.194 I/ActivityManager( 1113): Low Memory: No more background processes.
01-12 11:56:40.288 D/dalvikvm( 6399): GC_FOR_MALLOC freed 15237 objects / 1091120 bytes in 58ms
01-12 11:56:41.657 W/KeyCharacterMap( 6399): Can't open keycharmap file
01-12 11:56:41.663 W/KeyCharacterMap( 6399): Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65538.devname='qtouch-touchscreen'
01-12 11:56:41.663 W/KeyCharacterMap( 6399): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

This is why i switched away for now. Too many Launcher FC's when not even doing anything. Previous version never did this. Will be watching to see if there is any resolution to this. May wait for next update to try again. 12-3 was rock solid for me - the others since then have been iffy. (for me).

This is theme related. Had it happen to me also. Put stock theme back on and problem went away. Try a diff. theme and see if that helps. I'm gonna try some older themes that always worked and see if the problem occurs again. I'll report back later.
See jamezelles post from last night.
 
Last edited:
Unfortunately, I'm getting Launcher FC w/ every theme I try. As long as I keep Default system theme, I can change everything else w/o issue.
Stick w/ the stock system theme and you should be good.
 
Unfortunately, I'm getting Launcher FC w/ every theme I try. As long as I keep Default system theme, I can change everything else w/o issue.
Stick w/ the stock system theme and you should be good.

I get no FCs with any themes. I downloaded around 45 themes from a thread a while back and have tried a few and feel this is the most stable build yet. It has issues but no FCs. One thing I did differently in this build was not to restore anything from the backups, titanium or MIUI.


can't remember where I got those themes, it was a zip file containing a bunch. If you know where it is please mention it here.
 
IF there is a problem with themes, does it have anything to do with the new theme format? Either:
new format = bad
or
old format = bad on new releases
 
Back
Top