yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] bally3:
Just tried the new image posted in the Kaiser thread, works really well - the Android bootup logo is aligned to qvga size and everything else is as the 21st Jan system.img posted by DZO/Shadowline.

Just to go back to the heat issue I reported earlier. I left Android running with the screen off at work for an hour and did the same again with WinMo to test.

Android made my phone a lot warmer - WinMo on my desk the device is almost cold but with Android it gets quite warm. I'd love someone else to try this as I'm suprised I'm the only one to experience this. GPRS was off so was wifi on both occasions.
[Touch Cruise Android Development] ThaYoung1!:
Hi bally3,

I think this post must be placed in the Testing thread (if so: could someone move it together with this post).

I'm willing to test the 'heating-issue' with you. I've just booted Android on my phone and will leave it for one hour without 3G connection / screen off / not connected to a power source (on battery power). Will report the results in one hour (set my Android Alarm ;)).

For everybody else working on the Android For Polaris project: thumbs up! It's really great to see the progress made so far. Hope we'll get a fully working Android version in time. Keep up the great work.
[Touch Cruise Android Development] adderz91:
Spose ill report on the heating issue too.

Gimme an hour.

To the poster above. No rules apply to Bally, he keeps everything running so smoothly here regarding projects he deserves to do what he likes :-P.
[Touch Cruise Android Development] rogro82:
Because of the power management still not working its normal it will get hotter ( it isnt turning off most stuff, like winmo does and that isnt just wifi/bluetooth etc ), that also why it drains the battery faster then winmo. Just set your winmo so that it doesnt get turned off and feel after a few hours... it will also be a bit hotter...

As soon as the power management is completely working it will also result in a cooler phone..
[Touch Cruise Android Development] ThaYoung1!:
Test done... Left it for an hour; no heating issues. It's even colder than my hand. Temperature inside our office is 21 Celcius.
[Touch Cruise Android Development] imfloflo:
Just test this new system.img still no sms working for me :s

My phone isn't warm too.

I see the vibror icon for the first time when i decrease totaly the volume nice :)
[Touch Cruise Android Development] rogro82:
Yes fixed the vibra in the latest zImage... also can confirm it works you receive a call and when you drag ( hold ) an icon on the home screen.

System.img posted in the Kaiser thread doesnt have the modified ril code from DZO with the working network/sms, I already posted that on there and told them which file they need to include.
[Touch Cruise Android Development] adderz91:
Yeh thanks for clearing that up Rogro.

Mine also warmed up Bally, mostly on the screen side, the top half of the phone.
[Touch Cruise Android Development] mikeisback69:
Heating issue

I've done the test too, and got a bit warmer but nothing especial. Whats the last imege of android to polaris? is the one on the 1 page
[Touch Cruise Android Development] imfloflo:
Read the wiki page, it's the only place where you can find the lastest files
[Touch Cruise Android Development] rogro82:
Ok spooken to dcordes and am cleaning some stuff up so we can build directly on the changes made by DZO with the polaris mach type... So far all seems well and i can get it to boot using the right mtype.

This way people wont have to make any changes ( I hope ) when DZO makes general changes and can compile for Polaris easily.
[Touch Cruise Android Development] imfloflo:
Very good news to have a generic zimage and just have to change MTYPE we can now all work on same files and progress faster :).

Again thanks for the effort Rogro82
[Touch Cruise Android Development] excogitation:
fund raising?

Would it be a good idea to start a fund raising to get specific tasks done (faster ;-) e.g. those milestones (did I forget something?):

phone

Wi-Fi

USB networking

power management

GPS

bluetooth

main Camera - back

videophone camera - front

GPS

headset

appstore

...

btw

that sounds really good.
[Touch Cruise Android Development] mano42:
hm, I think you forgot GPS ;)
[Touch Cruise Android Development] rogro82:
Can anyone try out the added zImage with mtype set at 1723 in the default.txt?

So:

set MTYPE 1723

All functionality should be the same as it was before but now using the Polaris mach type and this one should still be able to work on kaiser/vogue/polaris with there own machtypes.

Thanks
[Touch Cruise Android Development] seminiox:
hi rogro82,

it starts booting crashes after "No partition found on SD card" with message:

p1

/bin/sh: can't access tty; job control turned off
[Touch Cruise Android Development] rogro82:
Have you been able to boot previous zImages and did you change the mtype in the default.txt?
[Touch Cruise Android Development] imfloflo:
Hey rogro just test your zimage with different MTYPE.

