yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] KazuDante:
here is the link : http://www.wikogeek.com/index.php?telephone=U+FEEL+LITE

the defconfig of the kernel that i ported that booted the r1 is the p4601_defconfig, you will see that it also has one for a 64bit kernel as well .

toolchain( 5.3 ) used : https://bitbucket.org/UBERTC/arm-eabi-5.3/get/df7b85146c62.zip

here is the outline used to build it :

#!/bin/bash

export ARCH=arm

SRCROOT=$HOME/kernel-3.18

export PATH=$HOME/arm-5.3/bin:$PATH

DRVS=$SRCROOT/drivers

MISCMTK=$DRVS/misc/mediatek

export CPATH=$MISCMTK/base/power/mt6735/:$MISCMTK/btcvsd/:$MISCMTK/cmdq/v2/mt6735/:$MISCMTK/ext_disp/mt6735/:$MISCMTK/fingerprint/gfx1xm/:$MISCMTK/gpio/mt6735/:$MISCMTK/i2c/mt6735/:$MISCMTK/m4u/mt6735/mt6753/:$MISCMTK/power/mt6735/:$MISCMTK/uart/mt6735/:$MISCMTK/video/mt6735/dispsys:$MISCMTK/video/mt6735/videox/:$DRVS/mmc/host/mediatek/mt6735/:$DRVS/pinctrl/mediatek/:$DRVS/spi/mediatek/mt6735/:$DRVS/watchdog/mediatek/wdt/mt6735/

mkdir -p tools/tools

mkdir -p out

make O=out TARGET_ARCH=arm p6601_defconfig

make O=out TARGET_ARCH=arm
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I built the kernel works just fine, SIM card no problem.

But like all builds screen doesn't rotate.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Can you send me the one you built?

---------- Post added at 06:06 PM ---------- Previous post was at 06:05 PM ----------

Idk y mine does not work regarding the sim cards

---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------

So......are we going to take a crack at the 64bit version? Because i think this source is good for our device and you built and seen it work correctly as well
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Perhaps you built from wrong source, I used the source that's for America, not European, I need 850 not 900.

I built kernel from UFeel_OpenSource.zip

Here are the specs.

UMTS for me must be 850, and they are see specs below.

http://www.devicespecifications.com/en/model/a58e3a7a
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Wait what? So your source is american? Mine only shows europe.

---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------

Can you link me to the american kernel source of the wiko u feel lite
[BLU R1 HD Guides, News, & Discussion] vampirefo:
U Feel is correct

U feel Lite is European
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Oh ok....but does the u feel kernel source has p4601_defconfig in arch/arm64/config directory?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Yes only difference is radio frequency.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Could that be fixed ? Or is it hard-coded in someway?

---------- Post added at 06:43 PM ---------- Previous post was at 06:42 PM ----------

So really this is a very very possible 64bit for R1.

---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------

Also i tought the p4601 had a different lcm and imgsensor then the 32bit variant....my download i slow so i couldnt show you....but compare the x64 vs the 32, some drivers have changed

---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------

