Active Topics
-
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 7 hrs, 50 mins ago -
Error after installing Leste on sdcard (12)
to Maemo 7 / Leste by teroyk - 8 hrs, 37 mins ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 3 days, 16 hrs ago -
Maemo repository (3)
to Community by torsen - 4 days, 9 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 6 days, 13 hrs ago - more...
| The Following User Says Thank You to sjgadsby For This Useful Post: | ||
|
2008-02-26
, 15:42
|
|
Posts: 609 |
Thanked: 232 times |
Joined on Dec 2007
@ the end of my rope
|
#22
|
THANK YOU!!!!
You are right, re-enabling the Bluetooth icon in the status bar removed the bug---i got my on-screen keyboard back *almost* immediately upon closing the iGo. I just waited until the icon turned from blue to gray/white and then the on-screen keyboard appeared when called.
This really is a strange bug. I'm not sure if it's made all the stranger in light of the fact that when the tablet has gone berserk in the past (as I described earlier), the bluetooth icon appears as the left-most icon in the status bar, but now that the icon is permanently enabled (as per your suggestion), it appears as the right-most icon. Perhaps this is an inconsequential observation, however.
Thanks again!
You are right, re-enabling the Bluetooth icon in the status bar removed the bug---i got my on-screen keyboard back *almost* immediately upon closing the iGo. I just waited until the icon turned from blue to gray/white and then the on-screen keyboard appeared when called.
This really is a strange bug. I'm not sure if it's made all the stranger in light of the fact that when the tablet has gone berserk in the past (as I described earlier), the bluetooth icon appears as the left-most icon in the status bar, but now that the icon is permanently enabled (as per your suggestion), it appears as the right-most icon. Perhaps this is an inconsequential observation, however.
Thanks again!
|
|
2008-04-16
, 18:55
|
|
Posts: 259 |
Thanked: 72 times |
Joined on Dec 2007
@ Halifax, NS
|
#23
|
I finally got around to voting for this. Bugzilla is kinda hostile to the general public, isn't it?
BTW, who do we have to convince to bump this up from "Low" priority?
I have had this bug lately, and I haven't disabled the bluetooth icon...
BTW, who do we have to convince to bump this up from "Low" priority?
I have had this bug lately, and I haven't disabled the bluetooth icon...
 |
|
2008-04-19
, 00:47
|
|
Posts: 61 |
Thanked: 7 times |
Joined on Dec 2007
|
#24
|
Id say, reflash you device with the same or the newest whichever you prefer Id say its from some other app conflicting with the sys.... just a guess but I had the same keyboard and when it was on the on screen disappeared and when it was off the on screen came back no problems, when the bt icon was displayed or not...
my igo slim was stolen and now I have a dinovo mini, but I never even had a hiccup with the igo.
my igo slim was stolen and now I have a dinovo mini, but I never even had a hiccup with the igo.
|
|
2008-04-22
, 07:57
|
|
Posts: 67 |
Thanked: 17 times |
Joined on Aug 2007
|
#25
|
I'm using the 4-row igo keyboard and in the middle of typing, if i press the "shift" key it activates this horrible auto-complete mode.
the worst part is that when i'm done with the bt kb, if i try to get on screen to appear, all that's left is this wierd grey box at the bottom (maybe for handwriting?) but it won't recognize any taps from the stylus and won't allow me an option to switch to on-screen kb (finger or stylus)
this is driving me nuts - maybe i can just disable handwriting? (i don't use it anyways)
the worst part is that when i'm done with the bt kb, if i try to get on screen to appear, all that's left is this wierd grey box at the bottom (maybe for handwriting?) but it won't recognize any taps from the stylus and won't allow me an option to switch to on-screen kb (finger or stylus)
this is driving me nuts - maybe i can just disable handwriting? (i don't use it anyways)
|
|
2008-04-22
, 15:00
|
|
Posts: 5,335 |
Thanked: 8,187 times |
Joined on Mar 2007
@ Pennsylvania, USA
|
#26
|
Originally Posted by sleepkyng
That's not normal. Do you have it configured as "Generic 105-key PC"?
I'm using the 4-row igo keyboard and in the middle of typing, if i press the "shift" key it activates this horrible auto-complete mode.
the worst part is that when i'm done with the bt kb, if i try to get on screen to appear, all that's left is this wierd grey box at the bottom (maybe for handwriting?)
 |
|
2008-04-22
, 16:03
|
|
Posts: 4,930 |
Thanked: 2,272 times |
Joined on Oct 2007
|
#27
|
Originally Posted by lm2
The statusbar is reset to a known safe (i.e. factory default) state on a desktop crash. That includes the BT icon, and puts it on the left. Your config, however, has it on the right. A couple points:
THANK YOU!!!!
You are right, re-enabling the Bluetooth icon in the status bar removed the bug---i got my on-screen keyboard back *almost* immediately upon closing the iGo. I just waited until the icon turned from blue to gray/white and then the on-screen keyboard appeared when called.
This really is a strange bug. I'm not sure if it's made all the stranger in light of the fact that when the tablet has gone berserk in the past (as I described earlier), the bluetooth icon appears as the left-most icon in the status bar, but now that the icon is permanently enabled (as per your suggestion), it appears as the right-most icon. Perhaps this is an inconsequential observation, however.
To change where it is, go Control Panel -> Panels, and select it, then use the /\ and \/ buttons to move it up and down the list.
And, to recover from a desktop crash, Control Panel -> Panels, OK. The config of the task navigator and status bar will be restored. (Home applets also die, but there's no quick way to recover them...)
Originally Posted by sleepkyng
I think it's actually shift+space, or some such...
I'm using the 4-row igo keyboard and in the middle of typing, if i press the "shift" key it activates this horrible auto-complete mode.
the worst part is that when i'm done with the bt kb, if i try to get on screen to appear, all that's left is this wierd grey box at the bottom (maybe for handwriting?) but it won't recognize any taps from the stylus and won't allow me an option to switch to on-screen kb (finger or stylus)
this is driving me nuts - maybe i can just disable handwriting? (i don't use it anyways)
What's that you say? your N800 has no slide-out keyboard? Whaddyaknow, I can't find mine either! But I must have one, or it wouldn't be out...
So just run
Code:
gconftool -t bool -s /system/osso/af/slide-open false
|
|
2008-04-22
, 17:27
|
|
Posts: 1,950 |
Thanked: 1,174 times |
Joined on Jan 2008
@ Seattle, USA
|
#28
|
Benson's solution
does the trick.
But seeing as I'm only the 8th person to report what is, for N800 users, a serious bug with a very non-obvious solution, it would be great if more users would go to the bug-reporting-site and report it. It just takes a minute to get an account and vote for the bug.
(I don't know how else to move it from Low Priority. They give "low priority" to a bug that essentially disables the unit for N800 users?)
Just run
and everything works again.Code:gconftool -t bool -s /system/osso/af/slide-open false
But seeing as I'm only the 8th person to report what is, for N800 users, a serious bug with a very non-obvious solution, it would be great if more users would go to the bug-reporting-site and report it. It just takes a minute to get an account and vote for the bug.
(I don't know how else to move it from Low Priority. They give "low priority" to a bug that essentially disables the unit for N800 users?)
__________________
.
. .
Help Save This Forum for N8x0/Diablo Users! Register and Vote for Solution #1 on this Brainstorm. (The Solution will let you see New Posts with any threads you choose -- like the N900 and Maemo5/Fremantle threads -- filtered out.) (To understand the Solution better, see these posts #17, #18, and #19.)
.
. .
Help Save This Forum for N8x0/Diablo Users! Register and Vote for Solution #1 on this Brainstorm. (The Solution will let you see New Posts with any threads you choose -- like the N900 and Maemo5/Fremantle threads -- filtered out.) (To understand the Solution better, see these posts #17, #18, and #19.)
|
|
2008-04-22
, 18:43
|
|
Posts: 1,950 |
Thanked: 1,174 times |
Joined on Jan 2008
@ Seattle, USA
|
#29
|
Originally Posted by GeraldKo
Hey, I filed my bug report and then just now I got an email that they upped the bug Priority from Low to Medium!
But seeing as I'm only the 8th person to report what is, for N800 users, a serious bug with a very non-obvious solution, it would be great if more users would go to the bug-reporting-site and report it. It just takes a minute to get an account and vote for the bug.
(I don't know how else to move it from Low Priority. They give "low priority" to a bug that essentially disables the unit for N800 users?)
__________________
.
. .
Help Save This Forum for N8x0/Diablo Users! Register and Vote for Solution #1 on this Brainstorm. (The Solution will let you see New Posts with any threads you choose -- like the N900 and Maemo5/Fremantle threads -- filtered out.) (To understand the Solution better, see these posts #17, #18, and #19.)
.
. .
Help Save This Forum for N8x0/Diablo Users! Register and Vote for Solution #1 on this Brainstorm. (The Solution will let you see New Posts with any threads you choose -- like the N900 and Maemo5/Fremantle threads -- filtered out.) (To understand the Solution better, see these posts #17, #18, and #19.)
 |
|
2008-04-22
, 19:01
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#30
|
Originally Posted by GeraldKo
You're welcome.
Hey, I filed my bug report and then just now I got an email that they upped the bug Priority from Low to Medium!
I have an iGo/ThinkOutside Stowaway 4-row keyboard, and I never had any trouble with my on-screen keyboard reactivating immediately after closing the Stowaway. That is, until I just disabled the Bluetooth icon in the status bar as above to test this out. With the status bar's Bluetooth icon disabled, your bug appears. Re-enabling the Bluetooth icon in the status bar kills the bug again.