Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to initialize Pebble Time Steel #80

Open
Astaoth opened this issue Aug 21, 2019 · 9 comments
Open

Unable to initialize Pebble Time Steel #80

Astaoth opened this issue Aug 21, 2019 · 9 comments

Comments

@Astaoth
Copy link

Astaoth commented Aug 21, 2019

Hi !
Last year I had some problem and my PTS asked me to initialize it. I tried with rockpool (a version with rebble) without luck. I have just made a new try, but nothing happens.

Is the PTS initialization working ?

Thanks !

@abranson
Copy link
Owner

Mine managed to get through it a few weeks ago, but it could be that the firmware isn't available anymore and I had it cached? I don't know the URL to check for Rebble firmware yet sorry.

@CosmicDuck
Copy link

I've the same issue with a "new" Pebble 301PK.
Although I use an newer one which connects fine the problem is that RockPool identify the new Pebble and want to initialise it, but I press the initialise button but nothing starts.
On the new Pebble my BT Phone Name is shown an a Hand with Fingers on a Phone is shown with pebble.com/app.

@Astaoth
Copy link
Author

Astaoth commented Sep 28, 2019

Here are some available firmwares : https://github.com/Freeyourgadget/Gadgetbridge/wiki/Pebble-Firmware-updates . Maybe when the Pebble needs to be initialized we can download them from there ? How can I put a firmware in the cache ?

@rubdos
Copy link
Contributor

rubdos commented Nov 14, 2019

Seems like the latest.json hosting S3 bucket doesn't exist any more. Maybe we should work with Rebble to see whether they can host the firmware files? I just worked around it by uploading the files mentioned by @Astaoth on my own server and compiling rockpool with that address instead.

@Astaoth
Copy link
Author

Astaoth commented Nov 14, 2019

@rubdos Do you know the url on which rockpool looks for the firmware ? Maybe I can try something on a homeserver and the /etc/hosts file.

@rubdos
Copy link
Contributor

rubdos commented Nov 15, 2019

It does HTTPS, so you'll have to fake a lot of things. If you want a quick fix for you right now, I can hand you an RPM that redirects to my server, and I can host the firmware for you for now.

It's on line 144 of firmwaredownloader.cpp: QString url("https://pebblefw.s3.amazonaws.com/pebble/%1/%2/latest.json");.

@cyberlyra
Copy link

I'm having the same problem again :( Now that the Rebble Alliance has taken over managing Pebble firmware, is it possible to point the firmwaredownloader.cpp to their services? And if so, how do I do it? (I assume via Developer Connection...)

@abranson
Copy link
Owner

abranson commented May 2, 2022

It's not configurable, so you'd have to build it with new URLs etc. Can you point me to any docs for that? It would be nice to get it fetching firmwares from Rebble finally. I still can't believe we're all still using our Pebbles, and they're all still going!

@rubdos
Copy link
Contributor

rubdos commented May 2, 2022

Can we ping the Rebble people, maybe via Discord, to ask these things? Would be nice if all URLs pointed to Rebble at some point.

My PT will soon need a new battery, but other than that I can see me using it a bit longer :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants