![]() |
Re: Slide 2 Answer
It's possible - not sure if it's recommended.
Camp using com.nokia.csd.Call /com/nokia/csd/call and trigger Coming to kill whatever you want - but ohmd aready tries to prioritize when a call is incoming. You could always grab the top processes sorted by load/cpu usage and kill it - but you'd lose whatever data was open. |
Re: Slide 2 Answer
Quote:
If something like MicroB is running there is in the most cases several MB of swap used. And it need's time to fetch more RAM to load the needed parts for the call ui. Perhaps you could get more slowdown at the beginning because of the cleanup routines after killing the prozesses. So, as hawaii already said, it's not the best idea. :) |
Re: Slide 2 Answer
Just asking..is the phone dialer application always loaded into the ram? if not doing that would help right?? or somehow if we can always keep the phone application open!
or in the next phone nokia can dedicate some ram or something like that to the Phone functions of the N9XX phone ( which will be coming out ) so as to make things faster :/. this will help? sorry if its been answered before! |
Re: Slide 2 Answer
Quote:
Simple and cheap solution! Yes, they have to develop how to communicate to this processor... But I would say it should not harder than the handling for the proximity sensor or the camera. And they don't need the software tuning and the not working bad tricks anymore. A solid solution. They could still use the standard linux part to show a ui, incomming call messages, and so on... but everything handled over d-bus and the driver between. But nothing critical on the software side. Everything else, the "ringtone" and "the Buttons" are hardware side handled inside the cheap Series40 Chip so that we are able to answer a call even if the kernel are running amok! :D But dreams could take sometimes a little bit longer... :rolleyes: |
Re: Slide 2 Answer
know what would be best.. Using a Series 60 touch UI dialer application on Meego... Develop it in QT. and make it run on the 2nd processor and as a Layer on top of the linux OS..so even if the phone is unstable...You can at least pick up calls.. that would be a dream come true for developers also...fudge all you want with the Linux and no need to worry about your calls..
|
Re: Slide 2 Answer
Quote:
You know, you could have a phone in your pocket and use N900 to link to the old phone via BT. An app could handle everything, but instead of call via GSM modem, call via BT, acting as a car kit. You're a genius. 90% of my problems, solved. And check out the standby on that baby. And since Phone is no longer needed, we can have an independent contacts app with renaming of numbers and GPS coords. OMG. That's ... that's IT! Where did I put that N80 with a washed out screen? |
Re: Slide 2 Answer
Just one word :
Battery. and why would i want to carry 2 phone when both of them have calling capabilities. i did this with my Palm Zire a few years ago...it sucked :P |
Re: Slide 2 Answer
Quote:
I am starting to think slide to answer may never be a plausible option and perhaps that's why Nokia went with the simple red & green buttons option? |
Re: Slide 2 Answer
I installed the deb from post #31 yesterday (ver 0.0.1) and had an update this morning (ver 0.1 I think).
Have I installed the qt-version, when I installed that update? There was a change in the GUI, but it wasn't like the screenshot from earlier in the thread. It was with two thin slides, that was from one end of the screen to the other. /oxpo |
Re: Slide 2 Answer
Quote:
Both use the same package name. |
Re: Slide 2 Answer
Hey, I just tried GTK version from post #31. Thanks!
It is a little bit confusing. Sliding right = answer Sliding left = reject but the right "button" = reject left "button" = answer I will continue playing with it. Could you make the window appear like in the QT Version? btw. the version string of the package is also confusing. I'll need to downgrade now to get the gtk version... |
Re: Slide 2 Answer
I like this very much. Havn't rejected a call by mistake since I installed it.
I agree with flexxxv, that the buttons are a little confusing, the texts should change place and I think another color combination would be better (I didn't see that there were text on the buttons at first) I hope someone can contiue to develop this. Sadly, all I can do is test, as I can't program. /oxpo |
Re: Slide 2 Answer
Sorry for doublepost, but I wanted to bump this too.
Is there anyone, with programing exerience, that can take a look at this. I just got my first call, from someone who is not in my contact list, and the screen showed a very dear friend. I really like this program, and it has helped me alot, and I HOPE that someone can help us (we with no programing experience that use this) and get it to work, even with unknown callers. Regards oxpo |
Re: Slide 2 Answer
1 Attachment(s)
@oxpo:I never coded in GTK (and have no scratchbox here to test this).
Maybe it works, maybe it doesn't even compile...if someone can build and test it... |
Re: Slide 2 Answer
1 Attachment(s)
I built the "new" package.
I just fixed the "unknown contact" problem. I didn't test it, let me know if it works. ;) |
Re: Slide 2 Answer
Quote:
/oxpo |
Re: Slide 2 Answer
Quote:
|
Re: Slide 2 Answer
The new version can handle numbers that aren't in the contact list. The only thing that doesn't work now are unknown numbers (at least with Swedish settings, where they are called "Okänt nummer"), where the program displays the last number (or contact) that has called before the unknown number.
/oxpo edit: It looks like the problem is the Swedish language settings. When I tried to change to English, the program displays the standard avatar, and no number, when an unknown number is calling. /oxpo |
Re: Slide 2 Answer
will test also
|
Re: Slide 2 Answer
Quote:
|
Re: Slide 2 Answer
Quote:
Maybe slide2answer_gtk Thanks for helping with this. /oxpo |
Re: Slide 2 Answer
Ok, I'll change the package name and version number.
I tried now the app...wouldn't be better to slide to the right to accept the call and slide to the left to reject the call (now it's the opposite)? |
Re: Slide 2 Answer
Quote:
/oxpo |
Re: Slide 2 Answer
1 Attachment(s)
Here you go, untested like the previous one. :p
Remove manually the previous slide2answer package before installing this. Code:
Changelog: |
Re: Slide 2 Answer
Change the name back to slide2answer and upload it to maemo.org's repositories (if you want to be a maintainer on the maemo.org page just request it, I don't mind ;)), that way it'll upgrade from the Qt version to the Gtk one.
|
Re: Slide 2 Answer
awesome stuff!
if I had my computer id upload a vid |
Re: Slide 2 Answer
Now it's working perfect for me. Both numbers not in contact list and unknown numbers work, both in English and Swedish.
Many thanks for this. I havn't rejected a phonecall by mistake since I installed this and that is a BIG change. /oxpo |
Re: Slide 2 Answer
Quote:
Btw I don't want to be the mantainer (someone with gtk experience would be better). :p @oxpo: thanks for the feedback. Now you can remove the package slide2answer-gtk and install slide2answer from the repository (well wait for version 0.1.1 to be imported). |
Re: Slide 2 Answer
Quote:
/oxpo |
Re: Slide 2 Answer
can we have a screenie, guys?
|
Re: Slide 2 Answer
Quote:
|
Re: Slide 2 Answer
i've restarted a phone after i've installed slide2answer, but the original thingy with only 2 buttons is back. what should i do?
EDIT: Re-installing slide2answer didn't help... still waiting for smbd who can help me. |
Re: Slide 2 Answer
can I look the rotation when it call? I will have it in portrait, it would be faster answer and not so much lagg.
|
Re: Slide 2 Answer
wow real great work, you guys are geniuses!
|
Re: Slide 2 Answer
How fast does the interface comes up when a call comes in? The original version took a goos 4-5 secs to come up... Does the Gtk vefrsion comes up faster?
|
Re: Slide 2 Answer
comes up straight away!
|
Re: Slide 2 Answer
gr8 work guys but can u make the caller photo bigger would be fantastic
|
Re: Slide 2 Answer
Slide to answer i think should never be implemented on the N900 because it will wear down the mechanics on the device and the keyboard will become loose with time.
I have had to deal with 2 keyboard problems so far because of this issue. |
Re: Slide 2 Answer
Quote:
|
Re: Slide 2 Answer
Quote:
|
All times are GMT. The time now is 09:58. |
vBulletin® Version 3.8.8