yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] dzo:
OK, thats good but you should be doing:

addlist mmutrace 0x5166a000 0x1000 while tracing the setlcd commands.

This address may change or it may be using the other mappings so do the dump mmu command again.

What you should see is something like:

002031: mem IRQS(0) 94e00000=00010000 (00010000)

002031: mmutrace 0255e9b8: e7e7130b(strb) 4f669b00 00000001 (00000000)

002031: mmutrace 0255e9cc: e5c70001(strb) 4f669b01 00000000 (00000000)

002031: mmutrace 0255e9d0: e5c73002(strb) 4f669b02 0000000e (00000000)

002031: mmutrace 0255e9d4: e5c70003(strb) 4f669b03 00000000 (00000000)

002031: mmutrace 0255e9d8: e5c72004(strb) 4f669b04 00000004 (00000000)

002031: mmutrace 0255e9dc: e5c70005(strb) 4f669b05 00000000 (00000000)

002031: mmutrace 0255e9e0: e5c7000a(strb) 4f669b0a 00000000 (00000000)

002031: mmutrace 0255e9e4: e5c7000b(strb) 4f669b0b 00000000 (00000000)

002031: mmutrace 0255e9e8: e5c7000c(strb) 4f669b0c 00000000 (00000000)

002031: mmutrace 0255e9ec: e5c7000d(strb) 4f669b0d 00000000 (00000000)

002031: mmutrace 0255e9f0: e5c7000e(strb) 4f669b0e 00000000 (00000000)

002031: mmutrace 0255e9f4: e5c7000f(strb) 4f669b0f 00000000 (00000000)

002031: mmutrace 0255e9f8: e5e61010(strb) 4f669b10 00000012 (00000000)

002031: mmutrace 0255ea04: e5c69001(strb) 4f669b11 00000000 (00000000)

002031: mmutrace 0255ea0c: e5c69002(strb) 4f669b12 00000092 (00000000)

002031: mmutrace 0255ea14: e5c69003(strb) 4f669b13 00000000 (00000000)

002031: mmutrace 0255ea18: e5c69004(strb) 4f669b14 00000000 (00000000)

002031: mmutrace 0255ea1c: e5c69005(strb) 4f669b15 00000000 (00000000)

002031: mmutrace 0255ea24: e5c69006(strb) 4f669b16 00000001 (00000000)

002031: mmutrace 0255ea34: e5c69007(strb) 4f669b17 00000000 (00000000)

002031: mmutrace 0255ea3c: e5c63009(strb) 4f669b19 00001d00 (00000000)

002031: mmutrace 0255ea5c: e5c69008(strb) 4f669b18 001d0004 (00000000)

002031: mmutrace 0255ea60: e5c6200a(strb) 4f669b1a 0000001d (00000000)

002031: mmutrace 0255ea64: e5c6100b(strb) 4f669b1b 00000000 (00000000)

002031: mmutrace 0255ea68: e5c6300e(strb) 4f669b1e 00000040 (00000000)

002031: mmutrace 0255ea6c: e5c6e00f(strb) 4f669b1f 00000000 (00000000)

002031: mmutrace 0255ea70: e5c65010(strb) 4f669b20 00000000 (00000000)

002031: mmutrace 0255ea74: e5c64011(strb) 4f669b21 00000000 (00000000)

002031: mmutrace 0255ea84: e5c71008(strb) 4f669b08 00000076 (00000000)

002031: mmutrace 0255eaa4: e5c73009(strb) 4f669b09 00000000 (00000000)

002031: mmutrace 0255eaa8: e5c70006(strb) 4f669b06 00769b1e (00000000)

002031: mmutrace 0255eaac: e5c72007(strb) 4f669b07 0000769b (00000000)

002031: mem IRQS(0) 94e00000=00010000 (00010000)

This is for kaiser and there is one of these sequences for each mddi command.

The useful numbers here are 0x1d0004 at 0x4f669b18 and 0x40 at 0x4f669b1e

