yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] hunderteins:
and that link is there, too?

"dhd.ko -> /lib/modules/dhd.ko"

hunderteins
[Streak 5 Android Development] peddi_th:
do you wand me to open the file dhd.ko and see if the abocve command present or not?
[Streak 5 Android Development] hunderteins:
Don't get me wrong. Compiling kernel and glueing boot.img is different from compiling

libs and other android userspace binaries.For example: At the moment I even didn't have

a working dell device-tree that fits into android 4.0.4_r2.1.

Although I have a slight idea, what is a major bumper at the moment (missing overlay in libui.so of ics

what our libcamera.so from gb expects) I don't expect a working camera soon.

hunderteins

---------- Post added at 10:44 AM ---------- Previous post was at 10:44 AM ----------

just show me your output of

ls -l /system/lib/modules/dhd.ko
[Streak 5 Android Development] peddi_th:
Please find the attached screenshot of my mobile.

Thanks

Peddi Reddy
[Streak 5 Android Development] hunderteins:
o.k. than the update script didn't work :(

can you get root inside your commandline? For example with the command su?

Than type in

# rm /system/lib/modules/dhd.ko

# ln -s /lib/modules/dhd.ko /system/lib/modules/dhd.ko

in the end there should be:

# ls -l /system/lib/modules/dhd.ko

lrwxrwxrwx root root 2013-11-14 06:46 dhd.ko -> /lib/modules/dhd.ko

(with other dates of course)

hunderteins
[Streak 5 Android Development] peddi_th:
Thank you,

I have executed above commands and now dhd.ko is referring to /lib/modules/dhd.ko and with different timestamp.

wifi is working now.

Thanks

Peddi Reddy
[Streak 5 Android Development] hunderteins:
I've got a little something for you

camera-app is still not working with this ROM, but at least I'm out of force closing and logcat looks funny :)

I took http://xdaforums.com/showpost.php?p=20281617&postcount=17 (=camera.streak.so) with camera.apk from ankuch and compiled in the patches from zbwu86 (Overlay = libui.so and MemoryHeapPmem = libbinder.so)

can please someone confirm my findings?

have fun,

hunderteins

edit: removed attachment, camera.apk from ankuch force closes, stock one is better
[Streak 5 Android Development] peddi_th:
applied the above update and didnt find any change in camera behavior.

cannot connect to camera.

I checked the timestamp of the file libui.so and it is showing some old timestamp.

I guess update didnt happen.

Thanks

Peddi Reddy
[Streak 5 Android Development] hunderteins:
Thank you for your replys. What custom recovery do you use? can you provide a logcat?

You can always use root-explorer and extract and replace the files by hand and kill/restart /system/bin/mediaserver with "killall mediaserver"

have a nice evening/day,

hunderteins
[Streak 5 Android Development] peddi_th:
I have replaced the files and reboot the device. little bit improvement in system performance and camera .

still camera is not working.

Thanks

Peddi Reddy
[Streak 5 Android Development] sinan33:
Did you checked the timestamp of the file libui.so?
[Streak 5 Android Development] hunderteins:
that camera.apk from ankuch force closes when you try to take a photo. Don't replace it with your stock one. But when you replace the libs (including camera.streak.so) you should at least can "use" the camera-app. It will not take photos, yet - The jpeg in /sdcard/DCIM/Camera is all green.

For now, I need my Streak working, so I go back to DSC. But I'll collect camera-data from there to find out, how liboemcamera.so is called. I'll need ltrace for android.

Does anyone remember why libstagefright.so on DSC and even 407 depends on the missing libmmparser.so and libmmparser_lite.so. Is it an oem-version from Dell?

The libstagefright.so from my android 4.0.4.r2.1-build doesn't have that dependency and I did not notice a regression with it.

have a nice weekend,

hunderteins
[Streak 5 Android Development] kibuuka:
[MENTION=2010230]hunderteins[/MENTION]: As of device tree/rest of source tree - i've got these floating around. If you need them, pm me, i'll archieve them and 'll setup ftp account for you.
[Streak 5 Android Development] sinan33:
[MENTION=2010230]hunderteins[/MENTION]

At the beginning of ICS development for Acer liquid E the green jpeg issue was occurred.

But then the devs (ThePasto) solve this issue; maybe they can help us?

I think the next step is easier than the most important step that you have solved.

Thanks your effort and time!

Best regards...
[Streak 5 Android Development] peddi_th:
Yes, I did and it is showing latest timestamp.
[Streak 5 Android Development] mokokawi:
Anyone get data working on at&t network?? If so.....what's your network settings
[Streak 5 Android Development] peddi_th:
HI ,

Thanks for your great work and can I update my device with this .zip as usual and test it?

Thanks

Peddi Reddy
[Streak 5 Android Development] sinan33:
[MENTION=2010230]hunderteins[/MENTION]

If i am not wrong _n0p_ has solved the HAL issue before.

Maybe he or kibuuka can help us.

Thanks your effort and time!!!

---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------
[Streak 5 Android Development] peddi_th:
Please have a look into this...it may help you to resolve msm_get_stat error.

http://lxr.free-electrons.com/source/drivers/staging/dream/camera/msm_camera.c?v=2.6.35

Thanks

Peddi Reddy
[Streak 5 Android Development] _n0p_:
[MENTION=2010230]hunderteins[/MENTION]:

I'd love to help, but i think SIGFPE was my issue too.

I beleive it's was some code calaculating frame parameters.

Also:

http://xdaforums.com/showthread.php?t=1834458&page=4

Also, i remember this guy succeeded:

https://github.com/Dorregaray
[Streak 5 Android Development] hunderteins:
It seems ICS is handling signals different than gingerbread. On top of my strace.log I find:

GB

