LinuxMCE Forums
General => Users => Topic started by: hari on December 10, 2008, 10:46:09 pm
-
Hi girls and guys,
if you want to try the PlutoMO (native, not Java) on a Symbian S60 3rd edition phone, you should read this post:
http://forum.linuxmce.org/index.php?topic=6858.msg42815#msg42815
br, Hari
-
Hi Hari
I just installed the last version of your Symbian MO on my E65, and I can confirm that it is working. Picture does not fit the phone screen, but probably this is the sizing issue your were mentioning on your post.
Also in your demo video the menu appears to be not on full screen ... so basically it's ok.
I noticed that even with native MO I can't use the red button to stop media. If I press red button MO exits, and media keeps playing.
I get this behaviour also with JavaMO, and I thought that maybe java cannot catch all keypresses.
I suspect instead that this may have something to do with the phone design, because on this phone I installed also TomTom Navigator, and every time I press red button TomTom exits immediately ...
Again thanks for your effort.
Regards
Marco
-
Hi Hari
I just installed the last version of your Symbian MO on my E65, and I can confirm that it is working. Picture does not fit the phone screen, but probably this is the sizing issue your were mentioning on your post.
Also in your demo video the menu appears to be not on full screen ... so basically it's ok.
I noticed that even with native MO I can't use the red button to stop media. If I press red button MO exits, and media keeps playing.
there seems to be a change of the red button handling in the 3rd edition. Iirc this can be adjusted.
I get this behaviour also with JavaMO, and I thought that maybe java cannot catch all keypresses.
yes, this is a j2me limitation
I suspect instead that this may have something to do with the phone design, because on this phone I installed also TomTom Navigator, and every time I press red button TomTom exits immediately ...
yup
Again thanks for your effort.
you are welcome :-)
best regards,
Hari
-
MarcoZan, what is the resolution of the E65?
br, Hari
-
MarcoZan, what is the resolution of the E65?
br, Hari
240 x 320 pixels
-
ok, some bug fixes (e.g. now caches screens locally) and hard coded resolution to 240x320 (used by many phones): see attachement
br, Hari
-
Hari, you're the best!!!
-
no, it is not me, it is _we_ :-)
-
I've installed it on my N95 8gb, it installed without any errors. but trying to run it just brings up a gray square and nothing happenes ...
Am I doing something wrong ?
thnx
Itsik
-
Hi Hari
I'm sorry for not having replied to your question in a timely fashion ... these days I'm pretty busy at work.
I've dowloaded an installed your last version of MO, tonight when I get home I will test it and let you know.
Danke shöne
Marco
-
tried to get it running on a Nokia N80. Installation went fine but after executing PlutoMO nothing happens...
appreciate any help
IF
-
tried to get it running on a Nokia N80. Installation went fine but after executing PlutoMO nothing happens...
appreciate any help
IF
The bluetooth should be on on your phone, bluetooth dongle should be recognized by core/MD. Check the BD and DCERouter logs under /var/log/pluto to find more info.
-
The bluetooth should be on on your phone, bluetooth dongle should be recognized by core/MD. Check the BD and DCERouter logs under /var/log/pluto to find more info.
Everything was on and the phone and MD were paired, still just the gray square and nothing else ... (N95 8GB) ...
-
Hi Hari
just a brief update about using last MO on my E65.
Display size is now correct, nevetheless I'm experiencing an issue when displaying media list. Basically all media titles are displayed in a microsopic char size, so they are unreadable.
Also in the main screen when I press the right button to change room a popup appears with some option to exit app.
Still facing issue with submenu (i.e they displayed somehow "shifted" by one position). This is the same issue I was facing also with javaMO so I suspect it has to do with my orbiter. Will try to delete and rebuild from scratch and let you know.
Since I mentioned it, after installing last version of MO on my E65 suddenly JavaMO stopped working. It basically starts but it shows me a blank screen, even if it accepts keystrokes and seems to react properly (i.e. if I press keys for a lighting scenario, the proper action is executed). Maybe it has something to do with the local caching?
Thanks again for your great job
Marco
-
no, the problem is that even if the application exits, the sdp record stays on the phone. So the bluetooth_dongle finds the entry with channel 19 first and does not look further for the real javamo channel.. After a phone restart the JavaMO should work fine.
Regarding caching, that was already there, I just had to fix some paths.
I've also seen the "messed" buttons, where they seem to shift a position on the grid. I agree that this is prolly a bug in Bluetooth_Dongle as I've also seen it with JavaMO.
The unreadable fonts will be addressed next, I'm sure this should be a minor tweak.
br, Hari
-
Hi,
bluetooth is defenitely on and also the JavaMo kind of works. Although it's not scaled right and the backlight comes and goes every few seconds but at least I can control the system. No chance to do so with PlutoMO because the application will not even start.
Here is the log:
05 12/22/08 12:04:44.081 [33;1mGoing to rotate logs...[0m <0xb3766b90>
05 12/22/08 12:04:50.852 [33;1mInquiry complete
[0m <0xb6790b90>
05 12/22/08 12:04:50.852 [33;1mInquiry started[0m <0xb6790b90>
05 12/22/08 12:05:03.674 [33;1mInquiry complete
[0m <0xb6790b90>
05 12/22/08 12:05:03.674 [33;1mLost connection to device: mac 00:12:D2:B6:7B:5C, id N/A[0m <0xb6790b90>
05 12/22/08 12:05:03.675 [33;1mInquiry started[0m <0xb6790b90>
05 12/22/08 12:05:06.458 [33;1mCannot remove device 0 from the detection list of 0[0m <0xb4f8db90>
05 12/22/08 12:05:06.458 [33;1mWaiting any operation with the socket to finish...[0m <0xb4f8db90>
05 12/22/08 12:05:12.034 [33;1mBDCommandProcessor_Linux_Bluetooth is destroyed.[0m <0xb4f8db90>
05 12/22/08 12:05:12.079 [33;1mvoid ClientSocket::Disconnect() on this socket: 0x827a128 (m_Socket: 10)[0m <0xb4f8db90>
05 12/22/08 12:05:12.082 [33;1mSocket::ReceiveData m_Socket 10 m_bQuit_get()1[0m <0xb3766b90>
05 12/22/08 12:05:12.082 [33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: 10 Command_Impl1 Dev #33[0m <0xb3766b90>
05 12/22/08 12:05:16.498 [33;1mInquiry complete
[0m <0xb6790b90>
05 12/22/08 12:05:16.500 [33;1mInquiry started[0m <0xb6790b90>
05 12/22/08 12:05:29.315 [33;1mInquiry complete
[0m <0xb6790b90>
05 12/22/08 12:05:29.315 [33;1mInquiry started[0m <0xb6790b90>
05 12/22/08 12:05:42.133 [33;1mInquiry complete
[0m <0xb6790b90>
05 12/22/08 12:05:42.133 [33;1mInquiry started[0m <0xb6790b90>
05 12/22/08 12:05:54.951 [33;1mInquiry complete
[0m <0xb6790b90>
05 12/22/08 12:05:54.951 [33;1mInquiry started[0m <0xb6790b90>
05 12/22/08 12:05:58.976 [33;1mDetected device mac: 00:12:D2:B6:7B:5C link quality: -69[0m <0xb4f8db90>
05 12/22/08 12:05:58.982 [33;1mAbout to connect to PlutoMO. We'll suspend scanning...[0m <0xb578eb90>
05 12/22/08 12:05:58.982 [33;1mSuspending scanning...[0m <0xb578eb90>
05 12/22/08 12:05:59.027 [33;1mInquiry complete
[0m <0xb6790b90>
01 12/22/08 12:06:00.563 [31;1mreceived channel: 19
[0m <0xb578eb90>
05 12/22/08 12:06:00.636 [33;1mCan't connect RFCOMM socket 00:12:D2:B6:7B:5C, channel 19[0m <0xb578eb90>
05 12/22/08 12:06:00.636 [33;1mWaiting any operation with the socket to finish...[0m <0xb578eb90>
05 12/22/08 12:06:00.636 [33;1mBDCommandProcessor_Linux_Bluetooth is destroyed.[0m <0xb578eb90>
05 12/22/08 12:06:00.636 [33;1mFailed to connect to PlutoMO. We'll resume scanning[0m <0xb578eb90>
05 12/22/08 12:06:00.636 [33;1mResuming scanning...[0m <0xb578eb90>
05 12/22/08 12:06:00.730 [33;1mInquiry started[0m <0xb6790b90>
05 12/22/08 12:06:04.111 [33;1mDetected device mac: 00:12:D2:B6:7B:5C link quality: -68[0m <0xb4f8db90>
05 12/22/08 12:06:04.114 [33;1mAbout to connect to PlutoMO. We'll suspend scanning...[0m <0xb578eb90>
05 12/22/08 12:06:04.114 [33;1mSuspending scanning...[0m <0xb578eb90>
05 12/22/08 12:06:04.124 [33;1mInquiry complete
I can't really interpret it...
thanks for any help!
IF
-
hi hari,
i try to install on my NOkia E71.
this application install but not run !
can you help me ?
thank you !
-
e71? runs fine here on a n73..
do you get any errors?
br, Hari
-
install fine no erro.
but when I execute plutomo, the screen only blinks
-
i have instaled on E61 too and aplication run , but no connect to dcerouter
-
@possy: could you plz try on your e61?
br Hari
-
i tried on E61 whitout sucess . is a gray square with no data !
-
@possy: could you plz try on your e61?
No Sir, hari, Sir.
No 0710 system available atm, Sir!
-
Hi Fernandes,
I had the same issue in my N95, (the application didn't start up and the screen blinks once), I uninstalled the PlutoMO, then reboot the phone and I installed again, now It's works but you will need to do this, every time that the PlutoMO crashes.
I have some problems with the buttons but no problems with PlutoMO at the startup.
I hope it helps.
Thanks
Hernan
-
@possy: could you plz try on your e61?
e61 isn't working here too. Hari, shall I send you an e61 for testing purpose?
eNoodle
-
Hi eNoodle,
thanks for the offer. But as I'm so busy with many things it would be dishonest to accept it. I cannot guarantee to work on that. My primary goal was to recompile the v2 version on Linux (for the auto-builder). That was done. My second goal was to look into the S60 3rd port. The basics are done. It needs some tweaks for different screen sizes on nowadays phones.
The E61 has very nice on device debug abilities (even over WLAN). You maybe want something like s60_3_1_app_trk_2_7.sisx. This should allow you to see the outputs/error messages from the failed app start on the phone (you also can do some other very interesting things with that one, but we better not discuss them here :-) ). I could not further test it as the data cable on my N73 got a loose contact.
If you still want to send the phone be aware that i really like that model and that I'm a lazy bitch and prolly will not fix the mobile orbiter but use it as a WLAN/SIP phone until you have grey hair :-p
best regards,
Hari
-
The E61 has very nice on device debug abilities (even over WLAN). You maybe want something like s60_3_1_app_trk_2_7.sisx. This should allow you to see the outputs/error messages from the failed app start on the phone (you also can do some other very interesting things with that one, but we better not discuss them here :-) ). I could not further test it as the data cable on my N73 got a loose contact.
Hi hari,
Thanks for information. I'll get that application and try to get more information out of it.
Greets,
eNoodle
-
Any sollution to the gray square thing ?
Plutomo is still a no go with the N95 8GB
-
the grey square is just the graphic area where stuff gets drawn. I'd assume you have some bluetooth issue, as the grey area shows up as soon as the dongle connects, but you seem to miss the sent images..
Did you pair the phone and the dongle?
best regards,
Hari
-
ok, some bug fixes (e.g. now caches screens locally) and hard coded resolution to 240x320 (used by many phones): see attachement
br, Hari
Hello,
I'm getting "Invalid application certificate" error when I install PlutoMO application on my Nokia E65.
Does anyone experienced the same error?
-
Hi Hari ,
i replace my bluetooth and now Nokia E71 work fine !!
only insue is screen size ! is a version for 320 x 240 pixels, 2.36 inches
other insue is a back button "C" in some screen have to sloow response !
thanks !
-
somebody needs to add a new BD command, like BD_PC_ReportScreenSize.. and need to add resolution detection to the symbian code. For now you could hard code the resolution and recompile the symbian orbiter.
Regarding the slow response on "C", can you elaborate in detail what you are encountering?
br, Hari
-
HI hari ,
i trie to go from submenu to main screen but on querty keyboard i need to press a upper case + "c" i need to press several times to work !
is a big problem go to back on menu !