if you look in board-htckaiser.c you will see:

{0x1d0004,0x40,0},

in reg_on_toppoly[], this is where it comes from.

Nearly there....
[Touch Cruise Android Development] imfloflo:
Ok so i type

HaRET(1)# addlist mmutrace 0x5166a000 0x1000
HaRET(2)# set permissivemmutrace 1
HaRET(3)# wi 20

setlcd 4 and setlcd 1

after i type

HaRET(4)# pdump 0xaa600008 4
aa600008 | 0076a140 | @.v.
HaRET(5)# dump mmu 2 0xaa600008
----- Virtual address map -----
cp15: r1=00a5387f r2=10640000 r3=00000001 r13=24000000

Descriptor flags legend:
C: Cacheable B: Bufferable D: Domain #
AP: Access Permissions (for up to 4 slices):
0: No Access 1: Supervisor mode read/write
2: User mode read 3: User mode read/write
4: Reserved 5: Supervisor mode read only
6: Supervisor/user read 7: Supervisor/user read
XN: No execute P: ECC enabled nG: Not-Global
S: Shared T: 'TEX' code

Virtual | Physical | Description | Flags
address | address | |
----------+----------+---------------+----------------------
4fc03000 | aa600000 | Extended (4K) | AP=3 T=2 XN
91900000 | aa600000 | 1MB section | AP=1 T=2
b1900000 | aa600000 | 1MB section | AP=1 T=2

but i don't see line like this

mmutrace 0255e9b8: e7e7130b(strb) 4f669b00 00000001 (00000000)

only like

mem IRQS(0) 94e00000=00010000 (00010000)

i type nledset command to play with led but

HaRET(2)# nledset 1 1 /activate the vibrator
HaRET(3)# nledset 1 0 /stop it

HaRET(3)# nledset 0 1 /blink orange
HaRET(2)# nledset 0 0 /reactivate the default led

don't know if it can be helpful
[Touch Cruise Android Development] alaamac199:
Hello there guys ..

I think that u should check this like cuz I believe it will be useful :

http://www.htc.com/www/support/android/adp.html

cheers!
[Touch Cruise Android Development] bally3:
Sorry for not posting recently, I've been having a read on haretconsole and how to get some of this gpios info that dzo mentioned.

imfloflo, did the information you posted help at all? which ones did you get if any?

biktor has posted a link to the sapphire (G2) where the system folder has been dumped. This includes wifi, bluetooth etc and may give us a lead on the missing bits we need to complete the kernel.

I dont know how fruitful this will be but if anyones interested, you could try and help us find a complete rom dump of the Sapphire device. :)
[Touch Cruise Android Development] imfloflo:
don't know i tried it but dzo didn't response my lastest post so don't know if you want help i can do some gpios test, we lost everybody on polaris thread :s
[Touch Cruise Android Development] bally3:
Try sending him a pm.. he's a busy man at the best of times but trying to develop for multiple devices must be a strain. As for losing everyone on the thread, thats been happening for a while but we should be grateful that people like exco, biktor and seidler are still doing stuff to support this device.

As mentioned before, the big wait for us seems to be the htc magic and as from the post yesterday from biktor on the kaiser thread it seems theres a good chance we may be able to use some of the drivers/code stuff as well the on screen keyboard. As we arent the only ones eagerly awaiting an osk, this is bound to be worked on as soon as we get our hands on it.

I dont know for sure whether that affects the gpios info that dzo mentioned, ou'll have to ask him - but personally unless told otherwise, I would continue to work on it. I've loaded linux onto my laptop and downloaded haretconsole to play with it. unfortunately I left my usb cable at work so it will have to be tomorrow before I can check whether I can get any of the info you posted.

I would pm dzo first and ask him whether its worth continuing and if the stuff you posted is any good and if we need more, then If he want to continue on this we can try and work together to do it.

I'm happy to arrange with you to be on irc to work on it together and maybe we can grab some other people too.

