yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] MassStash:
Still black screen no boot for me with that latest stuff.

~S-Off LTEvo; Viper4G_3.x.x; ArcReactor

cpu0/1: 1.7ghz ¦ 192mhz ¦ sleep: 486mhz max

Intellidemand

fiops

mpdecision: off
[Eee Pad Transformer Android Development] Dieselrellim:
Still getting black screen on the newest builds

Sent from my Transformer TF101
[Eee Pad Transformer Android Development] kenshin1388:
Same for me, flashed it before the preinstall and after. Just can't seem to get it.
[Eee Pad Transformer Android Development] onkelbebu:
For people not getting adb to work try following:

Use googles adb driver, not the one specifically for transformer. Try ADB Interface first, it that not works try ADB Composite, i am not in reach of my windows machine to validate wich one it was.

Then please get a logcat
[Eee Pad Transformer Android Development] kenshin1388:
Ill see what I can do for you. I'm at work right now so I was unable to grab a logcat earlier. Should be off in an hour or two.
[Eee Pad Transformer Android Development] jholtom:
The latest on goo.im has all of onkelbebu's changes merged in, but its not going on the front page till we know it boots.

From the last logcat I saw it had ubuntu-session crashing with a status code 126 (Which from my knowledge + google) is a SIGSEGV (Still possible to be wrong though) ubuntu-session is the actual desktop environment and display manager that runs atop surfaceflinger as of now, so that would explain the black screen.
[Eee Pad Transformer Android Development] kenshin1388:
Well when I got home I decided to convert my xubuntu install to lubuntu. In the middle of uninstalling xubuntu-desktop the breaker flipped. Never even got to installing lubuntu-desktop. Gonna be morning before I can even get that logcat for you. Stupid old 2001 laptop and its slowness lol.
[Eee Pad Transformer Android Development] ayr-ton:
There's some people with the black screen issue:

https://bugs.launchpad.net/ubuntu-tf101/+bug/1153306

No problem if someone want to report Ubuntu Touch related bugs in tf101 launchpad page. I will make the triage to the Ubuntu Touch developers.

The link for bug reports is:

https://bugs.launchpad.net/ubuntu-tf101/

Please, not submit bugs directly to the developers. The bugs will be confirmed and anyone can assign themselves for make pull requests to the jholtom repo.

---------- Post added at 11:20 AM ---------- Previous post was at 10:56 AM ----------

Not works for me :(

Can you submit a pull request to jholtom repo? The camera patch would be great :D
[Eee Pad Transformer Android Development] jholtom:
onkelbebu is on the team and is allowed to push directly to the repo without my check through the updated code before I pull. I do however check the commits before they are built and uploaded for ya'll testers to have at.
[Eee Pad Transformer Android Development] ayr-ton:
\o/

Do you have all the names and github pages of all developers with push access for I can update the credits in wiki page?

If you create a team in launchpad with them I could update the project page too :)
[Eee Pad Transformer Android Development] x3maniac:
First of all Great job jholtom!. i was actually gonna try to port this to the tf101. Great to see someone did it. hope you don't mind me asking some questions. the op post doesn't really describe much on how this works. does this boot using a standard android kernel then chroot into ubuntu touch? so some where in the initramfs loop mounts the img? reason why i'm asking is cause i was acutally going to use my approach and dual boot and install it into the emmc mmcblk0p16.

onkelbebu: may i ask how you got the camera to work? can you post a link to your commit? thanks i want to see if i can fix my kernel to get ubuntu to work with the camera. i'm acutally trying to get the gps working.

-don
[Eee Pad Transformer Android Development] onkelbebu:
Exactly, its the standard kernel for the device with some additional settings, pretty well documented here:

https://wiki.ubuntu.com/Touch/Porting

The chroot doesnt get mounted though, its a seperate dir on /data/. The chroot script is registered as a service in the core rc files.

I did not have to do much, i loaded the camera driver into ida and could see that it tries to load libandroid_runtime.so, but on first look it didnt import anything of it. So i made an empty stub lib, that way the driver could get loaded. I will look further into what the driver really needs.

My commit is here:

https://github.com/jholtom/android_device_asus_tf101/commit/4e8a3b83fa45a6fc4aba987778348207ebcb29e6
[Eee Pad Transformer Android Development] josteink:
TF101-support aside, how are the Ubuntu Touch Preview's coming along?

I just tried it on day of release (on my Galaxy Nexus) and then it had still quite some way to go before it could even be considered a daily driver. Missing apps, no PIN unlock, missing messages, network not working, etc etc.

I see Ubuntu has daily builds now. Has anyone any comment on how much Ubuntu itself has improved since launch? Is it getting better, or is it just new builds? :)
[Eee Pad Transformer Android Development] danielholm:
Sv: [Linux] [Dev] [WIP] Ubuntu Touch on the TF101 - Alpha

It should become better. The daily builds doesnt get built if no changes are made. Also Shuttleworth said a week ago that Touch should become a better every day experiance in a few weeks. But I´m too curious of how things progress. I really want it as my every day OS as fast as possible.

There are, however, a lot of stuff happening in the coreapps.
[Eee Pad Transformer Android Development] onkelbebu:
as far as i can tell, this is where development happens:

https://code.launchpad.net/~phablet-team

Imho its still lightyears away from being usable, to much mock up apps.
[Eee Pad Transformer Android Development] *Detection*:
Have the daily builds removed all the demo contacts and videos etc ?
[Eee Pad Transformer Android Development] ayr-ton:
I will talk to rsalveti for know if theres some problem with the upstream.
[Eee Pad Transformer Android Development] ayr-ton:
No. The dummy data will stay there until it changes the status of developer preview.

The status will change probably on 13.04 launch. As Mark Shuttleworth said, it will be "ready to use" in the next weeks.
[Eee Pad Transformer Android Development] *Detection*:
Thanks, good stuff, maybe I will have ownership of my tablet again by then....
[Eee Pad Transformer Android Development] Sziehr:
Has anyone tried this out on the Slider yet? I'm weak on linux fu, so I would rather wait for it to be a little more polished before I try it.
[Eee Pad Transformer Android Development] danielholm:
Sv: [Linux] [Dev] [WIP] Ubuntu Touch on the TF101 - Alpha

Wrong sub forum. Check out your device forum or the general Ubuntu Touch sub forum.
[Eee Pad Transformer Android Development] Sziehr:
This is the device forum for the ASUS Slider, it was never split off from the TF101.
[Eee Pad Transformer Android Development] danielholm:
Sv: [Linux] [Dev] [WIP] Ubuntu Touch on the TF101 - Alpha

Oh, what do you know. My mistake. Sorry.
[Eee Pad Transformer Android Development] ayr-ton:
That right.

---------- Post added at 08:52 AM ---------- Previous post was at 08:27 AM ----------

I think it can work. Probably the only big hardware difference between transformer and slider is the screen.

You can try after we fix the black screen issue.
[Eee Pad Transformer Android Development] ayr-ton:
I talked to rsalveti about the black screen issue and he replied here:

https://bugs.launchpad.net/ubuntu-tf101/+bug/1153306

More details of the working progress resolution above.

I will update you guys here when it fixed.
[Eee Pad Transformer Android Development] jholtom:
I'm rebuilding with the source tree updates now. This should fix the black screen problem, and many other things. ETA=~1 hr.

Sorry for the delay in getting this mess fixed, I've been busy with life and such....
[Eee Pad Transformer Android Development] ayr-ton:
No problem. We are all volunteers. ^^
[Eee Pad Transformer Android Development] jholtom:
Sorry that I've been slow getting both places in sync, since I'm not the biggest fan of launchpad, but since ubuntu uses it, might as well live with it for the project. I'll get you the info and update stuff over there.

EDIT: For the team name, anyone got ideas? :)

EDIT 2: So far ayr_ton its only me: github.com/jholtom and onkelbebu: https://github.com/bebu
[Eee Pad Transformer Android Development] *Detection*:
Team-UT (For Ubuntu Touch)

Team-Touch

Team-JHT (Your usernames main sounding letters)

Team-J.O (For both devs first initials)
[Eee Pad Transformer Android Development] jholtom:
Thanks!

Annnnnnndddddd. new build is uploading :)
[Eee Pad Transformer Android Development] *Detection*:
:) - Im missing out on all of this because I'm too soft to tell my girl its tough luck and I want my TF back!

What's the best way to back up saves from games shes playing so I can Nandroid > Test > Restore and she will be back to where she left off ?

Nandroid on its own is great but it misses saved data
[Eee Pad Transformer Android Development] ayr-ton:
I like more github for code repository. But launchpad is good to report bugs, translations, blueprints and the other stuff. bzr is not too good as git.

I think a good name could be tf101-hackers or tf101-ninjas, like the default groups I usually see in launchpad. Ahaha
[Eee Pad Transformer Android Development] jholtom:
The new build is up all. Happy testing!
[Eee Pad Transformer Android Development] Wdustin1:
Hmmm I'm still getting a black screen. Anybody else?
[Eee Pad Transformer Android Development] jholtom:
logcat and dmesg, thanks!
[Eee Pad Transformer Android Development] danielholm:
Sv: [Linux] [Dev] [WIP] Ubuntu Touch on the TF101 - Alpha

Check out Carbon.
[Eee Pad Transformer Android Development] 7Usam:
i dont have any problem , i just wip full partiton and install quantal* 20130221 then last version of touch 101 , keyboard resolution work :o
[Eee Pad Transformer Android Development] ayr-ton:
Same issue here.
[Eee Pad Transformer Android Development] xlenz:
Where are some steps to provide you with logcat and dmesg
[Eee Pad Transformer Android Development] *Detection*:
Cheers, looks exactly what I need :)
[Eee Pad Transformer Android Development] grsgs:
correct me if i am wrong, but that quantal is the mwc demo one isnt it ? not the current build
[Eee Pad Transformer Android Development] MassStash:
http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip

Is the development preview latest build I believe

~ TF101 on EOS4 Latest

Currently OC'ed to 1.4 with KatKernel 94
[Eee Pad Transformer Android Development] 7Usam:
Thanks MassStash that's what i mean ;)
[Eee Pad Transformer Android Development] fonix232:
Black screen here too. SBK1 TF101, 32GB model, installed with TWRP 2.3.2.3, manually. Wiped everything prior to install, wiped cache after install (ubuntu chroot is on data for sure).

Logcat: http://pastebin.com/hZ22YKcG

Dmesg: http://pastebin.com/2xZaGzYE

Hope it helps.
[Eee Pad Transformer Android Development] BlackSoil:
I am also getting black screen. I have tried re-installing a couple times with different version: 0.5, 0.6, and 0.7.

Here's my dmesg and logcat output. Any help is really appreciated :)

This seems to be the culprit to me.

<6>[ 60.654502] VFS: Can't find a valid FAT filesystem on dev mmcblk0p5.

I had that line for 0.5 and 0.7.. (didn't check with 0.6)
[Eee Pad Transformer Android Development] danielholm:
Sv: [Linux] [Dev] [WIP] Ubuntu Touch on the TF101 - Alpha

The black screen issue is from the latest build. Something went wrong during the build of ubuntu-session and a new image is baking. However, you can fix it my using apt-get upgrade on the device, from adb. Then you'll get the fix without having to re-download and re-flash.
[Eee Pad Transformer Android Development] BlackSoil:
How do I get network connection for apt-get though?

Also, do you mind checking your dmesg and tell me whether you have this line:

Can't find a valid FAT filesystem on dev mmcblk0p5.

Thanks a bunch!
[Eee Pad Transformer Android Development] fonix232:
Tried older images too, same, black screen. Will try the update way, although it is quite annoying that any time the Ubuntu release reboots, I have to reinstall the drivers for ADB to see the device.

EDIT:

Wireless connection from ADB, follow these commands:

(Sometimes works sometimes hangs on last command)

Although apt-get upgrade returns that there's no package to update.
[Eee Pad Transformer Android Development] f69m:
Here is a little trick, if nothing else works:

https://github.com/f69m/ubuntu-touch-tf300t/wiki/Use-apt-get-without-WLAN
[Eee Pad Transformer Android Development] fonix232:
A Windows solution would be nice too, I'm unable to connect to my device (using Wamp and OpenSSH client), I'm getting a bad file number error on port 22.

EDIT:

After a little bit of tinkering I successfully connected to the device via SSH, and apparently proxy is working too. But I still get the 0 update from apt-get (see image attached). Any ideas?

EDIT2:

Added the phablet-team ppa (it was a pain in the ass, add-apt-repository does not work, had to manually add the repos to the apt sources.list, then add the GPG keys, etc), it updated a few apps, and now I get the same. No screen, only backlight. Now I'm out of guesses, apparently this could be a device-specific problem (different display panel maybe?).

EDIT3:

There is also a new, preferred way to set the screen details, instead of modifying /usr/bin/ubuntu-session.d/, we need to create a new config file under /etc/ubuntu-session/, name it [ro.product.device].conf (in our case, it is tf101.conf), and reboot.

EDIT4:

Interesting thing, for one, the default framebuffer is not even used (/dev/graphics/fb0), for two, it contains the remainings of the last recovery view...

Also found out that ubuntu-session panics and crashes, with this log:

/usr/bin/ubuntu-session: 53: /usr/bin/ubuntu-session: cannot create /proc/119/oom_adj: Directory nonexistent
Stopping services...
Killing session bus...
/usr/bin/ubuntu-session: 45: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]

Point is, the process what occupies /proc/119/ does not exist, or did not run.

