New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable installation of "deb" Nexus 7 2013 gsm #643

Open
doniks opened this Issue May 31, 2018 · 33 comments

Comments

Projects
None yet
8 participants
@doniks

doniks commented May 31, 2018

Description of the feature

Enable installation of "deb" Nexus 7 2013 gsm

There is no porting needed. Not even compiling images. All the pieces are on the image server already. I think the only thing missing is some glue in the json files on the server or maybe in the installer.

The "deb" is the sibling of the "flo" device. The flo is the wifi version, deb is gsm.

Steps to reproduce

  • use ubports-installer
  • try to install for deb

Expected behavior

Can be installed

Actual behavior

deb is not an option in the installer

Workaround

  • install flo images with the installer
  • boot, look around,
    => observe that basically everything works (except sound)
  • boot into recovery mode
  • download last deb device image from image server:
    /pool/device-1b9d2f7256c3d6c98ba93b66ad48d9ce75833978cd65364df45693e0d40b27a1.tar.xz
  • as pointed out here for 15.04, deb, rc, v3
    system-image.ubports.com/ubports-touch/15.04/rc/deb/index.json
  • replace the /var/lib/lxc/......./system.img file
  • boot into fastboot mode
  • flash the boot.img from the device-1b.....a1.tar.xz
  • reboot into UT
    => observe that basically everything works including sound
@Flohack74

This comment has been minimized.

Member

Flohack74 commented May 31, 2018

@mariogrip what do you think?

@doniks

This comment has been minimized.

doniks commented Jun 3, 2018

Even xenial runs! Just saying ...

@zubozrout

This comment has been minimized.

zubozrout commented Jun 5, 2018

Hi,
well, sound certainly worked back when I was still having N7 deb - but back in the days it was a bit tricky to get this working: https://forums.ubports.com/topic/44/installing-ubuntu-on-nexus-7-2013-deb-lte :)

I've originally used an image from here: http://system-image.tasemnice.eu/ubuntu-touch/devel-proposed/ubuntu/deb/ but it died early in 2016.

Now I feel sad I don't have N7 any more - it was a great device and it was a blast running Ubuntu Touch on it.

@doniks

This comment has been minimized.

doniks commented Jun 6, 2018

@zubozrout sound is not an issue. it only doesn't work with the flo image on deb device. sound DOES work in deb device when using the deb image

this issue is just about adding deb to the json files on the server to allow normal installation

@zubozrout

This comment has been minimized.

zubozrout commented Jun 6, 2018

@doniks Oh, I see, sorry I've missed the last line of that report.

@NeoTheThird

This comment has been minimized.

Member

NeoTheThird commented Jun 9, 2018

@UniversalSuperBox If you have a report for me, i can add it to the installer api

@NeoTheThird NeoTheThird self-assigned this Jun 9, 2018

@UniversalSuperBox

This comment has been minimized.

Member

UniversalSuperBox commented Jun 9, 2018

I have flo, not deb, but it works fine using the old Android compatibility and xenial. I've asked @mariogrip to re-enable building of the flo image.

@zubozrout

This comment has been minimized.

zubozrout commented Jun 13, 2018

Great, I've missed that but both Flo and Deb have appeared here: http://system-image.ubports.com/ubports-touch/16.04/devel/ on Monday :).

@Flohack74

This comment has been minimized.

Member

Flohack74 commented Jun 13, 2018

Can you test it and then we can close this ? :)

@NeoTheThird

This comment has been minimized.

Member

NeoTheThird commented Jun 13, 2018

@Flohack74

Can you test it and then we can close this ? :)

It's not done by putting it on the system image server, we also need to add it to the installer. flo is already confirmed working, for deb i still need a recovery. Or can we use the same @UniversalSuperBox?

@doniks

This comment has been minimized.

doniks commented Jun 13, 2018

@NeoTheThird , maybe I'm not understanding your question right, or maybe you're just asking for independent confirmation from UniversalSuperBox, but my workaround is to tell the installer to install flo (which uses the flo recovery) to install onto my deb device.

FWIW, I've now also checked the partitions/recovery.img which is included in the deb device file /pool/device-1b9d2f7256c3d6c98ba93b66ad48d9ce75833978cd65364df45693e0d40b27a1.tar.xz, when I diff it against http://cdimage.ubports.com/devices/recovery-flo.img which the installer is using, it tells me it is different, when I boot either of these two recoveries the kernel introduces itself as:

uname -a
Linux localhost 3.4.0-5-flo #1-Ubuntu SMP PREEMPT Thu Sep 3 14:21:37 UTC 2015 armv7l GNU/Linux

so, in summary, images are different, kernels are the same, both recovery images boot and I can adb shell into them and nothing seems broken and the recovery-flo.img allows the installer to complete successfully

@NeoTheThird

This comment has been minimized.

Member

NeoTheThird commented Jun 13, 2018

@doniks Thank you, yes, that was my question. So I will go ahead and add deb to the installer. Does GSM work for you @doniks?

@doniks

This comment has been minimized.

doniks commented Jun 13, 2018

I don't have a sim card to test. It used to work once upon a time in good ol canonical days when I still had a sim card for it

@NeoTheThird NeoTheThird added this to In Development in Ubuntu Touch Jun 16, 2018

@NeoTheThird NeoTheThird added this to the 16.04 OTA-4 milestone Jun 16, 2018

Ubuntu Touch automation moved this from In Development to Quality Assurance Jun 16, 2018

@NeoTheThird

This comment has been minimized.

Member

NeoTheThird commented Jun 16, 2018

Okay, you should be able to use the installer for it now. I would appreciate if someone could test it @doniks

@doniks

This comment has been minimized.

doniks commented Jun 16, 2018

Well, I get a bit further, but it's not quite right. I think the installer is mistaking it for a flo.

I start from TWRP recovery
installer is sometimes able to detect that it is a deb, otherwise I select it manually
install 16.04/devel
boots to login screen, I can log in, connect wifi, open apps -> OK

However, I cannot hear any sound from youtube, nor change the volume form the indicator. The indicator is literally called "indicator-sound" with a cogwheel icon and no controls.

I'm sure this means it installed the android container from flo. When I go back to recovery and replace the /var/libl/lxc/somethingsomethign/system.img with the one for deb (from the device-1b9d2f7256c3d6c98ba93b66ad48d9ce75833978cd65364df45693e0d40b27a1 ) and reboot then I get sound

so I think it somehow mistakes the device for a flo.

To be clear. flo and deb are close enough so we can use the flo recovery.img for installing, but seems there is a difference in the android container (not sure about boot.img)

@NeoTheThird NeoTheThird reopened this Jun 16, 2018

Ubuntu Touch automation moved this from Quality Assurance to Accepted Jun 16, 2018

@NeoTheThird

This comment has been minimized.

Member

NeoTheThird commented Jun 16, 2018

Okay, thanks for testing

@Stefano0101

This comment has been minimized.

Stefano0101 commented Jun 16, 2018

Not working just like before, same output in the Recovery. Just tried the latest installer. 15.04 stable.

@doniks

This comment has been minimized.

doniks commented Jun 16, 2018

@Stefano0101

same

what exactly is "same"?

Can you install when you manually select the device?

@Stefano0101

This comment has been minimized.

Stefano0101 commented Jun 17, 2018

Nope, same issue as closed bug No. 300
It install the recovery, dovnload and push the files, reboot to recovery and fails.

@doniks

This comment has been minimized.

doniks commented Jun 17, 2018

ah I see. I don't think #300 and #643 are really duplicates though.

643 is about enabling the installation of the images that are already existing on the server onto the deb. The starting point is that those images, including the old kernel image, which I think is still from canonical times are working perfectly fine. Originally serving these files from the server and installing them in the installer was missing. Now they are served just fine, but somehow the installer ends up installing flo instead of deb.

300 is about the existing flo images not booting successfully on the reported flo devices. My best guess is that it is indeed down to the hardware revision as indicated in 300.

separate problems

PS: #64 and #643 are indeed duplicates. In the old one I tried to get the images rebuilt in ubports organization. I never managed. In #643 I realized that the old images are still around and install and run just fine.

@Stefano0101

This comment has been minimized.

Stefano0101 commented Jun 17, 2018

Exactly what I think. 2 different issues.

@NeoTheThird NeoTheThird moved this from Accepted to In Development in Ubuntu Touch Jun 29, 2018

@NeoTheThird

This comment has been minimized.

Member

NeoTheThird commented Jun 30, 2018