We're too close to the finish line to give up just yet and we're lucky that there are users like biktor and dzo who are willing to help other devices - something we should all take a lesson from.
[Touch Cruise Android Development] radem205:
I have made a zImage from the git, but it doesn't work for me, but maybe for you it works. It seems that you have to connect your phone with your pc (USB) to let Android boot the first time.

The new zImage have the split screen fix, but as you know I don't know if it works.
[Touch Cruise Android Development] imfloflo:
Just test with this setting in default and with usb plug in all the time.

set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "ppp.username=orange ppp.password=orange mddi.width=312 mddi.height=416 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=1 board-htcvogue.panel_type=1 no_console_suspend"
boot

Bootloader image isn't good.

boot ok

Detecting network ok

But just after when i try to unlock screen with menu button freeze and must soft reset :s

edit 2nde try:

launch it without touching it after 1 minute screen shutdown and the green led too.

i try to send sms on my device with http://www.google.com/intl/fr_fr/latitude/intro.html ^^ but receive it and down't wake up my device and after another 30sec go in sleep mode and can't do anything.

I try plug in plug of usb , all the button nothing :s

But after another moment i presse middle button and wake up device.

Call works but lot of button don't have reaction or strange things with the blue keyboard moving alone:s

i think this build broke all the previous work :s
[Touch Cruise Android Development] cuzzo94:
hi...can this android works on the artemis? please it's important!!!!:confused:
[Touch Cruise Android Development] bally3:
You could try it.. I'll have to look at the artemis specs but if the board is the same it should work.. best thing is to unzip the latest build from here to the root of your storage card, change the mtype to 1723 in the default.txt and run haret. Try mtype 1667 if it doesnt work.

Let me know how you go on. :)
[Touch Cruise Android Development] cuzzo94:
i'm downloading thanks!!! how is the interface? is the cupcake?

sorry for the english i'm italian:)
[Touch Cruise Android Development] cuzzo94:
noooooooooooooooooo.....every time the same error.....it start to load.....write some word and than the screen became black......and start windows....thanks to all......if you'll find something contact me.....(i can't speak very well....i think you can see this XD)....if you write something i'll ask this evening because i have to go.....bye
[Touch Cruise Android Development] imfloflo:
use the edit button plz ;)
[Touch Cruise Android Development] bally3:
If you start a thread in the Artemis forum for this, post up the link to the files, point to the specs (wiki) if there is one then we can take a look at it. pm me when its done.
[Touch Cruise Android Development] cuzzo94:
sorry i don't undestend were to post the link..... now i post it here.... http://xdaforums.com/showthread.php?t=496302
[Touch Cruise Android Development] biktor_gj:
Sorry guys, that zImage from the git is my fault :( I posted the ts osk with the ok key enabled, I think that may be your problem...

Give me two minutes and I'll post a zImage with the OK key remapped. Let's see if it works better...

EDIT: Just compiled a zImage with osk disabled. Do you get the same features you had before?

Rapidshare: http://rapidshare.com/files/212611386/zImage

PS: Artemis has a different cpu (omap), nothing of the work at Polaris, Vogue, Kaiser or Nike is going to work for it. Maybe you're more lucky at elf forums, or at wizard. Linwizard project, if it's still alive, may have the resources you need. Google it and you'll find the sourceforge project :)
[Touch Cruise Android Development] excogitation:
Go away.

No seriously ... the Artemis has an Omap 850 CPU in contrast to MSM7200 running in the devices talked about here.

So this kernel will not run on your device. (period)

important ... let me tell you what's important:

sustainability. peace. health. friends. family.
[Touch Cruise Android Development] imfloflo:
:o rapidshare for a zimage :s

Just test it with the same default.txt

Result:

ps: Hey Exco nice to see you back
[Touch Cruise Android Development] biktor_gj:
Hey just a stupid question. Where does it freeze, on haret? or on the kernel?

If it's on the kernel, it stucks on the line where it shows some mmc data or something like that?

And if it's something over there, have you tried having the usb cable connected to the phone at the time of boot? Because I'm facing that problem since the "initial usb work" commit and maybe that's what's causing you problems, more than the osk wich is the version I posted before on this forum, that was ugly, but didn't freeze :)

I've been checking the code and don't find another reason why it shouldn't boot... but please let me know so I can check further!

Regards
[Touch Cruise Android Development] imfloflo:
It freeze just when i launch haret, i see the blue progression bar and after the screen goes black and i didn't see anything more the screen freeze beore, not even tux or one line of code :s

I have read about the usb plug in to boot, and i keep my usb plug

edit just try with fresh package from dzo but nothing more :s

What is your default.txt settings?
[Touch Cruise Android Development] biktor_gj:
This is strange. Polaris kernels have always worked for the nike, and they still do, that's why I asked, it makes no sense for me... Anyway, here you've got a bootkit with my default.txt and one of my latest kernel.

http://rapidshare.com/files/211389157/Bootkit_03_20_2k9.rar

And another kernel that works for nike with charging:

http://rapidshare.com/files/212575243/zImage

Change the mtype to 1723 on default.txt to test the polaris kernel, or leave it as 1724 to see if nike's mtype works for you (it should, btw, exco has used it to try some things)

By the time of this writing 70 people from nike forum has downloaded it with no problem...

Unless proc_comm_wince is messing up don't know what happens...

EDIT: Attached my default.txt, it has mtype set to 1724, so change accordingly for polaris, but please use it to test if it works with nike code first
[Touch Cruise Android Development] imfloflo:
I'm @work so i can't go to rapidshare, thank to the proxy :s.

I'll test it when i come back to home or if somebody can upload it on mediafire it will be nice :)
[Touch Cruise Android Development] 1337hium:
Bootkit

http://www.mediafire.com/file/zni2my4f4wy/Bootkit_03_20_2k9.rar

zImage

http://www.mediafire.com/file/zmmo4zgzlm0/zImage
[Touch Cruise Android Development] biktor_gj:
zImage only:

2Shared: http://www.2shared.com/file/5163344/4e3e262f/zImage.html

DepositFiles: http://depositfiles.com/files/rb31z7hko
[Touch Cruise Android Development] radem205:
With my latest zimage (http://xdaforums.com/showpost.php?p=3505597&postcount=1015) I'm able to boot Android, but all the keys aren't working (mtype 1723).

I will try your zimage now.

Edit: With your zimage and default.txt (Nike one) I'm able to boot, but also without the keys working. Now I get a second led which blinks blue, orange and green. And it seems Android boots in safemode, is that right?

It seems the reset button isn't working anymore, so I have to reset by replacing the battery.

When I plugged out the USB cable, the keys are working (not registered good, but it works)
[Touch Cruise Android Development] imfloflo:
@radem205 have you change the mtype to 1723 for having the mapping key ?
[Touch Cruise Android Development] radem205:
When I use mtype 1723 Haret hangs when the bar is fully loaded :s
[Touch Cruise Android Development] biktor_gj:
I think Im starting to get what's going on. Seems like irq gets stucked with usb for you guys. Give me an hour and I will try to get usb disabled, then you tell me how it goes.

About the nike mtype, it's normal that keypad doesn't work and the leds do strange things, but at least it boots, and that's good, I was starting to freak out... And the service mode, android thinks you're booting with some keys pressed, no big deal since nike keypad conflict with polaris hardware in different places :)
[Touch Cruise Android Development] imfloflo:
@radem205 i have exactly this same bug with the 2 lastest zImage from @biktor_gj

@biktor_gj great find, if you want some gpios irq i can try to find them with haretconsole but not until 18h
[Touch Cruise Android Development] biktor_gj:
Ok, I've posted it on 2shared, I hope you can take it from there (don't have account on mediafire)

I have disabled usb, let me know what it does!

http://www.2shared.com/file/5163708/24ed07dc/zImage.html
[Touch Cruise Android Development] radem205:
Thank you Biktor! But when I use your new zimage with default.txt (nike one) and change the mtype to 1723, it doesn't boot (Haret also hangs).

When I use my zimage with mtype 1723 I can boot but the keys are messed up (a lot of keys aren't working).
[Touch Cruise Android Development] biktor_gj:
radem205, I've sent you a pm. I'm reverting all the changes I've done to the git, but I'm not sure if it has something to do with me, and I need to test out with someone who has a polaris...
[Touch Cruise Android Development] imfloflo:
@biktor_gj yes 2shared is ok for me so i'll test your lastest zImage with your bootkit package

and give it feedback (previous download give me a corrupt archive, so download again - i like FT/Orange Proxy at work :( -)
[Touch Cruise Android Development] biktor_gj:
I think radem and I found the problem, but it's going to take a while to fix it as I have quite a lot of things to redo, I expect to post a test zimage in a few hours so you can test if things are working again.

In case you're curious, it seems like it's not a good idea to mix proc_comm and proc_comm_wince. I still don't know why it behaves this way only on the polaris, but hey, at least I found the problem ;)
[Touch Cruise Android Development] imfloflo:
Download your package, your lastest zImage, change mtype to 1723 and set RAMSIZE to 0x08000000 but always freeze at the end of haret boot :s

What do you need to fix this problem?
[Touch Cruise Android Development] biktor_gj:
I made another kernel (not what is posted here) with proc_comm_wince removed from the build, and it booted on first try with radem's polaris, so it's that what was messing up. The problem is proc_comm_wince is what nike uses for microphone routing on calls, so it's not easy to remove it without breaking nike too. I will make some changes so proc_comm_wince only works for nike (as nobody else is using it for anything) and post back with another image so you can test it out
[Touch Cruise Android Development] imfloflo:
Don't need to remove it just use the ishtcnike /ishtcpolaris function to have 2 different part of code, no ?
[Touch Cruise Android Development] biktor_gj:
No worries, it seems like it was the ts driver, wich sometimes let the phone boot, and sometimes didnt. It should be fixed now. Changes are on the git, and you have a test kernel here: http://rapidshare.com/files/212999799/zImage

There's no on screen keyboard though.

Regards!
[Touch Cruise Android Development] imfloflo:
@bikto_gj thanks the lastest zImage boot with your previous package little bit long but hope it just the first time,

the bootlogo is not align but think it cause to the different value then 320*240.

The led just stay orange( usb charging at the boot) for a while and after screen turn off and wake up stay off not blink in red like under winmo.

No more split screen bug at wake up :) very apreciate

Call/sms test and work.

the camera button doesn't turn screen anymore
[Touch Cruise Android Development] Scalap:
i trying it as soon as i come back home.
[Touch Cruise Android Development] excogitation:
Without pm.sleep_mode it just blacks the screen out (while showing some various colours) - don't really know if that's important - but wasn't like this with earlier kernels.

Tried all board-htcpolaris_paneltype settings (1-3) w/wo USB connected.

With pm.sleep_mode=0 it boots a bit further till it hangs at mmcblk... (haven't tried other settings).
[Touch Cruise Android Development] imfloflo:
The blue OSK isn't present in the lastest zImage? cause when i push the middle button i don't see anything
[Touch Cruise Android Development] radem205:
When you have read the post of Biktor carefully, he said that there is no osk available yet.

@Exco: You have to connect your phone with your pc using a USB cable everytime you boot. Dzo is working on it to fix this problem.
[Touch Cruise Android Development] imfloflo:
radem205

oh yeah right so we have a working version but without anykeyboard too bad :s.

On some dzo previous release i remember there was the "cupcake" keyboard where the hell is it ?:)
[Touch Cruise Android Development] biktor_gj:
That was when we were using cupcake images, and not the g1 sdk images. You can get them on dzo's site: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

Try withe 23-02 or 21-02, I think newer images are all from the sdk. Note they might have other bugs you probably don't have on newer images..
[Touch Cruise Android Development] imfloflo:
Yeah yeah i know but i tough there was the 1.5 SDK release why don't we use it ?
[Touch Cruise Android Development] craigad:
Been away for a while and although not qualified to contribute, i have been following with keen interest until about 6 weeks ago.

Is it true to say that we are waiting for the release of the Magic before we can get both the OSK and all the google service functions in one release, i.e. cupcake?

/craigad
[Touch Cruise Android Development] elmot:
so its been quiet here for a while... keep on the work whit this!

*using my whip* *shhpish*
[Touch Cruise Android Development] bally3:
I appreciate its a lot of donkey work developing is but whipping.. sheesh! :p

Seriously though, patience.. all will come good in the end.. though my search for extra devs has been less fruitful than Adams attempts to stay away from the forbidden fruits.. dag nabbit! :rolleyes:
[Touch Cruise Android Development] imfloflo:
I hope you have right and we don't lost too many chef on our Polaris forum.

btw : Dzo seems to have made lot of progress with usb and will be release a new version soon :)

btw2 : Everybody is waiting for the HTC G2 to have the cupcake version with keyboard in.Cause on our polaris we don't have keyboard like kaiser and it isn't easy to type text.
[Touch Cruise Android Development] excogitation:
imfloflo - has the split screen issue been resolved with recent kernels?

(board-htcpolaris.panel_type)

Also theres a bugtracker (well has been for some time - but it seems to get used now) for bug reporting (I'd try to confirm before spamming it though).
[Touch Cruise Android Development] radem205:
Yes, splitscreen has been solved with the zimage attached.
[Touch Cruise Android Development] imfloflo:
@Exco yes the split screen has been solved with radem205 zImage, btw good to see you back here are you working on something ?
[Touch Cruise Android Development] excogitation:
do you need to set panel_type?

If I get anything done ... I will of course make it available here.
[Touch Cruise Android Development] imfloflo:
I didn't touch to the default.txt jsut change mtype, ram, and apn that's all. (i use the kaiser one )
[Touch Cruise Android Development] bally3:
I see from the number of pms I've had recently about updates on this project that people are getting worried.

Right now, the best any of us can do is to start hunting for the G2 rom dump when it appears and post it here to see whether we can salvage anything.

I've also put out a request in the testing thread for users to come forward to test a windows naked rom we can recommend but so far only one or two people have come forward so you can volunteer to help with that whilst we wait.

We need more people getting involved.. so come on people! ;)
[Touch Cruise Android Development] adderz91:
Tis such a shame, was looking forward to Android on my Polaris.

Seems most developers have jumped shipped to more interesting devices.

I myself am going to jump ship soon to a Nokia E71, Windows Mobile is driving me insane with its none existent usability and lack of "polish".
[Touch Cruise Android Development] bally3:
Its still very much reality that the project will get completed, but yes, the lack of devs is sad, but also inevitable.

I myself, have passed up two opportunities to upgrade, first to a diamond and then to a G1 as I just dont see the point of putting more money to get a devices that are slightly faster with vga screens that do pretty much the same thing as my beloved Polaris. Its just buying into the very reason that companies like htc dont bother about customer service (re: 3d driver) - they know that they can dangle the next shiny device in front of the ever-hungry consumer of their devices and all is forgiven and forgotton again - take a look at the newer msm720x devices - new device, same problems. We live in a world of disposable consumerism and the sad thing is we actually think its a good way to be as we've been programed to think it.

Besides, the idea of making Android work on our devices and giving it a new lease of life really makes me tick - its exactly what these companies wont want to see happen - it makes the consumer think twice about whether they need to upgrade! ;)
[Touch Cruise Android Development] imfloflo:
Totally agre with you bally3.

BTW have you got news from rogro82?