I've always enjoyed the stock browser and it's suddenly started to behave very oddly. I'm running up to date CM10 nightlies.
1) when I type the screen starts to move up on every key press. This happens with both dock and on-screen keyboards.
2) I use the quick controls (pie style) which removes the tab/search bars at the top of the screen. Sometimes this works fine, but other times the tab/search bar remains along with a strange legacy streak of the blue lines which indicate page download progress.
At first I thought t was due to an update in the Nightly (to 8th April) but I've flashed back to an earlier Nightly and the problem is still there.
Has anyone else seen this before? Any ideas what might be happening and how to cure it? Other browsers seem fine (I'm typing this on Boat).
dgjl said:
I've always enjoyed the stock browser and it's suddenly started to behave very oddly. I'm running up to date CM10 nightlies.
1) when I type the screen starts to move up on every key press. This happens with both dock and on-screen keyboards.
2) I use the quick controls (pie style) which removes the tab/search bars at the top of the screen. Sometimes this works fine, but other times the tab/search bar remains along with a strange legacy streak of the blue lines which indicate page download progress.
At first I thought t was due to an update in the Nightly (to 8th April) but I've flashed back to an earlier Nightly and the problem is still there.
Has anyone else seen this before? Any ideas what might be happening and how to cure it? Other browsers seem fine (I'm typing this on Boat).
Click to expand...
Click to collapse
Bump -still happening (15 nightly)...no ideas out there?
Related
Hello all,
I apologize in advance if this problem was solved before, I could not find it.
I have a Galaxy Note (GT-N7000) with Android 4.0.3. For a few weeks now I've been having problems with the onscreen keypad. Everything is working normal when suddenly the keypad stops responding. I can still touch other things on the screen and scroll through menus as normal, it's just the keypad that stops working. When I reboot the device, the problem is usually solved. As of yesterday, I have (occassionaly) had the same problem but the keypad doesnt even load. The page is sized down to accomodate the pad but there's just a black rectangle. To solve this, I needed to reboot twice.
I'm pretty sure this has to be software-related seeing as the rest of the apps/screen keeps working.
Thanks in advance for any help.
Anyone had this same problem? It's happening more frequent now, about twice a day.
Same problem here
I have the same problem and its driving me nuts! If i drag down the notification bar and click the "Select Input Method" button, nothing happens.
Tried going through settings menu and changing to stock/swype and still cannot enter anything. Swype even shows the word i entered in the suggestions bar but nothing appears in the text entry box!
Im so glad it's not just me. Do you use a custom keyboard? I use Swiftkey 3 but as i said, i tried switching to another keyboard and still got nothing. I have even had the problem persist after reboots sometimes!!
Is there another ROM I can flash? I have stayed stock until now, but between this and the bluetooth drop out bug and speakerphone issues, I'm about ready to give up on Samsung's Official ROM :/
When the problems started I didn't have a custom keyboard but now I'm using SwiftKey. Since that change I haven't had as much problems. Only thing that happens now sometimes is when you type for example tree and every keystroke after that then copies ree so you get treereereereereereeree.
There are certainly other ROMs but I'm not really into that so you should search the forum. I'm still (relucantly) using the official ROM.
Hey everyone, I'm having a weird issue with my GS3 SCH-I535. On any AOSP rom I try (CM10 Unofficial and Official, AOKP) my physical home button doesnt do anything except wake the screen when it's off. It wont return to my launcher. This doesn't happen on touchwiz roms (Synergy, stock).
Any ideas?
Isn't there an option to change hardware key functions? I'm not on CM10 yet. I will be tonight.
Sent from my SCH-I535 using Tapatalk 2
mustbepbs said:
Isn't there an option to change hardware key functions? I'm not on CM10 yet. I will be tonight.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I saw an option for changing the long press function and tried that, but even long pressing still doesnt work. the button is completely unreactive except for waking the screen
odd.. I tried flashing another kernel but it didnt support CM10 and wouldnt boot, so i reflashed CM10 without full wipe this time and everything works fine now.
my notification bar was also completely empty and that's fixed as well. maybe it just wasnt flashing correctly before?
either way problem solved
exershio said:
odd.. I tried flashing another kernel but it didnt support CM10 and wouldnt boot, so i reflashed CM10 without full wipe this time and everything works fine now.
my notification bar was also completely empty and that's fixed as well. maybe it just wasnt flashing correctly before?
either way problem solved
Click to expand...
Click to collapse
seems like i'm having the same problem. home button only wakes on screen off, also returns to home from notifications and recent apps ... but that's it.
Worked fine on a CM10 nightly 20121004 then flashed the 20121006 and it broke. Reflashed 20121004, and still broke.(just flashed the latest nightly, and still not luck) Tried what seems like all combinations of CM10/Nova Launcher/Trebuchet settings. Tried fixing permissions, wiping cache as well.
It randomly started working again last night, but again stopped working on a reboot.
I feel like this is possibly related; at the same time my Menu (long press) only works when I'm on the Homescreen
I have no legitimate answer to your issue, but on the galaxy players there is a variation in the us/international versions that require a home button/soft key patch built specifically into the kernel. Whether that can point someone to a solution, I don't know...
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
In case anyone stumbles on this thread;
I seemingly found out how to replicate this on a consistent basis. On reboot, home button will not work (except for above mentioned features)
Using the "Toggle Lock Screen" Notification Drawer Widget once or twice seems to restore complete functionality until next reboot.
I have no idea how/why, but it does seem to work for me.
Solved! It looks like the culprit was the Smooth Calendar widget...
-------------------------------------------------------------
I've had a really bizarre problem that started a couple of days ago. At that time I was rooted on the stock ICS. The first thing I noticed was that the keyboards would stop working. They'd come up, but no matter where I tried using it - GMail, Dolphin, Talk, etc - no text would be entered. The kayboard keys would flash and the autocorrect fields would populate as if I was typing normally though. This happened with both the latest Swype beta and the stock touch input. The only fix was a reboot which would help for a little while.
The other issue was the clocks not syncing up. The clock widget on my homescreen would show the current correct time, but the clock in the notification bar would be stuck on any given time for up to hours.
Here's the weird part. These issues survived a data and cache wipe and the install of a different rom. I'm now using ViperS 1.6.0. Could this possibly be a hardware problem? Nothing unusual happened between it working fine and the problem starting. No new apps, no water exposure or drops, etc... The closest thing to a cause I can think of is that some app that I had and reinstalled today was updated a couple of days ago and the new version is doing it...
Any other ideas?
So, I've been having issues with my TF101 for a while now. At first I thought it was ROM related, but I've seen this issue across a couple different ROMs, including the stock ICS update. The issue is that frequently, the launcher will crash and restart when swiping off the main homescreen. Other times, the UI overlay will crash. That is to say, the icons and everything will vanish, but the background will still be there. Sometimes a widget might be frozen on the screen (it's visible regardless of swiping, and you can't interact with it). I can still swipe, the background is still visible scrolling, and if you know where something should be, you can even tap it and it will open. Has anyone else experienced this? I've noticed the issue in the stock ICS launcher, Apex, or Trebuchet. When it happens, I either have to restart or at least re-apply the system them. Even the lock screen UI vanishes.
FWIW, my TF101 is a B60 unit, rooted, running RaymanFX's CM10 (4.1.2) ROM, and TWRP.
So no one's seen this kind of issue before?
I have a similar problem. Hitting the "home" button (it never disappears) solves the problem, no need for other apps or reboot or anything. I just plain hit the home button and everything reappears.
TheQuicksilver said:
So no one's seen this kind of issue before?
Click to expand...
Click to collapse
Sometimes, my UI vanishes, but if I wait about 10 seconds or so, it comes back. I guess the launcher crashes, but is automatically restarted by the kernel. I use the K.A.T kernel, maybe that is better with the re-launch when it crashes?
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!