Running a Jelly Bean ROM 4.1.1 from user Hashcode on my Fire and really enjoying it. Many Thanks to Hashcode for his work. However, have noticed that the JB keyboard doesn't always register when I hit the keys. I have actually loaded a different keyboard because it was happening so much. Anyone else seeing the same issue???
Yeah, that kept happening to me too, but I wasn't sure if it was me imagining things or if the keyboard really was skipping some touches...
Well, I have to use SwiftKey anyway, for the language support.
Yep, happened a lot to me. Eventually loaded the Go Keyboard. Before that, I turned off the tap noise bc at least then I didn't have the indication the touch had been registered.
I don't understand why Google won't include a decent keyboard that at least has long tap for secondary keys...
Sent from my Kindle Fire using xda app-developers app
Running MultiLing myself. Is it me or does the touchscreen seem more responsive with the JB ROM??
Sent from my Amazon Kindle Fire using xda app-developers app
My keyboard is working perfectly, actually better than stock. Did you guys do a full Factory Reset before flashing or did you flash over another rom? I had a lot of little issues when I first flashed after only doing system and cache wipes. Went back and did the reset and most of the problems were solved. Just wondering if that might be part of the problem.
Sent from my Amazon Kindle Fire using xda premium
jelly bean 4.1.2 keyboard issue
JimCo06 said:
My keyboard is working perfectly, actually better than stock. Did you guys do a full Factory Reset before flashing or did you flash over another rom? I had a lot of little issues when I first flashed after only doing system and cache wipes. Went back and did the reset and most of the problems were solved. Just wondering if that might be part of the problem.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
u know what, I tried both, installed JB 4.1.2 on existing ROm and then wipe dalvik cache battery factory reset, formatting system data cache...everything...now I have seen something positive with some negetives as well,
Negetives: when I ported JBMP release 3 the touch screen was completely off, however keyboard was working(I mean all keys)
in MiniCM-4.1.0 except the numlock (the bottom left key required to put numbers) wasn't working
Positives: with release 2...everything was working fine...
2.before rooting flashing and installing this ROM the keyboard is to work fine but there was no kight what so ever, but after flashing different kernels the light came back, I mean with ICS 4.0.4 and JB 4.1.2 the light is there (it got rectified donno how)
but can this be rectified? Anyone any ideas?
Thanks in advance
Related
Hello im have a problem where all my apps,shortcuts and UI randomly disappear or my screen and the only thing left is my wallpaper. The only way i resolve it is to go to settings/apps/launcher and force close it. It restarts but its just a temp fix cause randomly it happens again. I have tried Multiple Flexreaper,Thor, and Cm9 roms Multiple bootloaders and Kernals but it always comes back. I ALWAYS do a full wipe (by wiping everything even data) but after a while it comes back. Anyone know how to fix it or Any info would be great thanks
I can't help with a fix, but I can confirm that you are not the only one with this issue. I have three Acer tabs, One that's stock ICS A500 no root, one A500 with V3 bootloader and Flexreaper, and one stock rooted ICS with the V8 bootloader. All three do this same thing. The only way that I can get rid of the issue is to downgrade to the Honeycomb bootloader. If it was any more annoying I would go back to the Honeycomb bootloader and pretend to be a chicken while enjoying my nice solid user experience. I'm not sure how Acer bugged it up on this one. But as far as I can tell, it is an Acer ICS bootloader problem that carries over even if the bootloader is patched.
I've been trying to find a solution. So far, other than changing back to HCBL, nothing has worked. It's too bad that one of the Dev's can't see a tablet with this issue. Those guys can fix about anything...
Thak you for the info. Its good to know Im not the only one who has this problem. Do you think CM10 will fix it since its Jellybean?
I never experienced that issue...until I moved to Jelly Bean. It happened all the time on the first alpha port, but the latest cm10 is OK. I hasn't happen since. What launcher are you using?
I've tried a ton of launchers and it happens on them all. Also, it happens less frequently if I don't have a email widget on a home screen.
I'v also tried alot of launchers and they all do the same. Thanks for the email widget tip
Has there been any new developments on this issue and how to fix it?
I'm on hc bootloader and never have that problem. I am fully capable of flashing ICS bootloader, but have no interest in doing so. I see no clear advantage and hear nothing but problems. I'm running the newest TO Jelly Bean and it is practically flawless. Call me a chicken if you like, but I'm a happy chicken with a sweet tablet
Sent from my HTC One S using xda app-developers app
It happens to me all the time with all the launchers I 've tried. I am in unlocked ics bootloader and stock rom. The same happened with the locked bootloader. I tried the CM10 Rom same results. I removed all widgets from the homescreen with no luck.
If it's in the ICS Bootloader then all must have the same problem or not?
Any solution except going back to 3.2?
To fix it I had to go full stock to Honey Comb then reinstall CWM then install Thor cm v15 and no problems since. I think the problem is the ICS bootloader
if so, did it break Swype? i originally unrooted, went to stock, then flashed 4.1.2, and had subsequent problems with trying to install Swype Beta. i really can't live without it, even though i have swiftkey 3. if i can't use Swype with 4.1.2 yet, i won't accept the update until they update Swype itself.
let me know if anyone is in this situation or has updated and if Swype does or doesn't work. thanks!
frescagod said:
if so, did it break Swype? i originally unrooted, went to stock, then flashed 4.1.2, and had subsequent problems with trying to install Swype Beta. i really can't live without it, even though i have swiftkey 3. if i can't use Swype with 4.1.2 yet, i won't accept the update until they update Swype itself.
let me know if anyone is in this situation or has updated and if Swype does or doesn't work. thanks!
Click to expand...
Click to collapse
No problems with Swype for me... I had installed it when I was with 4.1.1, I used CWM installed the 33.4mb ota upgrade downloaded from Google. I did not unroot 1st, was on stock Rom, cmw asked to keep root and custom recovery and it did. I have been using only Swype ever since... 2 days without any issue...
Maybe you need to go back to 4.1.1 and start the whole process over????????? idk.... but good luck!!!
mk69 said:
No problems with Swype for me... I had installed it when I was with 4.1.1, I used CWM installed the 33.4mb ota upgrade downloaded from Google. kept root and custom recovery. I have been using only Swype ever since... 2 days without any issue...
Maybe you need to go back to 4.1.1 and start the whole process over????????? idk.... but good luck!!!
Click to expand...
Click to collapse
thanks. i had Swype working fine with 4.1.1, but i wiped everything and unrooted before going to 4.1.2 (because i was running motley kernel and the update wouldn't take). i'll download the OTA and hope for the best. worst case...can i go back to 4.1.1?
frescagod said:
thanks. i had Swype working fine with 4.1.1, but i wiped everything and unrooted before going to 4.1.2 (because i was running motley kernel and the update wouldn't take). i'll download the OTA and hope for the best. worst case...can i go back to 4.1.1?
Click to expand...
Click to collapse
From what I read here on xda, yes you can go back to 4.1.1, I have not personally done it, but I would assume you have to download the whole 4.1.1 Rom from Google and flash it back, but I think that will also wipe you clean...
i don't use Swype on my Nexus 7, but on my Galaxy S3, i flashed an AOKP 4.1.2 ROM and still using Swype- no issues.
Swype works great on my N7. I didn't get OTA, but installed off xda. I had to go back in and choose Swype as my input method but that is all.
Sent from a Buttery-smooth Amaze with xda-developers app
my Swype is working after ota...i wish they would stop making swype worse...previous versions were better....
Sent from my Nexus 7
Edit: Never mind, didn't realize this was the N7 forum when I came here searching "4.1.2 swype crash".
anyway top hey the latest Swype too work in tablet modes on the nexus 7 without modding dpi or flashing rom?
Sent from my Nexus 7
No problems here. In fact Swype put out a really nice update with theme support today our yesterday.
Sent from my Nexus 7 using XDA Premium HD app
Swype is broken completely for me. Un-rooted, everything stock. Some info here - http://forum.swype.com/showthread.php?9982-Official-Galaxy-Nexus-Jelly-Bean-Swype-Issue-Thread - but nothing I've seen which would fix it for me....
No problems on my end. Updated, restored root (via RootKeeper), and kept on goin'. Everything's peachy.
Everything is fine here, too.
Sent from my Nexus 7 using xda app-developers app
Hi Everyone,
I have a Galaxy note 10.1 (N8010 wifi only), and I was wondering if anyone has been able to find a good Jelly Bean firmware for this device.
I have installed the Stock N8000 (3G version) on my N8010 using Odin, and while the software works great as long as the screen is unlocked, random reboots occur when the screen is locked.
I don't really want to give up Jelly Bean on my tablet as the Samsung apps (S Note, multi-tasking, etc) are much improved, the improved usability has led me to the decision to deal with the random reboots for the time being.
Is there any way to port over the upgraded Samsung application software (improved S Pen functionality, updated TouchWiz sustem) to the ICS stock firmware? If not, is there a firmware/ROM out there for Jelly Bean that is made to operate on the wifi only version?
I could flash a custom ROM, though I haven't found one with the Samsung apps included - would this be accessible by flashing gapps or something similar (probably not gapps since it's Samsung software).
I would happily stick with the JB ROM I have now if there was any way to address the random rebooting issue, I've tried uninstalling any phone/SMS/mobile network related software using a utility called Link2SD but the random rebooting persists.
I have also tried (per the advice of another thread) enabling airplane mode to that it stops seeking mobile networks, though I have enabled wifi from here to make my tablet useful...rebooting still occurs, though it may be less frequent.
I'm rooted, so if there's anything I can do as root to address the rebooting issue, advice would be much appreciated. I just want to take an axe to all things mobile data/3G related. I'm sure I'm not the only one suffering with this issue here!
Cheers,
Nick
If you read here for about 15 min, you will find all that is needed for your problem. Get setcpu app and set to on demand and no more reboots, flash the n8010 fix to eliminate the phone framework.
Look here
http://forum.xda-developers.com/showthread.php?p=33909040
8013 is US WiFi
Sent from my GT-N8010 using Tapatalk HD
Missing Toolbar
Thank you very much for this info, much appreciated!
I have overcome the random rebooting issue, though my toolbar seems to have gone missing! I wiped the dalvik cache, not sure if that's what cleared it out? Anyway, I'll wipe my tab and set it up again to see if the toolbar returns. Thanks again!
Cheers,
Nick
KoRoZIV said:
If you read here for about 15 min, you will find all that is needed for your problem. Get setcpu app and set to on demand and no more reboots, flash the n8010 fix to eliminate the phone framework.
Look here
http://forum.xda-developers.com/showthread.php?p=33909040
8013 is US WiFi
Sent from my GT-N8010 using Tapatalk HD
Click to expand...
Click to collapse
The fix for 8010 worked for me, I used the German deodexed Rom. After you flash the jb Rom, boot in it and set-up your stuff, only after that get in cwm and flash the fix.
Sent from my GT-N8010 using Tapatalk HD
Since this issue has resolved this thread has no use anymore.
To OP next time be sure to create a question thread HERE
Thanks and thread closed.
Hello! I have an unrooted N7 that is stuck with 4.1.1. I regularly get a notification advising me of an update & I run it through the process only to be discouraged to find I'm still stuck with 4.1.1.
Can anyone help? I don't want to root & do a bunch of crazy stuff to get the update. Is there a good fix without rooting?
FYI, I found a "fix" that required turning off WiFi, clearing the some of the systems cache, turning the WiFi back on & searching for an update. No dice...
Sent from my Nexus 7 using xda app-developers app
If you have nothing to lose your best and easiest fix would most likely be to perform a factory reset.
Cheers
Sent from my Nexus 7 using XDA Premium HD app
My N7 stuck at stock 4.1.2(JZo54K), I force clean Google Service Framework and checked update. N7 found 4.2 and downloaded 80.6mb file then restart and install. After install N7 still show 4.1.2. pleas help me.
clintjames77 said:
Hello! I have an unrooted N7 that is stuck with 4.1.1. I regularly get a notification advising me of an update & I run it through the process only to be discouraged to find I'm still stuck with 4.1.1.
Can anyone help? I don't want to root & do a bunch of crazy stuff to get the update. Is there a good fix without rooting?
FYI, I found a "fix" that required turning off WiFi, clearing the some of the systems cache, turning the WiFi back on & searching for an update. No dice...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Try applying the update. When your tablet reboots and you see the Android on your screen, hold down the power button then, while holding it down, press volume up. That'll put the stock recovery in verbose mode. When it errors out, post what the text says here.
Similar thing here.
Brand new 32gb Nexus 7, finds the 4.2 update but half way through I get a Android with a red triangle/exclamation mark which then reboots back to 4.1.2
Be happy your stuck on jelly bean 4.1.x!
Sent from my NOOK using xda app-developers app
SimonCraddock said:
Similar thing here.
Brand new 32gb Nexus 7, finds the 4.2 update but half way through I get a Android with a red triangle/exclamation mark which then reboots back to 4.1.2
Click to expand...
Click to collapse
Tried half a dozen times then did a manual forced update using this guide, easy to follow and worked first time.
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
3dwarehouse said:
Be happy your stuck on jelly bean 4.1.x!
Sent from my NOOK using xda app-developers app
Click to expand...
Click to collapse
Yes, I wanted to say this. stay on 4.1.1 or 4.1.2,.... 4.2.x is a piece of crap. Much slower, not the same device at all.
Thanks for advice, then I tried not to update to 4.2 and be happy at stucked 4.1.2
finger crossed and wait for next stable version instead.
dopodMyanmar said:
Thanks for advice, then I tried not to update to 4.2 and be happy at stucked 4.1.2
finger crossed and wait for next stable version instead.
Click to expand...
Click to collapse
4.2.1 is pretty stable, stability is not the problem, but initially it broke a lot of apps compatibility (ok, this will be solved in time), but no matter what I do I have feeling it is slower, and it stutters. I never had this with 4.1.1 or 4.1.2. And I was so happy with my Nexus until 4.2 Anyways, I had 4.2 on my original Nexus, then it died and I sent for repairs, now I have new motherboard (so it counts as different device) and factory-installed 4.2 and it is the same. Even sometimes when playing a game it just stops for a split second... Trust me, new notifications and multi user (if you're not using it) is not worth the smoothness of 4.1.1
Cheers,
D.
dalanik said:
4.2.1 is pretty stable, stability is not the problem, but initially it broke a lot of apps compatibility (ok, this will be solved in time), but no matter what I do I have feeling it is slower, and it stutters. I never had this with 4.1.1 or 4.1.2. And I was so happy with my Nexus until 4.2 Anyways, I had 4.2 on my original Nexus, then it died and I sent for repairs, now I have new motherboard (so it counts as different device) and factory-installed 4.2 and it is the same. Even sometimes when playing a game it just stops for a split second... Trust me, new notifications and multi user (if you're not using it) is not worth the smoothness of 4.1.1
Cheers,
D.
Click to expand...
Click to collapse
Thanks for reply, I'm curious to know as why my N7 stuck at 4.1.2, there may be reason as I tried several times update (reboot and installed, stuck at 4.1.2) no matter how I tried) but I'm peace in mind as 4.1.2 stability.
If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
You may need to do a full wipe when you flash stock, it's possible something has corrupted somewhere along the line.
Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
..
Format all your data in system via CWM - then reinstall your ROM from scratch, it'll fix any coruption issues. ->>> Important >>> Make sure you make/get a PIT file for your device before you change anything in case you need to sort your partitions out for a reflash
I'll give it a try thank_you...
Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
How bizarre , I'd stick with the custom ROM for now just in case something else gets crazy corrupted - This Kitkat stuff atm is causing havoc all around.
Yeah I think you're right, maybe different batches of phones and buggy kitkat are causing problems for a few of us? It'll all get ironed out in the end hopefully..
Sent from my SM-N9005 using xda app-developers app
I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?
Colide said:
I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?
Click to expand...
Click to collapse
got the same problem as yours, no idea why though, after the update samsung keyboard and action memo stopped working.
I think I will wipe it tomorrow but it seems it's not working either
I'm checking around and they say that problem probably lies in the application S Pen Keep, there is no data on this one ... I guess as you said it's linked to the handwriting recognition. tried to do that using Snote transform into text as well and it immediately stopped working as well..
For time being I'm using different keyboard and I like it better than stock one. I really don't want to wipe a phone. Takes so much time to install everything back.
Sent from my SM-N9005 using Tapatalk
Did u guys intentionally or unintentionally uninstalled Samsung apps? From what I've understand, certain Samsung apps needs to be either freeze thru TB or disable it...
Haven't touched it. I've upgraded to KitKat without updating a bootloader and it happened.
Sent from my SM-N9005 using Tapatalk
same here, got the OTA update, after that it simply stopped working.. I don't need the keyboard .. I need the action memo more
Mine still isn't working, I'm on omega rom now so it doesn't affect me, but it still does it if I flash stock... Strange..
try to download another stock rom? maybe that will fix it.. if it did .. let us know... try to download the newest one that came up in Poland..
mine got fixed by formatting and wiping, re-download another stock rom I guess yours has some form of data missing ..
@Colide , just go back to factory settings , will resolve the issue, do it from the recovery of course.
I kinda hate it to wipe data. Lot of apps to reinstall. Thanks for a tip. ?
Sent from my SM-N9005 using Tapatalk