| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,671
» Latest member: Maryam6778
» Forum threads: 16,246
» Forum posts: 117,151
Full Statistics
|
|
|
| assistantpine, a working idea for a distro |
|
Posted by: tohipfortheroom - 01-20-2017, 09:27 AM - Forum: General Discussion on PINE A64(+)
- Replies (1)
|
 |
AssistantPine Developement
I have been working roughly 80 hours a week, so i have had a lack of time to focus on bigger projects, aka TV64 and or ChromiumOS, but i couldn't sleep last night, probably to much coffee. but i had a good idea of something id like work with the pine community on, due to time issues on my part i will need some help or assistance for this, and it is in the very basic, i have an idea, and a very basic blueprint on a plan of action. here is the idea. In the last 4 or 5 years, the virtual assistant has grown to be very powerful, amazon,google, apple and windows all have there's. Where is the Pure Linux one? and even better answer, where is the pine one? That is what i want to try to get started, my base idea, is to work off some of the work that's all ready been done in the Linux world. SemiCode OS, is a development based Ubuntu distribution, they have done some great work with what they call Sarah. you can check it out here https://github.com/semicode-ltd/sarah and of course with amazon releasing the source code of Alexa for Linux there is promise for this idea.
Mission Statement for this Project
I want to build a small base distribution for the pine64, that then could act as a hub or a standalone unit, loaded with the AI, then this main unit could then be used to manage any other units on the same network, basically a home-kit type idea. So step one would be to strip Ubuntu down and build around with Sarah, then work with code for touch screen's etc.I will have time this Sunday to work on this idea, and some more outlining on how this can work, right now I am curious, if anyone else thinks this would be a worth idea. Also any idea's that would be worthwhile to look into surrounding this idea would be awesome.
Send an Email for a invite to the slack team
tohipfortheroom@gmail.com
I have learned that slack is the best way for developers to get work done, if your interested pm for more information on help or if your really interested in helping. shoot me a email and i'll add you to the slack team
Follow the progress at Trello
Update 1/23/2017
After reaching out to SemiCode OS I have been contacted by Mohamed Saif Eldeen, the CEO and founder of SemiCode OS, We are going to be working together on some features of Sarah. A full port of SemiCode OS may be in work as well.
|
|
|
|
| Ubuntu USB Mic |
|
Posted by: matrix452 - 01-18-2017, 09:27 PM - Forum: Ubuntu
- No Replies
|
 |
Hey guys,
I'm trying to add a USB mic to my Linux install but it appears that it is not being detected. I am connecting via VNC and SSH. Any thoughts on this?
Here is what the output of cat /proc/asound/cards shows:
Code: 0 [DeviceEcho058 ]: USB-Audio - USB PnP Device(Echo-058)
USB PnP Device(Echo-058) at usb-sunxi-ohci-1, full speed
1 [sndhdmi ]: sndhdmi - sndhdmi
sndhdmi
|
|
|
|
| Bluetooth audio sink |
|
Posted by: jszmidt - 01-16-2017, 12:44 PM - Forum: Linux on Pine A64(+)
- Replies (1)
|
|
Hi all,
I'd like to use the PINE64 as a Bluetooth audio sink, but unfortunately it appears that the hardware doesn't support this option. Am I missing something? Is it a limitation of the chip or of the driver?
Here's the uname:
Code: root@pine64:~# uname -a
Linux pine64 3.10.102-2-pine64-longsleep #66 SMP PREEMPT Sat Jul 16 10:53:13 CEST 2016 aarch64 GNU/Linux
root@pine64:~#
Here's the output of bluetoothctl:
Code: [bluetooth]# show
Controller 34:C3:D2:BF:85:79
Name: pine64
Alias: pine64
Class: 0x000420
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d052B
Discovering: no
[bluetooth]#
For comparison, here's what it looks like on my laptop (Arch):
Code: [bluetooth]# show
Controller 60:57:18:C2:5A:05
Name: milosz
Alias: milosz
Class: 0x1c010c
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d052B
Discovering: no
[bluetooth]#
Cheers!
j.
|
|
|
|
| Power-On button does not always work |
|
Posted by: xalius - 01-16-2017, 05:45 AM - Forum: Linux on Pine A64(+)
- Replies (2)
|
 |
I was investigating why the power button does not always work to turn the Pine back on (shuts down after 5 seconds) after a shutdown with no power cycle.
It seems to work reliably with a battery connected though. After comparing the boot logs I think I found the issue, but need some input on how to fix this,
probably in the ATF or by making sure the AXP803 is in the right state after a shutdown with power-off.
Boot log differences: https://www.diffchecker.com/ZVbSo0ap (Left column is cold boot from power cycle, Right column is button triggered boot after a previous shutdown)
1.) On a cold boot the AXP detects correctly that there is no battery ( see lines 16, 38 in the diff )
no battery, limit to dc vs. normal dc exist, limit to dc
2.) A bit later in the startup this leads to (see line 117ff)
no battery exist vs. PowerBus = 2(0: not exist 1:vBus 2:acBus 3:vBus&acBus) Battery Voltage=0, Ratio=0 key trigger battery low power and vol with dc or ac, should charge longer
3.) And in the right case, the system gets switched off (see line 129)
[ 5.742]power off
So what basically happens is, that on a cold boot the AXP properly detects that there is no battery and so no issues with the battery voltage... after a shutdown without a power-cycle the AXP seems to come back in a state where it has a battery detected (even if there is none) and the low battery voltage / charge level triggers a power-off....
|
|
|
|
|
![[Image: Amadeo_Brussels.jpg]](https://s24.postimg.org/dj2ji42wl/Amadeo_Brussels.jpg)