Active Topics
-
Porting apps to Leste (34)
to Maemo 7 / Leste by Arno_11 - 1 hr, 12 mins ago -
Which is the best N95? What software modifications could be made to it? (0)
to General by Kalatti - 22 hrs, 58 mins ago -
Installing CSSU Stable in year 2024 (1)
to Maemo 5 / Fremantle by Maemish - 1 day, 15 hrs ago -
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,266)
to Maemo 5 / Fremantle by pali - 1 day, 17 hrs ago -
Firefox with Leste (7)
to Maemo 7 / Leste by teroyk - 1 day, 21 hrs ago - more...
| The Following User Says Thank You to For This Useful Post: | ||
 |
|
2014-04-07
, 10:48
|
|
Posts: 562 |
Thanked: 2,744 times |
Joined on Dec 2013
@ Espoo, Finland
|
#282
|
Originally Posted by nieldk
Next time, try following;
Well, the restart seems to not do it when this happens.
systemctl stop toholed.service
Remove toholed for 1 minute and reconnect
systemctl start toholed.service
Originally Posted by nieldk
For me this is matter of life and death
Not a major issue at all, so dont prioritize it
I was thinking could this be caused by hardware connection break between toh and phone, which might get the proximity sensor to reset, and thus loose configuration (and it will not generate interrupt from proximity clear and therefore not wakeup the display), but restart should reconfigure it. Unless the display controller itself gets so messed up that it refuses to show anything.
Updated HW has better reset circuitry, and i have to make some detections to the daemon to see is the display and proximity/ALS sensor still in good mood.
(And repeating me - journal could be very helpful)
|
|
2014-04-07
, 11:05
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#283
|
Originally Posted by kimmoli
Sure, I will provide the journeyctl output next time it happens (didnt happen today so far) - at the moment the journey log is quite short as for toholed.
Next time, try following;
systemctl stop toholed.service
Remove toholed for 1 minute and reconnect
systemctl start toholed.service
For me this is matter of life and death
I was thinking could this be caused by hardware connection break between toh and phone, which might get the proximity sensor to reset, and thus loose configuration (and it will not generate interrupt from proximity clear and therefore not wakeup the display), but restart should reconfigure it. Unless the display controller itself gets so messed up that it refuses to show anything.
Updated HW has better reset circuitry, and i have to make some detections to the daemon to see is the display and proximity/ALS sensor still in good mood.
(And repeating me - journal could be very helpful)
Code:
Apr 07 11:50:56 localhost toholed[1060]: Interrupt: Proximity cleared: ALS Apr 07 11:51:01 localhost toholed[1060]: Time now: 11:51 Battery: 83% Apr 07 11:51:29 localhost toholed[1060]: Interrupt: Proximity detect: ALS Apr 07 11:51:29 localhost toholed[1060]: Interrupt: Proximity cleared: ALS Apr 07 11:51:31 localhost toholed[1060]: Interrupt: Proximity detect: ALS
| The Following User Says Thank You to For This Useful Post: | ||
|
|
2014-04-07
, 18:14
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#284
|
Originally Posted by kimmoli
Complete, verbose log mailed
(And repeating me - journal could be very helpful)
Also, stopping and then starting the service does the trick. Didnt need to remove TOH
|
|
2014-04-07
, 18:31
|
|
Posts: 562 |
Thanked: 2,744 times |
Joined on Dec 2013
@ Espoo, Finland
|
#285
|
ok. thanks for the very verbose log... (just plain journal is enough...)
weird...
In the log you sent me there is no single proximity interrupt...
Even after the restart there is none.
Does the display blank when you place finger over the sensor on right side of the oled, and come back active when removing?
Note, it works better if phone is active, not so well when it sleeps.
I'll add some more diagnostics tomorrow evening.
weird...
In the log you sent me there is no single proximity interrupt...
Even after the restart there is none.
Does the display blank when you place finger over the sensor on right side of the oled, and come back active when removing?
Note, it works better if phone is active, not so well when it sleeps.
I'll add some more diagnostics tomorrow evening.
| The Following User Says Thank You to kimmoli For This Useful Post: | ||
|
|
2014-04-07
, 18:35
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#286
|
yes, proximity is working good
|
|
2014-04-29
, 07:24
|
|
Posts: 86 |
Thanked: 115 times |
Joined on Feb 2014
@ Spain
|
#287
|
I like this TOH, it's very nice! How can I get one?
|
|
2014-04-30
, 06:12
|
|
Posts: 562 |
Thanked: 2,744 times |
Joined on Dec 2013
@ Espoo, Finland
|
#288
|
Any feedback from first-ones ? It has been akwardly silent ...
| The Following User Says Thank You to kimmoli For This Useful Post: | ||
 |
|
2014-04-30
, 11:33
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#289
|
Mine has been working great, except the refresh rate 
Is there absolutely no way this to be fixed/avoided/worked around? Other than that, I had a bit of a release lately and will try to give more feedback during the next 6 holidays here (they start tomorrow).
One problem was a clash between toholed and tohkbd which resulted in a huge memory leak just after restart (in toholed) and Jolla dying in several minutes. Quick work with Terminal and managed to deinstall tohkbd to avoid it.
Is there absolutely no way this to be fixed/avoided/worked around? Other than that, I had a bit of a release lately and will try to give more feedback during the next 6 holidays here (they start tomorrow).One problem was a clash between toholed and tohkbd which resulted in a huge memory leak just after restart (in toholed) and Jolla dying in several minutes. Quick work with Terminal and managed to deinstall tohkbd to avoid it.
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
|
|
2014-04-30
, 11:48
|
|
Posts: 562 |
Thanked: 2,744 times |
Joined on Dec 2013
@ Espoo, Finland
|
#290
|
Originally Posted by Bundyo
I haven't found anything that would improve it.
Mine has been working great, except the refresh rate
Possible to do this is redesign hardware to use 3.3V for the display logic, and extrernal I2C level converter - If the internal oscillator has some relation to supply voltage.
Originally Posted by Bundyo
happy holidays!
... during the next 6 holidays here (they start tomorrow).
Originally Posted by Bundyo
Yep. I'm author of both softwares, and i have some plans to detect what is connected - it would be easier if dirkvl would have put eeprom on the tohkbd. Now seems that i have to make some detection to NFC side, and it seems that i have to store all TOH ID's in the daemons - which sux. Unless those TOH ID's are registered through Jolla, and i get some "name" through the store or something.
One problem was a clash between toholed and tohkbd which resulted in a huge memory leak just after restart (in toholed) and Jolla dying in several minutes. Quick work with Terminal and managed to deinstall tohkbd to avoid it.
And by 'longer period', I mean hours. It works quite well under normal circumstances (eg not in pocket) - but staying in the pocket for hours - not up - makes it not reactivate the display.
Not a major issue at all, so dont prioritize it
Just me I think, being on planes for the last weeks almost constantly LOL