MobileRead Forums - View Single Post

Tulkas · 11-15-2007, 05:19 AM

Ahhhh my Gen3 has gone haywire!!!!

It was working fine until I decided to plug it in for (1) recharge & (2) to see whether downloaded Mobipocket 6.1 would recognise it as a device. (2) was still a no. Anyway safely disconnected device but screen, which had until then been correctly showing the cable connected screen, then went weird ~ bottom half remained on cable symbol, the top went blank.

I've tried switching on/off, resetting and even as far as unplugging the battery but nothing changes it. Bottom half is fine. Top half you can sometimes see ghostly/faint image of what SHOULD be there and on page changes you can see a negative version of page as screen reflashes but thats it

I've emailed Bookeen but wonder if anyone else has experienced this? My initial thought was that screen had failed but brief 'negative' reflash screen would suggest perhaps not. Or could it be a system file has been corrupted somehow?

11-15-2007, 05:19 AM	#1
Tulkas Enthusiast Posts: 44 Karma: 10 Join Date: Jun 2007 Location: London, UK Device: iLiad, CyBook Gen3, iPod Touch, PB 360	Top half of screen has gone blank Ahhhh my Gen3 has gone haywire!!!! It was working fine until I decided to plug it in for (1) recharge & (2) to see whether downloaded Mobipocket 6.1 would recognise it as a device. (2) was still a no. Anyway safely disconnected device but screen, which had until then been correctly showing the cable connected screen, then went weird ~ bottom half remained on cable symbol, the top went blank. I've tried switching on/off, resetting and even as far as unplugging the battery but nothing changes it. Bottom half is fine. Top half you can sometimes see ghostly/faint image of what SHOULD be there and on page changes you can see a negative version of page as screen reflashes but thats it I've emailed Bookeen but wonder if anyone else has experienced this? My initial thought was that screen had failed but brief 'negative' reflash screen would suggest perhaps not. Or could it be a system file has been corrupted somehow?