Booting fine but can't call :s

I try to send sms it says "currently can't send your message, it will be send when the service becomes avalaible"

I use the lastest system.img from Mullins.
[Touch Cruise Android Development] Michel82:
Boots fine with the MTYPE and everything works like before. That includes the networking functionality; calling (without audio), sms and internet. Also your latest additions on vibra and backlight are working.

I guess this'll make source version control much easier.
[Touch Cruise Android Development] seminiox:
yupp, i've been able to boot your last release without any problems. I use M-Amine's ROM on a XDA Orbit2:

CE OS 5.2.19965 (Build 19965.1.2.3 M-Amine)

Radio: 1.59.42.23

and this is my default.txt

well some other news here..... i can get it booting 2 out of 3 times. getting lots of i/o errors..... i think i will format my sd card...... maybe some bad sectors
[Touch Cruise Android Development] rogro82:
Yes this way we can cleanly merge into the vogue-tree... Will save a lot of work keeping up with changes made by others for example DZO.

Imfloflo:

This should do nothing to your android specific problems ( like sending SMS ).

The code hasnt changed, besides changes needed to make to make it compile next to the kaiser and vogue.
[Touch Cruise Android Development] imfloflo:
@Rogro I know but, alwys the same probleme.

I will wait for a package with the lastest known stable version.

I will test why other success to send sms but not having sound both way during call and why i can't send sms but having good audio.
[Touch Cruise Android Development] rogro82:
Imfloflo:

You shoulnt look it in the zImage but in the system.img which needs to have a working Ril ( the ril created by dzo works for some and for some it dont... ). Im am not able to setup a phone call at all with the sms enabled system.img ( it stops immediatly with a call ended ).

For now i dont have a lot of time to look into it but if it wont work in the next few weeks ill try to build my own.
[Touch Cruise Android Development] imfloflo:
@I know it's in system.img but i had try 4 differents and no one succes to send sms :s

Will wait :)
[Touch Cruise Android Development] craigad:
I can confirm that using the new Zimage, there is no change in performance or functionality.

Which is what you needed to confirm is it not Rogro?

/craigad
[Touch Cruise Android Development] imfloflo:
Maybe there is a little hardware difference between version of polaris / 02 / cruise /P3650 ?
[Touch Cruise Android Development] rogro82:
Yes basically people being able to boot using the correct mach-type is what i needed to hear :) The code hasnt changed much, besided some things i had to change to make it fit in with the rest...

Known issues will be easier to solve after we are commited into the vogue-tree, so thats of my main concern now.
[Touch Cruise Android Development] dubbeld00:
I think it is because some people haven't updated the system.img. If I use the latest system.img, I can't browse on the webbrowser, while it is fixing other things (don't know what.. but I thought it did ;)). With an older system.img (without the modified ril) I can browse, but am not able to do other things...

So I guess we are all having the same problem, but due to the fact everyone is using different versions, we see all kinds of problems.
[Touch Cruise Android Development] imfloflo:
Ok so we must all use the same system.img and zImage. Maybe create a wiki page which list all avalaible system.img like for the zImage on polaris_linux page.
[Touch Cruise Android Development] pt-1:
Someone just needs to update this topic: http://xdaforums.com/showthread.php?t=473102
[Touch Cruise Android Development] dubbeld00:
I think I just wait a little more, since we are still seeing great progress over here, I guess in about a week or 2 we don't have these problems anymore, there is too active development at the moment...

So if you've addressed the problem, it is already solved by DZO, or we have a new system.img, or... and so on ;).

__

Waiting for the new UDK rom at the moment...

Btw, to the poster above me, marcelkordek is updating the topic quite well
[Touch Cruise Android Development] bpmorris:
Once again my thanks to Rogro82! I always look forward to his updates and then testing the many improvements.

I can confirm Android boots and works in the same way it had previously. For me that means no browsing where it has worked previously and no hanging up from calls....

HTC Touch Cruise

Gullum TF2D III

Rom Version:5.2.21109 WWE

Radio: 1.59.44.02
[Touch Cruise Android Development] Michel82:
I wonder what to expect next. Is it possible we create some sort of roadmap?
[Touch Cruise Android Development] imfloflo:
in the wiki page
[Touch Cruise Android Development] rogro82:
Ok ive finished my work on the backlight... Im now able to set the brightness from the settings in Android.

Nice how the screen fades out when pressing the power button.

Ill post up a new zImage when Ive tested all and think its stable.

Bit by bit its getting better..
[Touch Cruise Android Development] marcelkordek:
great work rogro !!
[Touch Cruise Android Development] Michel82:
Great news again, can't wait for your next release.

Did you hear anything from DZO about in-call audio yet? If it's only possible to divert audio to either external or internal speaker than internal audio might be more usefull for now, especially since the vibramotor is functional now.
[Touch Cruise Android Development] rogro82:
Ok here it is,

Let me know if the brightness is working. You can change it in Settings -> Display -> Brightness
[Touch Cruise Android Development] imfloflo:
OK just test it with the lastest system.img from mullins web page.

brightness working good.

Thanks.
[Touch Cruise Android Development] bpmorris:
Hi Rogro,

I can also confirm brightness settings now work. I loaded both your zimage and mullins system.img as linked to from the first post on the testing thread. I am also now seeing a noticeable performance lag. I suspect that has more to do with the system.img then your changes as this is the first time performance browsing the menus has been an issue. When I get a moment I will copy back DZO's system image and retest.

HTC Touch Cruise

Gullum rom

1.59.44.02:):)
[Touch Cruise Android Development] radem205:
Brightness works ok, but I also notice a performance lag (without using the mullins system.img). It takes a long time to boot and in Android everything works slowly.
[Touch Cruise Android Development] ThaYoung1!:
Just tested it. The brightness settings work correctly. Indeed it's nice to see it fade.

What doesn't work anymore is the adjustment of the screen orientation by (fully) pressing the camera button. When I press it the linux command prompt is shown and at every button press I'll see codes on the screen... Only a boot solves this problem.
[Touch Cruise Android Development] rogro82:
The touchscreen driver is fully stripped so that we can implement pressure / aligning in a decent way.

I dont have any performance lag... Can you try to reload with a new data.gz?

Hmmm somehow i guess i turned my debug option on in the keypad driver... ill go and turn it off and upload a new zImage
[Touch Cruise Android Development] mathojojo:
Hello, I have problem with the boot of Android.

I tested it the first time yesterday. I have all latest files (zimage, system.img,Haret.exe,Default.txt, init...). I set the Mtype in the default.txt file. The files are in the racine (french word, I don't really think it match at english :) ) of the sdCard

see the code I get from the booting process :

[ 2.533690] EXT3-fs: mounted filesystem with ordered data mode.
mount: mounting /dev/block/loop1 on /system failed: Invalid argument
Failed
Failed to mount /system
/bin/sh: can't access tty; job control turned off

I think i did a big mistake somewhere in my try, but where ?????
[Touch Cruise Android Development] rogro82:
mathojojo can you make your post in the test thread... they are able to help you over there i guess :)
[Touch Cruise Android Development] craigad:
Rogro82,

i take it you have seen poly_poly-man's comments on the battery?

http://xdaforums.com/showpost.php?p=3247520&postcount=2540

/craigad
[Touch Cruise Android Development] rogro82:
Yes was actually discussing this yesterday with cr2 who confirmed me it is working over i2c in our case.... Didnt had any time to look into it further because i had to create latest diff files of my work and test them and send them to dcordes to commit.

Luckily both kais and polaris share this so its more likely to get done soon.
[Touch Cruise Android Development] craigad:
OK........no pressure :-)

just trying to help avoid replication of work. Your time is precious.................

/craigad
[Touch Cruise Android Development] brumbrum:
Is it possible for you to put a link to this System.img-file?
[Touch Cruise Android Development] mathojojo:
Ohohhhh, an answer from Rogro82 himself :) I'm lucky :) Nice to meet you, and thank you for your great work !!

I ask maybe too much, but can you (or someone else) post the link for the test thread ??

Merci beaucoup/
[Touch Cruise Android Development] Michel82:
http://xdaforums.com/showthread.php?t=473102&goto=newpost
[Touch Cruise Android Development] rogro82:
Ok ive figured out the lag... youll need to power off Android because of the hardware changes ( the backlight works through the /sys/class/leds ).

To power off hold the power button and choose Power off... the button is a bit buggy so youll have to try it a few times because now and then after holding it the screen will go off.

Now the phone will actually power down and you can power it on again.
[Touch Cruise Android Development] Michel82:
I'm also having the lag issues. I tried turning off the phone as you explain and restart, but that doen't seem to make a difference.

I've also replaced my system.img (latest from DZO) with the one from mullins but i can't seem to make an internet connection with this one. Togga just says modem initialized, which it didn't before.
[Touch Cruise Android Development] rogro82:
Did you also try a new data.gz? Im having no lag issues what so ever...

Edit:

Fixed the camera button ( removed the set_console command )
[Touch Cruise Android Development] Michel82:
Yes tried a complete new installation. Going to put your new zimage on, with DZO's system.img. Maybe the lag is due to mullins system.img
[Touch Cruise Android Development] bpmorris:
Rogro..

New data.gz? I have just been using the new files out of the first post of the testing thread. Is there a new data.gz in another location we should be testing with? I assumed the one in the 19/01/09 package would be the latest?

Cheers!
[Touch Cruise Android Development] rogro82:
Its not a new data.gz, but i mean a clean data.gz which gets extracted as a new data.img to clean all your settings etc.

Sometimes its necessary to revert to a clean data.gz because of all the changes.

Be aware:

All stuff saved is gone as they are saved in the data.img
[Touch Cruise Android Development] Quilapvd:
I am wondering,

I have a bluetooth headset for wireless music playing and calls etc..

If Android is done for the Polaris? Can I use the bluetooth headset also at Android?

Just to clear up some things.

Greetz.
[Touch Cruise Android Development] Michel82:
Still having the lag issue (very annoying), it also seems touchscreen is not responding very well. Maybe these two problems are related.

This is what i did:

-Renamed my AndoidApps folder to prevent it from autoinstalling the apk's inside

- Deleted data.img

- Placed data.gz

- Placed latest system.img from DZO

- Placed latest zImage from Rogro

- Turned off phone like explained and restarted

B.t.w: Internet is working again with DZO's system.img
[Touch Cruise Android Development] rogro82:
Just did the same and turned off the phone from within Android with "Power off" function and restart the phone and haret...

No lag issue... Can anyone else also try this and share there findings..
[Touch Cruise Android Development] bally3:
dont just follow it flo.. CONTRIBUTE! :)

We need more people building these zimages - and someone posting them up for everyone to test.
[Touch Cruise Android Development] dwaradzyn:
Yes it does matter. Only on ROMs based on official HTC 6.1 ROM you can get 10/10 boots using HaRET.
[Touch Cruise Android Development] NeoS:
I've got vacation planned next week. ;) Playtime.
[Touch Cruise Android Development] imfloflo:
dcordes can build and put zImages like he already do, i haven't enough skills in linux to modify code in this files and then rebuild my own zimages but i can test it when they will be out.
[Touch Cruise Android Development] dwaradzyn:
My old dev environment was unstable - Eclipse was causing segfault about 20 seconds after starting and it was very inconvenient to reboot to Linux to play with kernel for Polaris. I've set up a new dev environment according based on 32bit ubuntu on VMWare.

I've built kernel from latest linuxtogo repository. I tried to boot Android 1.0 (from Vogue site) using this kernel. It does not seem to have SD issue - for the first time it successfully unpacked system.gz and data.gz files without SD error. Every previous kernels died on unpacking those files.

There is a bug that makes it hang when any button on onscreen keyboard is pressed - I'll look into that. Android 1.0 did not boot because I forgot to include loopback device in config. I will let you know if it will boot.
[Touch Cruise Android Development] dwaradzyn:
I also wanted to compare Vogue sources and latest linuxtogo sources. It is almost impossible - sources are based on completely different git commit and there are way too many differences.
[Touch Cruise Android Development] dwaradzyn:
Now Android 1.0 crashes few seconds after mounting system.img and data.img. The messages is:

A N D R O I D

binder: 367:367 unknown command 25356
binder: 367:367 ioctl c0186201 be987af8 returned -22
binder: 367:367 ERROR: Thread waiting for process work before calling bcREGISTER_LOOPER or bcENTER_LOOPER (state 10)

Anyone have and idea how to overcome this?

EDIT:

binder is a kernel module for IPC. I think this is userspace problem. I will try to get latest system.img from Vogue, maybe it will help.
[Touch Cruise Android Development] imfloflo:
How did you success to boot 1.0 on polaris with the extf3 SD partition ?
[Touch Cruise Android Development] dwaradzyn:
I did not success to boot into Android 1.0 GUI but it went further than previous time I tried it.
[Touch Cruise Android Development] dwaradzyn:
Ok here is the zImage I compiled from latest git.linuxtogo.org repository. There is also a full keyboard I use in Angstrom.

