The title kind of says it all...
I purchased a Sony PlayStation 3 Bluetooth keyboard (this one). It's not exactly like the one in the picture... the keys layout is french, I guess (AZERTY, QSDFG, WXCWB). Also, M and ; are swapped, for example. Anyway... all inputs are the same as on a standard keyboard... just that the layout is different. Oh well, irrelevant.
I have a Samsung Galaxy Note. I tried it on my phone and my friend's phone (Note, too). It worked - all keys, even some shortcuts, and the trackball.
When I first paired to it, it asked for a key. I had to insert it on the keyboard then press enter or return. Then it was paired and would connect every time I switched BT on and clicked it.
That was yesterday. Today... I performed a full wipe and reflashed the ROM (TouchWiz-based ROM, ICS). Now, it just won't connect anymore! I keep getting a message saying "Couldn't pair with Wireless Keyboard because of an incorrect PIN or passkey". I wasn't even asked for a passkey!
I also tried CM9, CM10 and AOKP ROMs. Same thing!!!
The batteries are good... but I tried another pair of AA batteries, too, just to make sure...
What is to be done?
-----
Edit : earlier today, after several attempts (half an hour), I was able to connect again. I was asked to insert a number on the keyboard and press enter, and it worked. Now, after some more (many!) attempts, like 12 hours after (I was gone), it finally connected again...
But if I full wipe and flash another ROM, I'll lose it again... :/
Oh and before someone steps in and moves this thread over to the Galaxy Note Q&A section...
I tried the keyboard on a HTC EVO 3D, and the same thing happened. Connected first time easily. Then, after unpairing... it's hard to pair back. So I'd say it's pretty wide-spread, not only stuck to one device.
I made a backup of Bluetooth Pairings with Titanium Backup... performed a full wipe and flashed back the TouchWiz ROM I grew to like. The restore went fine, although the back up was from CM9... totally different ROM...
Oh well...
-----
I still wanna know... does anybody have any sort of solution for occurings like this? As far as I know, I'm not the only one who's had such a problem, and it's not really device/keyboard specific .
-----
So many views... yet no answer...
Related
Has anyone experienced their TP crashing during normal operation, and found the only way to recover is through a hard reset?
That's what happened to me last night. I'm running a stock HTC ROM that I upgraded when it came out (two weeks ago?) and the device was working without any problems up until then.
Last night though I was using Opera to browse a website and it suddenly became unstable. I closed Opera and found it wouldn't re-start so I performed a soft-reset. From this point on the device wouldn't go past the boot screen (displaying 'HTC Touch Pro' with the red version numbers - not even getting to the animation). I attempted to soft reset a few times (and even removed the battery for a while) but it still would not boot.
So I performed a hard-reset and restored a backup, whereupon it now seems ok again.
To give a little more info:
- the device was fully charged (had been on charge via USB all day)
- TF3D not installed - standard WM6.1 with SPB Phone Suite installed
- Browsing over wifi (bluetooth and HSDPA connection were also active)
- Running Opera 15613
- Just before the crash, a bug appeared whereby typing a single character into a website textbox (using the slide-out keyboard) would cause that character to be repeated a large number of times on screen - this has never happened before
I've always run the device with the stock HTC ROM and never had any issues like this.
Anyone had anything similar happen?
Yep, just had to hard reset then restore sprite...I was trying to play a song through tf3d and it froze. Soft reset only lead me up to the first screen that states radio version...yaddah yaddah yaddah...hard reset 'solved it'.
Does your phone got hot?
I had a problem while browsing over wifi. To boost the speed i changed power manegment to best performance in wifi settings and phone got hot in few minutes, opera crashed and soft reset didn't help either. But for me removing betery solved the case and also cooling the device a little.
hope this helps
BHole
BHole said:
Does your phone got hot?
I had a problem while browsing over wifi. To boost the speed i changed power manegment to best performance in wifi settings and phone got hot in few minutes, opera crashed and soft reset didn't help either. But for me removing betery solved the case and also cooling the device a little.
BHole
Click to expand...
Click to collapse
It gets warm sometimes, however in this case I'd only been using the device for a few minutes, so I think it was still cold.
I tried removing the battery but that didn't help.
Seems to be behaving itself since then though.
I got the same problem nearly every day. After a few hours (up to 12) it gets frozen. Only hardreset was possible. I got this problem since a view months. I'm trying now to leave one after another program not installed after every necessary hardreset. Currently i'm suspecting either WM6.5 itself, vAlert or some other mortscript apps. For now i don't installed vAlert and there is no crash since over 24 h.
The following programs are innocent:
- tf3d
- pointui
- SmsReportsEraser
Surprisingly enough, I had the exact same problem just the other day. I got my TP about two weeks ago and was still looking around here learning the ropes of flashing etc and the differences between it and the Mogul. I kinda liked the business card reader that came on the stock rom and couldn't find it as a cab anywhere so I was undecided on flashing a new rom. I also didn't like the TF3d so I wasn't running it. I was using the regular win today screen with spb weather and Phone Suite installed. Worked fine like that for over a week. I got a text message on Tuesday and the TP froze up, so I did a soft-reset. It got frozen on the boot screen just as you described. Fortunately I was able to in hard-spl from the micro disk to unlock it, then I installed NFSFAN's custom rom, also from the micro disk.
Not related to the topic, but I really like how that new rom functions. I added the telus radio as well and now the battery at least makes it through the work day. Before I had to charge it mid day! Only thing I miss is that stupid business card program from the stock rom. If anyone can point me to a cab I'd really appreciate it. I get so many cards its a pain to enter them all manually.
Thanks,
PhilyT
I just started having this problem a couple of days ago. This has happened twice now. Warm-booting did start the reset process (I would get the splash screen), but it never got past that.
i think theres a thread about this somewhere. The cause isnt known but they are trying to pinpoint the problem. Bad rom chip, software problem etc
I've also have been affected by this and its a pain... having to setup the device again.
Mainly this problem has to do with tf3d2 in my case as i try to save a contact each time it will free. So i have to manually enter a phone number and store it.
I guess its better than a hard-reset
been flashing roms for a while now and everything was great until recently. i have this annoying video pop up problem that i cant seem to figure out if its the phone or what. what happens is randomly the tv/video out pops up and the screen turns to landscape mode. then all sound is lost. ive flashed original stock rom but the problem still happens even running stock. i cant figure out if its the phone and i need to do a warrenty exchange or if its something else. i am hard spld and security unlocked. if anybody else has this problem or had this problem and know of a solution id greatly appreciate it. i dont think its the way i flash roms. i flash with sd card thats formatted fat 32. sim card out and hard reset after first boot.
Sounds like you are describing the TVOUTPopup feature.
Usually, the TVOUTPopup only appears when the A/V Cable (extra cable) is physically connected to the device.
At first guess, I would be inclined towards a faulty USB connector.
yes it is the tv out pop feature. whats wierd is that its the new look from a different rom build. whatever rom i run (right now stock). when the screen comes up it turns landscape and has 4 colorful icons to choose from. internet,youtube,photos,and powerpoint office. once i hit the x button or hit close then it will keep repeating and keep the screen in landscape even though i havent slid out the keyboard. after multiple times closing the app it will stop doing it for a bit but then do it again few hours later.
Since you've tried different ROMs and are seeing the same behavior, I'm inclined to think it's hardware related. Assuming you have nothing connected to the device at the moment except for the SIM, examine the USB connector very closely for signs of damage.
If all looks ok, perform a hard reset and flash the Official HTC 5.05.405.1 ROM/Radio (should eliminate possibility of garbage in ROM) to the device and confirm that the behavior still occurs. If the problem persists, that would confirm it to be hardware.
HTH,
well i flashed the new att fuze rom. so far so good. no popup yet. this happened before though when i thought i fixed the problem. but after running a new rom for about 4 days it came back. if it is a hardware issue then my fuze needs to be exchanged right? thanks for all your help.
I have same issue with my FUZE (constant "Video Out" pop-up message, often switches to landscape mode, sound is off). Have you found any solution to this?
P.S. ...
I have an extreme problem with my Nexus. I've been through thick and thin with this phone, and I'm hoping you guys will help with a solution to this problem.
The power button to my Nexus is broken completely. I stabbed it so much that the clicking black part is completely removed from the slot (on the motherboard).
One time, my Nexus S died, and I realized I had no way to turn it back on. I tried every single method (battery pulling, button pressing, USB connecting, etc) with no answer. I finally was able to find a solution. I used Odin to restore the bootloader tar md5 file, and thus auto rebooting the nexus (when the box is checked). This worked like a charm, until I realize I made a fatal mistake.
I chose an md5 file for the ORIGINAL Nexus S (not 4g).
I was able to easily go into recovery with Quick Boot from the Play Store. I installed Raspbean Jellybean (02-05-13 build), but the installation was very faulty. The home button is nonfunctional (it vibrates when pressed, but nothing happens) and Browser is not working as it just closes itself instantly. Like an idiot, I didn't install Gapps before rebooting into the ROM.
Stuck in that dilemma, I used the built in email app to sync my Gmail account to the phone. I sent a Quick Boot APK to myself to try and open so I could reach recovery, but it said there's no type of program that can open that file (maybe because Gapps isn't installed).
The last thing I tried was Odin again. I tried to restore the ICS release keys, but Odin will not recognize my phone anymore for nothing. I tried 3 different USBs (2 with shorts, and 1 normal one. I don't know if the type of USB has anything to do with it). Nothing.
So here I am with a faulty, Gappless ROM on my Nexus S 4G with a completely broken power.
I'm wondering if you guys have any solution/suggestion to get Odin to recognize my phone again so I can restore it and work from there.
Apart from that, ANY solution to this problem is highly acceptable and greatly appreciated (ways to get into recovery, etc). I don't want this to be the last of me and my sweet ole Nexus =(,
Thanks x1000 XDA!
Hey Guys. I was actually able to reach recovery, because the ROM I'm using has a Power Menu widget in it's quick settings (Go Figure). But my phone is still unable to be recognized by Odin in Download mode. The phone is also not recognized by my pc at all. It only charges, no matter what USB I try. I even tried mounting in recovery, no go.
Please help. Thanks!
Hi,
First of all, great site you've got there, been checking it ever since I laid my hands on my first htc g1.
Secondly, and I hope I'm not double-posting about an issue already raised, as I've screened the threads quite thoroughly.
Here's the issue I have with my MK808B.
I've tried to start it with a USB ubuntu pendrive plugged into the USB OTG (I had saved some files I wanted to transfer, didn't realize it would mess things up).
Regular start up with this hdmi key is Google tv screen > android screen > home screen.
I get stuck at android screen, no matter how long I wait.
Out of nowhere, I tried to use another 2A power supply, as this had been advertised on other threads, no sucess... I also tried to start it with a paperclip pressing the reset button, didn't work...
Honestly, I don't know what to do exactly, I think it might have tried to boot ubuntu out of the usb stick...
I think I have no option left but to flash it (thus losing all that is installed already on it).
Is there any trick that could restore things the way they were? Any suggestion welcome.
Thanks for your time and help.
Solved by flashing
Hi,
Since no mgic trick happened to save the day, I was left with no choice but to flash it.
Used rockchip batch tools, crossed my finger so the stick wasn't a clone with the mediatek chip, flashed stock plus goodies rom, waited 10-15 minutes, and voila!
good as new, got rid of the chinese apps I couldn't even log on, but got a full wipe of my data.
TL;DR - Flashed a ROM designed for N3+ (which is supposed to be same phone) but touch screen is unresponsive now. Need help with SP MDT or editing uboot
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?).
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
____________________________________________________________________________________________
Hello everyone, like title says I have unresponsive touchscreen on my Star N9800 phone. It's pretty much a new phone, octa core, quad core GPU, 2GB RAM, 16GB storage, etc.
What I've done is I flashed the ROM designed for Star N3+ (which is supposed to be same phone) but my touch screen is unresponsive ever since then. I've googled and read some articles on xda about SP MDT. It's a tool which can help us choose the display driver we want the phone to run with. I actually ran into a problem when i downloaded SP MDT. I can select the database etc, but when i get to scatter file it just doesn't want to load it. Either it's incorrect name or file type. I've downloaded 3 original ROMs from needrom.com and strangely the scatters seem to be different. But none is accepted by SP MDT. I need someone of knowledge who can teach me where to find uboot and how to edit it correctly. I'm not a linux/android programmer and I really don't wanna get involved into much programming. I understand basic stuff, i can find files on the system, i can edit build prop correctly, remove or edit boot_logo, boot anim etc, but this is a bit more than that. 2
Please share some knowledge with me and please don't point me to google. There's no solution there, i've googled for 3 days now. The last resort for me is to make a post here (and hopefully don't get ignored for spamming because this isn't spam).
My email is: [email protected] - you can notify me here if I don't get automatically emailed by xda.
Thanks in advance.
BUMP
Have no solution but would like to learn as well if anyone can help us...
I had the same issue but gave up and flashed another rom instead.
Flashing another ROM didn't help my problem. Well partially it did. I've flashed 2014-1-7 original N9800 ROM and the touchscreen only needs 1 or 2 off/ons till it starts working. I'm kinda fine with it because it was completely unusable. Flashing drivers with SP MDT didn't really help. I've tried flashing RX5720TM_828A (from N3+ ROMs) and LP057APK (default in N9800 ROMs) and RX5720TM_813A (2nd in N9800 ROMs), and so far my touchscreen works only with 813A LCM driver. When i turn off the phone and then hold VOL- & POWER & OFF/ON it goes to factory mode. There i clicked version and it showed that 813A is installed as LCM driver, BUT touchscreen says (null). Could it be that my digitizer is no longer connected or what? Cuz it sometimes works correctly without turning the display off/on at all.
EDIT 15. July, 2014.
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?). It is possible that digitizer is detected but not working?
Even if i boot into recovery, screen doesn't react to touches.
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
Apparently it's the calibration which ****ed up my phone. I'm now trying to figure out how to calibrate the screen through CWM.
ever find a solution?
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Touch screen sometimes not react
AlexZap said:
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Click to expand...
Click to collapse
-------------------------------------------------------
I have exactly the same issue and same signes, the phone itself is working good, ring for incomming phone but the the screen is not reacting i cannot take the call, it receives emails.
Did someone have a solution please let me know... thanks
My phone is star N9800, 2Gb memory and 16 Gb storage, android 4.4.2 originaly installed and was working fine during 9 months
Touchscreen - hardware failure
Hi,
I am wondering if you may have experience and be able to help me with my Star N9008 phone which has has had its touch screen stop working while I had it in storage for about 3 months.
Very well stored, no shock, no humidity. I keep it with my laptop backpack as a spare in case my everyday phone fails.
Today I powered it up to make sure battery was good (found it good at 95%) and update applications, etc. Basically, just checking it was still good to serve as a backup should I need it.
Thing is, I found the touch screen is completely unresponsive. Connected a mouse to it and verified all was working good, did up the updates, etc.. using the mouse. Reboot and boot into service mode and restore menu. Also, no touchscreen response (I use TWRP). Thus, it must be hardware failure.
From experience, would you know what would cause this, and how to resolve?
Thank you.
So, its been a while.
So, it's been a while. I still have the phone in storage and pity it doesn't work...
I haven't bothered opening up the phone if I don't know what to really try and also risk damaging it.
Also didn't bother ordering a new digitizer to replace as it's economically unviable.... the phone is now really getting behind as new tech is further evolving, so I do unfortunately see it going in the rubbish soon (along with two brand new batteries I had purchased for it just before it died).
Has anyone been successful at finding the culprit?
In my case, it was fine and very well stored... so I don't really have an explanation other than the phone possibly having a 'countdown timer' to break it... (yeah, a bit too conspiratorial, lol)
I did not find a solution yet , phone still sits in storage