EDIT5:

While I couldn't figure out which process has the ID 119, apparently the removal of the resfix fixes that problem. Now I can see the other logs in ubuntu-session, but still no image. Framebuffer is still not used, even though I tried symlinking, nothing.
[Eee Pad Transformer Android Development] onkelbebu:
i already commited a fix for the new ubuntu-session format. at last we do not have to tniker with system files anymore :). As for the ubuntu-session script, i am still looking for the problem. I am able to start qml-phone-shell manually and keep it running but ubuntu-session fails

---------- Post added at 11:45 PM ---------- Previous post was at 11:23 PM ----------

try replacing /proc/$$/oom_adj with /proc/self/oom_adj know

About the fb device, i dont know whether surface linger uses it, as its mainly EGL surface
[Eee Pad Transformer Android Development] jholtom:
and i'm building for yet another time after a long week to try this again. I'll have it up soon.
[Eee Pad Transformer Android Development] fonix232:
It might be that the new images are NEON-enabled, and that's why we get the black screen+segfault (some other T2 device owners reported the same black screen problem with libc crashing)
[Eee Pad Transformer Android Development] jholtom:
That would be really a massive PITA, and it would really make ubuntu touch more exclusive to newer devices if its now required.....*fingers crossed* that this build works.
[Eee Pad Transformer Android Development] stephensonbrady:
Thanks for your hard work. It is really appreciated. I'll try the new build as soon as it's up.
[Eee Pad Transformer Android Development] jholtom:
New build is uploading now ETA~20 minutes....goo.im hates uploading....
[Eee Pad Transformer Android Development] stephensonbrady:
at the goo.im page it's saying "The file you requested was not found". could it not be finished uploading or just a bad link? thanks.

---------- Post added at 03:14 PM ---------- Previous post was at 03:06 PM ----------

ok, never mind. the link works now. i'll report back later to let you know if i'm still getting the black screen.
[Eee Pad Transformer Android Development] jholtom:
just finished uploading. try it now.

Any luck?
[Eee Pad Transformer Android Development] stephensonbrady:
just did a full system wipe and still got the black screen. I'm flashing again just to be sure though. i am also redownloading the quantal-preinstalled-phablet-armhf.zip file just to make sure its not corrupt.
[Eee Pad Transformer Android Development] jholtom:
Oh noes.... Maybe it has to do with the NEON

Logcat + dmesg?
[Eee Pad Transformer Android Development] stephensonbrady:
yep, black screen on second flash as well. Can't do a logcat at this time, not on home computer. :(

it was worth a try, and i'll still give it another go when i get the file redownloaded. thanks!
[Eee Pad Transformer Android Development] fonix232:
So indeed it is NEON :\ Damn Canonical then!

By any chance, can you rebuild the quantal-prebuilt image without NEON?

EDIT1:

Okay, traced back the exact problem. Installed the MWC image, and updated via the phablet-team repo. After reboot, instant black screen (previously it was working). So grabbed a nice logcat (it is limited though, it had no access to the Ubuntu services at all), what told me the problem:

E/linker ( 219): ics/linker.c:1598| WARNING: Skipping libc.so

The linker service for some reason skips the libc library, probably because of incompatibility. So it is not a fault on our device-side -- it is Canonical's ****-up with NEON. Will have to ask the phablet-team to either roll back the changes what enabled NEON, or create a separate branch without those changes.

Although, what is worth checking, is the two BZR repos in the build environment (they contain libhybris and phablet-api), in the ubuntu folder. It might be that they weren't updated, and thus the API mismatch causes the problem.
[Eee Pad Transformer Android Development] jholtom:
Right before I built I pulled both of the repoes so....I guess its stinking Canonica F***-up with NEON.
[Eee Pad Transformer Android Development] jholtom:
I can rebuild the canonical image, I think. I'll have to check on it though. The porting guide mentions it but it would probably take a bit to find the changes and rollback just the ones affecting us.
[Eee Pad Transformer Android Development] fonix232:
Actually, if my theory is right, all you have to do is to remove the NEON-capability flags from all the binary Makefiles.
[Eee Pad Transformer Android Development] billouetaudrey:
Hi, i wait to try it :D

Thx

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Eee Pad Transformer Android Development] ayr-ton:
x.x
[Eee Pad Transformer Android Development] jholtom:
in the canonical image or mine?
[Eee Pad Transformer Android Development] onkelbebu:
AFAIK it in there from the beginning.

I can not find any hints in the makefiles for the ubuntu libs that NEON is enabled. It would not bring any enhancements though, its only necessary for some faster vector math, think of MMX. I have not looked into it for sometimes, when i get home tonight i will perhaps look into it.
[Eee Pad Transformer Android Development] onkelbebu:
i got the latest image running again, but it will not automatically start and i dont know what the problem is yet. But now we know its not some binary incompatability :)
[Eee Pad Transformer Android Development] kenshin1388:
Sounds like this may be running well again soon. I'm gonna keep a close eye on this.
[Eee Pad Transformer Android Development] billouetaudrey:
No new for work version ? :)

Envoyé depuis mon Transformer avec Tapatalk
[Eee Pad Transformer Android Development] dosangst:
Followed aall the steps but still just a black screen:

This is the last part of the ADB output:

I/InputReader( 234): Device added: id=-1, name='Virtual', sources=0x00000301

I/InputReader( 234): Device reconfigured: id=2, name='atmel-maxtouch', size 1280x800, orientation 0, mode 1, display id 0

I/InputReader( 234): Device added: id=2, name='atmel-maxtouch', sources=0x00001002

I/InputReader( 234): Device added: id=1, name='gpio-keys', sources=0x80000101

What am I doing wrong?

Using TWRP recovery.
[Eee Pad Transformer Android Development] Dreamboxuser:
This looks very cool ... I can't wait to try it out.

I do have a few questions though.

1. What is the base image that everyone is using before building or flashing?

2. I'm running EOS4.2.2 MR1 build 175 and am wondering if I dirty flash the ubuntu overtop will that cause any conflicts?

3. Are you using the inline kernel building when you compile?

4. When you compile are you using stock cm10.1?

5. What rom did you use when you ran extract-files.sh?

I had another but i can't remember what it was...

edit: oh ya ... has anyone noticed a difference in how SBK1 and SBK2 devices run this....?

oh well.. excellent work and as i said before I can't wait to try it out.
[Eee Pad Transformer Android Development] tharonald1981:
Is there black-screen problem already solved? Or is there some way to get it working.

Maybe i did not read well but is this a dualboot ROM?
[Eee Pad Transformer Android Development] onkelbebu:
1. I always wipe system and data before flashing, to verify that really only the latest build is used

2. but flashing on top should not bring any harm.

3. We use lumpy kernel and build it with the rom

4. Dont understand what you mean sorry

5. Latest Stable CM10

i got an sbk1 device, but i dont think it should make any difference after booting the kernel.
[Eee Pad Transformer Android Development] Quintasan:
Well, instead of swearing at people you could just head over to IRC and ask people who work on that

Generally as I understood it, hardcoding NEON into Ubuntu Touch specific applications is not allowed. Maybe try upgrading hybris and phablet-platform from bzr before spinning a new image?
[Eee Pad Transformer Android Development] onkelbebu:
Sorry if i offended anyone, though i do not know what you mean.

I looked into hybris and pltform api and indeed my platform-api is 3 relevant commits behind. When i get home i will rebuild.
[Eee Pad Transformer Android Development] onkelbebu:
new build:

http://d-h.st/Ysl

use only with latest ubuntu package!:

as always i did following

wipe system, wipe data, reboot recovery, flash both zips, reboot.
[Eee Pad Transformer Android Development] billouetaudrey:
Boot fine ! ;)

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Eee Pad Transformer Android Development] MassStash:
D'you compile this?

~S-Off LTEvo; Strapped to this gnarly Sense5 port; ArcReactor

cpu0/1: 1.7ghz ¦ 192mhz ¦ sleep: 486mhz max

Intellidemand

fiops

mpdecision: off
[Eee Pad Transformer Android Development] jholtom:
added to OP under build number 0.8, thanks onkelbebu. did you commit to the repo the latest updates?
[Eee Pad Transformer Android Development] stephensonbrady:
Just curious, how long does it take you all to flash these two files?
[Eee Pad Transformer Android Development] rivenas:
sorry for the question but can you only log in as guest? Looks great by the way thanks for all the hard work........
[Eee Pad Transformer Android Development] stephensonbrady:
Hm, i'm still getting the black screen. Downloaded the updated versions of both files, wiped system, wiped both caches, and flashed.. Am I missing a step? Thanks for the hard work all of you are putting into this.
[Eee Pad Transformer Android Development] onkelbebu:
try to get me the ubuntu logs:

adb root
adb shell "for f in /data/ubuntu/home/phablet/.ubuntu-session/logs/*.log ; do echo \$f: ; cat \$f; echo ; done" > tf101.log
adb shell ls -la /data/ubuntu/etc/ubuntu-session.d/ >> tf101.log

then paste the file tf101.log anywhere i can see it