yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] murattiy:
relax julle131... i dont have pc... i want solution for recovery ... maybe easy it packet for u ???... but i dont know
[Galaxy S II Android Development] abtekk:
You need a PC.
[Galaxy S II Android Development] murattiy:
impossible recovery zip ?
[Galaxy S II Android Development] MaxWallstedt:
It's just as the OP says:

- install CyanogenMod (if not already installed, make sure it's working)

- wipe data/factory reset

- flash saucy-preinstalled-touch-armel-i9100.zip

- flash saucy-preinstalled-touch-armhf.zip

- reboot

- (optional) try to enable 3G data

I don't have any logs at the moment, it would be nice if someone could grab the logs and post the error messages related to RIL. From memory, I think something had to do with illegal ofono request or something like that.

It's not possible, as the problem is that sensorservice doesn't start as it should, and needs to be manually started.
[Galaxy S II Android Development] susimsu:
Maybe you could put the start of the sensorservice in the rc.local file :D
[Galaxy S II Android Development] haralampije2:
root@ubuntu-phablet:/# nmcli c

NAME UUID TYPE TIMESTAMP-REAL

/220051160079829/context1 d6b01fce-94c5-6ce9-c3df-9b08d01b76b1 gsm never

root@ubuntu-phablet:/# nmcli con up id /220051160079829/context1

** (process:7634): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/4: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

** (process:7634): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/4: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

Error: Connection activation failed: Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/4' failed in libnm-glib.

root@ubuntu-phablet:/#

hmhmhmhm:rolleyes:
[Galaxy S II Android Development] ekotim:
does it work on galaxy sl?
[Galaxy S II Android Development] bbfox59:
Just a little trick that I used on Galaxy Note in the fixit to start sensorservice at boot:

Try to add the next line in the /data/ubuntu/var/lib/lxc/android/pre-start.sh file:

sed -i "s/late_start/main/g" $LXC_ROOTFS_PATH/init.rc

Just before this section:

if [ "$INITRD" = "/android/system/boot/android-ramdisk.img" ]; then
sed -i "/mount_all /d" $LXC_ROOTFS_PATH/init.*.rc
sed -i "/on nonencrypted/d" $LXC_ROOTFS_PATH/init.rc

rm -Rf $LXC_ROOTFS_PATH/vendor
ln -s /system/vendor $LXC_ROOTFS_PATH/vendor

for dir in /android/*; do
mkdir -p $LXC_ROOTFS_PATH/$(basename $dir)
mount -n -o bind,recurse $dir $LXC_ROOTFS_PATH/$(basename $dir)
done
fi
[Galaxy S II Android Development] kilabdg:
Great job, but if calling and texting doesn't work, it is still unusefull. I hope, that you will create a solution for this issues.

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy S II Android Development] abtekk:
It will come, don't worry :). Have faith in Max.
[Galaxy S II Android Development] ahmedelhofy:
I am waiting, As soon as calling becomes working. I'll be testing this for sure
[Galaxy S II Android Development] Sloogy 82:
Me too right now I'm working with arch and I don't know a lot from Ubuntu repos an the strukture may be I take another test and look what I can do and send the locfile

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Android Development] dagingerninja:
TV Output

Hi,

So I am finally getting a replacement daily driver for my SGS2. This means that this weekend I can finally start playing around with Ubuntu Touch properly and for more than a day at a time. I was wondering if any work has gone in to getting the phone to output it's display to an external display? (After all this is one of the main reasons Ubuntu Touch is going to be so awesome!)

Thanks
[Galaxy S II Android Development] anzi2:
[MENTION=5366481]dagingerninja[/MENTION] using ubuntu phone as pc seems to be not available yet.

My question is: can we use this as dual boot yet? I was just wondering if it works as of ubuntu phone 1.0 :)
[Galaxy S II Android Development] norkris91:
Wont boot

ubuntu isnt booting on my GS2 (9100)

I have Siyah mod 6.0b5. 1 rom with android and 1 rom with ubuntu ( links from 1 page this thread) and i install them in the correct order, but it wont boot up :S any suggestions?
[Galaxy S II Android Development] Reyden:
Dualboot does not work yet. You have to choose whether you want to use android or ubuntu phone
[Galaxy S II Android Development] midgardian:
There are shortcomings to be very new, of course. Waiting for the development, needs time.
[Galaxy S II Android Development] dagingerninja:
A few questions about touch

Hi guys,

Sorry for the bad title but I couldn't think of what to call this post. Also I apologise for the following essay but I have quite a few questions.

So far I have built and flashed and it works fine (Except for the black screen after re-boot).

1.

Please could you explain what the 2 files I flash are and why I only build one of them and download the other? Is the smaller file that I build the 'core' and the bigger one all the graphical stuff or what?

2.

Am I correct in assuming that we are now using the flipped image, and if so why is it still necessary to install CM first? What part of CM does Ubuntu use. A flipped image means that Ubuntu is running natively and not boxed away inside of CM correct?

3.

For the black screen fix I must run

$ adb shell
$ android-chroot
$ sensorservice &

But I am getting Unable to mount Android Unable to open MTP device. Any suggestions?

And why is this only a temporary fix?

4.

Has anyone tried the audio fix yet? Was it successful?

5.

Am I the only one who cannot get the device to go into 'standby'? Once it is powered on the screen is permanently on...

and lastly is the speed a known issue (I often have to wait for menus to open and such). Is there something I can do about this to make the device feel more responsive?

Sorry about such a long post but I am trying to find my bearings and then hopefully when I have a better understanding of all of this I could maybe start looking at contributing instead of just leaching :p

Thanks a lot!
[Galaxy S II Android Development] julle131:
I will answer these as best as i can.

1. Yes. Cm zip is used by Ubuntu to communicate with the hardware to provide maximum compatibility. The bigger zip is the Ubuntu itself. Cm zip is smaller because it is stripped version of cm. For example, that version if cm can not run android applications.

2. Answer 1 answered a lot from this. Cm is the base so Ubuntu can run with maximum compatibility. Also, using cm base allows Ubuntu to host only one image for all devices. Ubuntu touch is never run boxed inside cm.

3. You run those 3 commands from you PC when Ubuntu touch is stuck on black screen and plugged to your PC. It uses adb to start the service which fixes the black screen. It is temporary fix, as it should start the service automatically. Its not practical to have your PC around to start your phone, is it?

4. Sorry, but I don't know about the audio.

5. And another one I can't comment on.

I hope my post is helpful to you :)
[Galaxy S II Android Development] dagingerninja:
Very helpful. Thank you very much!
[Galaxy S II Android Development] norkris91:
I tested it with clockmod (not dual boot) and the same thing happens, must be somthing wrong with the files or somthing
[Galaxy S II Android Development] norkris91:
Will a Custom kernel like clockworkmod / siyahmod unlock the bootloader or do i have to do that too?
[Galaxy S II Android Development] Reyden:
I am not sure but i think you have to keep everything as it is after flashing ubuntu to make it work. Won't work with any modification (different kernel etc.).
[Galaxy S II Android Development] susimsu:
With siyah kernel dual boot is not working, because with siyah both systems are using the same kernel. But there is a port of the uboot bootloader for the s2 which is able to boot different kernel. Maybe it is possible with that bootloader. You have to try it :D
[Galaxy S II Android Development] norkris91:
im not sure what u mean by: " With siyah kernel dual boot is not working, because with siyah both systems are using the same kernel. "

but i have to use a type of clockworkmod inorder to install ubuntu, what should i use? (if u think siyah is the problem)
[Galaxy S II Android Development] jpeg725:
I believe that if you flash a primary rom using siyah then the kernel gets replaced. So as long as you flash ubuntu as the primary rom it should work. BUT you will loose access to your secondary rom.

Question: Are the kernel differences just in the initrd or is the kernel more fundamentally incompatible?
[Galaxy S II Android Development] susimsu:
Siyah is not the problem, its just not working because it isn't made for ubuntu touch. Normaly both systems are using the siyah kernel (the primery and the secondary one). But ubuntu touch is not working with the siyah kernel. So you have to use a mthode which is able to boot both systems with different kernels. There is a port of the uboot bootloader which is able to do that (but i have never tested it yet) :D
[Galaxy S II Android Development] PATSmod:
Will test now! thanks!
[Galaxy S II Android Development] jpeg725:
The bootloader isn't locked.
[Galaxy S II Android Development] ngvhoang96:
no calls, no sms. not a phone..
[Galaxy S II Android Development] alb3rtt:
No solutions, no improvements and not a helpful post.
[Galaxy S II Android Development] dagingerninja:
Ubuntu Battery life

The battery life in Ubuntu is pretty amazing! I am guessing this is largely to do with the fact that sms/calls are not working so there is very little communication going on there. With minimal use under 50% charge has lasted 3 days!
[Galaxy S II Android Development] susimsu:
Thank you for testing!
[Galaxy S II Android Development] jpeg725:
I have seen many strange things. Boots that result in a permanent black screen. Boots that never turn the screen off. I'm guessing Dorimanx messed some things up some times, and starting the sensorservice may be what is needed for others.

Haven't noticed. I'm still trying to figure out how to navigate between programs and stuff.

The light has finally dawned. The smaller zip is the stripped cm version - that is why, as I discovered, it is unnecessary to flash cm first. The smaller one is the one you have to build for your particular device. The bigger one is the universal root filesystem for all devices.

Thanks for the idea. I didn't know about u-boot until you mentioned it.

If anyone knows how to could separate a samsung boot.img into the kernel, ramdisk and recovery parts. A simple test would be very interesting. Bundling Dorimanx kernel with the ubuntu ramdisk... Then if that boots there would be a chance dualbooting could be built in to Dorimanx's kernel.
[Galaxy S II Android Development] haralampije2:
Any luck talking to maintainer of the Oppo Find 5 for those sim problems on porting. Apparently they don`t have those issues.
[Galaxy S II Android Development] susimsu:
In my opinion the easyest way to add the dual boot support for ubuntu touch to the dorimax kernel would be to add a function to chainboot another kernel (like "real" bootloaders which are able to do dualboot do this) :D
[Galaxy S II Android Development] marcuspereira:
Ubuntu Touch looks amazing. I'll install soon. Thanks for your work. ;)
[Galaxy S II Android Development] Naraa:
Is this ROM possible to Dual-Boot by Siyah Kernel ?

I've already tried to Dual-boot... But my 1st ROM and Recovery dead. Now my Download mode is possible ...

Is there my used Siyah Kernel is wrong ?
[Galaxy S II Android Development] haralampije2:
Why is everyone focusing on dualbooting ubuntu and android, when ubuntu is not working properly. I don`t know what are we trying to accomplish here. Our focus should be porting, because with all respect to OP and other laborious people working on this project I think we should work harder on that CM base, or ask someone from CM team for help. There is sim support and working calls and sms on Ubuntu side, problem is Android and possibly kernel. If there were rewards for porting like they did for Oppo Find 5, we would have working sms and calls and than we should focus on dualboot.
[Galaxy S II Android Development] julle131:
What we are trying to accomplish here is progress. When you are able to dualboot, you can have ubuntu and android. That way you can debug ubuntu when you have time, and use android when you are not debugging. Using nandroid takes a lot of time, space and is generally very clumsy.

Maybe some people want try ubuntu, but they have to have their phone ready to use all the time? Maybe S2 is your primary phone, and you dont want to run alpha OS all the time?

Also, this is S2. It is one of the hardest phones for developers. Let them work in the order they want to, and respect what they do.

This post sounds aggressive, but i am just trying to tell you why dualbooting is progress, and a reason why there are no SMS nor phone calls with ubuntu.
[Galaxy S II Android Development] susimsu:
Of course, we should focus on calls and sms, but for me dualboot is needed as soon as ubuntu isn't working perfectly :D I need my smartphone and can't flash a not perfectly working operating system as my primary rom! IN my opinion the solution with uboot is good enough, it's just for testing. I'm a student of the 10th class and unluckily i don't have enough time for programming in ubuntu touch. Maybe in the X-mass holidays i will have time for playing around and maybe finding a solution for some problems. We have to find more programmers who are interested in that project and have time for programming.
[Galaxy S II Android Development] haralampije2:
I am sorry if you misunderstood me, because I was just trying to be polite. And S2 is hard to dev that is why I said we have to ask for help from other devs.
[Galaxy S II Android Development] koolkunz:
Will this work on cm 10.2 kernel

Will this work with cm 10.2 kernel
[Galaxy S II Android Development] jpeg725:
No. The main reason is that the kernel is bundled up with the initial startup files, and those are organised very differently in ubuntu.
[Galaxy S II Android Development] xter2:
Wow ubuntu for i9100 :) nice
[Galaxy S II Android Development] AOdu29:
Any people work on this rom...?

Envoyé de mon GT-I9100 en utilisant Tapatalk
[Galaxy S II Android Development] jpeg725:
Few. Most of the experts are busy on getting KitKat working.

However there is some very good news. Samsung have published sources that make tv_out work. Of course, if no one is working on it, we won't have it on UbuntuTouch for a while.
[Galaxy S II Android Development] kulitom:
Can you show me link for this news?
[Galaxy S II Android Development] zavorrax:
look at those commits:

https://gerrit.omnirom.org/#/c/2431/

https://gerrit.omnirom.org/#/c/2436/

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Android Development] george1255:
calls/SMS is working?
[Galaxy S II Android Development] ph87:
Please read the OP before asking questions!!!

You can find there all important informations!!

Gesendet von meinem GT-I9100
[Galaxy S II Android Development] jpeg725:
http://xdaforums.com/showpost.php?p=47267140&postcount=305

The best I can find for the mo.
[Galaxy S II Android Development] nelsontky:
cannot boot

Well Ubuntu touch is nice but for me it can't boot a second time. Idk why... ...
[Galaxy S II Android Development] ganiutomo:
Why CyanogenMod

Why do we need to install CyanogenMod? Does Ubuntu Touch need something from CyanogenMod?​
[Galaxy S II Android Development] haralampije2:
To rapidly support a wide range of devices, our architecture reuses some of the drivers and hardware enablement available for Android.

As a consequence, at the current images you'll find some of the Android services running at the device, separated in a lxc container, providing all the basic services needed for Ubuntu to run fully accelerated (media, graphics, modem, etc).

Source https://wiki.ubuntu.com/Touch/Porting.
[Galaxy S II Android Development] dagingerninja:
Hi there,

This is a known bug ATM.

If you read further up the posts you will see they explain how to temporarily fix this.

With your phone connected to your pc in its black frozen screen run the following commands

$ adb shell
$ android-chroot
$ sensorservice &

Hope this helps.

Cheers
[Galaxy S II Android Development] jpeg725:
Actually you don't need to flash cm first. I tried it.

I also checked the zip files, all the necessary stuff from cm is in the first zip. The other zip contains the root ubuntu filesystem and is common to all devices.
[Galaxy S II Android Development] soneric:
When we can use Call And sms Anyone have an idea?

GT-I9100 cihazımdan Tapatalk 2 ile gönderildi
[Galaxy S II Android Development] susimsu:
You have to learn to read! Just read the last 5 pages! We have this question again and again...
[Galaxy S II Android Development] murattiy:
$ adb shell ok

$ android-chroot not found

android-chroot ?
[Galaxy S II Android Development] Diamond5170:
This commands (android-chroot and ubuntu-chroot) removed a long time ago. We need to find another method to access android in lxc container. I find it, but now i don't remember how to do that.
[Galaxy S II Android Development] Diamond5170:
I found an easy solution :)

Not needed chroot, we can run sensorservice directly from ubuntu.

Add this line to /etc/rc.local (or use any other method)

./system/bin/sensorservice &

and black screen after reboot is fixed.

MaxWallstedt, please add this to guide. And switch "phablet-saucy" to latest "phablet-trusty", its working fine, i tested it.

---------- Post added at 06:45 PM ---------- Previous post was at 06:32 PM ----------

My build, based on trusty repo: https://docs.google.com/uc?id=0BzFI4xYcj01sXzdKeTZTQXRDQWM

Flash it and http://cdimage.ubuntu.com/ubuntu-to...d/current/trusty-preinstalled-touch-armhf.zip, reboot and add sensorservice to rc.local (from phone terminal, adb or ssh).

Sound, call/sms not working.
[Galaxy S II Android Development] wulsic:
cant we make a flashable zip also from that file with the fix or build included with it so you dont need adb?
[Galaxy S II Android Development] JediBrooker:
your first link is broken or doesn't have the correct permissions. any chance you could fix it up for us please?

cheers!

i had a go at trying to build tasty on my own but i couldn't get it to work. would you be so kind as to writing up a quick tutorial or the commands you put in to get it to build?
[Galaxy S II Android Development] EttyN:
The first link is not working for me either, the file isn't found.
[Galaxy S II Android Development] MaxWallstedt:
Thank you!

I've updated the OP. Please tell me if anything else needs to be updated.

Regarding the android-chroot script, it has been removed. There's however a new better method for entering the Android container:
[Galaxy S II Android Development] Diamond5170:
Sorry, fixed.
[Galaxy S II Android Development] haralampije2:
Apparently there will be huge progress soon https://lists.launchpad.net/ubuntu-phone/msg05332.html
[Galaxy S II Android Development] vijaysimhahr:
Great to see a new variant of OS. Thanks.
[Galaxy S II Android Development] Diamond5170:
We need to fix sound, other bugs will be fixed by system updates, but sound is device specific problem.

I do all steps from porting guide (sound part) but sound not working and i see error in syslog:

Dec 4 21:56:08 ubuntu-phablet pulseaudio[2266]: [pulseaudio] alsa-ucm.c: Failed to get the verb HiFi
Dec 4 21:56:08 ubuntu-phablet pulseaudio[2266]: [pulseaudio] alsa-ucm.c: No UCM verb is valid for U1-YMU823

Card name and directory name is valid, and i use device hw:0
[Galaxy S II Android Development] rumitdhamecha:
Waiting for it eagerly

Hope There is some good work. If SMS and Call starts working i will flash it the next min.

Keep up the work guys. :)
[Galaxy S II Android Development] hasanarbab:
Best of Luck

i have a S4 but I'm still keeping my S2, not selling just because it is an awsome phone and it's gonna be most awsome phone in the world with ubuntu on it. useless lovers of ubuntu like myself can only cheer you guys up. I wish i was an extra ordinary programmer like u guys and could help you. love you though ubuntu team :o
[Galaxy S II Android Development] dhevans79:
Hi,

I was waiting to buy a nexus 4 second hand for development, until I realised my old sgs2 was a good candidate.

I really want to say thanks to the developers there who are working on this port. It is really appreciated, and much respect for the work you're doing.

If I understand correctly, I can do the blackscreen reboot fix from the phone terminal, however the terminal is not responding to any commands, including ls. It just appears to hang until I issue a ctrl+c. Do you have the same behaviour?

Does this mean that the reboot is occurring correctly, the issue is just with the display output? How come this is not an issue after the initial img flash?

Cheers,
[Galaxy S II Android Development] usrXD:
Wow! Hard work! :)
[Galaxy S II Android Development] rtorres0106:
nice work thanks..
[Galaxy S II Android Development] JavaZoid:
what exactly is the problem dudes, this has been almost a year now, is there still source code that Canonical needs to provide..

has Canonical even provided working RIL directories yet, working functions ?.. what exactly are the issues now ? blocking the project from getting completed ! ...maybe i could devote some of my time to help out, but i would like to know what are the current issues
[Galaxy S II Android Development] wulsic:
so far as i know we need to fix pulseaudio and sms/call maybe is going to be fixed by canonical this month still i think

and sensorservice we may can automatically include with install zip i can look into that maybe or it is possible if i have some free time

if some developer who knows more about sound then watch this link:

https://wiki.edubuntu.org/Touch/Core/PulseaudioProfiles

i dont have time to do it i think we can configure the audio to work with this

correct me if i am wrong
[Galaxy S II Android Development] JavaZoid:
well from what it seems, Canonical has a new partner, so Canonical isn't providing anything until that's all solid & official or it might suddenly boost the project, who knows.. but great job so far dudes, thanx for your time & effort :highfive:

---------- Post added at 09:27 PM ---------- Previous post was at 08:58 PM ----------

Audio not working could could be due to many things.. hardware, kernel, audio-engine its-self, thats alot of debugging, if anyone would be-able to provide a fast fix is Cyanogen Mod, i assume they have expertise in all area's

how does audio work on the GT19100 running Android ... & Ubuntu why would it be any different.. seems like the bug is leaning towards a kernel issue to me :confused:
[Galaxy S II Android Development] pauloavelar:
Most things not working could be called bugs...

-

I'm waiting for the Calls/Data/SMS fix to fully migrate.

I love CM 10.1, but I'm also a big fan of innovation.

Oh, and btw, getting wi-fi to work was awesome, guys! Keep up!
[Galaxy S II Android Development] MaxWallstedt:
Hi!

I looked in the new ubuntu-session file, and the change would work for this device, but there a a lot of devices that identify as "SMDK4210" (N7000 for example) and all these devices use different values in ubuntu-session. Would you still consider this change worthwile?
[Galaxy S II Android Development] ogra-ubuntu:
well, the script will go away at some point in favour of something cleverer. Currently it only checks for the "Hardware" fiield in /proc/cpuinfo so thats the only thing we can match against, do you have an idea how to differentiate further in that context (do different SMDK4210 probably use different values in the "Revision" field ?)
[Galaxy S II Android Development] Gerrett:
AW: [ROM][GT-I9100][WIP] Ubuntu Touch Developer Preview

Maybe its better to check device name like

getprop ro.product.device

So every device can get his own settings.

Gesendet von meinem GT-N7000 mit Tapatalk 2