yashsingh1/xdaforums huggingface dataset:
[About XDA developers] pzumk:
Hi,

I were about to update my profile/visitor message which showed what I use on/with my phone but I can't see them anymore!

Did you remove the feature? Do I have to put everything in my signature like all the other n00bs do to stretch the posts?
[About XDA developers] Livven:
Hehe, nur weil du Moderator im größten deutschen Handy-Forum bist, heißt das noch lange nicht, dass du andere als Noobs bezeichnen darfst, besonders da du gerade selber eine noobische Frage stellst :p.

It does seem that visitor messaging has been disabled, but I never found it useful anyway.
[About XDA developers] pzumk:
Is it possible to bring it back? Please admins.

##

Haha xD Da hast du dich mit deiner überdimensionalen Signatur wohl gleich angesprochen gefühlt :D

Meine Frage war berechtigt weil ich das zurück haben möchte :D:D
[About XDA developers] Livven:
I'd probably contact svetius or Mike (mikechannon) on this, they're the forum admins ;).
[About XDA developers] svetius:
We disabled it because we found that the vast majority of users don't use it. Disabling it means that your User CP loads a bit faster, and also it's one last thing to cause undo load on our servers.

If there's a huge number of you that disagree with this action, we can reconsider, but again, our understanding was that it was a generally unused feature - most people just use Private Messages. :D
[About XDA developers] Livven:
I agree, there's really no need for visitor messaging, it's just confusing and usually either PMs or posts in the specific thread are better. But from what I see, the OP wanted to use it to display information about his phone, so maybe you could add an option to choose a phone model and providing some info about it (ROM etc.), like the operator/country logos.
[About XDA developers] pzumk:
Okay I can understand that.. Could you atleast add more profile fields like

Firmware/ROM:

Phone: (actually not needed because of the many subforums)
[About XDA developers] the-equinoxe:
In regards to our German speaking Friends:

-please translate fully..

Da sind hier ja auch Mods die Deutsch plaudern ;)

(for the non-Germans: we have moderators who actually speak German ;) )
[About XDA developers] orb3000:
Completely agree to leave it disabled

Neither do I

Habla Español:rolleyes:
[About XDA developers] Livven:
Didn't know you speak German :D.
[About XDA developers] ElCondor:
Nearly all Dutch people can speak German;):p
[About XDA developers] Livven:
I guess that living in a country with a less common language does have its benefits - if you live in England, you most probably won't know that many foreign languages, but if you live in Netherlands, you not only learn English but even German. Do you speak it, BTW?
[About XDA developers] ElCondor:
Yes that must be the cause, but it also depends on how far a country is 'cultured' I think.

Well my German isn't very good, but I can speak it good enough to be understandable.

My French is much better than my German though.
[About XDA developers] Livven:
Wow, how many languages do you speak? Dutch, English, German, French...
[About XDA developers] ElCondor:
Exactly! But they're all working about the same grammatically, so for example Chinese is a much harder language;)

But we're going way offtopic!:)
[About XDA developers] pzumk:
back to topic please?!

Sonst gibts ärger. ;D
[About XDA developers] g2tl:
ahhhh can you at least temporarily restore it? I had created a list of trusted/recommended traders there :/
[About XDA developers] ElCondor:
I suggest you contact either svetius or mikechannon about this, I am not sure if it's possible to restore the information, but most likely they made a backup of it.

Btw it should've been better if the admins had warned first before proceeding with desabling the system, but that's just my opinion.
[About XDA developers] pzumk:
Agreed with the guy above.
[About XDA developers] ben_duder:
It would be really cool, like Livven said, if we could get our phone to show up on our profile.

I would actually like to see it on posts as I think it's more important than a user's join date, and quite a lot of members don't include it in their sig.
[About XDA developers] ElCondor:
Join date is very important, it shows (better than amount of posts) whether you're a noob or not.

But indeed, it would be very useful to have some space for the phone name somewhere in the posts.
[About XDA developers] ben_duder:
I suppose it is important and I'm not saying we should get rid of it, but I've seen quite a few noobs who have joined two years ago to download a ROM and not come back since, hence not actually reading or knowing anything about the site and what it does.

Anyway, yeah - most troubleshooting threads will ask for things like your specific model number, SPL, ROM, radio etc. and if these data could be added to the little side bit without wasting a load of space then it would be really useful.
[About XDA developers] krook6023:
I have no problem with visitor messages being disabled…but having a device, rom, radio etc that showed on your posts would be very useful…plus it would work very nice with the new skin!
[About XDA developers] flyboyovyick:
And a thanks system like other forums. So that you can thank people who have helped you and vice versa.
[About XDA developers] pzumk:
Okay, since there's the new style with the profile infos on the left which will be default for everyone soon, I'd like to have

Phone

ROM/Firmware

added. :)
[About XDA developers] ben_duder:
+1 :) Maybe radio too...
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
Hi all.

I've been lurking on the Kaiser forum for some time and have found a wealth of very useful info... Except when it comes to running Android via HaRET.

Yes, I know there have been a million questions. Yes, I have seen many of them inserted into what should be straight developer/bug threads. Even so, the "answer" to my issue doesn't work.

From "How to run Polymod’s AWESOME 2.1 Eclare Build and Updates":

NOT TRUE. I have booted more than 20 times pressing/holding the center button at different times and with different intensities. No matter what I do, I get this blasted error message. Any solution other than the stock one listed above would be cause for hero-worship.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
This error can have a number of causes, namely the file system, is the SD card formatted FAT32, ( some cards come formatted FAT16 as standard), or having the SD card set up incorrectly, for haret you need to have all files in the andboot folder.

Provided haret starts correctly, which it is since you cannot reach the post-install stage unless it is booting the kernel, then the only part of the procedure that can go wrong is the installer.

The only things I can think of that would cause the installer not to start is either the card itself, or problems with the andboot folder and/or the files inside.

The only advice I can give at the moment is to calmly start haret, watch the scrolling text until you get the pause, and the 'press d-pad to start installer' text.

At that point if you press the d-pad centre button, and hold it you will see '^@' on the screen, if you do not see the '^@' or see anything else then the installer cannot start, it will only respond to the correct key.

If you see anything else it is possible you have incorrectly set an option in default.txt file.

If all this still fails, then report back with anything you find, I may have some other ideas based on what you find out :)
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
+1 on zenitys answer and in addition you are using the correct basefiles to run haret?
[Tilt, TyTN II, MDA Vario III Android Development] loserskater:
Try using the screen as a giant keypad and pressing and holding the center of the screen.

EDIT: Scratch that... It only works as a keypad once the menu is up. Sorry.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
that works?

Seriously?

I mean really?

No it bloody does not, ( lol, can't believe i actually tried it ).....
[Tilt, TyTN II, MDA Vario III Android Development] Joe1981AL:
i had this problem and pulled my hair out, eventually i downloaded a different haret basefile and copied to my SD and bam it worked, sorry but i'm i soon after went to nand and erased the haret files so i don't have them anymore.
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
zenity: Yes, it is FAT32 and yes all files are in andboot. I do see a '^@' when I press the center button if I press it when prompted. If I press and hold as soon as I see Tux, I don't get that character pair. I see a different string of characters if I press one of the other buttons instead. I haven't modified the default.txt file in any way other than to re-name it from default-kaiser.txt.

I am using the files from a haretinstall.zip that I got directly from sourceforge Android HTC project (sourceforge.net/projects/androidhtc/files/... not allowed to post links <_<). The files were under the date 02-13-2010. I have since grabbed two other more current versions of haretinstall.zip and will try them after I post this. I am also using the most current androidinstall.tar and androidupdate.tar from sourceforge, though I have also tried Polyrithmic Eclair 2.1g's androidinstall.tgz.

Thanks all for the replies and I'll try those other haretinstall.zip's while waiting for any other replies. :)
[Tilt, TyTN II, MDA Vario III Android Development] deezy7:
maybe try a different sd card?

I couldn't get any nbh's to be read off of my 2gb patriot, but when i put in my 16gb sandisk the nbh's worked.

I know this is only marginally related lol, but it's worth a shot?
[Tilt, TyTN II, MDA Vario III Android Development] Joe1981AL:
I do remember trying the 2/13 first and that is the one that holding the button did absolutely nothing, it was either 2/14 or 2/20 (those are in my browsing history) that did work for me. It was a "ta dah" moment when the install menu popped up.
[Tilt, TyTN II, MDA Vario III Android Development] Joe1981AL:
I doubt it, cause its reading the kernel if he is getting the error message. The error message about system.img is because an install hasn't been performed to create a system.img or data.img file on the sdcard.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Actually it's very related, android seems unusually sensitive to SD card issues that winmo simply ignores.

If you have another SD card available then try that, if not then all I can suggest at the moment is reformatting a couple of times, that worked for one of my 2Gb cards that simply would not recognise my NBH files no matter what I did.

An alternative might be to grab kalt_kaffe's zimage from here : http://xdaforums.com/showthread.php?t=660158

this seems to be the best zImage for eclair at the moment. Just download it, put it in andboot with the rest of the haret files, make sure it's named correctly, ( it'll probably need you to delete the zImage file already there anyway, or overwrite if you use a card reader and windows).

Since you are getting the ^@ then the kernel is running properly, that actually only leaves the SD card, the reason you get the other character pair if you press to early is that with some zImages the keyboard may not be set up early enough, which is why I always wait for the pause, never failed me yet.
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
Maybe... Maybe...

Thanks again all.

It may well be the SD card but a more current set of HaRET basefiles did finally fix the center button issue. I have been able to get android installed but little else. I have a blank screen (with clock, battery and wifi in the top bar) but nothing else.

I'm going to blame this issue particular tar files I used and I will go back and try the Eclaire by Polyrithmic or the one by kallt_kaffe you linked. I didn't really want the Andriod HTC tar files but was using them in an attempt to minimize the variables causing my initial button issue.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
If you are going to use polymod may I suggest the 2.1D download linked in my sig, it's only the install.tar, but is pretty stable, and is in fact what I use for my everyday android on my main kaiser.

Since you have a working set of haret files, simply replace the zImage with kalt_kaffe's zImage, replace the installer with poly's 2.1D and you should hopefully be good to go :)
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
I tried 2.1d and it locked during the post-install setup. I also tried kalt_kaffe's zImage with both 2.1g and it broke my wifi.

As such, I am back to using 2.1g with the kernel that was originally bundled with it... Even bluetooth seems to work. I can see my lappy but I haven't tried pairing yet. No microphone though as far as I can tell. It'll be awesome once the ethereal developers find a way to make the camera work.

At least now I have something new to play with. I'm eying Warm Donut b/c I like the look but I don't know if I want to undo the working install I have. Never know till you try, right? :D
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
I guess this is probably already well-known but my kaiser's camera works under Warm Donut. The pics aren't all that great but it does take them.
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
If anyone else stops by... I'm having audio problems. I'd had audio problems with all the different Android releases I've tried so far. The main problem is that there is no audio. No alerts, rings or media.

Any suggestions?
[Tilt, TyTN II, MDA Vario III Android Development] aikeru:
The way I understand it, that can be affected by your radio firmware... The radio firmware I use without any problems for android is in my sig. :)

Please post which one you are using, too!
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
Good call! I hadn't considered my radio version though I have seen numerous posts suggesting that users upgrade... Or at least swap theirs out.

WM6 indicates that my radio version is 1.27.14.09.

Radio 1.27.14.09

Protocol 22.45.88.07h

ROM 1.62.00.00

I'll do a little reading and see if I can't figure out how to swap a new radio (probably the one you're using) in.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Ok that's one old radio, go here : http://xdaforums.com/showthread.php?t=393182, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio.
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
I got the radio nbh and now I am working out how to use nand. Most everything I see is geared toward wiping windows to replace it with android. I don't want to do that yet so I'm trying to parse now to flash this nbh without jacking up my device or the windows that is currently on it.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
oops, forgot you were still on winmo, no matter, flashing radio will not wipe winmo either, just rename it, put it on SD, power down, press power+camera, once you get the tricolour screen it'll disappear and check the nbh, then ask you to press power button to flash it, once it's complete, just reset, and thats it.
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
Well... I can't flash HardSPL onto the phone but maybe that shouldn't be a surprise since the person I bought it from said it was "unlocked". I haven't found any way to confirm that I have HardSPL installed but that hardly matters because I can't seem to flash the radio nbh either.

Running KaiserCustomRUU.exe correctly identifies my ROM version but says nothing about the radio. When I try to "Update" with the radio nbh, the flashing utility correctly identifies the radio version but won't flash it... It ends with an error (on the PC end) and I have to power-cycle the phone.

Everything I can find talks about flashing ROMS and says that flashing radios is "just like flashing a ROM" except that it isn't working for me. I guess I'm a little slow. :confused:

EDIT: Just saw your 3:19PM comment Zenity. I will try that. What do I rename it to? The name you gave on the last page?
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Rename to KIASimg.nbh, also you can see what SPL your phone has by putting it into bootloader and reading the text at the top, make sure you do this without an SD in, or it'll go past too fast.

It'll either have a 3.xx HardSLP or perhaps an OliPof one, depending on how it was unlocked.

I do suggest getting HardSPL on there somehow, if you don't already have one.

Another way to go might be to try flashing a more recent stock ROM, these usually have a radio upgrade as well, but it will replace your present winmo install, ( that old a radio it must be 6.0, the wiki has links to more recent stock roms which do not require HardSPL to install).

You will almost certainly have issues running android without at least a 1.65.xx radio.

Your not slow, it's a lot to take in, and most of us have had a head start ;)
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
Well, I put it on the SD, named as you said and booted as you said. It went bast the tri-color bootloader screen and into a white "Loading" screen and stayed there for 10+ min before I pulled the battery out.

I got back into the bootloader without the SD as you suggested and I see:

KAIS1*0

SPL-1.93.0000

CPLD-8

Since that's not a 3.xx as you suspected, I suppose that means that it does not have a HardSPL on there... I guess that means I need to figure out how to get one flashed on properly. I imagine that the radio won't flash on until I do, which would explain the 10+ min "Loading" screen when I tried it.
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Yes, that'd explain it, also if it is winmo 6.0 you may not be able to flash hardSLP 3.x anyway, have a look here : http://xdaforums.com/showthread.php?t=498320, and notice that HardSPL for winmo 6.0 is a 1.x version number.
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
Heck yeah! :)

Following the instructions on pof's thread ("HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free)") I was able to get HardSPL 1.1 with AT support flashed. I was then able to flash the new radio from the SD without an issue.

Now I've got:

ROM 1.62.502.0

Radio 1.71.09.01

Protocol 25.75.40.02.eMo

I may flash a new windows ROM at some point but right now I'm going to boot into android and see if my audio works. Thanks again for the custom help! :D
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
No audio yet but at least now I am somewhat updated. :rolleyes:
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
The audio issue may be related to you running 6.0, I seem to recall someone else having a similar problem with audio a few months ago while running 6.0.

Glad you sorted out the whole HardSPL issue, I know most of the time you'll get the whole 'search and ye shall find' thing, but hell, knowing where to look helps too ;)
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
Ain't that the truth. I may be new to modding my mobile but I'm not new to keeping marine aquaria and I tell noobs to search all the time. ;)

I couldn't leave well enough alone... Especially after I booted back into windows after the radio update and found my audio broken. I decided to flash on WM6.1. After reading and trying (and failing) to get a HardSPL 3.xx or higher, I decided to just try flashing the official WM6.1 release w/o updating and it worked great! I may try flashing on a new HardSPL eventually but not just now because...

I just booted into android and my audio is working now. :thumbsup:

The official release downgraded the radio as I knew it would. The bootscreen now says:

R 1.65.21.18

G 25.88.40.05H

D 3.57.00.00

May be useful if anyone stumbles across this thread while searching. :cool:
[Tilt, TyTN II, MDA Vario III Android Development] aikeru:
Thanks for posting your solution, too! :) A lot of people neglect to do that once their problem has been solved... It's a great community here.
[Tilt, TyTN II, MDA Vario III Android Development] mr_fosi:
No prob! :)

I've been active on other forums enough to know the frustration of always seeing the question asked but never seeing the solution posted.

One other point of interest for kaiser users: incubus's super eclair's "settings" dialogs are fairly crashy. Setting ringtone, brightness, or other such sliders is a problem. Other parts such as wifi, bluetooth, status and such are all good.
[Windows Mobile Development and Hacking General] zombie89:
i know all i need to do is delete a registry file to enable tethering because ive done it before, but i had to replace my phone and i cant for the life of me find that file. ive been looking for hours and multiple forums but i just cant find it. if somebody could explain in detail how to get to that file or post a link to an existing thread it would be greatly appreciated. thanks alot
[Desire General] Noodled24:
Getting fed up with my blackstone, and the winmo "loading" icon. Looking to upgrade. The desire is my first choice at the moment but reading this forum has frankly terrified me.

Granted when I first got my blackstone there were lots of errors and horror stories posted in the forums and mine has been fine, so on that level I'm willing to take the risk.

The bigger issue is moving from Win6.5 with manilla, to Android 2.1 with sense.

Android seems fairly solid now. But watching the Google I/O Keynote, I wasnt thrilled with the way they intend to deliver adverts...

1) I'm guessing there isnt much difference between manilla and sense - different layouts etc, but 99% of the features in manilla are surely available in sense too?

2) Are there any common WinMo features that Android isnt capable of? I've read that android cant play some of the more common video types?

3) Google seem to be updating android a lot. HTC updates seem at best infrequent. Have HTC updated their previous android devices to the latest version of the OS / Sense?

4) Can anyone speculate on how long the desire will be upgradable? For example, i'm guessing the first 'google phone' the G1 is nowhere near powerful enough to run Froyo? Even in the mobile world 18 months seems a short lifespan for a device, since most contracts are now 24 months.

Thanks for any help. I had planned to nip to my local Orange shop and try to get myself one today, but had a few reservations and found it cheaper online. Anyway, cheers again.
[Desire General] XDA mark:
First of all, I moved from a leo (HD2) to the Desire. Overall, the Desire is an amazing experience. Android is also starting to become mature. And Sense ui almost only adds stuff for a even better experience.

Previous devices have been updated once, as far as I know. But HTC is not even that bad: Samsung usually does almost nothing at all regarding updates. The only device that is sure to be updated a lot is the Google phone, N1.

2.2 is coming soon for the Desire. The next version is still far away. But since the Desire's hardware is so highend, there is a chance for the Desire to be updated for the second time.

I recommend the Desire.
[Desire General] djet:
2) Have both HD2 and Desire. If you are deeply insane on Exchange / Task / Time management Android is a poor's choice for now. No native Exchange support at all (Froyo seems to change this but I haven't tried it yet), average OEM (HTC) client with some rather limited Exchange functionality (no tasks) and a few clients by ISV none of them are close to Pocket Informant. The latter is expected sooner or later but likely not this year.