after some more testing and examination of the hardware stuff, i'm in doubt that this problem is hardware related.
So i started to think of some software related issues.
I know that bootcode and Android filesystem should be aware of bad blocks in NAND memory.
But anyway here's the history of the device (so far i know it):
- It came to me with stock bootloader and firmware 1.5
- A stock update was made to firmware 1.6
- I did a downgrade to RC7 using a goldcard
- Rooted the device using telnet
- Installed cm-recovery-1.4
- Followed the steps from cyanogen's wiki to move to v18.104.22.168
- Also did a radio update to 22.214.171.124i
- Installed Hard-SPL as well
Everthing went fine, also no problems during registering to a google account.
I am able to boot into HSPL and the cm recobery is also intact.
It's very strange that the trackball weirdness did not change during all these up/downgrades.
I also got some issues with the power button.
Sometimes the device can not be set to sleep and immediately comes back into active state
Apart from that the device behaves quite normal...
What the hell is wrong with this device?
Could there still be some corrupt areas in NAND caused by bad blocks even after reflashing the system?
Any advice would be welcome!