5,604,050 Members 47,101 Now Online
XDA Developers Android and Mobile Development Forum

Ubuntu for N80xx

Tip us?
 
X-Stranger
Old
#191  
X-Stranger's Avatar
Senior Member - OP
Thanks Meter 182
Posts: 153
Join Date: Sep 2008

 
DONATE TO ME
Quote:
Originally Posted by kiven_09 View Post
Was working, but hangs after 2 mins!
Why?
Please help
Can we get more details? What was working? What did you do? What session running?

As I mentioned before, the Gnome might work unstable due to graphics support issues.
By clicking "THANKS" you encourage me to do more.
Donations are always welcome too
 
Haabba
Old
#192  
Junior Member
Thanks Meter 0
Posts: 10
Join Date: Sep 2013
Quote:
Originally Posted by X-Stranger View Post
Can we get more details?s.
please

help meeee whats the porblem with me , when i boot with recovery , stop at this black screen ??
Attached Thumbnails
Click image for larger version

Name:	2014-03-13-1595.jpg
Views:	214
Size:	271.7 KB
ID:	2626913  
 
X-Stranger
Old
#193  
X-Stranger's Avatar
Senior Member - OP
Thanks Meter 182
Posts: 153
Join Date: Sep 2008

 
DONATE TO ME
You did something wrong: the initrd cannot find /sbin/init process to initiate Linux run. Still need more details: what did you do before it stopped to work, what kind of installation did you do, what is the model of your device, etc.
By clicking "THANKS" you encourage me to do more.
Donations are always welcome too
 
ncc74656
Old
#194  
Senior Member
Thanks Meter 7
Posts: 279
Join Date: May 2008
Would it be possible for someone to make elementary os for our tablet?

Sent from t.....k
 
ddggttff3
Old
#195  
ddggttff3's Avatar
Recognized Contributor / Recognized Developer
Thanks Meter 760
Posts: 593
Join Date: Dec 2009
Location: Twin Cities, MN

 
DONATE TO ME
Quote:
Originally Posted by ncc74656 View Post
Would it be possible for someone to make elementary os for our tablet?

Sent from t.....k
Not really, Elementary OS only releases x86 and x64 packages.
Devices:
Nexus 5
Nexus 7 2013
Samsung Note 10.1
Nexus Q
Too Many Chromecasts

Retired:
GS3, Droid Bionic, N7 2012, Droid X, HTC Vogue
 
kuitsu
Old
(Last edited by kuitsu; 9th April 2014 at 07:46 PM.)
#196  
kuitsu's Avatar
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Oct 2010
Location: Tampere
Quote:
Originally Posted by X-Stranger View Post
Confirmed, the solution I've taken from ArchLinux does not work in Ubuntu. To fix Bluetooth, please overwrite /opt/bluez/brcm_patchram_plus file with attached to this message (don't forget to unpack it before) and make it executable ("chmod +x /opt/bluez/brcm_patchram_plus"). Then go to /etc folder of Ubuntu, find rc.local file and comment out the line starting with "/usr/bin/valgrind ...", save file and reboot.

Please let me know if this helps. As for me, I was able to connect my bluetooth mouse after fix.
First of all thanks for great work.

Ubuntu is working nicely except I am having troubles to get bluetooth keyboard working.

I did the fix described above and changed bluetooth device address
Code:
mount /dev/mmcblk0p3 /srv
cp -f /srv/bluetooth/bt_addr /opt/bluez/
umount /srv
Also I had to manually start brcm_patchram_plus with command
Code:
nohup /opt/bluez/brcm_patchram_plus --bd_addr `cat /opt/bluez/bt_addr` --enable_hci --enable_lpm --no2bytes --tosleep 50000 --baudrate 4000000 --use_baudrate_for_download --patchram /opt/bluez/bcm4334.hcd --i2s=1,0,0,0 /dev/ttySAC0 >/dev/null 2>&1 &
after boot. It did not seem to work when started from rc.local.

After these steps I was able to enable bluetooth but still gnome bluetooth settings could not find my bluetooth keyboard. I succeeded to pair my bluetooth keyboard from command line using commands
Code:
root@GT-N8000:/# hcitool scan
Scanning ...
	7C:1E:52:09:A1:E7	Microsoft Wedge Mobile Keyboard
root@GT-N8000:/# bluez-simple-agent hci0 7C:1E:52:09:A1:E7
DisplayPasskey (/org/bluez/2902/hci0/dev_7C_1E_52_09_A1_E7, 065352)
Release
New device (/org/bluez/2902/hci0/dev_7C_1E_52_09_A1_E7)
root@GT-N8000:/# bluez-test-device trusted 7C:1E:52:09:A1:E7 yes
After these steps bluetooth keyboard appeared in gnome settings too. Even though keyboard was communicating with tablet for sure in authentication step above it just won't like to connect after pairing anymore. The connect command just gives varying error messages such as
Code:
root@GT-N8000:/# bluez-test-input connect 7C:1E:52:09:A1:E7
Traceback (most recent call last):
  File "/usr/bin/bluez-test-input", line 42, in <module>
    input.Connect()
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
and obviously keyboard is not working.

Am I doing something wrong or missing something or is bluetooth driver just buggy?
 
X-Stranger
Old
#197  
X-Stranger's Avatar
Senior Member - OP
Thanks Meter 182
Posts: 153
Join Date: Sep 2008

 
DONATE TO ME
You seems to be doing all correctly, but yes, the bluetooth is a bit buggy. On ArchLinux it was not able to work without running it through valgrind - without that tool the bluetooth process was failing and disappearing from process list. Please check if you have the bluetooth daemon running on the last step.
By clicking "THANKS" you encourage me to do more.
Donations are always welcome too
 
GPOT97
Old
#198  
Junior Member
Thanks Meter 0
Posts: 7
Join Date: Jan 2012
Quote:
Originally Posted by czikus View Post
Ok, that's progress. What I did was:
- get the recovery from /dev/mmcblk0p6
- unpack it
- unpack the initrd.img
- replace the modules
- pack initrd.img
- abootimg --create recovery.img -k zImage -r initrd.img -f bootimg.cfg
- flash back to /dev/mmcblk0p6

This results in errors during boot as shown in the attached image


What am I doing wrong?

Btw. Donation on the way
I have a few questions for you, here they are:
1) What is working/not working as of right now?
2) What is the process you went through to get things working?
3) Can I replicate this process and continue to work on this?

I am well versed in Linux and getting things working on proprietary hardware (*cough* *cough* Apple). I was hoping I could help, but first I want to know what you have tried and what has worked. Save me a little bit of time. PM me if you want to collaborate and work on this together.

Tags
galaxy, linux, n8000, note, ubuntu
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes