-
Notifications
You must be signed in to change notification settings - Fork 110
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
PerCodec:DecodeError:Requested Bits to decode 3, Remaining bits 1 #139
Comments
yes. Installed the latest (as of yesterday). I just took it out for an hour or so and got:
... 141 repetitions of "BufferTooShort" skipped ...
This is on an Orbic with a SIM, but no active account on Verizon. USB and WiFi web interfaces both accessible. |
on the bright side, this error is fairly benign -- it just means our telcom parser is failing to parse a certain type of message. we should figure out which type and fix it, though! |
Same here. Inactive SIM. Orbic UI shows "NO SERVICE". Anything we can do to provide info to help debug? |
I believe it only occurs when the web page is displayed. I see it over USB for a certainty, occurring every minute or two. Disconnecting and walking around with the Orbic in my pocket for over two hours, there were no errors. They started up when I reconnected to USB. |
This is a benign error you can ignore. |
oops apparently @wgreenberg plans to fix it eventually! |
I'm curious if anyone has seen these errors, and am trying to figure out what they mean. I've gotten quite a few of them, all the same message:
The timestamp doesn't line up to an entry in the pcap. I'm assuming this means some error on-device when either a hardware error occurs or some kind of decoding error. Any idea how to troubleshoot?
Installed RayHunter from tag v0.2.5 to an Orbic. Install seemed fine and can access the web UI.
Thanks,
Char
The text was updated successfully, but these errors were encountered: