Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 10 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 11 hrs ago -
Maemo repository (3)
to Community by torsen - 3 days, 3 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 7 hrs ago - more...
| The Following User Says Thank You to caprico For This Useful Post: | ||
|
2014-05-28
, 13:36
|
|
Posts: 61 |
Thanked: 17 times |
Joined on Jan 2012
|
#62
|
I hope you could help us. what are we doing wrong?
|
|
2014-05-28
, 15:06
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#63
|
well, I will look at this, the culpritt is
"which: no laptop-detect in"
I am not sure why you have this issue, I just had to completely reinstall my device, and I didnt have this issue.
"which: no laptop-detect in"
I am not sure why you have this issue, I just had to completely reinstall my device, and I didnt have this issue.
| The Following User Says Thank You to For This Useful Post: | ||
|
|
2014-05-28
, 17:19
|
|
Posts: 108 |
Thanked: 417 times |
Joined on Oct 2013
|
#64
|
Originally Posted by nieldk
Thanks a lot - the "no laptop-detect" culprit suprised me as well. I'll try to find out more about it, but no success so far.
well, I will look at this, the culpritt is
"which: no laptop-detect in"
I am not sure why you have this issue, I just had to completely reinstall my device, and I didnt have this issue.
@az2111: What message do you get when opening prey.sh via terminal next to response status 422?
|
|
2014-05-28
, 18:04
|
|
Posts: 108 |
Thanked: 417 times |
Joined on Oct 2013
|
#66
|
Just did that (re-install) that and updated the config file with my information. Running /usr/share/prey/prey.sh --check gave back the same "no laptop-detected in..." and 422 status messages like previously.
I wonder if it has to do something with my new Prey account. I set it up just yesterday (didn't have one previously).
On Prey Help Center someone with status responce 422 connection error got following answer: "Now, the reason why Prey is having trouble registering your device is because it’s trying to call a function that, for some reason, hasn’t been loaded (full_hardware_params). "
Unfortunately I can't do anything with that answer
EDIT: I'll try it out on another Sailfish device. Let's see what happens there.
EDIT2: Ok, tested it with another Sailfish device (fresh install) and got the same problem.
Last edited by caprico; 2014-05-28 at 18:17.
I wonder if it has to do something with my new Prey account. I set it up just yesterday (didn't have one previously).
On Prey Help Center someone with status responce 422 connection error got following answer: "Now, the reason why Prey is having trouble registering your device is because it’s trying to call a function that, for some reason, hasn’t been loaded (full_hardware_params). "
Unfortunately I can't do anything with that answer
EDIT: I'll try it out on another Sailfish device. Let's see what happens there.
EDIT2: Ok, tested it with another Sailfish device (fresh install) and got the same problem.
Last edited by caprico; 2014-05-28 at 18:17.
|
|
2014-05-28
, 19:14
|
|
Posts: 108 |
Thanked: 417 times |
Joined on Oct 2013
|
#68
|
Thanks again for your answer. The problem is that no new device (Jolla) was added to my profile. So I can't change any configurations. I set up a computer with the official client - that worked well.
The option "Add device" just sends me to a link where I can download various clients (I was hoping to see an option there to manually set up a device).
So it indeed seems that due to some server changes, new Prey users can't register a Sailfish device anymore.
Last edited by caprico; 2014-05-28 at 19:16.
The option "Add device" just sends me to a link where I can download various clients (I was hoping to see an option there to manually set up a device).
So it indeed seems that due to some server changes, new Prey users can't register a Sailfish device anymore.
Last edited by caprico; 2014-05-28 at 19:16.
|
|
2014-05-28
, 19:53
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#69
|
Originally Posted by caprico
perhaps its worth a try to uninstall latest version (prey-0.6.3-1) and then try by install the previous version (prey-0.6.2-6)
Thanks again for your answer. The problem is that no new device (Jolla) was added to my profile. So I can't change any configurations. I set up a computer with the official client - that worked well.
The option "Add device" just sends me to a link where I can download various clients (I was hoping to see an option there to manually set up a device).
So it indeed seems that due to some server changes, new Prey users can't register a Sailfish device anymore.
Direct link to rpm package (install in terminal)
https://openrepos.net/sites/default/...-6.armv7hl.rpm
| The Following User Says Thank You to For This Useful Post: | ||
|
|
2014-05-28
, 20:21
|
|
Posts: 108 |
Thanked: 417 times |
Joined on Oct 2013
|
#70
|
Originally Posted by nieldk
Good one
perhaps its worth a try to uninstall latest version (prey-0.6.3-1) and then try by install the previous version (prey-0.6.2-6)
Direct link to rpm package (install in terminal)
https://openrepos.net/sites/default/...-6.armv7hl.rpm
That worked! Device is registered and shows up as Jolla on Prey profile. "No laptop-detect" still appears, but doesn't seem to influence the registration.Code:
>> Registering device under account! -- Gathering system and hardware information... which: no laptop-detect in (/bin:/sbin:/usr/bin:/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/nemo/bin:/usr/share/prey/platform/linux/bin) -- Sending request to Control Panel... -- Got response status 201. -- Device succesfully registered! Applying configuration... -- All set. Assigned key is xxxxxx. -- Checking URL... == Verifying status... ...
Last edited by caprico; 2014-05-28 at 20:25.
| The Following User Says Thank You to caprico For This Useful Post: | ||
-I verified the API key
Last edited by caprico; 2014-05-28 at 11:01.