Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 17 hrs, 40 mins ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 18 hrs, 54 mins ago -
Maemo repository (3)
to Community by torsen - 1 day, 10 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 8 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 14 hrs ago - more...
| The Following User Says Thank You to Flowcont For This Useful Post: | ||
|
2013-10-11
, 10:55
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#132
|
Originally Posted by Flowcont
The usual way I start such reverse engineering tasks is I try to get as much raw data as possible, and then try to make sense of it.
If you could give us some hints of the work you've done and where/how to start working on it(even create a new thread) that'd be awesome.
Thanks for your work.
I compiled the driver module (bcm4751-gps.ko) with a lot of debug printouts, restarted nped, started maps and looked at the results to see what the intresting parts were.
Then I added more thorough logging to get at the data buffers passed between the kernel driver and nped.
Now next step would be to try to make sense of the data, and try to decipher the protocol specification. When that's done the positioning daemon can be replaced with a new implementation.
The source of nped is closed, but the algorithms on GPS calculation are public so the task should be doable.
 |
|
2013-10-11
, 12:26
|
|
Posts: 72 |
Thanked: 239 times |
Joined on Sep 2013
|
#133
|
what about CMT(cell modem) in 3.5 kernel?
|
|
2013-10-11
, 17:51
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#134
|
Originally Posted by juiceme
why cant we just access that chip direcly? or did Nokia put some firmware inside that chip that is binary crap instead of NMEA?
The usual way I start such reverse engineering tasks is I try to get as much raw data as possible, and then try to make sense of it.
I compiled the driver module (bcm4751-gps.ko) with a lot of debug printouts, restarted nped, started maps and looked at the results to see what the intresting parts were.
Then I added more thorough logging to get at the data buffers passed between the kernel driver and nped.
Now next step would be to try to make sense of the data, and try to decipher the protocol specification. When that's done the positioning daemon can be replaced with a new implementation.
The source of nped is closed, but the algorithms on GPS calculation are public so the task should be doable.
Btw. just found out that Nexus7 using same chip. wonder if android daemon is open source.
Not have a clue what I am talking about here but maybe doable via libhybris as a second alternative?
also found this:
https://gitorious.org/meif_protocol/...5e8ab2578808b:
__________________
Keep safe and healthy
Keep safe and healthy
Last edited by mikecomputing; 2013-10-11 at 18:05.
| The Following User Says Thank You to mikecomputing For This Useful Post: | ||
|
|
2013-10-11
, 18:05
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#135
|
Originally Posted by mikecomputing
You got it nailed!
why cant we just access that chip direcly? or did Nokia put some firmware inside that chip that is binary crap instead of NMEA?
Nobody makes (or uses actually) anything that gives out NMEA any longer
It's all about power saving and cost today. GPS chips are just the RF frontend and decoder, and the actual positional calculation is done by the main CPU. This makes kind of sense as then it is easier to use ephemerals downloaded thru net.
Most chipsets implement a variation of a proprietary binary protocol called MEIF ghich has been developed by Nokia (and N9 uses it also)
| The Following 4 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2013-10-11
, 18:09
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#136
|
Originally Posted by mikecomputing
Unfortunately that part is closed. The replicant people are also looking at it though.
Btw. just found out that Nexus7 using same chip. wonder if android daemon is open source.
Not have a clue what I am talking about here but maybe doable via libhybris as a second alternative?
 |
|
2013-10-22
, 22:27
|
|
Posts: 84 |
Thanked: 43 times |
Joined on Nov 2012
|
#137
|
Sounds like we are gonna be able to see a port for N9 soon, I presume.
Any chances, what do you think?
__________________
Nokia 808 PureView - 113.010.1507 / Nokia N9 - PR1.3 (OC @ 1.25 GHz) / Jolla - 1.0.8.21
Nokia 808 PureView - 113.010.1507 / Nokia N9 - PR1.3 (OC @ 1.25 GHz) / Jolla - 1.0.8.21
| The Following User Says Thank You to torcida For This Useful Post: | ||
|
|
2013-10-23
, 14:41
|
|
Posts: 83 |
Thanked: 40 times |
Joined on May 2013
@ Slovenia
|
#138
|
will there be any theme similar to meego (eg. Icons an the swipe transtitions, the system unrestricted ui) because i think MeeGo's biggest problem is the lack of apps... What i think to have the sailfish platform and meego look...
|
|
2013-10-23
, 17:44
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#139
|
Originally Posted by anzx
Well, you could just add patched qt-components-qt5 in the path of Sailfish Silica. to have a similar look. But you'll need to patch 'em urself or get them patched
will there be any theme similar to meego (eg. Icons an the swipe transtitions, the system unrestricted ui) because i think MeeGo's biggest problem is the lack of apps... What i think to have the sailfish platform and meego look...
 |
|
2013-10-23
, 18:47
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#140
|
Hopefully, or rather probably, there will be a working Sailfish image for the N9 the same day it's released for the Jolla. Problem will be Wayland but hopefully it'll work well enough. Not sure if it's possible to run Sailfish's UX on X11 without having the source available.
__________________
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
| The Following User Says Thank You to xerxes2 For This Useful Post: | ||
Thanks for your work.