Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

M

mpnegro

@mpnegro

1

Reputation

222

Profile views

Posts

Followers

Following

Joined

Last Online

Best posts made by mpnegro

RE: Ubuntu Phone Bq 4.5 don't detect SIM card after flash with ubports!

Hi All,
After reflashing again, clean the SIM card, change and re-change the SIM slot, it finally detected the SIM card. Probably something is damage, or in the SIm or in the slot. Thks for the help

posted in Support
M
mpnegro

Latest posts made by mpnegro

RE: One Plus One and Halium 7 or 9

Humm... Thks for the info
Regards
Miguel Pires

posted in Off topic
M
mpnegro
One Plus One and Halium 7 or 9

Hi
Will OPO be ported to use Halim 7 or 9 to use a new kernel?
Regards
Miguel

posted in Off topic
M
mpnegro
RE: Traing to install in OnePlus one

Soved, by installing android and phblet tools.

posted in Support
M
mpnegro

Traing to install in OnePlus one

Hi,
I'm traing to install UT in one OnePlus One A0001.
I'm runing the app with sudo to see whats wrong with the installer, and I'm receiving this in terminal:
sudo ubports-installer
debug: Using native platform tools!
debug: Running platform tool exec cmd adb kill-server
debug:
debug: Running platform tool exec cmd adb -P 5038 kill-server
debug:
debug: Running platform tool exec asar cmd [object Object] -P 5038 start-server
debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device '(null)' not found

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug:
debug: adb shell: getprop ro.product.device
debug: Running platform tool exec cmd adb -P 5038 shell getprop ro.product.device
debug:
debug: getprop: A0001
debug: adb shell: cat /etc/system-image/channel.ini
debug: Running platform tool exec cmd adb -P 5038 shell cat /etc/system-image/channel.ini
debug:
debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug:
debug: reboot to bootloader
debug: Running platform tool exec cmd adb -P 5038 reboot bootloader
debug: fastboot: wait for device
debug: Using fallback platform tools!
debug: Running platform tool fallback exec asar cmd fastboot devices
debug:
debug: reboot to bootloader [DONE] err:null
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices
debug: Running platform tool fallback exec asar cmd fastboot devices

The phone is in fast boot mode.
Can someone help me out?
Miguel

posted in Support

M

RE: OpneVpn Editor App

Hi all!!,
Long time I don't setup a new VPN. Yes we don't need this app for OpenVpn now, the system settings have all the necessary things to setup a OpenVpn with CA.
Regards
Miguel
PS: I think that app have more options but i really don't remember because I don't have the app anymore

posted in Support
M
mpnegro
RE: most wanted core apps to run ubuntu as daily phone OS

Hi
I need this app OpenVpn editor APP
http://news.softpedia.com/news/ubuntu-touch-openvpn-support-gets-a-prototype-ui-here-s-how-to-install-it-498543.shtml

posted in App Development
M
mpnegro
RE: OpneVpn Editor App

@Phil-UK Anyone have the app? I really need this to connect to my servers

posted in Support
M
mpnegro
OpneVpn Editor App

Hi
Anyone now wher I can find the OpenVpn editor APP? The old links don't work
http://news.softpedia.com/news/ubuntu-touch-openvpn-support-gets-a-prototype-ui-here-s-how-to-install-it-498543.shtml

posted in Support
M
mpnegro
RE: Ubuntu Phone Bq 4.5 don't detect SIM card after flash with ubports!

Hi All,
After reflashing again, clean the SIM card, change and re-change the SIM slot, it finally detected the SIM card. Probably something is damage, or in the SIm or in the slot. Thks for the help

posted in Support
M
mpnegro
RE: Ubuntu Phone Bq 4.5 don't detect SIM card after flash with ubports!

Hi
Thks for the replays.
@jamesp The phone was working ok before i flash the device, so probably this is not hardware problem.
@advocatux I've done that, and don't work.
If no solution I'm going to try to reflash with the Bq Image again and see if it starts to work.

posted in Support
M
mpnegro