Related
Just saw some interest for Fedora install on Nook in another thread to my surprise. I thought I am the only pervert interested.
Anyway this is pretty raw at the moment. You need to know your way around Linux and have a Linux box (naturally).
Just not to disappoint you later on, here's what not working:
Only based on Fedora13 from upstream (F14 work is ongoing by Fedora-Arm team and I am just tracking them).
Wifi (still did not get to look into it)
BT (same)
accelerated graphics
Don't know of any touch-friendly WM, so defaults to Gnome.
Multitouch (disabled in driver at the moment since no userspace support anyway).
backlight control does not work, need to rewrite the kernel driver
Xorg does not know what to do with accelerometer input.
Probably tons of other things I forgot about.
You must be out of your mind if you want to try it on a tablet at this stage. Or just super curious.
You will need a microSD (at least 2G) card that you can dedicate to this.
Instructions:
Get "base" fedora sdcard image: http://nook.handhelds.ru/fedora/fedora-sdcard-v0.1.img.gz
Get base Fedora 13 beta3 rootfs: http://lists.fedoraproject.org/pipermail/arm/2011-May/001271.html
Get kernel modules for the kernel: http://nook.handhelds.ru/fedora/modules-2.6.32.9-fc13.tar.bz2
Unzip the base sdcard image and write it to your sdcard with dd.
run fdisk on the sdcard and add another partition covering the rest of sdcard in addition to the one already there. Write changes
do mkfs.ext4 /dev/yoursdcard2 (basically format the second partition you just created as ext4)
mount the /dev/yoursdcard2 somewhere as root (/mnt/somewhere later on)
untar the F13-beta3 rootfs to the /mnt/somewhere
Now you are almost ready, just need to fill some configs.
Edit /mnt/somewhere/etc/sysconfig/network-scripts/ifcfg-usb0 and add this there:
Code:
DEVICE=usb0
#BOOTPROTO=dhcp
BROADCAST=192.168.2.255
IPADDR=192.168.2.2
NETMASK=192.168.2.0
NETWORK=192.168.2.0
GATEWAY=192.168.2.1
ONBOOT=yes
Edit /mnt/somewhere/etc/resolv.conf and change "nameserver" there to 8.8.8.8
Add multitouch config in /mnt/somewhere/etc/X11/xorg.conf.d/touchscreen.conf
Code:
Section "InputClass"
Identifier "touchscreen"
MatchIsTouchScreen "on"
MatchProduct "cyttsp-i2c"
Driver "mtev"
Option "SendCoreEvents" "On"
Option "SwapAxes" "true"
Option "InvertY" "true"
EndSection
cd /mnt/somewhere/lib/modules and untar the modules file there.
umount /mnt/somewhere
Ok, now you are ready to do some stuff on the nook.
Insert your sdcard into the nook and boot it. You'll see Fedora text console. The installation is pretty basic.
Plug the nook into your Linux PC usb port. It should see a new network device
On the linux PC as root execute: ifconfig usb0 192.168.2.1 netmask 255.255.255.0
Enable ip forwarding on your host if you have it disabled (typically in /etc/sysctl.conf, the setting is ...ip_forward, make it =1. Run sysctl -p for the changes to make effect.
Enable internet access to internet for your nook via IP masquerading: iptables -t nat -I POSTROUTING -s 192.168.2.2 -j MASQUERADE ; iptables -I FORWARD -s 192.168.2.2 -j ACCEPT ; iptables -I FORWARD -d 192.168.2.2 -j ACCEPT
Now use ssh to login to your Nook: slogin [email protected] the root password is "fedoraarm" (no quotes)
Once logged into the nook, time to install some packages.
rpm -Uvh http://hongkong.proximity.on.ca/yum/base/12/arm/fake-kernel-provides-1.0.0-0.fc12.armv5tel.rpm
update the system: yum update ; yum install tar openssh-clients
Install the gnome environment: yum groupinstall 'GNOME Desktop Environment' --skip-broken
The gnome installation will take a while and will download everything from the net.
Now install the multitouch Xorg driver, get it at http://nook.handhelds.ru./fedora/xf86-input-mtev-0.1.12-1.armv5tel.rpm
Ok. Now you are ready to go. Run "startx &" and the Gnome will start on the nook. You can play with it a bit, use your finger as the mouse pointer.
You can add startx & at the end of e.g. /etc/init.d/rc.local to make it start on system startup or you can do it in a more pretty way.
There are some virtual keyboards in the repo. I tried gko and it sucks.
the "onboard" seems to be the one working best for me. "xvkbd" is a bit hard to operate.
The best one of them all is fvkbd, but it needs libfakekey missing from the repo, grab it at http://arm.koji.fedoraproject.org/p...3/armv5tel/libfakekey-0.1-6.fc13.armv5tel.rpm
Enjoy.
Fedora-arm homepage: http://fedoraproject.org/wiki/Architectures/ARM
I intend to include all the missing pieces into the fedora repo so that you don't need to install all those extra things. Also eventually I plan to add more hardware support and then hopefully migrate to a much newer kernel.
Ha, cool. Glad to see that not everyone thinks that only Ubootoo should be thrown on devices. I'll give this a twiddle for fun.
13 had Moblin, I wonder if that's any better for touch input..
Now i don't feel near as silly for working on my gentoo install for the nook!
Nice, I am still waiting on OpenSuSe
Why not try using Gnome 3? I just poked around in Fedora 15 today and saw the new UI, and I loved it. Bigger buttons, launcher dock, etc. Give it a look!
pts69666 said:
Why not try using Gnome 3? I just poked around in Fedora 15 today and saw the new UI, and I loved it. Bigger buttons, launcher dock, etc. Give it a look!
Click to expand...
Click to collapse
Fedora15 is not available for arm arch yet. But there is some work in that direction. So sure, once it's available I'd give it a try.
Great stuff here. I knows its early development, but fun none the less to see what our nooks can do.
And thanks verygreen for all your developments lately
Sent from my NookColor using Tapatalk
verygreen said:
Fedora15 is not available for arm arch yet. But there is some work in that direction. So sure, once it's available I'd give it a try.
Click to expand...
Click to collapse
in fedora 13,
Code:
su
yum install gnome-shell
...
============================================================================================================
Package Arch Version Repository Size
============================================================================================================
Installing:
gnome-shell i686 2.28.0-3.fc12 fedora 301 k
Installing for dependencies:
gjs i686 0.4-1.fc12 fedora 126 k
mutter i686 2.28.0-2.fc12 fedora 1.2 M
Transaction Summary
============================================================================================================
Install 3 Package(s)
Upgrade 0 Package(s)
...
gnome-shell -replace
I haven't tested it myself; however, it is something I found. My linux hard drive had hard drive failure. So, I am on windows in the meantime. Will report back later after testing it myself.
pts69666 said:
in fedora 13,
Code:
su
yum install gnome-shell
...
============================================================================================================
Package Arch Version Repository Size
============================================================================================================
Installing:
gnome-shell i686 2.28.0-3.fc12 fedora 301 k
Installing for dependencies:
gjs i686 0.4-1.fc12 fedora 126 k
mutter i686 2.28.0-2.fc12 fedora 1.2 M
Transaction Summary
============================================================================================================
Install 3 Package(s)
Upgrade 0 Package(s)
...
gnome-shell -replace
I haven't tested it myself; however, it is something I found. My linux hard drive had hard drive failure. So, I am on windows in the meantime. Will report back later after testing it myself.
Click to expand...
Click to collapse
No "gnome-shell" package in Fedora-arm repo at this moment,
Quite excited to see some work in bringing Fedora to the Nook Color! I <3 Fedora.
I just wish ARM had the same support as the full Fedora. Or that they would skip releases for Fedora ARM and go yearly... aka, skip to 15 next, then 17.
Could this be used to help port Ubuntu Touch?
moocow1452 said:
Could this be used to help port Ubuntu Touch?
Click to expand...
Click to collapse
No, Ubuntu Touch is based on CM and has very little in common with a full Linux port.
(This is not nessesary for MAC but you can have this for further use later,
In general you will need:
Python 2.4 -- 2.7, which you can download from python.org.
JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older. You can download both from java.sun.com.
Git 1.7 or newer. You can find it at git-scm.com)
Setting up a Mac OS X build environment
To build the Android files in a Mac OS environment, you need an Intel/x86 machine running MacOS 10.6 (Snow Leopard).
Android must be built on a case-sensitive file system because the sources contain files that differ only in case. We recommend that you build Android on a partition that has been formatted with the journaled file system HFS+. HFS+ is required to successfully build Mac OS applications such as the Android Emulator for OS X.
Creating a case sensitive disk image
If you want to avoid partitioning/formatting your hard drive, you can use a case-sensitive disk image instead. To create the image, launch Disk Utility and select "New Image". A size of 25GB is the minimum to complete the build, larger numbers are more future-proof. Using sparse images saves space while allowing to grow later as the need arises. Be sure to select "case sensitive, journaled" as the volume format.
You can also create it from a shell with the following command:
# hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/android.dmg
This will create a .dmg (or possibly a .dmg.sparsefile) file which, once mounted, acts as a drive with the required formatting for Android development. For a disk image named "android.dmg" stored in your home directory, you can add the following to your ~/.bash_profile to mount the image when you execute "mountAndroid":
# mount the android file image
function mountAndroid { hdiutil attach ~/android.dmg -mountpoint /Volumes/android; }
Once mounted, you'll do all your work in the "android" volume. You can eject it (unmount it) just like you would with an external drive.
Installing required packages
Install XCode from the Apple developer site http://developer.apple.com/. We recommend version 3.1.4 or newer, i.e. gcc 4.2. Version 4.x could cause difficulties. If you are not already registered as an Apple developer, you will have to create an Apple ID in order to download.
Install MacPorts from macports.org.
Note: Make sure that /opt/local/bin appears in your path BEFORE /usr/bin. If not, add
export PATH=/opt/local/bin:$PATH
to your ~/.bash_profile.
Get make, git, and GPG packages from MacPorts:
$ POSIXLY_CORRECT=1 sudo port install gmake libsdl git-core gnupg
If using Mac OS 10.4, also install bison:
$ POSIXLY_CORRECT=1 sudo port install bison
Reverting from make 3.82
There is a bug in gmake 3.82 that prevents android from building. You can install version 3.81 using MacPorts by taking the following steps:
Edit /opt/local/etc/macports/sources.conf and add a line that says
file:///Users/Shared/dports
above the rsync line. Then create this directory:
$ mkdir /Users/Shared/dports
In the new dports directory, run
$ svn co --revision 50980 http://svn.macports.org/repository/macports/trunk/dports/devel/gmake/ devel/gmake/
Create a port index for your new local repository:
$ portindex /Users/Shared/dports
Finally, install the old version of gmake with
$ sudo port install gmake @3.81
Setting a file descriptor limit
On MacOS the default limit on the number of simultaneous file descriptors open is too low and a highly parallel build process may exceed this limit.
To increase the cap, add the following lines to your ~/.bash_profile:
# set the number of open files to be 1024
ulimit -S -n 1024
Next: Download the source
Your build environment is good to go! Proceed to downloading the source....
Why you posted this? It can be found on android's website. Also,you didn't post the whole tutorial.
why not simply install VirtualBox vor Mac and install a VM within?
...sometimes the life is complicated^^
@SWEATTAIMI did you actually manage to get a fully working build on mac? And if yes which version of OS X?
I've tried many times on OS X 10.7 and eventually ended up installing ubuntu on a separate partition...
secondary partition? what about the users here?
i use a VM on a small **** x86 notebook and can do all the development work + complete compiling. i thought a mac has much better hardware^^
I used to have ubuntu installed in vmware too but compiling took too long and it was really annoying. I rather prefer it this way... No shared resources
popdog123 said:
@SWEATTAIMI did you actually manage to get a fully working build on mac? And if yes which version of OS X?
I've tried many times on OS X 10.7 and eventually ended up installing ubuntu on a separate partition...
Click to expand...
Click to collapse
Fully working what ?
Sent from my LG-P500 using xda premium
ciaox said:
Why you posted this? It can be found on android's website. Also,you didn't post the whole tutorial.
Click to expand...
Click to collapse
This is full for mac
Its a setup only
Sent from my LG-P500 using xda premium
SWEATTAIMI said:
Fully working what ?
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
:|
10 char
popdog123 said:
:|
10 char
Click to expand...
Click to collapse
You mean build then i have not came to that point yet as i downloaded all sources on my Japanese lesson xD
Sent from my LG-P500 using xda premium
I wonder if this will work for ICS on 4GB macbook
caslca said:
I wonder if this will work for ICS on 4GB macbook
Click to expand...
Click to collapse
Yes it will worked on a macbook 2010 version
Sent from Mexico
Hey XDA!
For those of us that use Arch linux, compiling Android projects can be a little more challenging than on Ubuntu due to the fact the Arch is a rolling release distro. To solve this, I made a tool that allows YOU to choose whether you want to run Arch or Ubuntu in the command line without dual booting. This isn't anything new, just a simplified implementation of an existing method.
What it does:
When you open a terminal, you will be prompted with "Would you like to connect to Arch linux or Ubuntu?". You can enter A for Arch or U for Ubuntu. If you choose Arch, you will be put into your stock environment, but your bash prompt will look like
Code:
[[COLOR="red"]user[/COLOR]@[COLOR="cyan"]Arch[/COLOR] ~]:
If you choose Ubuntu, you will be entered into your Ubuntu chroot, and your bash prompt will look like
Code:
[[COLOR="red"]user[/COLOR]@[COLOR="magenta"]Ubuntu[/COLOR] ~]:
DISCLAIMER
Because Arch linux is aimed at enthusiast and experienced linux users, replies about simple or lack-of-experience issues will not be given priority. Use the following with caution.
How to setup an Ubuntu chroot:
1. Install schroot and debootstrap
2. Follow the steps given here https://bbs.archlinux.org/viewtopic.php?id=100039, or run create-chroot.sh in the OSConnect git repo.
How to install OSConnect:
1. Clone https://github.com/frap129/OSConnect
2. Run the given install.sh
3. If you use terminal mostly locally, respond "Local" to the prompt. If you mostly connect via ssh, respond "SSH" to the prompt.
4. If you connect via SSH, connect as root from now on, not your user. OSConnect will switch to your user for you.
Done! Restart to use.
XDA:DevDB Information
OSConnect, Tool/Utility for the Chef Central
Contributors
frap129
Source Code: https://github.com/frap129/OSConnect
Version Information
Status: Stable
Created 2016-05-15
Last Updated 2016-05-15
How it works:
Ubuntu chroot:
This work by downloading the Ubuntu system files to /var/chroot/ubuntu. The schroot tool then executes bash from ubuntu, and tricks the system into believing that /var/chroot/ubuntu is actually the system root directory.
OSConnect:
OSConnect is contained in its own file, .osconnectrc. This file is executed when shell is reached via your .bashrc. The .osconnectrc is a bash script that asks what operating system you would like to use, then either dumps you into normal shell, or starts the Ubuntu chroot. It also modifies the PS1 (bash prompt) to look cleaner and better distinguish between Arch and Ubuntu.
What is the difference between local and ssh?
The only difference between the local and ssh versions is whether or not youre prompted for your password (when chroot is started) because schroot must be run as root. On the local version, you are simply prompted for your password when necessary. On the ssh version, you are expected to connect as root, and therefore will not be prompted for your password.
HALP I CANT LOG IN AS ROOT
If you are having trouble connecting via SSH as root, follow https://askubuntu.com/questions/511833/cant-ssh-in-as-root
Resource wise is this lighter than running ubuntu as a docker image?
HaoZeke said:
Resource wise is this lighter than running ubuntu as a docker image?
Click to expand...
Click to collapse
I'm way to late for this to matter, but yes, its much lighter than running at as a docker image
frap129 said:
I'm way to late for this to matter, but yes, its much lighter than running at as a docker image
Click to expand...
Click to collapse
Better late than never! ? neat stuff ?
So many of you have been asking, "How do I add Remix OS to my current boot configuration?", "Is it possible?".
Well, I'm telling you it is if you follow my guide on how to Dual/Triple-Boot Remix OS with virtually any OS. This guide is mainly for Windows 10 and Ubuntu 16.04 but it will work with any OS that is Dual-booted with Ubuntu!
Files/Tools Needed:
Remix OS Installation Zip
7-zip
Manual Install
Step 1 Extract your downloaded Remix OS zip
Step 2 Extract the resulting ISO file
Step 2a Create a partition where you want to install Remix OS
Step 2b Copy the files extracted from the ISO file to the newly created partition
Step 3 Reboot to Ubuntu
Step 4 Install Grub-Customizer
Step 4a Open Terminal via the App Launcher or with the key combo CTRL+ALT+T
Copy/Paste and run these commands
Code:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
Step 5 Open Grub-Customizer
Step 5a CTRL+N Name: Remix OS Type: Other
Copy/Paste this into the text box:
Code:
set root='(hd0,2)'
linux /RemixOS/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive SRC=/RemixOS REMOUNT_RW=1
initrd /RemixOS/initrd.img
Step 5b If you are using Remix OS x64 change 'androidboot.hardware=remix_x86' to 'androidboot.hardware=remix_x86_64'
Step 5c Change (hd0,2) to what yours is eg, sda2 will be (hd0,2) sdb3 will be (hd1,3)
Step 6 Click OK
Step 6a Click Save, once done close Grub-Customizer and reboot to Remix OS
Note: You will see a black screen for a while, this is becuase the system.sfs is being coverted to system_dev.img which involves extracting the sfs file and renaming the output!
After a while, Remix OS should boot up!
Congrats, you have now have added Remix OS to your Boot Configuration!
Have fun guys!
Hi. My Minecraft pe always crash in Remix OS. Can you help me?
Farras said:
Hi. My Minecraft pe always crash in Remix OS. Can you help me?
Click to expand...
Click to collapse
Nah, sorry. It is most likely crashing to due the drivers included in Remix OS!
moman2000 said:
Nah, sorry. It is most likely crashing to due the drivers included in Remix OS!
Click to expand...
Click to collapse
in my case i'm already dualboot windows 7 and remixos (using remix istaller) and i planing to install ubuntu, i was create new partition for ubuntu and my question is how do i can boot to remixos?, can u help me?
Ubuntu 20.04 sees phone with Linux adb v28 using 'adb devices'.
I've installed the usb driver for my Blackview A80 phone in VirtualBox Windows 10 VM. However, VirtualBox Windows 10 VM fails to see my phone with adb (v1.0.32 & 1.0.39). I'd like to download adb.exe v1.0.40 (as that's the requirement to run B4A Windows app under Wine in Ubuntu.). But I can't find that version anywhere. Has anyone got adb.exe v1.0.40?
I've followed the instructions on
http://adbcommand.com/articles/How to build adb(1.0.40) for windows on Ubuntu but I get 'fatal: cannot make .repo directory: Permission denied' on the step
repo init -u https://android.googlesource.com/platform/manifest. I know nothing about repo. Anybody have any ideas about this repo problem?
johnaaronrose1 said:
Ubuntu 20.04 sees phone with Linux adb v28 using 'adb devices'.
I've installed the usb driver for my Blackview A80 phone in VirtualBox Windows 10 VM. However, VirtualBox Windows 10 VM fails to see my phone with adb (v1.0.32 & 1.0.39). I'd like to download adb.exe v1.0.40 (as that's the requirement to run B4A Windows app under Wine in Ubuntu.). But I can't find that version anywhere. Has anyone got adb.exe v1.0.40?
I've followed the instructions on
http://adbcommand.com/articles/How to build adb(1.0.40) for windows on Ubuntu but I get 'fatal: cannot make .repo directory: Permission denied' on the step
repo init -u https://android.googlesource.com/platform/manifest. I know nothing about repo. Anybody have any ideas about this repo problem?
Click to expand...
Click to collapse
have you tried using chocolatey on the windows VM, to see if their adb source works for you?
you would need chocolately preinstalled, this thread would explain better.
How To Use Chocolatey
========================= ============================================ HOW TO USE CHOCOLATEY ============== ============= Hi Friends~! This amazing package manager changed my Windoz life
forum.xda-developers.com
after you have chocolatey installed, you would run this command:
choco install adb
essentially, it will dl the latest adb, and wrap all it's variables with the correct permissions, even in a vm. I'm not sure if this will help you, but just wanted to put it out there~!
Have a good day~!
jenneh said:
have you tried using chocolatey on the windows VM, to see if their adb source works for you?
you would need chocolately preinstalled, this thread would explain better.
How To Use Chocolatey
========================= ============================================ HOW TO USE CHOCOLATEY ============== ============= Hi Friends~! This amazing package manager changed my Windoz life
forum.xda-developers.com
after you have chocolatey installed, you would run this command:
choco install adb
essentially, it will dl the latest adb, and wrap all it's variables with the correct permissions, even in a vm. I'm not sure if this will help you, but just wanted to put it out there~!
Have a good day~!
Click to expand...
Click to collapse
The specified link does not AFAIK give instructions on how to install chocolately.
Oh It Does~! As well As a VM demonstration on how to install on an unlisted YT vid. But Okay~! Just trying to help ;-)
The link you supplied with its links to "How to install chocolately" sends me to an advertising site.
johnaaronrose1 said:
Ubuntu 20.04 sees phone with Linux adb v28 using 'adb devices'.
I've installed the usb driver for my Blackview A80 phone in VirtualBox Windows 10 VM. However, VirtualBox Windows 10 VM fails to see my phone with adb (v1.0.32 & 1.0.39). I'd like to download adb.exe v1.0.40 (as that's the requirement to run B4A Windows app under Wine in Ubuntu.). But I can't find that version anywhere. Has anyone got adb.exe v1.0.40?
I've followed the instructions on
http://adbcommand.com/articles/How to build adb(1.0.40) for windows on Ubuntu but I get 'fatal: cannot make .repo directory: Permission denied' on the step
repo init -u https://android.googlesource.com/platform/manifest. I know nothing about repo. Anybody have any ideas about this repo problem?
Click to expand...
Click to collapse
Would this help?
Android SDK Platform Tools for Windows
Android Debug Bridge version 1.0.26 platform-tools_r03-windows.zip (2011-02-23) platform-tools_r04-windows.zip (2011-05-10) platform-to...
cxzstuff.blogspot.com