getpid() = 5979
sigaction(SIGILL, {0xb000586d, [], SA_RESTART}, {SIG_DFL, , 0x97fa0) = 0
sigaction(SIGABRT, {0xb000586d, [], SA_RESTART}, {SIG_DFL, , 0x97fa0) = 0
sigaction(SIGBUS, {0xb000586d, [], SA_RESTART}, {SIG_DFL, , 0x97fa0) = 0
sigaction(SIGFPE, {0xb000586d, [], SA_RESTART}, {SIG_DFL, , 0x97fa0) = 0
sigaction(SIGSEGV, {0xb000586d, [], SA_RESTART}, {SIG_DFL, , 0x97fa0) = 0
sigaction(SIGSTKFLT, {0xb000586d, [], SA_RESTART}, {SIG_DFL, , 0) = 0
sigaction(SIGPIPE, {0xb000586d, [], SA_RESTART}, {SIG_DFL, , 0x97fa0) = 0
getuid32() = 0
geteuid32() = 0
getgid32() = 0
getegid32() = 0

ICS

getpid() = 511
getuid32() = 0
geteuid32() = 0
getgid32() = 0
getegid32() = 0
sigaction(SIGILL, {0xb0005909, [], SA_RESTART|SA_SIGINFO}, NULL, 0x4a33c) = 0
sigaction(SIGABRT, {0xb0005909, [], SA_RESTART|SA_SIGINFO}, NULL, 0x4a33c) = 0
sigaction(SIGBUS, {0xb0005909, [], SA_RESTART|SA_SIGINFO}, NULL, 0x4a33c) = 0
sigaction(SIGFPE, {0xb0005909, [], SA_RESTART|SA_SIGINFO}, NULL, 0x4a33c) = 0
sigaction(SIGSEGV, {0xb0005909, [], SA_RESTART|SA_SIGINFO}, NULL, 0x4a33c) = 0
sigaction(SIGSTKFLT, {0xb0005909, [], SA_RESTART|SA_SIGINFO}, NULL, 0x4a33c) = 0
sigaction(SIGPIPE, {0xb0005909, [], SA_RESTART|SA_SIGINFO}, NULL, 0x4a33c) = 0

It seems on GB the SIGFPE was not fatal, but on ICS it is.

So I set it to SIG_IGN before I get into HAL_openCameraHardware(0);

So that control-Thread from libcamera.so is continuing working and talks to the worker in liboemcamera.so via /dev/msm_camera/config0

old_handler=signal(SIGFPE, SIG_IGN);
camera = HAL_openCameraHardware(cameraid);
signal(SIGFPE, old_handler);

But now I have a ugly SIGSEGV in setParameters with parms = 0x41252cd4, when in GB the parms was 0x40706d1c.

I was manipulating the CamParameters in camera_get_parameters() with setting KEY_SUPPORTED_PREVIEW_SIZES and so on,

but it seems the other side is just ignoring these, when I look into the parameters I get in camera_set_parameters()

I noticed also, that in camera_set_parameters the const char *params stops uneven at 1000 chars.

all for now, I got work.

hunderteins
[Streak 5 Android Development] abauer:
[MENTION=1168675]hundred[/MENTION]eins the new Kit Kat is supposed to be build with legacy devices in mind 512 mb ram, so the streak should do very well, maybe it would be worth to try to port it, just a thought though.
[Streak 5 Android Development] hunderteins:
camera.msm8660.so

gingerbread-libcamera.so-wrapper conducts into SIGPFE-blind alley. So I checked for alternatives.

I tried camera.msm8660.so. That stopps at mm_camera_get_camera_info cause it uses the ioctl MSM_CAM_IOCTL_GET_CAMERA_INFO that is not implemented in msm_camera.c. After I integrated that routine (1) into AUSTIN_CAMERA and increased some command buffer I got a really elaborate logcat. Very informative, but it stopped at setParameters again.

just to keep you updated,

hunderteins

(1) https://github.com/dsc-team/dsc-team-kernel-project/commit/716b9987ec1b4e37262ed10f1f4d37777396a43c
[Streak 5 Android Development] hunderteins:
I patched all setParameter-functions to make missing props not fatal. Now I'm one step further: the problem is start_preview(). It fails at

E/MemoryHeapBase( 574): mmap(fd=36, size=462848) failed (Invalid argument)

I allready patched libbinder.so with MemoryHeapBase, but it had no effect on this problem. Has anyone that Lenovo S2005 ICS ROM-zip (1) handy? I'm to stupid european, to load it from that asia-site.

To make this library really talkaktive you may set

setprop persist.camera.mmcameradebug 1

setprop persist.camera.hal.capture 1

setprop debug.camera.qcamerahaldebug 1

hunderteins

(1) http://115.com/file/be6mfk0d#SNARL-IT168-V7-BASE.zip
[Streak 5 Android Development] kibuuka:
Was not really hard, actually (thanks to google translate) :) here you go
[Streak 5 Android Development] hunderteins:
/dev/ion not avaiable on kernel < 3.0

Hello,

I have reached another deadend in the approach with camera.msm8660.so from lenovo s2005. As you can see in the attached logcat, I circumvented the problem with that mmap from above with canceling setPreview in Camera.apk. This way the camera app starts, but has no preview. When I try to take a picture, I get an error that I cannot fix. For this driver /dev/ion (a memory-manager build in into 3.0 kernels) is mandatory. This is o.k. on the lenovo s2005 with it's 3.0.8 kernel, but not on our dsc-ics kernel that is 2.6.35.14 based.

Just for reference I attached the modified files (liboemcamera and camera.msm8660.so binary patched), if you ever get a 3.0 kernel for the Streak or want to check my findings.

For now, I'll go back to zivans56/dorregaray approach with a standalone driver for qsd8k.

Have fun,

hunderteins
[Streak 5 Android Development] hunderteins:
Hello,

I tried to reverse engineer (1) libcamera.so from 407 and found some starting points. It seems the CameraHardwareInterface differs from any other modell (qsd8k or not) camera hal I tried until now. We've got 11 more functions at the end of that table.

The attached CameraHardwareInterface.h is what I gathered from " `vtable for'android::QualcommCameraHardware" in libcamera.so. Some functions are clearly dummies - like getPanoramaCount() or getPanoramaMaxCount() but for others I have no idea how the parameters might look like. For example 'sendCamHalCtrlCommand()' with parameter 'CamHalCtrlCommand_t' nags me most. It's not funny when you google some functionname or parameter structure and there is not a single hit for it. But I found references into setSelfTimer(int,ulong), setMultiShot(ulong), setMultiShotDone(ulong) and setSensorEngMode(ulong) inside that function. So I guess it is some extention that is not basically needed. I'm also not sure about the return-values of all these functions.

Clearly streak specific is switchSensor() which accepts "ov5642" or "ov7690" and writes them into /sys/class/msm_camera/austin/status. (this I tried and it switched sensors)

To find more about the differences of 407 and gingerbread aosp. I decompiled 407 framework.jar and that of gingerbread aosp. This brings attachment diff_camera_aosp_407.txt. It seems we get more CAMERA_MSG_* from libcamera.so than other models: CAMERA_MSG_STATS_DATA, CAMERA_MSG_META_DATA have to be dealt with. We also need functions like native_encodeData() or native_sendMetaData() or native_setFaceDetectionCb(boolean paramBoolean). I've no idea how to set especially the callbacks in our camera hal, but I think that they must be set to work with the 407 libcamera.so/liboemcamera.so

Last but not least, I gatherd the parameters that are set from 407 camera.apk when the camera starts (that is one point the ics-version stopps working) This is done like described in (1) by attaching gdb to the living mediaserver process. This is the attachment gdb.txt.

That was fun, but I'd like to tap into the start-up of CameraService, to see how the camera is initialized on system start.

All for now,

hunderteins

(1) http://xdaforums.com/showthread.php?p=19943347
[Streak 5 Android Development] muteman3:
Same thing with animation to rotate the screen. First rotate 180 degrees and then in the right position.
[Streak 5 Android Development] kibuuka:
Hmm. I've patched oasp sources to make portrait mode behave right (there was no support for 180 degree rotation, 90 and 270 only), w/o it boots with flipped screen.
[Streak 5 Android Development] TheManii:
I guess that's not the preferred way to do it, I know our device isnt the only one that has an upside down screen. But you know the code better then me so I cant say much more.

I'm gonna run down the list and test everything I can, I can say that GPS works fairly well.

Small suggestion: Perhaps you should change the date stamp in the rom's filename to be YYMMDD instead of DDMMYY, it's much more approporate for date build numbers. It's only a suggestion though.
[Streak 5 Android Development] deysmacro:
for mass storage mode, cant we use external apps such as Dual Mount SD or something like that? something like a workaround apps...
[Streak 5 Android Development] TheManii:
Tested some stuff: SMS works but cellular data is completely broken as I can seem to save APNs.

GPS works, and AGPS might via wifi, but I cant tell. AGPS wont work without wifi though as it would need cellular data without wifi.

Can anyone else confirm that it's not just me that cant set APNs?

My setup:

Double fac reset on install: Boot menu and streakmod

At&t sim

Entered APN info from venue (with working data) and selected save and nothing saves

I dont currently have any access to adb as I cant install the drivers on Win8RP/x64. Thus I cant check logcat.
[Streak 5 Android Development] kibuuka:
Confirming, this part is completely broken at the moment. Trying to fix, will write back when build is finished and tested.
[Streak 5 Android Development] TheManii:
Ok, waiting to report back when you have something new for us to test :D

Wish I could recompile API15 apks so I could mod the virtual buttons that ICS otherwise has :(

Edit: are you using the stock RIL binaries from 407? If you are remember to use the patched one that fixes USSD codes.
[Streak 5 Android Development] kibuuka:
Oh and btw. Is there a way (build.prop setting maybe) to control webkit behaviour system-wide? If you disable OpenGL rendering (about:debug, then settings, debug, uncheck Use opengl renderer) - pages will render just fine.
[Streak 5 Android Development] TheManii:
You're right that it fixes it, but it doesnt preserve that setting on a force stop of browser and restart.

You could mabye hardcode it to not use OGL rendering until you figure out why OGL rendering breaks it I guess.
[Streak 5 Android Development] :
hey have you looked at CM9 source

with hPA patches
[Streak 5 Android Development] TheManii:
I've briefly taken a look at his CM7.2 code but not his CM9 code, just as much I'm not currently a serious coder.

Also: I do believe that the headphone icon is now removed from ICS, after looking at a NS stock 4.0.3 dump the old icon is simply not in framework-res or SystemUI anymore. The most logical answer is that it no longer exists.
[Streak 5 Android Development] kibuuka:
One silly question about way frameworks.jar being built

While browsing thru source tree i've noticed that aosp lacks vendor-specific RIL files in frameworks/base/telephony/java/com/android/internal/telephony/

CM has one file named QualcommSharedRIL.java. gingerbread branch of CM source tree had QualcommNoSimReadyRIL.java (name looks familiar, no? :))

ro.telephony.ril_class=QualcommNoSimReadyRIL

The question is - will simple dropping in of this file in aosp source tree will it be enough for it's compilation into the frameworks.jar or it should be explicitly set for compilation somewhere in makefiles?

(i know that's a silly question - i'm by no means a java person. just provide me with answer, thank you :))
[Streak 5 Android Development] TheManii:
Since goog cant force vendors to supply their ril sources, they just expect them include the binaries in the final assembly (even on the nexus devices).

Rest of it I really have no idea, but pretty much noone has the ril source except the device and/or baseband makers.

Are there any compile errors from it being missing at least?

Edit: do you even know for a fact that ro.telephony.ril_class is needed?

Neither the S5/GB nor the NS/ICS have that, only rild.libpath and rild.libargs.

The V/CM7.2 had: ro.telephony.ril_class=venue which sounds like a dummy value and the S5/CM7.2 had ro.telephony.ril_class=streak.

I can say with certianty that both devices functioned correctly (cellular wise) with those dummy values.
[Streak 5 Android Development] kibuuka:
Since it not in aosp source tree - there's no missing file errors :)

As of need of custom ril class - check this

View attachment logcat_b_modem.txt

- i believe ConnectivityService has difficulties that are RIL-related :)

ADD: grepped source tree - aosp sources contain no references to ro.telephony.ril_class at all. Please make a quick check - on venue's CM rom comment ro.telephony.ril_class out and tell if anything changes in gsm connectivity.
[Streak 5 Android Development] TheManii:
commenting out ro.telephony.ril_class seemed to give the same issue on the V/CM7.2 as in that cellular data didnt work, but changing the S5 to =streak didnt fix it though.

Edit: it could be specific to CM, as CM does add a lot of things.
[Streak 5 Android Development] kibuuka:
reading through cm sources - they surely added loads of code :)

Now I'm wondering if any of aosp roms running on non-reference devices is really aosp :)
[Streak 5 Android Development] mikegapinski:
For wifi you need to make WPA Supplicant version 6(it is on CM source). For Bluetooth ap you need: https://github.com/PolishBloodProje...mmit/0d58798e5901fef0fe482e526304ce4c86a5f15b For msm_fb problems with codecs: https://github.com/PolishBloodProje...mmit/30a26de68aad5b89588cce6b705998c6fac08b7a

Codecs, Qcom stuff:

https://github.com/PolishBloodProje...mmit/0a67069684e70c7545e90ee9eca57c9f6ed83772

https://github.com/PolishBloodProje...mmit/bce0c09e084e044ef7db28608f8d9c2b9482bb8a

https://github.com/PolishBloodProje...mmit/779253bf0d611ba2dcf60274f29e1c9528538823

https://github.com/PolishBloodProje...mmit/d97268d6a8b3acb9c59e92a8da354672d3d9c1e7

https://github.com/PolishBloodProje...mmit/7097d0ed3071c796f525cd71e40995e0fbb34f29

https://github.com/PolishBloodProje...mmit/e63c0bb2043c34060f779fe53b2d977d3e27f4bd

Ril:

https://github.com/PolishBloodProje...mmit/49714d3e43acafe8c5665339b446e4cb2fc99223

You will also need to add this to prop:

ro.telephony.ril.v3=signalstrength,skipbrokendatacall,facilitylock,datacall,icccardstatus,1

If that will work I will post how to fix more stuff
[Streak 5 Android Development] kibuuka:
Hey Mike. Will try your variant of ril backport - got my own instance already, but it got severe issues. Thanks for your efforts.

Wish there were no need for sleep :D
[Streak 5 Android Development] sinan33:
Thank you for your efforts and time Mike!

We are looking for your ICS rom too.

Thanks for both of you!
[Streak 5 Android Development] nom051205:
Wooowwww.....what a great moment, more dev comes more bugs fixed.

Yeeaahh....this ICS baby will grow up fast..:D
[Streak 5 Android Development] msprakashmmc:
Thank you so much for your effort mike :-)

Hope to see your support throughout the ICS project & also for all future versions too dude..:-) We ll support you always :-)
[Streak 5 Android Development] Crinos512:
ICS ActiveSync System Encryption.

I tried to set up Exchange email on this rom and was informed that I needed to encrypt my system.... Ok, I'm game.

fail. :eek:

logcat shows the reason as

not a biggie, except that the email notice saying I must encrypt will not go away and I cannot complete or cancel the email setup until it does.
[Streak 5 Android Development] lordmorphous:
Can you go into Settings -> Applications and clear data for the email app?
[Streak 5 Android Development] Crinos512:
nope... shows no data set yet. Need to do a fac. reset most likely. :-(

ah well.

Another feature request would be the option to reboot instead of simply shutdown... it's the little things.

---------- Post added at 11:04 PM ---------- Previous post was at 10:36 PM ----------

Similar issue? :confused:
[Streak 5 Android Development] kibuuka:
Ok, Mike, there're results of using your ril wrapper backport:

Data call not possible

logcat -b radio:

if (!allowed && DBG) {
String reason = "";
if (!((gprsState == ServiceState.STATE_IN_SERVICE) || mAutoAttachOnCreation)) {
reason += " - gprs= " + gprsState;
}
if (!mPhone.mIccRecords.getRecordsLoaded()) reason += " - SIM not loaded";

EDIT: Resolved second issue.
[Streak 5 Android Development] green750one:
Hi.

Not a dev, but experienced in testing & as my ds5 is no longer my daily phone am happy to get involved in testing.

Long time Android user & an used to fastboot, flashing roms etc

Cheers

P.
[Streak 5 Android Development] dimasrafi:
Well done kibuuka

I appreciate your work on Dell Streak 5, and here I report to you I used this pre Alpha 4.0.4 used for my daily activity after you lunch the last update at 23rd June. IMHO everything works fine to me except camera and gps when I install SYGIC, browser worst but I use Opera Browser as alternative and work really fine...touch screen is fine even still little lag but work fine..phone, sms work.

Keep this work bro...., and let me be your tester...:good::good::good:
[Streak 5 Android Development] mikegapinski:
Try to specify what kind of RIL you use in build.prop. Without it phone won't load Qcom RIL for example.
[Streak 5 Android Development] kibuuka:
Tested with every single custom RIL. Result's are more or less equal. Also, i believe prob is generic and not depending on custom RIL handler as getIccRecordsLoaded() is called form PhoneBase.java
[Streak 5 Android Development] mikegapinski:
Compare it to GB, maybe there are some changes related to this device in CM7 frameworks
[Streak 5 Android Development] kibuuka:
Thought of it, will try with froyo rild.

UPDATE: Ha! Used rild from froyo-based rom - it's worked for data connection when ril class being unset in build.prop (it fails to query active networks, though).

Dear Dell, GJ at breaking things! *sigh*

Okay, since we have termporary workaround for mobile data now, it's time for fixing something else, i guess. Stay tuned.
[Streak 5 Android Development] msprakashmmc:
Wwwwoooowwwww... What a COMBO effect from MIKE & kibuuka..:) This is what we Wanted..:) Thanks for your Support Mike & kibuuka..:) :) Getting ready to taste ICS..:):)

And also Congrats For all your work to WAVE mike..:) Really Wave Users Rejoice With ICS now...:) I saw the thread, Really U made our dream to come true..:) Eagerly Expecting Further Updates & ready for testing dude..:):)
[Streak 5 Android Development] green750one:
Mmmm. What am I doing wrong? Complete failure factory reset. Clean flash of gingerstreak 2.44. Factory reset again plus delvik & cache clean. Flashed both ICS & gapps zips. Factory reset again. Reboot but stuck on android boot logo.

Suggestions? Really want to provide some feedback for the devs.

Cheers
[Streak 5 Android Development] kibuuka:
You may try to omit last step. Also, which baseband version you have?