Database Develop

Are the usual annoying bugs in the Kaiser?

Hi, I'm considering going back to WMobile phones and seriously considering the Kaiser. I currently have the N73 but had many wm5 phones before, SPV m600, Trinity, XDA Orbit, Wizard etc etc, all had annoying little "bugs".
I know the Kaiser is only just out, but can anyone tell me if you have noticed any of the following?
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
2) delay in waking up.
3) slow response in dialing, i.e. when pressing a number on the dial pad.
4) Missing incoming comes, i.e. full reception but people unable to get through. Extremely annoying.
5) Rebooting itself
6) Alarm not going off.
Hows the call quality?
Anyone used and have any issues with the T9 pad, think that's what it's called. I use to use this, but gave me problems when i switched back to virtual keyboard, e.g. wouldn't switch back at all.
Sorry for all the questions.

1) Haven't tested this yet, i'm hoping this isn't the case though...!
2) Wakes up pretty quick, no unbarable lag
3) Same as 2) - all seems pretty responsive, no bad lag
4) Never had that issue before, don't expect to get it with the Kaiser
5) Nope, although i haven't installed any other apps etc yet...
6) Same as 4)
I can only really compare with the Universal (as that's the only other WM phone i've owned)... my initial impressions are that it's a lot quicker than the Universal... maybe that's partially due to the fact that i haven't installed any bits yet... or really tweaked it.
The 3 second delay was REALLY annoying.... as i'd have to start every phonecall with: "hello....... hello? heeeelllllllllo?" lol... i hope this isnt the case with the Kaiser!
Also i think a lot of the noticable improvements are also due to the fact that im using a vanilla HTC phone, as opposed to a crappy T-mobile 'runined' one! Also i think WM6 has brought in a lot of changes which are noticeably improved over WM5.
EDIT: oh and the only thing that really 'bugs' me - is that i'm used to the lovely VGA Screen of the Universal, so dropping down to QVGA is rather noticable... text looks blockier and using Cleartype seems to make it alot fuzzier than on the Universal.... but that's my only really negative point so far.... hopefully it'll be the ONLY one
EDIT2: Something else i just thought of.... the fact that when my Universal locked up... if i didnt have my Stylus on me (which i usually didnt) and i didnt have a small pin-like object to stick into the reset hole... i was SCREWED... which REALLY pi**ed me off.... countless times i'd be on the train home from work, about to email a friend... only to have my phone lockup... then i'd have to wait an hour before i could reset it and start writing... GRRRRR. Anyway, the Kaiser actually turns off when you hold down the power button... simple... and GREAT! (the power button on the Universal was so stupid.... in my opinion.... was there any way (except by using 3rd party apps) to actually turn the damn thing OFF?! lol)

Hi
hongsit said:
Hi, I'm considering going back to WMobile phones and seriously considering the Kaiser. I currently have the N73 but had many wm5 phones before, SPV m600, Trinity, XDA Orbit, Wizard etc etc, all had annoying little "bugs".
I know the Kaiser is only just out, but can anyone tell me if you have noticed any of the following?
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
2) delay in waking up.
3) slow response in dialing, i.e. when pressing a number on the dial pad.
4) Missing incoming comes, i.e. full reception but people unable to get through. Extremely annoying.
5) Rebooting itself
6) Alarm not going off.
Hows the call quality?
Anyone used and have any issues with the T9 pad, think that's what it's called. I use to use this, but gave me problems when i switched back to virtual keyboard, e.g. wouldn't switch back at all.
Sorry for all the questions.
Click to expand...
Click to collapse
1) The delay is/was caused by the CPU/OS coming out of standby. With PDA type Windows Mobile devices they have a standby mode where the whole operating system is suspended. The mobile chip remains powered and when a call comes in it has to send a wake up request to the CPU and OS. It is the time the CPU and OS takes to become responsive that causes the delay. I noticed this delay was quite a lot on the Toshiba G900, several seconds or rings before it had woken up to sound the internal audio to alert you to the call. Sometimes it wouldn't wake at all :-(
The Kaiser wakes very quickly, hardly any delay at all, they have certainly put in a lot of work in this area.
Windows SmartPhones don't have this problem as they remain "always on" so respond without delay even though they may look off.
2) Answer above, very quick, almost instant.
3) Seems okay to me.
4) This is probably the OS failing to wake up, I would doubt this happens on the Kaiser.
5) Okay so far.
6) This again is related to the CPU/OS failing to wake up to a request. It is likely the phone you have experienced this with has some problems waking up when asked and would explain all your concerns.
Hope that helps.
Regards
Phil

I read on another thread regarding the assembly which houses the green and red call buttons being loose. What is the opinion of other users over here. I am asking this as I am considering buying one soon to replace my Touch
Regards

Yes the whole section moves slightly on mine, it must just be where they float on a rubber section underneath.
I hadn't noticed this until now, why is this a problem? If it was fixed two tight the keys would scrape against the sides when pressed. Makes sense there is some space.
Regards
Phil

The buttons feel a bit 'loose' but no more than in any other device (the buttons on my PSP for example).

Thanks for the reply guys, kaiser sounds promising, just hope it continues to impress.

hongsit said:
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
Click to expand...
Click to collapse
There are two contributors to this:
One is a registry entry, where all of the "standard" options cause a 3 second pre-ring delay and 3 second delay between rings. This can be fixed in the registry.
The second is network delay. The caller will hear ringing before your phone rings (usually 1-2 rings) no matter what phone you use. I've had such delays with every mobile phone I have ever used, smart or not. If you try the registry hack (search around for the exact key, numerous posts on it and I can't remember the exact registry key at the moment) and are still not happy, you have one option to reduce ring latency - get a landline.

Turning things round...

OK,
After a week or so with a Diamond things are finally getting turned around enough that I can appreciate it.
Please don't think this post is just one of the usual wailing complaints posts -as stated I 'm beginning to finally like the device - but somewhere there is a line between ranting that the phine is crap and worshipping the thing. I also think we need a post that can list the things that need fixing the most urgently, and any temporary workarounds for newbies (I know they are there but spread over many large posts).
The Diamond is a great phone let down by a few bugs.
However:
My battery life is now acceptable since I used the Advanced Config program (details in other threads) to disable GPRS auto-attach. This made a large diference to my battery life, and seems to be about the best thing you can do to improve the phone!
I've also updated to the wonderful custom Comm Manager to turn off 3G until I need it.
I applied the speed tweaks in the first post of this forum, which certainly helped, but was still getting slow and jerky response form TF3D, so have decided to replace TF3D with SPB Mobile Shell 2 for now, which works really well on the Diamond and is also gesture controlled (there's a free 30 day trial). (BTW, I'd LOVE someone to get the old HTC TouchFlo to work on this device as an alternative).
This is my choice, not a complaint(!), others love TF3D I know...
The built in audio player is quick to access, but way too limited feature-wise for me, so until someone can port across HTC Audiomanager I am using the free trial of Pocket Player. I've added it to my programs. This also has a built in pre-amp so I don't have to use AudioBooster (which causes the lost bass bug). (IMHO, you need some sort of pre-amp as otherwise all players are too quiet - at least for my ears which have been bashed by loud music for too long...)
Unfortunately it still skips/jerks every few songs as do all players on the Diamond - others also report this also - definitely one for HTC to look at...
Every time I use the phone I now quickly flick the volume up and down before turning it off . So far this has preveneted the dreaded lost all sound bug that other users and myself occasionally get (and I don't even use Bluetooth!). I can live with this, but it's happening to lots of users so I suspect HTC are working on it for the next update.
I'm told the memory leak is a Windows 6.1 error rather than HTC's but we will wait and see. A soft reset every morning is the best cure for now.
So, still some issues (and this is not forgiving HTC for them) but there are always problems and bugs for those who go for the first releases of software. However, what I am saying is that the phone is usable, and even enjoyable, until HTC get these issues sorted.
And I really hope some clever bod is busy working away on getting the old TouchFlo and AudioManager/Booster system working for the Diamond! A small step back perhaps, but it worked so fluidly and easily with my large fingers
Just my thoughts. A.

Did you found a way to use Pocket Player with bluetooth A2DP access?
I can't over rule ouchflo/WMP player priority to control Pocket Player from my HDH980 Sony Bluetooth headset, it always starts the integrated WMp-Touch flo player...
or , as you mentionned, you only use corded headset?
good review -points you mentionned by the way !

if you want the old touch flo try this:
http://www.touch-commander.com/

Unfortunately it still skips/jerks every few songs as do all players on the Diamond - others also report this also - definitely one for HTC to look at...
Every time I use the phone I now quickly flick the volume up and down before turning it off . So far this has preveneted the dreaded lost all sound bug that other users and myself occasionally get (and I don't even use Bluetooth!). I can live with this, but it's happening to lots of users so I suspect HTC are working on it for the next update.
Click to expand...
Click to collapse
it what's in the package is not good enough (and most of the time is not) use program that are made special for yr scope.
i experienced perfect a2dp audition using corepalyer...p e r f e c t! no skipping, sophisticated equalizer, all the 9 yards i highly recommend it!

Nice post. Let's hear some more configs that make the diamond useful. EVERY htc in the past has started off as a piece of crap, and has grown to be awesome (with a few notable exceptions like the jasjam which was always a dog). I've always been SA' earliest adopter (usually buy the first or second unit in country) and as a result, face more frustratuion that later adopters, but still swear by them. Inevitably the solution lies in constructive posts like the one above.

craigiecraigie4 said:
Nice post. Let's hear some more configs that make the diamond useful. EVERY htc in the past has started off as a piece of crap, and has grown to be awesome (with a few notable exceptions like the jasjam which was always a dog). I've always been SA' earliest adopter (usually buy the first or second unit in country) and as a result, face more frustratuion that later adopters, but still swear by them. Inevitably the solution lies in constructive posts like the one above.
Click to expand...
Click to collapse
I should have written the above myself.
For sure it is more challenging and rewarding to be part of the trend setters and making these crappy devices working the way they should do.
I am as much looking forward to have a Diamond which will increase its performance like my TytnII did (which now is faster in general than the Diamond)
Looking forward to contribute where I can

KukurikU said:
it what's in the package is not good enough (and most of the time is not) use program that are made special for yr scope.
i experienced perfect a2dp audition using corepalyer...p e r f e c t! no skipping, sophisticated equalizer, all the 9 yards i highly recommend it!
Click to expand...
Click to collapse
It IS a much better audio player - the preamp feature is awesome, and music sounds heaps better than the built in player - BUT I've already heard a skip...

salada2k said:
It IS a much better audio player - the preamp feature is awesome, and music sounds heaps better than the built in player - BUT I've already heard a skip...
Click to expand...
Click to collapse
s**t happen

KukurikU said:
s**t happen
Click to expand...
Click to collapse
Good observation

How to replace TF3D with Spb Mobile Shell?

GPS-lag: A misunderstood feature

Hi,
I read a lot of threads about GPS-lag on the Diamond, and found no such effect on my device. Finally, I remembered one thing which I learned about GPS-devices a long time ago:
Most of them use a feature called "static navigation" which effects the behaviour at slow speeds or stand-still, especially when walking. This is a feature which the developers of the devices may choose to activate, but it is usually not at the user's discretion to enable or disable.
When static navigation is active, the device will give less information when it moves at low speeds, typically at least up to 6km/h (ca. 4mph). Above this fixed speed, it behaves normal, under this speed, it will not give speed- or directiondata, and will often average the location data, so not every movement will be reported to the software.
When static navigation is not enabled, the reading tends to "jump" when the device is standing still, like in front of a traffic light. I remember my first receiver which had no static navigation, and when I stood at a crossing, the software would reroute after some seconds. The reason: My GPS showed me on the wrong lane and in the wrong direction, and the software believed that I was on the wrong road and had to reroute.
While static navigation is a little annoying for pedestrians, it is a blessing for people who use their devices in a car or on a bike. Here, it will smoothen the operation with road-bound software a lot.
Fwiw: I can experience the same thing. When I move by foot, the reading in Google Maps will lag a little, however when I'm on my cycle or in my car, the reading is very accurate. I have no real problem with the lag in GMM, and prefer a device which works well with Route 66.
Have fun!

this information isn't new it's in most of the threads and your post is misleading. early on you claim you don't have a problem on your device. whereas what you mean is that your device behaves as everyone else's but it doesn't bother you.
edit: I see you have edited

i interpret that as,
"my device behaves as everyone elses, and here's why.."

my icon is shown about a block behind where i actually am while driving through nyc at 30mph. that's unacceptable. your big words and lengthy explanation don't make it no better lol

MY GPS works fine once it gets a lock. But it takes a while to getb that first lock. No real lag that is noticable.

Refurb ATT Tilt Performance

OK - I bought a refurbished Tilt for $110 in 12/08 - not an interesting statement in and of itself, but I've been reading the forums, and I'm pretty sure that my device does not have any of the issues that other people are having with their devices. My 2D menus react quickly, just like any other touch screen device I've ever seen, and there is maybe a fraction of a second delay when I open a program from the start menu to when it loads (also well within the realm of expectation). I can play 3GPP movies on my phone in full screen without any resolution or playback issues. When I hit the volume bar on the screen to adjust the volume during video playback, there is also no lag or performance issue of any kind - the video just keeps playing smoothly. I know that was an issue that was cited in a bunch of threads. Works great in full screen video playback mode too - just like watching a movie on my computer (tested with a copy of Midnight Meat Train and works great). I was also able to remap my PTT button right from the preferences menu - no CAB file or external hack needed. I was really hesitant to buy a Tilt based on all the negative feedback - mine performs like a dream. If this sounds different from your Tilt, let me know - if it turns out my refurb has a different version or patch or something, I'd be happy to share it.

Hello,
Maybe You can start by sharing what OS, ROM version and radio version did Your Tilt used, so our friends will knowing it, and try it.
Thanks

Ok
Hmm... being a noob, how exactly can I figure that out? Is there a way to access an info screen in the phone?

Nevermind
Duh:
ROM version: 3.57.502.2 WWE
ROM date: 07/17/08
Radio version: 1.65.21.18
Protocol version: 25.88.40.05H

I have the same ROM, version, Date, and Radio, and I experience a similar level of speed. Programs take from a faction of a second to 2 seconds depending on the size, but for the most part it's pretty responsive. I haven't quite found the right size for videos, I use an ipod format and they are just a touch laggy on fast moving scenes, but no sound lag at all, and the volume change doesn't affect it at all. The only noticeable lag I notice on my phone is when switching to landscape mode, it takes several seconds for my typing to register.

I inadvertently purchased a re-furbed Tilt about a year ago.... Needless to say I was pissed. But to date I have had no issues whats ever. With the exception of Active sync coming on randomly Its fast on every level and always does what I tell it... Smoothly and cleanly.
I love this phone!

Switching Orientation
"The only noticeable lag I notice on my phone is when switching to landscape mode, it takes several seconds for my typing to register."
Re-mapping the PTT button as the landscape orientation control helps knocks out some of the lag (usually takes 1-2 seconds). If you use the shortcut button to manually orient the screen, the auto-orient on slideout feature diasables itself, which is nice.

COMPETITION - Pebble Air Drums

Hey all! My name is Alex Markley and I was ecstatic to have my app idea selected as a finalist for this app development challenge!
My app idea is simple: Strap a pebble onto your wrist, fire up the companion drum machine app, and go to town on your air drums! (Drum stick optional.)
I'm a tad behind on my announcement and setting up my project but I am an experienced Pebble developer (I made the semi-popular Roku Remote app) so I expect to deliver on time!
I'm looking forward to engaging with you, the XDA developer community, as the contest progresses!
Thanks,
XDA:DevDB Information
Pebble Air Drums, Device Specific App for the Pebble
Contributors
alexmarkley
Version Information
Status: Testing
Created 2014-08-21
Last Updated 2014-08-21

Updates
August 27th, 2014 -
I'm disappointed to report that in my testing the latency in the communication between the Pebble and the host device is far too high to allow my app idea to work. In order to play an instrument in real time you really need a latency of less than 10 milliseconds for a reasonable experience. Anything above 25 milliseconds is absolutely unworkable. In my tests with Pebble, I have routinely measured message ack times of well over 150-200 milliseconds, with spikes of almost 2000 milliseconds!
Now I freely grant that these numbers represent message round trip times, not one-way message times, but I don't know how to measure the actual time between message sending and message receiving between two separate devices. (Presumably the one-way time is roughly half of the round trip time, but the measured jitter is so high I have no idea how reliably that could be assumed.)
Because of this uncertainty, I did actually implement simple drum machine functionality, allowing me to trigger drum samples directly from the watch. Unfortunately, it was as I suspected. The drum sounds were so delayed as to result in a sad mess whenever I tried any kind of rhythm.
I have tried a number of things in my attempts to speed up the delivery of AppMessage dictionaries. I have reduced the size of the dictionary to a single uint8. I have set app_comm_set_sniff_interval(SNIFF_INTERVAL_REDUCED). None of that has even made a dent in the problem.
Unless somebody can suggest a way to dramatically improve this problem, I am afraid I must withdraw my app idea from the contest.
Thanks for reading!
--Alex Markley

Reserved

@alexmarkley: Too bad. Your idea was my favorite. Pebble Corp should really make some effort to reduce the lag between the watch and the phone. I don't know the BlueTooth standard in details, but I doubt the lag would be its fault as I use BT tethering on a daily basis without any problem.

Alex,
I was also looking forward to seeing your app work. I also ran into the variability of response time between messages when I tried blasting the titles and subtitles of 100 menu items from JS to C for my Food Trucks app. I did a timing of this yesterday and it took an average of 20 seconds to send over that amount of data to the watch. Since I was able to scroll down concurrently to data streaming, I inserted a little wait message until the actual text showed up.
I also experimented with SNIFF_INTERVAL_REDUCED and it maybe only helped 10%, if at all. I decided to leave it out of my app, as I wanted the app to be battery friendly.
Good luck next time.
Mike