(ANDROID) touch screen not working - Tilt, TyTN II, MDA Vario III Android Development

i have been trying every and any build of android i can find for my kaiser but i have yet to find any build or any of the latest files that will allow my touch screen to work. when i go to haret it boots up fine then it take me to the main startup up android screen where it asks you to touch the android and thats as far as i can get because my touch screen isnt responsive in android but work fine in WM i am funning Styles Black rom and yes there is nothing else on the sd card and android files are on the root of the sd ......someone please help

with all these people running android i figured i could get a little help??

First things First!!!
Wich version of Android are you using ?

i have tried the pre made android builds and i have tried make my own by the book no watter what build or what i change i can not get touch screen working. i have even tried changing roms and radios nothing the actually hardware keys work just no touch

Will you kindly post the content of the default.txt file please ?

daedric said:
Will you kindly post the content of the default.txt file please ?
Click to expand...
Click to collapse
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
#set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
#set initrd "initrd.gz"
set initrd "\Storage Card\initrd.gz"
#set initrd "\Storage Card\initrd-console.gz"
#set initrd "\Storage Card\android.bin"
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# 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 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
#
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop ppp.nostart=0 board-htckaiser.panel_type=1 ppp.apn=wap.cingular [email protected] ppp.password=CINGULAR1 pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=1"
boot

daedric said:
Will you kindly post the content of the default.txt file please ?
Click to expand...
Click to collapse
this is from the ion premade build running on tpc's new elite rom with a tmobile sim????? any suggestions

what radio version are you running? 1.7x i believe is whats recommended.

Try this one:
set RAMSIZE 0x08000000
set MTYPE 1667
set KERNEL zImage
set initrd initrd.gz
set cmdline "ppp.username= ppp.password= mddi.width=320 mddi.height=428 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htckaiser.panel_type=1 no_console_suspend lcd.density=128"
boot

jmhalder said:
what radio version are you running? 1.7x i believe is whats recommended.
Click to expand...
Click to collapse
i just upgraded radios to make sure 1.71.xx
no differrence still no touch active
trying txt above now

did you try using the default txt that daedric posted

jamezelle said:
did you try using the default txt that daedric posted
Click to expand...
Click to collapse
yeah i just it and it didnt even boot in to linux at all????
im lost it seems im the only person having these problems
and my radio is 1.71.09.01

jamezelle said:
did you try using the default txt that daedric posted
Click to expand...
Click to collapse
i went through and deleted everything off my SD card and formated it in FAT32 (it was previously FAT) and then tried all the files again to no avail??? any other suggestions

MotoHo said:
i went through and deleted everything off my SD card and formated it in FAT32 (it was previously FAT) and then tried all the files again to no avail??? any other suggestions
Click to expand...
Click to collapse
sorry xda i cant let this die im not a noob and this is really iretating it doesnt make sense i have done everything by the book and still nothing?>

help!! please

the Mtype for kaiser seems to be 1553... your first default.txt is correct
for your screen, you could calibrate it; press camera button and touch upper right and after down left. release camera button... your screen is calibrate

okay i will try and let you know

i tried the screen calibration and nothing....touch screen does not register anything. let me make sure that i am doing this right> after andoid boots up completely and it asks you to touch the android you hold the camera button and touch the top right then touch the bottom right then release the camera button? if so that did NOTHING whatsoever

MotoHo said:
i tried the screen calibration and nothing....touch screen does not register anything. let me make sure that i am doing this right> after andoid boots up completely and it asks you to touch the android you hold the camera button and touch the top right then touch the bottom right then release the camera button? if so that did NOTHING whatsoever
Click to expand...
Click to collapse
It's good... Working for me on KAIS130, your problem doesn't be here.
There is "pointer location" in "dev tools" ... but without touchscreen, how to go into
my "default.txt":
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd "initrd.gz"
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop board-htckaiser.panel_type=2 ppp.apn=orange ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=320 mddi.height=480 lcd.density=160 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=0"
boot

i tired the default txt you have and nothing still no touch i have been doing some reading and there are other guys using samsung that have been having similiar issues .. why do i have to have the only retarded att tilt on xda?

Related

Space Key not appear in Full Qwerty Keyboard