Unless its in the one i have wich is not american version
[BLU R1 HD Guides, News, & Discussion] vampirefo:
A 64bit kernel, might be possible but our software is 32bit.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
We have many 64bit softwares to port, we are missing a x64kernel and a x64 twrp
[BLU R1 HD Guides, News, & Discussion] vampirefo:
And you have a 32bit bootloader, first step is to see if the bootloader will allow a 64bit kernel boot.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
But a 64bit (from a computer technician's view is backward compatible with x32 , its only when the kernel is x32 that x64 userland/binaries wont work.

---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------

Wow totally forgot about the bootloader.....danm

---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------

I think there was a device that i ported that they included the source codes for its preloader and bootloader, and the device was a mt6735....wow i need to find it again that might be need later of if we find out that the bootloader wont load x64 kernel
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I will look into building a 64bit twrp, if that boots then the bootloader allows 64bit kernels, if not then nothing can be done.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Here are the first differences i look for , in this case the lcm drivers are different on the arm64 p4601 compared to the p6601

Also the touchscreen drivers are different p4601 uses a gt1151 while p6601 uses a gt615 firmware.
[BLU R1 HD Guides, News, & Discussion] moriel5:
The Doogee X5 Pro has the same chipset, and it has a 3rd party x64 bootloader (built by SnowCat4PDA).

The stock is also x32.

It also has 3rd party AOSP 6.0 and 7.0 ROM (also by SnowCat4PDA).

The 6.0 AOSP is available in both x32 and x64, the 7.0 is not yet available in x64, but it will be.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
X5 pro is def a mt6735 but to a mt6735m , can you link us to that 3rd party bootloader?
[BLU R1 HD Guides, News, & Discussion] moriel5:
Better that I link you to SnowCat4PDA's GitHub page:

https://github.com/SnowCat6
[BLU R1 HD Guides, News, & Discussion] KazuDante:
[MENTION=2472806]vampirefo[/MENTION] what errors are you facing when compiling the x64 of the p4601_defconfig?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
It won't build, this is 32bit source.

The 32bit p4601 will compile, 64bit won't.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
The weird thing is the for the kernel source of wiko u feel lite it did build the Image.dtb and not an zImage.dtb....so the other source has both x32 and x64 then.

---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------

But that would leave us with the sim frequencies problem
[BLU R1 HD Guides, News, & Discussion] vampirefo:
See if you can build it, might be my toolchain then.

make[3]: *** No rule to make target 'include/config/hz.h', needed by 'kernel/time/hz.bc'. Stop.
../scripts/Makefile.build:402: recipe for target 'kernel/time' failed
make[2]: *** [kernel/time] Error 2
/home/vampirefo/Downloads/kk/p6601/Makefile:938: recipe for target 'kernel' failed
make[1]: *** [kernel] Error 2
[BLU R1 HD Guides, News, & Discussion] KazuDante:
What toolchain are you using? 4.9?

Here is where i get the tool chain that i use....when i compile for x32 i use 5.2 armeabi and for x64 i use either a 4.9 or 5.3 but nothing higher then 5.2 for x32 and 5.3 for x64

https://bitbucket.org/UBERTC/

---------- Post added at 08:58 PM ---------- Previous post was at 08:39 PM ----------

@vampirefo also got a confirmation from a good friend of mine that works on kernels (used to) and he confirmed that bootloaders are not related to ether 32bit or 64bit....so we should be good in that department and not worry about the bootloader
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Did you compile the 64bit kernel?
[BLU R1 HD Guides, News, & Discussion] KazuDante:
On the wiko u feel lite kernel source it compiled , i havent fixed it on the wiko u feel source , stops at builtin.o but failed error about some missing brakets

---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------

I will give it a go again tomorow on the lite source instead since it was the lite's kernel i initially ported , for now getting it to boot x64 is #1 and i guess we coukd figure out the frequencies for the sims later on
[BLU R1 HD Guides, News, & Discussion] KazuDante:
[MENTION=2472806]vampirefo[/MENTION] mine would compile but since we have to change the lcm drivers to be the same as ours , when its building the kernel thats when i get theses errors of undefined reference to "Disptepin_Enable....if i can get pass that it would compile with the correct lcm driver

---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------

[/COLOR [MENTION=2472806]vampirefo[/MENTION] And its just when it was prettymuch done with it

And thats on the wiko u feel kernel source not the lite kernel source(EU) so both can compile it , we just have a few quirks to fix up sadly but its our best shot tho.
[BLU R1 HD Guides, News, & Discussion] onlykhaz:
Wow, it's been a while... I've read the las 3 pages and I'm very happy with all the hard work and the things you guyz have accomplish, specially [MENTION=2472806]vampirefo[/MENTION] (you little hard head) xD it good you stay true in what you believe, and now [MENTION=6928202]KazuDante[/MENTION] has been all over the place with let's hope some great news soon :D.

Either way I just wanted to say thanks (y)
[BLU R1 HD Guides, News, & Discussion] KazuDante:
[MENTION=2472806]vampirefo[/MENTION] We need to talk in private , this is very important.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Found a kernel source that the Lonovo device was also on 3.18.19 , but has patches that started from 3.18.19 up to 3.19.X kernel.....and since mt6735 and mt6753 are the same , wondered if those patches could be applied as well.

https://github.com/jsharma44/android_kernel_lenovo_A7010a48
[BLU R1 HD Guides, News, & Discussion] KazuDante:
BLU is removing files from the kernel source!!!!......i just downloaded another copy from there ftp server , wiped my hole laptop to install a clean new Mac OS , then setup my vm linux and now im getting errors during compiling , flash_info missing , clkbuf missing....wtf BLU!!

---------- Post added at 06:57 PM ---------- Previous post was at 06:56 PM ----------

@vampirefo please link me to a working repo plz.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Use the one on my github
[BLU R1 HD Guides, News, & Discussion] KazuDante:
can u send me the link plz? i was attempting to compile under gcc6 since ive seen that it could be done....so far 5.3 is the max (that without modding the compiler files in /include/linux

Edit: Found it
[BLU R1 HD Guides, News, & Discussion] vampirefo:
https://github.com/vampirefo/android_kernel_mediatek_mt6735
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Those patches are available online. They are generic linux kernel latches.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Should we fire up the phone call arsenal once more? Or did Vamp's stuff fix it?
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Yea [MENTION=2472806]vampirefo[/MENTION] github is complete , i can compile the kernel , have to start over tho but where's the fun in it if its easy.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I have compiled several builds of cm14, haven't gotten anywhere yet.

Another build is compiling now, hopefully it boots.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Did you try using the boot image from the cm14 port to see if it boots?
[BLU R1 HD Guides, News, & Discussion] xWolf13:
He's trying to build from source. It would be easier to fix things with a compiled from source boot image rather than reusing a boot image from a dirty port
[BLU R1 HD Guides, News, & Discussion] KazuDante:
It was to determine if the boot.img is the problem or the rom , sort of process of elimination.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
No isn't boot.img, it's below files.

libc.so

libart.so

libandroid_runtime.so

pid: 946, tid: 946, name: main >>> zygote <<<
01-01 21:33:49.656 989 989 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-01 21:33:49.663 989 989 F DEBUG : Abort message: 'art/runtime/jni_internal.cc:492] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:467: Unable to construct file descriptor table.'
01-01 21:33:49.663 989 989 F DEBUG : r0 00000000 r1 000003b2 r2 00000006 r3 00000008
01-01 21:33:49.663 989 989 F DEBUG : r4 b6f1458c r5 00000006 r6 b6f14534 r7 0000010c
01-01 21:33:49.663 989 989 F DEBUG : r8 b42a3230 r9 000001d3 sl 0000000a fp b4285400
01-01 21:33:49.663 989 989 F DEBUG : ip 00000000 sp bed51fe0 lr b5dbcca7 pc b5dbf504 cpsr 200f0010
01-01 21:33:49.677 989 989 F DEBUG :
01-01 21:33:49.677 989 989 F DEBUG : backtrace:
01-01 21:33:49.677 989 989 F DEBUG : #00 pc 0004a504 /system/lib/libc.so (tgkill+12)
01-01 21:33:49.677 989 989 F DEBUG : #01 pc 00047ca3 /system/lib/libc.so (pthread_kill+34)
01-01 21:33:49.677 989 989 F DEBUG : #02 pc 0001d585 /system/lib/libc.so (raise+10)
01-01 21:33:49.677 989 989 F DEBUG : #03 pc 000190d1 /system/lib/libc.so (__libc_android_abort+34)
01-01 21:33:49.677 989 989 F DEBUG : #04 pc 00017138 /system/lib/libc.so (abort+4)
01-01 21:33:49.677 989 989 F DEBUG : #05 pc 0031a5f1 /system/lib/libart.so (_ZN3art7Runtime5AbortEPKc+328)
01-01 21:33:49.677 989 989 F DEBUG : #06 pc 000b5205 /system/lib/libart.so (_ZN3art10LogMessageD2Ev+1132)
01-01 21:33:49.677 989 989 F DEBUG : #07 pc 00262ecb /system/lib/libart.so (_ZN3art3JNI10FatalErrorEP7_JNIEnvPKc+94)
01-01 21:33:49.677 989 989 F DEBUG : #08 pc 000c7c71 /system/lib/libandroid_runtime.so
01-01 21:33:49.677 989 989 F DEBUG : #09 pc 000c813f /system/lib/libandroid_runtime.so
01-01 21:33:49.678 989 989 F DEBUG : #10 pc 000c88ef /system/lib/libandroid_runtime.so
01-01 21:33:49.678 989 989 F DEBUG : #11 pc 7525995f /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x27dd000)
01-01 21:33:49.894 280 280 I ServiceManager: service 'media.radio' died
01-01 21:33:49.894 280 280 I ServiceManager: service 'media.sound_trigger_hw' died
01-01 21:33:49.894 280 280 I ServiceManager: service 'media.audio_flinger' died
01-01 21:33:49.894 280 280 I ServiceManager: service 'media.audio_policy' died
01-01 21:33:49.896 280 280 I ServiceManager: service 'media.player' died
01-01 21:33:49.896 280 280 I ServiceManager: service 'media.resource_manager' died

Swapping them out will already built cm14, allows mine to boot, need to figure out why my build doesn't correctly compile them.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Thats weird indeed , i will look into changes that were made on those specific files
[BLU R1 HD Guides, News, & Discussion] vampirefo:
My R1HD device tree is up for those that want to try and build CM14.

https://github.com/vampirefo/android_device_blu_p6601
[BLU R1 HD Guides, News, & Discussion] KazuDante:
when you swapped the 3 files thats giving the issue did you get a chance to see what works correctly and what does'nt?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Same as your port, I guess, I have cm14 running via dual boot, as I need my phone for work.

I just boot into cm14 as I need to, then I can boot into regular android as needed.

Phone on charge now, will test tomorrow, quick test everything seems to work but camera.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
in the boot.img , in init.mt6735.rc did you change the default selected lib from camera.mt6737m.so to camera.mt6735.so ?.....libshim.so(or something like that) is used to workaround the camera issues regarding not finding symbols referred by another .so file.

---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------

but i have seen a github device tree soure that was using a camera wrapper method , ill post it when i find it again....that might also give us a clue.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I made no changes to boot.img, as I simply wanted it to boot, I change boardconfig to repack boot.img for R1HD.

My vendors blobs are from R1HD (V17), will look at boot.img tomorrow, would be nice if it's just ramdisk.

Edit

Just the libandroid_runtime.so file needs to be added, I change all three, then after I get it booted, worked with it and found the runtime file is bad for some reason.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
From my understanding each version of android has a different runtime so using a 6.0 on a 7.0 or 5 wont work.....unless we had the patch to apply to ours to bring it up to 7.1.....also regarding the ramdisk in posts that ive read when i was porting alot of people were saying that the way 7 reads and bring up the partions is different now , but if you made it boot on stock boot thays even better
[BLU R1 HD Guides, News, & Discussion] vampirefo:
After translating DeckerSu ReadMe he doesn't have camera working either.

So must need some kind of patch.

I am going to download Lineage OS and see if it compiles with my current device tree as CM is gone.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Lineage OS is the same as CM14, same problems exist no camera, have to swap out runtime file to be able to boot.

My tree builds both CM14 and Lineage OS, so that is a plus.

Need to find out why runtime file doesn't build correctly, and try and find camera patch.

Sent from my LineageOS R1HD by tapatalk
[BLU R1 HD Guides, News, & Discussion] KazuDante:
could you post or send me the link of the bootable lineageos?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I haven't uploaded, not much different than CM14, different bootscreen, just the word android.

In about it list Lineage OS instead of CM.

Sent from my LineageOS R1HD by tapatalk
[BLU R1 HD Guides, News, & Discussion] KazuDante:
oh ok. then when you can , link me to either one of your compiled builds since its.....or do you have a hangouts,telegram account......heres my email : xxnightterror89xx@gmail.com : you can email me the required info privately .
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Not a problem, I will upload it today, if you are wanting to swap files use V17, as my ROMs use V17 files, not 7.4.2 not sure it matters, but you never know.

Sent from my LineageOS R1HD by tapatalk
[BLU R1 HD Guides, News, & Discussion] KazuDante:
one a side note , when i was attempting to fix the camera in the port i do remember seing something in the log about the ID of the camera , https://github.com/CyanogenMod/android_device_oneplus_bacon/blob/cm-14.1/camera/CameraWrapper.cpp

sadly its not for mtk , ima still look around for that mtk one i saw somewhere.

Added: https://github.com/olegsvs/android_...ce7513033cbb01dafcf3faa5020326/libmtk_symbols

Another : http://4pda.ru/forum/index.php?showtopic=715583&st=5420#entry56174802 (use Google Chrome Browser on pc to translate)

He also made a refrence to this site , again regarding the LD_Preloader : https://rafalcieslak.wordpress.com/...eat-inject-features-and-investigate-programs/

3 : http://4pda.ru/forum/index.php?showtopic=715583&st=5380#entry56156046 (again use Chrome for translating)

---------- Post added at 10:48 AM ---------- Previous post was at 10:16 AM ----------

Okay , thanks in advance.
[BLU R1 HD Guides, News, & Discussion] onlykhaz:
Happy new year! Kinda of.... here are my news... my phone got stolen cause criminality in venezuela is off the roof I manage to take a sreenshot of the lastknow location, but authorities are useless, they will not enter that zone cause is dangerous.

http://imgur.com/TEcL7QH

of course the sim was thrown away so there is nothing else I can do, I think I can manage to find another R1 but for now I'm on a dummy phone [Alcatel Ot-305A].

I've read a little of what I can understand and It seems that you guys built an upgrade for de R1. If you let me suggest, don't fix camera for now, In priorities, for me its like 5.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Rom is uploaded.

https://xdaforums.com/r1-hd/development/lineage-os-r1hd-t3530751
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Downloading and will try some swapping to see , since the libs are actually for our device.
[BLU R1 HD Guides, News, & Discussion] theclaws:
How do i compile this? And, most importantly, after compiling, what do i have to do to run the OS on my phone?
[BLU R1 HD Guides, News, & Discussion] Androidx86Fan:
Well thats very disappointing. Who would use a 32 bit ARM cpu on Marshmallow stock?
[BLU R1 HD Guides, News, & Discussion] Androidx86Fan:
how u dew dat!?!?!?!
[BLU R1 HD Guides, News, & Discussion] zombie_ryushu:
Is anyone here still working on driver level issues for the R1 HD with Android Nougat?
[BLU R1 HD Guides, News, & Discussion] David Márquez:
hi, is there anything possible with the camera drivers on Linageos 14.1? justt wondering if the development for this device is not dead yet
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I think this is pretty much dead at this point
[BLU R1 HD Guides, News, & Discussion] jrk190:
Nice to see you on another corner of the forums again. Really grateful for all of your MTK work.
[BLU R1 HD Guides, News, & Discussion] PowSniffer0110:
Damn.... Honestly I thought this phone was gonna BLOW UP when it released.... Doesn't look like it AT ALL. I thought devs and common users alike would be buying this phone out of stock. Here's to wishful thinking and hoping we get some GREAT support! And this thing blows up!
[BLU R1 HD Guides, News, & Discussion] KazuDante:
is there any chance for this phone to be able to run custom roms like CM13,Zephyr-OS ect? i dont mean as of right now but after some kernel tweakings are made.
[BLU R1 HD Guides, News, & Discussion] lolwatpear:
Be prepared for disappointment then. I don't know where devs have went for non-nexus devices, even when the devices in question cost a measly $60 and it's bootloader has been unlocked shortly after launch. These aren't the good gs3 or HTC one m7 days.
[BLU R1 HD Guides, News, & Discussion] Fullmetal99012:
I am interested in doing development for this device. I purchased one, I just don't have a dev environment set up yet.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Please if you can make it work so that other roms can be ported over to it like cm13(cm13.1/cm14) and other cm/caf/aosp/xosp/dui ect roms can bring new life into this phone.
[BLU R1 HD Guides, News, & Discussion] Windslash31:
"real" devs that compile a rom from source tend to prefer snapdragon chips more than mtk. cause mtk is RARELY released a source code for their phones (even if they released it, its a partial/not complete source) whereas phone with snapdragon chip tend to have the source release/use another phone with the same chipset that have the source released, which make things easier.

if what youre looking for in a phone is custom roms, devs and custom kernels. you shouldnt go with mtk phones
[BLU R1 HD Guides, News, & Discussion] kal250:
UPDATE -- Well scratch that, the scatter block locations are different, plus this has extra partitions, its a EU phone, its also a Tinno phone, the SoC is the same but im assuming its not going to be as simple as I thought, back to research lol

So I'm researching mt6735 phones and come across the Wiko U Feel lite, its almost identical to the R1 HD, the Wiko has a fingerprint sensor, it has an update to M 6.0.1 at the following http://world.wikomobile.com/sav-1154-5542-frequently-asked-questions-u-feel-lite, im wondering how easy it would be to port this over to the R1, thus giving us 6.0.1 fixes?? It has a Windows installer similiar to HTCs RUU package updaters. I wonder if we could pull their package and port it with android kitchen(or whatever the MTK equivalent)... I'm new at this so I'm probably getting more excited than realistically possible :p
[BLU R1 HD Guides, News, & Discussion] jrk190:
Nougat got pushed to AOSP. I'd absolutely love to see it on this phone if we ever get binaries sorted out and all.
[BLU R1 HD Guides, News, & Discussion] kal250:
Considering the price point and maturity of the newer SoCs, Mediatek is going to be popping up in more phones.... And as far as a "real" developer, that has to be the lamest comment I have ever heard. A dev is a dev, sure each has their own skillset level, but trying to imply that anyone who chooses to work on a product you consider inferior, is not a "real" developer is an unfair assumption. Granted we may not attract devs who are accustomed to working with a particular brand, but all it takes is one device to peak some interest. Mediatek has been abit friendlier as of late in releasing source to their OEMs. Who knows maybe things will take off, maybe not. But a "real" developer is anyone who puts forth time and effort into a project. Just my 2 cents
[BLU R1 HD Guides, News, & Discussion] PowSniffer0110:
Heck yea! You're right and I was going to say the same thing!