04-29-2016, 04:25 PM
I received my 2GB board yesterday. Today I purchased a 64GB Class 10 Micro SD XC card from Walmart. It tested fine. I then attempted to follow the PhoenixCard instructions to burn the Android 5.1.1 Image Release 20160303. Phoenix gave me an error each time identified the source .img file saying, "Script not found! Please use new version image!". I attempted to re-download and re-unpack that file multiple times. Receiving the same error message, I then tried the older Android Image Release 20160216.
This one successfully burned to the SD card on the third attempt.
On the first power up (using a potentially lower powered adapter) I got to the splash screen, but that was as far as it went--after a long wait time, it powered off.
I hooked up the Pine64 power adapter that I purchased with the board, and tried again. This time it went past the splash screen and froze on the Pine64 logo screen. After about a half hour, I turned it off and on again. This time it went to a screen that said it was updating my contacts. I had a circle of death going round and round, but it never completed this process before it rebooted on its own.
On the reboot, it never got past the Pine64 logo.
I restarted it and it went a bit further. It seemed to have booted successfully, but as soon as I selected (using the purchased mouse/remote accessory) settings/wifi, it restarted again. I noticed that the system was very slow to respond to my inputs.
It rebooted into the operating system, and my remote isn't responding 100% of the time. The cursor moves around the screen, but I cannot select anything. I somehow activated Settings/bluetooth (currently in the off position), but I cannot get out of that screen. Android sent me back to the home page--or it rebooted again.
I'm pretty patient, but I have spent a day on this and have read more posts and problems than I ever imagined I'd have to.
Can anyone confirm that the Pine64 supplied power adapter is sufficient? It says it is 5V 2A.
The response time and the time it takes to navigate from page to page is ridiculously slow (like going between settings main page into Wifi). Settings has taken so long on several occasions that Android has offered to close it for me. If I choose to wait it seems to finally get there on its own. Okay, I thought I was a patient man...
Any ideas why it is so slow to respond? Again, the cursor moves effortlessly around the screen.
This one successfully burned to the SD card on the third attempt.
On the first power up (using a potentially lower powered adapter) I got to the splash screen, but that was as far as it went--after a long wait time, it powered off.
I hooked up the Pine64 power adapter that I purchased with the board, and tried again. This time it went past the splash screen and froze on the Pine64 logo screen. After about a half hour, I turned it off and on again. This time it went to a screen that said it was updating my contacts. I had a circle of death going round and round, but it never completed this process before it rebooted on its own.
On the reboot, it never got past the Pine64 logo.
I restarted it and it went a bit further. It seemed to have booted successfully, but as soon as I selected (using the purchased mouse/remote accessory) settings/wifi, it restarted again. I noticed that the system was very slow to respond to my inputs.
It rebooted into the operating system, and my remote isn't responding 100% of the time. The cursor moves around the screen, but I cannot select anything. I somehow activated Settings/bluetooth (currently in the off position), but I cannot get out of that screen. Android sent me back to the home page--or it rebooted again.
I'm pretty patient, but I have spent a day on this and have read more posts and problems than I ever imagined I'd have to.
Can anyone confirm that the Pine64 supplied power adapter is sufficient? It says it is 5V 2A.
The response time and the time it takes to navigate from page to page is ridiculously slow (like going between settings main page into Wifi). Settings has taken so long on several occasions that Android has offered to close it for me. If I choose to wait it seems to finally get there on its own. Okay, I thought I was a patient man...
Any ideas why it is so slow to respond? Again, the cursor moves effortlessly around the screen.