Hi all.
Suddenly, the "Space Key" does not appear in Full Qwerty Keyboard.
Now ".com" & "/" appear instead of "Space Key".
(plz see the attached file)
I want to change from ".com" & "/" to "Space Key",, how ever i don't know the way.
Could u give the solution?
i had exact same problem. apparently you have to do a registry change to fix it. HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
Your variable might not be 1 but when my screen was as yours it was a 2. Laater it switched on its own to a 9 so dont lose this registry change because your probably going to have to do it again. I noticed when i added new contact or something to that effect it changed the variable
Thank you very much for your solution!
My "CurrentET9Style" is 6.
After revise from 6 to 0, Back to normal keyboard.
Thank you !!!
mjcole2003 said:
i had exact same problem. apparently you have to do a registry change to fix it. HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
Your variable might not be 1 but when my screen was as yours it was a 2. Laater it switched on its own to a 9 so dont lose this registry change because your probably going to have to do it again. I noticed when i added new contact or something to that effect it changed the variable
Click to expand...
Click to collapse
Did you install the tweak cab from ppgeeks? if so, that is your issue. It was in the 1st post
thanks ,i think i get it.
supdawg said:
Did you install the tweak cab from ppgeeks? if so, that is your issue. It was in the 1st post
Click to expand...
Click to collapse
who's first post? I did install the tweak cab from ppcgeeks and would like to read that 1st post. If i uninstall the tweak will it fix the reacurring problem or do i have to hard reset? Thanks
when i changed to "autocomplete" I had the same problem with the space key being gone until i put the registry back the way it was...Tj
Keep CurrentET9Style = 0 ??
Changed HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
This works temporarily, but when I click on the time in a calendar entry, it switches to numbers, and does not switch back unless I re-edit the registry. Is there any way to keep the setting from changing at all? I want it to stay at CurrentET9Style = 0.
Anybody?
Hi everyone. Okay, first let me just say that the "FixStuckTP2Keyboard.cab" is fine and it does work. But it reverts your keyboard back to the "eT9" and you probably did a registry hack to change it from that in the first place (changed it to "COMP") am I right? Not to knock that cab, like I said it works just fine but I did NOT want to "install" a cab file everytime this happened (after it would change it back to "eT9" I would have to go back into the registry and change it to "COMP" again.)
Let me tell you HOW this is happening in the first place, it has something to do with Opera. You can test this very easily. First get your keyboard working properly, then open Opera. Type something in the address bar or just tap the address bar and BAM! Your keyboard is stuck in that mode. Now I don't know why this happens, that mode is getting stuck in memory for some strange reason and it will NOT let go.
I'm assuming this is ONLY happening to those of us who have used the registry (or a program or cab) to change the keyboard to "COMP" instead of "eT9" since changing it back to "eT9" solves the problem.
There are three solutions:
1.) ONLY use the slide-out keyboard when using Opera.
2.) Use the FixStuckTP2Keyboard.cab
3.) Use the MortScripts I created.
Use "KB-OFF (eT9).mscr" to force the "eT9" info into the registry. Then use "KB-ON (COMP).mscr" to enter the "COMP" info back into the registry, then do a soft reset.
You can rename these files if you like.
Yeah I know it sucks to have to do a reset just to get the use of your spacebar back just because you used the virtual keyboard when using Opera but hey, what are you gonna do?
UPDATE: Just noticed that "sometimes" my scripts don't work if you click on them one after another (again for some strange reason). If this happens to you just click on "KB-OFF" soft reboot then click on KB-ON" & reboot. Weird I know.

tmobile Touch pro2 service problem

hey everyone, i ran the xdandroid and everthing worked except it says no service and i tried the apn and search for network but nothing happened. Also how can i get my music to work or is that something that doesnt work
i10ve2pwnu said:
hey everyone, i ran the xdandroid and everthing worked except it says no service and i tried the apn and search for network but nothing happened. Also how can i get my music to work or is that something that doesnt work
Click to expand...
Click to collapse
try doing it over wifi I doubt you will get it to work without a data plan.
Get that Startup Right!
Make sure you're startup.txt is correct. Here's mine
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=-1,-2,3 htc_battery_smem.fake=1 physkeyboard=rhod210"
boot
My guess is you're forcing CDMA in the cmdline and you've got a GSM phone.
Delete this "force_cdma=1"
Try that and let me know.

Smith's simple android boot script

