yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Q&A, Help & Troubleshooting] herojig:
Is it possible to turn the screen KB off somehow, when using my phablet with a keyboard attached. So annoying eh? Also, what's up with Swiftkey not playing well with BT keyboard... it dunna like. Well, thx!
[Galaxy Note II Q&A, Help & Troubleshooting] AA1973:
Wrong forum. TL;DR

7100 ≠ 7000
[Ubuntu Touch Ports to Android] MikeCriggs:
Ubuntu Touch Device Port Support Thread

Get Started Here: https://wiki.ubuntu.com/Touch/Porting

General Guidelines of This Thread

| (PLEASE READ BEFORE POSTING)

[*]Use the "search" tool and Google before asking questions.

[*]Please use www.pastebin.com or the "hide" BB tags for large blocks of code.

[*]Post ADB Logcats if you can.

[*]THIS IS

NOT

A PORT REQUEST THREAD,

DO NOT ASK FOR PORTS TO YOUR DEVICE!

[*]Be courteous to fellow members.

[*]Everyone was a noob at some point, so do NOT flame in this thread.

[*]Don't just share your problems, share your knowledge of work-arounds and bug fixes.

[*]Don't forget to hit the "thanks" button when someone has helped you, even if they tried and couldn't.

[*]Keep unrelated discussions to a minimum.

I will help out where I can, but I personally own a Nexus device, so I don't have to port :P. Although, I do have experience in porting, compiling, building, and troubleshooting Android ROMs.
[Ubuntu Touch Ports to Android] mrtain:
It's Up!

The porting guide has now been posted on the above link!
[Ubuntu Touch Ports to Android] Tigrouzen:
Its look's chrooted im right ?
[Ubuntu Touch Ports to Android] tillum:
Re: [DEV ONLY] Porting to Your Device

Far as I can tell. The Ubuntu file system is running in a container on top of a very basic android. Clever way to do it.
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

It's actually very easy to port this to just about any device that has CM 10.1. In fact, you don't even need to worry about Dalvik because there is none :).
[Ubuntu Touch Ports to Android] mufti.arfan:
Re: [DEV ONLY] Porting to Your Device

So any device not supporting CM can't have Ubuntu OS?
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

It can, but it's just not as easy to port.
[Ubuntu Touch Ports to Android] mufti.arfan:
Re: [DEV ONLY] Porting to Your Device

Hmmmm true.... will need much effort then..
[Ubuntu Touch Ports to Android] jaestreetss:
Re: [DEV ONLY] Porting to Your Device

We need a port for the n4.

I ran the preview on my phone and I was liking it
[Ubuntu Touch Ports to Android] Darktitor:
Re: [DEV ONLY] Porting to Your Device

Can the ZTE Blade running Ubuntu OS ??

It has a CM10.1 base but it's an arm v6 or v5 I've forgotten XD

Envoyé depuis mon eeepc avec Tapatalk
[Ubuntu Touch Ports to Android] TingTingin:
Re: [DEV ONLY] Porting to Your Device

Armv6 is a tough mountain to climb and even if it is done some apps won't work

PHONE SLOW CLICK ME?

_____________________________________

"If your doing the right thing then to hell with everyone else -Deadly"​
[Ubuntu Touch Ports to Android] coderzs:
Re: [DEV ONLY] Porting to Your Device

I have modifided kernel for ubuntu touch .. What is next ? Can i use cm10.1 what i have builded 6 days ago ? Or need rebuild it with ubuntu sources ?
[Ubuntu Touch Ports to Android] Darktitor:
Re: [DEV ONLY] Porting to Your Device

OK so It's not possible :(

Envoyé depuis mon eeepc avec Tapatalk
[Ubuntu Touch Ports to Android] TingTingin:
Re: [DEV ONLY] Porting to Your Device

I'm not saying that am just saying it will require alot of work for a small pay off :)

PHONE SLOW CLICK ME?

_____________________________________

"If your doing the right thing then to hell with everyone else -Deadly"​
[Ubuntu Touch Ports to Android] Darktitor:
Re: [DEV ONLY] Porting to Your Device

OK It's for a friend XD

Me I have a Galaxy SL i9003.

I'm waiting a CM10.1 port

Envoyé depuis mon eeepc avec Tapatalk
[Ubuntu Touch Ports to Android] TingTingin:
Re: [DEV ONLY] Porting to Your Device

:eek: lol

PHONE SLOW CLICK ME?

_____________________________________

"If your doing the right thing then to hell with everyone else -Deadly"​
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

I'm sure it could, but Ubuntu doesn't officially support Arm v6 or v5.
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

You will need the Ubuntu sources, CM 10.1 source for your device, proprietary blobs and vendor files, and to read the guide :p.

I want to attempt a Galaxy Note (GT-N7000) or Galaxy S3 port (SGH-I747 & GT-I9300 I believe might be the unlocked model number), but I'd need testers because as I've sold all of my devices but my Galaxy Nexus.

If anyone is interested, please feel free to PM me.
[Ubuntu Touch Ports to Android] tillum:
Re: [DEV ONLY] Porting to Your Device

Awesome. Have pm'd you. Looking forward to getting this running on my GT-N7000
[Ubuntu Touch Ports to Android] Akhilender:
Re: [DEV ONLY] Porting to Your Device

Is it possible to port ubantu for Htc explorer?
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

If it has CM 10.1
[Ubuntu Touch Ports to Android] TingTingin:
Re: [DEV ONLY] Porting to Your Device

We can't say unless someone tries to port it we are not psychic also is that phone armv6 is so then forget about it ubuntu doesn't support it which means the dev will have two mountains to climb and you'll have problems with apps

PHONE SLOW CLICK ME?

_____________________________________

"If your doing the right thing then to hell with everyone else -Deadly"​
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

I'm afraid that's true or I would be running 12.10 on my Raspberry Pi.
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

I will be making another thread for the N7000 port tomorrow when I start it. I have a few testers so far. If you're interested contact me via PM or preferably GTalk at michael.s.corigliano@gmail.com
[Ubuntu Touch Ports to Android] Akhilender:
Re: [DEV ONLY] Porting to Your Device

It's arm v7 and also there is cm10.1 though not stable.. S-off is required for that??
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

You would probably need a fully unlocked bootloader in order to overwrite certain protected partitions. I think s-off would be necessary on most HTC devices.
[Ubuntu Touch Ports to Android] ssDen_lol:
Hey guys. I have problem with compile Ubuntu Touch on my i9300.

make: *** No rule to make target `/home/ssden_lol/UTouch/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp',
needed by `/home/ssden_lol/UTouch/out/target/common/obj/APPS/GalaxyS3Settings_intermediates/src/R.stamp'. Stop.

Google can't help me.

Help me plz.
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DEV ONLY] Porting to Your Device

Post removed.
[Ubuntu Touch Ports to Android] TToivanen:
Re: [DEV ONLY] Porting to Your Device

Galaxys3settings is trying to get built even though it is a dalvik app. Delete everything mentioning it in makefiles.
[Ubuntu Touch Ports to Android] JDAapps:
Re: [DEV ONLY] Porting to Your Device

Unlocked bootloader for sure, but not sure why s-off would be required?? I saw a thread for flashing UTouch in Windows were boot and recovery were loaded through fastboot ... that works fine with s-on.
[Ubuntu Touch Ports to Android] darkkham:
In the ubuntu touch porting guide, it's specified that parts of cm10.1 of the candidate phone, are needed to build the port.

For a Samsung Galaxy S2 i9100 port, It's possible, instead of CM 10.1 parts, to use original available samsung sources ?
[Ubuntu Touch Ports to Android] f69m:
Re: [DEV ONLY] Porting to Your Device

Well, anything is possible! :P

Honestly, use the Ubuntu Git repositories that have part of CM sources with some modifications, together with the CM packages for your device as a starting point.

Anything else would probably be much more work. Very much. But not impossible. ;)

Edit: Actually, using different Kernel sources should not be a big headache. As long as it is just the Kernel and works with the CM device port.
[Ubuntu Touch Ports to Android] darkkham:
It's simply because i9100 haven't a good enough CM 10.1 and if components needed by ubuntu touch, are inside the samsung source too, it would be surely better... for now that ubuntu touch is in preview.
[Ubuntu Touch Ports to Android] Roundtableprez:
Re: [DEV ONLY] Porting to Your Device

If you take a crack at the HTC one s id be willing to test :D
[Ubuntu Touch Ports to Android] iksel:
HTC

Desire S Ubuntu proud tester is here :)
[Ubuntu Touch Ports to Android] skyFx:
fatal: unable to connect to phablet.ubuntu.com

does anybody get similar errors?

root@ubuntu:/home/skyfx# phablet-dev-bootstrap -c ./a700

INFO: phablet-dev-bootstrap:Changing to workdir /home/skyfx/a700

INFO: phablet-dev-bootstrap:Initializing repository

fatal: unable to connect to phablet.ubuntu.com:

phablet.ubuntu.com[0: 91.189.95.18]: errno=Connection refused
[Ubuntu Touch Ports to Android] rycus86:
Syncing the repo is a pain in the ass...

Keep trying until the process finish without errors.

Also: try pinging phablet.ubuntu.com just in case :)
[Ubuntu Touch Ports to Android] El Aero:
Hi, did manage to port Ubuntu Touch to HTC Desire S? Great! :good: Could you please share the image files so Saga owner could test is as well? IIt would be nice:o
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

Tell me about it... Especially after wiping your HD and syncing for the first time. There's over 10GB of source for AOSP alone. That's a lot of bandwidth and a lot of time.
[Ubuntu Touch Ports to Android] astronfestmon:
Re: [DISCUSSION] Porting to Your Device

Trying to port for mediacom 907c allwinner a10. I have one. Trying....
[Ubuntu Touch Ports to Android] TingTingin:
Re: [DISCUSSION] Porting to Your Device

List of ports

http://xdaforums.com/showthread.php?p=38468700

PHONE SLOW CLICK ME?

_____________________________________

"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"​
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

Thanks Ting. You're one of the most helpful people in this forum :).
[Ubuntu Touch Ports to Android] astronfestmon:
Re: [DISCUSSION] Porting to Your Device

I've got almost compiling for softwinner 907.
[Ubuntu Touch Ports to Android] astronfestmon:
Re: [DISCUSSION] Porting to Your Device

I'm facing a make error stopped by unfinished process build.

Android cm907 compiling.

What is happening?

Someone could help me?
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

Post your output?
[Ubuntu Touch Ports to Android] JunDavis:
Re: [DISCUSSION] Porting to Your Device

Can't decide if to port to Optimus 3D or Xperia Play. T.T

Edit: Optimus Would probably be easier
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

I'm sure it'd be a lot easier. Just don't expect 3D to work :p.
[Ubuntu Touch Ports to Android] fopoku2k2:
Re: [DISCUSSION] Porting to Your Device

Thanks, but there's no link for S3 i9300 port. Kindly update.

---------- Post added at 12:13 PM ---------- Previous post was at 12:06 PM ----------

Thanks, but there's no link for S3 i9300 port. Kindly update.
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

Look at the ports page on Ubuntu's site.
[Ubuntu Touch Ports to Android] El Aero:
Hi everyone!

I'm trying to port Ubuntu Touch to HTC Desire S (saga). When I command

it crashes with this:

What does it mean? What should I do to fix it? Please help.
[Ubuntu Touch Ports to Android] PVL_93_RU:
Re: [DISCUSSION] Porting to Your Device

