Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 1 day, 3 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 2 days, 2 hrs ago - more...
pali |
2015-01-02
, 11:05
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#51
|
sudo u-boot-update-bootmenu
| The Following User Says Thank You to pali For This Useful Post: | ||
|
|
2015-01-02
, 11:07
|
|
Posts: 3,074 |
Thanked: 12,960 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#52
|
Originally Posted by pali
are we sure it is a problem? I mean - does mce in R1.3 behave differently?
So it is problem of mce which is in cssu, see:
https://gitorious.org/community-ssu/...witches.c#L324
It disable proximity gpio-switch if call is not active or not ringing.
@freemangordon: what to do now?
anyway, I'll check what stock mce does as soon as I get back to my desktop.
EDIT: code in stock mce and mce in cssu is 100% identical, it must be something else
__________________
Never fear. I is here.
720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900
Community SSU developer
kernel-power developer and maintainer
Never fear. I is here.
720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900
Community SSU developer
kernel-power developer and maintainer
Last edited by freemangordon; 2015-01-02 at 13:06.
| The Following 5 Users Say Thank You to freemangordon For This Useful Post: | ||
|
|
2015-01-04
, 02:26
|
|
Posts: 242 |
Thanked: 169 times |
Joined on Nov 2011
|
#53
|
I forgot to say: I was running latest CSSU stable (no thumb) and kp52 before the proximity stopped working (no u-boot at all).
Only packages updated were kp and kp settings and after that proximity stopped working.
I don't know how can I help to debug this, in case tell me useful informations I could provide (logs, cat, etc..)
Last edited by enne30; 2015-01-04 at 02:35.
Only packages updated were kp and kp settings and after that proximity stopped working.
I don't know how can I help to debug this, in case tell me useful informations I could provide (logs, cat, etc..)
Last edited by enne30; 2015-01-04 at 02:35.
|
|
2015-01-14
, 17:25
|
|
Posts: 186 |
Thanked: 79 times |
Joined on Feb 2010
|
#54
|
I also have no wifi w/o sim card
|
|
2015-01-14
, 18:06
|
|
Posts: 186 |
Thanked: 79 times |
Joined on Feb 2010
|
#55
|
I was unable to insmod wl1251_spi.ko due to Unknown symbol crc7
|
|
2015-01-14
, 21:39
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#56
|
see first post where is link to packet injection load script
 |
|
2015-01-14
, 21:52
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#57
|
Originally Posted by hardkorek
Let me guess. Your WiFi is on channel 13, right?
I also have no wifi w/o sim card
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
|
|
2015-01-15
, 09:23
|
|
Posts: 186 |
Thanked: 79 times |
Joined on Feb 2010
|
#58
|
I have tried the script, but possibly older version. I also have the same error using interface switcher applet(can not remember exact name now).
channel doesn't matter because I can not load all driver modules so no interface to interact with channel.
channel doesn't matter because I can not load all driver modules so no interface to interact with channel.
|
|
2015-07-27
, 12:37
|
|
Posts: 242 |
Thanked: 169 times |
Joined on Nov 2011
|
#59
|
Originally Posted by enne30
I resolved uninstalling and installing again packages
Maybe this is related with shortcutd not working: in dmesg I see proximity log only while making a call;
otherwise I can trigger proximity sensor but no log results in dmesg.Code:[82871.672821] proximity (GPIO 89) is now open [82872.453887] proximity (GPIO 89) is now closed [82874.008972] proximity (GPIO 89) is now open [82874.789886] proximity (GPIO 89) is now closed [82875.571044] proximity (GPIO 89) is now open [82905.782165] slide (GPIO 71) is now closed [82907.329010] slide (GPIO 71) is now open
- shortcutd
- proximityd (shortcutd alone did not resolve)
I can confirm no event is shown in dmesg, although shortcutd now is working fine;
while triggering proximity during calls results in dmesg showing proximity events.
So my previous post reports normal behaviour, it's not a bug.
| The Following User Says Thank You to enne30 For This Useful Post: | ||
|
|
2015-09-15
, 11:56
|
|
Posts: 242 |
Thanked: 169 times |
Joined on Nov 2011
|
#60
|
For the sake of knowledge, I had same problem reported above upon rebooting.
I found the problem was related to proximityd not starting on boot (shortcutd needs proximityd running).
I solved changing this line into /etc/event.d/proximityd
to this one (I saw shortcutd starts this way)
Now proximityd starts properly on boot and shortcutd works good.
This change made necessary since upgrade to kp53, as reported previously.
Last edited by enne30; 2015-09-15 at 12:06.
I found the problem was related to proximityd not starting on boot (shortcutd needs proximityd running).
I solved changing this line into /etc/event.d/proximityd
Code:
#start on started dbus
Code:
start on started hildon-desktop
This change made necessary since upgrade to kp53, as reported previously.
Last edited by enne30; 2015-09-15 at 12:06.
| The Following 4 Users Say Thank You to enne30 For This Useful Post: | ||
