I am using phiremod v6.1, but although I have heard reports that blutooth is working, it has never worked for me. Whenever i try to activate it, it appears to attempt to do it, but then turns it off few seconds later. At no point was I able to enable blutooth on my Nook Color.
Is this a common problem? Or am I doing something wrong?
Try turning off both wi-fi and bluetooth, reboot then turn on bluetooth.
And when you reboot, do it by slamming the Nook off by holding down its button for five seconds. That is what did it for me- a hard reboot.
Related
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.
Hi all,
In recent weeks my bluetooth is turning off when it isn't being used. I only use it for hands free in the car and up until a few weeks ago it always stayed 'On' however now, once disconnected from the car radio, it turns off again.
If I turn it back on away from the car it will go to 'Off' shortly after turning it 'On'.
It's a touch annoying as it means I have to get in the car, turn the engine/radio on, unlock the phone, set bluetooth to 'On' every time I drive and want the phone on hands free.
When connected to the car radio, the bluetooth stays on without problem, so I am not entirely sure what is going on.
I have tried turning battery saver off, restarting the phone etc. but nothing has changed this behaviour.
Has anyone got any suggestions on what I can try next, I'm a bit stuck!
Thanks
Long clicking the button on my headset no longer activates S Voice when in sleep mode. I've tried everything I can to solve the issue, but no joy. I bought a replacement headset in case that was the issue, but still the same. I've installed the Headset Button Controller app and tried the setting 'Prevent sleep mode', still the same. When I use the debug mode in HBC advanced settings, it detects all button presses apart from long click. It did work, but then just suddenly stopped. The phone is only about a month old, but I don't want to have to try and get a replacement. I'm just hoping that there's people far cleverer than me that might have some idea I can try and to fix this. Can anyone suggest anything? Thanks.
Hello again, nookies!
I've come across a small bug/problem on my Nook Simple Touch with GlowLight. Wondering if any of you might know the cause/how to fix it.
It's been happening for a little while, but I don't know when it started exactly. I've just been coping with it for a while.
So the problem is as follows: Whenever I either let my Nook go to sleep, tap the power button to make it sleep, or turn my Nook all the way off and reboot, if I had the GlowLight on directly before any of the above actions, for some reason my Nook doesn't register that the light was turned off when I turned off the device. I mean, yes, the light itself turns off, of course, but when I want to turn it back on again after putting it to sleep or even rebooting entirely, the light is still considered "On" in the GlowLight control window, and for me to actually turn it on again, I have to turn it "Off" first, and then back on again.
This is somewhat annoying, as I normally need to turn on my GlowLight at the lockscreen using the "hold the N button" function, but if I do after I had the GlowLight on before turning it off, I have to hold the N button for 2 seconds to get the Nook to think that the light is "Off", and then I have to unpress the N button and then press it for 2 seconds again to actually get the light to turn on.
Hopefully I wasn't all too redundant, but can anyone help me fix this little bug?
Thanks,
3N
I stuck with the original firmware my phone came with for ages, but eventually succumbed and upgraded to H990ds10i_00_OPEN_TW_DS_OP_1117.kdz
Everything seemed to go fine, but for some reason bluetooth turns on really slowly, either after restarting the phone or going into airplane mode, it can take ten minutes or more to turn on!
Once on, it works fine, but it is frustrating that it can take so long!
It doesn't matter whether you turn the bluetooth on from the settings menu or the notification shade, the bluetooth logo turns on temporarily but when you go back it's still off.