Just to let you know, that IMHO the analysis and information you are
collecting are even more important than rewriting the proprietary
components. It helps both understanding the inner workings of the
system (what about writing a Maemo 5 Internals document for the
proprietary parts? :)) and help
What I want is the output from this shell script. I also want to know what
the name of your service provider is (i.e. the company you pay for service)
as well as the name of your operator (i.e. the company that actually
operates the cell towers and/or matches the MNC/MCC that get output by the
On 2011-09-07 7:20 AM, Jonathan Wilson wrote:
There is source at
http://repository.maemo.org/pool/maemo5.0/free/r/rtcom-eventlogger/ for
version 1.4-4+0m5 which matches whats on my fully updated phone.
Brilliant, thanks, exactly what I was after. I went repo hunting before
but must've missed
Just wondering...there's a code dump of this component on Gitorious:
https://maemo.gitorious.org/maemo-rtcom/rtcom-eventlogger
...but AFAICS it appears to be the pre PR1.1 code (it's missing a few of
the API changes and uses the original DB name 'el.db' rather than the
updated 'el-v1.db' name.
I've successfully pushed before, but now I'm trying to push new changes,
but it's failing with (repo name changed):
git.exe push -v --progress origin master:master
Pushing to https://mr_...@vcs.maemo.org/git/reponame
Fetching remote heads...
refs/
refs/heads/
refs/tags/
updating
On 2011-08-07 11:29 AM, koos vriezen wrote:
FWIW I had to run 'git config --global --add http.sslVerify false'
before I could push this week. Wasn't so a few months ago IIRC.
(See, http.sslVerify option at
http://kernel.org/pub/software/scm/git/docs/git-config.html )
Thanks for the reply.
Ok, I'll admit I'm new to Git as a first point of business...but I'm
trying to upload my initial push to my new Garage Git repo, but I keep
getting the same error that tells me nothing at all about how to fix things:
Pushing to https://vcs.maemo.org/git/qwerkisync/
error: Cannot access URL
I'm not sure what the problem is, but maybe QDBusInterface isn't
happy with the result of the introspection. Try not using
QDbusInterface, and just send the method on QDBusConnection.
Brilliant, works perfectly without any hacks:
QDBusMessage
I'm trying to bring up the Accounts UI using DBus in a Qt application:
const char * NOKIA_SERVICE_ACCOUNTS_UI(com.nokia.AccountsUI);
const char * NOKIA_PATH_ACCOUNTS_UI(/com/nokia/AccountsUI);
const char * NOKIA_IFACE_ACCOUNTS_UI(com.nokia.Accounts);
QDBusInterface