[Linux] [Dev] [WIP] Ubuntu Touch on the TF101 - Alpha

Search This thread

*Detection*

Senior Member
Dec 5, 2011
10,512
2,862
Durham
delete the networks from the graphical interface, reboot and try again.

Can't delete them, long press does nothing, pressing once just connects to them again

It says this "find: File system loop detected; `./data/ubuntu' is part of the same file system loop as `.'."

But navigating via /data/ubuntu only cures the read only problem, it still finds no wpa_xxxxx

EDIT
/data/ubuntu/system/ exists, but /etc/ is not in /system/
 
Last edited:

jholtom

Inactive Recognized Developer
Sep 26, 2010
300
440
NoVA
Can't delete them, long press does nothing, pressing once just connects to them again

It says this "find: File system loop detected; `./data/ubuntu' is part of the same file system loop as `.'."

But navigating via /data/ubuntu only cures the read only problem, it still finds no wpa_xxxxx

Wipe cache, and reboot, along with running this:
Code:
adb root
adb remount
adb shell
nano /etc/wpa_supplicant.conf
remove network blocks....
or it might be /etc/wifi/wpa_supplicant.conf
 

*Detection*

Senior Member
Dec 5, 2011
10,512
2,862
Durham
Check dmesg, and pastebin it. along with running ifconfig wlan0.
iwconfig too.
Thanks!


Ok, and I`m in

Capture.PNG




EDIT - dmesg
http://pastebin.com/HmGVuk7f


Code:
root@android:/ # ifconfig wlan0
wlan0: ip 192.168.1.134 mask 255.255.255.0 flags [up broadcast running multicast]


EDIT -
Code:
root@localhost:/# iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11abg  ESSID:"DD-WRT"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:xx:xx:F9:2D:07   
          Bit Rate=65 Mb/s   Tx-Power=1496 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=70/70  Signal level=-37 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@localhost:/#
 
Last edited:

jholtom

Inactive Recognized Developer
Sep 26, 2010
300
440
NoVA
So its got an ip, and appears to be connected.

run:
Code:
ping google.com
wget http://google.com
cat index.html

Thanks for being so awesome and a great tester!
 

*Detection*

Senior Member
Dec 5, 2011
10,512
2,862
Durham
So its got an ip, and appears to be connected.

run:
Code:
ping google.com
wget http://google.com
cat index.html
Thanks for being so awesome and a great tester!


:) Loving every second of it :)

ping google.com works fine and returns a ping of 33

Code:
127|root@android:/ # wget http://www.google.com
wget: bad address 'www.google.com'
1|root@android:/ # wget http://google.com                                      
wget: bad address 'google.com'
1|root@android:/ # wget google.com                                             
wget: not an http or ftp url: google.com
1|root@android:/ # cat index.html
/system/bin/sh: cat: index.html: No such file or directory
1|root@android:/ #
 

*Detection*

Senior Member
Dec 5, 2011
10,512
2,862
Durham
Edit it and remove all the network blocks, reboot, and reconnect to the network. inside the chroot run curl google.com - it should say something about a document being moved.


Won't let me edit the file, just throwing up errors saying to try in different modes which I have, no difference

And: curl: command not found
 

*Detection*

Senior Member
Dec 5, 2011
10,512
2,862
Durham
inside the chroot, run apt-get install curl wget.
then try them again.
I cannot believe they shipped such a stripped down image.

wget

Code:
root@localhost:/# wget google.com
--2013-03-02 01:06:21--  http://google.com/
Resolving google.com (google.com)... 173.194.70.139, 173.194.70.101, 173.194.70.138, ...
Connecting to google.com (google.com)|173.194.70.139|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.google.com/ [following]
--2013-03-02 01:06:21--  http://www.google.com/
Resolving www.google.com (www.google.com)... 173.194.69.103, 173.194.69.99, 173.194.69.104, ...
Connecting to www.google.com (www.google.com)|173.194.69.103|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.co.uk/ [following]
--2013-03-02 01:06:22--  http://www.google.co.uk/
Resolving www.google.co.uk (www.google.co.uk)... 173.194.34.56, 173.194.34.63, 173.194.34.55, ...
Connecting to www.google.co.uk (www.google.co.uk)|173.194.34.56|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'

    [ <=>                                   ] 10,631      --.-K/s   in 0.001s  

2013-03-02 01:06:22 (17.0 MB/s) - `index.html' saved [10631]


