yashsingh1/xdaforums huggingface dataset:
[Dell Venue] changkho1908:
-SD card detected :good:

-GSM, Wifi: working

- touch screen: working well

- Camera cann't connect :(

- brightness level can not set

- speaker not working, when play the songs, just appear a headphone icon on status bar and headphone not sound

- Home button still not working :(

- I can't install apk app download via browser :( (maybe without gapps)
[Dell Venue] prasad12ka4:
Does this require gapps to be flashed?

Also did you try any other camera app for camera?
[Dell Venue] changkho1908:
:laugh::laugh::laugh::laugh::laugh::good::good::good::good::good:
[Dell Venue] kakagi:
Try to flash gapps for cm9. And see wether you can use playstore and install app via playstore.

And please report about bluetooth and gps and check voice talk working or not.

Whizkins said he also fixed SOD in his build, lets wait for his build also.
[Dell Venue] kakagi:
list updated more testing results needed..
[Dell Venue] x1123:
More testing please GPS .... for speaker my suspect is phoenix patch for DS .... should be Not Necessary for DV
[Dell Venue] x1123:
comments

Thanks for testing

- mutekey ... my kernel is build-in this should be not necessary I think this caused the device mute all times :D

- camera ... This should be handled at the last, since tweaking camera is hard due to related to (AFAIK) proprietary binary

FROM KERNEL BUILD PROCESS

drivers/media/video/msm/ov8810_abico.o
drivers/media/video/msm/ov8810_semco.o

probably we can get drivers from chipset provider ....
[Dell Venue] prasad12ka4:
ICS ROM Test Video

http://www.youtube.com/watch?feature=player_embedded&v=AoNWFTaCXi8

User:trungtony85

From www.tinhte.vn

Has posted the above test video of ICS ROM.

All credits to him for the video :good::good:
[Dell Venue] adridu59:
For the camera, you guys will need new libs for ICS. That is proprietary code so you must either ask manufacturer to release them or find similar libs from other devices.
[Dell Venue] x1123:
camera always Big Thing on CM rom :D ... btw any idea related to the phone Totally Mute All Times ... I suspected this is libsoundpool.so ... the error is AudioFlinger can not create audio track ... :( ...
[Dell Venue] WhizKins:
I got the audio working. Here's a list of things that need attention right now:

* Home button not working (It's being mapped as the MOVE_HOME key), I'm using the surf_keypad.kcm file from CM7

* Video doesn't work (Probably needs OMX libraries)

* Soft button lights don't work (Need to port liblights?)

* Accelerometer doesn't rotate back to portrait from landscape

* Battery Drain

EDIT: Headset is not working, sound just comes from the speaker even when headset is plugged in

And probably a lot of other things like Camera but I'll look into the camera later :)

If anyone has any suggestions for these, please let me know :)
[Dell Venue] kakagi:
Battery drain might be a kernel issue.

And what did u change for audio working?
[Dell Venue] kakagi:
updated the working lists and 1st post.
[Dell Venue] WhizKins:
I disabled the libaudio from DSC sources and used CM9's libaudio.

And another thing, headset isn't working, that needs to be fixed too.
[Dell Venue] changkho1908:
many issues gonna fix :)
[Dell Venue] x1123:
Good News. For audio, if possible you can build without soundpool ... soundpool is great but causing exhausting of memory and on certain device the mapping got weird.

* Home button not working (It's being mapped as the MOVE_HOME key), I'm using the surf_keypad.kcm file from CM7
* Video doesn't work (Probably needs OMX libraries)
* Soft button lights don't work (Need to port liblights?)

all above about library ... I'm preparing my kitchen with dell overlay from DSC in my CM-9 three looks what I will have.

for video : I ddid not know how android codecs working

* Accelerometer doesn't rotate back to portrait from landscape
* Battery Drain
EDIT: Headset is not working, sound just comes from the speaker even when headset is plugged in

If u use my build kernel : I switch off Portrait Fix patch by phoenix at dsc source :D I will rebuild with switch on this option.

Speker always on is also phoenix patch will try rebuild with this option off

Battery Drain is lightssensors.so need to be re-baked.

can u give us the libs or whole rom with audio function :)
[Dell Venue] adridu59:
Those are object files generated at compile time, no way you'll find proprietary stuff within the Linux Kernel tree.

https://github.com/adridu59/dsc-team-kernel-project/blob/ICS/drivers/media/video/msm/ov8810_abico.c

https://github.com/adridu59/dsc-team-kernel-project/blob/ICS/drivers/media/video/msm/ov8810_semco.c
[Dell Venue] x1123:
WhizKins,

would you please let us know what android source tree did you usu for rom successfully built you posted. I toke a look last night official CM9 tree did not support qsd8k board :confused: Thus I used EVERVOLV and put kernel source tree in the android tree, expecting clean build of rom with kernel .. just need little tweaking on DSC overlay sources. I faced ERROR

:hardware/qcom/display/libqcomui/qcom_ui.cpp:64: error: undefined reference to 'gralloc::IAllocController::getInstance(bool)'
collect2: ld returned 1 exit status
make: *** [out/target/product/venue/obj/SHARED_LIBRARIES/libQcomUI_intermediates/LINKED/libQcomUI.so] Error 1

:rolleyes: :rolleyes: :rolleyes:
[Dell Venue] WhizKins:
I used the stock CM9 sources, you've made your own device files for the Venue or you're building it for some other device?
[Dell Venue] kakagi:
I have talked the dev thewhisp who is working with ics and jellybean rom for samsung galaxy mini(arm v6) for over one years and more and now ics and jb is fully stable now for that device no single glitch. Anyways He agreed to help and asking to me that is there any sources available github so that he can see n help us for the speed up of the development.

If u guys please share the source on github it wld be much help so that I can talk to him further.

Thanx
[Dell Venue] adridu59:
+1
[Dell Venue] x1123:
I used evervolv source tree since they have qsd8k board for passion and I add dell/venue forlder modified from dell/streak overlay . My imagination qsd8k-common from evervolv > vendor/device from modified dell/streak :D it will less work.

my last built stop at 208 minutes this is very near to complete .. I need to see the build log and report.

kakagi,

my soource is not tested ... I build with BoardConfig to directly build the kernel.

cyanogen instruction >

My thinking once I have success build I will share the source on github, I think good idea to share source at github to enable another people take a look and help.

Note

my last build error

make: *** No rule to make target `out/target/product/venue/obj/STATIC_LIBRARIES/lib_driver_cmd_bcmdhd_intermediates/lib_driver_cmd_bcmdhd.a', needed by `out/target/product/venue/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant'. Stop.
[Dell Venue] Songlambr37:
come on Buddies, we are waiting for the last result,,,:good:
[Dell Venue] adridu59:
As you wish but it's always better for the others (and possibly for you too) to upload the stock source and commit each change.

So that we can easily see what changes you did and why.
[Dell Venue] chacona:
I totally agree, that's what learning is all about! :)
[Dell Venue] x1123:
adridu, you are correct ... I will get rid and clean the source tree and file folder in my box and push to github. I just doing small reconstruction of folder tree for easy understanding i.e I put in a folder named configs for all configs files libs for all libs file .. etc, I used dell folder from dsc-project as references, i Think, i'm not so good and confusing with the folder tree since everything they put and one folder named files . I will get rid to reconstruct and push to github. One after that try rebuild the rom.

whizkin ROM gave us a a hope and make all of us sure ICS can boot on Venue, since whizkin rom < coming from DS < some libraries token from CM 7 < cm7 probably token some stock 406/407/408 at the end I loss track which library is mandatory, whats are changed from cm7 to cm9 ... etc ... etc I decided to reconstruct all of them. For example today CM 9 used wpa 8 DSC configuration used WPA 5 this caused by build messy all of these is AFAIK :D
[Dell Venue] x1123:
Hi Guys,

Before I push to github appreciate someone to take a look attached 2 critical file.mk BoardConfig.mk and device.mk I need to clean up folder in mybox before pushing and test to build.
[Dell Venue] x1123:
I face unresolved problem on build test on wpa_supplicant various configuration on BoardConfig.mk I have made .... NO LUCKS ... I think whizkin who has succuessful build need to share the configuration on wifi stuff

my build error

make: *** No rule to make target `out/target/product/venue/obj/STATIC_LIBRARIES/lib_driver_cmd_bcmdhd_intermediates/lib_driver_cmd_bcmdhd.a', needed by `out/target/product/venue/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant'. Stop.
[Dell Venue] adridu59:
More like if you have the detailed changelog its FAR easier to debug aka. track down incorrect/incomplete changes.
[Dell Venue] x1123:
First ... I think I do this for fun, never wish to be a personal project or whatever :D coz of build failure I reconstructed the dell folder from dsc. I have pushed to GITHUB ... from Now on we can start build testing. I personally use evervolv repository source tree ... sure anyone can use cm9 source tree since evervolv is based on cm9.
[Dell Venue] x1123:
any news from wizkin. my build stuck at wpa supplicant and power matter. I need to clean my source and make build testing again .... whoah
[Dell Venue] kakagi:
Dont know abt whizkins may be he his busy with fixing or any other works...it wld be better if he also share his source/work.
[Dell Venue] WhizKins:
Hi guys, sorry for the late reply, I had exams so I was busy. My sources are a mess and need some cleanup, I'll release them once I clean them up a bit (probably tomorrow or the day after). I also have a ROM I built which is very much functional albeit with some bugs like camera and stuff. It can be used with some minor tweaking.

I'll release the ROM once I finish tweaking and uploading.
[Dell Venue] kakagi:
Best of luck 4 ur exam results :P

And thanks for your hard work. We r looking forward to ur rom and sources at github :)
[Dell Venue] x1123:
appreciate if you were able to share your device/dell/venue folder contents <-- did you use this name ? in the source folder tree. I just clean up my source by syncing again from beginning :D ... I never have built success for the rom. I will try with mini build, I think I can use your configurations as reference .... btw how is your exam ? is everything went well .... :)
[Dell Venue] WhizKins:
Yes, I used device/dell/venue :)

and the exams went alright thanks for asking :)

Btw, I released my ROM, it's usable as a daily ROM but with a few bugs like camera and headset not working. Here's the link to the thread: http://xdaforums.com/showthread.php?p=34364122

I made a new thread as I thought it was a release ready ROM and should belong to a new thread. We can still continue this thread for further development on ICS as there are a lot of things to do still.
[Dell Venue] WhizKins:
Hi guys,

Here's the source code (device files) as requested. They're still not very clean but they build :P

Github: https://github.com/gastly/android_device_dell_venue
[Dell Venue] chacona:
Thank you, do you think that with these files, we can prepare for a JB build? Moving from Android 2.x to 4.x requires much work, however, I do not think we need to meet the same difficulties when moving from ICS to JB. Am I right?
[Dell Venue] x1123:
Fully agree ... development thread should not provide ROM thus common users will not brick their device and don't know how to revive. sometimes a user not patient enough his/her eagerness can send their device into crappy plastics :D

---------- Post added at 08:30 AM ---------- Previous post was at 08:10 AM ----------

:good:

You are right from GB to ICS = HARD WORK from 4.0 > 4.1 should be easier, but some proprietary still coming from 2.3 :D
[Dell Venue] kakagi:
for camera can we use lib from gingerbread i saw for some device some dev back ported camera from gingerbread to ics.

@ whizkins little bit off topic :P

where do you stay in delhi? i stay near saket :D
[Dell Venue] adridu59:
That is not backporting ; by definition backporting is when you port upstream changes to an older version.

Here it is forward-porting.
[Dell Venue] kakagi:
Oops sorry ...but is it possible for us to use gingerbread lib in ics via some modification?
[Dell Venue] kakagi:
ok i talked to Thewhisp about the data problem and ringtone sound problem this is all he said in PM

"About data. Try "logcat -b radio" it should show the problem. Incoming call via speaker - probably wrong snd's in audio libs"

may dev find it usefull.
[Dell Venue] x1123:
logcat -b radio

D/QCRIL ( 93): [qcril.c 2124] [CM_SS_EVENT_RSSI(73729)] Subscription: 0x8 --> 0x8
D/QCRIL ( 93): [qcril_arb.c 740] RID 0 voice tech: gw modem id=0, ma=Multimode(0), net_pref=GSM WCDMA preferred(0)
D/QCRIL ( 93): [qcril_arb.c 988] RID 0 data tech: gwl modem id=0, pdt modem id=1, pdt=Unknown(0), ma=Multimode(0), net_pref=GSM WCDMA preferred(0)
D/QCRIL ( 93): [qcril_arb.c 630] Arch: cdma modem id=0, evdo modem id=0, gwl modem id =0, ma=Multimode(0)
D/QCRIL ( 93): [qcril_cm.c 11021] GW signal is available.
D/QCRIL ( 93): [qcril_cm.c 11067] Signal strength: gwl_rssi: 14, gw_bit_error: 255, cdma_dbm: -1, cdma_ecio: -1, hdr_dbm: -1, hdr_ecio: -1, hdr_sinr: -1, lte_rsrp -1, lte_rsrq -1
D/QCRIL ( 93):
D/QCRIL ( 93): [qcril.c 1814] UI <--- RIL_UNSOL_SIGNAL_STRENGTH (1009) --- RIL [RID 0, Len 40, (null)]
D/QCRIL ( 93): [qcril.c 2836] Exit qcril_process_event() : CM_SS_EVENT_RSSI, err_no 0
D/QCRIL ( 93): [qcril_event.c 278] qcril_event_main(): Waiting...
D/RILJ ( 276): [0116]> SCREEN_STATE: false
D/QCRIL ( 93): [qcril.c 2577] UI --- RIL_REQUEST_SCREEN_STATE (61) ---> RIL [RID 0, token id 116, data len 4]
D/QCRIL ( 93): [qcril_cm.c 11934] De-registering the RSSI and HDR RSSI events on screen-off request
D/QCRIL ( 93): [qcril_cm.c 11993] Reply to RIL --> Screen off
D/QCRIL ( 93): [qcril_reqlist.c 164] [RID 0] Not found ReqList entry : token id 116
D/QCRIL ( 93): [qcril.c 1728] UI <--- RIL_REQUEST_SCREEN_STATE (61) Complete --- RIL [RID 0, Token 116, Success, Len 0 Off]

I will dig into details for this code base :D ...

For ringtones, probably whizkin switch off phoenix patch in the kernel for speaker always wake ( when swtiched ON the Headset will got problem ... whoahhhh ) ... I tried to swith on this option in kernel and ringtones ringing

I will upload the kernel along with rom without tilerender ... this evening. My thinking without tilerender the device will be better to render 3d ... god for gamers :D ... I changed the WEXT DRIVER TO V_08_X thetering wifi and bluetooth wroks like a charms.

Camera I will test with driver wrapper ... mean GB drivers will be wrap by ICS rom ... but this is really hard work :(
[Dell Venue] chacona:
Also, x1123, I think your previous ROM (ported from passion) runs 3G quite well, can we merge two ROM's files so that 3G is fixed for Whizkins' ICS?
[Dell Venue] x1123:
APNs Problem faced by many of custom ROM 4.0 ( I got info from googling ... :D ) RIL is very specific software layer to give certain instruction to modem for proper work .... unfortunately this software is written by vendor (htc, dell, samsung, motorolla, nokia, sony, huawei ... etc etc) under proprietary copyright is just like the camera. You and me play game with open source software with help of aosp project, cyanogen mod, aokp, caf etc etc which probably their boys have no access to this piece of software. In open source camps there are many project like nouveau = open source driver writting project for Nvidia GPU, radeon = open source project for ATI brand GPU, I found freedreno an open source project for adreno GPU. Too many vendor having their own RIL code base, thus not easy for open and free devs to have information access how a hardware works. Other things, we are going to LTE, after hxdpa, hsdpa, gprs, wcdma etc etc. and a ROM probably can not cover all of network architecture served by carrier ... as you can see RIL DEFAULT PROPERTY FOR HTC getting longer and longer. DV Ics "thought" and become real coming from DS environment thus a lot of configuration still using DS configurations, we as hobbyist make trial to fork everything available on public space to build ICS rom for DV .... the result still not so good but we will not stop.

apns-conf.xml copy file what we have is probably 1000th copy from somewhere nowhere ... aosp project confirmed APNs list in android is absolutely generated from a file apns-conf.xml located at /system/etc/ folder .. in some respect a carrier work hard to protect their interest thus APNs list will NOT SHOW unless triggered by a set of file written by a carrier roger and orange case for DV 408 rom GB base is developed by olleh and we probably copied apns-conf.xml from them :D who knows that olleh did not do something there .. I downloaded more than five apns-conf.xml file from various internet sites and flashed to DV Ics (my own built and whizkin).... the end result is exactly same. No APNs list appear on device. I believed more people try to build a rom will give more info and experience. I can write simple tutorial special for DV to have more people do build test ... it is now easy. Fyi in my box i3 processor with 8 GB ram spent 185 - 216 minutes to build a ics rom depending of configuration i.e you can choose common_mini_phone configuration which lighter than common_full_phone configuration.

Today you can sync cm9 source, download WHIZKIN SOURCE AT GITHUB put the whizkin file to /device/dell/venue. download ADRIDU KERNEL FILE AT GITHUB put somewhere among the rom source > default is kernel/device/kernel-folder-name > appoint the kernel source in BoardConfig.mk and ascertain certain kernel config .... rom will build flawlessly ... NOOBPROOF all files area available with google help.

sorry for long writting ...
[Dell Venue] kibuuka:
As of APNs and 3G - GB's apns.conf would not work with ICS rom - use one that's shipped with cm9. rild from dell's GB roms known NOT to work with 3G data when used in ICS roms. Struggled with this problem myself - the only way to get 3G working on streak's ICS port was using rild from older froyo-based roms. Using froyo rild however is partial solution - some users reported 3G being still unavailable to them. From what we've learned in process - there was some operator incompatibility (i was unable to reproduce it - 3G data worked with every mobile operator's SIM i have in my area :)) Another argument for using froyo's rild - it has no infamous USSD bug in it and hence ain't need any patching :)
[Dell Venue] adridu59:
Hi, I believe you linked to the wrong repo. The right one is here :

https://github.com/adridu59/dsc-team-kernel-project
[Dell Venue] WhizKins:
Sorry for the late replies guys, I'm busy with college lately.

If we build a working ICS, moving to JB will not be that much of a hassle as far as I understand.

I stay in North-West Delhi in Pitampura :D

Thanks for that kibuuka, I'll try to incorporate those changes in my next build :)

As for camera, I tried to build a camera wrapper and made the library to load but it crashes the phone when opening the camera (Black screen). I'll have to strace and get useful debug info though. Do you guys have a working camera for Streak?
[Dell Venue] terminal17:
Guys one question...can we use a working ics or jb rom as base...and make changes in the build.prop file and use that on our device?
[Dell Venue] kibuuka:
Short answer is - you can try, but you'll most likely fail to :)

There're portions of rom (any rom, "working" or not :)) that are device-specific. This automagically means that venue (actually, any other phone/model) needs a bit of hand (by "hand" i mean tailoring sources for specific device configuration) work to make rom suitable for/functional on it. Best solution (imho) is taking source tree (aosp, cyanogen, you name it), applying device specific patches, making proper /device/ section and building rom from source. This approach provides best results in terms of configurability - you're not limited to other rom's compile time options (compiled in resources, to name one - if you use mdpi rom as base - interface will look crappy on hdpi device). Another trouble i've ran into while messing with ics rom for streak - i had to tweak portions of usb related code to make sd mounting work - and changes made were unique for streak - devices using similar hardware used different (remember, these're devices that are almost identical to venue/streak in terms of hardware parts used) settings for sd mounting to work properly.
[Thrive Themes and Apps] icedventimocha:
*****ATTENTION*****

Please do NOT post this apk anywhere else. Anything you find wrong should be posted in this thread, please do NOT rate or give a review in the playstore based on your experience with this apk. Please leave feedback or let me know if I missed/messed something up.

*****PLEASE MAKE SURE YOU UNINSTALL PREVIOUS VERSIONS BEFORE INSTALLING THIS APK*****

Thanks:

Twitter

Developer CleAndroid and Upward Spiral for the .9 images (I hate those things)

If you like it hit thanks

Screenshots and downloads:

RED http://bit.ly/QqfVWD

ICS BLUE http://bit.ly/TyqbsM

BLACK http://bit.ly/Zasohm

GREEN http://bit.ly/TdauaF

ORANGE http://bit.ly/Tdexnm

PURPLE http://bit.ly/YVhYTI

PINK http://bit.ly/WJeFRo

HIPPIE http://bit.ly/UdVUhk

CAMO http://bit.ly/TxWw0G

FLAME http://bit.ly/SBMQDp

BLOODY http://bit.ly/SBPp8G

STEEL http://bit.ly/WOvXfV

NIGHTSKY http://bit.ly/RMjx3F
[HTC EVO 3D] jaku78:
Hi,

I already had an unlocked bootloader but I installed a ROM that updated my HBOOT to 1.58 LOCKED. Now I was trying to wipe that with a super wipe and now I'm stuck being unable to get to the recovery (it just brings me back to the bootloader) and my normal start up is stuck at the HTC logo. Can anybody tell me what I should do? What direction I should go into fixing this? I already had s-off from before.

Thank you.
[HTC EVO 3D] Amel.Spahic:
You probably don't have recovery. There are many threads on "how to install recovery"..Also, you have this: (It works on both CDMA - which you have, I suppose, and GSM)

[YOUTUBE]Gv6EYaIKoH8[/YOUTUBE]

Also, you have some interesting stuff HERE
[HTC EVO 3D] coal686:
What pro said. Also, if you're s-off, the locked bootloader doesn't matter. If you have trouble after trying to flash a recovery, you could also run the ruu.exe to reset everything back to stock (you'll stay s-off) and then flash a new hboot and recovery and then custom ROM. I did that recently and it fixed my issues.
[HTC EVO 3D] jaku78:
Thanks for the fast replies both of you. That's really interesting situation because I know I had recovery before. You think I should still go for it?

EDIT: Looking at that video it looks like its installing an app, my phone won't get past booting up. Basically all I got is my HBOOT. I'm going to try what coal suggested.

What Coal told me to do worked, I'm back into stock and it boots up fine now. I'm going to try to get a new hboot and recovery now.

I was able to get down to 1.4 HBOOT again and flashed a CM10 ROM. Thanks for your help guys, you lead me in the right direction
[HTC EVO 3D] Amel.Spahic:
You are welcome..
[HTC EVO 3D] mnomaanw:
You would just have flashed another recovery using a PG86IMG.zip. or fastboot ..

---------- Post added at 10:18 AM ---------- Previous post was at 10:17 AM ----------

The "LOCKED" or "RELOCKED" status matters if you are trying to flash boot,recovery partitions etc using fastboot.
[HTC EVO 3D] ramjet73:
I agree that it matters, but you can gain access to those fastboot commands if you are S-OFF by flashing a custom recovery such as JBear, Revolutionary, or the engineering (ENG) bootloader, at least on the CDMA model of the Evo 3D/V. I highly recommend that over unlocking the bootloader since having a locked hboot makes it much easier to return to 100% stock. Not so much with relocked since the only way to get rid of that status is to set S-ON and do the wire tick.

ramjet73