After SR ShowSim changes from 0 to 1 everytime- why? Is it possible to improve it?
Hey guys,
Just got myself a Q9H and even though I know XDA supports HTC mostly, I hope I can find a solution here. Navigation on the Q9H is terrible. The hold delay for when you press the Dpad to navigate up or down is simply slow. How can I speed this up?
I've checked the registry and find these keys I think could help this be improved. Sadly I have no knowledge if I'm in the right place and what the DWORD data should be for this to improve:
HKCU\ControlPanel\Keybd | DWord: APP5_LongPress = 0xD0 (208)
HKCU\ControlPanel\Keybd | DWord: InitialDelay = 0x3E8 (1000)
HKCU\ControlPanel\Keybd | DWord: RepeatRate = 0xA (10)
HKCU\ControlPanel\Keybd | DWord: RockerInitialDelay = 0x1F4 (500)
HKCU\ControlPanel\Keybd | DWord: RockerMaxRate = 0x19 (25)
HKCU\ControlPanel\Keybd | DWord: RockerMinRate = 0x5 (5)
HKCU\ControlPanel\Keybd | DWord: RockerMode = 0x1 (1)
HKCU\ControlPanel\Keybd | DWord: RockerThreshold = 0x2 (2)
HKCU\ControlPanel\Keybd | DWord: TimeToMaxRate = 0x9C4 (2500)
Could anybody help?
see this
http://www.everythingq.com/forum/moto-q-hacks/moto-q-benchmarks-speed-hack-8703.html
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
Hi!
I just got my MXQ Pro S905 android tv box and right out the box, the remote control didn't work. I googled and visited different website and I found a remote.conf file to replace the current one on the box, so I did. Now the remote partially works. I can use the arrows, volume up down, etc... The problem is I still can't get the power button or the mouse to work Any expert help on how to get it to work please?
Here is the new remote.conf file that partially works ( power button and mouse don't work):
#************************************************* ************************************************** ******
#this file is configuration for each factory remote device
# work_mode 0 :software mode 1 :hardware mode
# repeat_enable 0 :disable repeat 1 :enable repeat
#
# factory_code each device has it's unique factory code.
# pattern:custom_code(16bit)+index_code(16bit)
# examble: 0xff000001 = 0xff00(custom cod) 0001 (index)
#
# release_delay unit:ms.release will report from kernel to user layer after this period of time
# from press or repeat triggered.
#
# debug_enable 0 :debug disable 1 :debug disable
#
# SW MODE:
# bit_count how many bits in each frame
# tw_leader_act time window for leader active
# tw_bit0 time window for bit0 time.
# tw_bit1 time window for bit1 time
# tw_repeat_leader time window for repeat leader
# REG
# reg_base_gen set value for PREG_IR_DEC_BASE_GEN
# reg_control set value for PREG_IR_DEC_CONTROL
# reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE
# reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE
# reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
# reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME
#************************************************* ************************************************** **********
#amlogic NEC remote
factory_code = 0x7f800001
work_mode = 0
repeat_enable = 1
repeat_delay = 40
repeat_peroid = 39
release_delay = 121
debug_enable = 1
fn_key_scancode = 0x15
left_key_scancode = 0x1c
right_key_scancode = 0x48
up_key_scancode = 0x44
down_key_scancode = 0x1d
ok_key_scancode = 0x5c
pageup_key_scancode = 0x04
pagedown_key_scancode = 0x1b
mouse_begin
0 0x1c
1 0x48
2 0x44
3 0x1d
mouse_end
key_begin
0x4d 113
0x56 114
0x4e 115
0x25 105
0x26 103
0x27 106
0x28 108
0x0d 97
0x1b 158
0x53 102
0x51 704
0x49 139
0x52 388
0x31 2
0x32 3
0x33 4
0x34 5
0x35 6
0x36 7
0x37 8
0x38 9
0x39 10
0x30 11
0x58 389
0x44 14
0xbd 122
0xbb 123
0x09 393
0x11 390
0x54 391
0x4f 392
key_end
repeat_key_begin
0x4d 113
0x56 114
0x4e 115
0x25 105
0x26 103
0x27 106
0x28 108
0x0d 28
0x1b 158
0x53 102
0x51 704
0x49 139
0x52 388
0x31 2
0x32 3
0x33 4
0x34 5
0x35 6
0x36 7
0x37 8
0x38 9
0x39 10
0x30 11
0x58 389
0x44 111
0xbd 122
0xbb 123
0x09 164
0x11 390
0x54 391
0x4f 392
repeat_key_end
try a reflash
guide here
http://forum.xda-developers.com/showthread.php?t=3400814
Sent from my SM-G920F using XDA-Developers mobile app