yashsingh1/xdaforums huggingface dataset:
[Touch Diamond2, Pure Android Development] Richard321:
i have a topa 100

and i would love to try android

i hope someone would find a solution fast

Greetings
[Touch Diamond2, Pure Android Development] artukas613:
Hi,

Same problem, TOPA100. Maybe, there is some one with new topa100 and working android. If we can find working one, maybe we will figure it out what is wrong.

:)
[Touch Diamond2, Pure Android Development] coolbluesea:
Yes, I get same bug . mabye only run on the TD2 before 2010 edition.
[Touch Diamond2, Pure Android Development] player911:
Have you guys tried to format your SD cards and try again? I was running into a similar problem where it wouldn't boot into Android. I formatted my Sd card to FAT32 and ONLY copied the Android folder over to it.

Then it was booting perfectly.
[Touch Diamond2, Pure Android Development] Spitfire128:
I think at least three of us have tried so. Didn't work.
[Touch Diamond2, Pure Android Development] muta0998:
Hello!could you tell me ,how to fine my Topaz "mytype"????

Thank you!!!
[Touch Diamond2, Pure Android Development] Spitfire128:
If you're asking how to see if your Topaz is a Topa100 or Topa300 or whatever else versions may exist, it says so somewhere under the battery.
[Touch Diamond2, Pure Android Development] kenzo82:
I have the same problem like you guys. Android 2.0.1 not working on my topaz too. Just rebooted back to WM.
[Touch Diamond2, Pure Android Development] mweirauch:
Thanks! You can use the autobuild service packages though, as the changes have been integrated.
[Touch Diamond2, Pure Android Development] mweirauch:
When does it reboot? Are you sure everything is setup correctly? Have you tried a recent autobuildservice image?

EDIT: Seems to have been a false report, as another thread indicates him running android.
[Touch Diamond2, Pure Android Development] mweirauch:
topa210 broken

It seems the monodie fix for newer topa100 broke topa210 :/

@topa100 users, don't test this ;)

@topa210 users, please test the kernel and provide the dmesg output. (e.g. via "adb shell dmesg")

I am interessted in the very first lines of the dmesg output with "parse_tag_monodie: ATAG_MEM ...". I wouldn't mind if you attach the full dmesg output (via attachment would be ok) so I can see the full log as well for some LCD panel stuff to verify ;)

EDIT: fixed package ;)

EDIT2: removed attachment
[Touch Diamond2, Pure Android Development] TheJokah:
mweirauch which zimage should i try. Are these modules for a certain zimage or will any work?
[Touch Diamond2, Pure Android Development] mweirauch:
Try the one from my post above: linux-msm-topa210-2010-07-18-atag-check.zip

It only contains the zImage. Leave your original modules as is. No matter if they match or not.
[Touch Diamond2, Pure Android Development] TheJokah:
I just unpacked the file and it only had modules, no zimage.
[Touch Diamond2, Pure Android Development] mweirauch:
Ouch! Sorry! I updated the file. You can keep the modules on your device and now just update the zImage from the updated package.
[Touch Diamond2, Pure Android Development] TheJokah:
i just updated my system.ext2 file to rc1 package, will this effect anything?
[Touch Diamond2, Pure Android Development] mweirauch:
No. That should be fine.
[Touch Diamond2, Pure Android Development] bheremans:
I have a topa100 and can't boot with the newest kernel. The last lines on the screen are :

PPP bsd compression module registred
alocated dma bufeer at ffc0b000, dma_addr id 239000

This is before adb connects ..

I can boot fine with the zImage you provided :

With that kernel it continues :

[ 0.000000] Linux version 2.6.27.46-01125-g8d9fee6-dirty (michael@torch) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #12 PREEMPT Sun Jul 18 14:25:24 CEST 2010

[ 0.000000] CPU: ARMv6-compatible processor [4117b362] revision 2 (ARMv6TEJ), cr=00c5387f

[ 0.000000] Machine: HTC Topaz cellphone (Topaz is a silicate mineral of aluminium and fluorine)

[ 0.000000] parse_tag_monodie: ATAG_MEM 0x10000000

[ 0.000000] parse_tag_monodie: mono-die = 0x0

[ 0.000000] fixup: nr_banks = 2

[ 0.000000] fixup: bank0 start=10000000, node=00000000, size=06b00000

[ 0.000000] fixup: bank1 start=20000000, node=00000000, size=05e00000

[ 0.000000] Ignoring unrecognised tag 0x00000000

[ 0.000000] Memory policy: ECC disabled, Data cache writeback

[ 0.000000] On node 0 totalpages: 51456

[ 0.000000] free_area_init_node: node 0, pgdat c030b8cc, node_mem_map c08fc000

[ 0.000000] DMA zone: 50756 pages, LIFO batch:15

[ 0.000000] PLL0: MODE=00000007 L=0000000c M=00000004 N=00000005 freq=245760000 Hz (245 MHz)

[ 0.000000] CPU0: D VIPT write-back cache

[ 0.000000] CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets

[ 0.000000] CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets

[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 50756

[ 0.000000] Kernel command line: acpuclock.oc_freq_khz=650000 lcd.density=240 msmvkeyb_toggle=off sensor=topaz msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
.....
cut
.....

[ 1.436859] PPP generic driver version 2.4.2

[ 1.437438] PPP Deflate Compression module registered

[ 1.437622] PPP BSD Compression module registered

[ 1.438873] allocated dma buffer at ffc0b000, dma_addr 2523b000

[ 1.439178] read CFG0 = aa5400c0, CFG1 = 8744a

[ 1.439331] CFG0 = e85408c0, CFG1 = 4745e

[ 1.439453] CFG0: cw/page=3 ud_sz=516 ecc_sz=10 spare_sz=0 num_addr_cycles=5

[ 1.439697] NAND_READ_ID = 5501bcec

[ 1.439910] status: c03020

[ 1.440032] nandid: 5501bcec maker ec device bc

[ 1.440185] CFG0: cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=4

[ 1.440368] DEV_CMD1: f00f3000

[ 1.440490] <6>NAND_EBI2_ECC_BUF_CFG: 1ff

[ 1.440643] flash_id: 5501bcec size 20000000

[ 1.441345] usb_probe() io=d6008000, irq=47, dma=ffc0c000(2523c000)

Some other newer kernels generates a kernel panic and then reboots. The kernel from 7/2 boots fine without problems

UPDATE : with usb disconnected at booting it generates a kernel panic but goes beyond the usb probe point .. maybe something with the new battery detecting stuff ?

Bart
[Touch Diamond2, Pure Android Development] bheremans:
Ok was real fast now :-)

just before the kernel panic :

kernel bug at mm/filemap.c 569

unable to handle nullpointer
[Touch Diamond2, Pure Android Development] mweirauch:
^^ This is from my test kernel, right?

Ok, I see the problem. Your device, which is obviously a non-monodie device also reports 0x10000000 which is 256MB. The old topaz - including mine - did report an erroneous value passed from HaRET so that I could dynamically detect monodie (also reporting 256MB) or "old" topa100. But as it seems now, some "other" topa100 with two memory banks seem to correctly report 256MB via HaRET which is the culprit...

ATAG_MEM reported by HaRET seems to be as follows:

topa100 dualdie-old: 0x05100000 (81MB)
topa100 monodie-new: 0x10000000 (256MB)
topa100 dualdie-new: 0x10000000 (256MB) (also topa210?)

I already tried to find some info on how to detect the physical memory info in WinCE so that one could actually pass "more correct" info via HaRET to the linux kernel.

Thanks for testing! Will try to find a solution.
[Touch Diamond2, Pure Android Development] bheremans:
the log provides was from your kernel.

Thx for fixing.

I don't know how old my topaz is (main board was replaced with one from ebay ..)
[Touch Diamond2, Pure Android Development] niall0s:
Thanks for locating and now attempting to fix the bug guys :)
[Touch Diamond2, Pure Android Development] cheesy33:
I have the trouble with my topa200 to, with this new kernel I can boot, but wifi fails.

Now I go back to zImage from July 2nd. All other files are newest. On my first viewing it seems working fine with known problems like sound and camera.

Edit:

I try to use the VPN-Feature (PPTP and L2TP/IPSec) but I get no connection. Can someone help me on this topic?

Greetings

Cheesy
[Touch Diamond2, Pure Android Development] mweirauch:
updated monodie package

As stated in the XDANDROID topaz thread I had to disable the dynamic memory detection and support for monodie topaz as it caused trouble for many more users then it had use.

I am sorry I had to do this step especially as we found a solution on how to support both devices types. Apparently the "hack" doesn't work out for newer dualdie topaz :/

In the meantime I prepared a monodie package which only works on monodie devices: Download here.

You can also use the old package which can be found in the first post, it just misses the battery detection fixes which work better in the package posted above.

@Spitfire128 If you could please update the first post with the link to the updated package? And perhaps, for the time being, alter the thread title to "Pending" or something?

I am looking for a solution.

PS: Don't be irritated by the differing panel behaviour. The above package contains some experimental panel setup code. The colors might be a bit more greyish, but the panel should unblank faster if you wake the device. :D
[Touch Diamond2, Pure Android Development] cheesy33:
Sorry, I want to help, but explain this:

When I start haret.exe from WinMo FileManager, Android boots immediately.

Cheesy
[Touch Diamond2, Pure Android Development] mweirauch:
When you start haret.exe it immedeately starts booting the linux kernel? Never seen this. Usually one presses the "Run" button to do so.

One ususally does start haret on the phone, it then sits there automatically waiting for a connection from your PC. You then start 'haretconsole' from your PC which connects to HaRET which is running on your phone. One can then execute different commands to explore the device.

Information about HaRET and haretconsole can be found here.
[Touch Diamond2, Pure Android Development] MusikMonk:
That would happen with a startup.txt set top boot directly (i.e. simply renaming default.txt to startup.txt).

You probably know that already but I felt that I should post something "useful" in my first post in this section. I don't have much skills (yet :p) in porting Android or dealing with Linux kernel but it certainly interests me, as you can see from the link in my siggy. So I'm planning to try and get involved here as soon as I can, which should be starting next Monday. So... I'm hoping you would welcome me as an apprentice ;)
[Touch Diamond2, Pure Android Development] mweirauch:
Haha, I would rather call myself an apprentice as well then call me an expert. I also just slipped into it and try to get things going ;)

If you wan't to do kernel related work, compile your own + external modules, you should set up a build environment first.
[Touch Diamond2, Pure Android Development] shavenyaknz:
Hi mweirauch

I ran this command but can't find 'OEMAddressTable' in the file, I've attached it in case it can help you.

To get this far I ran Haret on the device, hit listen for connection then on the Pc ran haretconsole and entered the pwf command.

Do I have to boot linux then run the pwf command ?
[Touch Diamond2, Pure Android Development] mweirauch:
Hm. Was your device running WinCE for a long time? Then you won't see it because it starts over at the beginning of the log area when it reaches the end.

Try issueing the command after you booted WinCE. Just WinCE involved. No linux kernel, no android.
[Touch Diamond2, Pure Android Development] mweirauch:
Hi Bart,

thanks for providing your results. They are identical to mine.

Now I could use some info from a topa100 monodie device from somebody else ;)

Thanks,

Michael
[Touch Diamond2, Pure Android Development] mweirauch:
Thanks shavenyaknz. Evaluated OEMAddressTable gives the following result:

Usable Banks:
start=0x10000000 end=0x16f00000 (111m)
start=0x18000000 end=0x20000000 (128m)

Exactly how expected regarding the start offsets. Now I only need to find a way to dynamically find the OEMAddressTable in memory as its offset/location differs. (Within WinCE/HaRET that is.) Have digged the net for ages but couldn't really find a solution on how to do that from userland, yet.

Thanks so far!

Michael
[Touch Diamond2, Pure Android Development] stijnr:
Hi, I've got a T5353 TOPA100, but I don't know if I've got mono- or dualdie. A series of zImages weren't working for me, and I had to revert to linux-msm.201007022233.

Is XDANDROID still not able to use the complete memory banks; does this only apply to mono- or dualdie?

My currently working setup is posted here.
[Touch Diamond2, Pure Android Development] mweirauch:
If the last know version was from 2010-07-02, then you do have a dualdie device. The fix I commited to the repository broke some dualdie devices. You can grab a recent build from the autobuildservice here and use these.
[Touch Diamond2, Pure Android Development] soheil1223:
Question

How Can I know My Topa100 is monodie or dualdie???
[Touch Diamond2, Pure Android Development] mweirauch:
If your device boots the linux kernel from the autobuild service then you don't have a monodie device. If your devices freezes or soft resets right after haret has finished loading the kernel, then it is likely - correct setup assumed - that you've got a monodie device. For the time being you should be using the test kernels posted here which are specifically adjusted for monodie devices. They won't run on regular devices until a proper detection fix is established.
[Touch Diamond2, Pure Android Development] tommy1994:
great,i finally found my d2 is monodie!

cause the build on page1 work for me

also,is the build keep up to date?
[Touch Diamond2, Pure Android Development] mweirauch:
Yes, I try to keep it up to date until the issue is resolved. Allthough the most recent version is here until I find some more time again. :D
[Touch Diamond2, Pure Android Development] kangan_1342:
Tanx all

I Downloaded the package from First Post ... And It worked for me ... fast .. with wireless connection and every thing is ok ... but I want ask you : Is it Danger for my topaz100 ? can this package make any damage to my phone ?

you made me very happy by giving me Android --- please make me very very happy by answer my qustion .... tanx
[Touch Diamond2, Pure Android Development] mweirauch:
As with every modification to your phone which is not coming from the device manufacturer you always carry the risk of breaking your phone. Everything provided here is provided as is and comes with no warranty that nothing breaks.

On the other hand, I've not heard of any devices which broke, yet. ;)
[Touch Diamond2, Pure Android Development] mweirauch:
2010-08-23-A monodie package

Hello monodie users,

here's an updated package with the recent changes to the linux-msm repository.

Though nothing really new for us, except tun-kernel module and device shutdown. (Shutdown doesn't work for me, though. Device hangs. Perhaps a data.img recreation will do ;))

Download: Here

@Spitfire: If you like, update the first post with the new package link.

Have fun.

Michael
[Touch Diamond2, Pure Android Development] ReWind402:
Glad to hear that you are supporting monodie users :).

Welcome back :)
[Touch Diamond2, Pure Android Development] kangan_1342:
Thank you all ....

there is some thing I want to ask .... When I run Android in my Topaz, My phone's back become warm and hot , and phone's charge become empty very fast ... are you have same problem ?what the problem is ?
[Touch Diamond2, Pure Android Development] mweirauch:
Doing the best I can - and time permitts - until the issue is solved finally. Just have sent off a mail to the HaRET mailing list requesting for a little assistance on finding the OEMAddressTable.

That is all more or less related to unoptimized drivers and kernel. And if you charge your device it will becoming hot anyways. We all have the same behaviour. Additionally, if you overclock and the CPU runs on full speed you might experience some extra heat dissipation.
[Touch Diamond2, Pure Android Development] mweirauch:
haret dumps required

Hi again,

phh had the idea that using the PCB id might work as well for detecting which device is used.

I need the output of the following command executed in haretconsole. (dumps parts of smem)

pd 0x01f00000+0xfc000 0x100

Especially I'd be interessted in the dump from shavenyaknz (monodie) and bheremans (new dualdie). But everybody - no matter if monodie or dualdie - can report back. Please always report your device name. (topa100, topa210)

Thanks in advance!

Michael
[Touch Diamond2, Pure Android Development] ReWind402:
Great idea phh had, i have an older dualdie device, do you still want the output?

