[Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N7000

eagleofdeath13

Senior Member
Dec 16, 2010
871
142
0
Which means we will never have a working port for the note!!

Or how precisely do u expect to compel Samsung to release it?

Since its all about Samsung releasing sources for a phone that's 2years old

But then again, CyanogenMod didn't seem to need Samsung's rild to get the radios to work

Sent from my GT-N7000 using xda premium
So??

What's up with ubuntu touch?

Sent from my GT-N7000 using xda premium
Do you have the rild sources? You have your answer ...
 
  • Like
Reactions: projeto56

SS

Member
Feb 16, 2005
11
0
0
I think this has some people hopeful that there may be a way around it.. If anyone could clarify this it would sure answer some questions..

Lol^^^^^ you know the drill.


Incidentally this was what I was told on the mailing list.:



On Sun, Jun 2, 2013 at 3:37 AM,* wrote:

> In addition I would like to clarify if ports now have working gsm too and if

> not, will they ever have?

>

> Accurate information is becoming an issue for the public because there are

> large gaps and huge expectations.

>

> For instance there is talk about lots of Samsung phones that supposedly will

> never get radio working without sources from Samsung. And precisely how

> anyone will get those from Samsung is unclear considering some of those

> devices are two years old and Samsung had not released them.

>

> It would be weird to eventually find out only nexus and dedicated hardware

> will run touch.


We don't necessarily need the sources here, as we're using the Android

RIL to talk with the modem. As long your device supports a recent

Android version (e.g. CM10.1), you should be good (unless there are

specifics that needs to be done for your hardware).


We're working with the Nexus family because it's easily from a

developer perspective, but nothing blocks us from using a different

hardware.


Also, remember that Galaxy Nexus uses a Samsung based hardware and modem.


--

Ricardo Salveti de Araujo

Clearly somebody somewhere don't know what they are talking about or are plain out just lying.
Either way no big deal. Its normal





Sent from my GT-N7000 using xda premium
 

bbfox59

Member
Feb 22, 2011
25
35
0
I think it would be portable the day that the rild source will not necessarly be patched (the patch used on the rild src is just for disable some credentials that ubuntu touch can't handle so it is possible to think that, one day, the source wouldn't need anymore to be patched).

That's what I think, if someone know that I tell something not true be free to correct me ;)

Kind regards,

Sent from my GT-N7000 using xda app-developers app
 

4llerbuntu

Senior Member
Jun 12, 2011
406
51
58
No use bumping this thread until changes are made to the way Ubuntu is built.

Sit there and wait. When something new happens Gerrett will let you now.

Sent from my GT-N7000 using Tapatalk 4 Beta
hot from the dev mailing list is the following:

hi,

It was often claimed that due to the fact that Ubuntu runs in a chroot
under android this just makes it another "android shell" ... i can
assure you this isn't the case anymore, since as of today we have
switched to a new image model !

Instead of booting into android and firing up the Ubuntu system after
android has booted, the new images now boot into Ubuntu and initialize
android inside an LXC container during boot.

so here now comes the official announcement of what we call the "Flipped
Ubuntu Touch Image"

############################################################

Announcing the flipped images as default.

The images are not necessarily in the same state as the traditional one,
but we believe it's good enough already for us to flip it by default,
and move forward just fixing and improving the flipped scenario (which
matches our desired architecture).

What does "flipped container" mean anyway?

The legacy Ubuntu Touch images run Ubuntu inside a chroot on top of
android. For the flipped model we are instead booting directly into
Ubuntu and then start up android inside an LXC container before starting
any services/applications.
Currently we're providing images for maguro, mako, manta and grouper,
and all are tested and known to work.

The daily builds of container flipped Ubuntu Touch images can be found
at http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/

We run adbd on the Ubuntu side, so you will be able to use the "adb
shell" command from your PC to get into the running system.

Before flashing the latest flipped image, make sure you have the latest
version of phablet-flash installed (version 0.14daily13.06.22-0ubuntu1).
You can still flash the legacy images by using the new argument
'--legacy'.

Useful commands after flashing the image:
Getting info about the container: lxc-info -n android
- This will tell you if the container is actually running
and where you can find it (/proc/$pid is usually the
namespace where lxc puts it)

Android container access: android-chroot
- As the name suggests this will give you chroot access
into the android container.

Modifying android:
if you want to i.e. change the services that get started by default you
can do the following:
$ cp /var/lib/lxc/android/rootfs/init.rc /var/lib/lxc/android/overrides/

Now you can edit /var/lib/lxc/android/overrides/init.rc to your liking
(i.e. to prevent surfaceflinger from starting because you work on Mir
you would delete all surfaceflinger related blocks in there).

Using androids adbd instead of ubuntus:
By default adbd running in the Ubuntu rootfs will use usb, and as we
can't have both running at the same time, it's just easier to force the
Android one to start over tcp.

To access the Android adbd via tcp:
At your host:
$ adb forward tcp:5555 tcp:5555

Then start Android's adbd over tcp, in the target:
$ sudo setprop service.adb.tcp.port 5555

And then at your host just connect and use adb shell:
$ adb connect localhost:5555
$ adb -s localhost:5555 shell

Community Ports

We hope to have an updated detailed tutorial explaining how to port your
device to the new flipped model later this week, so if you're a porter,
stay tunned!

For known issues and bugs, please make sure to check
https://bugs.launchpad.net/touch-preview-images/+bugs?orderby=-id&start=0.

If you have any further questions, feel free to post any question in the
#ubuntu-touch channel on irc.freenode.net (or by replying this email).

ciao
oli
BUT THEN ALL THIS IS OVER MY HEAD ANYWAY
 

projeto56

Senior Member
Apr 8, 2011
1,603
567
0
29
Boituva - SP
hot from the dev mailing list is the following:



BUT THEN ALL THIS IS OVER MY HEAD ANYWAY
I meant radio-related modifications. So we wouldn't need the sources to built a modified radio version to use phone and 3g functionality on Ubuntu.

When those modifications come in we will have a usable (barely perhaps) rom.

Till then, stop posting useless info, as probably who is interested in building Ubuntu already have the same message on their emails.
 
  • Like
Reactions: Gerrett and teraxul

4llerbuntu

Senior Member
Jun 12, 2011
406
51
58
Sorry i have to bump this one more time.

Forgive me in advance. :)

