|View Poll Results: Should Paranoid Android change to an AOSP base.|
|Yes, AOSP base with a few features from cm||279||63.41%|
|NO, stick with a cm base(current base)||161||36.59%|
|Voters: 440. You may not vote on this poll|
I discover this bug for Paranoid Android 4.2.1. Here is how I discover the bug:
I use "VMLite VNC Server" to remote control my Nexus 7 sometimes. It works great for Paranoid Android ROM 4.1. However, when i updated to 4.2.1, I am unable to use the app anymore. When I connect to the Nexus 7, the connection is made, but what shown on my VNC viewer client is a quadruple screen of recovery boot. It is not a recovery boot problem cause I tried both TWRP and CWM and it is the same for both. I have attached pictures in the post.
Next, I decide to switch VNC server to "droid VNC server". The problem still persists. Then, I switch to a different VNC viewer client and it is still the same. I switch to an older version of 4.2.1 ROM and the bug still presents.
I have a Galaxy S3 running 4.2.1 ROM from Cyanogen Mod and there is no problem at all running VNC server on that device. This is not a serious bug but it is quite annoying not able to run VNC server like I use to do. Please fix this bug in the next version if you can.
PS: not sure if this is where you post bug report. If not, you can direct me to the correct place and I will post it.
|best rom ever|
|Thread Tools||Search this Thread|