yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] RickyGoldsmith:
So I went and checked it out myself.

As suspected, it is more complex than thought. First, most of these vendors ship the binary-only blobs along with the kernel. Second, even if we try to pick the binary-blobs, it depends on how adaptable the binary was built (not just the kernel, also the userspace stuff). Then there is HAL, but is not much of use with binary-only drivers.

I guess folks will have to live with this MIUI ROM, or the Stock GiONEE ROM, for an unseeable future.
[Miscellaneous Android Development] Ganesh Kumar:
Soo disappointing:(:(:( ..mobile is good but not able to upgrade software....
[Miscellaneous Android Development] debasish497:
What is the future of this development thread,.... Are we trying with some other porting? Sad that Gionee has disowned this device in this manner.
[Miscellaneous Android Development] RickyGoldsmith:
Well!!! We do have a working ROM for now. Will be there another one? Maybe Yes. It'll depend on how long I can keep getting a based 4.1.2 ROM available.

With no newer kernel in place, I'm afraid if things would change, for newer porting.
[Miscellaneous Android Development] Fury3D:
Hi guys, i want to know if this rom works on my Blu Vivo 4.65HD d930i. I think its a same phone, Allview p6 stony too. Can anyone help me? Thank you!
[Miscellaneous Android Development] mihirf2003:
Hi, I updated my baseband to a new version as mentioned in the 3rd post, but after that the phone is not able to connect to 3G network. It always shows 2G data, and when I try to connect to WCDMA only, there is no network. I am using Vodafone and it worked perfectly fine with the older baseband. Has anyone faced the same issue? And how can I shift back to old baseband?

Thanks

UPDATE: it is confirmed that the baseband update weakens the 3G signals. I restored my earlier backup before updating the baseband and now 3G works perfectly fine.
[Miscellaneous Android Development] deepak2111:
as mtk source tree is not full or faulty. there is no hope for new kernel or development..

though development is going on.. by enthus.. like

varun.chitre...at here

bucefal82......at here

lenz flare..at here

so keep working..
[Miscellaneous Android Development] daemol:
Do we need full sources for MIUI porting? Can't we use patchrom method to make the ROM working on this device?
[Miscellaneous Android Development] deepak2111:
take a look...miui porting guide
[Miscellaneous Android Development] Ganesh Kumar:
Even I'm facing same thing how to update old baseband version?
[Miscellaneous Android Development] daemol:
I was referring to https://github.com/MiCode/patchrom

No sources needed and receive OTA updates. They have even published a sample build for Lenovo A830
[Miscellaneous Android Development] OpenMinded:
would anyone know how to fix the front cam issue?

I made a port based on the N828 for another device and have the same issue.

I think it work before I added serveral /dev/cambla's to init.rc .

Perhaps removing of those that are not needed?

If someone knows, it would be great if we can fix it :).
[Miscellaneous Android Development] RickyGoldsmith:
Posting it public to the community also, for others to benefit.
[Miscellaneous Android Development] RickyGoldsmith:
Not just a sample. They have a full ROM release for the A830.

The patchrom branch for MTK is based for Android ROM 4.2+

This GiONEE device (GN878, QNOIR, Walton et cetera), has only had ROM update up till 4.1.2.

We have friends working hard to make the 4.1.2 shipped kernel work on the 4.2 ROM. Stay tuned. You might soon see another thread (with another ROM) for this phuckin' device. :D:D:D:D:D
[Miscellaneous Android Development] RickyGoldsmith:
If you don't know what you did, you will not know what to fix.
[Miscellaneous Android Development] OpenMinded:
I do not understand your comment fully.

I pretty much know what I did, I got a nearly working MIUI port of a Amoi N828 on my Star N9389.

In the OP you mention a specific camera issue with the front cam, that I have as well.

I was hoping anyone knows a solution to that, thus helping fix this ROM and my port :).

I suspect it might have to do with the init.rc in the boot.img.

I posted here about that:

http://xdaforums.com/showpost.php?p=44585557&postcount=975

I thought I'd "ask around" because there are a lot of experienced porters here who might know.
[Miscellaneous Android Development] daemol:
Well, that is a great news. New devices from Gionee, ELIFE Series are shipped with 4.2 ROM.
[Miscellaneous Android Development] RickyGoldsmith:
The front cam issue has got to do with the auto focus mode. The libs are a hodge podge of Lenovo + GiONEE. And then, the cam app is from lenovo. But then, the driver is from GiONEE. This phucked up combination makes it br0ken in certain circumstances.

I hightly doubt it'd have any thing to do with with an rc service script. But hey,, if you do find a resolution, please do share here too. :cowboy::cowboy::cowboy::cowboy:
[Miscellaneous Android Development] RickyGoldsmith:
But I don't know if that makes it compatible with Dream D1 aka GN878. Can you confirm that for us?
[Miscellaneous Android Development] OpenMinded:
I am unsure, what resolution does the device have?

I do think the issue may have a similar source.

The camera is in the gallery2.apk, I do not think any device specific stuff is in there.

It's the lib, hw and firmware dirs and the init.rc that seem to matter.

I wil try to make time to play more with init.rc. if you have please do.

An approach would be to only add devices that are needed for the two cams.

mine has ov8825 and another.

I need to sleep now, work tomorrow :).

cheers
[Miscellaneous Android Development] vizhigal:
My D1 front camera is ov9726_mipi_raw and the back camera is ov8830_mipi_raw ( no kernel source is available for this ov8830).

Elife E3 front camera is ov2722mipiraw ( 2.0 MP ) and back camera ov8830mipiraw and have one more driver ov8835mipiraw. For other sensors E3 touchpanel and LCM different rom D1. For E3 the touch panel driver is is gt9xx , lcm is gn_byd_nt35590 for D touch panel driver mms144 and lcm is gn_smd_s6e8aa.

Let me check E5 if the recovery image is avilable. ( the stock rom file size is more than 500 mb )
[Miscellaneous Android Development] OpenMinded:
I have a OV7675 as front cam.

I have it partially working by adding /dev/OV7675 and clearing the app cache.

You might try and add yours the same way.

It's still flaky, it worked 4 times in a row after the app wipe, now every now and then.

Not sure why, but it's a bit better at least :).

---------- Post added at 09:13 AM ---------- Previous post was at 09:11 AM ----------

Where did you find that driver? perhaps there are some more :)

---------- Post added at 09:26 AM ---------- Previous post was at 09:13 AM ----------

mmm, found when it works: when keeping the cam-take button pressed!

No the question is: how to fix it?
[Miscellaneous Android Development] RickyGoldsmith:
Let me address this in public so that others can also be informed.

Q1: Either way is fine. You can do it from within the Android OS also. After the realignment of the partition size, the vfat partition has a possibility to get corrupted, which in your case has happened. So just format it.

Q2: No. RTFM. emmc doesn't contain the OS's system files.

Q3: What if your phone falls down and breaks into 2 pieces? The ROM is there as is. Use it if you want, or revert back to what you were using. Step 2 in the howto, for increasing the partition size, clearly stated that you should have a backup of your data

All that said, bricking an MTK device is very hard. I wouldn't be worried about that. The question is, when your OS gets corrupted, do you have all the necessary information to recover it.
[Miscellaneous Android Development] RickyGoldsmith:
Hey [MENTION=353809]OpenMinded[/MENTION]

Does that mean that Android's /dev/ management is static ? I was under the impression that the /dev/ file system was hotplug enabled....
[Miscellaneous Android Development] OpenMinded:
HI Ricky,

I don't know, I just know that some devices names are needed there because people pointed it out.

I must say I might be wrong about adding that device, because the change is gone at boot :).

Will try now with modded ramdisk and perhaps after with more devices.

Does your cam work when you keep the button pressed?

Mine does.

cheers
[Miscellaneous Android Development] RickyGoldsmith:
Nope. Doesn't work for me. I checked the link that you mentioned. It doesn't have anything apart from a couple of chown and chmods.

From your previous post, I got the impression that android has static dev file system. :laugh::laugh::laugh::laugh::laugh:

Damn the lack of time. Wish I could spend some time reading up on android os internals.
[Miscellaneous Android Development] deepak2111:
[MENTION=5347335]omarrana[/MENTION] I got your problem.give me your partition detail as said earlier by using mtkdroid tool or by dumchar_info.
[Miscellaneous Android Development] OpenMinded:
It keeps being strange. My cam sometimes even works when just pressed once, but sometimes not.

I tried copying the init.rc from the boot image from the port rom to my port, but then it does not boot.

The file structure also differs from my original boot.

I also tried copying all files, then the phone does not boot either :(.

No clue how to fix these last things:

- front cam sometimes working

- not shutting down properly.

I also have a lack of time, might have to quit without any more help too.

Thanks anyway. I'll be fiddling a bit more and let you know if I can fix it.

I have not found anything strange in logcat either.

Oh and I think the dev is mostly dynamic, because it are just settings of rights (no mknod)
[Miscellaneous Android Development] OpenMinded:
I think I figured out the Camera issue.

When I use the deoxed file Gallery2.apk on my original rom, I have the same issues like in the MIUI rom.

So the problem must be the apk.

I have tried another with no succes.

I tried my odexed files on the MIUI rom with no success.

So now I am trying to deodex it, but all automated tools I found untill now do not bloody work!

It's really annoying.

I am trying to find out to do it with smali and baksmali.

Do you have any clue?

Any help is appreciated!
[Miscellaneous Android Development] OpenMinded:
well, seems I pulled it off.

Hard to find proper docs.

One need to baksmali the odex file, decompile the apk, put the out folder files in a folder named smile and recompile.

Done that, I attached the file.

It works on my device and is signed.

Just put it in /system/app (after unzip) and rename the other, set permissions to 644 and reboot phone.

Let me know if it works.

If it does not, you can probably fix it by deodexing your Gallery2.apk and put that in the rom.

please hit thanks if you're happy, makes me happy too :).

cheers

[update]

works on my miui rom too :).

Can anyone help with that shutdown issue??

[/update]
[Miscellaneous Android Development] OpenMinded:
oh and you do need to put those "chown and mods" into your init.rc too!
[Miscellaneous Android Development] ankjain:
Help! No 3g coverage

dear all

i tried MIUI 3.1, everything went find but now my BSNL sim can catch only 2g signal:(:(, can anybody provide earlier base band? as somebody mentioned that current baseband has some problem regarding 3g signals.

also let me know how to flash it.

regards

ankjain
[Miscellaneous Android Development] RickyGoldsmith:
I will do it soon. Just been on the run. [MENTION=373710]others[/MENTION] if you have it now, could SBT of you please add it
[Miscellaneous Android Development] RickyGoldsmith:
Modem.img form Stock ROM

Bunch of folks have been complaining of bad 3G reception with the new modem. If you want to revert back to the old modem
[Miscellaneous Android Development] nathan30:
Available for other MTK devices ?
[Miscellaneous Android Development] amirfida:
can i use it on my mediatek phone Chip model is MT6589 can i use this on that ?
[Miscellaneous Android Development] deepak2111:
[MENTION=3094817]RickyGoldsmith[/MENTION] [MENTION=5277821]debasish497[/MENTION] as we discussed earlier we have kernel 4.2.1 which booted on our device, so it can be possible further development?
[Miscellaneous Android Development] debasish497:
we are not sure of the boot image,.. how much it works,..
[Miscellaneous Android Development] vizhigal:
Is the boot.img uploaded in the FB forum by Mr.vishu is from 4.2.1?
[Miscellaneous Android Development] deepak2111:
Sony xperia C sources

http://developer.sonymobile.com/dow...es/open-source-archive-for-build-16-0-a-0-36/
[Miscellaneous Android Development] amirfida:
i have the same chip as this phone only problem is i cannot port this because the base is diffrerent mine one is Android 4.2.1 and this one is Android 4.1.2 is there any way i can make it work ?

Thanks

EdiT : guys my device has kernel 3.4.5 if you guys need that just tell me what files you need and provide it to you ;)
[Miscellaneous Android Development] debasish497:
Do you have the same device gn878?... if that can you share your stock rom?
[Miscellaneous Android Development] amirfida:
no sorry mate it's Xtouch X1 ... but same specs as dream D1
[Miscellaneous Android Development] Ganesh Kumar:
Development is stopped for this mobile:confused::confused::confused:
[Miscellaneous Android Development] debasish497:
no paused
[Miscellaneous Android Development] hamsam:
Hey i have a questions??

Does it work with every mtk6589 device??
[Miscellaneous Android Development] :
I too would like to know that. I want to try this on my hy5001
[Miscellaneous Android Development] deepak2111:
Interesting development here.

http://xdaforums.com/showthread.php?p=45962288
[Miscellaneous Android Development] RickyGoldsmith:
Call for help with BOOTCLASSPATH

Do any of you know what this is and how to fix it???

D/AndroidRuntime( 909):
D/AndroidRuntime( 909): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit (start-system-server) <<<<<<
D/AndroidRuntime( 909): CheckJNI is OFF
D/AndroidRuntime( 909): language=-Duser.language=zh region=-Duser.region=CN
D/dalvikvm( 909): boot class :
D/dalvikvm( 909): (0) am.jar
D/dalvikvm( 909): threadid=1: interp stack at 0x41b99000
E/dalvikvm( 909): ERROR: must specify non-'.' bootclasspath
D/dalvikvm( 909): VM shutting down
D/dalvikvm( 909): 0 compilations using 0 + 0 bytes
D/dalvikvm( 909): Compiler arena uses 0 blocks (8100 bytes each)
D/dalvikvm( 909): Compiler work queue length is 0/0
D/dalvikvm( 909): VM cleaning up
W/dalvikvm( 909): CreateJavaVM failed: dvmClassStartup failed
E/AndroidRuntime( 909): JNI_CreateJavaVM failed
I/IspDrv ( 909): {IspDrv} [~IspDrvImp]
I/Netd ( 913): Netd 1.0 starting
[Miscellaneous Android Development] RickyGoldsmith:
Okay!!! Here likes the problem...

on early_property:ro.build.type=user
write /proc/bootprof "INIT: user build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/mediatek-op.jar:/system/framework/CustomProperties.jar

on early_property:ro.build.type=eng
write /proc/bootprof "INIT: eng build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/mediatek-op.jar:/system/framework/CustomProperties.jar:/system/framework/emma.jar

Does anyone know how init.rc is generated? It is not persistent across reboots. So there must be a template somewhere, from which it generates it.
[Miscellaneous Android Development] RickyGoldsmith:
MIUIv5 Android v 4.2.1

Very crude. But this gives hope that we'll see a 4.2 soon. I was too lazy to do cosmetic changes (device name etc) at this stage. Don't get fooled by the device name.

All thanks to the ROM maintainer.
[Miscellaneous Android Development] stas2z:
Hi, im the dev of rom and wish u luck in this difficult business :)

Feel free to ask me if you have any questions
[Miscellaneous Android Development] RickyGoldsmith:
[MENTION=5335657]stas2z[/MENTION] Your heap growth defaults seem to aggressive. I think these could lead to adverse effectsl.

dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
[Miscellaneous Android Development] stas2z:
it's a default settings for most mt6589 roms
[Miscellaneous Android Development] RickyGoldsmith:
[MENTION=5335657]stas2z[/MENTION] Right now, 2 major components are completely dead for me. The WIFI and the Bluetooth. My initial attempts at fixing it have failed. Before I dive in deep, wanted to check with you if you have done anything special in particular ???

Also, the newest patch 3.9.27, causes a System UI crash. The crash is persistent. Did you encounter this problem?
[Miscellaneous Android Development] stas2z:
Nothing special.

Nope, it works perfect on proper device.
[Miscellaneous Android Development] vizhigal:
"Right now, 2 major components are completely dead for me. The WIFI and the Bluetooth"

I do have faced this when porting D1 to 4.2.1 Jiyau G4 lewa.

The reason is JB4.2.1 rom uses wlanloader from system/bin which is not in 4.1.2 . D1 -4.1.2 wlan is by insmode.

1. when changing the romdisk of D1 boot.img with 4.2.1 romdisk , make the below changes in 4.2.1 romdisk.

2. Files need to be modified = init.project.rc , meta_init.project.rc , factory_init.rc

First modification ;

a. In init.project.rc , chnage # insmod /system/lib/modules/wlan.ko to insmod /system/lib/modules/wlan.ko

b..In meta_init.project.rc , factory_init.rc keep #insmod /system/lib/modules/wlan.ko as it is.

Second modiication ;

a.search and Delete the below lines from all the three init.project.rc , meta_init.project.rc , factory_init.rc documents.

service wlanLoader /system/bin/wlan_loader

user root

group root

class main

oneshot

Now you can change the 4.1.2 boot.img with 4.2.1 modified romdisc.

With this wifi and bluetooth should work.

Use powergrep to search the logcat errors in the libraries.

You can also use arm-eabi-readelf & arm-eabi-ld to find out the compatibility of D1 .so with the port rom libraries.

1.Use ubuntu linux environment , search and copy all the .so files ( almost 400 ) of the port rom in to a folder. Ex ;portlib.

2.Create a folder in ubuntu Ex; java , copy the arm-eabi-readelf & arm-eabi-ld and the portlib

3.Cd the terminal to java .

4.If you want to check hwcomposer.mt6589.so of D1 with 4.2.1 library ,

5 use this command ./arm-eabi-ld hwcomposer.mt6589.so -rpath portlib

6.You will get hwcomposer.mt6589.so: undefined reference to `DpBlitStream::setDstBuffer(void*, unsigned int, int)'

7.If you search the D1 libraries for DpBlitStream::setDstBuffer with powergrep . you will see it is from libdpframework.so .

8.Now if you change the port libdpframework.so with that of D1 and again if you check ,

9.You will not get the warnings..

10.For arm-eabi-readelf command is ./ arm-eabi-readelf -d hwcomposer.mt6589.so or you can choose --help..

11.Attached as tools.
[Miscellaneous Android Development] RickyGoldsmith:
Thanks. That is a lot of stuff. Let me try it tonight. I did fiddle with the initrd for 4.1 vs 4.2, also was able to make the 4.2 initrd work, but wasn't aware that 4.2's wlan activation was completely different. I'll let you know how it goes.

I just analyzed my initrd image and I'm pretty close to what you've stated. I'd just not deactivated the wlanLoader service. Need to boot and test now.
[Miscellaneous Android Development] RickyGoldsmith:
[MENTION=3082969]vizhigal[/MENTION]

Unfortunately, that didn't help. I still get the same error I got during my investigation...
[Miscellaneous Android Development] RickyGoldsmith:
[MENTION=3082969]vizhigal[/MENTION] And the error is:

E/FWKEXT ( 445): Enter GetCurrentOP
E/Hald ( 128): Set "/dev/wmtWifi" [1] failed
E/WifiStateMachine( 445): Failed to load driver!
E/WifiStateMachine( 445): DriverFailedState
E/FWKEXT ( 445): Enter GetCurrentOP
E/FWKEXT ( 445): Enter GetCurrentOP
E/Hald ( 128): Set "/dev/wmtWifi" [1] failed
E/WifiStateMachine( 445): Failed to load driver!
E/FWKEXT ( 445): Enter GetCurrentOP
E/WifiStateMachine( 445): DriverFailedState
E/WifiService( 445): Invoking mWifiStateMachine.setWifiEnabled
E/FWKEXT ( 445): Enter GetCurrentOP
E/Hald ( 128): Set "/dev/wmtWifi" [1] failed
E/WifiStateMachine( 445): Failed to load driver!
E/WifiStateMachine( 445): DriverFailedState
E/FWKEXT ( 445): Enter GetCurrentOP
E/ATCIJ ( 1381): Couldn't find 'atci-serv-fw' socket after 16 times, continuing to retry silently
E/FWKEXT ( 445): Enter GetCurrentOP
E/Hald ( 128): Set "/dev/wmtWifi" [1] failed
E/WifiStateMachine( 445): Failed to load driver!
E/WifiStateMachine( 445): DriverFailedState
E/FWKEXT ( 445): Enter GetCurrentOP
[Miscellaneous Android Development] RickyGoldsmith:
This is the other thing that I see in the dmesg. I looked around, but I have no clue about that errcode.

<6>[ 253.954524] 0)[120:6620_launcher]socket_close[32244]
<3>[ 253.954612] 0)[120:6620_launcher][WMT-DEV][W]WMT_unlocked_ioctl:unknown cmd (-2147180522)
<6>[ 253.954657] 0)[120:6620_launcher]socket_create[32246]:fd=4
<6>[ 253.954774] 0)[1:init]socket_accept[32247]:fd=8
<6>[ 253.954800] 0)[1:init]init: PropSet[persist.mtk.wcn.combo.chipid:0xffffffff] Start
<5>[ 253.954831] 0)[1:init]init: Sync Persist[persist.mtk.wcn.combo.chipid:0xffffffff] Start
<5>[ 253.977482] 0)[1:init]init: Sync Persist[persist.mtk.wcn.combo.chipid:0xffffffff] Done
<6>[ 253.977522] 0)[1:init]socket_close[32247]
<6>[ 253.977560] 0)[120:6620_launcher]socket_close[32246]
<3>[ 253.977653] 0)[120:6620_launcher][WMT-DEV][W]WMT_unlocked_ioctl:unknown cmd (-2147180522)
<6>[ 253.977701] 0)[120:6620_launcher]socket_create[32248]:fd=4
<6>[ 253.977825] 0)[1:init]socket_accept[32249]:fd=8
<6>[ 253.977851] 0)[1:init]init: PropSet[persist.mtk.wcn.combo.chipid:0xffffffff] Start
<5>[ 253.977883] 0)[1:init]init: Sync Persist[persist.mtk.wcn.combo.chipid:0xffffffff] Start
<7>[ 253.991502] 0)[589:sh][589:sh] fork [2309:sh]
<5>[ 253.995534] 0)[1:init]init: Sync Persist[persist.mtk.wcn.combo.chipid:0xffffffff] Done
<6>[ 253.995588] 0)[1:init]socket_close[32249]
<6>[ 253.995637] 0)[120:6620_launcher]socket_close[32248]
<3>[ 253.995740] 0)[120:6620_launcher][WMT-DEV][W]WMT_unlocked_ioctl:unknown cmd (-2147180522)
<6>[ 253.995794] 0)[120:6620_launcher]socket_create[32250]:fd=4
<6>[ 253.995940] 0)[1:init]socket_accept[32251]:fd=8
<6>[ 253.995970] 0)[1:init]init: PropSet[persist.mtk.wcn.combo.chipid:0xffffffff] Start
<5>[ 253.996003] 0)[1:init]init: Sync Persist[persist.mtk.wcn.combo.chipid:0xffffffff] Start
<7>[ 253.996711] 0)[2309:dmesg][exec] /system/bin/dmesg(3)
[Miscellaneous Android Development] RickyGoldsmith:
Infact, for me, the wlan0 interface was never detected. I wonder why, because the device interface would have very less to do with being detected by the system services (in this case, wlanLoader):

130|root@android:/ # netcfg
ccmni2 DOWN 0.0.0.0/0 0x00000080 46:86:96:dd:1c:a0
ccmni1 DOWN 0.0.0.0/0 0x00000080 aa:bc:63:eb:69:e3
ccmni0 DOWN 0.0.0.0/0 0x00000080 c6:11:65:9d:94:d3
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
ifb1 DOWN 0.0.0.0/0 0x00000082 12:ef:6e:e5:8c:5d
ifb0 DOWN 0.0.0.0/0 0x00000082 32:67:58:ce:90:b3
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
tunl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
[Miscellaneous Android Development] RickyGoldsmith:
[MENTION=3082969]vizhigal[/MENTION]

Can you share your 4.2 based boot.img, that works/boots on the Dream D1 (with wifi/bt) ? I'd like to see if that can help.
[Miscellaneous Android Development] RickyGoldsmith:
and the current failing boot arg for the kernel is:

root@android:/ # cat /proc/cmdline
console=ttyMT3,921600n1 vmalloc=506M slub_max_order=0 lcm=1-gn_smd_s6e8aa fps=5803 pl_t=3535 lk_t=1219 printk.disable_uart=1 boot_reason=4 