i installed opera mini, used for about 5 minutes, uninstalled
then noticed my orientation would not work..
anybody else have this happen..
ended up doing a complete redo ..wipe and install new rom
figured it was from dropping it in the toilet last month
Related
I've been using my HD2 for months trouble free.
The last few weeks i've been running android and windows, mostly windows but playing about with android in the evenings about a week ago i downloaded the HD2 Froyo V2.1 and installed all went ok, thats been fine all week but yesterday i decided to have a go at running android most of the day which is working really well.
But here's the issue went back into windows last night and its just not running it will boot up and seem fine for a few min then it just freezes, i'm using elegancia rom so did a hard reset set everything back up seemed ok for about 10min then tried to log into twitter and the phone froze, reinstalled everything again and same thing happened.
So this morning i decided to install an Nrgy rom to see if that made any difference.
I put the 1914 sense rom on so its close to stock as possible and that seems to be ok but when i log onto twitter it restarts sense and i've had a few issue's with it randomly switching sense off but it doesn't freeze now it just restarts sense.
Any ideas i've not used android with the Nrgy rom as yet is there anyway that something android has put onto the SD card may be effecting the stability of windows ?
Any ideas much appreciated...
Just to add i've just read that there appears to be a twitter issue.
But i'm still getting random sense resets without using twitter ?
Hey guys,
I've been having some keyboard issues for a while now and it's really starting to bug me. I'm currently on BAMF 2.1, but I've used various iterations of BAMF and I was even experiencing the same problem on CM7. Whenever I install a new ROM I do a complete wipe 3x and lately I haven't even been restoring data on my apps.
When typing, certain letters just don't work. It's really odd. I can sit there and tap tap tap away, and it may take like 6 taps to get a letter to work. At first I thought it was my screen, but I experience NO issues with the screen anywhere else but typing. The fact that what letters don't work often change (both in landscape AND portrait) also makes me think that it's not the screen.
I'm currently using Smart Keyboard Pro with a DX skin (had a DX before this and loved the keyboard), but I've even switched to the market version of the GB keyboard and experienced the same problem.
Edit: I forgot to mention that it doesn't always happen. I could go half a day with no issues, but then it pops up and it's pretty persistent.
Does anyone have any ideas? It's really starting to become a problem.
I have experienced maybe something similar. Since I flashed gingerbread ( my keyboard sometimes locks up. There's usually a delay of 3 seconds before it picks up. I'm using swift but it has happened on swype and the stock keyboard.
Happens to me, exact same problem but it also happened on my inc so I'm not too worried lol it IS annoying but doesn't last for an extended amount of time
Sent from my ThunderBolt using XDA Premium App
Ugh, this is still happening to me and still being a pain in my ass
A while back I've updated the phone to Android 2.3.3. Everything worked great, no problems whatsoever but a few months later, when I tried to start the camera, everything went wrong (see video at the bottom of this post). It's been like that for maybe 3 weeks and then it went back to normal.. it worked fine for 2-3 days then it went crazy again.. after about 1 week, it worked fine again. Now it's not working as it should (I don't see the video, just static/random colors). I've tried SE Update Service but it didn't fix the issue. I've been searching the internet for about 2 weeks now and I wasn't able to find anyone who is experiencing the same problem. I have a few apps installed but none of them control the camera.
Recently I installed FeraLab and the problem is still there. I bought a camera (spare part) but I don't really want to start taking the phone apart if there is another (easier) fix.
Any help would be greatly appreciated! Thank you!
Youtube Link: http://www.youtube.com/watch?v=6bn5vvjm538
Flashed neutrino 2.9 this morning and it is AWESOME! It was my first time ever flashing anything onto my phone, and everything worked out great! There are only 2 things I am wondering about...
First off, am I able to get swype set as my input method? I realize it's a pretty stripped down rom and swype has most likely been removed to cut down on size or increase efficiency etc. I've tried installing the swype beta, and managed to get the installer installed (yeah it's kind of an odd system, you download and install the installer to install swype) but for whatever reason when I type in the user/pass to get the actual swype installed, it just sits there forever and doesn't do anything. I've also just tried restoring swype with titanium backup from the backup I did on my stock rom, but it just starts a force-close loop until I set the input method back to the regular keyboard.
Secondly, and this is extremely minor, when I set up the fingerprint unlock there doesn't seem to be any backup unlock system for it. In the stock rom as we all know there is a pin that you can set to unlock as an alternative to swiping your finger on the reader. Maybe I'm just paranoid, but it would be a bit of a pain in the ass if I was to drop my phone and a rock smashed the fingerprint sensor, or my index fingers got chopped off in some freak accident haha.
All input greatly appreciated! Apologies if this is in the wrong forum, didn't seem quite appropriate to be posting over in the development section for something like this though.
*EDIT*
Swype problem solved. Looks like there was something wrong with the swype beta installer. After force closing it and opening it again it worked just fine, and swype is now installed and working (so far) perfectly!
So... Sort of a bump, but I ran into a new problem today.
For some reason when charging my phone, it only charges to 92%. I had it plugged in for about 12-13 hours, and it just seemed to stop charging. I pulled the battery, rebooted the phone, plugged it back in, etc. Didn't seem to do anything.
Anybody run into this one and know of a solution?
Tried this already?
Worked like a charm! Thanks.
was the fingerprint pin bypass every addressed?
i just started using 2.91gt+ and i won't enable the fingerprint lock with out a bypass pin...
i'm a marine engineer so my hands are constantly in and out of oil, fuel and fast orange so i've had days where on the stock rom it wouldn't even recognize i swiped my finger over it at all
Hey guys!
I've already posted my problem in the Nexus 4 Q/A-Forum.. till now without help. Well i thought that maybe here is a good place to get help, too!
So whats my problem.. Yesterday i flashed a new update of Xylon-Rom (clean flash) on my Nexus 4. Installed and restored all Apps. Usually I use Swiftkey 4 as keyboard, so I set up everything like all the times before. The last times everything works fine, but this time not. I set up SK as my standard keyboard and began to write. After a while I wanted to write again, but suddenly there was the AOSP keyboard. Changed back to SK. But after some moments it happend again. So everytime when there is a text input AOSP appears.. I change back to SK then, but after turning screen on some minutes later AOSP again.
As it would be not enough, the same thing is happening since yesterday on my gf phone (HTC One S, also rooted with Carbon Rom). Like on my phone, it never happenend before.
What I've done till now? Erased App-Data of both keyboards, disabled AOSP keyboard. Everything without success.
Dont know why it happens now... I often flash other Roms, Updates etc and I use Swiftkey for a long time. Restoring with Titanium works everytime. And this time i haven't done any other thing on Restoring.
I hope u understand my problem (my english isn't the best ) and anyone could help me!?
Thanks so far.
Cls
Tried to freeze the AOSP in Titanium -> no effect
Set Swiftkey as System-App -> no effect
:X
I was encountering this with swipe keyboard previously, and my solution was to use swiftkey.
Sent from my Nexus 7 using Tapatalk 4 Beta
same thing
im suffering from this problem too.. no solution yet :3