I saw this on the mailing list. Which portion does our devicr fall on?.

Im just trying to decide if i should simply sell off this phone now and not wait in vain.

Some older Android phones may have shipped with a fully binary RILD, as opposed to the newer phones which combine a binary vendor library with an open-source wrapper ( in the AOSP tree, see /hardware/ril/libril/ril.cpp ). As our project was originally started using ICS, we assume the newer RILD model, and as such, we patch ril.cpp to remove the socket credential check.

This check is performed by libril asking for the socket credentials of the remote process, then calling getpwuid() to get the matching username. If the username returned isn't "radio", then the socket is closed. Game over.
Sent from my GT-N7000 using xda premium
 
A

AndroidSlave

Guest
Sorry i have to bump this one more time.

Forgive me in advance. :)

I saw this on the mailing list. Which portion does our devicr fall on?.

Im just trying to decide if i should simply sell off this phone now and not wait in vain.



Sent from my GT-N7000 using xda premium
Honestly you're going to sell your device solely because Ubuntu touch has issues with rild?

Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
 

4llerbuntu

Senior Member
Jun 12, 2011
406
51
58
Yes actually.

I am fully invested in the ubuntu ecosystem and i intend to switch to touch immediately v 1.0 is released.

I cannot get to buy a nexus in my country at least not at prices that make any sense so i need a device that can run touch.

Iv held on to this Note simply because it seems to be a great device to use touch on at least at the initial stages up till 14.04 but if its not gonna happen......


I guess u guys really have to forgive my intrusions but my point is clear.



Sent from my GT-N7000 using xda premium
 
A

AndroidSlave

Guest
Yes actually.

I am fully invested in the ubuntu ecosystem and i intend to switch to touch immediately v 1.0 is released.

I cannot get to buy a nexus in my country at least not at prices that make any sense so i need a device that can run touch.

Iv held on to this Note simply because it seems to be a great device to use touch on at least at the initial stages up till 14.04 but if its not gonna happen......


I guess u guys really have to forgive my intrusions but my point is clear.



Sent from my GT-N7000 using xda premium
I hear you man... I didn't know it was so important to you...

Sent from my ME301T using Tapatalk 2