IMO - Desire S is not capable of running Ubuntu
[Ubuntu Touch Ports to Android] El Aero:
Why not? It has all needed perositories) More than that even HTC Desire (Vision) can run Ubuntu Touch
[Ubuntu Touch Ports to Android] PVL_93_RU:
Re: [DISCUSSION] Porting to Your Device

And judging by reports - it lags like hell
[Ubuntu Touch Ports to Android] hell_lock:
What are the minimum requirements for making it run?
[Ubuntu Touch Ports to Android] PVL_93_RU:
Re: [DISCUSSION] Porting to Your Device

They are listed on Ubuntu Touch official site
[Ubuntu Touch Ports to Android] TingTingin:
Re: [DISCUSSION] Porting to Your Device

Wait u thinking about porting it? If so there aren't really any requirements u can check the post on my Sig (if you're on pc) to see what I mean the only real benchmark is that it's based on cm 10.1 source so if you can run cm 10.1 that's not to say you can't do it without cm 10.1 but it will be tough also this OS doesn't have armv6 compatibility so it would be very difficult to port to our phone

PHONE SLOW CLICK ME?

_____________________________________

"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"​

---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------

The official operating system also lags like hell so successful port

PHONE SLOW CLICK ME?

_____________________________________

"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"​
[Ubuntu Touch Ports to Android] El Aero:
http://xdaforums.com/showpost.php?p=38752407&postcount=26

Fisrt build for Saga. almost nothing works)
[Ubuntu Touch Ports to Android] hell_lock:
Re: [DISCUSSION] Porting to Your Device

I am doing it for my desire X.
[Ubuntu Touch Ports to Android] PVL_93_RU:
Re: [DISCUSSION] Porting to Your Device

That's good, Desire X seems to get no love from developers whatsoever. Even no CyanogenMod for that pretty device!
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

Have you set up your local_manifest.xml correctly?
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

This is to be expected. Especially on HTC devices.
[Ubuntu Touch Ports to Android] jabza:
repo sync error

Hi all. I'm working on porting Ubuntu Touch for the Samsung Infuse 4G, and I'm not particularly far. Currently, I'm running into an issue. When I enter the command repo sync, terminal returns this error:

Fetching projects: 13% (19/141) fatal: Couldn't find remote ref refs/heads/phablet-10.1
fatal: Couldn't find remote ref refs/heads/phablet-10.1
error: Cannot fetch scotthartbti/android_device_samsung_infuse4g

The last part, the error on fetching scotthartbti/android_device_samsung_infuse4g is becuase CM10.1 is working through his port, and thats scott.hart.bti's source code. Can anyone provide some insight on either of those errors?
[Ubuntu Touch Ports to Android] JDAapps:
Looks like your manifest is not correct. It is saying that it cannot find the project's remote using the path(refs) you've assigned in your manifest.

Without seeing what you have, it's hard to say what is wrong about it, but re-review the Touch porting guide section 'Enabling a new device', as that gives you insight and example as to how to correctly add your device-specific parts to the manifest.
[Ubuntu Touch Ports to Android] jabza:
repo sync error

I see. I left the default manifest.xml as it was, and then I created local_manifest.xml in the same folder. Heres the content:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com" />

<project path="device/samsung/infuse4g" name="scotthartbti/android_device_samsung_infuse4g" remote="github" />
<project path="kernel/samsung/infuse4g" name="scotthartbti/cm_samsung_kernel_dempsey" remote="github" />

<project path="kernel/samsung/dempsey" name="CyanogenMod/android_kernel_samsung_dempsey" remote="github" revision="refs/heads/cm-10.1" />
<project path="packages/apps/SamsungServiceMode" name="CyanogenMod/android_packages_apps_SamsungServiceMode" remote="github" revision="refs/heads/cm-10.1" />
<project path="device/samsung/aries-common" name="CyanogenMod/android_device_samsung_aries-common" remote="github" revision="refs/heads/cm-10.1" />
</manifest>

