Related
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.
Im sure a fair number of you will have experienced the same thing where you press a key once and you get like 3 of that letter and sometimes for me the Fn key doesnt work too well either
i've tried like swirling the keys around to move dust etc but it didnt help
maybe i should just send it back? becuase its really annoying
I also have this problem sometimes. Thought it might be a software problem or so, but maybe you are right and particles are collecting there.
Did someone try that on X1?
Well, if there was such a solution I wouldn't have to send my X1 to the service centre. And just delaying it as much as possible, but given that my warranty ends next week, I'd probably have to go down soon. And anyway, it's not just repeats that I'm facing. Sometimes it's the other way round, as in the keyboard not responding unless I press the key down real hard.
Mopral said:
Did someone try that on X1?
Click to expand...
Click to collapse
just tried, and seems to work! thanks
settings-personal-buttons-up/down control
delay before first repeat set to long
repeat rate 3 from fast
works good!
I'd say it works about 80-90%. It does save the X1 from the trash piles, so kudos to the friendly guy who dug up the solution, and no kudos to SE and/or MS who can't think of fine-tuning the keyboard settings before they ship a product that was $800-900 unlocked at launch.
Caveat and an inappropriate rant: I remember doing so much research, and everyone across so many different forums said a hardware keyboard is the way to go if you do a lot of texting. Not true. I find that hardware keyboards require a lot of efforts to press compared to a virtual keyboard, even worse if it's not spaciously laid out, and even worse if, unlike the X1, the positioning of the keys relative to each other is off.
Truth is I type even faster on an iPhone/ipod touch than an X1, without feeling like an RSI is coming on, and it's not because of predictive text entry. It's because my thumbs can use a lot less force on the keys. I believe most people still press way too hard on a touch screen trying to be control freaks.
So the keyboard may be 80-90% improved, but I've got my budget ready for an iPhone. And no more listening, no more being open to suggestions!
beingthere said:
Caveat and an inappropriate rant: I remember doing so much research, and everyone across so many different forums said a hardware keyboard is the way to go if you do a lot of texting. Not true. I find that hardware keyboards require a lot of efforts to press compared to a virtual keyboard, even worse if it's not spaciously laid out, and even worse if, unlike the X1, the positioning of the keys relative to each other is off.
Click to expand...
Click to collapse
Well, I don't want to live without h/w keyboard anymore. And I did a fast typing challenge against an iPhone and won. The guy who wrote on that iPhone was a real freak, had an iPhone since it came out and types really fast...but I love the h/w keyboard on the xperia. If it would not have this double-letter error I would love it even more...Now I'm going to fix it with the solution mentioned above. Thanks!
I just want to add one thing...
The reason I say the fix is 80-90%, is because I think CPU speed and/or power settings might contribute somewhat to the keyboard issue. Once last week, I had the phone plugged into AC, and the keyboard suddenly became free of issues, and responded properly to my typical typing efforts.
Using nueCPL-ClockSpeed v1.3 in an unscientific test, the keyboard produces more mistakes on a lower speed (384MHz), but its Max Performance setting didn't exactly reproduce the AC power remedy.
This is not a very stringent observation at all, but since I am stuck with the X1 for a while, I'll keep on trying I'm betting that the next iPhone will be a significant update, so I have to hold off the purchase for now... and kiss NRGZ28's toes for his rom's.
Sapa13 said:
just tried, and seems to work! thanks
settings-personal-buttons-up/down control
delay before first repeat set to long
repeat rate 3 from fast
works good!
Click to expand...
Click to collapse
for two days, since i set this way, not even one double or missed letter!
i've done everything you've all said but it doesnt work does that mean it is a physical problem?
comeradealexi said:
i've done everything you've all said but it doesnt work does that mean it is a physical problem?
Click to expand...
Click to collapse
really dont know, since i set that way no problem at all.. maybe dirt came under your keyboard
Anyone having a similar experience? Any sort of screen input seems to bog down really bad and finding myself having to retype things and hit keys again. Wondering if it is somehow heat related? Or some kind of software flaw? It happens with the stock keyboard and swiftkey as well. Any input is appreciated, thank you.
This happens to me all the time now. It is really annoying. I'm going to do a clean reinstall and see if that helps.
It happens to many people. I get this too sometimes when typing on keyboard, it will miss some of the keys/letters. It could be touchscreen issue and/or LG Keyboard issue. The interesting thing is that when I started to use the phone it didn't do that, but in 4 or 5 days it started to do that. I cleared the cache of LG Keyboard, but still didn't help. I hope LG gives us some sort of software update even if it is not 5.1.1. We need a normal working phone!
Yeah interestingly enough it happens mostly on the charger. When I'm off, it seems to be pretty much good. Although it does miss some presses on occasion if I don't press deliberately enough. It's almost as though the touch screen sensitivity is botched
Yes common lg issue. No idea why
change the keyboard and hopefully lg will send a software update to fix this and this only while charging also is your phone usable
What temps are you guys getting when the Keyboard lag occurs while charging for both battery and CPU?
In my case and also others have reported that keyboard lag occurs in any condition if the phone is charging and when it is not. I think I have eliminated the keyboard lag by disabling vibrate in LG Keyboard settings. Now don't have any missed key presses.
I get this when charging very time, and I don't use the LG keyboard. It's definitely a hardware issue. I don't use the stock LG charger though, but it doesn't sound like that would make a difference.
Hello all, here again with another issue that I haven't seen mentioned anywhere.
My sound and slow performance problem was recently resolved on its own after a complete revert to stock and back to running a custom ROM, but now I have another question. How do you know if the vibration motor is dead?
I took my phone apart recently to see what could be wrong, what could be loose, and what might be dirty, but everything looks really good, the speakers work, wireless charging works, everything seems fine. The only problem is that no matter what I do, vibrate will not work for anything.
Then I noticed what seemed to be the vibration motor, which is a little piece of metal with a rod going through, with metal rings that seem to just spin freely. It's still firmly attached to the motherboard, yet I get no vibration for anything. Even enabling it for my keyboard actually causes the keyboard to lag and skip letters, yet when disabled, its smooth as butter.
I also don't have any settings for vibration strength anymore in Kernel Adiutor, even after testing multiple kernels to see if maybe it wasn't supported.
Has anyone here had any of this happen before? I've already ordered a new motherboard to swap out with this one, but I just wanted to see if there was anything I could do to fix this, or hear what you all have to say. I don't mind spending the little bit of money to fix it myself, but if I could avoid shelling out about 60 for another motherboard, I would prefer to do that.
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Just to weigh in I also have this issue not very often but enough to notice it. Especially since the last update also when I zoom with the stock camera it just freezes.
I'm having similar issues, camera fixes if i reboot but thats annoying if your trying to get a moving shot, also noticed it sometimes freezes switching to portrait mode.
For the screen freeze I have found if i use my finger print to unlock when the screen isnt responding its starts to work. but i didnt have the problem until i put on a crappy glass screen protector.
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
godsfilth said:
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
Click to expand...
Click to collapse
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
jonchance_84 said:
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
Click to expand...
Click to collapse
hmm maybe, i only had show new notifications turned on but ill try turning it off and see how it goes over the next couple days
Ok so since turning off my ambient display, no issues so far.
karlkarloff said:
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Click to expand...
Click to collapse
I use Ambient Display and sometimes the screen behaves as you've described where it won't reach to touch, but I've always just given it time/pressed the power button repeatedly until the screen came on (or continued to tap the screen lightly)... never tried pressing down very hard.
Not to Necro a thread but I've experienced this aswell, infact it's happening right now as I type this.