yashsingh1/xdaforums huggingface dataset:
[Dell Venue] x1123:
I don't think so. I need to rebuild the kernel with 3d HW activated along with variable samsung s6e63m0_driver ... unless I know how to build rom without 3D hw acceleration include. all kernel will boot. But we need this 3D in ICS
[Dell Venue] kakagi:
logcat if u want to see

btw how to flash those drivers its in .tar.gz format
[Dell Venue] kakagi:
yah hw accelaration needed, for my other device samsung galaxy mini team jellaxy also include hw accelaration,

---------- Post added at 12:07 AM ---------- Previous post was at 12:03 AM ----------

its strange that arm v6 600mgz only device run ics and jelly bean so soomthly and more over everything working except youtube hd video coz quallcom didnt rlz thier source code for armv6 otherwise everything works,, camera was the main issue for those ics build but after almost 9 month they able to solve it also.
[Dell Venue] x1123:
Thanks for the logcat. I will take a look later on. untar the drivers and push via adb. The archive content system/lib/egl and system/etc/firmware

adb remount
adb push system/lib/egl system/lib/egl/
adb push system/etc/firmware system/etc/firmware/

[b][color=red] depending from where folder you flashing [/color][/b]
[Dell Venue] x1123:
Your logcat is showing completely messy the device .... very bad. I will repack the rom flashable via CWM pls wait device will be like attached logcat. My friend help me to test like You kakagi ..... great work with you.
[Dell Venue] kakagi:
ok i again took the logcat
[Dell Venue] kakagi:
i used this command in this logcat

adb logcat > name of problem.txt

but in prev i used this command

adb logcat -v long > name of problem.txt
[Dell Venue] x1123:
on device stae via adb :

adb devices
adb shell
# rm -rf system/lib/hw/gralloc.qsd8k.so
[b][color=blue] this will delete module gralloc.qsd8k.so [/color][/b]

I sorted out we don't have a file named

/system/bin/mmService

/system/bin/DrmHost

/system/bin/qmuxd

/system/etc/install-recovery.sh

DrmHost is for DRM, mmService to load some picture etc, install-revovery.sh ... duno what for this one.
[Dell Venue] chacona:
install-recovery.sh is the script file that restore the recovery partition each time our device is booted, I think. In CWM, each time we restart our DV, there always be an option not to flash recovery, FYI.
[Dell Venue] kibuuka:
you can adb pull these from froyo ROM, since these are closed source ones and being injected into ICS ROM (and being used as-is) at build time anyway :). add them into ICS-based ROM zip before flashing it to your device. install-recovery.sh currently does nothing, it's safe to omit it.
[Dell Venue] changkho1908:
anything new?
[Dell Venue] x1123:
News is there But It is BAD NEWS I spent the week end to sort out DV ICS boot problem. AFAIK best kernel sources for DV is by Kibuuka. I built with various combination of configurations but still No lucks. The main problem is kgsl driver with yamato firmware can not communicate with device via ioctl = input/output control thus we need to patch kibuuka kernel with latest kgsl build template. again (AFAIK) I saw Tiamat done with this patching, as he said on his sites ... the source still weird, but well booting. I toke tiamat 2.6.38-ics and 2.6.38-ics-tiamat. built with error on bcm4329 ... flash to DV with passion rom ICS .... NOT BOOTING . I saw during building the kernel kgsl drivers build flawlessly at tiamat sources. Kibuuka is here, he probably can advise what we should do or he is willing to patch his source :D ... LOL

I also in thinking that firmware yamato i have is old one. Considering Passion, Bravo and X10 xperia success booting ICS. DV must be able to do same.
[Dell Venue] changkho1908:
Kibuuka, plz help us :o
[Dell Venue] x1123:
Changkho every user joining this forum as I believed is advance user. so you can also help by compiling kernel and test. User various sources available in the internet for Tutorial you follow MY BLOG
[Dell Venue] kibuuka:
first: i need to know which sources we mess with :)

second: what venue's code name is (streak is "austin")?
[Dell Venue] prasad12ka4:
Thunder (I guess)
[Dell Venue] changkho1908:
dell lighting or dell thunder :good:
[Dell Venue] kibuuka:
thunder? taking in account that streak's 4.05 source tree seem to be equal to venue's 4.06...

ohhkay. now could anyone post (here or elsewhere) .config of venue's kernel that's built manually (dell's or dsc source trees - it doesn't matter) from source and is functional (boots, provides full hw support for GB-based rom)? thanks in advance
[Dell Venue] x1123:
Dell Venue code name is TOUCAN I used kibuuka kernel sources by considering have been proved booting on DS5 I still have no luck to have good build enable booting on DV. From logcat I understood there is Hal implemented on ICS for Audio via linux alsa. Thus switch on sound card flag in kernel source to have alsa hal compiled in. I will also try to build from dell-406 source.

I did Not touch passion-rom build from evervolv sources under pressumption, passion GB build booting flawlessly on DV without any single tweak, thus ICS Build should be same ....... (unless CHANGED THE KERNEL).

attached working config from to build kibuuka source and ramdisk file for your easy to mess. to build boot image just do

mkbootimg [b][color=red] (Please ansure you have this kind of file at your path )[/color][/b] --kernel yourZimage-renamed --ramdisk 1vnr.gz --board venue --pagesize 2048 --base 0x20000000 [b](pagesize and base value options is FIXED for qsd8k) [/b] --cmdline "androidboot.hardware=venue" -o YourNamedofFileDOTimg

the result is kernel+ramdisk flashable via fastboot

This is probably a clue to sort out problem :

- Hal implemented at ICS base source code

- 3D drivers is needed. in case of DV Qualcom provide binary drivers for ICS

- I faced ioctl KGSL_GET_PROPERTY error .... this is in my opinion related to firmware. (yamato_pfp.fw and yamato_pm4.fw) I have even tried to build this firmware into kernel binary .... but No Lucks.
[Dell Venue] kibuuka:
ok x1123, here what needs to be done (to shorten mileage i assume you're using ics branch of my git sources from now on).

you need to diff two versions of board-qsd8x50_austin.c - from Phoenix and ics branches. resulting diff is what you need to apply/add/change in board-qsd8x50_toucan.c in ics branch (as it implements everything you need to properly initialize adreno hardware in a way new driver needs it). rest of code (updated kgsl code/headers, genlock support and other changes) is reuseable and (mostly, you probably will have trouble with touchscreen driver) board-independent.

configdv.zip is broken btw
[Dell Venue] x1123:
Hmmm .... let me try once I have time ... Thanks for dvise
[Dell Venue] terminal17:
Any development so far on the kernel and rom? Just curious :D:p
[Dell Venue] x1123:
Yes Today I get the kernel and ROM Booting ...... :D ... But very far from usable :(
[Dell Venue] terminal17:
Good work...waiting for u to release the rom after the bug fixes...nice to hear our DV is getting ICS rom very soon...:):D:p
[Dell Venue] x1123:
Downlod : isc-venue-passion-base

How to flash

- download above links

- extract somewhere in your path/folder

- turn your DV into fastboot mode

- connect to PC with adb / fastboot alive

- Flash

$ fastboot erase system
$ fastboot erase boot
$ fastboot flash system system.img
$ fastboot flash boot boot-1.img

very unsable ... very early dev, for fun and dev only at least we have a CLUE how to boot ICS on DV and the chance is somewhere out there ... :)
[Dell Venue] prasad12ka4:
Superb Simply Superb!!!

Can you provide details and what is working or what all is not working?

So we can start troubleshooting it?

Need to fix the download link., its down :(
[Dell Venue] changkho1908:
fighting!!! :good::good:

---------- Post added at 05:58 AM ---------- Previous post was at 05:54 AM ----------

File not available

could you make a zip file to flash via CWM?
[Dell Venue] kakagi:
Gr8 news :) kindly not having pc connection will test it later after, could u plz reupload the file :)
[Dell Venue] changkho1908:
:(:(:(:(:(:(:(:(:(:(:(
[Dell Venue] nguyen_vh:
Please FIX as many bugs as possible :D.. X1123 "D

We're wating for your ROM :D.....

GOODLUCK :D.. WISH YOU HAVE A GOOD TIME :))D
[Dell Venue] changkho1908:
everybody, please click thanks button to support x1223 :good:
[Dell Venue] chacona:
Yes, x1123, please post the file again, we're willing to help you test and debug it. Thanks!
[Dell Venue] x1123:
ROM ICS VENUE FOR TEST DOWNLOAD FLASH VIA RECOVERY .

Above is evervolv ICS passion build WITHOUT 3D HARDWARE ACCELERATIONS , intention to make sure that ICS Bases Build for Passion is bootable ... into DV, kernel build based on 406, or Kibuuka or DSC Team : Results are similar ..... Touch Screen NOT WORKING at all .

I have been looking for correct patch or method how to enable 3d Hardware Accelaration in either 406 source tree or Kibuuka Tree, since Kibuuka source is working at DS5/7 ICS Base ... His source should be capable to boot at ICS DV, since when flashed into 3D hardware acceleations ICS ROM, kernel locked and KGSL ioctl locked. :(
[Dell Venue] changkho1908:
touch screen not working :( only hard buttons working :(
[Dell Venue] kakagi:
May this help ...

https://groups.google.com/forum/m/#!topic/android-porting/Rmvqi8fPYCg

---------- Post added at 11:08 AM ---------- Previous post was at 11:02 AM ----------

http://code.google.com/p/androidscreencast/

This may help to control the ph via pc without touchscreen.

Fps is slow so have patience.
[Dell Venue] x1123:
Thanks for pointing ... but in DV case we need to PATCH 406 kernel with KGSL Adreno Drivers. I got tiamat patch file however this patch file is include Overclocking, Under/Overvolting ... etc , other problem, ref to 2.6.35.7 version of 406 kernel have been 7 times patched and No explanation from dell what kind "patch" they have been aplied. tytung patch is for 2.6.32 kernel ... this is very hard works since we must "merge" 2.6.32 and 2.6.35 tree > then patch with adreno 200 drivers > then (again) get rid with Kconfig and Makefile to have "vanilla" kernel for DV with 3dhw accel capable. Further challange to know the pagesize of mem in DV device.

Kibuuka probably can explain here what kinds of patch he applied in his sources 2.6.35-14 ... and kibuuka kernel source is definitely for DS thus using 406 is best for DV.

some probably willing to test to patch 406 with tiamat.patch attachaed here is the small guide

download clean 406 kernel source tarbal
unpack the tarbal > cd to unpacked folder
copy tytung.patc to unpacked folder
[b]
patch -p0 > tytung.patch
...
...
[/b]
if they ask to REVERSE (-R) answer YES (y)
usually by default the answer is NO (n)
due to this is downgrading ...

once I have time I will do patching

Note

Please do "hunting" in the google, adreno 200 patch file for 2.6 kernel and share here the patch file ... to let other user try this dirty works :D
[Dell Venue] kakagi:
I did a quick search and found this thread in xda. Its a thread of htc hd2 kernel.

They have patch take a look if it helps. The sources are at github.

http://xdaforums.com/showthread.php?t=1322639

---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------

I will search later with my desktop...
[Dell Venue] x1123:
Kakagi, you are so eager and enthusiastic on this device ... really great to know :D ... I personally happy with CM7 ... I just bought Desire V 2 sim cards gsm gsm running ICS with kernel 3 this is my first device running ICS by default. but my feeling DV is still more elegant in design, very simple device. corning goriila glass make this device very strong.

Tytung implementation is more complicated , I saw "securecrt" at github having simpler implementation for adreno 200 and 220 only in which tytung, I think cover adreno 3xx and 2xx .. one or more dv user probably can ask tytung to patch 406 source with his patch .... LOL or at least borrow his patch file. I have been long time did not deal with patching kernel source code. To write our own code ... I have no idea DV HW details. It is probably available at internet. This must be not so heavy since we need to patch one driver only gpu

I did some little work on this, but still no lucks in building :( :(

this is my error

CC drivers/gpu/msm/adreno_ringbuffer.o
In file included from drivers/gpu/msm/adreno_ringbuffer.c:18:
drivers/gpu/msm/kgsl.h:41:26: error: linux/atomic.h: No such file or directory
In file included from drivers/gpu/msm/kgsl_device.h:36,
from drivers/gpu/msm/kgsl.h:43,
from drivers/gpu/msm/adreno_ringbuffer.c:18:
drivers/gpu/msm/kgsl_pwrctrl.h:54: error: 'KGSL_MAX_PWRLEVELS' undeclared here (not in a function)
drivers/gpu/msm/adreno_ringbuffer.c: In function 'adreno_ringbuffer_extract':
drivers/gpu/msm/adreno_ringbuffer.c:843: error: 'struct kgsl_devmemstore' has no member named 'current_context'
drivers/gpu/msm/adreno_ringbuffer.c:857: error: 'struct kgsl_devmemstore' has no member named 'current_context'
make[3]: *** [drivers/gpu/msm/adreno_ringbuffer.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make: *** [drivers] Error 2

I just realize, since I clean download 406 from dell, the source intended to build in ROM I have to manage including my folder tree in PC BOX .... OMG a lot or work. My old 406 source is messy since I have cleaned some warning. Let us do together ... to have DV running ICS/CM9
[Dell Venue] TheManii:
Kibuuka: have you made any changes to the touchscreen controller drivers?

I've never had the time to diff S5/405 V/406 against phoenix/ics.

If there were changes, that's likely why TS isnt working, as the S5 uses a different TS controller.

The V and S7 use an Atmel mxt224, and supports 5-10 touchpoints in hardware, the S7's TS driver is badly mangled so dont bother using it as a source.

The mxt224 is a common controller otherwise, you can likely merge in a working one from a different similar device.

I wonder if the V's TS driver has been modified from the original, you can easily reenable all the points with 1-2 lines of change on other devices.
[Dell Venue] kibuuka:
lemme recall. only changes that were done:

#1 hPa's patches for touchscreen (unsure if these apply to 5" part of aou touchscreen driver only - check #ifdefs and add similar patches to 4" related part of code if needed)

#2 cm9 patches related to legacy touchscreens support - aosp lacks these

#3 (optional for venue as it's touchscreen ain't physically flipped afaik, also it was substituted by later version of hPa's code, still in my source tree, inactive) changes to screen orientation part of aosp code - these are trivial and not needed on venue
[Dell Venue] terminal17:
Any progress in development?
[Dell Venue] adridu59:
I have never used the erase commands, I think they are not mandatory.

Kernel needs some mods, I will look at it ASAP.
[Dell Venue] adridu59:
@x1123 I have pushed my mods. (:

https://github.com/adridu59/dsc-team-kernel-project/commits/ICS

Fork my repo,

checkout the ICS branch

, and then

make toucan-perf_defconfig

make
[Dell Venue] adridu59:
@x1123 Just commited the Makefile fix, I had forgotten..
[Dell Venue] x1123:
Okay let me check ... did you put adreno200 device drivers in the source tree ?

Edit

Just checked you put adreno devices drivers in the source three .. I forked and will build and report the result

Report

... Boot Loop :D attached logcat ... I will rebuild tonight
[Dell Venue] x1123:
I have downloaded adridu kernel source tree for DV and saw proper genlock and adreno2xx added in the tree ... kernel build went flawlessly. I have 4 ICS Rom my own build : 1. Based on Bravo, 2. Based on Passion for blackrose bootloader, 3. Based on Passion based on stock htc bootloader, 4. ICS Aosp Generic <for emulation> . With the proper kernel, generic rom usually booting in a real device .. sure without base band functionality, mean we can not calling as a phone.

adridu kernel source is what I expected with proper adreno2xxx gpu drivers and genlock available, buidling went very good with adreno libs built without warning or error. However the symptom in booting in DV exactly similar with 406 kernel source :( :( :( ... this is really frustating. I test with Leo device all four rom build booting properly :D .... whats wrong with this DV .... The only rom booting in DV is one without touchscreen functionality (built without gralloc libs ) ................. wazzahhhhhh
[Dell Venue] lungocphu:
Fighting

Waiting for your success
[Dell Venue] changkho1908:
join us on facebook https://www.facebook.com/groups/386664754742736/
[Dell Venue] x1123:
I have spent week end to check and test adridu kernel source. The source in my opinion should be okay, with adreno200 drivers in the source tree. However the [colore=red] FUNNY [/color] thing, No singgle ICS Based ROM either for Bravo, passion and Xperia 10 booting with the kernel, symptoms are similar gralloc.qsd8k.so problems this is essential adreno200 libs.

I did test the kernel by downloading various GB Rom for : Nexus One, Bravo Devise and Experia 10 all GB ROM booting flawlessly ... so many good ROM in xperia 10 and passion thread on GB base. DV user can download, flash adridu build kernel + wifi module and DV baseband. I believed DV will be good for daily device.

But our goal is booting ICS on DV ... I believed we are closer than last week ..... :D adridu kernel source is the closest source available today to boot ICS on DV ... I need to go deeper and probably check line by line the toucan-qsd8k file in the board folder source and see what's wrong with the build. ROM IS NOT THE ISSUE AT ALL.
[Dell Venue] adridu59:
@x1123 I tried to raise MSM_FB_SIZE as in Austin board file, can you try to recompile the kernel with it ? Thanks.
[Dell Venue] x1123:
SORRY ...can you give me more details instructions ... what do you mean ...???

---------- Post added at 01:44 AM ---------- Previous post was at 01:34 AM ----------

armmake austin-perf_defconfig

armmake prepare

time armmake

In file included from kernel/sched.c:2:
kernel/sched_bfs.c:527: error: conflicting types for 'grunqueue_is_locked'
include/linux/sched.h:1535: note: previous declaration of 'grunqueue_is_locked' was here
make[1]: *** [kernel/sched.o] Error 1
make: *** [kernel] Error 2
[Dell Venue] adridu59:
No I wasn't asking you to build for Austin board, just cherry-picking the new commit (ebb56c3bb998a19497d09622cd96e711dd130768) and rebuilding toucan like before. :good:
[Dell Venue] x1123:
picked up and built

I/sysproc ( 959): Entered system_init()
I/sysproc ( 959): ServiceManager: 0x13afe0
I/SurfaceFlinger( 959): SurfaceFlinger is starting
I/SurfaceFlinger( 959): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
W/qsd8k.gralloc( 959): FBIOPUT_VSCREENINFO failed, page flipping not supported
W/qsd8k.gralloc( 959): page flipping not supported (yres_virtual=802, requested=1600)
I/qsd8k.gralloc( 959): using (fd=33)
I/qsd8k.gralloc( 959): id = msmfb31_30001
I/qsd8k.gralloc( 959): xres = 480 px
I/qsd8k.gralloc( 959): yres = 800 px
I/qsd8k.gralloc( 959): xres_virtual = 480 px
I/qsd8k.gralloc( 959): yres_virtual = 1600 px
I/qsd8k.gralloc( 959): bpp = 16
I/qsd8k.gralloc( 959): r = 11:5
I/qsd8k.gralloc( 959): g = 5:6
I/qsd8k.gralloc( 959): b = 0:5
I/qsd8k.gralloc( 959): width = 76 mm (160.421051 dpi)
I/qsd8k.gralloc( 959): height = 127 mm (160.000000 dpi)
I/qsd8k.gralloc( 959): refresh rate = 0.00 Hz
D/CALCFPS ( 959): DEBUG_CALC_FPS: 0
D/CALCFPS ( 959): period: 10
D/CALCFPS ( 959): ignorethresh_us: 500000
D/CALCFPS ( 959): DEBUG_CALC_FPS: 0
D/CALCFPS ( 959): period: 10
D/CALCFPS ( 959): ignorethresh_us: 500000
E/qsd8k.gralloc( 959): Error mapping the framebuffer (Invalid argument)
E/FramebufferNativeWindow( 959): couldn't open framebuffer HAL (Invalid argument)
E/SurfaceFlinger( 959): Display subsystem failed to initialize. check logs. exiting...

looklike the gralloc.qsd8k ok with evervolv cm9 passion base rom ... device facing bootloop :(

code at BoardConfigCommon.mk for qsd8k

# Hardware rendering
BOARD_EGL_CFG := device/htc/qsd8k-common/egl.cfg
USE_OPENGL_RENDERER := true
# We only have 2 buffers
COMMON_GLOBAL_CFLAGS += -DMISSING_GRALLOC_BUFFERS
# Debuging egl
#COMMON_GLOBAL_CFLAGS += -DEGL_TRACE
[Dell Venue] adridu59:
You should not use device tree from other phones... either use overlay from DSC Team Streak or build one yourself from Dell Venue BoardConfig.
[Dell Venue] x1123:
Adridu, thanks for advise. However the MAIN different on device specific is very little, let say passion source tree having qsd8k-common which is definitely including DV .... :D ... Im not really developer. My understanding not so advance ... LOL I flashed again with Xperia 10 ROM which is ported from desire base. Again the room booting nicely but face dead touchscreen I replaced /system/lib/hw/FILES with ds5 cm9 rom... I believed, problem is in RAMDISK I'm familiar building ramdisk for x86 (my PC) but no idea for this DV ...

This is init scripts for PC

#!/bin/sh

#Mount things needed by this script
mount -t proc proc /proc
mount -t sysfs sysfs /sys

#Disable kernel messages from popping onto the screen
echo 0 > /proc/sys/kernel/printk

#Clear the screen
clear

#Create all the symlinks to /bin/busybox
busybox --install -s

#Create device nodes
mknod /dev/null c 1 3
mknod /dev/tty c 5 0
mdev -s

#Function for parsing command line options with "=" in them
# get_opt("init=/sbin/init") will return "/sbin/init"
get_opt() {
echo "$@" | cut -d "=" -f 2
}

#Defaults
init="/sbin/init"
root="/dev/hda1"

#Process command line options
for i in $(cat /proc/cmdline); do
case $i in
root\=*)
root=$(get_opt $i)
;;
init\=*)
init=$(get_opt $i)
;;
esac
done

#Mount the root device
mount "${root}" /newroot

#Check if $init exists and is executable
if [[ -x "/newroot/${init}" ]] ; then
#Unmount all other mounts so that the ram used by
#the initramfs can be cleared after switch_root
umount /sys /proc

#Switch to the new root and execute init
exec switch_root /newroot "${init}"
fi

#This will only be run if the exec above failed
echo "Failed to switch_root, dropping to a shell"
exec sh

when fail ... kernel will send us into shell and we can do many thing. But at the piece of smartphone ... dropped to shell is nothing can do :D ... guide me.

attached DV booting xperia x10 ics rom with dead screen
[Dell Venue] changkho1908:
hey x1123, we've been waiting for you, we're Vietnamese, Indian, Korean...anywhere on the earth :) everyday, we're following your ICS infomation :D

please don't give up.:o thankful to you :)

we're on facebook: https://www.facebook.com/groups/386664754742736/
[Dell Venue] adridu59:
Yes, of course all QSD8xxx phones are based on qsd8k-common but there is a device-specific hardware design which usually needs some fixups... did you try building against Dell Streak overlay?

Can you contact DSC Team for info? because as I said earlier I do not touch this kind of stuff usually so I do not have more knowledge than you tbh.