The first two are the device and kernel source from scott.hart.bti's Unofficial CM 10.1 ROM for the Infuse. The second bunch is the dependencies listed in his cm.dependencies file.
[Ubuntu Touch Ports to Android] JDAapps:
Looks to me like you need to define what revision (branch/tag) to use for the first two, as since it doesn't see this, it's falling back to default of phablet.
[Ubuntu Touch Ports to Android] leerpsp:
Re: [DISCUSSION] Porting to Your Device

Im going to try and work on porting this to the ideapad k1 i have not ever made a rom and dont know how but im going to try and have a go at it and by the looks of it if i dont try porting it for the k1 then we will not ever see one. They even stoped updating there roms and making roms for this on xda so i hope i can port this.
[Ubuntu Touch Ports to Android] fabioio:
I've followed the guide to build ubuntu for the s3(i9300) but i haven't all the knowledges to compile it..

i was wondering if someone can explain me what i'm supposed to do in this two parts of the guide

sorry for the noob question..
[Ubuntu Touch Ports to Android] EtherealRemnant:
Well I guess I'm going to get my hands dirty and work on a d2tmo build. Here comes a long sleepless night! lol

EDIT: One of these days I'll get around to updating my signature and location :P

EDIT2: I am learning a lot about git, I'll tell you that!
[Ubuntu Touch Ports to Android] EtherealRemnant:
Alright, I'm hung up now. I have done everything and gotten everything set up but when I tell it to build d2tmo, it fails on this:

make: *** No rule to make target `/home/kinetik/ubuntu/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp', needed by `/home/kinetik/ubuntu/out/target/common/obj/APPS/GalaxyS3Settings_intermediates/src/R.stamp'. Stop.

Any ideas? I've come so close!
[Ubuntu Touch Ports to Android] alroger:
R.stamp and building p1.

I've been able to get around that by removing P1Parts from device/samsung/p1-common/device_base.mk. I've read somewhere that it's trying to build an apk or some java which will not be used. P1Parts is basically the settins part of CM10.1 for the Galaxy Tab 7 #sgt7 model #p1.

I have a sucessfull build. It boots, showing kernel boot progress line and shuts down at the end. snif snif. Right at the end I can actually adb shell in for a sec before it shuts down.

Any ideas? Any tips on debuging what's being executed, or any log files I can check? In CwM I can adb shell in and even ubuntu_chroot shell.
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

You should be able to logcat if you're able to get in to ADB.
[Ubuntu Touch Ports to Android] f69m:
Re: [DISCUSSION] Porting to Your Device

You need to remove all Java targets from your device package.

Java is not included in the "tiny" Android base used by Ubuntu Touch, so the Java projects won't build and won't be used anyhow.

It is as simple as going through the *.mk files in your device/XXXX/YYYY directory and remove the respective lines.
[Ubuntu Touch Ports to Android] mr.nou:
Re: [DISCUSSION] Porting to Your Device

Anyone works it on xperia ray?
[Ubuntu Touch Ports to Android] alroger:
Nope. As I said it only conneted for a fraction of a second. adb logcat never gets a chance to run. Tab just shuts down.
[Ubuntu Touch Ports to Android] alroger:
f69m, how can you tell which are Java targets and which are not?
[Ubuntu Touch Ports to Android] MikeCriggs:
Re: [DISCUSSION] Porting to Your Device

Well that's unfortunate :/.
[Ubuntu Touch Ports to Android] stealthnoodle:
Re: [DISCUSSION] Porting to Your Device

I'm facing a similar issue for the HTC one S, except I've got it to boot to a black screen and stays on like that (have to hold power to turn off), that's all i know ATM seeing it finished compiling last night and i copy'ed the files and went on to work this morning
[Ubuntu Touch Ports to Android] hell_lock:
Re: [DISCUSSION] Porting to Your Device

What's the size of sources ?
[Ubuntu Touch Ports to Android] TingTingin:
Re: [DISCUSSION] Porting to Your Device

Like 6-700mb

S4 INFO
[Ubuntu Touch Ports to Android] f69m:
Re: [DISCUSSION] Porting to Your Device

Sorry for the late answer.

Well, there is no general way to tell from the module name, unless it contains something like "jni".

A good hint is, if the corresponding subdir contains *.java files. :P

If you are not familiar with the source for your device or with the Android build system, probably the best way to go ahead is to disable those modules that give compilation errors. Complaining about issues with R.* is sure to be a Java Android app and can be disabled.

Sorry that I am not more specific, but the CM device packages differ quite a lot and I don't know yours.
[Ubuntu Touch Ports to Android] JunDavis:
Re: [DISCUSSION] Porting to Your Device

Anyone know which preinstalled package I should use?

That points to kernel issues. Major :P
[Ubuntu Touch Ports to Android] moocow1452:
Is this the DEV troubleshooting thread? Because I've been trying to port Touch to my Nook Color, and the repo sync doesn't seem to play nice when I add bn/encore to the list of projects at the end of the file from CyanogenMod or NookieDevs. Is it a little more involved?
[Ubuntu Touch Ports to Android] JunDavis:
Re: [DISCUSSION] Porting to Your Device

Explain a bit more please
[Ubuntu Touch Ports to Android] moocow1452:
So far, I've been trying to port Touch to the Nook Color, and while I can import NookieDevs/android_device_bn_encore as per the manifest.xml just fine with the "refs/heads/cm10.1" flag as the revision, I have not be able to procure the kernel the same way, doing for now with just the latest git clone from steven676/ti-omap-encore-kernel3 and dropping it where it should be.

With that done, I've worked my way down to tracking down the Fstab and starting the kernel mods, but I was wondering, what would I need to get the manifest.xml to recognize the kernel git as is. Presumably, it has something to do with the revision, since that specific kernel doesn't have differenations between cm10.1 and jellybean, so how can I specify the one that the project agrees with?

EDIT: Now that I'm picking kernels, there's one named encore_cm10.1_config and one that's encore_cm_config among a whole lot of others, should I just patch both with the Ubuntu kernel patches, or is there a way to make sure I got the right one?
[Ubuntu Touch Ports to Android] JunDavis:
Re: [DISCUSSION] Porting to Your Device

I would patch both to be safe.
[Ubuntu Touch Ports to Android] moocow1452:
Done and done. Now if I'm reading this right, all I need to do is somehow get brunch to recognise encore as a valid build target, as what I have so far gives me...

make: *** No rule to make target `/home/user/Nook/out/host/linux-x86/bin/mkimage', needed by `/home/user/Nook/out/target/product/encore/ramdisk.ub'. Stop.
make: *** Waiting for unfinished jobs....

Any ideas on what the magic words are?
[Ubuntu Touch Ports to Android] alroger:
Don't mind me if I'm being too obvious... but have you been able to build your ROM/kernel for your device, before trying it into Ubuntu? First step before all.

Another thing, for my Tab all CyanogenMod repo refs are "cm-10.1" not just "cm10.1", not sure about yours. And about the manifest, once you are able to build your own ROM successfully, look into your local manifest, roomservice.xml and you should have the correct lines to copy from there.

My tab CM does not have a fstab to play with, and looking into the code and the actual partitions I see that it already is mounted without nosuid.

Just my 2 cents, since I'm still unable to boot my experiments.
[Ubuntu Touch Ports to Android] moocow1452:
Looking to run before I walk, thinking that if I can get it to build, I can iron out anything else with no sweat since the Nook has a boot from SD option and local installs I can choose from. Anyway, how can I add encore to the specialized brunch command for Ubuntu?