I put a different recovery on the server, could you try the installer again?

@Stefano0101

This comment has been minimized.

Stefano0101 commented Jun 30, 2018

I'll try again.

@Stefano0101

This comment has been minimized.

Stefano0101 commented Jun 30, 2018

Yeah, I just tested the new installer. NOPE. did not work, even when installer says success! This hardware revision of Nexus 7 is problematic. It again trows errors once the files are pushed to recovery and rebooted to recovery to flash it. I would suggest, you just close this as Nexus 7 is an old device and probably it's just wasting of time to try to fix this. We want to progress on 16.04 and go forward with a ,,NEW DEVICES"
I don't mind not to have UT on Nexus 7.

@doniks

This comment has been minimized.

doniks commented Jul 3, 2018

Tried again now, but it doesn't seem to like that recovery image:

Fastboot: Unknown error: sending 'recovery' (12592 KB)...OKAY [ 0.426s]writing 'recovery'...FAILED (remote: image is not a boot image)finished. total time: 0.430s

Automatically generated error report
Version: 0.1.13-beta
Host OS: linux
Host Dist: Ubuntu Linux 18.04
Package: Snap
Host Arch: x64
Node: v8.2.1

Error log: http://paste.ubuntu.com/p/8r74kn93mz/

@doniks

This comment has been minimized.

doniks commented Jul 4, 2018

Also, I observe now that from ut settings -> updates it seems to forever (I waited mintues) look for an update but never find one ... I think there is also something stuck there.

@Flohack74

This comment has been minimized.

Member

Flohack74 commented Jul 18, 2018

@doniks the problem with the updater is not flo/deb specific, I got this sometimes across all devices...

@doniks

This comment has been minimized.

doniks commented Jul 20, 2018

@Flohack74 I'm wondering whether you are speaking of the same issue as me. I do not ever get a system update.

multiple weeks. multiple reboots. multiple times hacking a newer version in with (minimally modified) rootstock script. I'm taking about perfect reproducability. It fails 100% of the time. Is this what you mean? Can you point me to the issue nr. I had a look but couldn't find it.

@doniks

This comment has been minimized.

doniks commented Jul 24, 2018

Another observation, might be related to the non-working update: I see no build tag in System Settings -> About

@papagunit

This comment has been minimized.

papagunit commented Jul 30, 2018

Came here from #300. Did the process on an Ubuntu 18 machine with a 7 2013 wifi, no issues detecting the device, recovery mode, flashing files, etc. Got to the ubuntu spash screen, and it said "This phone needs restoring from a PC or service center". Eventually discovered that I need to flash it back to kitkat (it was on 6), and then go through the installation process as normal. The first 5 steps in this git helped me out, while using this image.

Just as an fyi for anyone else having issues. Appears to be few other nexus 7 users out there.

@NeoTheThird NeoTheThird removed this from the 16.04 OTA-4 milestone Aug 3, 2018

@NeoTheThird NeoTheThird removed this from In Development in Ubuntu Touch Aug 3, 2018

@NeoTheThird NeoTheThird removed their assignment Aug 3, 2018

@NeoTheThird

This comment has been minimized.

Member

NeoTheThird commented Aug 3, 2018

Ok, sorry guys. It seems like deb is actually a little more different than we anticipated. We're going to put a pin in this for now and maybe come back to it later.

@doniks

This comment has been minimized.

doniks commented Aug 5, 2018

@NeoTheThird ok, so I'll continue to use my hackish install method. Let me know if there is anything I can do to help.

@doniks

This comment has been minimized.

doniks commented Aug 13, 2018

FWIW system-image-cli is not happy:

$ system-image-cli 
b'00ffc806\n'
usage: system-image-cli [-h] [--version] [-C DIRECTORY] [-b BUILD]
                        [-c CHANNEL] [-d DEVICE] [-f FILTER] [-m MAXIMAGE]
                        [-g] [-i] [-n] [-v] [--progress PROGRESS]
                        [-p PERCENTAGE] [--list-channels] [--factory-reset]
                        [--production-reset] [--switch CHANNEL]
                        [--show-settings] [--set KEY=VAL] [--get KEY]
                        [--del KEY] [--override-gsm]
system-image-cli: error: 
Configuration directory not found: /etc/system-image/config.d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment