Increasing the verbosity doesn't add much to the log.

I notice that these lines get printed whenever I touch the screen, use the keyboard or press the volume keys. The camera button or the lens door do not trigger these messages.

Searching the web for these messages doesn't give much (expect pointing to this forum message, that's quick indexing Google!)

I'm still open to suggestions!

What is the content of the file /etc/X11/xorg.conf ?

My xorg is not so verbose.

What is the output from ls -l /usr/bin/Xorg

You could remove the file and create a symlink from /tmp/Xorg.0.log to /home/user/MyDocs/Xorg.0.log, so the file will be on the 30GB filesystem. You will need to do this at every boot.

It's on the 1st page on this thread, but I've also attached it to this post.




Yeah, I can do that (modifying the /etc/event.d/xomap and /etc/event.replace.d/xomap files is better I would think).

What I wonders is "why am I getting this" and it seems that I'm the only one...

How does you Xorg process got started? On my phone I have the following (note that I've increased the "logverbose 1" to 3 myself).

You seem to have the same Xorg binary that I have.

I asked about the config file, not the log file.

My Xorg runs with -logverbose 1, Did you get those messages before increasing 1 to 3?

Oh, sorry Matan, I read too quickly.

Yes, I had these messages before updating the verbosity. Actually, increasing the verbosity didn't change the content in any way.

I have a big problem right now: I edited /etc/event.d/xomap to put the log file directly into the MyDocs folder, but now my phone doesn't boot anymore... I'm trying to see if I can restore these files without reflashing the device.

I'm in the NITDroid OS right now, looking to find an x-term equivalent or even better a ssh daemon for me to go in the phone and try to reset these files to their original content...

wish me luck!

oh well, I did not manage to get to the point where I can edit the root fs partition. It seems to be a pretty advanced thing to do and it looks like my embedded-fu isn't up to the right level yet.

So I reverted to the only logical solution: reflash.

The good thing is: after the reflash, I don't have these weird EV_KEY lines anymore.

This isn't the level of understanding I wanted to reach (either understanding the cause of these log messages or understanding how to edit the root fs without booting into mamo) but at least, I didn't spend to much time without a phone

In case you're still seeking reassurance, I'm having this problem too. I assume it's related to me using my bluetooth keyboard, since it's only since I started using it that I saw the problem. In fact, I usually notice I've run out of space in /tmp because the keyboard will connect but I can't type on it. I'd be interested in a proper solution, I don't really want to reflash at this point, it's easier just to echo to /tmp/Xorg.0.log every so often.

Yesterday I noticed that big latin P was corrupted in any app title. So i switched it off today at 12:00 approximately, but when I turned it on I just fell asleep and it was laying waiting me to enter unlock code until 18:00 (long night with my friend's broken FreeBSD server, if you have proftpd 1.3.3c, upgrade it immediately to 1.3.3d+!). And now I have these
... you wouldn't believe where. In microb history.
And rebooting didn't help.

Any news about this? I have the same problem.
These don't seem to be error messages, it's just logging all keyboards and mouse events. But why?
Could not find any documentation about this.

for me it disappeared after second or third reboot.
However I didn't have any problems with Xorg.0.log, it was showing only in MicroB