yashsingh1/xdaforums huggingface dataset:
[Touch Diamond2, Pure Android Development] tommy1994:
omfg!!!!!!

the sound is working!!!!!!!

that is awesome!!!!!!

i finally can dump my window OS!!!!!

yoyoyoyoyoyoyoyo

hope the next is 3D fix,so we can play 3D game lol
[Touch Diamond2, Pure Android Development] bheremans:
newer dualdie :

HaRET(2)# pd 0x081C00 64
00081c00 | 050001ed ffffff80 020000d4 00000102 | ................
00081c10 | ffffffff ffffffff ffffffff ffffffff | ................
00081c20 | ffffffff ffffffff 86c8256e 00000000 | ........n%......
00081c30 | 00000000 fffffffe 00000000 ffffffff | ................
[Touch Diamond2, Pure Android Development] test222:
which zImage you are using?
[Touch Diamond2, Pure Android Development] tommy1994:
http://xdaforums.com/showpost.php?p=7853522&postcount=226

also,i tested the voice input and it working:)

all i can say is thank you a lot developer!!!!!

keep it going!
[Touch Diamond2, Pure Android Development] shavenyaknz:
Here's the dump of my monodie device:

HaRET(1)# pd 0x081C00 64
00081c00 | 190001ed 00ffff80 00000102 020000d4 | ................
00081c10 | ffffffff ffffffff ffffffff ffffffff | ................
00081c20 | ffffffff ffffffff f0b8f050 00000000 | ........P.......
00081c30 | 00000000 fffffffe 00000000 ffffffff | ................
[Touch Diamond2, Pure Android Development] mweirauch:
anydie test package

Hi again,

please test the attached package. It's trying to do do dynamic device detection. So everybody - no matter which device - is invited to test.

Report back your results (including device type).

Michael

PS: Sound freezing issue commented in code, but already got told what it is. Just need time to fix it and test and then commit to official tree :)
[Touch Diamond2, Pure Android Development] kangan_1342:
hello body .... I tried new pakage ... every think was like before ... Sound,touch screen,bluetooth .... . but one think was added : My device restart when I was runnig Android ... It was first time that my device restarts in android .... by the way Thank you for your hard working
[Touch Diamond2, Pure Android Development] mweirauch:
I assume you have a monodie device, right? You used the anydie-package, right?

What did you do when the device restarted? An error description is always helpful when reporting errors :)
[Touch Diamond2, Pure Android Development] kangan_1342:
Yes I have Monodie device and I used anydie package ...

description : Some body called me ... in the Call Screen , I Pulled the red botton for rejecting call , and the call rejected but the Screen locked same as hardware keys ...

BUT : I think this happend becuse I didn't let Android starts compeletly ... and maybe it's my fault , not the package ....
[Touch Diamond2, Pure Android Development] shavenyaknz:
Work for me on my monodie device, you rule mweirauch.

I've been having the same issue with other kernels built about the same time as sound was fixed. Perhaps it was some previous changes that caused this ? I saw someone on another forum saying that using one of the earlier packages would fix it so I assume somebody is frantically working on that.
[Touch Diamond2, Pure Android Development] mweirauch:
Thanks for you reports! Only need some non-monodie users - except myself - that it is working.

The freeze on call end may just be a bug which was always present , just didn't show up until sound was fixed. Will try to reproduce...
[Touch Diamond2, Pure Android Development] MusikMonk:
The any-die package seems to be working fine on my topa100 dual-die device.

I did a general test and didn't notice anything that should work but wasn't working.
[Touch Diamond2, Pure Android Development] mweirauch:
Ok, my handset freezes ~9 secs after a call is established. It looks like it is no regression but a bug which just comes up now that sound is enabled. I've reverted the local fixes which enable h2w (HTC 2 wire) support so that device doesn't freeze on sound, but it still freezes on call.

So I am pretty sure that it is no recent change in code, just the fact that enabling sound now triggers this freeze which has to be resolved.
[Touch Diamond2, Pure Android Development] mweirauch:
test autobuild service

Just commited my monodie detection changes. (And the freeze on sound issue reported, not the freeze-on-call-issue.)

Please test the autobuildservice build when it is ready: http://glemsom.users.anapnea.net/android2/htc-msm-linux/

Might take some minutes till the new build arrives!
[Touch Diamond2, Pure Android Development] kangan_1342:
Thank you ... I'm going to test this one ... as soon as I can , I'll Report result ...
[Touch Diamond2, Pure Android Development] shavenyaknz:
Just downloaded the latest modules which were up to commit 'a3674318' by phhusson just after you added the monodie detection. Everything is great on my monodie.

Thanks mweirauch !
[Touch Diamond2, Pure Android Development] bheremans:
My newer dual die device is booting fine with the latest kerel.

Thanks!
[Touch Diamond2, Pure Android Development] mweirauch:
conclusion?

After all the positive replies here and no negative results in the XDANDROID thread, do you guys think the issue can be considered closed? ;)
[Touch Diamond2, Pure Android Development] ReWind402:
Yes, my device too works properly without issues, there was not negative report in the general thread.
[Touch Diamond2, Pure Android Development] shavenyaknz:
Yeah sounds like a plan. Thanks for all your hard work mweirauch.
[Touch Diamond2, Pure Android Development] kangan_1342:
Every thing is great ... but I have 2 qustions :

1- How I can turn of the LED ? When I push the End call Key , my screen become Black but,I think it's not in deep sleep,becouse when I turn it on again may battery percent decrease ... also my LED is on ( Orang ald Green ) all time.what should I do ?

2 - Still may battery become hot ... and battery become empty very fast ? ?!

thanx all ...I use the lastest package u refferd .
[Touch Diamond2, Pure Android Development] mweirauch:
The LED is used to indicate if the device is sleeping or not. It's meant as a debugging helper ;) When the kernel has matured it will be turned off again. When the LED is green, the device sleeps, when it's orange, it is not sleeping.

BUT: The LED costs virtually no power. Just a little bit. So don't worry.

Yes, it doesn't last that long. But don't trust the displayed values. They are not reliable. Yesterday I played mp3 for more then an hour on 5%. That's virtually impossible in winmo ;) So wait until battery reportings get fixed ;)

[/QUOTE]

I hope you mean the autobuild service builds. You don't have to use packages from this thread anymore.

Btw: If you have questions unrelated to the monodie/dualdie discussion, ask them in the main thread please. This thread is dedicated to the afformentioned issue. Thanks.
[Touch Diamond2, Pure Android Development] Staphill:
It works !!! :) Thank you
[Touch Diamond2, Pure Android Development] ReWind402:
it seems that some users are having problem running haret after the 29th dynamic monodie commit dont know if this causes the problem but it seems that only 26th works for them ( ex. http://xdaforums.com/showpost.php?p=8011130&postcount=4396 ), others are also having similar problems :s
[Touch Diamond2, Pure Android Development] mweirauch:
Ok, so after some replies from the people reporting that their device froze on boot it turned out, that the balsat autobuild packages are to blame. The glemsom autobuild packages are working fine.

So false alarm and this thread can stay 'Solved'.

Michael

PS: I think we should only advertise the glemsom builds which have official linkage form the XDAndroid project and I don't trust that "optimized for speed" on the balsat builds tagline until proved otherwise. No offense.
[Touch Diamond2, Pure Android Development] ReWind402:
Changed the general thread to link only on glemsom autobuild.
[Touch Diamond2, Pure Android Development] ashway:
Anydie kernels don't work on my latest monodie Topaz.

The latest kernel that works fine is

linux-msm-topa100-2010-08-26-A-monodie-only-sound-pkg.zip

So, it seems that dual-/mono- die detection doesn't recognize memory type of my Topaz.

What information should I provide to assist you to add support of Topaz like mine?

Thanks in advance.
[Touch Diamond2, Pure Android Development] mweirauch:
Hi ashway,

if the topic wouldn't be solved, the thread title wouldn't carry "Solved" in it. ;)

I recently commited another monodie detection case to the linux-msm kernel repository. Just check out the autobuildservice here.

Have fun!

Michael

PS: Note to myself: I should really clean up testing kernels posted to the forums ;)

EDIT: Please read my reply with a smile. It's not meant to be harsh in any way.
[Touch Diamond2, Pure Android Development] ashway:
Thanks.

The htc-msm-linux @ 20100926_001914 realy works, while all previous that already have monodie detection don't work. Even the kernel from the latest bundle - 2.2 FRX01.

I'd recommend mention about such things in the thread, before marking it as Solved. ;)
[Touch Diamond2, Pure Android Development] mweirauch:
Glad to hear that it works for you.

The first monodie fix is some time old already, but recently another SKUID for the PCBA "appeared" which was yet unknown, so I added it as well to the list of monodie PCBs after I gathered the necessary information from the user.

(here)

Thanks for reporting back.

Michael
[Touch Diamond2, Pure Android Development] RufusThorne:
Worked for me!! -- Thanks very much.
[Touch Diamond2, Pure Android Development] Charles481:
It doesn't update zImage forever?
[Touch Diamond2, Pure Android Development] mweirauch:
Pardon? If your question was if this testing zImage will get updated, then no. It was only for testing out stuff.

To get the latest kernel head to the kernel autobuild site here.

Also have a look at the dedicated XDAndroid thread for Topaz here and read the instructions.
[Touch Diamond2, Pure Android Development] Charles481:
my device is topa170.I tried many of new zImages my phone just rebooted. Only "topa100-2010-08-26-A-monodie-only-sound-pkg" is running.

and it doesn't Charge.
[Touch Diamond2, Pure Android Development] mweirauch:
Hi Charles481.

Seems your device is not covered yet in the monodie detection. Please follow the procedures detailed in this post: http://xdaforums.com/showthread.php?p=9357431#post9357431

It's enough to perform steps 2-9. Step 9 created some files all starting with "topa_". Please post the content of file "topa_pcba_id.txt" here in a "<code>" section. (Please note, that some editors might not like the file content as it's a raw memory dump.) Alternatively upload the file somewhere and post the link.

Michael
[Touch Diamond2, Pure Android Development] Charles481:
:) My dumps of HARET. (except topa_smem.txt)

View attachment Haret_Dump_TOPA170.zip.zip
[Touch Diamond2, Pure Android Development] mweirauch:
Hi again. Your dump contained a new pcba skuid: http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commit/90604444443e357a2c286fbfc196519a427eda84

Grab the just built kernel from the autobuild site and report back please. (htc-msm-linux @ 20110615_174606)

Michael
[Touch Diamond2, Pure Android Development] Charles481:
It worked for me,thanks Michael.But the kernel has some bugs.the android always displays the battery is charging
[Touch Diamond2, Pure Android Development] mweirauch:
Glad to hear that it worked out for you!

Regarding the battery, I will have to verify. Have not been running the .27 kernel on the Topaz for a while... (This is a topic for the main FRX06 thread then, anyway.)

Michael
[Touch Diamond2, Pure Android Development] Charles481:
Oh!It is system image problems.The zImage is normal.My device can charge in other systems.Thanks!
[Touch Diamond2, Pure Android Development] howado:
hello i have same problem :) i tried format SD, new SD card , new rom , new radio .... unlock to 2,51 olinex :D , stock rom , cooked rom , new initrd , new zimage , 1,6 version and 2,0,1 version ... and still nothing ... :confused: :confused: I want an android in my WM:) shadowline version freezes , XDA reboot back to WM [(in my topaz)topa100] ...
[Touch Diamond2, Pure Android Development] mondychan:
our Topazes are cursed! :cool:
[Touch Diamond2, Pure Android Development] sntc06:
I'm using TOPA100 now, and sadly I tried many of zImages my phone just rebooted...

BUT, a while ago I downloaded a zImage file from somewhere I can't remember (must be buried in the pages I guess...)

Somehow, this is so far the ONLY zImage that let me boot Android...

I'll upload it for you guys. Give it a try! :)
[Touch Diamond2, Pure Android Development] kenzo82:
cool..will try it out. Thanks!!!
[Touch Diamond2, Pure Android Development] kenzo82:
Hey! It is working!!! Thank you very much!
[Touch Diamond2, Pure Android Development] Spitfire128:
Yup, working for me too. At first it froze at the point where the Nexus-animation was supposed to kick in (used the latest Xdandroid build) but with this one it booted all the way into Android. Despite various restarts it's still near unusably slow and unresponsive, but hey, it's a huge improvement.

Now if someone could find out what the problem-causing difference between that zImage and more recent ones is, we might get a better one working...
[Touch Diamond2, Pure Android Development] richice:
cool,it's useful
[Touch Diamond2, Pure Android Development] lobfredd:
Have u guys tried boot android through gen.y dual boot thing?

I have 2 topaz100 and android only work on a newly formatted sdcard with only andoid files on it.

I tried to run haret through Gen.Y.Dualboot and it works 100% on both of my topaz (both topaz 100) with any zImages out there. :D
[Touch Diamond2, Pure Android Development] Spitfire128:
^ When did you get your Topaz('s)? It doesn't work on mine even when I use the Gen.Y dualboot; I just get the same ol' soft reset.

EDIT: Or rather/also, do you have the same problem as we do without the Gen.Y dualboot.
[Touch Diamond2, Pure Android Development] lobfredd:
I got them in March this year.

yup same problem as u if i dont use Gen.Y dualboot.
[Touch Diamond2, Pure Android Development] Spitfire128:
Strange. I formatted my SD card, threw the new Android build from the main thread on there, made it autoboot Android, but it still just soft resets.. That's perhaps because Windows Mobile is still being booted 'below' Gen.Y DualBOOT, of which I'm not sure if it should be happening. The WinMo taskbar keeps popping up above the program, even the Launching HTC Sense screen appears at some point.

I guess I'm doing something wrong, but what? Gen.Y DualBOOT is installed on the device memory (already tried re-installing), Android's in the storage card's root.
[Touch Diamond2, Pure Android Development] iceman198:
I never had much luck with Gen.Y DualBOOT...Android wouldn't load at all or if it did, it errored all over the place...so I just stick with waiting for windows to be done (as in let it get fast to respond) and then just run Haret manually.
[Touch Diamond2, Pure Android Development] Spitfire128:
Well, the dual boot does work with the zImage posted earlier (Android boots the same as it would directly from Windows in that case), though unless it's malfunctioning for me it's not a true dual boot system as much as it is a popup asking me wether to run Android or go back to WinMo once WinMo is already near done loading.

I still hope this will get us somewhere... There must be some way to get things working if they do for lobfredd. Could you maybe give a few more details? Which Android build are you using? How does Gen.Y DualBOOT work for you, does it also launch 'on top' of WinMo?
[Touch Diamond2, Pure Android Development] shavenyaknz:
Cool that works for me too. Perhaps there was some kind of change in the zImage between that one (Dec 20th 2009) and another one I tried which didn't work (Dec 22nd 2009). Perhaps if we can work out what the difference is between the two we can get it compiled into a new zImage.
[Touch Diamond2, Pure Android Development] robinsa:
for is not working.

It remains lock at android logo
[Touch Diamond2, Pure Android Development] Orzash:
Having the same problem:

sometimes it gets to the android logo and just freezes, and sometimes I can see the notification bar, and then it freezes again.

The most advanced step I got to is "continue using: *something* / setup wizard", and then it froze once again.

:S
[Touch Diamond2, Pure Android Development] Charles481:
Me too..My phone is topa170...It has the same problems too..

Many of zImage just rebooted..though the zImage can boot android,the zImage has so many problems.
[Touch Diamond2, Pure Android Development] swgr:
same problem completely, all zImages cause reboot, except the "very slow one".

what's more, using the "very slow one", my d2 stuck in the android logo screen for more than 3 hours.. i don't know whether it's just very, very slow, or the system has already crashed..

hope this problem can be solve soon because more and more people will become users of TOPA100..
[Touch Diamond2, Pure Android Development] Spitfire128:
If the zImage posted isn't working you may want to try a different Android build with it. For me XDAndroid didn't work, this one however did boot all the way up. Though it's still not really usable.
[Touch Diamond2, Pure Android Development] iceman198:
Just for kicks and giggles

Anyone want to try downloading this one (http://www.duttonbiz.com/xda/2010-04-27 XDAndroid 2.1.rar).

This is already to go for the Topaz, all you have to do is just unzip it and move the "Android" folder to the root of your SD card. I recommend you do format of your SD to fat32 just before for safe keeping.

If it resets back into WinMo the first time, try one more time just after WinMo boots up...make sure it's the first thing you do.

Let me know if you get anywhere.
[Touch Diamond2, Pure Android Development] Spitfire128:
Nope.

I formatted my SD card to FAT32. Only put the Android files on there. Tried multiple times. It's not working, it just soft resets.
[Touch Diamond2, Pure Android Development] iceman198:
That's crazy...what size (capacity) is your microSD card? Also, your signature says you're using a custom ROM for WinMo...even though the first post in this thread says you have, just want to make sure...but have you tried the stock WinMo ROM?

I just made a post on the main topaz android thread asking for someone with your model who has it working and maybe we can compare specs? Don't know if you guys have tried to get someone yet...

Sorry if this is all repetitive, just trying to cover the bases.
[Touch Diamond2, Pure Android Development] Spitfire128:
Thanks for trying to help us out. Doesn't matter that it's a little repetitive, any help is welcome.

My MicroSD card is 8 GB. I also tried a 1 GB one I had lying around. Tried different formatting configurations. I did try the stock ROM as well as a few others, someone else did as well.

The only clue we have as to what's causing this is the fact that everyone who is having this problem seems to have a Topa100 purchased this year, usually around March; the last Topa100s made before production was ceased, according to the store where I purchased mine. And the only clue I can see towards getting it to work, is whatever the relevant difference between most zImages and the working one is.
[Touch Diamond2, Pure Android Development] Tim4:
I think the reason why hspl and android doesnt works on latest topa100 is that memory has been changed (Older one based on Samsung or Hynix on some units, and Olinex said that making hspl for hynix was painfull)

So maybe memory contol drivers must be changed
[Touch Diamond2, Pure Android Development] madman_cro:
i have topa100 and hspl works same as android
[Touch Diamond2, Pure Android Development] Spitfire128:
I think HSPL has already been fixed, because it's also working for me. Android isn't though. I'm guessing we got ours after you got yours.

That memory drivers stuff sounds interesting, I hope it'll get us somewhere.
[Touch Diamond2, Pure Android Development] iceman198:
Ok, and just to clarify...you state on the first post that there seems to be only one zimage you can get to boot. What do the others do? Just a looping boot animation?
[Touch Diamond2, Pure Android Development] Spitfire128:
We don't get the boot animation, not even the Linux screen with the black background and the white text.

There was one other zImage, can probably be found somewhere in this thread, that froze on the Linux screen, but it was an old one that never really fully worked in the first place. (I put it back in the OP)
[Touch Diamond2, Pure Android Development] iceman198:
That's weird because it hasn't even tried to touch the zimage if you don't get the tux in the top left screen...

Just for kicks, rename your STARTUP.TXT to something else and then run Haret. It should say that it can't find it and then ask you what text file to load. There will be a box in the bottom that should read something like "Topaz device found".

Can you verify that?
[Touch Diamond2, Pure Android Development] Spitfire128:
Already done that before, and it did as you described, but it didn't change a thing about the result: just a soft reset.

EDIT: Wait, are you sure it hasn't touched the zImage at all yet? Because I can verify that builds that just get the soft reset with most zImages do boot with the 'working' one. So that would be really weird indeed.
[Touch Diamond2, Pure Android Development] iceman198:
Sorry, you're correct...but to my knowledge, all it does is just check to make sure it exists before bringing down winmo.

so...even though you renamed STARTUP.TXT to something else, it still does a soft-reset as soon as you run Haret?

what operating system are you running to copy stuff to your phone?
[Touch Diamond2, Pure Android Development] Spitfire128:
Well, during the soft reset, the screen is completely black (edit: off) for a brief moment. Couldn't that be the point at which it's like "screw this zImage" and resets?

That is correct. I renamed startup.txt and chose it manually, but I just got a soft reset. I'll try once more as soon as I have full access to my stuff again, but I'm sure it didn't change anything.

I use Windows 7, phone on Disk Drive.

EDIT: Oh, turns out I still got Android on my SD. Renamed startup.txt to lol.txt, then ran Haret. It did say "Found machine Topaz", but when I pressed "Run" it just soft reset.
[Touch Diamond2, Pure Android Development] iceman198:
Ok...so Haret finds your phone right...

So, sounds like you're right and that it definitely has something to do with the zimage.

Have you tried one of the "dirty" zimages? (http://balsat.hopto.org/) If not, try that. They don't contain debugging stuff...maybe that has something to do with it. The first one listed is the latest version. They completely automated to mimic the htc-kernals so it's the same thing, just no debugging.

If that doesn't work, can you try this; Do you have another computer that's not windows 7? Plug your phone into and start from scratch and copy all the needed files over? Like re-download them?

The reason I'd like you to try a different computer and re-download them (don't just copy them from some place where you've touched them with the Windows 7 machine) is because maybe for some deranged reason it's changing the file permissions when it copies whatever over to your phone...This is probably not the case but wouldn't hurt to try.
[Touch Diamond2, Pure Android Development] Spitfire128:
There's only one pc in this home, so that's not going to work.. I guess I could try downloading it directly onto my phone. But since that's going to be rather slow and I'm a little busy that'll have to wait.

I tried the latest "dirty" zImage. (I'm assuming I don't need to do anything with the modules tar.gz file.) There's no change.
[Touch Diamond2, Pure Android Development] iceman198:
it's the zimage file that tells which tar.gz to use...so..that didn't work..stink...

Well, until you can access another computer or something...maybe try the latest version of Haret? I've attached it to this post.