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.

Backlight turns on, then after delay, message or call arrives

Hi everyone,
I've searched the forums through Google extensively trying to find out if anyone else is having the same problem that I am, but haven't been able to find any related threads.
I'm using the ATT Tilt with Dutty's WM6 ROM and the .17 radio -- I've noticed that when a text message arrives and my phone is in standby with the screen off, the backlight will turn on and then about 3-5 seconds later, the actual text message will show up on the screen or the call will show up...
I'm not sure if others are experiencing this and if anyone has a solution to it -- its not the end of the world if I have to live with it, was just hoping maybe someone else experienced the same thing and had found a solution...
Thank you very much!

Gas Addict said:
Hi everyone,
I've searched the forums through Google extensively trying to find out if anyone else is having the same problem that I am, but haven't been able to find any related threads.
I'm using the ATT Tilt with Dutty's WM6 ROM and the .17 radio -- I've noticed that when a text message arrives and my phone is in standby with the screen off, the backlight will turn on and then about 3-5 seconds later, the actual text message will show up on the screen or the call will show up...
I'm not sure if others are experiencing this and if anyone has a solution to it -- its not the end of the world if I have to live with it, was just hoping maybe someone else experienced the same thing and had found a solution...
Thank you very much!
Click to expand...
Click to collapse
I have this too....I don't really mind though. I see it light up on my desk, look down, and watch my email/message appear.
I'm on Dutty's v4 and .11

Same experience here.
As long as this isn't the case with telephone calls, I can live with it
Having a 5 second delay on answering a phone call could make you miss the call...

dont really se the problem tbh, the phne wakes up when it starts receiving the message and then notifies you when its arrived - the lag you observe must be simply he time it takes to download the message?

Happens to me every time. I see my phone light up, and know I'm getting a message. When I get a call it lights up and instantly shows who's calling.

I agree this isn't so much a problem. I see it as FAD (Functioning As Designed).
See what happens is the Tower Sends a signal to the Phone saying (Incoming Call/Message Heading your way). It Wakes Up checks its Registry for What you set your Ringtone as. Tower passes the Call and It Rings. You Hit the Green Phone and You are connected YAY!
Now Messages are a tad different. The Phone wakes up looks for what your Message Alert Tone is. Tower Passes the Message. The Phone saves it, makes it into a readable format (If you have Threaded SMS adds it to the proper thread) and Notifies you that all is ready.

Same here, I like it. I can pick up the phone before it makes sound and have the phone already in my hand when the msg is showing up.

no different than when my non-3g phones would start chattering with the pc speakers a few seconds before an incoming call or message.

same here
i see no problem in this

snathanb said:
no different than when my non-3g phones would start chattering with the pc speakers a few seconds before an incoming call or message.
Click to expand...
Click to collapse
I loved that!
Ducka-Duck-Ducka-Duck-
Ducka-Duck-Ducka-Duck-
Ducka-Duck-Ducka-Duck-
Ducka-Duck-Ducka-Duck-
RIIIIIIIIIIIINNNNNGGGGGG

OT but... iPhone users are suing apple over that btw b/c it's blowing out their expensive home theater speakers. (no shielding due to thin design = DUCKA-DUCK-DUCKA-DUCK instead of ducka-duck-ducka-duck)

Sleuth255 said:
OT but... iPhone users are suing apple over that btw b/c it's blowing out their expensive home theater speakers. (no shielding due to thin design = DUCKA-DUCK-DUCKA-DUCK instead of ducka-duck-ducka-duck)
Click to expand...
Click to collapse
Nuh uh. Lol, when I had my iPhone I had no chattering at all, only on crappy speakers.

Sleuth255 said:
OT but... iPhone users are suing apple over that btw b/c it's blowing out their expensive home theater speakers. (no shielding due to thin design = DUCKA-DUCK-DUCKA-DUCK instead of ducka-duck-ducka-duck)
Click to expand...
Click to collapse
Yes I had a friend who went to the dark side and had a iPhone It was indeed LOUD. Never thought of suing Apple for it.
~~Tito~~ said:
Nuh uh. Lol, when I had my iPhone I had no chattering at all, only on crappy speakers.
Click to expand...
Click to collapse
Well Think about that statement how many iPhone users are smart? Most are trend followers and don't know much about speakers probably got sold to them by some "winner" at Big Buy.

I have the same problem.

on mine too, but only for messaging.

Same problem for messaging and calls. I pretty think this glich is for all HTC phones. Seen this on HTC touch too.

I've had many different PDA phones over the last five years and used many different cooked ROMS (starting off with the original WM2003) and this has always been the normal behavior. Must be by design.

Hmm, I dunno if its about being by design as much as it has to do with the fact that from wakeup to showing the message it takes much longer on a complex PDA than it does on a simple phone with no complicated programs or settings in it.
IMHO it seems that because of all the bulk of software running on a PDA with an OS and all, it just isn't as efficient at doing simple small tasks as a regular non-PDA phone is....which I guess is the price we pay for carrying little computers in our pockets rather than a simple phone.

Gas Addict said:
Hmm, I dunno if its about being by design as much as it has to do with the fact that from wakeup to showing the message it takes much longer on a complex PDA than it does on a simple phone with no complicated programs or settings in it.
IMHO it seems that because of all the bulk of software running on a PDA with an OS and all, it just isn't as efficient at doing simple small tasks as a regular non-PDA phone is....which I guess is the price we pay for carrying little computers in our pockets rather than a simple phone.
Click to expand...
Click to collapse
I would agree with that statement. My wife's razr lights up and rings instantaneously...but has the functionality of my big toe.

Alright Lets Put an End to this. this ISN'T a PROBLEM. Its how Phones Work If they are "asleep" or not in "Full Operation Mode" then it must "Wake" to fully operate the processes that are needed to do what it is asked. Start a Call, Receive a message, etc etc.
And just FYI, My Old V3 Razr would Turn on The Front screen a couple seconds before I received a message or a call.

Touch Lock Pro and Incoming Calls

I love the TouchLockPro Software, but it seems like the user has to unlock the phone before taking an incoming call, rather than the phone just unlocking automatically. Has anyone found out how to fix this? I've tried using S2U2 but it kills my battery too quickly. Any advice?

You should post in the threat of zuinige rijder ... here is the wrong place...
Greetz
Boris
xda-developers > Diamond > Themes, Applications and Software > [APP][Updated 22-12-2008] TouchLockPro v1.9.2 bug fix release

tilmees said:
I love the TouchLockPro Software, but it seems like the user has to unlock the phone before taking an incoming call, rather than the phone just unlocking automatically. Has anyone found out how to fix this? I've tried using S2U2 but it kills my battery too quickly. Any advice?
Click to expand...
Click to collapse
As far as i know thats "the feature". What use would it be if it unlocked in the pocket of your pants and answered itself by a random touch?

Skaryd said:
As far as i know thats "the feature". What use would it be if it unlocked in the pocket of your pants and answered itself by a random touch?
Click to expand...
Click to collapse
Indeed. And there is also the light sensor, which will auto unlock when there is enough light. In too dark conditions you can use the GSENSOR, Stylus or Capacitive NavSensor for unlocking.

Lock the screen when the face is upto the phone

Ok well i don't know exactly what to call this but i was hoping that there was an app out their that is like the iphone so that when i answer a call it shows me the normal end call and what not but when i put my face against the speaker (or more so the light sensor) that the screen would lock. I think that this would a great app because so many people end calls with their cheek that it is a bit annoying. but any way thanks for any help in advanced.

http://forum.xda-developers.com/showthread.php?t=466519
^^^^Try that, works a treat

thank you im downloading now =]

Ok well this works for the time being but now i was thinking someone could make an app that would turn off the screen when the light value gets below a certain point. (i would try but unfortunately i only know a little c++ and vb) so any one with the expertise if you could make it i would be highly appreciative. Thank you.

Incoming call screen

Hi everyone!
I have Samsung Galaxy S6, 5.1.1 Xtresolite Deodex. With TWRP.
I m bit annoyed of Samsung's native "Incoming call screen" because I always accidently decline incoming calls when I try to take out phone from my pocket. On my previous phone I didn't recognized that problem(iPhone 6).
Good solution can be to change method of answering calls from just simple "tap" to "slide to answer". I have seen this answering method also on the previous versions of Android(Kit Kat).
What would you suggest? I would appreciate any suggestion. But the best is not to use a separate application but just to modify its native calling screen(kind of addon).

you have settings/accesibility single tap mode or you can change the answering method from phone app/settings home button to answer

exivious said:
you have settings/accesibility single tap mode or you can change the answering method from phone app/settings home button to answer
Click to expand...
Click to collapse
It doesnt solve the problem because this will be just an additional method to answer. It will not prevent accident declines of calls. I would like totally replace answer and decline buttons on the screen by the slider.

sams979 said:
Hi everyone!
I have Samsung Galaxy S6, 5.1.1 Xtresolite Deodex. With TWRP.
I m bit annoyed of Samsung's native "Incoming call screen" because I always accidently decline incoming calls when I try to take out phone from my pocket. On my previous phone I didn't recognized that problem(iPhone 6).
Good solution can be to change method of answering calls from just simple "tap" to "slide to answer". I have seen this answering method also on the previous versions of Android(Kit Kat).
What would you suggest? I would appreciate any suggestion. But the best is not to use a separate application but just to modify its native calling screen(kind of addon).
Click to expand...
Click to collapse
Idk what you're talking but my S6 is slide to answer. You probably have something enabled in accessibility.

In my mind, i think incoming call screen should enable proximity sensor for off the screen when it in pocket, so when you pick it up u will not face the problem.
In daily use, I insert my phone in pocket in position screen outward of body. pick it only the margin of the phone.
sorry for my bad English

JoeFCaputo113 said:
Idk what you're talking but my S6 is slide to answer. You probably have something enabled in accessibility.
Click to expand...
Click to collapse
Thank you very much. That's it. I found of that it can be changed in Settings/Accessibility.