Many users have reported that Webtop can be loaded but the track pad is unresponsive. After some remote investigation sessions and user interactions, it is believed that this is an official timing bug that can be temporary fixed by clearing the dalvik cache of some apps(eg. DockService and PortalApp) and then reboot to increase the boot time of Android so as to allow other (unknown) process to run earlier than certain Android related services to allow the track pad from working.
A better fix would be to find out the exact racing services and then re-run the intended services manually. This will need Photon owner to provide remote investigation session and my time. :) Email me if you wish.
On some Razr, its evbridge will fall into a dead loop at early stage. One instance was reported by Miguel Ortiz. He provide a remote investigation session so that I have chance to test running the evbridge from WT-2.0.0-82 and WT-2.0.0-113. Both could run normally on his Razr Maxx. His Webtop version is WT-2.0.0-139.
Another instance of this is reported by Lorenzo Kellogg. He has a XT912 with WT-2.0.0-139 from Verizon. It is interesting that the evbridge(113) has the same behavior on it. By setting the TZ variable(to GMT, let say) that skipped the /etc/localtime, evbridge(both 113 and 139) can be started without any problem. By analyzing the difference between a hanging and non-hanging strace log, /etc/localtime(or /usr/share/zoneinfo/$TZ) is found to be the culprit.
I'm able to reproduce the problem on a Razr that hasn't this problem by using the /etc/localtime extracted from Lorenzo's phone. The steps to reproduce:
It is found that the /etc/localtime found from Lorenzo's phone is exactly the same as /usr/share/zoneinfo/US/Michigan.
Okay, to summarize the stuffs of evbridge dead loop:
The timezone file is Europe/Brussels. It is reported by Viktor Horvat. Webtop version WT-2.0.0-113. What's up? ?_?