yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] rogro82:
Hi all,

Ok because i got tired of retyping shell commands in the terminal I wrote an application that allows you to save/run shell scripts from within the Android UI.

It even allows you to create shortcuts on your desktop to a specified script.

I created scripts and shortcuts for things like Reboot as Android doesnt have a reboot option. I know some people would love to have the ability to reboot or execute shell scipts and this makes it possible without the need of a keyboard :D You can write the .sh files place them in the root of your sdcard and load them from within the application.

Its written for the G1, but i think it should work on the Polaris as well ( Hopefully :) )

Could anyone give it a try? Files can be found here:

http://xdaforums.com/showthread.php?t=486486

The phone uses /system/bin/sh and /system/bin/su ( which is a copy of sh with suid set, so its executed as root user ), I guess the image doesnt have su... so you should either copy sh to su and chmod 4777 it. Or try to execute the files without "Needs Su" and makesure the sh file has suid set.
[Touch Cruise Android Development] Michel82:
Nice feature and very handy for us polaris people since we don't have a softkeyboard since the latest versions from DZO.
[Touch Cruise Android Development] radem205:
@Rogro: Thank you for this wonderfull app!

I saw dzo has released a new package (http://it029000.massey.ac.nz/vogue/files/android-1.1-27-02-09.zip) with a fix for the softkeyboard on the vogue.

I have tried the package but the keyboard isn't working for the polaris, but I think it's not difficult now to fix this for the polaris (I can't :p but I hope Rogro will look into it :) ).

Also the screen displacement isn't fixed yet :(
[Touch Cruise Android Development] marcelkordek:
hey also have seen the new package from dzo, i read in vogue thread that this is without a soft keyboard... dzo writes that we must wait for the release of the htc magic.... hope it will released soon =)

@ radem205:

i use the latest files from dzo (the 23.02.09 package not 27.02.09!!)

and i have no screen displacement... i began with a fresh install and after the first reboot screen displacement were gone =)
[Touch Cruise Android Development] radem205:
Ok, I will try that. Thanks!!

Edit: Could you post your default.txt? Because your method isn't working :s and I think it has to do with a setting in default.txt

But in the commits (http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue) dzo said that he fix the softkbd for the vogue. I think he mentioned that the good looking softkbd from the cupcake version isn't implemented (I hope :p).
[Touch Cruise Android Development] marcelkordek:
ok post i as soon as possible....
[Touch Cruise Android Development] imfloflo:
Just try the 27 1.1 release and receive an sms when screen is of cause the screen split in 4 part :s

Less blurry but not good for the moment.
[Touch Cruise Android Development] kulen:
nice to have you back rogro :)

and bally thank you for all your effort. I believe if you were a developer, and with all your enthusiasm, we would already have fully funcional working Andorid on our Polarises :)
[Touch Cruise Android Development] radem205:
That would be great!!
[Touch Cruise Android Development] marcelkordek:
here's my default.txt (setup for eplus germany)

#alloctest 0x2000

set RAMSIZE 0x07000000

set RAMADDR 0x10000000

set FBDURINGBOOT 0

set MTYPE 1723

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 0 for best power savings

# board-htcvogue.panel_type - Panel type used to power the panel off and on

# 0=Don't power off the panel (Default)

# 1=Hitachi 2=Topoly 3=Samsung

#

#set cmdline "ppp.apn=www.vodafone.net.nz ppp.username=\"\" ppp.password=\"\" pm.sleep_mode=3 msm_sdcc.msmsdcc_fmax=20000000 no_console_suspend board-kaiser-keypad.atttilt=1"

set cmdline "ppp.apn=internet.eplus.de ppp.username=eplus ppp.password=gprs pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 board-htcvogue.panel_type=3"

boot
[Touch Cruise Android Development] radem205:
Thank you! But I thought to let the power collapse working you have to set the pm sleepmode to 1, isn't it? How long does your phone work with a full battery?
[Touch Cruise Android Development] marcelkordek:
pm sleepmode is set to 1 =) i haven't test it yet but i think power collapse isn't working on polaris... right?
[Touch Cruise Android Development] radem205:
I think power collapse isn't working well on polaris yet. But try change the resolution, for example to 312 x 416 (advice from dzo) in default.txt. Then you will see the screen displacement is back :(. With your default.txt it's working.
[Touch Cruise Android Development] dzo:
Can someone with screen displacement problems after wakeup try this:

http://cs-alb-pc3.massey.ac.nz/vogue/files/zImage-test

May or may not work, I can't test it.
[Touch Cruise Android Development] marcelkordek:
using you zimage and it works...
[Touch Cruise Android Development] radem205:
Thanks dzo, but it didn't work for me. I'm using the resolution 312 x 416 . A long time ago we had this problem too and rogro solved this problem. Do we have to set some specific in default.txt to let it work?
[Touch Cruise Android Development] dzo:
The best way to fix this is to power the panel down when the device is asleep. The fact that you get this problem probably means that power collapse is working (pm.sleep_mode=1), do a dmesg in the terminal to see for sure.

The panel power up sequence is a little tricky and someone will need to trace it on all the possible panel types. Vogue has 3 panel types, kaiser has 2.

To trace it you need to trace pmdh accesses to physical address 0xaa600008 (remember to look at all the mappings). Use setlcd 4 and setlcd 1 in another haretconsole session to turn the panel off and on.

This will give you a physical address where the mddi commands are stored. Trace this page and you will get the actual mddi commands. Timings are also important, look at the panel code in board-htckaiser and board-htcvogue.

Martin
[Touch Cruise Android Development] imfloflo:
With the lastest package "android-1.1-27-02-09" the bootlogo isn't ok.

Just tried the new zImage-test and always have the screen split when i wake up if i wake up agay the screen move to the right and to the top, wake up 5 time and the horizontal alignement is ok but the vertical isn't

my default.txt was set to original dafault-kaiser value just change ram and mtype
[Touch Cruise Android Development] marcelkordek:
dzo, is it possible to add languages ??

tested your new zimage-test.... now when phone wake-up the screen is black.
[Touch Cruise Android Development] radem205:
Thanks for your reply! But I can't test the power collapse using "dmesg", because we don't have a working softkeyboard at this moment.

Unfortunatly I'm not able to trace things using haretconsole, because I don't have linux installed :(

Which zimage do you mean?
[Touch Cruise Android Development] bally3:
screen displacement with the 27-02 or the new image does not happen if the resolution is set to either 240 x 320 native or at 320 x 480.

This leads me to believe that we just need to find the correct resolution for the Polaris as at 312 x 41, not only do you get the displacement after power down, the screen is also slightly bigger (noticed more when q&d keyboard s used). I would play round with these resolutions from the kaiser thread and report back the ideal one if anyone wants to help:

I would also advise everyone to go back to the 21-02 files as they work much better on the Polaris.

Anyone care to post a link with the 21-02 files with the 128mb data.img file included?

Thanks :)
[Touch Cruise Android Development] radem205:
The 21-02 files are from the cupcake version, right? I want to upload the files, but where can I find the 128mb data.img? Because at the moment I have a 64mb data.img.

BTW: This is a great app (with softkeyboard (only for the program)): http://www.chompsms.com/
[Touch Cruise Android Development] bally3:
its all in the kaiser thread, sorry im out at the momentso i cant post the link but what you need to do to make itwork is install android as norma dont make any changes to it, reboot and then replace the data.img file with the 128MB version and restart. you should now see 80mb or more storage space in settings.
[Touch Cruise Android Development] radem205:
Here are the files with data.gz that will extract to 128M:

uploading again...
[Touch Cruise Android Development] marcelkordek:
zimage-test from 28.02.09
[Touch Cruise Android Development] bally3:
btw, hs anyone found a better soft keyboard apk to the q&d yet? preferably one that runs at startup automatically.

Actually has anyone found a good start up program? i downloaded a load of apps from the Market app but they all disappeared when I put the 27-02 files on :rolleyes:
[Touch Cruise Android Development] bally3:
Memory Up program destroys Android memory and wipes SD Cards

There will be a number of apps on Market that have not been tested by x-devers before.

Whether the above article is true or not Now that Market is working on Android, a word of warning and caution to all - especially if you are new to xda developers - if you choose to download apps from Market, do so at your own risk. Their are comments on the most popular ones and any that have more negative than positive comments should be downloaded with caution.

At the time of writing this, we are using Android from our memory cards so I'm not sure whether any malicious software would be able to access any other part of our phone to cause permenant damage, but regardless of this, you should still take the same cautions as you would be expected to using Win mobile.

It goes without saying that xda developers or anyone involved with this project take no responsibility for apps downloaded that cause damage to your device.

*** I posted this on the Kaiser thread also, but as I took lead on this project with the Polaris, I will ask again personally for Polaris users to exercise a degree of precaution when downloading and testing builds and apps. There is an eagerness which we can all understand of users wanting to help - but taking unneccesary risks like flashing radios from other devices carries a huge amount of risk of rendering your device useless and should only be taken if you understand the risks,
[Touch Cruise Android Development] radem205:
@Bally: Which resolution have you checked already? So I can check some resolution too.

BTW: For some reason the files from 21-02 doesn't boot on my device anymore, so I deleted the download link :s

Edit: Using 300x400 as resolution I noticed the displacement only occurs in vertical way :s (so horizontal is fine)
[Touch Cruise Android Development] rogro82:
Can someone try to copy the functions that power on/off the panel from the board-htckaiser to the board-htcpolaris to see if these are also working for the polaris?

I dont have a lot of time, but if no one knows how to do this ill try them tomorrow..

If those dont work some one should figure out the values as stated by dzo...

Its this part:
[Touch Cruise Android Development] radem205:
I've tried to build a zimage, but when I use the code underneath I get an error (error 127):

export PATH=home/arjen/android-kernel/arm-2008q1/bin:$PATH

make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

Error:

arm-none-linux-gnueabi-gcc: Command not found

Could someone explain what I doing wrong?
[Touch Cruise Android Development] kensou.8:
You have:

export PATH=home/arjen/android-kernel/arm-2008q1/bin:$PATH

instead of:

export PATH=/home/arjen/android-kernel/arm-2008q1/bin:$PATH

^^
[Touch Cruise Android Development] radem205:
I've tried that also, but it didn't work. The arm-none-linux-gnueabi-gcc is located in /home/arjen/android-kernel/arm-2008q1 so I don't know why he can't find it :s

The whole error:

make: arm-none-linux-gnueabi-gcc: Command not found

CHK include/linux/version.h

make[1]: `include/asm-arm/mach-types.h' is up to date.

CHK include/linux/utsrelease.h

CC arch/arm/kernel/asm-offsets.s

/bin/sh: arm-none-linux-gnueabi-gcc: not found

make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 127

make: *** [prepare0] Error 2
[Touch Cruise Android Development] kensou.8:
simple test:

try in others directory (/tmp for instance) to execute binaries of linux toolchain.

another thing about export: did you typed in a console or did you write it a file like .bashrc or .profile ?
[Touch Cruise Android Development] radem205:
It's working now, but I get another message :s. Sorry for these questions in this forum, but I try to help someone in the future.

Error:

scripts/kconfig/conf -s arch/arm/Kconfig

drivers/usb/Kconfig:148:warning: multi-line strings not supported

CHK include/linux/version.h

SYMLINK include/asm-arm/arch -> include/asm-arm/arch-msm

make[1]: `include/asm-arm/mach-types.h' is up to date.

CHK include/linux/utsrelease.h

UPD include/linux/utsrelease.h

CALL scripts/checksyscalls.sh

<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented

<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented

<stdin>:1321:2: warning: #warning syscall pselect6 not implemented

<stdin>:1325:2: warning: #warning syscall ppoll not implemented

<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented

<stdin>:1377:2: warning: #warning syscall timerfd_create not implemented

<stdin>:1389:2: warning: #warning syscall timerfd_settime not implemented

<stdin>:1393:2: warning: #warning syscall timerfd_gettime not implemented

CHK include/linux/compile.h

CC init/version.o

CC init/calibrate.o

init/calibrate.c: In function 'calibrate_delay':

init/calibrate.c:172: internal compiler error: Segmentation fault

Please submit a full bug report,

with preprocessed source if appropriate.

See <URL:https://support.codesourcery.com/GNUToolchain/> for instructions.

make[1]: *** [init/calibrate.o] Error 1

make: *** [init] Error 2
[Touch Cruise Android Development] excogitation:
I'm also getting this error (which I thought was because I'm on Jaunty) - maybe the build is broken?
[Touch Cruise Android Development] radem205:
Look here: http://xdaforums.com/showpost.php?p=3331331&postcount=3290 . But I think we already use this vogue_defconfig:confused:
[Touch Cruise Android Development] excogitation:
I think the htc-vogue branch is broken at the moment ... well maybe not.

Can someone try if it works with arm-2008q3?
[Touch Cruise Android Development] radem205:
It's working with the arm-2008q3 . What have you changed in the board-htcpolaris.c exco? Maybe we can work together to make a working zimage?

Tomorrow I will look at it and maybe I can post a new zimage (hopefully).
[Touch Cruise Android Development] excogitation:
Haven't changed anything yet. Good to hear that it works with 2008q3 - and I can confirm that.

What do you mean with "working zImage"? You should now get a working zImage.
[Touch Cruise Android Development] radem205:
sorry, I didn't express myself clearly. I mean a zimage with a fix for the annoying screen displacement (see earlier suggestion from rogro)
[Touch Cruise Android Development] excogitation:
I haven't tried that.

I've started playing with the latest cupcake and 1.1 versions.

What do I need to do to see the screen displacement?

Do I still need togga on 1.1 to connect to the internet?

(I noticed that version doesn't show the gprs icon after boot).

edit: yes you do (get it here)

So now how do we get the already started wlan/bluetooth/wired headset working?
[Touch Cruise Android Development] imfloflo:
For screen displacement just lock and unlock screen with power button.

Have you keyboard on your version not the dev's keyboard but the keyboard we have on previous release ?
[Touch Cruise Android Development] bally3:
Good to see other users trying their hand at developing on this project :)

Their seems to be a split now between Cupcake and 1.1, I thought 1.1 was just an experimental build by DZO but it seems we're forking off to it instead which is slightly confusing.

I cant stress enough at this time how important I think it is to keep to the kernel development as much as possible as I really do think we are at that point where we could lose momentum totally if we continue down the current path.

Dubbeld00, hows the touch screen driver coming along? any updates?

Does anyone else feel confident with doing some driver work? Someone mentioned that wifi/gps/bluetooth drivers will probably be created on the Kaiser forum, but to be honest I dont see it happening at the moment at least. Too many people engrossed with why DZO's latest build doesnt give them GPRS etc. We seem to be losing focus a bit I feel.

Considering the shelf-life of our devices, progress on this project should be considered a priority, especially where the kernel is concerned. Poly Poly man on the Kaiser thread corrected me on the user land in that there would be development work required for the differences in devices for all devices and not one version for all as I previously thought, but I still think that given that those differences should not be big enough to stop Android from loading, we should still make kernel development the priority.

It will probably need someone in the Kaiser forum to make a start in making the changes in Android as we dont have the dev power here to do it so rather than wait around for this, I say lets get the kernel completed.
[Touch Cruise Android Development] radem205:
The highest priority is to let the onscreen keyboard working. The vogue needs an onscreen keyboard too, so I think dzo will fix this in the future (hopefully). He said we have to wait until the htc magic is released, because this device has an onscreen keyboard.

And offcourse the screen displacement is a big issue at the moment.
[Touch Cruise Android Development] excogitation:
I don't see any screen displacement - but maybe you can make a picture. - I guess that means not all panels are affected.

No keyboard.

The osk will become available once the Magic is out so you don't really need to waste any time on it.

The difference between 1.1 and cupcake is that the google services only work with 1.1

(and I haven't read anywhere that those are ever going to work with cupcake (development branch)).

So 1.1 is in my opinion the interesting version for users.

I'm not too impressed with how the scaled 1.1 looks though.

320x480 (2/3) -> 240x320 (3/4) ...

But that's also going to improve according to the roadmap.

Development on both Polaris (rogro82 switched to a Dream and is busy) and Nike (biktor_gj bricked his Nike) came to a halt.
[Touch Cruise Android Development] bally3:
Again, in answer to both points - we should leave to userland to its development and concentrate on the kernel development for exactly those reasons - these things are already in the pipe-line.

Dubbeld00 was thinking about the touch screen driver, someone on Kaiser was talking about working on the wifi driver. I'm hoping we can get some devs to take note and consider donating time to this project. I've been on irc recently a few times but it always seems quiet on there too.
[Touch Cruise Android Development] bally3:
From Kaiser thread:

This is what I want to see.. come on someone.. help out here! ;)
[Touch Cruise Android Development] frankmoneylv:
deleted post
[Touch Cruise Android Development] bally3:
according to markya23 if we have the same wifi chip as the kaiser it should work, im at work so cant check but can someone tell us whether it is the same or nit and what chip it is? please?
[Touch Cruise Android Development] kulen:
Where can I find which wlan chip is in polaris?

mac address lookup says producer is HTC. But that's no use.
[Touch Cruise Android Development] worstenbrood:
http://www.digchip.com/datasheets/parts/datasheet/477/TNETW1350.php
[Touch Cruise Android Development] excogitation:
Did you open your Polaris, or where do you take that info from?

(I thought it had the same chip as Kaiser tnetw1251)

Anyways there's also a tnetw1350 driver.
[Touch Cruise Android Development] bally3:
so which one is it, do we know?
[Touch Cruise Android Development] radem205:
In this thread http://xdaforums.com/showthread.php?t=355277&page=53 and this post http://xdaforums.com/showpost.php?p=2049010&postcount=529 you can see that the polaris has the same chip as kaiser.
[Touch Cruise Android Development] frankmoneylv:
post deleted
[Touch Cruise Android Development] bally3:
thanks radem and to you guys too.

I'm just going through marky's instructions at the mo.
[Touch Cruise Android Development] bally3:
just found a file called tnetw1251.dll in the windows directory.

I wonder what the deal is with not just creating the image with the required files then? I mean we create cooked rom with the same files.. grey area perhaps?

Anyhoo, if anyone wants to join in, can you post up the files he mentions and we can look at getting them cooked for us to test by someone?

Working wifi would be a real treat at the mo with market working.:cool:

** My apologies for the double posts - Opera Mini in Gullums rom keeps logging me out of my id and into this wierd "frankmoneylv" ID even when I log out and back in again!! :confused:
[Touch Cruise Android Development] frankmoneylv:
deleted post again
[Touch Cruise Android Development] bally3:
I've combined the files from markya23 (thanks mate :) ) with the other required files. Now if only someone will give this a go..

tiwlan.ini

wpa_supplicant.conf

fw1251r1c.bin

wlan.ko

Also added tnetw1251.dll just in case
[Touch Cruise Android Development] imfloflo:
Thanks bally3 have you post it in another thread like you said this is the same chipste on kaiser
[Touch Cruise Android Development] kulen:
what do we do with this? is that only for developers to help them implement wifi or we can use it somihow?

Great to se this going on anyhow!
[Touch Cruise Android Development] bally3:
a dev needs to add them to the system.img file and recreate it to make it work as per markya23''s guide.

Not much to do until then, i'm afraid. looks like Rogro's busy on the Dream thread and Dubbeld00 has disappeared again so I guess its radem and exco who may be able to do this, if not lets hope the kaiser guys get it working and it works fine for us too. Seeing that its the same chip that should in theory be the case.
[Touch Cruise Android Development] kulen:
Great!

I hope there is some good soul that is able and willing to do that for us.

Thank you Bally
[Touch Cruise Android Development] excogitation:
Thats not a problem (I also see no problem in distributing an image containing those files).

If I read the code right - I think wlan stuff is atm only available for Kaiser though it shouldn't be a huge problem to port it to Polaris (different gpio's?) - but it's not even working on Kaiser yet (also I don't know if I can do it without causing damage to my device).

The bluetooth stuff should also be fairly easy (at least afair) - but thats only built-in for Nike atm (and also not working).

Wired Headset also "only" needs to be ported from Vogue.

Battery and Leds are also working on Kaiser but not Polaris.

Same goes for powering down the different screens (the issue I don't have) and touchscreen improvements.

So in my opinion all these issues could be fixed in a very short time by someone knowing what he's doing (unfortunately that doesn't describe me ;-).

Btw - how do I get to the console on our Polaris?

Also is there a working osk for the console?
[Touch Cruise Android Development] markya23:
Don't hold your breath on 'this Kaiser guy' :) Real life (tm) is currently getting between me and Android hacking... :(