After SR ShowSim changes from 0 to 1 everytime- why? Is it possible to improve it?
Related
now I have no quick keys from digits, but only letters. I do not know like one can move this again. Hangs it maybe together with any other installed program?
some any ideas?
In the Registry, goto:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shell
*press left softkey (values)
Change the DWORD value as follows:
HasKeyBoard = 0 (for numbers)
HasKeyBoard = 1 (for letters)
*a soft reset is not needed. but, in case it doesn't change anything automatically, a soft reset wouldn't hurt.
thanks to greatbal for this tip
Just delete all Sony-Ericsson phones from BT devices list.
Hello,
thank you very much! Now I have the HotKeys(Digits) again
Is it a bug with Sony-Ericson?
This is the bug of WinMobile, maybe.
Hi, I'm new and I have a problem to filter my sim contacts. I have just tried to edit the registry changing the value 1 to 0 in the string HKEY_CURRENT_USER / Control Panel / Phone but nothing.......after the soft reset the contacts are always visible.
Someone has the solution?
Thanks and have a nice day
Hi,
I've just find where it is...
Open your registry editor and go to :
HKEY_CURRENT_USER / Control Panel / Phone
Open the valueName ShowSim
Replace the 1 by 0
Press the top button for turn off your phone for approximativelly 1 min
Make a soft reset and it's done, Your SIM contact will disapeared...
Best regards
cadoudal56 said:
Hi,
I've just find where it is...
Open your registry editor and go to :
HKEY_CURRENT_USER / Control Panel / Phone
Open the valueName ShowSim
Replace the 1 by 0
Press the top button for turn off your phone for approximativelly 1 min
Make a soft reset and it's done, Your SIM contact will disapeared...
Best regards
Click to expand...
Click to collapse
Did the same, however, if you do not soft reset then sim contacts disappear after the above tweak, but after soft reset, they re-appear and value of ShowSim turn to 1 again .... .
How to keep this change permenant even after soft resets as other registry tweaks don't change after resets but this conatcs thing does
dr_s said:
Did the same, however, if you do not soft reset then sim contacts disappear after the above tweak, but after soft reset, they re-appear and value of ShowSim turn to 1 again .... .
How to keep this change permenant even after soft resets as other registry tweaks don't change after resets but this conatcs thing does
Click to expand...
Click to collapse
Yes, it's true.....also I have tried to rename like "ShowSimold", to copy and change the value in 0 but nothing, after soft reset the value returns to 1 again.
In this post http://forum.xda-developers.com/showthread.php?t=299848 there's a solution for WM6 but I do not know if it is ok for our Touch Cruise.
hey guys is there any application which can turn on the pda by pressing and hardware buttons .? my pda doesnot have that options in settings.
Haad said:
hey guys is there any application which can turn on the pda by pressing and hardware buttons .? my pda doesnot have that options in settings.
Click to expand...
Click to collapse
It would help a lot to know what device you have
Normally on my Universal I just press the on/off hardware button and voila
go to hkey_current_user/controlPanel/keybd/
change DefaultKeyLock = 0
now u can turn on pdaPhone with any hardware key!
netnerd said:
go to hkey_current_user/controlPanel/keybd/
change DefaultKeyLock = 0
now u can turn on pdaPhone with any hardware key!
Click to expand...
Click to collapse
there is no default keylock in keybd folder.
there are default, initial delay and repeat rate.
the device is a not htc made, imate jaq3.
try adding DWORD DefaultKeyLock = 0
or get new phone! haha
lol ive tried adding dword defaultkeylock 0.. but nothing.. i am just askin is there an application..?? can this option be extracted from another rommaybe wizards? or prophets.?
The problem hangs boot! Help!
Install android 2.2 for instructions.
Androida stitch boot and reboot the phone vibrates 2 times, there is a white screen with white letters and black penguin after 1-2 seconds stops and load weight. Tried everything possible nbh, who collected himself in atools. In general the white screen with white penguin only works on kernel 2.6.32 with the following parameters polaris-240x320-Froyo-1-2.6.32.
SCREEN: hxtp://i56.tinypic.com/1y3ebt.jpg (hxtp ->http)
Black screen with the penguin got the normal parameters of polaris-240x320-Froyo-3-2.6.32 but the download just hangs like a white screen. At the core of 2.6.25 for all pereprobovanyh me Parameter only color bars. What's the problem? Who knows how to solve it?
Decided to hold a small exeperimental. I had an old build android-1.5-2009-07-09, which run in the past from Presov to small exeperimental. I had an old build android-1.5-2009-07-09, which run in the past out of Haret normal, with a black boot. This assembly contains:
1) with parameters default.tht
(# Alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# Ppp.username - The username used to connect to the network when dialing
# Ppp.password - The password used to connect to the network when dialing
# Ppp.apn - Set apn of your provider
# Ppp.nostart - Set ppp.nostart = 1 to disable starting the ppp connection on boot
# Msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# Pm.sleep_mode - The mode used when the phone is off
# 0 = Power Collapse Suspend, 1 = Power Collapse, 2 = Apps Sleep,
# 3 = Slow Clock and Wait for Interrupt 4 = Wait for Interrupt
# Default is 1, use one for best power savings
# Board-htcpolaris.panel_type - Panel type used to power the panel off and on
# 0 = Don't power off the panel (Default)
# 1 2 = Sony = Topoly 3 = Topoly (probably just the same as 2)
# Lcd.density - Defaults to 160, 128, shows more on screen
#
set cmdline "board-htcpolaris.panel_type = 0 ppp.apn = wxw.vodafone.net.nz ppp.username = none ppp.password = none pm.sleep_mode = 1 mddi.width = 324 mddi.height = 432 no_console_suspend board-htcpolaris -battery.battery_capacity = 1350 mddi_client_vogue.vsync = 0 "
bottles)
2) haret.ehe,
3) initrd.gz,
4) resources.zip,
5) system.img,
6) zImage
Try to start the assembly with diabetes. In the beginning is all fine, black boot, but then hangs up and says: Varning ---
sisten.img not found on the CD.
It's weird, because sisten.img lies on CD.
Poshamaniv to build its atools Fail default with the following parameters:
set RAMSIZE 0x07300000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.lzma
set cmdline "no_console_suspend board-htcpolaris-battery.battery_capacity = 1350 ppp.nostart = 0 hw3d.version = 1 mddi.width = 324 mddi.height = 432 clock-7x00.mddi = 0xa51 board-htcpolaris.panel_type = a board-htcpolaris . no_boot_vibration = 1 mddi_client_vogue.vsync = 0 sys_partition = / sdcard / andboot / system.img data_partition = / sdcard / andboot / data.img fstype = 2 "
boot
Try to run the assembly Froyo [2.2.2] My Modified Fresh Froyo Release 20-2-2011 with these parameters is out of Haret. The loader is still a white background. That's what vydalood Haret. This assembly contains: hxtp://i53.tinypic.com/20z9y8k.jpg (hxtp ->http)
Those who have any ideas? Why download the old version, so good with black boot and Froyo not?
I climbed a lot of forums and for some reason or where there is no answer to this question, although people with the same problem there. I have a broken display and I replaced it with a new one, after that there was such key problems.
On one of the branches of the forum says that they say it is because the display problem and needed origenalny. But after analyzing all available information, I think that probably in problemma HARD-SPL 2.20Olix!!! This SPL does not support the display non-origenalnogo.
I think that this key problems to be solved, because sooner or later and your display may break mashines and I think you do not want to buy origenalny display for $ 50-100 for this old devaysa.
By this I beg you, help me to find someone who could create a new HARD-SPL for HTC Polaris. Maybe someone knows and understands the programming and be able to make himself SPL. Please respond to all!
Hi
So you want to emulate the native android shutdown sequence. Broken power button? Car or fixed Nexus 7 installation? TV Stick? Here is the solution! (I advise you not to use one of the many shutdown apps because they shutdown without unmounting filesystem etc. and thus can damage your filesystem in the long run).
This should work on ANY Android device!
You can do it directly on your device, no adb needed. BUT: You have to be rooted!
How to:
1. Install Bash X from playstore (I'm not affiliated with them)
2. Start it and choose #root shell
3. Type: getevent -c 3
4. Push power button and release it (short, without the boot dialog)
5. Now you see something like this:
# getevent -c 3
add device 1: /dev/input/event0
name: "pmic8xxx_pwrkey"
add device 2: /dev/input/event1
name: "gk-keypad-8064"
add device 3: /dev/input/event4
name: "hs_detect"
add device 4: /dev/input/event3
name: "suspend_autotest_pwrkey"
could not get driver version for /dev/input/mice, Not a typewriter
add device 5: /dev/input/event2
name: "touch_mxt1188S"
/dev/input/event0: 0001 0074 00000001
/dev/input/event0: 0000 0000 00000000
/dev/input/event0: 0001 0074 00000000
#
add device output shows you the event numbers off your input devices. On my LG Pad the power key is assigned to /dev/input/event0. On your device it will be a other eventX number. On my Nexus 7 it is event2 (gpio).
Now we convert the hex strings of the events in dec (google a online converter). The last 3 lines then look like this:
/dev/input/event0: 1 116 1
/dev/input/event0: 0 0 0
/dev/input/event0: 1 116 0
1 116 1 means power key down
1 116 0 means power key release
6. Install Tasker. Set up a new profile with the profile you want to be the trigger for your action (shutdown). Under tasks choose script, start shell and paste our new script:
/dev/input/event0: 1 116 1;
/dev/input/event0: 0 0 0;
sleep 1;
/dev/input/event0: 1 116 0;
Now we need only some dpad keys for going down and right in the menu:
input keyevent 20;
input keyevent 66;
input keyevent 22;
input keyevent 66;
(Where 20 is down, 22 is right and 66 is enter. This works on stock and CM10)
The Tasker action finally looks like this:
/dev/input/event0: 1 116 1;
/dev/input/event0: 0 0 0;
/dev/input/event0: 1 116 0;
input keyevent 20;
input keyevent 66;
input keyevent 22;
input keyevent 66;
exit;
Don't forget to check "use root" in your action. Test it out!
Cool it is
I also thank the many people working on this question on other places.
edit: if you experience no proper shutdown (have to press 15sec power button for boot), its because tasker hangs on shutdown. Export a app from tasker and start it with automateit. Weird but it works
Olivier