| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
3 hours ago
» Replies: 5
» Views: 525
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: KelsonV
Yesterday, 02:20 PM
» Replies: 0
» Views: 46
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 104
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 456
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,102
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 56
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 77
|
Second screen mirroring
Forum: General
Last Post: andrekyler
11-17-2025, 01:06 AM
» Replies: 3
» Views: 1,895
|
7 inch touch panel patche...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: mkjmkj
11-17-2025, 12:57 AM
» Replies: 0
» Views: 84
|
Pine64 LTS v1.2 not turni...
Forum: P64-LTS / SOPINE Hardware, Accessories and POT
Last Post: in_sympathy
11-16-2025, 08:09 PM
» Replies: 0
» Views: 62
|
|
|
DOA pin64 2GB - what now? |
|
Posted by: bongo - 05-03-2016, 11:23 PM - Forum: Getting Started
- Replies (8)
|
 |
i got my 2gb pine64 yesterday.
- i first tried to install android (latest rooted version) but all i got was the red led. btw: i created the flashcard using the "usb image tool", as phoenix did not accept this image.
- next try i gave to the android phoenix card image, which i burnt using the phoenix tool. creating the flashcard succeeded on the 2nd try. again the same effect. only the red led.
- 3rd try i was using debian jessie. again the same. nothing but the red led ;-(
i did this test using a kingston 16gb micro sd, which was tested to be fine and has successfully been used with a raspi before.
i tried two power supplies which both are rated 2A and have been used with a raspi.
all i have connected to the pine64 is the hdmi monitor.
i measured the current, drawn from the power supply. after turning on, it's at about 400mA, going down to in between 250mA and 300mA after some time.
what else can i do?
looks like i got a dead one ;-(
|
|
|
|
| OctoPrint on Pine64 |
|
Posted by: Spaz - 05-03-2016, 09:10 PM - Forum: Linux on Pine A64(+)
- Replies (3)
|
|
I got my Pine64 setup using the latest Debian and setup OctoPrint. While the software appears to be working the serial USB (/dev/ttyACM0) doesn't seem to exist so I can't connect to my printer. Has anyone gotten OctoPrint to work using the distros Pine64 has provided?
|
|
|
|
| Slow Downloads - can I help? |
|
Posted by: rez410 - 05-03-2016, 07:48 PM - Forum: General Discussion on PINE A64(+)
- Replies (15)
|
|
Hey everyone,
While downloading some of the images, I noticed the bandwidth is pretty limited. Would it be ok if I hosted the same exact files on a site of my own?
I would use the exact same files and list the same hash. Just trying to offload some of the load and offer fast downloads.
|
|
|
|
| GPS |
|
Posted by: queonda - 05-03-2016, 05:31 PM - Forum: Accessories
- Replies (12)
|
|
Anyone have success on a GPS module to work on the Android image for the Pine64?
|
|
|
|
| Issue with Widgets on Android |
|
Posted by: fsa317 - 05-03-2016, 04:29 PM - Forum: Android on Pine A64(+)
- No Replies
|
|
Most widgets, when I try to place them on my home screens hang and fail. I found this in the log (similar messages for lots of widgets):
This is consistent whenever a widget has a "configuration" screen after placing it. Widgets without a configuration screen seem to work OK. One example widget is the MSN Money app, when you try to add the stock widget after selecting the stock symbol it crashes.
Code: 05-03 15:20:07.758: E/AndroidRuntime(18457): Process: com.android.launcher3, PID: 18457
05-03 15:20:07.758: E/AndroidRuntime(18457): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.android.launcher3.CellLayout.findCellForSpan(int[], int, int)' on a null object reference
05-03 15:20:07.758: E/AndroidRuntime(18457): at com.android.launcher3.Launcher.completeAddAppWidget(Launcher.java:1623)
05-03 15:20:07.758: E/AndroidRuntime(18457): at com.android.launcher3.Launcher.completeAdd(Launcher.java:727)
05-03 15:20:07.758: E/AndroidRuntime(18457): at com.android.launcher3.Launcher.finishBindingItems(Launcher.java:4516)
05-03 15:20:07.758: E/AndroidRuntime(18457): at com.android.launcher3.LauncherModel$LoaderTask$10.run(LauncherModel.java:2764)
05-03 15:20:07.758: E/AndroidRuntime(18457): at com.android.launcher3.DeferredHandler$Impl.handleMessage(DeferredHandler.java:51)
05-03 15:20:07.758: E/AndroidRuntime(18457): at android.os.Handler.dispatchMessage(Handler.java:102)
05-03 15:20:07.758: E/AndroidRuntime(18457): at android.os.Looper.loop(Looper.java:135)
05-03 15:20:07.758: E/AndroidRuntime(18457): at android.app.ActivityThread.main(ActivityThread.java:5254)
05-03 15:20:07.758: E/AndroidRuntime(18457): at java.lang.reflect.Method.invoke(Native Method)
05-03 15:20:07.758: E/AndroidRuntime(18457): at java.lang.reflect.Method.invoke(Method.java:372)
05-03 15:20:07.758: E/AndroidRuntime(18457): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:920)
05-03 15:20:07.758: E/AndroidRuntime(18457): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:715)
|
|
|
|
| Pine64 will not turn on |
|
Posted by: destroyer - 05-03-2016, 02:54 PM - Forum: Getting Started
- Replies (5)
|
|
I followed the tutorial on the wiki to create a boot able sd-card with Phoenix card. Put the card in the board and then plugged in a 1.5 amp power supply and nothing. No screen output or no led on the board.
|
|
|
|
| Advice on creating micro SD (Android) |
|
Posted by: phoenixcrap - 05-03-2016, 12:13 PM - Forum: Android on Pine A64(+)
- Replies (2)
|
|
In hindsight, I suspect my username reveals my frustration. Received my 1Gb board today and hurried off to download, via the Wiki, the latest Android version, WinRar and Phoenix. I unpacked the Android Image into it's own folder and likewise Phoenix. Opened the Phoenix application and went off to select my Android image file 'android-ver5.1.1-20160428-pine64-8GB' (7,569,408 KB). I immediately got the Phoenix error message "Script not found. Please use new image version".
I've tried deleting the downloaded Android file and re-downloaded (incase it had become corrupt in download) and unpacked, this time using Winzip. Same result when I try to select that image file with Phoenix ( "Script not found. Please use new image version")
I've tried downloading different Android versions (all via Wiki) with the same results.
Any idea what I might be doing wrong here people?
|
|
|
|
| Single Thread for Problem Status's |
|
Posted by: gbestwick - 05-03-2016, 12:13 PM - Forum: General Discussion on PINE A64(+)
- Replies (2)
|
|
Hello there!
I've been piddling with my 2G board for a little while and, of course, had the usual set of issues that happen. I'm not even slightly annoyed by this as I know what I was getting myself into backing a project like this! On that note, I'd like to thank the devs and the team for all of their hard work and for putting up with the angry people who need a time out and a cookie.
But, one thing I think people would find really helpful is a single location summary of known bugs, and their workarounds. Maybe there could be sticky thread places somewhere, and categorize them by general group, and then put the higher priority/greater group affected first.
A good example is I've been having the "purple screen" issue caused by using an HDMI->DVI adapter. When it first happened, it would have been wonderful to know that that was a problem.
Anyhoo, just my two cents.
|
|
|
|
|