Ok, so there are a few things I've ran into when it comes to running android.
1.) If you have WinMo overclocked, Android will not boot.
2.) If you have WinMo handling your backlight, then sometimes the backlight will always be turned on, even if you "power off" your phone.
3.) Lastly, after running android, my WinMo time gets messed up, very very messed up. (Still coming up with a solution for this)
So, In order to remedy all of the above problems, I've created a simple android startup script, complemented by a WinMo startup script.
Well, here they are, simple, but effective!
Code:
#Android Boot Script
#Sets proper WinMo settings for booting Android
#################################
If(Question("Boot Android?","Droid", "OkCancel")=CANCEL)
Exit
Else{
RegWriteDWord ("HKCU", "ControlPanel\BackLight", "LightDetectOn", "0")
Copy("\Storage Card\andboot\backlight.mscr" , "\Windows\Startup\backlight.mscr" , TRUE)
Run("\Program Files\OverClockTool\OCT_Stop.exe")
WaitForActive("OCT: message" , 5)
SendOk
Run("\Storage Card\andboot\haret.exe")}
endif
As seen above, in line 2 of the actual code, that script mentions "backlight.mscr" so here is that as well:
Code:
#WinMo settings restore
#Simply sets autobacklight back on.
#################################
RegWriteDword("HKCU", "ControlPanel\Backlight", "LightDetectOn", "1")
Delete("\Windows\Startup\backlight.mscr")
Again, simple, but effective.
I would love to see what others would like to add to this!
Regards
Smith

[Q] Android 2.3 on tilt (Kaiser) how to Wifi/bluetooth

Hi!
I have the new android 2.3 running fine on a tilt however the WiFi and bluetooth will not turn on and gives an error. From what I have read I do not see the typical network update.tar for 2.3. Any suggestions on how I should proceed would be greatly appreciated! Iv experimented with different software flashing various ROMs ROM suggestions would also be graciously received.
CHEERS!
Rom Ver 3.57.502.2 WWE
Radio ver 1.70.olinex
Protocol ver 25.65.30.04h
change RADIO or
androidupdate.tgz version.
thank you for the suggestion, I did try different radio ROMS and dloaded the latest update and applied. when in the android interface, setting wireless gives an error when I select it to turn it on. Does anyone have this working on an HTC kaiser? any assistance would be greatly appreciated!
Did you try Kernel version .32? Its never supposed to give Error on turn on with .32
it locks up on boot with latest zimage
last line at boot: device-mapper: uevent: version 1.0.3
generated with atools:
set RAMSIZE 0x07300000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.lzma
set cmdline "no_console_suspend ppp.nostart=0 hw3d.version=1 mddi.width=240 mddi.height=320 board-kaiser-battery.battery_capacity=2160 board-htckaiser.panel_type=0 board-kaiser-keypad.atttilt=1 sys_partition=/sdcard/andboot/system.img data_partition=/sdcard/andboot/data.img"
boot
Progress! wifi does come on with kernel 2.6.25, I get an IP but cannot browse. I can ping the phone. Once the screen saver comes on I cannot get back in. A white screen when I try to wake it up. Still open to suggestions
wardman said:
Progress! wifi does come on with kernel 2.6.25, I get an IP but cannot browse. I can ping the phone. Once the screen saver comes on I cannot get back in. A white screen when I try to wake it up. Still open to suggestions
Click to expand...
Click to collapse
Change Panel Type in default.txt
THANK YOU! panel type = 2 seems to work great
So any thoughts on the WiFi and not able to surf?
What radio should I use if I want to keep the duel boot option and get wifi to work on kernel 32? if that is my problem...
please help
I updated to radio 1.70.19.09 still freezing on kernel .32 on device-mapper: uevent: version 1.0.3
AND
Still wifi seems to be active but browser does not work. I can ping the phone!
I have same problem, wifi seems to be active but browser and app does not work.
Probably the problem is the dns setting or the routing table.
I suggest both to open terminal (or adb) on the phone and ping the google ip.
If it works the problem is the dns settings.
I tried this..
http://209.191.122.70/
(yahoo.com)
times out on the tilt, loads fine on laptop...
I boot froyo and wifi works!
Where can i find a 2.3 android? and kernel compatible?
I have the solution to the problem of you with wifi:
Step 1: Download Andboot folder (3mb) http://www.4shared.com/zip/p28ZDul3/Andboot.html
Step 2: download Gingerbread (CyanogenMod - ANDROID 2.3)
http://forum.xda-developers.com/showthread.php?t=948134
The wifi will not work after this rom, but there's a solution:
download the update wifi
http://www.4shared.com/file/45NA6EXA/androidupdate.html
and Update.
Now you have the android 2.3 (CyanogenMod) installed and the bluetooth and wifi working!
Take this opportunity to ask for help with the camera because I could not make it work.
I hope it helps.
What's that haret...exe in the andboot folder for. What's the difference to the haret.exe you get after unrar the ziped file?

Tab Pro 8.4 + TWRP 2.7.0.2 + CM11 = wrong date & time

