Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 6 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 2 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 11 hrs ago - more...
| The Following User Says Thank You to somedude For This Useful Post: | ||
|
2012-03-18
, 13:56
|
|
Posts: 61 |
Thanked: 29 times |
Joined on Nov 2011
|
#312
|
Originally Posted by ejasmudar
I wasn't able to login to the web client also earlier.
Interestingly, I am also not able to login here:https://web.ebuddyxms.com
Its ok now though
|
|
2012-03-18
, 14:05
|
|
Posts: 61 |
Thanked: 29 times |
Joined on Nov 2011
|
#313
|
I am testing it now, it seems to be very reliable.
Worth mentioning that I removed my nokia account and rebooted my device. it asked me to sign in to a nokia account when it turned it on again.
I did this because none of my notifications were working, Facebook, Pulse or XMS.
So far XMS is doing good (fingers crossed). will need to test other notifications as well
Worth mentioning that I removed my nokia account and rebooted my device. it asked me to sign in to a nokia account when it turned it on again.
I did this because none of my notifications were working, Facebook, Pulse or XMS.
So far XMS is doing good (fingers crossed). will need to test other notifications as well
|
|
2012-03-18
, 14:38
|
|
Posts: 40 |
Thanked: 12 times |
Joined on Dec 2011
|
#314
|
Just to share my recent experience...
I've uninstalled the Nokia store version and reinstalled the updated app at http://beta.ebuddy.com/nokia/xms-qt.deb
Still faced random crashes, power drain by eBuddy and other stuff. So I uninstalled it, used Filebox to find all related 'xms' files and deleted them. Reinstalled again and right now it's working perfectly well.
I've uninstalled the Nokia store version and reinstalled the updated app at http://beta.ebuddy.com/nokia/xms-qt.deb
Still faced random crashes, power drain by eBuddy and other stuff. So I uninstalled it, used Filebox to find all related 'xms' files and deleted them. Reinstalled again and right now it's working perfectly well.
 |
|
2012-03-18
, 14:39
|
|
Posts: 1,312 |
Thanked: 736 times |
Joined on Sep 2009
|
#315
|
Originally Posted by UnlimiteD3k
Tried the method of deleting nokia account and rebooting and adding it back again and nope it still is looking for the data connection for me. Tried a Nokia pulse with same two different accounts and it is working fine as far as the push goes.
I am testing it now, it seems to be very reliable.
Worth mentioning that I removed my nokia account and rebooted my device. it asked me to sign in to a nokia account when it turned it on again.
I did this because none of my notifications were working, Facebook, Pulse or XMS.
So far XMS is doing good (fingers crossed). will need to test other notifications as well
|
|
2012-03-18
, 14:44
|
|
Posts: 8 |
Thanked: 1 time |
Joined on Jan 2012
|
#316
|
Originally Posted by somedude
Didn’t have to re-flash. I found another way and now the app its working again, first I uninstalled the app then using file manager went to /home/user/.local/share/data and delete eBuddy folder. Then I installed the app again and it worked without any trouble.
did reflash help any?
| The Following User Says Thank You to Noztradamus For This Useful Post: | ||
|
|
2012-03-18
, 14:51
|
|
Posts: 397 |
Thanked: 185 times |
Joined on Oct 2011
|
#317
|
Originally Posted by Noztradamus
if you talked about push notification, no it didn't work for me. But i found that uninstalling the newer xms, delete nokia account, reboot, add nokia account, install xms from Nokia Store instead, try chat with ur friends on ebuddy a couple of times and it works for me thus far.
Didn’t have to re-flash. I found another way and now the app its working again, first I uninstalled the app then using file manager went to /home/user/.local/share/data and delete eBuddy folder. Then I installed the app again and it worked without any trouble.
|
|
2012-03-18
, 15:07
|
|
Posts: 1,312 |
Thanked: 736 times |
Joined on Sep 2009
|
#318
|
Originally Posted by Noztradamus
WOW What a run-around to get an application working on a phone,
Didn’t have to re-flash. I found another way and now the app its working again, first I uninstalled the app then using file manager went to /home/user/.local/share/data and delete eBuddy folder. Then I installed the app again and it worked without any trouble.
but this did the trick so far it is not looking for a data connection, just xmsed the xms bot, now need to find if the push works with this, checked with pulse and its working.
|
|
2012-03-18
, 15:12
|
|
Posts: 8 |
Thanked: 1 time |
Joined on Jan 2012
|
#319
|
Originally Posted by kai_en
The issue was not push notifications, I could not send or receive any messages from my n9 because the app was keep “searching for network connection”.
if you talked about push notification, no it didn't work for me. But i found that uninstalling the newer xms, delete nokia account, reboot, add nokia account, install xms from Nokia Store instead, try chat with ur friends on ebuddy a couple of times and it works for me thus far.
I used the web browser to send and receive messages without any problem but the app was causing the trouble. Then I solved the issue by following the steps described on my previous post.
|
|
2012-03-18
, 15:16
|
|
Posts: 8 |
Thanked: 1 time |
Joined on Jan 2012
|
#320
|
Originally Posted by somedude
Well if the trick didn’t work I don’t know what else to recommend solving this issue. Currently I’m not using the app from the ovi store but the one from the ebuddy xms beta page on Facebook.
WOW What a run-around to get an application working on a phone,
but this did the trick so far it is not looking for a data connection, just xmsed the xms bot, now need to find if the push works with this, checked with pulse and its working.
eBuddy developers keep updating the app for other platform but for meego its not updated since dec-2011.
"For past couple of days non of the meego users of XMS been able to either receive or send messages, is there any clarifiaction about this error from the team? has it even been looked at? is there any working solution? How long are we supposed to wait for the resolution on this?"