Blu R1 HD is ready for the devs!

[jrk190]

YUP

They lefted out a couple of important things

EDIT:
can someone give the the .prop build fingerprint?
need to check something

i wonder if i can order this one to Europe...

-The M.A.D. team

Nice to see you on another corner of the forums again. Really grateful for all of your MTK work.

 

[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!

 

[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.

 

[lolwatpear]

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!

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.

 

[Fullmetal99012]

I am interested in doing development for this device. I purchased one, I just don't have a dev environment set up yet.

 

[KazuDante]

I am interested in doing development for this device. I purchased one, I just don't have a dev environment set up yet.

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.

 

[Windslash31]

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!

"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

 

[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

 

[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.

 

[kal250]

"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

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

 

[PowSniffer0110]

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

Heck yea! You're right and I was going to say the same thing!

 

[Fullmetal99012]

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.

It would be nice to bring a plethora of options to this device, however I feel like getting CM running would be a good start. maybe CM/AOSP.

Hopefully I'll get some free time in between work to look at setting up the device tree/getting the kernel to compile.

 

[N00b-un-2]

Just wanted to say... I just bought the $49.99 version of this phone specifically to try and port TWRP and AOSP to it. should be arriving tomorrow. I'm downloading the source code and will set up an android build VM tonight.

In case anyone is wondering, I do have a bit of experience porting recoveries and ROMs to devices and am looking forward to developing for this device.

 

[onlykhaz]

Just wanted to say... I just bought the $49.99 version of this phone specifically to try and port TWRP and AOSP to it. should be arriving tomorrow. I'm downloading the source code and will set up an android build VM tonight.

In case anyone is wondering, I do have a bit of experience porting recoveries and ROMs to devices and am looking forward to developing for this device.

I'm very happy we got a new dev here :good:
Dude why don't you put another 10$ for the 2gb ram version if you can return it for the other one it would be better for all of us and for you.

 

[Oscar_david]

I'm very happy we got a new dev here :good:
Dude why don't you put another 10$ for the 2gb ram version if you can return it for the other one it would be better for all of us and for you.

I have the same question, especially because most of us have the $60 version, and of course I wonder whether ROM development would be different for each version.

 

[_AI_]

Just wanted to say... I just bought the $49.99 version of this phone specifically to try and port TWRP and AOSP to it. should be arriving tomorrow. I'm downloading the source code and will set up an android build VM tonight.

In case anyone is wondering, I do have a bit of experience porting recoveries and ROMs to devices and am looking forward to developing for this device.

You are an amazing human being. We thank you, our children thank you and Android thanks YOU :good::good::good::good:

 

[Fullmetal99012]

Just got my Dev laptop working again. Just need to download Linux and set up a development VM.

 

[N00b-un-2]

To address everyone -- no, there doesn't seem to really be any difference between the the 8GB and 16GB variants. Aside from RAM and storage, the two are otherwise identical. I spent last night unlocking the bootloader, flashing TWRP (I was totally prepared to start working on porting, but someone saved me the trouble), rooting and removing all of the Amazon nonsense.

It took HOURS to pull down the AOSP source because Nougat source code was just released and everyone has been just hammering the google servers. That being said, I have my dev box built and my environment is in place. I'm looking at the Mediatek source code right now and trying to figure out where everything goes and what everything is called. I'm hoping to be able to successfully compile the kernel source in the next week or so.

please be patient with me. bear in mind that a kernel that compiles is not necessarily one that boots. And it certainly doesn't mean Im going to have a working port of CM13 (or 14) any time soon. Also, I have a real job outside of android dev work and thats what pays the bills.

Are there any other devs working on this right now? Has anyone else figured out if mediatek does anything non-standard with their toolchain?

 

[AtomicFizzle]

I'm not really a developer, but I like messing with stuff. Got it to compile I think!

unzip -o ../Downloads/kernel-source.zip 
gedit kernel-3.18/drivers/mmc/core/mmc.c
	took out @xuchunsheng code blocks
mkdir tools/tools

export PATH=/home/adam/android-ndk-r12b/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin:$PATH&&export CROSS_COMPILE=arm-linux-androideabi-&&export ARCH=arm

drvs=~/build/kernel-3.18/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/

make p6601_defconfig
make -j4 zImage

CPATH thing seems a little weird, but I guess it gets through those troublesome includes. Maybe there's something supposed to be in the build.ini that they didn't give us.

  OBJCOPY arch/arm/boot/Image
  Kernel: arch/arm/boot/Image is ready
  LDS     arch/arm/boot/compressed/vmlinux.lds
  AS      arch/arm/boot/compressed/head.o
  GZIP    arch/arm/boot/compressed/piggy.gzip
  CC      arch/arm/boot/compressed/misc.o
  CC      arch/arm/boot/compressed/decompress.o
  CC      arch/arm/boot/compressed/string.o
  SHIPPED arch/arm/boot/compressed/hyp-stub.S
  SHIPPED arch/arm/boot/compressed/lib1funcs.S
  SHIPPED arch/arm/boot/compressed/ashldi3.S
  SHIPPED arch/arm/boot/compressed/bswapsdi2.S
  AS      arch/arm/boot/compressed/hyp-stub.o
  AS      arch/arm/boot/compressed/lib1funcs.o
  AS      arch/arm/boot/compressed/ashldi3.o
  AS      arch/arm/boot/compressed/bswapsdi2.o
  AS      arch/arm/boot/compressed/piggy.gzip.o
  LD      arch/arm/boot/compressed/vmlinux
  OBJCOPY arch/arm/boot/zImage
  Kernel: arch/arm/boot/zImage is ready

 

[Nonta72]

I got a question, Are the ROMs in all versions (OEM and Amazon) actually 32-bit or 64-bit ?

Thanks!