Develop Bugs

[MOD] Taste Nexus S Gingerbread on Galaxy S v6 - network (unstable) - tech DEMO

UPDATE statement.
As original author for this thread, videos and first demos, I'm not currently working on the Gingerbread port these days (heavily busy working on Voodoo sound improvements).
It doesn't mean I lost interest in it, only that I miss time at the moment.
CyanogenMod team work on a serious port of Gingerbread for Galaxy S, witch won't be just a technical demo like the original spirit of this one.
Of course, such goal requires a lot of work, dedication, and also some calm.
There is a lot of natural interest about Gingerbread on Galaxy S, and it's perfectly understandable too.
Giving an ETA until the porting work is done or some major advance is made would be dishonest.
It means that not asking for ETA will be appreciated. However, you're welcome discussing other aspects.
If you want more technical insights and a few updates by most actives developers for this port, i would recommend to follow:
http://twitter.com/CMSGSTeam
http://twitter.com/codeworkx
http://twitter.com/dumdidum
[list needs to be completed, thanks for input]
Thank you!
Original post:
Galaxy S with Nexus S kernel - Booting Nexus S Android Gingerbread
Videos are here:
http://www.youtube.com/supercurioxda
Early demo Releases - V6
Requirements
You must be root on your phone
Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.
Verizon Fascinates are not yet supported - Epic4G will require a lot more development.
You must have proceed to complete backups before
Some busybox installation is also useful for tar.
Another Important note
Be sure you have access to the download mode using the 3 buttons combination.
If you don't, it will be extremely difficult (even if in theory not impossible) to to flash another kernel back.
Steps:
1/ Download this system dump on your sdcard:
system dump archive
2/ Run these commands
Code:
adb shell
su
cd /data
mkdir gingerbread
cd gingerbread
busybox tar zxvf /sdcard/system-dump-as-root.tar.gz
busybox cp -a /efs efs
sync
reboot download
3/ unzip the attached nsonsgs.tar.zip to nsonsgs.tar
4/ flash the kernel with Odin or Heimdall - no pit - no re-partition
Watch Gingerbread boot on your phone !
How do I get back?
Everything is still in place on your phone - no harm done.
All you need to do is to flash your preferred custom (that support Ext4 obviously) Kernel back on your phone
What's about this port:
- It uses the Nexus S kernel compiled from sources
- It runs the exact /system image release, we dumped on IRC from an actual Nexus S device.
Am i French ?
Now you don't have any doubt anymore
Which filesystem ?
This early preview runs on Ext4. no RFS at all, the kernel don't support RFS.
Does everything work ?
Nope, but there are progresses.
Don't work: GPS / Voice / camera
Work: everything else: like sound, GL acceleration etc
Will it work ?
I think most of it will work after countless hours spent on it.
Is it flashable with Odin ?
Won't be so easy, but it's one of the goals
Do you work alone ?
Credits go the IRC channel #NSdev on freenode, and now a team formed regrouping most Captivate/Vibrant/Fascinate/I9000 developers and CyanogenMod team, with Kernel and ROM developers and also newcomers.
When will this/that work ?
The only honest answer is: there is no answer.
Please don't ask for ETA, don't pressure developers, they need peace of mind
Is this Open Source ?
Everything is fully published under an open source license
Latest initramfs: https://github.com/project-voodoo/nsonsgs-initramfs
Kernels: https://github.com/galaxys-kernel
Who are the actual contributors to the code?
For the kernel, you can follow works here : who / when.
https://github.com/galaxys-kernel/linux_samsung_galaxys_port/commits/galaxys-port
As it is a team work, sometimes it's not the guy who had the idea who commits the code, but still
Articles:
http://www.engadget.com/2010/12/18/samsung-galaxy-s-receives-gingerbread-port-right-from-the-nexus/
http://briefmobile.com/samsung-galaxy-s-android-2-3-gingerbread
And a lot of other ones now!
Versions:
V6
- Easy root. You only need to install Superuser app from Market.
Downloads :
Kernel you can flash with Odin / heimdall / kernel flashing apps
ClockWorkMod unsigned update.zip
V5
- Wifi semi-working (tend to crash the phone on Wifi sleep timeout)
- Calls working but no DATA for me (coolya had data, which means: erratic) - voice not tested.
- kind of laggy, but there is a lot of headroom.
- GPS working only by Wifi/Triangulation networking - No satellites.
Fantastic job by coolya who did most of the advancement, for Wifi, baseband and also OneDRAM partitions configuration. Really really awesome work.
We were so lucky the snow forced him to stay at home instead of going to work
This time you can really start to play with the phone, install apps, surf on the Internet all this with Gingerbread! kind of cool
V4
Buttons fixed thanks to the contributions of xcaliburhands, pawitp, fenfir
No need to create some directories manually anymore.
Kernel available as ClockWorkMod recovery update.zip - be sure you have access to 3 buttons !
V3
SDcard now works
- As internal storage
- As USB storage
V2
improved pre-init script and mounts:
no more insufficient space
improved dual-boot solution
faster boot
faster disk I/O
V1
initial
Edit: we started working now as a team, joining XDA forces with CyanogenMod.
Gingerbread CM is AOSP, which means the port will be the real Google experience, using clean source modified just as we need to.

Holy moly..... I can't wait! Thanks Curio (and any other devs)!
I wonder how fast this ROM will be! 2.2.1 is smooth as butter as it is!

That was quick! I saw the title before saw who posted I thought it was just going to to someone asking for eta's... Nice work!

LOL are u serious? Doc was trying to run it the other day but couldn get pass the boot screen haha

Let's wait patiently for the port, and let the dev do his work.
Sent from my GT-I9000 using Tapatalk

Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App

We're waiting...

heymanator said:
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Patience, it will come to all in time
Sent from my GT-I9000 using XDA App

heymanator said:
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
What works on one GSM Galaxy S works on every GSM Galaxy S with only minor tweaks.

Time to dust off my i9000 and get it out of the drawer.

why was it in the drawer?

boodies said:
why was it in the drawer?
Click to expand...
Click to collapse
Cause I was fed up GPS not working among other things... been using my Desire for about 6 weeks. Boy, definitely missed this screen, and Swype... but not the lag.

I want the package more than the video!

I think I just wet myself!

in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...

Red John said:
Cause I was fed up GPS not working among other things... been using my Desire for about 6 weeks. Boy, definitely missed this screen, and Swype... but not the lag.
Click to expand...
Click to collapse
If your GPS doesn't work and you have lag then it is your fault for being too lazy to fix it
Sent from my GT-I9000 using XDA App

TettZor said:
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Click to expand...
Click to collapse
That made my day lol
Sent from my GT-I9000 using XDA App

TettZor said:
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Click to expand...
Click to collapse
HAHAHA I'm hoping Samsung hire some of these devs! And I guess there's not much use of a "Nexus S" now that the Galaxy S is able to run what the Nexus S runs.

Waiting waiting.....
Sent from my bad-ass i9000

Looks like it will be out later.
supercurio François Simond
But I guess that in about than 1 day I will publish a method, and you will be able to boot #Android #Gingerbread on your #GalaxyS
1 hour ago Favorite Retweet Reply
»
François Simond
supercurio François Simond
Ok the video will come later, no ETA
1 hour ago Favorite Retweet Reply

androbada

Hi all
I heard about this some time ago, but now there is silent. Could somebody tell me about progress in this project. Thanks in advance

androbada is fake,
about the current REAL android porting:
you should read the irc logs
there are 3 diferent builds
- oleg_k one : galaxyS build booting from jtag, most advanced one in theory but unusable without JTAG box
- emulator kernel one: stable but no drivers no screen etc booting by FOTA hole
-galaxyS kernel booting from FOTA hole, services restating. only adb in recovery mode working
in resume anything usefull for normal pple for now.

mushrom said:
you should read the irc logs
there are 3 diferent builds
- oleg_k one : galaxyS build booting from jtag, most advanced one in theory but unusable without JTAG box
- emulator kernel one: stable but no drivers no screen etc booting by FOTA hole
-galaxyS kernel booting from FOTA hole, services restating. only adb in recovery mode working
in resume anything usefull for normal pple for now.
Click to expand...
Click to collapse
clarification: pretty much NONE of the work being done by the people here (oleg k, rebellos, mijoma etc) is related to androbada, the androbada project was a SCAM. Please do NOT relate them.
additionally, all current kernel builds are also built from Olegs kernel source

lol thats true, i didnt remember i thought he was just asking for android on wave...
btw... i think someone said something about an emulator kernel...

anghelyi managed to get stable services by copying the android filesystem *from* an android emulator, he couldn't get the display to work though, best he could do is see the gui by capturing screenshots from the phone through Dalvik Debug Monitor, best i've done without files from the emulator is screenshots of the Bootlogo's and i9000 looping boot animation, which also doesn't appear on the Wave's display.

[Gen9] ICS build Alpha 1, now works for A80 and A101.

Hi Guys,
*edit*
Teaser time is over, here is the build.
Version alpha 1 is here, nothing new for A101, it just adds touchscreen for A80 owners.
Preliminary warning: this is buggy as hell, don't expect a functional build. This is only if you want to get an early taste of ICS. And as usual, I'm not responsible if you blow your tablet.
What works:
- Framebuffer with 3D driver enabled.
- Touchscreen (A101 only)
- Wifi
What doesn't work:
- Everything else
- Internal storage is not mounted.
- Most notably, audio/video/power management/charging.
Instructions:
- You need sde menu enabled, see instructions here if you didn't do it already.
- Copy sysroot_ice.img to internal storage root:
Code:
adb push sysroot_ice.img /data/media
- In developer menu, flash kernel and initrd from zip file:
On boot menu, select "Recovery system"
Select "developer edition menu"/"flash kernel and initramfs"
A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
Select OK, the kernel should flash.
Select OK to reboot.
- Choose developer edition in boot menu
You should see two menus coming before boot, just wait for timeout. Other options won't work for your device.
Informations/Tips:
- Wifi AP scan doesn't work at first. Just add a dummy network, it doesn't matter if it doesn't exist really, scan will work after that (on wifi panel, click on "Add Network" button, top right of the screen then type "dummy" as network SSID, then OK).
- As I didn't want to interfere with regular build, data partition is the same as system image file, so there is only about 90M for apps.
I don't need feedback on bugs and problem running it as there is too many in current state. But let me know if you were able to run it though.
Updates
12/12/2011 - version alpha1, should support A80 now. Thanks to a1Pha for the test!
Thanks,
LeTama

* reserved *

for the buzz
http://www.jbmm.fr/?p=24451

Archos 70?
If this can be done on an Archos 101, could it be done on an Archos 70 as well? [The 8GB version without the hard drive.] My old Archos 70 needs a new lease of life!

pstjmack said:
If this can be done on an Archos 101, could it be done on an Archos 70 as well? [The 8GB version without the hard drive.] My old Archos 70 needs a new lease of life!
Click to expand...
Click to collapse
This a 101 G9, not G8... I believe it could be done on G8, even though ram will probably an issue. I'll try probably someday.

Build released, see first post.

how use the 2 anothers files ?

Hi Cajl,
The zImage and initramfs.cpio.gz ? These are the one that must be flashed through sde. I added the instructions in first post, this is the same thing as previous rooted firmware.
As it is, the initrd is not compatible with previous rooted firmware, you'll loose the possibility to run it after flashing ice kernel+initrd. You can reflash it again afterwards though.

Alpha 1 released, touchscreen should now work for 80 G9. Let me know if it doesn't work for you, there is two touchscreen drivers and only one is confirmed to work.

Market Working
Good news, after digging with it and deleting all Archos's craps. I finally make Market to work + Wifi, so this will be a great news now.
First google and download Market_v3.4.4.apk
then adb push Market_v3.4.4.apk /system/app
then adb shell
#cd /system/app
#rm Phonesky.apk
#cp Market_v3.4.4.apk Phonesky.apk
#rm Market_v3.4.4.apk
#chmod 777 Phonesky.apk
there we go!

letama said:
This a 101 G9, not G8... I believe it could be done on G8, even though ram will probably an issue. I'll try probably someday.
Click to expand...
Click to collapse
Please try for A70 when you have time as there is a large audience of us.

wozhere said:
Please try for A70 when you have time as there is a large audience of us.
Click to expand...
Click to collapse
I did this weekend, results are not very good so far... It's quite slow, few seconds to go from apps to widgets for instance. I didn't play much with it, touchscreen driver need more work and I couldn't make it work properly yet.
We'll see. Much work needed and slowness could come for a hidden problem somewhere, but I couldn't see anything obvious.

letama said:
I did this weekend, results are not very good so far... It's quite slow, few seconds to go from apps to widgets for instance. I didn't play much with it, touchscreen driver need more work and I couldn't make it work properly yet.
We'll see. Much work needed and slowness could come for a hidden problem somewhere, but I couldn't see anything obvious.
Click to expand...
Click to collapse
Sounds a challenge, thanks for working on it whenever you have spare time and keep us posted from time to time. If pulled off, even in a limited version, it will be a great coup.

+1+1+1+1+1+1+1

Yeah... everyones leaching for ICS these days
The limited RAM on Gen8 will be definitely a blocker...
On the other hand people even made efforts to run ICS on the good old Dream device. But this of course is a technical challenge, it's far from daily use.
Anyway i like reading your threads, letama...
Regards,
scholbert

Just saw this, ICS on the old HTC G1 (528MHz CPU & 256MB of RAM):
http://forum.xda-developers.com/showthread.php?p=19648827

Works so far on my G9 80, no problems with the touchscreen driver. Good work

you are the man, keep on the good work

link is down
i want to help with developing (I have a AOSP ICS rom for the play so i know how ics works)

I re-uploaded on uploading.com, first post updated.

[discussion|support|F.A.Q] Porting Ubuntu Phone OS to Defy(+)

Well this thread is dedicated about the possibilities of getting a port of ubuntu phone os. Recently displayed and would be launched around MWC 2013, Ubuntu OS will be launched for galaxy nexus! .
although there are short threads present about the topic, aim of this thread would be to provide Support/Bug-Report/F.A.Q if any port of ubuntu shows up for our phone from our great developers.
This is refreshingly new OS.
HERE IS THE LINK TO THREAD--> http://forum.xda-developers.com/showthread.php?t=2174544
I am damn sure some-one will take up this great job
Latest: Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting
Some of Features of ubuntu phone:(taken from wikipedia)
OS family Unix-like
Working state Current
Source model Open source
Initial release February 2013; 30 days' time
Available language(s) Multilingual
Update method Ubuntu Software Center (+ APT, …)
Package manager dpkg
Supported platforms i386, ARM
Kernel type Monolithic (Linux kernel)
Userland GNU
Default user interface Unity shell
So what may be the hindrances:
What kernel version is it based on
will it require bootloader unlock ;-(
UBUNTU PHONE OS
since it is yet to be released this is an open discussion, if any developer takes this project for defy, this thread will be a F.A.Q/support/Bugreport thread (if ever it happens )

i'm here for tests.
i'm not a developer, but you guys can count with my defy+ for tests. I really would like to have ubuntu phone on my defy+.

I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium

Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.

swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
what is ubuntu's packaging method? i mean the OS image?

pgreed said:
Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.
Click to expand...
Click to collapse
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone. Plus, as far as I remember (though I can easily be wrong on this, since I haven't touched an Ubuntu machine for months, now), this OS (specially considering it was specifically deployed for running on phones) doesn't take more than 2GB when installed. Again, I can be wrong, BUT... What about multiboot? A class 6 8GB card (or even a class 4, like the one included with our phones) may do the job, and we will still be able to boot CM10+ and ask silly questions to Google Now.
vedhasd said:
what is ubuntu's packaging method? i mean the OS image?
Click to expand...
Click to collapse
I may be wrong, but I think I read in more than one place it'll be available as a flashable zip. Since the folks there at Canonical were able to boot this little beauty in a Galaxy Nexus, and they intend to release the GNx version (without many workarounds needed to install) before the end of january, I think it's pretty safe to bet on a recovery-flashable zip file. Last, but not least, I think an install script (like the ones devs use in current Android flashable zips) may be slightly modified to install Ubuntu from a system image, specially if you consider Aroma-based installers are doing wonders in matter of personalizing Android installations. This not considering (and in this matter I have absolutely no idea) the possibility of the disk installer of linux distributions be already running scripts very similar to those used on Android flashable zips to install desktop OSs on computers. Devs will be better suited to tell about the latter.
P.S.: if anyone there tried Android-x86, you guys can see the installable image is very similar to an Ubuntu (or any other linux) installation zip. This might lead us in the opposite direction, looking at which modifications were made for the installer to work with Android, and reversing them for a Ubuntu installer to work in a flashable zip.

K3n H1mur4 said:
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone.
...
Click to expand...
Click to collapse
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.

pgreed said:
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.
Click to expand...
Click to collapse
It may depend on how far our devs will be able to strip down the OS for our phone, I think we may not require full fledged running desktop compatibility but it still depends by what extent we can strip down the footprint!
Sent from my MB525 using xda premium

Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting

red lens defy+ guinea pig
swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
'm not developer but my red lens defy+ is available as a guinea pig.
Then I can make rather a system as primary OS alpha and p500 use my day-to-day
sorry my english

It would be nice if we had more one option rom. Live freedom!

are there some news? i've founded this video, but I can't understand if this is related to the thread in android development...
in youtube: watch?v=hglLF3dM8Zk (i'm not allowed to post link ^^ )

Kayant had released an alpha preview.. but the ubuntu project will be helpful iff we some how boot up 3.0.x kernel with RIL
Sent from my MB526 using xda premium

[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.