curl
Code:
root@localhost:/# curl google.com
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>
root@localhost:/#
 

Top Liked Posts

  • There are no posts matching your filters.
  • 94
    Hello All, I've got Ubuntu Touch compiled for our beloved TF101's.

    Thread by TomTcom with instructions on how to build: http://xdaforums.com/showthread.php?t=2326453 <- Same way I do it, so have at ye!

    Remember this is still in Alpha on the ubuntu end, and our end too, but is still getting better, well at least ours is.

    New pretty picture attached by Oeio

    Instructions
    - First download the latest image (below).
    - Then download quantal-preinstalled-phablet-armhf.zip from here
    - Place both of these files in a place where you can flash them from recovery
    - Wipe data
    - Then flash the ubuntu-touch-tf101.zip, and then quantal-preinstalled-phablet-armhf.zip. IN THAT ORDER
    - Reboot and you should be good to go, make sure to clear cache.....
    - After reboot follow the instructions in post 3 to fix the resolution, and then reboot again.

    Downloads
    Generic Ubuntu Stuff - quantal-preinstalled-phablet-armhf.zip
    Current (0.9): here
    Fresh new Saucy Salamander build : http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/

    (0.7)
    http://goo.im/devs/jholtom/ubuntu-touch-tf101-0.7.zip

    (0.6)
    http://goo.im/devs/jholtom/ubuntu-touch-tf101-0.6.zip

    (0.5)
    here

    (0.4)
    here

    (0.3):
    here

    (0.2)
    here

    (0.1)
    here 2nd Mirror here


    Working:
    Touch Screen
    Power Button
    Battery meter - charge and discharge work, along with charge via dock
    Audio
    Dock Keyboard - no function keys yet.
    Auto-Rotate
    WiFi
    Brightness Control

    Not quite sure:
    HW Acceleration

    Not Working:
    Camera
    Some font problems.

    Untested:
    Everything else....

    Screenshots
    http://localhostr.com/files/krQu43a/WP_000052.jpg
    http://localhostr.com/files/pKschgA/WP_000053.jpg
    http://localhostr.com/files/N6neEKE/WP_000056.jpg
    http://localhostr.com/files/RUGlOzs/WP_000063.jpg
    http://localhostr.com/files/qeuzqGp/WP_000057.jpg
    http://localhostr.com/files/8lgNnpO/WP_000062.jpg
    http://localhostr.com/files/rm8FrIj/WP_000064.jpg
    http://localhostr.com/files/LtpxAS7/WP_000067.jpg
    http://localhostr.com/files/5hQQLuq/WP_000077.jpg <- Proof of Working WiFi
    Video
    http://youtu.be/o9s8F5cwhp0
    http://youtu.be/KHpHp21aylU
    Thanks *Detection* for the screenshots and video (and onkelbebu)

    Information:
    - The Ubuntu Touch system is currently in developer-preview state, just to give you an idea of how incomplete this is.
    - My build sources may be broken; either get along with it or wait for me to fix it.
    - No longer am I the sole developer, we now have onkelbebu on board pushing changes and updating.

    SOURCES
    My modified device tree is here:
    https://github.com/jholtom/android_device_asus_tf101
    Now using this kernel
    https://github.com/jholtom/kernel_asus_tf101-lumpy

    Sources for Ubuntu are at:
    http://phablet.ubuntu.com/gitweb


    Thanks:
    onkelbebu, for his help with getting wifi working, and everything else.
    RaymanFX, Timduru and others for the kernel and device tree.
    *Detection* for being an awesome first tester.
    and of course, Canonical :p

    Don't forget the Thanks button :)
    21
    Notes

    1) Do not flash any other kernel with this; there are no compatible ones as of now.
    2) In case you missed it: I am the official Ubuntu Touch developer responsible for the Transformer https://wiki.ubuntu.com/Touch/Devices


    CHANGELOG
    Current (0.9)
    New build after hiatus, no major changes
    just upstream updates.

    (0.8)
    Continued attempts to fix the black screen problems.
    new resolution fix implemented from ubuntu end.

    (0.7)
    Merged changes again
    Re-added procfs patch

    (0.6)
    Merged changes from ubuntu
    Added procfs patch from ubuntu

    (0.5)
    Added resolution fix on boot, and synced ubuntu sources
    Fixed Brightness Control - Thanks onkelbebu

    (0.4)
    Updated internet fix in kernel (PARANOID_NETWORK)

    (0.3)
    removed uchroot changes, and updated ubuntu sources
    edited init.ventana.rc for WiFi fix.

    0.2
    Updated ubuntu sources (specifically to uchroot)

    0.1
    First build with minimal changes for TF101 to boot.
    14
    That's simply awesome :)

    Thanks to all workers ! I'm waiting for that ! :D

    That script is just what i'm adding into the flash of 0.5 so that no one has to do the screen resolution fix themselves, on first boot it will run and patch if for you.
    Expect 0.5 within 2 hours of this post.
    EDIT: UPLOADED
    13
    reserved

    DEPRECATED - no longer needed as it now autofixes on first boot
    Fix for the Screen Density - Copy and Pasted from the Ubuntu Wiki.

    Instructions (Run from shell with transfomer connected and on.)
    adb shell
    ubuntu_chroot shell
    vi /usr/bin/ubuntu-session

    Find and edit the values for the following entries (there are two entries for each:
    GRID_UNIT_PX=10 (as suggested - read below)
    QTWEBKIT_DPR=1.2 (looks best to me by trial and error)



    SCREEN PIXEL RATIO

    We have 2 important variables that define the pixel ratio behaviour of the system and the applications, ie. how they visually scale. Look at /usr/bin/ubuntu-session for GRID_UNIT_PX and QTWEBKIT_DPR. Add another device specific settings there based on your device, using the method below to calculate the desired DPR.

    The number of pixels per grid unit (GRID_UNIT_PX) is specific to each device. Its goal is to make the user interface of the system and the applications of the same perceived size regardless of the device they are displayed on. It is primarily dependent on the pixel density of the device’s screen and the distance to the screen the user is at. That second value cannot be automatically detected and is based on heuristics. We assume that tablets and laptops are the same distance and that they are held at 1.235 times the distance phones tend to be held at.

    A reference device has been chosen from which we derive the pixels per grid unit for all other devices. The reference device is a laptop with a 120 ppi screen and the pixels per grid unit is set to 8 px/gu.

    Asus Transformer Tablet - 1280x800 - 149 ppi - 10 px/gu

    There is no way for the system to dynamically identify the correct pixel ratio for the device, which as a side effect things might be bigger/smaller than expected. For each device you will have to visually verify the quality of the result and adjust the number if necessary. If unsure, send screenshots and screen specifications of the device to the Canonical design team.
    12
    New information for porters

    Friends,

    Daniel Holback send some new information for help the porters. The ports sources will be available through the https://code.launchpad.net/~tf101-image-dev and merge requests will be welcome. :good:

    I will make some fixes to revamp the tf101 port availability and tomorrow I will send more information about how to fork this. My build will be saucy based, fliped image. Links in some hours with the steps to help with the upstream project. :fingers-crossed:

    Thanks to jholtom and everyone else helping in this :highfive: