Related
If you don't know what this is, then you don't need to know!
I successfully compiled Nano to run on Android!
http://android.modaco.com/content/software/291983/nano-editor-for-android/
It will run perfectly on any ROM that has terminfo set up, if your ROM doesn't, you may need to do this before running nano:
Code:
su
export TERMINFO=/etc/terminfo
export TERM=linux
Any problems, holler! I'll be putting this in my next Hero pack too...
P
That's cool!
Definitely will give it a try. Use nano every day on my ubuntu system. It would be nice to see that familiar item on my phone . Screen would be pretty wild as well. Screen's another one of those utilities that is hard to explain but easy to show
I'd like to get rsync working on my phone as well since I use it for backups all the time on my desktop now. Think it would be really handy to have a gnu-utils package that people could add.
What owner permissions should I set for it? I get a Permission Denied error on CyanogenMod 4.0.4.
EDIT: Nevermind, forgot to run chmod +x on it.
sweet! I was looking for this about a week ago. glad someone did it. THANKS!
I've mailed you concerning this. I've been through hell trying to compile that *****, hope you are willing to help out. So far I've compiled bash4.0 and busybox 1.15.1 with no problems, but im stuck on nano2.0.9. Anyway check the mail, hope you can help! And congrats for pulling it off hehe.
wops, doublepost.
guys, i wanna learn abt nano for ndroid. how to make it run in android mobile?
i'm using ra-ion1.6.1 donut. already push nano into /system/xbin and /system/bin. but how to make it run? and how to use command in ms-dos?
su
export TERMINFO=/etc/terminfo
export TERM=linux
i dun understand this.
i'm currently using vista.
do i need linux os to do anythg?
how to enable syntax highlighting???
I am currently using nano taken from here http://android.modaco.com/content/software/291983/nano-editor-for-android/ on my G1 (SuperD 1.9.3).
I really want to enable syntax highlighting, and I went through this guide:
http://www.technotizie.it/frame/74510/nano-syntax-highlighting-how-to-enable-syntax-highlighting-in-nano-text-editor
I installed nano binary into /system/xbin and gave it executable permissions.
I created a /system/home dir and created a .nanorc file as stated here:
http://wiki.linuxhelp.net/index.php/Nano_Syntax_Highlighting#Alt_C.2FC.2B.2B.2Fh
I also set up a $HOME var, with value = /system/home
nano starts up but doesn't highlight my .cpp syntax.
what am I missing???
Thanks,
Genesio
Anyone have the terminfo directory saved off by chance? Seems to be missing from my htc evo stock 2.2 rom.
Edit: And naturally five seconds after posting I find it. See androidforums.com/evo-4g-all-things-root/124506-guide-full-bash-shell-nano-tab-completion-color-over-ssh.html
Hi all,
i've got a problem with my nano...
The "enter" button just do an LF, so I do not know how to give the "ok" for saving file,exiting, etc ... any help ?
mpmilestogo said:
Screen would be pretty wild as well. Screen's another one of those utilities that is hard to explain but easy to show
Click to expand...
Click to collapse
I second this... I even have screen on my .bash_rc. It is pretty convenient!
I made it run, but in another note, I have always thought the terms' screen size is quite small.
Nevertheless, nice utility!
Hi, I have a problem with nano..
when I try execute them, it writes
Code:
Error opening terminal: linux.
What can i do?
(miui 2.8.31) (4.0.4)
SEmp91 said:
Hi, I have a problem with nano..
when I try execute them, it writes
Code:
Error opening terminal: linux.
What can i do?
(miui 2.8.31) (4.0.4)
Click to expand...
Click to collapse
I have the same problem.
The link you seek. terminfo should be in /etc
paulobrien said:
If you don't know what this is, then you don't need to know!
I successfully compiled Nano to run on Android!
http://android.modaco.com/content/software/291983/nano-editor-for-android/
It will run perfectly on any ROM that has terminfo set up, if your ROM doesn't, you may need to do this before running nano:
Code:
su
export TERMINFO=/etc/terminfo
export TERM=linux
Any problems, holler! I'll be putting this in my next Hero pack too...
P
Click to expand...
Click to collapse
I've just got this :
oad $ bash
[localhost /mnt/sdcard/Download]$ nano
Error opening terminal: screen.
EDIT : [SOLVED!]
If you are a termux user and want to install a nano or vi or any other binaries of termux in Andriod su mode. Here is the link to Termux superuser.
Give it a star if it was helpful !!!
I've been running Debian natively from my SD card for a while, so I decided I'd share the [relatively easy] instructions. First, though, here's the status of the hardware support...
* X11 is working quite nicely. 480x640 resolution is best for using E17.
* I'm trying to think up a solution for the 3D accelerator. LLVMpipe works but it's not much faster than classic Mesa. Maybe that's because I'm only testing performance with Mupen64Plus and SuperTux Ideally we would have an open-source OpenGL ES 1.0 driver with an OpenGL 1.3 wrapper/Gallium state tracker, but unfortunately Qualcomm closed it
* The hardware buttons don't generate input events (except the power button, which apparently makes SDL windows fullscreen).
* USB function ether works. This means you can SSH into it or update packages without a data connection (I don't think data even works).
* Sound doesn't work because Android doesn't use ALSA - or maybe because DZO hasn't written the proper driver...
* Camera(s) would need a Video4Linux driver; again, not my area
* Bluetooth is untested.
* GPS needs userspace work (gpsd?) - maybe the HTC Dream page at HTC-Linux.org has info...
* Calling - untested because: 1) I doesn't got the software, and 2) even if it worked, I have no one to call
If you're willing to wait indefinitely for those things to be fixed (or if you don't care), all you need is a Debian chroot on an EXT2-formatted SD card and my special NBH. The NAND should also work*, but Debian probably wouldn't fit on it. These instructions should also work for Ubuntu, Gentoo, FSO/OpenMoko, Angstrom, ARMedSlack, Fedora, or what have you - the only requirements are ARMv6 or lower and a semi-standard root filesystem layout (i.e. /sbin/init).
For those of you who don't trust binaries, I've uploaded my patches to the kernel and tinboot needed for Debian to boot. For everyone else, I have NBH files ready. Just flash the NBH, insert your SD card, and it should boot.
Links:
http://www.mediafire.com/?mnv2memddug (source)
http://www.mediafire.com/?immywzmmqjn (binaries)
*LogFS patch included and enabled in my NBH.
Interesting, i'm going to have to try it out, any chance of getting it bootable from within android, like haret is with windows?
what exactly is debian??
is it like ubuntu thats on my computer
jadenj5 said:
what exactly is debian??
is it like ubuntu thats on my computer
Click to expand...
Click to collapse
yes
10char
little confused though, where do I get the debian root files though
Debian Root
Instructions to build your own RootFS follow. If you're lazy, Google for a pre-built one.
If you're on Ubuntu:
Code:
sudo apt-get install debootstrap
sudo debootstrap --arch armel --foreign unstable root/ http://http.us.debian.org/debian
Substituting "unstable" for "stable" or "testing", "root/" with the the path to the directory you want the rootfs in (probably your SD card mountpoint), and your country code in ftp.??.debian.org (or another mirror). You might also need to do
Code:
sudo mount -o remount,rw,dev,exec $MOUNTPOINT
to your SD card (which, again, should be ext2-formatted) for debootstrap to work.
Then to complete the bootstrap:
Code:
sudo apt-get install qemu-kvm-extras-static
sudo cp /usr/bin/qemu-arm-static $ROOTFS/usr/bin/
sudo chroot $ROOTFS
From inside the chroot, do
Code:
/debootstrap/debootstrap --second-stage
Then, apt-get install whatever you want on the phone (after configuring /etc/apt/sources.list), exit the chroot, unmount the card, insert it in your phone, and boot!
You'll need - at the very least - xserver-xorg-video-fbdev and xserver-xorg-input-evdev *WITHOUT* installing the other video or input drivers. And a desktop/window manager. If you haven't used Debian before, try e17.
Thanks man, i'm going to go check it out
If you're lazy, Google for a pre-built one.
Click to expand...
Click to collapse
can't find one.?
If you're on Ubuntu:
Click to expand...
Click to collapse
ubuntu 10.04 debootstrap doesnt know about stable/testing/unstable names, but knows about lenny, squeeze, sid
okay, I maked Debian unstable rootfs - here it is (127MB tar.bz2). here is dpkg -l.
root password is "1", apt sources.list is configured to most close to me mirror. I also added /proc into fstab.
how to pack my rootfs into .img image now?
can you post a screenshots please ???
there is nothing to show now, really. we need to make working pack first.
google e17 screenshots, on device you will have same.
a note about the sound issue. You are correct in that the vogue kernel does not have alsa support at this time.
nice job on this
Code:
E: No such script: /usr/share/debootstrap/scripts/stable
debootstrap installed with no errors but that's what I get when I try to run
Code:
sudo debootstrap --arch armel --foreign stable /media/79e9dd5a-174b-4324-a704-6aa06807fe35 http://http.us.debian.org/debianc
Try "lenny" instead of stable.
gTan64 said:
Try "lenny" instead of stable.
Click to expand...
Click to collapse
progress but now i get
Code:
I: Retrieving Release
E: Failed getting release file http://http.us.debian.org/debianc/dists/lenny/Release
Look closely - the mirror URL doesn't contain "debianc", does it?
gTan64 said:
Look closely - the mirror URL doesn't contain "debianc", does it?
Click to expand...
Click to collapse
I'm F-ing retarded
/facepalm
-Edit- any packages you would advise to install?
New problem
Code:
[email protected]:/$ sudo chroot /media/79e9dd5a-174b-4324-a704-6aa06807fe35_
chroot: cannot run command `/bin/bash': Exec format error
Could it be because sudo apt-get install qemu-kvm-extras-static had no packages and I had to install sudo apt-get install qemu-kvm-extras
Code:
sudo cp /usr/bin/qemu-arm-static $ROOTFS/usr/bin/
This step is essential - without qemu-arm-static in your chroot, you won't be able to run/emulate any ARM binaries (in this case, Debian-armel's /bin/bash).
Yes, you do need the static version. Last I checked it was actually in the Ubuntu repositories, so look again...
As far as what packages to install, here you go.
Essential packages: xserver-xorg-{video-fbdev,input-{mouse,keyboard}}
Essential desktop packages (pick one): e17 fluxbox lxde xfce4
Recommended packages: cellwriter xfce4-goodies
Suggested packages: Whatever floats your boat.
Packages I installed even though having no sound makes them useless: zynaddsubfx supertux sopwith bomberclone
First of all, I need to give my thanks to great DevGhostofNet for his excellent work on getting Ubuntu 11.01 running on Xoom. I borrowed his template on this instruction page as I really don't have my template and using this way to show my appreciation to his work.
Second, I figured though I am not big dev by any means, hopefully any time I spent on such things can add some value to owners of either DS7 or Xoom, especially DS7, which really needs any effort on it in addition to testing help.
So I would throw in my two-cent hours/efforts to get this started. I see huge potential in it, though now it is quite WIP, because the non-graphical version is running well but not Gnome sessions.
1.What is working?
Shell Ubuntu 11.04
I modified the installation scripts to mount DS7 partitions correctly and copy some modified script into original image.
2. What is not working?
Gnome Session
I can install necessary components up to a point where the wall paper is loaded, sidebar is loaded but the guest system did not take/register input properly yet.
3. Why we care?
It has huge potential in it. It uses a part of your sdcard to run a guest system, and you can literally install all those great Ubuntu apps in it in future when more dev effort makes this happen.
4. What is the impact to my existing Android OS?
Minimal. The impacts are:
1. there will be ubuntu scripts in /system/bin/
2. Loop7 device will be borrowed while ubuntu is mounted.
3. under /sdcard, there is a folder ubuntu which pretty much contains everything
4. in LOST.DIR of your /sdcard, there may be lots of temp files if you experimented a lot of install/uninstall of this guest system.
If you still want to take a crack now.........
DISCLAIMER: I will not responsible for any bricked device. Please although this experiment won't affect your other files at all, but **** happens all the time, please do backup and understand what you are trying to do before proceed.
[Before Installation:]
1. You should know what you are doing at this step.
2. You have rooted your device already
3. You configured adb and have a terminal apps in your DS7. (Terminal apps can be found in market. Android Terminal seems to work fine)
4. You have a VNC client. (Android-vnc in market seems fine)
[Installation:]
1. Download the DS7Ubuntu files From my post at http://www.OpinionatedFool.com
2. Extract it into /sdcard/ubuntu folder
3. Open a terminal
Code:
su
cd /sdcard/ubuntu
sh ubuntu install
Just click yes when you are asked some questions. This process takes about 5 mins
reboot after installation
NOW after rebooting, you officially are running a text based Ubuntu 11.04
4. Open you terminal
Code:
su
ubuntu start
ubuntu shell
If you are interested to go further, I really encourage to because we need better devs to bring us further. I am willing to try more but it will take longer time as I have been away from Linux for a good 6 years.
5. After you are in Ubuntu Shell environment. you can do
Code:
vi /sbin/installubuntu
6. Inside installubuntu, the following are present:
Code:
#!/bin/sh
/usr/bin/apt-get -y -q update
/usr/bin/apt-get -y -q upgrade
/usr/bin/apt-get -y -q install python-software-properties
#/usr/bin/add-apt-repository ppa:unity-2d-team/unity-2d-daily
/usr/bin/apt-get -y -q update
/usr/bin/apt-get -y -q install tightvncserver xrdp
/usr/bin/apt-get -y -q install ca-certificates desktop-file-utils doc-base eog g
conf-editor gedit ghostscript-x gnome-about gnome-applets gnome-control-center g
nome-media gnome-menus gnome-nettool gnome-panel gnome-session gnome-session-can
berra gnome-system-monitor gnome-system-tools gnome-terminal gnome-themes-select
ed gnome-themes-ubuntu gnome-utils gtk2-engines gtk2-engines-pixbuf gucharmap hu
manity-icon-theme indicator-applet-session inputattach language-selector launchp
ad-integration lftp libgd2-xpm libgnome2-perl libpam-ck-connector libsasl2-modul
es libxp6 nautilus nautilus-sendto notify-osd rarian-compat screen smbclient sof
tware-center synaptic software-properties-gtk ttf-dejavu-core ttf-freefont ubunt
u-artwork ubuntu-extras-keyring ubuntu-sounds unzip update-manager update-notifi
er x-ttcidfont-conf xterm yelp zenity zip maximus
/usr/bin/dpkg-divert --local --rename --add /sbin/initctl
/bin/ln -s /bin/true /sbin/initctl
I am good up to completion of this step in the script above
Code:
/usr/bin/apt-get -y -q install tightvncserver xrdp
Then the following bulk apt-get process will cause issues. The main course is on gconf2 as far as I know.
I tried to install them separately after install gconf2, but it is not stably working.
i.e. sometimes I did install them all correctly, but sometimes I am getting segmentation error, which is annoying and requires wipe ubuntu folder and reinstall ubuntu.
I am too rusty on Linux now that better devs may figure it out easily.
[How to Uninstall it?]
In case you want to get rid of it. Here is how:
Through ADB or Terminal Simulator in your DS7
Code:
adb shell
su
mount -o remount,rw /dev/block/mmcblk3p3 /system
rm /system/bin/ubuntu*
mount -o remount,ro /dev/block/mmcblk3p3 /system
[Next Step]
Install and configure a working copy of Gnome-session on this successfully. Hopefully there will be Kernel Dev to have a Ubuntu kernel specifically for DS7? That will be the best.
We can then
1. Run Apache server and you will access your files through Dell Streak 7 as long as you are tethering in its own LAN. (or a lot more)
2. Run browsers in graphical version of Ubuntu on your DS7 so that you can do whatever with hulu or netflix or anything. Basically you are carrying a freaking DS7 laptop with you. with touch screen and huge mobility
[Notes]
1. pts need to mounted
2. use Unity-2d seems to be better than Unity
3. mtab need to be replace manually with the mtab I included in the zip file
4. kernel is not configured to have shared memory management ...
I'll definitely be following this thread with interest!
native ubuntu would be nicer rather than the crap of chrooted ones, they are just pointless IMHO as the device has to try and manage 2 oses at once, the 7 doesnt realy have the ram to manage that
Any updates on this project ?
Guess not :-(
Quick question to the op
Does wifi work so you can update / install packages?
If so, does it see the wifi cards chipset? I'm looking into getting aircrack-ng set up to tinker with. ( saves me from dragging out my laptop to test security on networks with my job )
Currently I'm using my Mac with kismac which does the job nicely , however, if I can use the ds7 under Ubuntu its one less reason to drag it along.
Can you copy the device information for me or does it act like a LAN card ?
Thanks !!
what is the latest development?
In a few weeks, i will tell my team to look at the cm7.1 things. I hope you will help us? I will send you a pm but remember me
ubuntu
is this still being worked on or attempted? or is there a ubuntu rom out already?
Is this anything like Ubuntu installer...
http://forum.xda-developers.com/showthread.php?t=1390351
After using webtop2sd app the next step on using my webtop on motorola atrix was to start using programs like aptitude, synaptic or command line apt-get to install much more useful programs to use offline on this motorola modified ubuntu jaunty distribution.
The first problem faced was that motorola had left a lot of broken dependencies that would break webtop system if someone just try to use any automatic solution.
To help on this task i developed a bash script that fix those broken dependencies using three different approaches:
1 - The first logical step is just install the missing packages from ubuntu jaunty, taking care to not overwrite any original packages developed from motorola
2 - Since some packages were made from motorola and were already installed on webtop, the second step was creating FAKE packages to just tell apt-get that the package is already installed leaving the original motorola installed package intacted.
3 - Somehow, there is one fake package that breaks the system if is installed. For this package, the idea was backup all files provided from the package developed from motorola and install ubuntu jaunty package overwriting motorola's files. After installation restore the original files on top of ubuntu jaunty files to maintain maximum motorola original system.
After fixing apt-get broken dependencies the use of apt-get could upgrade original motorola`s file. To avoid that there is another script that mark to HOLD version installed. Doing that, it is more difficult to normal users to upgrade packages that would overwrite motorola packages.
Now let's explain how to use WebTopScripts.
Requirements:
* Rooted Atrix.
* Working WebTop after webtop2sd modifications.
* webtop configurator running and preliminaries fix applied from this program (most of all corrections are related to sources.list).
* basic skills to run bash scripts and commands from terminal command line
* working lxterminal program on webtop
Install Script on your Atrix:
* Download file from this thread and save on your download folder (/mnt/sdcard/download)
* run these commands on lxterminal:
Until version 1.6:
Code:
cp /mnt/sdcard/download/webtopscripts-1.4.tar ~/
cd ~
sudo tar -xvf ~/webtopscripts-1.4.tar
sudo chmod -R 777 WebTopScripts
bash WebTopScripts/setup.sh
After version 1.7:
Code:
cp /mnt/sdcard/download/webtopscripts-1.7.tar ~/
cd ~
sudo tar -Pxvf ~/webtopscripts-1.7.tar
cd /osh/usr/share/
sudo chmod -R 777 WebTopScripts
bash WebTopScripts/setup.sh
Run Scripts to fix apt-get:
Until version 1.6:
Code:
cd ~
bash WebTopScripts/fix-apt-get.sh
After version 1.7 execute this command and choose options from menu:
Code:
webtopscripts
Just use this script with care, and at your own risk, because apt-get may break your system.
Using webtop2sd you may easily recover from original webtop but since your are on a rooted device all caution is needed.
Good luck and enjoy.
New repository for updated versions on: webtopscripts google code
Version 1.5 released 10/01/2012
Version 1.6 released 11/01/2012
Version 1.7 released 24/01/2012
Many thanks to donation made by:
amenditman
...
Please feel free to contribute on WebTopScripts Project on Google Code
Install script to help use of dpkg -i xx.deb command
If you want to use some functions provided from WebTopScrips to install packages directly from deb files like command "sudo /usr/bin/dpkg -i --root=/osh <<package_deb_file.deb>>", you may run the code:
Code:
cd ~
bash WebTopScripts/scripts/install.sh <<package_name>>
Just need to make sure to write proper settings on file:
Code:
cd ~
leafpad WebTopScripts/scripts/config.txt
Example of config.txt (You just need to include dependencies that are not on webtop yet) :
[gksu]
site="http://launchpadlibrarian.net/23917569/gksu_2.0.2-1ubuntu2_armel.deb"
file="gksu_2.0.2-1ubuntu2_armel.deb"
depends="libgksu2-0;gnome-keyring"
[libgksu2-0]
site="http://launchpadlibrarian.net/25028748/libgksu2-0_2.0.9-1ubuntu3_armel.deb"
file="libgksu2-0_2.0.9-1ubuntu3_armel.deb"
depends=""
[gnome-keyring]
site="http://launchpadlibrarian.net/25333836/gnome-keyring_2.26.1-0ubuntu1_armel.deb"
file="gnome-keyring_2.26.1-0ubuntu1_armel.deb"
depends="libgcr0;libgp11-0"
[libgcr0]
site="http://launchpadlibrarian.net/25333843/libgcr0_2.26.1-0ubuntu1_armel.deb"
file="libgcr0_2.26.1-0ubuntu1_armel.deb"
depends="libgp11-0"
[libgp11-0]
site="http://launchpadlibrarian.net/25333840/libgp11-0_2.26.1-0ubuntu1_armel.deb"
file="libgp11-0_2.26.1-0ubuntu1_armel.deb"
depends=""
Click to expand...
Click to collapse
To install gksu you just need to run:
Code:
cd ~
bash WebTopScripts/scripts/install.sh gksu
You may contribute with more config text for installing more packages on this thread to share with others users that do not want to use apt-get easy installation process.
Visit site bellow to find path for armel jaunty deb files on web:
https://launchpad.net/ubuntu/jaunty/armel/
Hope to have your contribution soon.
Programs Installed after apt-get fix from WebTopScripts
I will list here all applications that were installed and how I did it after fixing apt-get.
=== Reserved ===
You my friend, have to much time on your hands.
This is freaking wicked GOD like.
Thank you !
very nice I had been working on getting dependencies t work for days and kept breaking the webtop.
I've also been working on this for days and am happy to confirm it works beautifully!
May god carry your soul to heaven when you die.
I am now completely satisfied in replacing my netbook with the lapdock
im installing gnome desktop now =D
youre the man
I think I may have just died! Awesome job.
You make my day
Sent from my MB860 using XDA App
Thank you everybody that tested the script. My pleasure to help and contribute.
I need your help on this issue:
Sometimes when you are installing programs, the program is not able to configute itself.
I found oout that the main problem is that some programs modified by motorola are preventing that since they don't have all functionalities that are expected from them.
For example program readlink can not be used with option -q, program sed can not be used with some optins, etc....
To fix that the only way is to overwrite motorola file with ubuntu original jaunty file. BUT that sometimes breaks the system.
Here is your possible contribuition: to find out with me wich files can be overwriting without problems.
Here is an example to how to overwrite readlink:
Code:
cd ~
bash WebTopScripts/scripts/install.sh coreutils
rm -R ~/tmp
dpkg-deb -x WebTopScripts/packages/coreutils_6.10-6ubuntu1_armel.deb ~/tmp/
sudo cp ~/tmp/bin/readlink /usr/bin/readlink
To overwrite grep we need to include this package on WebTopScripts like this:
Code:
cd ~
sudo tee -a WebTopScripts/scripts/config.txt <<EOF
[grep]
site="http://launchpadlibrarian.net/[URL="tel:19665074"]19665074[/URL]/grep_2.5.3%7Edfsg-6ubuntu1_armel.deb"
file="grep_2.5.3~dfsg-6ubuntu1_armel.deb"
depends=""
EOF
bash WebTopScripts/scripts/install.sh grep
rm -R ~/tmp
dpkg-deb -x WebTopScripts/packages/grep_2.5.3~dfsg-6ubuntu1_armel.deb ~/tmp/
sudo cp ~/tmp/bin/grep /bin/grep
sudo cp ~/tmp/bin/egrep /bin/egrep
Finally, I am open to yours suggestions ....
This looks awesome! Can't wait to try it out today. has anyone installed a working chrome browser yet?
I am trying to find a working APT source for Jaunty to test against. Anyone have a working /etc/apt/sources.list I can use?
starrwulfe said:
I am trying to find a working APT source for Jaunty to test against. Anyone have a working /etc/apt/sources.list I can use?
Click to expand...
Click to collapse
Use WebTop2SD & install webtop configurator. It will fix your apt source and keys.
If you're more advanced than that and just want repo, check out old-releases.ubuntu.com as your starting fqdn.
bb12489 said:
This looks awesome! Can't wait to try it out today. has anyone installed a working chrome browser yet?
Click to expand...
Click to collapse
chromium ppa doesn't have jaunty binaries so this isn't possible. You might want to look at debian webtop for chromium.
_Alex_ said:
chromium ppa doesn't have jaunty binaries so this isn't possible. You might want to look at debian webtop for chromium.
Click to expand...
Click to collapse
yea i tried debian, but no one can get chrome to work on it. Displays pages for a second then craps out :/
aaron.a said:
im installing gnome desktop now =D
youre the man
Click to expand...
Click to collapse
did it work ???
Does any one have sources.list for any armel chromium? I had before for i386 one daily build that could work with jaunty since will not contains many dependencies on ubuntu stuff. But that was i386, i am not familiar with armel yet.
Sent from my MB860 using XDA App
this is outstanding. well done.
i am one of the many that seem to have been experimenting with this and constantly breaking it. i did find however, that overwriting most of the packages that contain binaries that were included in the original rootfs (coreutils, findutils, etc) helped fix missing arguments especially when trying to build from source using apt-get.
also force overwriting locales let you rebuild a locale for your own language and gets rid of errors and some awn-manager issues due to dependencies on the locale files.
but alas, my awn-launcher is broken so i am out of action for the time being.
arvati said:
Does any one have sources.list for any armel chromium? I had before for i386 one daily build that could work with jaunty since will not contains many dependencies on ubuntu stuff. But that was i386, i am not familiar with armel yet.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You can find and add PPA ubuntu sources from www.launchpad.net. Unfortunately, there are no armel jaunty binaries for Chromium stable, dev or beta available.
** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
**Download Link Updated to build 2020-07-10**
TL;DR:
This is a Clean, Stock LineageOS Build for Xiaomi Mi 9 (cepheus) that does NOT include any GApps, MicroG, or Signature Spoofing.
What you choose to add/modify after installing this ROM is entirely up to you.
All,
I wanted to distance myself from Google as much as possible, so I decided to build LineageOS from the source.
I used the LineageOS source they provide via GitHub, available here.
I also use the Proprietary Blobs for the Cepheus Device Tree from Demon000's GitHub, available here.
To get current version to build, I also needed to add the LineageOS/android_hardware_xiaomi source to my local manifest and use the repopicks Cozzymy13 includes in the OP of his ROM's thread. [Thanks k1l for and Cozzymy13 for pointing out these additions!]
The result is a stock build of LineageOS 17.1 for the Cepheus device. In the spirit of LineageOS, this does not include Signature Spoofing. You will need to use Xposed or some other method if you desire that functionality.
This also does not include MicroG or any other additional applications. This is pure LineageOS, built on 2020-07-10.
NanoDroid patcher works well for anyone who wants to add MicroG support. You will still need to use Xposed or similar if you want Signature Spoofing as NanoDroid does not offer a patch for Android 10 as of this build.
Feel free to provide download mirrors.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Flash lineage-17.1-20200710-UNOFFICIAL-cepheus.zip
3) Format Data (Wipe -> Format Data -> type "yes"
3b) - OPTIONAL - Flash Magisk Zip for Root
4) Reboot to system
Alternate Install Steps for Full MicroG with Signature Spoofing:
From TWRP:
1) Wipe Date (standard wipe)
2) Flash lineage-17.1-20200710-UNOFFICIAL-cepheus.zip
3) Format Data (Wipe -> Format Data -> type "yes"
3b) - OPTIONAL - Flash Magisk Zip for Root
4) Reboot to system (ignore any errors about missing Google Services)
5) Reboot to TWRP
6) Flash NanoDroid Patcher (either the Full package or you can customize per the instructions in the NanoIx link below)
7) Reboot
8) Install the Magisk Module for Xposed Framework and the EDXposed.ZIP as per the instructions in the Xposed link below)
9) Reboot to activate the new Module
10) Within the EDXposed App, Install the FakeGApps Module
11) Reboot to activate the new Module
As everything I really care about is working in this build, I do not plan to devote much, if any, time to "supporting" this release. I just thought I'd share my clean 17.1 LineageOS in case anyone else is interested.
Download:
LineageOS 17.1 Unofficial (Built: 2020-07-10) md5sum: 1c340fc16a6fbc7586d0a856acb9c600
NanoDroid Patcher (optional): NanoIx
Magisk Root (optional): Magisk
XPosed for Android 10 - Magisk Module (optional): Xposed
Just found a new bug:
Wireless Hotspot will not start.
Can anyone confirm if this is an issue with other LineageOS build for this device?
Messed around too much and had to re-flash. Afterwards, I could not get apps to register with MicroG Cloud Messaging, so some notifications were not working.
If anyone runs into this issue, just get a root shell and run this command:
Code:
adb shell
su
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546 --receiver-include-background
This will register the current user with Cloud Messaging. You can verify this works with the "Push Notification Tester" app in the Aurora Store.
This knowledge comes to you courtesy of lxp over on the MicroG Github
Using for 3 days now, and is working good, i don't use MicroG and no google apps. Nice work
Using it for second day, and everything seems fine, hotspot working too.
Only problem is with Revolut app which say it's incompatible app, are there any workaround?
Btw. Good job, thanks!
Simonell said:
Using it for second day, and everything seems fine, hotspot working too.
Only problem is with Revolut app which say it's incompatible app, are there any workaround?
Btw. Good job, thanks!
Click to expand...
Click to collapse
I'm not familiar with that App. Is it working on other AOSP-based ROMS?
It looks like Mobile Banking app. I don't have an account to really test; nor do I have the energy to try and troubleshoot individual apps.
Are you by chance running it on a rooted install? If you have rooted this ROM, that could be why you are having trouble with that Banking App. I know they tend to not like rooted phones.
I have been happy with this build since I compiled it on the 25th, but I may update and compile from current source. It I do, I can make it available for you to try.
Of course, if it is broken on other LineageOS builds, or if you are rooted, I would expect it to still complain on this build, too.
If you rooted with Magisk, there is a Magisk Hide option in the Magisk Manager app that may let you hide your root from that specific banking app.
photonmedia said:
I'm not familiar with that App. Is it working on other AOSP-based ROMS?
It looks like Mobile Banking app. I don't have an account to really test; nor do I have the energy to try and troubleshoot individual apps.
Are you by chance running it on a rooted install? If you have rooted this ROM, that could be why you are having trouble with that Banking App. I know they tend to not like rooted phones.
I have been happy with this build since I compiled it on the 25th, but I may update and compile from current source. It I do, I can make it available for you to try.
Of course, if it is broken on other LineageOS builds, or if you are rooted, I would expect it to still complain on this build, too.
If you rooted with Magisk, there is a Magisk Hide option in the Magisk Manager app that may let you hide your root from that specific banking app.
Click to expand...
Click to collapse
It's working after root and Hide in Magisk Manager. I was confused because it was showing up as "Incomaptible with device" in google play store, after rooting it's installed. Thanks!
Could you send commands which you used to compile ROM? I have some free space on my home server, maybe I could set up Jenkins with auto building. Is it possible to get auto update working?
Simonell said:
It's working after root and Hide in Magisk Manager. I was confused because it was showing up as "Incomaptible with device" in google play store, after rooting it's installed. Thanks!
Could you send commands which you used to compile ROM? I have some free space on my home server, maybe I could set up Jenkins with auto building. Is it possible to get auto update working?
Click to expand...
Click to collapse
ThePiGuy already has a great overview of building for unsupported/unofficial devices here
You'll need to install all the base requirements on your build distro before you proceed. This includes the adb and fastboot tools, the build packages, and the java versions as mentioned in this LineageOS build guide for one of their other Xiaomi "supported" devices.
What I post here is basically my method of pulling the relevant info from the two build guides above to get a successful build for the Xiaomi Mi 9 (cepheus).
I will say as for the Requirements, it really needs to be 16GB of RAM. I tried building in a VM with 8GB multiple times and it failed due to running out of memory. This could just be because I run on SSDs and do not use SWAP space/files...
When it comes to your Proprietary Blobs, I pulled mine from Demon000's Github Source
You will need these repos, and we will cover these steps further down:
vendor_xiaomi
kernel_xiaomi_sm8150
device_xiaomi_cepheus
device_xiaomi_sm8150_common
When performing the "ccache -M $G" command I used:
Code:
ccache -M 50G
Now let's create your base folder where you want to make all the magic happen. Be sure to have plenty of storage available. In my case, I needed about 200GB.
Code:
mkdir -p ~/android/lineage
cd ~/android/lineage
When performing your repo init commands, reference branch 17.1:
Code:
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
Sync the repo to your current working directory, in this case the lineage folder you created above (which should still be your working directory):
Code:
repo sync
This will pull down 100+GB of files, so this takes quite some time.
Following along, you should be in your folder called "lineage" where you ran your repo init and repo sync commands. In my case this is:
Code:
~/android/lineage/
Attached is my manifest file called "cepheus.xml" that references the Demon000 github source.
Place this cepheus.xml file here:
Code:
~/android/lineage/.repo/local_manifests/cepheus.xml
(creating the local_manifests folder if necessary)
Now you need to complete the build of your device tree.
You will clone each of the four repositories above into their respective locations in the device tree:
vendor_xiaomi -> ~/android/lineage/vendor/xiaomi/
kernel_xiaomi_sm8150 -> ~/android/lineage/kernel/xiaomi/sm8150
device_xiaomi_cepheus -> ~/android/lineage/device/xiaomi/cepheus
device_xiaomi_sm8150_common -> ~/android/lineage/device/sm8150_common
Note: Be sure to check each of those four locations and make sure the contents of the repository are in those folders, not, for example: ~/android/lineage/device/sm8150_common/device_xiaomi_sm8150_common. You don't want the repo contents within that extra subfolder...
In my case, I created the necessary directory structure and changed to that directory, then cloned the repo and moved the contents from the subfolder created by the clone operation into the correct location.
Code:
mkdir -p ~/android/lineage/vendor/xiaomi/
cd ~/android/lineage/vendor/xiaomi
git clone https://github.com/Demon000/vendor_xiaomi.git
mv vendor_xiaomi/* .
rm -r vendor_xiaomi
Code:
mkdir -p ~/android/lineage/kernel/xiaomi/sm8150
cd ~/android/lineage/kernel/xiaomi/sm8150
git clone https://github.com/Demon000/kernel_xiaomi_sm8150.git
mv kernel_xiaomi_sm8150/* .
rm -r kernel_xiaomi_sm8150
Code:
mkdir -p ~/android/lineage/device/xiaomi/cepheus
cd ~/android/lineage/device/xiaomi/cepheus
git clone https://github.com/Demon000/device_xiaomi_cepheus.git
mv device_xiaomi_cepheus/* .
rm -r device_xiaomi_cepheus
Code:
mkdir -p ~/android/lineage/device/xiaomi/sm8150_common
cd ~/android/lineage/device/xiaomi/sm8150_common
git clone https://github.com/Demon000/device_xiaomi_sm8150_common.git
mv device_xiaomi_sm8150_common/* .
rm -r device_xiaomi_sm8150_common
Now return to your base lineage folder:
Code:
cd ~/android/lineage
Now that you have init'd and synced your repo and pulled your proprietary blobs into their respective folders, you are ready to build with the brunch command:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
For me, I have no idea how long this took to complete as I left it running overnight. I would imaging at least 4 hours on my i5 device. Once it's done, you should have a TWRP-flashable zip and an OTA zip in the ~/android/lineage/out folder.
Note: If after compiling for some time, the process fails with errors, it should provide you with information on how to track down the error. In my case, I ended up with it stopping with a failure a couple times, but I just re-ran the above brunch command and it picked up where it left off, eventually completing successfully. YMMV
I'm sure there are cleaner, simpler ways of going about this, but I'm just getting my feet wet with current Android source. I haven't really done any sort of Android "development" since the days of KitKat...
photonmedia said:
ThePiGuy already has a great overview of building for unsupported/unofficial devices here
You'll need to install all the base requirements on your build distro before you proceed. This includes the adb and fastboot tools, the build packages, and the java versions as mentioned in this LineageOS build guide for one of their other Xiaomi "supported" devices.
What I post here is basically my method of pulling the relevant info from the two build guides above to get a successful build for the Xiaomi Mi 9 (cepheus).
I will say as for the Requirements, it really needs to be 16GB of RAM. I tried building in a VM with 8GB multiple times and it failed due to running out of memory. This could just be because I run on SSDs and do not use SWAP space/files...
When it comes to your Proprietary Blobs, I pulled mine from Demon000's Github Source
You will need these repos, and we will cover these steps further down:
vendor_xiaomi
kernel_xiaomi_sm8150
device_xiaomi_cepheus
device_xiaomi_sm8150_common
When performing the "ccache -M $G" command I used:
Code:
ccache -M 50G
Now let's create your base folder where you want to make all the magic happen. Be sure to have plenty of storage available. In my case, I needed about 200GB.
Code:
mkdir -p ~/android/lineage
cd ~/android/lineage
When performing your repo init commands, reference branch 17.1:
Code:
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
Sync the repo to your current working directory, in this case the lineage folder you created above (which should still be your working directory):
Code:
repo sync
This will pull down 100+GB of files, so this takes quite some time.
Following along, you should be in your folder called "lineage" where you ran your repo init and repo sync commands. In my case this is:
Code:
~/android/lineage/
Attached is my manifest file called "cepheus.xml" that references the Demon000 github source.
Place this cepheus.xml file here:
Code:
~/android/lineage/.repo/local_manifests/cepheus.xml
(creating the local_manifests folder if necessary)
Now you need to complete the build of your device tree.
You will clone each of the four repositories above into their respective locations in the device tree:
vendor_xiaomi -> ~/android/lineage/vendor/xiaomi/
kernel_xiaomi_sm8150 -> ~/android/lineage/kernel/xiaomi/sm8150
device_xiaomi_cepheus -> ~/android/lineage/device/xiaomi/cepheus
device_xiaomi_sm8150_common -> ~/android/lineage/device/sm8150_common
Note: Be sure to check each of those four locations and make sure the contents of the repository are in those folders, not, for example: ~/android/lineage/device/sm8150_common/device_xiaomi_sm8150_common. You don't want the repo contents within that extra subfolder...
In my case, I created the necessary directory structure and changed to that directory, then cloned the repo and moved the contents from the subfolder created by the clone operation into the correct location.
Code:
mkdir -p ~/android/lineage/vendor/xiaomi/
cd ~/android/lineage/vendor/xiaomi
git clone https://github.com/Demon000/vendor_xiaomi.git
mv vendor_xiaomi/* .
rm -r vendor_xiaomi
Code:
mkdir -p ~/android/lineage/kernel/xiaomi/sm8150
cd ~/android/lineage/kernel/xiaomi/sm8150
git clone https://github.com/Demon000/kernel_xiaomi_sm8150.git
mv kernel_xiaomi_sm8150/* .
rm -r kernel_xiaomi_sm8150
Code:
mkdir -p ~/android/lineage/device/xiaomi/cepheus
cd ~/android/lineage/device/xiaomi/cepheus
git clone https://github.com/Demon000/device_xiaomi_cepheus.git
mv device_xiaomi_cepheus/* .
rm -r device_xiaomi_cepheus
Code:
mkdir -p ~/android/lineage/device/xiaomi/sm8150_common
cd ~/android/lineage/device/xiaomi/sm8150_common
git clone https://github.com/Demon000/device_xiaomi_sm8150_common.git
mv device_xiaomi_sm8150_common/* .
rm -r device_xiaomi_sm8150_common
Now return to your base lineage folder:
Code:
cd ~/android/lineage
Now that you have init'd and synced your repo and pulled your proprietary blobs into their respective folders, you are ready to build with the brunch command:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
For me, I have no idea how long this took to complete as I left it running overnight. I would imaging at least 4 hours on my i5 device. Once it's done, you should have a TWRP-flashable zip and an OTA zip in the ~/android/lineage/out folder.
Note: If after compiling for some time, the process fails with errors, it should provide you with information on how to track down the error. In my case, I ended up with it stopping with a failure a couple times, but I just re-ran the above brunch command and it picked up where it left off, eventually completing successfully. YMMV
I'm sure there are cleaner, simpler ways of going about this, but I'm just getting my feet wet with current Android source. I haven't really done any sort of Android "development" since the days of KitKat...
Click to expand...
Click to collapse
Thanks! I will try this guide at the weekend, and post results
Simonell said:
Thanks! I will try this guide at the weekend, and post results
Click to expand...
Click to collapse
For what it's worth, I just successfully compiled an updated build today, but it fails to boot after flashing. Had to go back and flash my 2020-01-25 build from the OP.
YMMV
.
stock mi 9 camera works or not on this rom? because i don't raelly like gcam.
ahmadharith said:
stock mi 9 camera works or not on this rom? because i don't raelly like gcam.
Click to expand...
Click to collapse
I was able to install ANXCamera and their ANXCustLibsQ_160.DisloyalInnocentVelvetworm.zip Libraries and it works fine for me. Sometimes Portrait mode freezes, but I never use that anyway...
https://github.com/XEonAX/ANXCamera
us23heep said:
Hello friends!
Sorry my poor english. I am stuck 5 days with this error. Google cant answer. Please can you tell me if what I am doing wrong?
Error always say ... depends on undefined module
Try 1: pastebin.com/33nmpQLU
Try 2: pastebin.com/n3gxTXgY
Try 3: pastebin.com/7Lre4ZiF
Standard manifests:
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
local_manifests:
pastebin.com/kt4ES0d4
Thank you :good:
Click to expand...
Click to collapse
It seems like maybe it is not seeing some or all of the device tree files it needs. You may try manually downloading those device files an putting them in the appropriate folders as I mentioned I did in the steps I posted.
I built this yesterday using the instructions above... thanks a lot for those photonmedia!
Some of the instructions were wrong, ie a _ instead of a - in a dir name, but easy fixed.
After that, the entire build completed with 0 errors.
I didnt end up with a ZIP file though, just a approx 400MB "build-lineage_cepheus.ninja" file?
MWPau said:
I built this yesterday using the instructions above... thanks a lot for those photonmedia!
Some of the instructions were wrong, ie a _ instead of a - in a dir name, but easy fixed.
After that, the entire build completed with 0 errors.
I didnt end up with a ZIP file though, just a approx 400MB "build-lineage_cepheus.ninja" file?
Click to expand...
Click to collapse
did you first
Code:
breakfast cepheus
and then
Code:
brunch cepheus
?
the .zip is actually in the
/out/target/product/cepheus/ folder.
I did *exactly* as was instructed above...
Code:
cd ~/android/lineage
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
MWPau said:
I did *exactly* as was instructed above...
Code:
cd ~/android/lineage
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
Click to expand...
Click to collapse
My understanding is that the breakfast command is not necessary when you are building for unofficial devices and manually populating the necessary device tree files; you skip to the brunch step.
That is per the other guide I referenced in my instructions and how I was able to build this release.
I have not tried to pull and build an updated version as of this time.
k1l said:
the .zip is actually in the
/out/target/product/cepheus/ folder.
Click to expand...
Click to collapse
I missed this at the end of your reply :/
Yup, it's in there. Thanks
Code:
838M -rw-r--r-- 2 root root 838M Feb 25 01:31 lineage-17.1-20200224-UNOFFICIAL-cepheus.zip
photonmedia said:
For what it's worth, I just successfully compiled an updated build today, but it fails to boot after flashing. Had to go back and flash my 2020-01-25 build from the OP.
YMMV
Click to expand...
Click to collapse
Same for me. Have been trying to get it sorted the last few days, i dont know whats going on.
Original OP build works ok.