Seems to me that pressing button on my BT headset does not activate Voice Dialer properly. I can't hear confirmation sound and it just stuck in Voice Dialre screen. That only hapenes when device in standby mode. When it's ON - everything is fine. Anyone got the same problem?
Ok, anyone can confirm this with their KJAM please?
I had the same thing. I hard reset and the same again . Its a s if the K-Jam does not wake quick enough from standby. I found if I clicked the button once , left it then clicked the button aagin it worked. This is in the known problems for the SP5 but not in the Jam... Email sent :wink:
Okay so I think I know at least A solution but I'm hoping that someone here will be able to suggest something besides a hard reset.
I've got a Cingular 8125 a couple of weeks ago. Flashed it to the latest imate rom. I kept it from installing the custom imate stuff but did install some of the Cingular cabs.
Now I'm having a few problems with the phone. It's quite a list.
A) I can't enable wifi at all. At one point I could but the phone locked up on me while I was trying to resetup my connection. I had no choice but to soft reset it. Now I can't enable wifi at all. If I click on it in the comm manager to turn it on it will sit there with the spinning wheel like it's enabling then go back to the same icon with the x on it. I've tried turning flight mode on and off, etc but nothing seems to help it.
B) the phone HAS been locking up. It will just sort of freeze and stop responding. Sometimes I'm able to get to the memory settings in control panel and still have available memory (it's usually been around 16 MB of program memory when this has occured) but even so closing everything will often not help. Even if it unfreezes then it will usually do so not much later and often it just won't unfreeze.
C) sometimes I can't close out the phone application. This seems to happen when Magic Button is running. I click to close it and it goes from the phone to my call history. Closing that goes back to the phone again. I can't get to the Today screen. Pressing the red hangup button would sometimes fix it but usually not.
D) voice command is REALLY wonky using my BT headset (Scala 500). Okay, I know it doesn't officially work with BT headsets and I could live with that. But why does it have to be so damned random?
1) Sometimes pressing the button once will get me the chime. Usually it just gets me a lower pitched tone. If the first press doesn't get it then typically a second within a short time will. Sometimes it takes three though.
2) At one point the phone would usually play my selected ringtone and announce the incoming call over the headset. Other times I would only get the default incoming call sound on the headset and the phone and voice command announcement are over the phone speakers instead. In the last couple of days I've ONLY been getting them from the phone.
3) While typically when I'm using the headset with voice command the feedback DOES come over the headset, sometimes it gives me the confirmations from the phone instead
I think there were a few other flaky issues too but this is the majority of them. Also many of them were present before the rom upgrade so I don't think it's responsible for most of it.
edit: oh, one other thing is that after the ROM upgrade I can't get the default input to stay on anything but keyboard. Even if I change it, I turn around and it's back to keyboard again. I'm thinking, though, that there's a reghack for this?
*bump*
===A) I can't enable wifi at all. At one point I could but the phone locked up on me while I was trying to resetup my connection. I had no choice but to soft reset it. Now I can't enable wifi at all. If I click on it in the comm manager to turn it on it will sit there with the spinning wheel like it's enabling then go back to the same icon with the x on it. I've tried turning flight mode on and off, etc but nothing seems to help it.==
I have the same problem with you. Can anybody help?
any solutions i have the same problem
Try this: back up your PIM, then flash phone back to OEM ROM (cingular, t-mobile, whatever it is for your model). Then unlock it again (if needed), and flash the ROM again. If it's still garbage, try reading the thread for the ROM you loaded (chances are you're not the first to experience this problem, and the other testers of that ROM may offer solutions). If it's still garbage after all that, consider using a different ROM altogether. CRacing's CR86 Touch HD and SVI's ANGEL are both quite nice, and VERY reliable for functionality.
wtf?! They all worked fine an hour ago (power, camera, talk, softkeys, messages...) and now they don't. It isn't a hardware issue because when it goes into standby, I can press the power button to bring it out of standby. Now though, I can't open anything using their respective keys and can't power it off. Anyone have any issues like this? I hadn't installed anything or even been using the phone from the time they worked to the time they stoped working.
Try opening settings -> buttons ->lock and click in "dont lock keys"
Had similar problems that now for some reason went away.
/d
dodgy said:
Try opening settings -> buttons ->lock and click in "dont lock keys"
Had similar problems that now for some reason went away.
/d
Click to expand...
Click to collapse
Unfortunately, I tried that and it didn't fix it. It's so odd that the Comm Manager button works when the phone is on and that the power button will work to turn it on or to wake it up. Are there places in the registry that control what the buttons do? Maybe I need to reset this thing? I love this phone when it isn't locking or acting up.
So I reset the phone to it's factory settings. After I went through the calibration and setup, the keys still weren't working. Before I did the reset, I did notice the keyboard keys weren't working either . So after the reset, the buttons still weren't working. I kept just typing stuff in on the keyboard with Word open and it finally started working...all buttons are still working now, but I don't trust it much. Should I bring it in to Cingular to get a new one? I'm still within my 30 days
Yes. If you can get a new one do it. do it.
Well a few days ago I went on a barrage and installed a bunch of apps like Gyrator 2, SensorLock, LevelSight, HTC Home, Ultimate Launch, HomeScreen ++.
I also coincidentally noticed two problems now First is when the device is on and I press the power, it doesn't turn the device off! Second is the HD is supposed to be able to detect the status of the stylus so when you pull it out in a call it opens the notes application. I also checked with Gyrator 2 which shows what the system reads for the stylus status and it no longer detects whether the stylus is in or not!
I'm going to try to uninstall each app one by one... but do any of you know whether there might be some other problem?? Or if someone's experienced the same thing, what are some recommendations to remedy this issue?
Each day of using the HD more and more problems keep popping up... I didn't drop $900 on this phone for nothing ><"
Do you also have problems with the volume buttons? If so, then perhaps your keypad service isn't running. You can check this with task manager v3.1
cardefbel said:
Do you also have problems with the volume buttons? If so, then perhaps your keypad service isn't running. You can check this with task manager v3.1
Click to expand...
Click to collapse
Ahh nifty the volume buttons don't work. Now how to turn this back on... hrmmm... time to poke around.
I had this problem when using MobileMagic for auto rotation using the G-Sensor. Uninstalling this fixed the problem. I now use ChangeScreen and find that this works better for me.
Hope this helps.
cardefbel was right it was the keypad service, I must've turned it off while messing around in the registry, should be more careful next time...
Turned it back on and everything works fine now. Thanks!
Hello all,
I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed.
Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear.
Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates.
I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue.
This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input.
Thanks.
Hi there, i am facing the same issue since two days now
First i am unable to come up with the physical home button issue and now there is this new issue. The phone does not respond after a call and the screen remains off and does not respond to any touch (double tap) or even the power button and home button pressed. I had to take the mobile into the recovery mode via home buttons power button and volume rockers. Is there any possibility of this getting fixed. I think i made a huge mistake purchasing this phone.. Slowly getting into problems one by one.. First the physical home button issue then this screen off issue. Checking for updates daily but seems like ZUK officials and Cyanogen are sleeping! Highly disappointed!!!!
In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue.
Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen?
ingtrans said:
In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue.
Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen?
Click to expand...
Click to collapse
Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue?
Sydarij said:
Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue?
Click to expand...
Click to collapse
Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all.
ingtrans said:
Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all.
Click to expand...
Click to collapse
After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy!
Sydarij said:
After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy!
Click to expand...
Click to collapse
This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. )
In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that...
ingtrans said:
This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. )
In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that...
Click to expand...
Click to collapse
Yes, the accidental wake up is set yet the issue cannot be resolved. Any other way you can resolve this and prevent the issue from reproducing? In my opinion, ZUK and Cyanogen officials are asleep after launching their new flagship. Dont see any updates coming from them since last 2 months. highly disappointed with this!
Sydarij said:
Any other way you can resolve this and prevent the issue from reproducing?
Click to expand...
Click to collapse
No idea. The solution I found seems to work well for me, at least I have not had any issues since I applied it.
Please turn on adaptive brightness. Issue will be resolved
ingtrans said:
Hello all,
I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed.
Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear.
Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates.
I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue.
This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input.
Thanks.
Click to expand...
Click to collapse
Hi! I'm facing the same issue for the last 3 days. I felt everytime there is any moisture of sweat on the ear piece the phone hangs and doesn't get unlocked.
Will try shutting the double tap options. Hope it works! This is the first time I've brought anything in the launch sale without reading reviews. Hope I don't regret this.
sir when call come rintone accor but calling display doesn,t show
when i press phone icon in menu then it shows
phone is lenovo zuk z1
screen freezes during/after call !!
did you solve this problem?
i too have posted the same problem here ..
any sugesstions?
i am facing a black screen while calling and receiving calls on my zuk z1 .. any solution? and where do i find the proximity setting in my settings?