Develop Bugs

ANDROID SDK 2.0 is released

ANDROID SDK 2.0 is released, and I hope some of you devs/chefs wil use it to build a new custom rom for us Hero fans.
It has the multitouch feature for keyboard etc activated and build in.

O i want 2.0 so bad getting rid of the htc skin called sense (it's fun to have but not more then that!) and go like real android
If i knew enought to cook a (2.0) rom myself i would take this day of from work and will strugle til i get something working for the Hero
I will reward the dev who makes a working 2.0 ROM (with at least 90%+ working hardware) with 50 dollars (ofcourse for the HERO!)

Count my $20 in.

Why did you put this at the dev board? There is a similar one in the discussion board with more information.

As you can see here is where the real money is

You guys don't really seem to realize what it means when the SDK is released.
The same happened when the 1.6 SDK is released.
It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.

jaapschaap said:
As you can see here is where the real money is
Click to expand...
Click to collapse
If that's the case I might as well chip in with a twenty ;-p

It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.
Click to expand...
Click to collapse
I knew it but because of the TS his story i start believing it can be transfomrt into a ROM

dream owners using eclair rom. not the full rom but usuable. at least they can test it.

dipje said:
You guys don't really seem to realize what it means when the SDK is released.
The same happened when the 1.6 SDK is released.
It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.
Click to expand...
Click to collapse
Yes and no.
Take a look at platforms\android-2.0\images\ in your SDK.
;]
Not a rls, but at least something to play with.

adwinp said:
Yes and no.
Take a look at platforms\android-2.0\images\ in your SDK.
;]
Not a rls, but at least something to play with.
Click to expand...
Click to collapse
Those are emulator images, not made for a specific handset, therefore they don't work correctly if you flash then or repackage the contents to update.zip's!
Look at dream board and you'll see the issues with the DEV 2.0 ROM

True, then again, what do we have unyaffs for?

i just want 2.0 to come out, now. with moto droid coming out on nov. 1, it shouldnt be hard to port hopefully. im really in love with android 2.0 and i prefer it to the sense ui, it looks so much nicer

im really excited bout what htc is doing about android2 and their sense, since android2 looks nice now either ;-) hopefully we get a sexy merge of both!

Here's the build.prop, but might as well take a look the the updated apks...
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ECLAIR
ro.build.display.id=sdk-eng 2.0 ECLAIR 17704 test-keys
ro.build.version.incremental=17704
ro.build.version.sdk=5
ro.build.version.codename=REL
ro.build.version.release=2.0
ro.build.date=Thu Oct 22 01:18:16 PDT 2009
ro.build.date.utc=1256199496
ro.build.type=eng
ro.build.user=android-build
ro.build.host=apa4.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=sdk
ro.product.brand=generic
ro.product.name=sdk
ro.product.device=generic
ro.product.board=
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=ldpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=sdk-eng 2.0 ECLAIR 17704 test-keys
ro.build.fingerprint=generic/sdk/generic/:2.0/ECLAIR/17704:eng/test-keys
# end build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

[ROM] I927UCKI3 [23.09.2011][Android 2.3.5]

I927UCKI3:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.UCKI3
ro.build.version.incremental=UCKI3
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Fri Sep 23 11:16:36 KST 2011
ro.build.date.utc=1316744196
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-79
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I927
ro.product.brand=samsung
ro.product.name=SGH-I927
ro.product.device=SGH-I927
ro.product.board=SGH-I927
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927UCKI3
ro.build.hidden_ver=I927UCKI3
ro.build.changelist=601619
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927-user 2.3.5 GINGERBREAD UCKI3 release-keys
ro.build.fingerprint=samsung/SGH-I927/SGH-I927:2.3.5/GINGERBREAD/UCKI3:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I927UCKI3
ro.build.hidden_ver=I927UCKI3
ro.build.changelist=601619
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Download:
http://hotfile.com/dl/137505177/0a48afe/SGH-I927_ATT_I927UCKI3.rar.html
Pass: sampro.pl

So what's different about this ROM?

Rockwig said:
So what's different about this ROM?
Click to expand...
Click to collapse
Well, we dont know until we try it. A letter change is usually a bigger update than a letter so we know at least a few things have i changed, i hope it has the black gallery fix...

Usually when I ROM is posted, a change log is posted as well. That would be nice in this. At least so there is some idea on what people could be flashing.

Rockwig said:
Usually when I ROM is posted, a change log is posted as well. That would be nice in this. At least so there is some idea on what people could be flashing.
Click to expand...
Click to collapse
Looking at his other posts, I think its an update to the official stock firmware. Probably leaked.

Nice thanks!

Has anyone tried this rom yet? Any news on the differences?
Sent from my SAMSUNG-SGH-I927 using XDA App

This is a firmware update leaked by Samsung. It will be stock, no root, no CW Recovery. All carrier bloatware will be in place.
Assuming this works the same as the I897 leaks, you'll need Odin to install it.
Przekret is great posting the newest "official" leaks so when you see him posting ROMs it's safe to assume it'll be a stock leak. He has been great in providing leaks for the I897 devs and us ROM flashaholics.

Thanks so much.It is always nice to see new updates and people willing to share with us ;-)

is this the latest stock rom?

As far as I know the latest version is 2.3.6.

shinydesert said:
As far as I know the latest version is 2.3.6.
Click to expand...
Click to collapse
Can u provide me a link or a system dump?i m gonna make a custom rom.

I was able to download it last Friday night,but right after that I changed the kernel and installed a rooted 2.3.5 version.
Last night I checked for new updates and the device downloaded the new update but the installation failed,if you think there is a way to find those new files I will be more than glad to dig into the phone.

any noticeable difference b/w the 2?(performance,i mean)
u shud have had a nandroid backup

sakindia123 said:
any noticeable difference b/w the 2?(performance,i mean)
u shud have had a nandroid backup
Click to expand...
Click to collapse
I don't think 2.3.6 added anything significant other than a really minor 'feature' so I suggest working with 2.3.5 if no one comes forth with a 2.3.6 dump soon.

vil33 said:
I don't think 2.3.6 added anything significant other than a really minor 'feature' so I suggest working with 2.3.5 if no one comes forth with a 2.3.6 dump soon.
Click to expand...
Click to collapse
so i started makin a rom based on this.
Ps-U have a hell lot of bloatware!

This is a stock firmware leak...that alone should tell you it will have all of at&t's bloatware in it.

Rogers ROM is a better starting point in my opinion. It's very similar to AT&T but there is manual operator setup in networks and delivery reports for messages. Both features are missing in AT&T ROM but are quite useable.

too bad.i already made the rom as i couldnt find any other

SGH-I927/ATT/I927UCKI3/I927ATTKI3/I927UCKI3
from this (2.3.5) somebody have 4 files version with pit?
I looking for...!!!

[Q] ICS port from neo L ?

Hi,
Will we have an ICS port from the Xperia Neo L ?
I read that this phone has the same hardware as Xperia Play
Just go on (talk.sonymobile.com/message/238221)
Thanks.

Max77230 said:
Hi,
Will we have an ICS port from the Xperia Neo L ?
I read that this phone has the same hardware as Xperia Play
Just go on (talk.sonymobile.com/message/238221)
Thanks.
Click to expand...
Click to collapse
Why would we need one.
Sent from R800x

it should have some improvements, will try and port in a few minutes
if i get a ftf or systemdump

hi nick,
I've found the .479 neo L firmware, it runs in setool2
(sonyericsson-world.com/files/file/3047-4-1-b-0-479-fsp-world-for-xperia-neo-l-mt25i-setool2/)
You need to create an account, and download is long (150kbps), but at the end you'll have your .sin_file_set firmware file, to test when you can.
Thanks.
There's an other file who contains kernel in (sonyericsson-world.com/files/file/3024-4-1-b-0-479-app-sw-generic-for-xperia-neo-l-mt25i-setool2/)
I've unpack files (with 7-zip) and create a .ftf bundle with flashtool and you should have a ~400Mb file.

Very good news !!!
I have flashed .479 neo L system and partitions (so no kernel and baseband, just software), and everything works but Wi-Fi. UI is very smooth. I will edit some news later.
Cheers.
What's going if i flash neo L baseband ? (flashed new baseband, it's -74, works well)
Okay, now with the modules from DooMKernel wifi works very well, but no hotspot.
Tested gamepad on Experiment 13 and all buttons works

Max77230 said:
Very good news !!!
I have flashed .479 neo L system and partitions (so no kernel and baseband, just software), and everything works but Wi-Fi. UI is very smooth. I will edit some news later.
Cheers.
What's going if i flash neo L baseband ? (flashed new baseband, it's -74, works well)
Okay, now with the modules from DooMKernel wifi works very well, but no hotspot.
Tested gamepad on Experiment 13 and all buttons works
Click to expand...
Click to collapse
And what happens if we flash the kernel? I never tried...

Wow, I don't get something Can someone please explain? How come we are able to just flash the neo l firmware and its seems more or less everything works? Is it because the Neo L specs are basically identical to the Play's ?

It would be great if DooMLord can make a custom kernel with the .479 sources that was provided by sony last week (developer.sonymobile.com/wportal/devworld/downloads/download/41b0479tarbz2). I think the ROM will be more optimize (Wi-Fi), and it's a real gift by sony as the fact is that the MT25i il a clean copy of the PLAY without gamepad.

@fareed
It's because neo L has the zeus hardware, just in rev.2 (no gamepad), so that's why i said that if we make a custom kernel with the neo L sources we can get all working, cause at the moment i suffer wifi issues (need doomlord modules cause of no stock kernel, and no hotspot).
@vokal
I will try to flash it tomorrow and i will send you the result.
Edit : wow, amazing ! incredible ! it seems that gamepad is integrated, i tried it on PES2012 and it works, also L and R.
I think that just the touchpad doesn't work. Wait for a patch, i will look at xDark work.
So anyone Know where i can upload my ROM to share it ?

Max77230 said:
@fareed
It's because neo L has the zeus hardware, just in rev.2 (no gamepad), so that's why i said that if we make a custom kernel with the neo L sources we can get all working, cause at the moment i suffer wifi issues (need doomlord modules cause of no stock kernel, and no hotspot).
@vokal
I will try to flash it tomorrow and i will send you the result.
Edit : wow, amazing ! incredible ! it seems that gamepad is integrated, i tried it on PES2012 and it works, also L and R.
I think that just the touchpad doesn't work. Wait for a patch, i will look at xDark work.
So anyone Know where i can upload my ROM to share it ?
Click to expand...
Click to collapse
I can confirm that the System partition does in fact install and boots fine, but I allways get Keyboard FC's and alot of stuff didnt got installed :S
Edit: here is the Build.prop, found some funny things:
Code:
##### Merging of the /util/data/semc_kernel_time_stamp.prop file #####
ro.build.date=Thu May 24 16:12:14 2012
ro.build.date.utc=1337868734
ro.build.user=BuildUser
ro.build.host=BuildHost
##### Final patch of properties #####
ro.build.product=MT25i
ro.build.description=MT25i-user 4.0.4 4.1.B.0.479 IL5_3w test-keys
ro.product.brand=SEMC
ro.product.name=MT25i_1265-5721
ro.product.device=MT25i
ro.build.tags=release-keys
ro.build.fingerprint=SEMC/MT25i_1265-5721/MT25i:4.0.4/4.1.B.0.479/IL5_3w:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1265-5721
ro.semc.version.cust_revision=R2I
persist.ro.ril.sms_sync_sending=1
ro.settings.apn.lock=ä¸*国移动互联网,ä¸*国联通互联网,ä¸*国移动MMS,ä¸*国移动WAP,ä¸*国联通MMS,ä¸*国联通WAP
#########################################################################
ro.config.ringtone=xperia.ogg
ro.config.notification_sound=notification.ogg
ro.config.alarm_alert=alarm.ogg
ro.semc.content.number=PA1
################# Updating of the SW Version #################
ro.semc.version.fs_revision=4.1.B.0.479
ro.build.id=4.1.B.0.479
ro.build.display.id=4.1.B.0.479
##### Values from product package metadata #####
ro.semc.product.model=MT25i
ro.semc.ms_type_id=PM-0110-BV
ro.semc.version.fs=WORLD-i
ro.semc.product.name=Sony Xperiaâ„¢ neo L
ro.semc.product.device=MT25
ro.product.model=MT25i
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.incremental=IL5_3w
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.type=user
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony Ericsson
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.characteristics=default
# end build properties
#
# system.prop for phoenix
#
# Notify the system that the RIL only signals once
ro.telephony.call_ring.multiple=0
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
ro.semc.timescape_keys=Sony_Ericsson_Xperia_PLAY
#Automount restored because of the exclusion backcover HW key operation.
#ro.product.sdcard.automount=0
ro.semc.sols.product-code=107
ro.semc.sols.company-code=5
# Disable strict mode checking
persist.android.strictmode=0
# Constant values for Battery test in Service menu
ro.semc.batt.capacity=1500
ro.semc.batt.test.z_threshold=50
ro.semc.batt.test.min_level=70
#Default values/Locales for the hiding languages feature
ro.product.locale.excluded=ar_EG ar_IL fa_IR iw_IL
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=framework/SemcGenericUxpRes.apk
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-sonyericsson
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.semc.xloud.supported=true
ro.sf.lcd_density=240
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.semc.dashboard.xperiaplay=true
ro.semc.dashboard.searchuri=http://pss.dl.playstation.net/pss/content/list.html
ro.usb.pid_suffix=17C
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.drm.active.num=4
ro.drm.active.0=semc,1
ro.drm.active.1=cmla,0
ro.drm.active.2=viaccess,0
ro.drm.active.3=marlin,1
Also found some xperia play stuff on framework
Going to update my NeoS rom with these

Ohh thanks. Media fire is good for hosting but I have my own website and hosting so I'd be more than happy to host your files. Just pm me for details

Vokal,
For the keyboard FC, I've solve it, do a full Wipe,(data+dalvik+cache), and I've flash vendor partition for uninstalled apk's.
resume for people who want to try this ROM :
Fresh install : Do a full wipe
- flash system + userdata+vendor(partitions)
- if you want more you can flash all but kernel (I found that the new -74 baseband has a better signal reception).
@fareeed : How can I send you my files ? i'm okay but does it'll cost me anything ? cause i'm only 17 and i don't have something to pay.

Max77230 said:
Vokal,
For the keyboard FC, I've solve it, do a full Wipe,(data+dalvik+cache), and I've flash vendor partition for uninstalled apk's.
resume for people who wnt to try this ROM :
Fresh install : Do a full wipe
- flash system + userdata+vendor(partitions)
- if you want more you can flash all but kernel (I found that the new -74 baseband has a better signal reception).
@fareeed : How can I send you my files ? i'm okay but does it'll cost me anything ? cause i'm only 17 and i don't have something to pay.
Click to expand...
Click to collapse
Baseband -74 works Great! flashed the rom wih the new xperia game launcher it didnt installed, the old one works fine, going to test if the touchpads work on minecraft. Does anyone know if they worked on ICS Beta? I mean in Minecraft.
Thanks!

vokal1992 said:
Baseband -74 works Great! flashed the rom wih the new xperia game launcher it didnt installed, the old one works fine, going to test if the touchpads work on minecraft. Does anyone know if they worked on ICS Beta? I mean in Minecraft.
Thanks!
Click to expand...
Click to collapse
Vokal maybe we could use the sources from Neo L ICS 4.0.4 and put them into our ICS 4.0.4 roms to increase stability and speed.... If this iss faster that is.
If only I could use my phone I would of done this myself.

I've flash the new kernel. Wifi works without modules but always no hotspot, and a new problem. Luminosity is so low when is set to automatic. So it looks the same but in waiting for kernel optimizations, i roll back to ICS beta kernel.
PS : the camera image is also inverted, and no more gamepad !(Edit : No more root also)
@Vokal : Yes, Touchpads worked on Minecraft in ICS beta.

Max77230 said:
I've flash the new kernel. Wifi works without modules but always no hotspot, and a new problem. Luminosity is so low when is set to automatic. So it looks the same but in waiting for kernel optimizations, i roll back to ICS beta kernel.
PS : the camera image is also inverted, and no more gamepad !(Edit : No more root also)
@Vokal : Yes, Touchpads worked on Minecraft in ICS beta.
Click to expand...
Click to collapse
flashed the camera from the ICS beta and its fixed now

Oh, I've drive you in error, hotspot works !
So i think i've finish for today and i'm really happy for the fact that everything works with ICS beta kernel (but no touchpads) and it's the best rom i've seen on XPlay, very smooth. I'll give a try on Antutu before sleeping.
Edit : I managed to get a 3100 score in antutu at stock, with a very good score in 3D, this ROM looks promising, better than xDark ICS.
Tomorrow i will look at his touchpad patch, and someone can explain to me what's the incidence of mt25i in build.prop, as it would be r800i ?

Max77230 said:
Oh, I've drive you in error, hotspot works !
So i think i've finish for today and i'm really happy for the fact that everything works with ICS beta kernel (but no touchpads) and it's the best rom i've seen on XPlay, very smooth. I'll give a try on Antutu before sleeping.
Click to expand...
Click to collapse
WOOOOOW flashed the whole firmware, including the kernel and it works!!!!! yeah!!!!!

Well, it smells good for locked bootloaders ! Have you the same problems as me ? (luminosity, gamepad, camera-seems that you've fixed it).

Max77230 said:
Well, it smells good for locked bootloaders ! Have you the same problems as me ? (luminosity, gamepad, camera-look like you've fixed it).
Click to expand...
Click to collapse
yeah the big problem is to gain root now, so people with locked bootloaders can flash fixes or custom roms based on stock
Edit: Just Got Root and Clockworkmod!

[ROM][WIP][kexec] Ubuntu with Freedreno!

I've been working on getting Ubuntu running on my Sprint Galaxy S3 using the same method I used on my Epic 4G - kexec from recovery loading the root filesystem off a partition on an SD card.
What I've done so far:
* Found a kexec loader to boot into a custom kernel, which is required for booting off an SD card, among other things;
* Compiled a custom kernel with KGSL DRM support enabled for Freedreno;
* Built a minimal Ubuntu 13.10 armhf rootfs and compiled the Freedreno DRM/DDX/Mesa Gallium driver with changes to support the Adreno 225 and stub occlusion query (possibility of full dekstop OpenGL 2.1 support!);
* Got X11 working with USB keyboard, touchscreen, and fbdev. Still working on getting the Freedreno DDX to load.
I still get a kernel oops with the camera driver (http://pastebin.com/egZbxsED), but it apparently doesn't affect stability or cause reboots anymore.
Working so far:
* USB Host - only tested with a keyboard, but other input/storage/audio/video devices should also work.
* Framebuffer console - thanks castrwilliam!
* Touchscreen works with X.org fbdev driver and the following added to /usr/share/X11/xorg.conf.d/11-evdev-quirks.conf:
Code:
Section InputClass
Identifier "Touchscreen"
Driver "evdev"
MatchProduct "sec_touchscreen"
EndSection
* Power and volume buttons
Untested:
* Bluetooth - might need firmware
* Sensors - should work just fine
* Home, menu and back buttons should work but probably need mapping
Unlikely to work due to proprietary Android-only blobs:
* Camera
Kernel config changes:
# IMPORTANT: remove the line that says "depends on !MSM_KGSL_DRM" from drivers/gpu/msm/Kconfig:70
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_VT_CONSOLE=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_DRM=y
I may eventually post a pre-built kernel, but if you don't know how to compile a kernel from source, this guide is not for you.
Likewise, if you don't know how to prepare an armhf Ubuntu root filesystem, this guide won't help much.
After building the kernel, copy arch/arm/boot/zImage to your SD card along with the attached zImage.zip (CWM-flashable kexec loader).
It might need modifications (META-INF/com/google/android/updater-script) depending on how you have your card set up.
UPDATE: Unfortunately, this phone hasn't been a good fit for me. I never got very far booting Ubuntu or Freedreno, so I decided to sell it.
For anyone still interested in this project, I believe castrwilliam has the required patches.
When I get my next Snapdragon device (either the new Nexus 7, a Nexus 4, a Galaxy S4, or another phone with Adreno 320 graphics), I will post the Mesa patches for occlusion query support. Sorry I wasn't more helpful with this device.

Added to favourites, I'll see what I can do with it over the weekend
Sent from my SPH-L710 using Tapatalk 4 Beta

Great work. Good luck debugging.
Sent from my SPH-L710 using xda app-developers app

Maybe taking a look at how Motorola worked Ubuntu, in a way, with Webtop that came on the Photon. The Photon has the integrated Ubuntu-based 'Webtop' application from Motorola. The Webtop application is launched when the phone is connnected to the external display through Laptop dock or HD multimedia dock. In Webtop mode, offering similar user interface of typical Ubuntu desktop, the phone can run several applications on external display such as Firefox web browser, SNS clients and 'mobile view' application enabling total access of the Photon and its screen. In September 2011, Motorola released the source code of Webtop application at SourceForge.
I know it's not an app you're trying to use but it may help in finding how to work some of the kinks you have. I hope that helps

Hi, I'm the person maintaining Ubuntu currently for HP Touchpad (http://forum.xda-developers.com/showthread.php?t=2225462) (which also uses an MSM SOC.) It's starting to show its age... I'm trying to get this to where you have it currently on a Verizon S3 / d2vzw (obviously, kexec'ing into a Verizon kernel instead.) Maybe we could collaborate?
Currently I have the KT747 kernel (kexec host support as well as guest) (compiled as a zImage. If you can provide me with access to the patches you have for freedreno and hopefully also an initramfs image (I'm going to mod the HPTP rootfs, so no need there)... I'd love it.

My only modifications to the kernel so far are the ones I mentioned in the OP and three of Rob Clark's Freedreno commits from the mako-kernel branch of kernel-msm on his GitHub - namely, "kgsl: drm: remove checking on 'active'", "video/msm: add true ARGB", and "kgsl: fix null ptr on cache flush".
At one point I had X11 working with freedreno displaying the GNOME background, but the screen blanked after 10 seconds and I couldn't recover from that. Unfortunately, after experimenting with different kernel config options, I lost that semi-working configuration and the GPU started to page fault, sometimes displaying a corrupted screen and sometimes rebooting before displaying anything.
Believe me, I've been working on this for weeks, and it's very frustrating that it doesn't even sort of work. My minimal modifications to Mesa to get it to recognize the Adreno 225 are highly unlikely to be the cause of the problems, and I highly doubt the differences between the 220 and 225 are to blame since it was working at one point. It's a one liner, figured out from from freedreno/mesa issue #2.
Castrwilliam, the initramfs is the least of your worries. I don't use one, since its only function is to display the Plymouth splash, which doesn't work anyway.

gTan64 said:
...
Castrwilliam, the initramfs is the least of your worries. I don't use one, since its only function is to display the Plymouth splash, which doesn't work anyway.
Click to expand...
Click to collapse
Yeah, I realized how you were doing this after looking at the kexec script. I was trying to boot from Android, not recovery, and was under the impression you had put a disk image on external SD, and then made the initramfs loop-mount that and boot from it... but now I see you partitioned it.
It's a shame you don't have your original config, I'll try to get it booting again on my end. I remember doing something like this a while back, where I made like 10 differently configured kernels at once, and tested them each in turn. I imagine the ramconsole would help a good bit so that I could look a how far we're getting. (The touchpad has its own version of that, which you can read directly from the bootloader (bootie.) Then again, it also has LVM volumes for storage instead of actual partitions (except for boot) - which makes it uber easy to boot lots of OSes.)
Currently I'm not doing too well. I remember that kexec did work at one point on d2vzw hardware but I'm assuming that it still does now (new bootloaders, 3.4 kernels, ...) I do kexec -e, the reboot happens, I see the Samsung bootloader screen, then the screen blanks for like 5 seconds and it reboots again - back into android.

castrwilliam said:
I imagine the ramconsole would help a good bit so that I could look a how far we're getting...
the screen blanks for like 5 seconds and it reboots again - back into android.
Click to expand...
Click to collapse
The RAM console should be enabled by default, so check /proc/last_kmsg once Android boots back up.
It could be something simple like the root filesystem not mounting, either due to how you partitioned the card or not having time to settle, hence rootwait. Or it could be something else. I haven't gotten any useful output in /proc/last_kmsg with the framebuffer console enabled, so make sure that's disabled unless you want a headache and a psychiatrist visit.
Unfortunately, I've spent way too much energy trying to debug the GPU page fault, and I probably won't have much time to work on it after next month. I want this bug dead and forgotten, so more eyes would be great!

X11 works (shows something on screen) with the X.org "fbdev" driver. I can't reproduce anything with "freedreno" (or "modesetting", which I accidentally loaded at one point...)
The touch screen doesn't respond, but the power key works and brings up a shutdown dialog.
Screenshot attached. I used the 13.04 Touchpad rootfs with some modifications...

Okay, you can get the fbcon working by either loading it as a module during boot OR changing its "module_init" macro in drivers/video/console/fbcon.c to "late_initcall".
Picture attached. Sorry for blurriness, I don't have an actual digital camera, only what's on my sig. This should make debugging a bit easier.

Nice to see some more freedreno development on android phones
I'm using freedreno with a slightly different approach, starting it directly from android on a chrooted shell, which is a lot more easier to debug.
The kernel needs some fixes from the mako branch and the following configs:
Code:
CONFIG_DEVTMPFS=y
CONFIG_VT=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_2D=y
CONFIG_MSM_KGSL_DRM=y
Rob Clark (the maintainer of freedreno) has been working on his own kernel driver for adreno gpu:
https://github.com/freedreno/kernel-msm/commits/ifc6410-drm
This would be a nice addition/replacement for the current qualcomm gpu driver.

Wootever said:
Nice to see some more freedreno development on android phones
I'm using freedreno with a slightly different approach, starting it directly from android on a chrooted shell, which is a lot more easier to debug.
The kernel needs some fixes from the mako branch and the following configs:
Code:
CONFIG_DEVTMPFS=y
CONFIG_VT=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_2D=y
CONFIG_MSM_KGSL_DRM=y
Rob Clark (the maintainer of freedreno) has been working on his own kernel driver for adreno gpu:
https://github.com/freedreno/kernel-msm/commits/ifc6410-drm
This would be a nice addition/replacement for the current qualcomm gpu driver.
Click to expand...
Click to collapse
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?

Semi Working Freedreno/X11
castrwilliam said:
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?
Click to expand...
Click to collapse
HEY, look what I did?!
(There are a lot of patches req'd to get this far. Even at this point, there's a weird bug where the cursor loops across the edge of the screen and windows overlap themselves. If you want to know, I'll elaborate in a further post, otherwise, let's get that touchscreen working for release!)
Thanks to Rob Clark (again, the author of freedreno) who helped me get this far on his IRC channel at Freenode.

castrwilliam said:
HEY, look what I did?!
(There are a lot of patches req'd to get this far. Even at this point, there's a weird bug where the cursor loops across the edge of the screen and windows overlap themselves. If you want to know, I'll elaborate in a further post, otherwise, let's get that touchscreen working for release!)
Thanks to Rob Clark (again, the author of freedreno) who helped me get this far on his IRC channel at Freenode.
Click to expand...
Click to collapse
Are we keeping track of all the necessary patches? I'm on https://github.com/CyanogenMod/android_kernel_samsung_d2, branch cm-10.2_kgsl, with the per-process pagetable hack, the "active" kgsl_drm fix, Adreno 225 case in Mesa (freedreno_screen.c), and my stub occlusion query hack. I wasn't on #freedreno when Rob Clark pointed out the libdrm bug I heard about from the Wiki - did you fix that? I'm still getting the assert crashes.
I'll be on #freedreno at some point tomorrow.

gTan64 said:
Are we keeping track of all the necessary patches? I'm on https://github.com/CyanogenMod/android_kernel_samsung_d2, branch cm-10.2_kgsl, with the per-process pagetable hack, the "active" kgsl_drm fix, Adreno 225 case in Mesa (freedreno_screen.c), and my stub occlusion query hack. I wasn't on #freedreno when Rob Clark pointed out the libdrm bug I heard about from the Wiki - did you fix that? I'm still getting the assert crashes.
I'll be on #freedreno at some point tomorrow.
Click to expand...
Click to collapse
I got this to work by using a fairly old libdrm, but a new DDX (xf86-video-freedreno). I haven't fixed the assert bug on the newer ones.
You need to patch the DDX's msm-device.c to set the width to 736 (has to be a multiple of 32), and then disable/comment out/delete where it calls the mode-set function (there's a comment about making xrandr happy in the right place.) I can make a patch soon, but I have a feeling that this is what made the other bug happen with the looping cursor.
edit -- I fixed the looping cursor. A patch is attached...
Youtube video of it working: http://www.youtube.com/watch?v=rh9wmmYuKxY
Tips:
Set the firnware path for the dhd (wi-fi) driver to /system/etc/wifi/bcmdhd_sta.bin (WITHOUT the _b2 buffix, it will be added by the module). Set the nvram file to /system/etc/wifi/nvram_net.txt. Then, add the Android partitions to the /etc/fstab (mmcblk0p14 is system.)
apt-get install xserver-xorg-input-multitouch and then add a config file under /usr/share/X11/xorg.conf.d/ to get the touchscreen working. It will act like a laptop trackpad. You MUST use the multitouch driver. "evdev" will segfault the server on any touch. Note that you can match the TS in an InputClass with its udev name, "sec_touchscreen".
The date that I compiled the working Freedreno libdrm was the date that Ubuntu 13.04 was released. I'm working on narrowing it down to a Git SHA1 revision. I used Rob Clark's repository, not the freedesktop one.
Use the master branch of the DDX, sorry for the earlier confusion.
For battery savings, you might want to cherry pick the DPMS commit from the a3xx branch of the DDX.

castrwilliam said:
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?
Click to expand...
Click to collapse
There are two binaries you can execute with adb shell stop/start that kills and restart the android proccesses, allowing access to the framebuffer.

Okay, so 2-D does work with my mods, but I just tried 3-D last night (ran es2gears with the Adreno 225 mod in place on mesa) and the pagefaults returned.
I did notice something about your pagefault reboots, though: they shouldn't necessarily be happening, it's a NULL pointer dereference that can be fixed in the handler by doing this in drivers/gpu/msm/kgsl_iommu.c (function is kgsl_iommu_fault_handler):
Change
Code:
curr_context->pagefault = 1;
curr_context->pagefault_ts = curr_global_ts;
To:
Code:
if (curr_context) {
curr_context->pagefault = 1;
curr_context->pagefault_ts = curr_global_ts;
}

So anyone got any updates for this if not i will start building upon what is there if it is ok
Sent from my SCH-S960L using xda premium

allenjthomsen said:
So anyone got any updates for this if not i will start building upon what is there if it is ok
Sent from my SCH-S960L using xda premium
Click to expand...
Click to collapse
I guess it is OK. Hopefully you can make a dent in this development. Keeping my eye on this thread.

No longer developing for this phone
Unfortunately, this phone hasn't been a good fit for me. I never got very far booting Ubuntu or Freedreno, so I decided to sell it.
For anyone still interested in this project, I believe castrwilliam has the required patches.
When I get my next Snapdragon device (either the new Nexus 7, a Nexus 4, a Galaxy S4, or another phone with Adreno 320 graphics), I will post the Mesa patches for occlusion query support.

[Q] Why did Asus compile a 32 bit Lollipop ? As anyone tryed to build a x86_64 bit ?

I don't get why Asus is targeting x86 for their build of android while having a x86_64 kernel build.
It can't be from Intel or drivers since it's all kernel side so the only thing is their Zen UI apps i guess.
Now if i had a better computer and a faster internet connection i would try to build an x86_64 version myself but so far i've only managed to build the kernel and it wasn't pretty on my 5 year old laptop.
Looking at the .prop files i see
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
Click to expand...
Click to collapse
same lines in the last x86_64 atom emulator
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,x86
ro.product.cpu.abilist32=x86
ro.product.cpu.abilist64=x86_64
Click to expand...
Click to collapse
So yeah is Asus too constrained to support both x86 and x86_64 (though in theory their should be no difference, just a few different options in the build for x86_64 SoC) or is it a technical problem ?

roadtoai said:
I don't get why Asus is targeting x86 for their build of android while having a x86_64 kernel build.
It can't be from Intel or drivers since it's all kernel side so the only thing is their Zen UI apps i guess.
Now if i had a better computer and a faster internet connection i would try to build an x86_64 version myself but so far i've only managed to build the kernel and it wasn't pretty on my 5 year old laptop.
Looking at the .prop files i see
same lines in the last x86_64 atom emulator
So yeah is Asus too constrained to support both x86 and x86_64 (though in theory their should be no difference, just a few different options in the build for x86_64 SoC) or is it a technical problem ?
Click to expand...
Click to collapse
Intel z3560,z3580 are x64 bit cpu,so it supports both x86 and x64bit,in theory x64bit os is faster in processing,more memory bandwidth,better app operation[if app is optimized] ,supports more than 4gb ram...but answer for why asus didnt use x64bit OS i dont know,i asked them,even they dont know,they said we might give in future,..maybe @Asus_USA can give answer