yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] biktor_gj:
@Radem: On the kernel is done automatically, it should be working fine. Anyway, the way you can check it out, is searching for a line like this on dmesg:

msm_sleep(): exit power collapse %ld

Instead of %ld it should say the frequency (400000000 hz) it has restored after coming back from power collapse, so, what you should do, is boot android, let it suspend, wait for some minutes (just in case), and after waking up, connect through the usb, connect to telnet and after login, run dmesg, or dmesg | more and find this line. I can patch it manually for a fixed speed, but it's better if it handles on its own (for compatibilty reasons)

@Marcelkordek: About the reboots on opengl, it shouldn't do that. Maybe first try with clean files (remember dzo's last system.img). It could be the radio too, but if it was working before I don't think so. About the audio, try plugging the headset during boot, and then play some music, does it work that way? Is the rest of the people having issues with audio lately?

EDIT: Forgot to talk about the wheel:

The input events are disabled, because I still have to patch it. On dmesg, you get some output like this whenever you touch the wheel: Polaris Wheel: Direction X

On normal move, it goes like this (no matter the direction):

Polaris Wheel: Direction B

Polaris Wheel: Direction C

Polaris Wheel: Direction B

Polaris Wheel: Direction C

Polaris Wheel: Direction B

I would need to know wich direction it takes when you move one way and then change direction... can somebody provide me with that info so you can start using the wheel?

Regards!
[Touch Cruise Android Development] briggs81:
So for the people having success with this, what packages are you using?

I seem to be getting random results, all the time. Sometimes it just gives me a very snowy screen, other times it Android does boot up, just can't seem to get it to use my internet connection.
[Touch Cruise Android Development] imfloflo:
I touhgt i had put the gpio code for the wheel long time ago, and exco too.

Can someone make a package with working configuration 1.1 and another with f00bar 1.5 ( VK include) that will be easilier for people who don't read the thread everyday.

cause having a zImage from you + others files from dzo + others from f00bar they will be lost.

BTW good job what you need todo now Wifi ?gps ?camera?
[Touch Cruise Android Development] briggs81:
This would be really helpful as I am sure most of my questions, at least, are because i am using something that may not be the most up to date, and I'm not familar with what can be interchanged with other peoples work and what can't be.
[Touch Cruise Android Development] imfloflo:
For the moment the how to do :

-remove all the previous android files of the SD

-download the lastest DZO's package (here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D)

-override the system.img by this one system-gpu.img

-override the zImage by the lastest avalaible in this thread.(can be one's from biktor_gj, radem205,exco, rogro82)

-use this default.txt

#Polaris
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz

set cmdline "mddi.width=312 mddi.height=416 pm.sleep_mode=0 board-htcpolaris.panel_type=0"
boot
[Touch Cruise Android Development] radem205:
Thanks for your reply. The red button works now as a power off/on button. When I press the red button the screen goes into sleep mode :s

I will look at the wheel soon, so you can working on it. Good job!
[Touch Cruise Android Development] miazza:
Is this new release automatically connecting to the web or it maintains the DZO initrd.gz that does not connect automatically ?

I would like to avoid another very big bill from VODAF*NE.

I do suggest to have always a version (as option) not connecting automatically. I imagin that if I maintain my initrd.gz it will work as before.

Thanks

miazza
[Touch Cruise Android Development] imfloflo:
I think dzo have disable auto connection in all initrd he release.
[Touch Cruise Android Development] miazza:
This is a good info.

Thanks

miazza
[Touch Cruise Android Development] briggs81:
Now that I am somewhat up to speed I will try experimenting with other zImages.

So far, no luck with biktors. It's slow response etc, as already reported. Have tried exco's also and that one for me just seems to crash at the haret booting screen.. no "Go Go Go" !
[Touch Cruise Android Development] Michel82:
Tnx imfloflo. Running the f00bar 1.5SDK with keyboard now and installed biktors latest zImage (with the GPU changes). But it's extremely slow.... any1 knows if this is anything specific?
[Touch Cruise Android Development] Michel82:
Seems to be biktor's latest zImage. Replaced it with an older one and works like a jiffy.
[Touch Cruise Android Development] masterorg:
Thanks for the report.

Do you have some experience with the battery drain?

I've tried last image on the other thread but the battery drain was very fast.
[Touch Cruise Android Development] briggs81:
If I wanted to try f00bars files, what specific ones would I use from his package?
[Touch Cruise Android Development] biktor_gj:
In theory, my last kernel should work well with the latest system.img from dzo. Please test if with that it's working fine or is also extremely slow, because the only change from the git sources is the hardware 3d acceleration, and it shouldn't make it slower... or is this an issue that's been here for a while?
[Touch Cruise Android Development] radem205:
The issue was also before the new zimage. Dzo said it was caused by a wrong speed of the cpu clock after power collapse (see http://xdaforums.com/showpost.php?p=3662443&postcount=1154). Exco has changed the speed and after it the problem was gone.
[Touch Cruise Android Development] excogitation:
I only forced it to 400MHz as dzo proposed - but I have no idea how to fix it properly. Also this problem appeared a few builds ago (no issues before).

Thanks biktor, for working on Polaris stuff even though you don't have one.
[Touch Cruise Android Development] biktor_gj:
Ok, I patched the cpu clock thing, let's see how this works!

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

Maybe you want to try OpenGL with Qualcomm's benchmark application too:

http://it029000.massey.ac.nz/vogue/files/com.qualcomm.qx.neocore.apk

On Nike I have 17- 17.2 fps depending on system status... how does it do here?
[Touch Cruise Android Development] imfloflo:
Ok thanks bikto_gj.

Which files are you using ?

lastest dzo zip+ system-gpu-img+your zImage?

and if someone could upload it directly in the forum thanks in advance :$)
[Touch Cruise Android Development] radem205:
Your latest zimage is working great! So it has to do with the speed of the CPU clock?

I get 17.9 fps after running the benchmark.

BTW: The red button behaves as a power button (on / off)

Edit: The second boot is again very slow :s, also in Android everything is very slow
[Touch Cruise Android Development] biktor_gj:
So you have better 3d performance! I wonder why is my phone so special that nothing works completely for me but it does for everybody else...

About the red button... that's the normal behaviour of the END key on Android :( If you have an ongoing call, the red button acts as "end call". If the phone is idle, it acts as suspend, and if you hold it, it gives you the power down menu. On the Nike I mapped the end key to the power button, and use red key as "back". I can put whatever you want on that key, so just tell me how you want it :)

About the audio... with or without headset? or it doesn't matter? It can be two different things, depending on the headset behaviour it will be one or the other... so please just tell me so and I'll fix it (it's me who broke support for the polaris when rearranging vogue-hw, and it's easy to fix)

Regards!

EDIT: Does this fix the audio? http://rapidshare.com/files/226666716/zImage

Also, when it goes slow... is like a 15-20 second lag between touchscreen tap and the phone actually doing something? does the console part of the boot process appear more slowly too or is it just when you're on Android?
[Touch Cruise Android Development] imfloflo:
I think the red button should be the back button , like we have the power button to have the power function.
[Touch Cruise Android Development] radem205:
When I enable audio in WM, audio is working on Android. I'm sorry for this mistake!

Also the bootprocess is going very slow (stuttering). And when I tap on an icon it takes very long until android reacts. So everything is going very slow. But it's from time to time, so sometimes the speed is ok...
[Touch Cruise Android Development] dzo:
On Vogue I get 25.5 fps and slightly less on kaiser so there is something wrong somewhere, are you using the vogue-mddi client with vsync. perhaps the vsync isn't working. Why don't you create another branch on ltg with your changes and I can have a look at what's different.
[Touch Cruise Android Development] briggs81:
I am using dzo's latest and the system gpu img and biktors latest zImage and it is very choppy for me too.
[Touch Cruise Android Development] Michel82:
It would be great if all releases could be converted to the latest SDK 1.5. Would it be difficult to merge the latest 1.5 changes into you releases DZO? The keyboard is kinda mandatory for us polaris users.
[Touch Cruise Android Development] imfloflo:
f00bar have 1.5 version working well on polaris.

Can someone make new package for the polaris and upload it to have a wiki up to date.
[Touch Cruise Android Development] radem205:
Indeed foobar has the new SDK 1.5, BUT without the very good changes made by dzo (like the new GPU).
[Touch Cruise Android Development] imfloflo:
Yeah but i read DZO try 1.5 this morning maybe we will have a surprise soon
[Touch Cruise Android Development] biktor_gj:
Hi, first sorry for the delay, I've been trying to find out why it's not working correctly but didn't find it. Truth is, I simply ripped off the code from the kaiser and copied it to the nike and the polaris. I don't really know wich mddi client is using each, but I guess we're using the same the Kaiser is using, as all the board files come from there and we've only patched some things to make it work with these phones.

Anyway, as I didn't want to screw anything on the git, I just did a diff so you can take a look. if you need anything just tell me so and I'll do it as fast as I can :)

Regards!

Forgot to say, before the last commit, it seemed like it was working faster (at least sprite text reported 22ms/frame, now it reports 37-45 ms/f), so we may be using vogue's mddi, and those last changes screwed it up?
[Touch Cruise Android Development] dzo:
Can you try reverting the changes I made to acpuclk_set_rate in clock-7x00.c so it's the same as in a0941b3ba3894b3510e52bea03eaf7f5e7e47e1b.

Also what frame rate do you get if you boot with mddi_client_vogue.vsync=0 in default.txt.

Hope that helps,

Martin
[Touch Cruise Android Development] biktor_gj:
Just a little update:

If I disable vogue's vsync I get a lower but more stable framerate (vsync=1 -> 37-45 ms/f, vsync=0 -> 44 stable)

Also, if I replace acpu clock values everything goes slower, so I have started reverting manually your last commit, and found if I replace, on hw3d.c this line:

IRQF_TRIGGER_RISING, "hw3d", 0);

for this:

IRQF_TRIGGER_HIGH, "hw3d", 0);

I get about 20fps, but with corrupt graphics (images move like overlapping on the bottom part of the screen)

Still working on it!
[Touch Cruise Android Development] dzo:
That's because it doesn't wait for the frame to be drawn before displaying it so it obviously goes faster but this isn't what you want. It took me a whole day to figure out the interrupt trigger was wrong. How about the acpuclk_set_rate changes, can you post a haretdump of the polaris clock regions:

pdump 0xc0100100 0x20

and

pdump 0xa8600000 0x200

p.s. this is what vogue looks like:

HaRET(25)# pdump 0xa8600000 0x200
a8600000 | 2017fe27 001881d8 00000011 00000019 | '.. ............
a8600010 | 00000000 00000015 00000000 00108000 | ................
a8600020 | 00000000 00001000 00001a80 00001a80 | ................
a8600030 | 00001004 00000000 00000018 000dfe7f | ................
a8600040 | fe8c404f 0001fff3 fff4005c 0000080c | O@......\.......
a8600050 | 00000400 0003ff39 f8fa0b60 0659cfff | ....9...`.....Y.
a8600060 | d658014c 00000a00 0001fff3 fff4495c | L.X.........\I..
a8600070 | 0001ffe7 ffe8095c 00000000 00000000 | ....\...........
a8600080 | 00000a00 00004000 00000400 00000a51 | .....@......Q...
a8600090 | 00001000 00141554 0001ffb4 ffb50040 | ....T.......@...
a86000a0 | 0001ffef fff00b69 0019f3ff f418005c | ....i.......\...
a86000b0 | 00000a00 00000000 0001fff7 fff8005a | ............Z...
a86000c0 | 03070131 00002a79 00000000 00000014 | 1...y*..........
a86000d0 | 00000000 00000000 00000000 00000000 | ................
a86000e0 | 0000000c 00000000 00000fff 00000fff | ................
a86000f0 | 00000000 00ffffff 00ffffff 0000ffff | ................
a8600100 | dc7d7815 006c0c22 00000000 00008000 | .x}.".l.........
a8600110 | 00008000 00000000 00000000 00000000 | ................
a8600120 | 00000000 00000000 00000000 00000000 | ................
a8600130 | 00000000 00000000 00000000 00000000 | ................
a8600140 | 00000000 00000000 00000000 00000000 | ................
a8600150 | 00000000 00000000 00000000 00000000 | ................
a8600160 | 00000000 00000000 00000000 00000000 | ................
a8600170 | 00000000 00000000 00000000 00000000 | ................
a8600180 | 00000000 00000000 00000000 00000000 | ................
a8600190 | 00000000 00000000 00000000 00000000 | ................
a86001a0 | 00000000 00000000 00000000 00000000 | ................
a86001b0 | 00000000 00000000 00000000 00000000 | ................
a86001c0 | 00000000 00000000 00000000 00000000 | ................
a86001d0 | 00000000 00000000 00000000 00000000 | ................
a86001e0 | 00000000 00000000 00000000 00000000 | ................
a86001f0 | 00000000 00000000 00000000 00000000 | ................
HaRET(26)# pdump 0xc0100100 0x40
c0100100 | 00001100 00000006 00000000 00000000 | ................
c0100110 | 00000007 0000007f 00000000 00000000 | ................
c0100120 | 00000000 00000000 00000000 00000000 | ................
c0100130 | 00000000 00000000 00000000 00000000 | ................

Martin
[Touch Cruise Android Development] excogitation:
HaRET(1)# pdump 0xc0100100 0x20
c0100100 | 00001100 00000006 00000000 00000000 | ................
c0100110 | 00000007 0000007f 00000000 00000000 | ................
HaRET(2)# pdump 0xa8600000 0x200
a8600000 | 2015fcaf 001b8350 00000000 00000011 | ... P...........
a8600010 | 00000001 00000055 00000000 00118000 | ....U...........
a8600020 | 00000000 00001000 00001a80 00001a80 | ................
a8600030 | 00001004 00000000 00000040 000dfe7f | ........@.......
a8600040 | fe8c6149 0004fe88 fe8c0049 00000814 | Ia......I.......
a8600050 | 00000400 0003f42f f8fa0b60 0145e7ff | ..../...`.....E.
a8600060 | e9440144 00000a00 0001fff5 fff64044 | D.D.........D@..
a8600070 | 0001ff87 ff880044 00000001 00000000 | ....D...........
a8600080 | 00000a00 00004a80 00000400 00000e2c | .....J......,...
a8600090 | 00001000 00141554 0001ffb4 ffb50040 | ....T.......@...
a86000a0 | 0001fff5 fff60b79 0003ff9b ff9e0078 | ....y.......x...
a86000b0 | 00000a00 00000000 00e1f7ff f8e00044 | ............D...
a86000c0 | 00180d01 00000079 0001fffa fffb0049 | ....y.......I...
a86000d0 | 00000000 00000000 00000000 00000000 | ................
a86000e0 | 0000000c 00000000 00000fff 00000fff | ................
a86000f0 | 00000000 00ffffff 00ffffff 0000ffff | ................
a8600100 | dc7d7a15 00600cdf 00000000 00008000 | .z}...`.........
a8600110 | 00008000 00000000 00000000 00000000 | ................
a8600120 | 00000000 00000000 00000000 00000000 | ................
a8600130 | 00000000 00000000 00000000 00000000 | ................
a8600140 | 00000000 00000000 00000000 00000000 | ................
a8600150 | 00000000 00000000 00000000 00000000 | ................
a8600160 | 00000000 00000000 00000000 00000000 | ................
a8600170 | 00000000 00000000 00000000 00000000 | ................
a8600180 | 00000000 00000000 00000000 00000000 | ................
a8600190 | 00000000 00000000 00000000 00000000 | ................
a86001a0 | 00000000 00000000 00000000 00000000 | ................
a86001b0 | 00000000 00000000 00000000 00000000 | ................
a86001c0 | 00000000 00000000 00000000 00000000 | ................
a86001d0 | 00000000 00000000 00000000 00000000 | ................
a86001e0 | 00000000 00000000 00000000 00000000 | ................
a86001f0 | 00000000 00000000 00000000 00000000 | ................
[Touch Cruise Android Development] dzo:
The only thing I can see that may make a difference is the value at a860008c, that's the clock for the panel, try changing it to 0xa51, but perhaps your panel doesn't run that fast.
[Touch Cruise Android Development] dzo:
Just tried this on kaiser and it seems to work. Can you patch mddi.c like this and see if it helps:

diff --git a/drivers/video/msm/mddi.c b/drivers/video/msm/mddi.c
index 5652e5e..03a3883 100644
--- a/drivers/video/msm/mddi.c
+++ b/drivers/video/msm/mddi.c
@@ -551,6 +551,8 @@ static int __init mddi_init(struct mddi_info *mddi, const char *name,
if (pd->has_vsync_irq)
mddi->flags |= FLAG_HAS_VSYNC_IRQ;
}
+ // set up pmdh clock
+ writel(0xa51,MSM_CLK_CTL_BASE+0x8c);
/*
mddi->clk = clk_get(&mddi->panel_pdev.dev, clk_name);
if (IS_ERR(mddi->clk)) {
[Touch Cruise Android Development] imfloflo:
HaRET(1)# pdump 0xc0100100 0x20
c0100100 | 00001100 00000006 00000000 00000000 | ................
c0100110 | 00000007 0000007f 00000000 00000000 | ................

HaRET(1)# pdump 0xa8600000 0x200
a8600000 | 2015fc2f 001b83d0 00000000 00000011 | /.. ............
a8600010 | 00000001 00000055 00000000 00118000 | ....U...........
a8600020 | 00000000 00001000 00001a80 00001a80 | ................
a8600030 | 00001004 00000000 00000040 000dfe7f | ........@.......
a8600040 | fe8c604f 0004fe88 fe8c0049 00000814 | O`......I.......
a8600050 | 00000400 0003fb37 f8fa0b60 0145e7ff | ....7...`.....E.
a8600060 | e9440144 00000a00 0001fff5 fff64044 | D.D.........D@..
a8600070 | 0001ff87 ff880044 00000001 00000000 | ....D...........
a8600080 | 00000a00 00004a80 00000400 00000e2c | .....J......,...
a8600090 | 00001000 00141554 0001ffb4 ffb50040 | ....T.......@...
a86000a0 | 0001fff5 fff60079 0001ffef fff00069 | ....y.......i...
a86000b0 | 00000a00 00000000 00e1f7ff f8e00044 | ............D...
a86000c0 | 00180d01 00002a79 0001fffa fffb0049 | ....y*......I...
a86000d0 | 00000000 00000000 00000000 00000000 | ................
a86000e0 | 0000000c 00000000 00000fff 00000fff | ................
a86000f0 | 00000000 00ffffff 00ffffff 0000ffff | ................
a8600100 | dc7d7a17 00600cd3 00000000 00008000 | .z}...`.........
a8600110 | 00008000 00000000 00000000 00000000 | ................
a8600120 | 00000000 00000000 00000000 00000000 | ................
a8600130 | 00000000 00000000 00000000 00000000 | ................
a8600140 | 00000000 00000000 00000000 00000000 | ................
a8600150 | 00000000 00000000 00000000 00000000 | ................
a8600160 | 00000000 00000000 00000000 00000000 | ................
a8600170 | 00000000 00000000 00000000 00000000 | ................
a8600180 | 00000000 00000000 00000000 00000000 | ................
a8600190 | 00000000 00000000 00000000 00000000 | ................
a86001a0 | 00000000 00000000 00000000 00000000 | ................
a86001b0 | 00000000 00000000 00000000 00000000 | ................
a86001c0 | 00000000 00000000 00000000 00000000 | ................
a86001d0 | 00000000 00000000 00000000 00000000 | ................
a86001e0 | 00000000 00000000 00000000 00000000 | ................
a86001f0 | 00000000 00000000 00000000 00000000 | ................
HaRET(3)# pdump 0xc0100100 0x40
c0100100 | 00001100 00000006 00000000 00000000 | ................
c0100110 | 00000007 0000007f 00000000 00000000 | ................
c0100120 | 00000000 00000000 00000000 00000000 | ................
c0100130 | 00000000 00000000 00000000 00000000 | ................

I don't have the same result on my polaris
[Touch Cruise Android Development] radem205:
Just an addition to the problem: sometimes I get, after the Haret console, a colored screen (pink, green, white) and the phone hangs. So no terminal displayed at all.
[Touch Cruise Android Development] biktor_gj:
Results on the HTC Nike:

Spire Text: 17-23 ms / frame (~20 ms less per frame)

Qualcomm's benchmarking app: 17.5 fps (~0,5 fps faster than before)

So, it's working better :) The results show a big speed increase when rendering small objects (2x speed), and a slight better performance when rendering full screen. Good enough for me :)

Polaris users, please test this kernel, let's see how this works for you:

Rapidshare: http://rapidshare.com/files/227835391/zImage
[Touch Cruise Android Development] radem205:
never mind
[Touch Cruise Android Development] radem205:
What I noticed with the new zimage:

- Two times booted: No problems with hanging phone (edit: third boot everything is going very slow again :( )

- I get an framerate of 17.6 fps

@Biktor: Do you have time to figure something out and test things on yahoo messenger? So maybe you can solve this easily?
[Touch Cruise Android Development] imfloflo:
I'm with the f00bar 1.5 version ,all working fine except :

The boot sequence with the tux is now very clear and readable :) , the new bootlogo "android" is nice.

I don't like the red button with this function i prefere when it was the back button.

The keyboard backlight always stay on :s.

The vibrator stay block must push red button twice to stop it.

This version doesn't find my operator name it always says "Android" instead of "orange FR"
[Touch Cruise Android Development] radem205:
Do you have problems booting Android? (goes very slow for example?)

If you haven't any problem, which zimage are you using?
[Touch Cruise Android Development] biktor_gj:
Didn't notice I reverted polaris keypad too (I had already fixed it)

Back button to red key: http://rapidshare.com/files/227870237/zImage
[Touch Cruise Android Development] imfloflo:
No probleme booting, i use dzo lastest package + lastest biktor zImage + f00bars system.img for having 1.5sdk.

@biktor_gj nice the lastest have good function on red button but still have the alwasy keyboard light on and the vibrator bug do you know were it can from ?

how can i install com.qualcomm.qx.neocore.apk cause in terminal emulator i don't successs to type "su" and try "start com.qualcomm.qx.neocore.apk " "install com.qualcomm.qx.neocore.apk "
[Touch Cruise Android Development] radem205:
Are you able to give me your whole package (all files) with an upload program (like rapidshare)? That would be great!!
[Touch Cruise Android Development] radem205:
Neocore isn't working with foobar's system.img. You have to use the system-gpu.img from dzo (http://it029000.massey.ac.nz/vogue/files/?C=M;O=D)

When you place the .apk in the folder "AndroidApps" it automatically installs.
[Touch Cruise Android Development] imfloflo:
Ok i mixed some f00bar and dzo's files i will retry i named my folder "apps" and not "AndroidApps" too bad ^^.

edit ok so my device doesn't support qualcomm accelerated graphics so i will wait until f00bar port it to the 1.5 system.img cause VK is really a must to have for our polaris
[Touch Cruise Android Development] joannerve:
where I can download android 1.5?
[Touch Cruise Android Development] biktor_gj:
imfloflo, just so you know, I fixed the keypad backlight problem, and dzo fixed the vibration hold, so all those things should be working fine on last releases.

On the other hand, all of you who are having problems with the phone responding too slow, disable vogue's mddi client vsync function from kernel's cmdline on default.txt and you should be good to go:

mddi_client_vogue.vsync=0
[Touch Cruise Android Development] radem205:
In your latest zimage (biktor) the vibration isn't working well. I think it has to do with the system.img foobar uses in his 1.5 version.
[Touch Cruise Android Development] Michel82:
I can't see the forest for the trees. Which combination of kernel, zImage, default.txt (resolution, panel_type?) settings is currently the best for our polaris?! Can someone make me a package?