P.S.: We will need to look more deeply in board-htctopaz-panel.c because we have there an annoying problem when we press the unlock hw button the backlight is on ( button backlight ) but screen is still off and if i do the usual unlocking gesture then the display opens up - sry for off topic
[Touch Diamond2, Pure Android Development] mweirauch:
Yeah, I have no idea why. It seems to be wakelock related. (Of which I don't have a deep knowledge of. It stops in the middle of the device wackeup phase.)

To workaround the issue, just hold the end-call-key a tad bit longer. That always works for me. Other solution is to use the power key - then it always wakes up correctly. That makes me think that it might not entirely related to the panel code itself. Deeper investigation to be done ;)
[Touch Diamond2, Pure Android Development] ReWind402:
Here is the output :) :

TOPA100 - older dualdie

HaRET(1)# pd 0x01f00000+0xfc000 0x100
01ffc000 | 00000302 00000000 00000000 00000001 | ................
01ffc010 | 00000032 00000000 00000000 00000000 | 2...............
01ffc020 | 39342e34 2e35322e 00003139 00000000 | 4.49.25.91......
01ffc030 | 342e3136 63746534 2e35322e 00553533 | 61.44etc.25.35U.
01ffc040 | 00000000 00000004 00000001 0000002a | ............*...
01ffc050 | 01375000 00000000 2143ab01 4365cd00 | .P7.......C!..eC
01ffc060 | xxxxxxxxx xxxxxxxxx xxxxxxxxx xxxxxxxxx | xxxxxxxxx
01ffc070 | 5f435448 3230315f 00000000 00000000 | HTC__102........
01ffc080 | 00000000 00000200 00000000 00000000 | ................
01ffc090 | 00000000 00000000 00000000 00000000 | ................
01ffc0a0 | 00000001 00000001 5566ef01 5510bcad | ..........fU...U
01ffc0b0 | 00000000 00000000 00000077 00000000 | ........w.......
01ffc0c0 | 00000000 00000000 00000000 00000000 | ................
01ffc0d0 | 00000002 00000000 00000005 00000011 | ................
01ffc0e0 | 000004e6 0000026d 00000000 00000000 | ....m...........
01ffc0f0 | 00000000 00000000 00000000 00000000 | ................
[Touch Diamond2, Pure Android Development] shavenyaknz:
Hi mweirauch,

Here's my monodie dump

HaRET(1)# pd 0x01f00000+0xfc000 0x100
01ffc000 | 00000302 00000000 00000000 00000001 | ................
01ffc010 | 00000032 00000000 00000000 00000000 | 2...............
01ffc020 | 39342e34 2e35322e 00003731 00000000 | 4.49.25.17......
01ffc030 | 342e3136 2e637434 332e3532 00005532 | 61.44tc.25.32U..
01ffc040 | 00000000 00000006 00000001 0000002a | ............*...
01ffc050 | 01374000 00000000 2143ab01 4365cd00 | .@7.......C!..eC
01ffc060 | xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
01ffc070 | 5f4c5343 3130305f 00000000 00000000 | CSL__001........
01ffc080 | 00000000 00000200 00000000 00000000 | ................
01ffc090 | 00000000 00000000 00000000 00000000 | ................
01ffc0a0 | 00000001 00000001 5566ef01 1543bcec | ..........fU..C.
01ffc0b0 | 00000000 00000000 00000077 00000000 | ........w.......
01ffc0c0 | 00000000 00000000 00000000 00000000 | ................
01ffc0d0 | 00000002 00000000 00000001 00000005 | ................
01ffc0e0 | 000004d1 00000263 00000000 00000000 | ....c...........
01ffc0f0 | 00000000 00000000 00000000 00000000 | ................
[Touch Diamond2, Pure Android Development] bheremans:
dump from newer dualdie device TOPA100 :

HaRET(1)# pd 0x01f00000+0xfc000 0x100
01ffc000 | 00000302 00000000 00000000 00000001 | ................
01ffc010 | 00000032 00000000 00000000 00000000 | 2...............
01ffc020 | 39342e34 2e35322e 00003139 00000000 | 4.49.25.91......
01ffc030 | 342e3136 63746534 2e35322e 00553533 | 61.44etc.25.35U.
01ffc040 | 00000000 00000004 00000001 0000002a | ............*...
01ffc050 | 01375000 00000000 2143ab01 4365cd00 | .P7.......C!..eC
01ffc060 | xxxxxxxx xxxxxxxx 33303130 30303739 | xxxxx80201039700
01ffc070 | 5f435448 3131455f 00000000 00000000 | HTC__E11........
01ffc080 | 00000000 00000200 00000000 00000000 | ................
01ffc090 | 00000000 00000000 00000000 00000000 | ................
01ffc0a0 | 00000001 00000001 5566ef01 1542bcec | ..........fU..B.
01ffc0b0 | 00000000 00000000 00000077 00000000 | ........w.......
01ffc0c0 | 00000000 00000000 00000000 00000000 | ................
01ffc0d0 | 00000002 00000000 00000005 00000011 | ................
01ffc0e0 | 000004e6 0000026d 00000000 00000000 | ....m...........
01ffc0f0 | 00000000 00000000 00000000 00000000 | ................

regards,

Bart
[Touch Diamond2, Pure Android Development] mweirauch:
monodie sound package

Before we get to the bad news regarding dynamic monodie detection...

Updated package with sound for monodie topaz attached to this thread so you can get a smile on your face like I do right now. :D

Michael

PS: Don't wonder that the package is so small. I forgot to strip all unneeded symbols from the modules before, so they never fit the the 8MB upload limit. That is fixed now :)
[Touch Diamond2, Pure Android Development] ReWind402:
I think i will put the monodie package for download on the main thread so that monodie users doesnt fell excluded from the project :) ( and maybe another redesign in 1st four posts ).

P.S.: Do you know maybe what was the problem regarding sound i am really curious ( in few & simple words :) ).

What happened with the dynamic monodie detection? :(
[Touch Diamond2, Pure Android Development] bheremans:
some register values that where wrong. You can see the commit her e:

Enable sound commit

more info in the irc logs here arround 6:19 irc logs
[Touch Diamond2, Pure Android Development] ReWind402:
Tnx for pointing this to me, i checked the log but it seems that i skiped those few lines :).
[Touch Diamond2, Pure Android Development] mweirauch:
All dumps indicate no difference at the relevant positions :(

pcb_cx 0x1ffc048=0x00000001
pcb_id 0x1ffc0ef=0x00000000
[Touch Diamond2, Pure Android Development] mweirauch:
some other dump required

Ok, perhaps SKUIDs are different:

If all reporters could please dump the following:

pd 0x081C00 64

And before I ask you to dump parts of smem again and again, dump the whole thing, if you like.

pwf smem_dump.txt 0x01f00000 0xfffff

This will create a file smem_dump.txt in the directory where haret.exe is on your phone. Please send the file privately as <yournick-device>-smem_dump.txt via PM.

Rewind402, shavenyakns and bheremans, if you would be so kind. Everybody else is invited to join in. The more dumps the better!

We need to find a uniform indicator because as soon as we are on nand, there can be no HaRET analyzing the WinCE OEMAddressTable which we could use then, anyway ;)
[Touch Diamond2, Pure Android Development] ReWind402:
Alright here is the smem dump ( older dualdie device ):

Sry, i had to zip it because when i upload the .txt it writes it exceed file limit.
[Touch Diamond2, Pure Android Development] mweirauch:
Thx. I need more sleep.... I striked the first dump request in the last post, but of course I still need that. Already past 12 here. Bed's calling and clock's rining at 6am... If you could also provide the first dump, please ;)
[Touch Diamond2, Pure Android Development] ReWind402:
Here you go :P:

HaRET(1)# pd 0x081C00 64
00081c00 | 050001ed ffffff80 020000d4 00000102 | ................
00081c10 | ffffffff ffffffff ffffffff ffffffff | ................
00081c20 | ffffffff ffffffff 86c8256e 00000000 | ........n%......
00081c30 | 00000000 fffffffe 00000000 ffffffff | ................

Good night m8 :)
[Touch Diamond2, Pure Android Development] kangan_1342:
Great ... I tested the new zImage & modules ... Sound is working now ... I can see the day is coming that we have a better Version of ANDROID than phones with original android ... Thanx all developers ...