Hi, I have some weird behavior with date and time in CM11 - I can set it through settings (I can`t use network time, I do it manually), but after reboot it reverts back to 2nd January 2014 It is not frozen though, it changes in time. Another strange thing that in TWRP time is total different from actual and that reverted in CM11. So I have three "times": original we live in, for CM11 after reboot and for TWRP
As I can`t find anything about it, I suppose everyone`s time is fine. So can someone with CM11 and TWRP please try to set some wrong time manually and check whether it is changes on reboot? Thanks.
EDIT: While researching, I find this line on dmesg output:
"alarm_set_rtc: Failed to set RTC, time will be lost on reboot"
Found this topic
http://forum.xda-developers.com/showthread.php?t=2480713
So, maybe crpalmer could confirm that all is needed is to recompile kernel with `rtc_write_enable` to `true` flag?
Zero-V said:
Hi, I have some weird behavior with date and time in CM11 - I can set it through settings (I can`t use network time, I do it manually), but after reboot it reverts back to 2nd January 2014 It is not frozen though, it changes in time. Another strange thing that in TWRP time is total different from actual and that reverted in CM11. So I have three "times": original we live in, for CM11 after reboot and for TWRP
As I can`t find anything about it, I suppose everyone`s time is fine. So can someone with CM11 and TWRP please try to set some wrong time manually and check whether it is changes on reboot? Thanks.
EDIT: While researching, I find this line on dmesg output:
"alarm_set_rtc: Failed to set RTC, time will be lost on reboot"
Found this topic
http://forum.xda-developers.com/showthread.php?t=2480713
So, maybe crpalmer could confirm that all is needed is to recompile kernel with `rtc_write_enable` to `true` flag?
Click to expand...
Click to collapse
My time is correct (via network time services). Why (and how) are you unable to use them?
Can you provide specific steps to reproduce the problem that you are seeing?
crpalmer said:
My time is correct (via network time services). Why (and how) are you unable to use them?
Can you provide specific steps to reproduce the problem that you are seeing?
Click to expand...
Click to collapse
I`m not surprised that your time via network sync is correct. About why - I`ll make long story short: I have no wifi now and will not have for some times in future.
Specific steps are easy enough: set manually time&date in settings, then reboot - time&date are far from what you have set (without network syncing of course).
Can you go to terminal or adb shell and see if that rtc message is there? E.g.
dmesg | grep time
or
adb shell su -c dmesg | grep rtc
Zero-V said:
Hi, I have some weird behavior with date and time in CM11 - I can set it through settings (I can`t use network time, I do it manually), but after reboot it reverts back to 2nd January 2014 It is not frozen though, it changes in time. Another strange thing that in TWRP time is total different from actual and that reverted in CM11. So I have three "times": original we live in, for CM11 after reboot and for TWRP
As I can`t find anything about it, I suppose everyone`s time is fine. So can someone with CM11 and TWRP please try to set some wrong time manually and check whether it is changes on reboot? Thanks.
EDIT: While researching, I find this line on dmesg output:
"alarm_set_rtc: Failed to set RTC, time will be lost on reboot"
Found this topic
http://forum.xda-developers.com/showthread.php?t=2480713
So, maybe crpalmer could confirm that all is needed is to recompile kernel with `rtc_write_enable` to `true` flag?
Click to expand...
Click to collapse
I finally got a chance to try this out for you and I think that the reason that the write is disabled is that our hardware PM hardware doesn't have an RTC that can be set.
When I enable the write, it tries it and fails:
Code:
<6>[ 7.226332] qcom,qpnp-rtc qpnp-rtc-e1946600: Seconds value to be written to RTC = 1392714221
<3>[ 7.226437] qcom,qpnp-rtc qpnp-rtc-e1946600: SPMI write failed
<3>[ 7.226443] qcom,qpnp-rtc qpnp-rtc-e1946600: Write to RTC reg failed
which means that there isn't much that I can do to fix it.
crpalmer said:
I finally got a chance to try this out for you and I think that the reason that the write is disabled is that our hardware PM hardware doesn't have an RTC that can be set.
When I enable the write, it tries it and fails:
Code:
<6>[ 7.226332] qcom,qpnp-rtc qpnp-rtc-e1946600: Seconds value to be written to RTC = 1392714221
<3>[ 7.226437] qcom,qpnp-rtc qpnp-rtc-e1946600: SPMI write failed
<3>[ 7.226443] qcom,qpnp-rtc qpnp-rtc-e1946600: Write to RTC reg failed
which means that there isn't much that I can do to fix it.
Click to expand...
Click to collapse
Strange, so there is no way to change hardware clock from OS? Even from stock Samsung`s Android? Maybe from recovery? I mean I think it has to be a way to set it somehow...
EDIT:
Wait, are you saying there is no hardware RTC of any type? I doubt it! Because when rebooted, tablet`s clock is not set to specific date&time, it is go back by some N seconds. And anyway not having RTC in such device is almost impossible imho.

Categories

Resources