| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
No telephone call audio, ...
Forum: PinePhone Pro Hardware
Last Post: biketool
1 hour ago
» Replies: 0
» Views: 17
|
Password reset via u-boot...
Forum: PineNote Software
Last Post: oliviamillera
10 hours ago
» Replies: 7
» Views: 3,312
|
Selling my Pinephone Pro ...
Forum: General Discussion on PinePhone
Last Post: Kevin Kofler
Yesterday, 10:25 AM
» Replies: 2
» Views: 2,807
|
Window Maker Live for Pin...
Forum: Linux on Pinebook Pro
Last Post: vajak
Yesterday, 07:14 AM
» Replies: 0
» Views: 46
|
sd card problems
Forum: PinePhone Accessories
Last Post: ottahe
Yesterday, 06:42 AM
» Replies: 2
» Views: 91
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: mdk
Yesterday, 02:57 AM
» Replies: 6
» Views: 786
|
Battery connector dead
Forum: PinePhone Hardware
Last Post: mdk
Yesterday, 02:54 AM
» Replies: 4
» Views: 2,475
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: ArmbianForSBCs
Yesterday, 02:42 AM
» Replies: 1
» Views: 209
|
Armbian has been released...
Forum: News
Last Post: ArmbianForSBCs
Yesterday, 02:41 AM
» Replies: 20
» Views: 31,529
|
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-30-2025, 08:07 AM
» Replies: 3
» Views: 218
|
|
|
| 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.
|
|
|
|
|