Edit:

It was created from git.linuxtogo.org branch msm-htc, commit 1082670ccae30e6592311cc9dee93ba978382a25.

I uploaded one more diff you should apply and config i used for compiling. You should get identical kernel if you use those.
[Touch Cruise Android Development] maximos86:
i have tested your zImage and it works for me with ur keyboard. however i found nothing different from previous zImages...
[Touch Cruise Android Development] kensou.8:
It work for me too. At the first glance, it seem there is no change but the keyboard look like different. Now I've to use a pen to use it (it seem smaller than the previous one). Calling worked for me (sfr france).
[Touch Cruise Android Development] imfloflo:
@dwaradzyn so which version do you run 0.8 SDK?
[Touch Cruise Android Development] dwaradzyn:
I tried to run Android 1.0. It failed to boot but the reason was not related to SD issue (i think so). 0.8 version should work fine with this kernel.
[Touch Cruise Android Development] dwaradzyn:
BTW

You can also try other distros. Make a 256 MB ext2 partition on your SD card (you can use gparted for that), unpack this rootfs onto that partition and put:

set RAMSIZE 0x07800000
set MTYPE 1723
set KERNEL zImage
set cmdline "rootdelay=5 root=/dev/mmcblk0p2 fbcon=rotate:0,font:MINI4x6"
boot

into your default.txt and boot. It willl look like this:
[Touch Cruise Android Development] imfloflo:
I thought we must make a ext3 partition to use 1.0 SDK on our SD with polaris?

Why don't create a new thread with all distrib and picture which can be install and work on our polaris?
[Touch Cruise Android Development] bally3:
We already have two threads on Android - this one was created as the other one was getting too big and confusing. It might help to add this to the first post which I shall do when I get home today - hopefully.

Dwarardzyne, thanks for kick-starting this again, I will take a look at the images you've posted tonight. I was also wondering how to get a linux setup going as I use windows on both my laptop and my pc, but the vmware idea seems like a good one - I'll have that set up as soon as I get the chance.

Keep up the good works peeps - its good to see everyone getting enthusiastic with this project again :)

With regard to 1.0 and 0.8 - is the vogue version based on 1.0? if it is then we should try to get this working first I think as, DZO pointed out our devices are almost identical and we should be able to take a lot more of whats working from his version.
[Touch Cruise Android Development] bally3:
Can you do this as well as keeping your windows partition on your SD card?
[Touch Cruise Android Development] dwaradzyn:
Yes. This is exactly what I have. On my 8GB card I have 7,5GB FAT32 + 2*256MB ext2 to play with linuxes.
[Touch Cruise Android Development] imfloflo:
dcordes and szsoftware are 2 member of xda and they test lot of things in irc #htc-linux about booting 1.0 SDK via SDcard on polaris maybe we should ask them?

You can read this logs if you can't access IRC à work, there are a big source of informations http://irclog.iclem.net/?chan=htc-linux&day=9 and previous days
[Touch Cruise Android Development] Michel82:
Hmm stangest thing, i did a few more shutdowns and reboots and after about the 5th time the problem seems to be gone. Could it be it doesn't always cleanly shuts down?
[Touch Cruise Android Development] rogro82:
Ill look into it, luckily the power down worked after a few tries... ill just go and check all the drivers if they shut down normally.

Thanks for trying once more.
[Touch Cruise Android Development] bpmorris:
Rogro,

I just did all you suggested new data.gz, DZO's system image and your latest zimage and now were moving forward again. So much so toga is now working and I can connect to the net where before the modem was not initializing. I cannot see any performance lag either, I can only assume that there is something suspect in mullins system image. If you keep developing were more then happy to keep on testing!!!
[Touch Cruise Android Development] pt-1:
Could you be so kind and post the link for the data.gz as I just deleted my data.img and added a "old" data.gz and it boots again ;-)
[Touch Cruise Android Development] bpmorris:
PT-1,

I tend to save all my files locally however I am %99 sure I downloaded it directly from DZO webpage. Here is the URL.

http://it029000.massey.ac.nz/vogue/android-21-01-09.zip

Extract that and then I imagine all you should have to do is add Rogro's latest zimage...