"binder: 139:139 transaction failed 29189, size 0-0"

Hey guys. Im not too code savy. Slowly tryung to get into it, but i have no idea what this hang up means. The system seemed to work fine for months. I downloaded a new launcher, and a couple days later, on load, it scrawls that over and over. Any ideas? Id greatly appretiate any feedback, thanks.

Comments

  • Hi Aperturelab,
    could you please elucidate the problem more detailed? When exactly does the system hangs up? Please add system logs, so we can analyze and understand the issue precisely.

  • Where could i find the system logs? I opened the sd on my computer and cant find a folder for that
  • There's a topic in the help kb:
    https://help.emteria.com/kb/emteria-os-debugging-and-bugreports

    In the past in /data/misc/logd/ I saw some system-#.txt and logcat.00# files but I don't know how those relate to the Submit Bugreport above.

  • on that topic, it mentions Settings > Emteria > Submit bug report. I'm assuming that's referring to within Emteria's settings app. Unfortunately, my OS wont load past the initial loading screen of white text on black background. I also cannot find data/misc/logd.

  • We have removed /data/misc/logs as they can slowdown the IO access to the sdcard. Usually you don't want the system to continuously write system logs and wear down the storage.

    @Aperturelab, maybe your sdcard is broken? Its difficult to tell without hardware access. The Binder error you have mentioned in the title can be caused by many different problems including bad sectors on the data storage.

  • Ive formated and re-wrote thr os for this sd card numerous times. Perhaps its been worked too much, and has some residual damage from the formating. Ill get a new sd card, add and change things to my preference and see if the problem re-occers. Thank you all for your time and suggestions.
    Shall i report back to this post if problem persists?

  • Yes, sure.

  • ive used my Pi for numerous months and havent had issues. it seems there was a conflict between how the OS booted, and a specific application that changed the launcher and User Interface. If i remember correctly, it was called ADW Launcher. Im currently using Nova Launcher, running smooth.

  • Awesome, thanks for reporting!

  • edited January 23

    Hi @kalkov, my SatNav Emteria device wanted to be updated to version 0.6.1 (from 0.6.0) yesterday. I agreed because I would like to install microG. All went well, update was downloaded, system rebooted to Recovery mode where downloaded files were applied. But after second reboot updated system got jammed in black "console" screen with couple of messages "binder: x:y transaction failed z, size a-b".

    I had to format SD and reinstall Emteria. Sure, it could be only coincidence, but I had Nova launcher installed (because of possibility to lock desktop, night mode, etc.) before the updating. @Aperturelab wrote about similar problem related to usage of "third-party" launcher, so it's possible that usage of another launchers could cause update problems.

  • @Martin thanks for the information. I will try to find some spare time and install Nova Launcher for a test.

  • I use Nova and haven't had any issues with it.

  • Thanks for message. So my problems probably caused any particle from space.

  • Hopefully its one-off error.

  • Unfortunately, I am still experiencing this problem. I tried to make backup of SD card by Win32 Disk Imager and restore it to another SD card (for test). I tried it couple of times but booting of copy of Emteria always ended with this error.

  • Guess the only solution is to start over fresh.

  • Could you please provide more details for reproducing: install emteria.OS, create a backup, restore a backup?

  • I used Win32 disk Imager to create the backup of SD card from my SatNav device (Emteria on RPi 3B+). After it, just for test, I used Win32 Disk Imager to restore previously created backup image to another SD and boot from it. I tried couple of times but every attempt for boot of copy ended by this misterious error - binder transaction failed.

  • Thanks, I'll check this next week.

Sign In or Register to comment.