Blu R1 HD is ready for the devs!

[jasonmerc]

band 12 is already released tho.

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

You need to enable it in engineering mode every time the phone starts though. Its not automatically enabled on boot.

 

[KazuDante]

Yea thats the stupid part...wich is one reason i wanted to know if its possible to unveil more bands since Blu wont.

Sent from my R1 HD using Tapatalk

---------- Post added at 04:42 PM ---------- Previous post was at 04:14 PM ----------

Android 7.0 would def be a nice addition to this phone.[emoji12]

Sent from my R1 HD using Tapatalk

 

[jasonmerc]

Yea thats the stupid part...wich is one reason i wanted to know if its possible to unveil more bands since Blu wont.

Sent from my R1 HD using Tapatalk

---------- Post added at 04:42 PM ---------- Previous post was at 04:14 PM ----------


Android 7.0 would def be a nice addition to this phone.[emoji12]

Once this device tree is done, I can't imagine cm14 being too far off

 

[KazuDante]

I found an article on cross-porting , i used to port rom on mt6572 so i will try to cross port the one from the j3 that someone already got it to boot. Dont know how that will work out since it was back in 2013 i ported roms

Sent from my R1 HD using Tapatalk

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

Would a 4.8 linaro work when compiling the kernel?

Sent from my R1 HD using Tapatalk

 

[vampirefo]

I found an article on cross-porting , i used to port rom on mt6572 so i will try to cross port the one from the j3 that someone already got it to boot. Dont know how that will work out since it was back in 2013 i ported roms

Sent from my R1 HD using Tapatalk

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

Would a 4.8 linaro work when compiling the kernel?

Sent from my R1 HD using Tapatalk

Most likely the linaro tool chain would work.

I can't think of any reason to use it, unless that's the only tool chain you have.


Sent from my R1 HD using Tapatalk

 

[KazuDante]

It was the first i downloaded when i was setting up my vm for taking a crack at building the kernel

Sent from my R1 HD using Tapatalk

 

[superdragonpt]

one last question....is this soc able to OC/UC and OV/UV?

No OC ( cpufreq is locked on board) unlocking those via sw does nothing, just placebo

UV, ye, you need to find the register, but on this SoCs ate rather unstable


Any new kernel source released by BLU?
(Sorry I didn't had time to read previous post, too busy )

Cheers

 

[superdragonpt]

(...)

the CPU does support 64 bit architecture. Looks like, if we can get an arm64 kernel to cross compile, we could build out 64 bit AOSP source against that. Technically 64 bit is totally possible on this device. as for now, I'm more concerned about successfully compiling the kernel itself though.
Once I do that, my first goal is to bake in double tap to wake.

??
Will never work .

If the ROM is 32bit, it'll only run @32

Nothing you can do on kernel

32, 64 bit ROM sources differ a lot just so you know.

I'm amazed (?) Why did the phone came with 32bit only?

The SoC yes does support 64bit, the only possible reason is a limitations. Is one(or more) of the hardware .

But still

Cheers

Edit; About bands, those are locked via modem MOLY. You can't unlock more than the ones already available via mediatek engineer menu
( *#*#3646633#*#*) .
If it lacks any band, then its due to licensing , and/or platform not support .

You may yes have the case that some bands are supported , but just not enabled.

 

[KazuDante]

??
Will never work .

If the ROM is 32bit, it'll only run @32

Nothing you can do on kernel

32, 64 bit ROM sources differ a lot just so you know.

I'm amazed (?) Why did the phone came with 32bit only?

The SoC yes does support 64bit, the only possible reason is a limitations. Is one(or more) of the hardware .

But still

Cheers

Edit; About bands, those are locked via modem MOLY. You can't unlock more than the ones already available via mediatek engineer menu
( *#*#3646633#*#*) .
If it lacks any band, then its due to licensing , and/or platform not support .

You may yes have the case that some bands are supported , but just not enabled.

But will modifying the modem moly file(s) possibly enveil more bands , since the 4g ones that are enabled dont work for me ?
by all mean its most likely illegal but can it be done?

 

[superdragonpt]

But will modifying the modem moly file(s) possibly enveil more bands , since the 4g ones that are enabled dont work for me ?
by all mean its most likely illegal but can it be done?

You can't modify modem ..

Even if you had modem source, device needs to be compatible, and may also need some changes.

cheers

 

[N00b-un-2]

But will modifying the modem moly file(s) possibly enveil more bands , since the 4g ones that are enabled dont work for me ?
by all mean its most likely illegal but can it be done?

superdragonpt is correct. without source code for the modem you can't modify it. and yes, depending on which bands you are trying to enable you are either in breach of A) Licensing (each band is licensed on a per chip basis much in the same way particular features of the ARM instruction set are licensed to different ARM CPUs)
B) federal law -- the FCC regulates which bands of radio communication can be used in which jurisdictions (outside the US other regulatory agencies handle this). EG; Wifi. There are more wifi channels and bands in existence than are in use in the US. The use of bands not authorized for use in a given jurisdiction could interfere with other types of radio transmissions. The obvious case that comes to mind is aircraft communication. if your laptop is broadcasting noise in a frequency used by aircraft and you cause a plane to crash, you are at fault. Hence why it's illegal.

---------- Post added at 08:53 PM ---------- Previous post was at 08:49 PM ----------

Most likely the linaro tool chain would work.

I can't think of any reason to use it, unless that's the only tool chain you have.


Sent from my R1 HD using Tapatalk

not sure why you would. You can just grab the prebuilts from the AOSP github, or the official NDK.

 

[vampirefo]

But will modifying the modem moly file(s) possibly enveil more bands , since the 4g ones that are enabled dont work for me ?
by all mean its most likely illegal but can it be done?

I already said you can't modified bands, what bands BLU allows is it period.

Only BLU can modify bands.

Sent from my R1 HD using Tapatalk

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

superdragonpt is correct. without source code for the modem you can't modify it. and yes, depending on which bands you are trying to enable you are either in breach of A) Licensing (each band is licensed on a per chip basis much in the same way particular features of the ARM instruction set are licensed to different ARM CPUs)
B) federal law -- the FCC regulates which bands of radio communication can be used in which jurisdictions (outside the US other regulatory agencies handle this). EG; Wifi. There are more wifi channels and bands in existence than are in use in the US. The use of bands not authorized for use in a given jurisdiction could interfere with other types of radio transmissions. The obvious case that comes to mind is aircraft communication. if your laptop is broadcasting noise in a frequency used by aircraft and you cause a plane to crash, you are at fault. Hence why it's illegal.

---------- Post added at 08:53 PM ---------- Previous post was at 08:49 PM ----------



not sure why you would. You can just grab the prebuilts from the AOSP github, or the official NDK.

Correct, but he wants to use linaor tool chain for one reason or other.

There used to be hype about this tool chain a few years ago, but it was mainly just false hope.
Sent from my R1 HD using Tapatalk

 

[bullet25]

Just in case any Dev who knows what they are doing is watching this thread. This is my current error in my attempt to build.

make: * No rule to make target '/home/bob/workspace/CM13/out/target/product/p6601/obj/STATIC_LIBRARIES/libminui_intermediates/libminui.a', needed by '/home/bob/workspace/CM13/out/target/product/p6601/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd'. Stop.

 

[vampirefo]

Just in case any Dev who knows what they are doing is watching this thread. This is my current error in my attempt to build.

make: * No rule to make target '/home/bob/workspace/CM13/out/target/product/p6601/obj/STATIC_LIBRARIES/libminui_intermediates/libminui.a', needed by '/home/bob/workspace/CM13/out/target/product/p6601/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd'. Stop.

You most likely could get answers from here
http://forum.xda-developers.com/showthread.php?t=2274332

They probably need to see your device tree, before they can help you, the key to compiling anything is a complete tree, I compiled cm12.1 for my blu energy x plus phone, took a while to get the tree correctly, and cm12.1 source had to be patched several times.

https://plus.google.com/101944948426591597599/posts/ZSCcTy2Us9t



so no doubt cm13 and cm14, must be patched before you can build it for your device.
my guess the vendor blobs for this phone will be close to 300, almost that many buliding cm12.1 for my older phone.

 

[vampirefo]

I have made a stock rom flashable via twrp, have adb remount working.

So now need to compile a twrp recovery.

Sent from my R1 HD using Tapatalk

 

[KazuDante]

I have made a stock rom flashable via twrp, have adb remount working.

So now need to compile a twrp recovery.

Sent from my R1 HD using Tapatalk

Did you upload the twrp flashable stock rom?

Sent from my R1 HD using Tapatalk

 

[vampirefo]

Did you upload the twrp flashable stock rom?

Sent from my R1 HD using Tapatalk

No when I do, I will make it's own thread.

0cee0d831502a2a867f036d951c3c78c /home/vampirefo/Desktop/R1HD/stock_rom/stock_rom_R1HD_6.5.zip

I have downloaded @ColtonDRG normal-stock-oob which is V12 non prime version, I checked the permissions on the system to see if 6.5 and V12 used different permission they use the same.
So a V12 rom can be made from my exact stock_rom_R1HD_6.5.zip, I may or may not provide a non prime version, even if I don't all a user has to do it open my stock_rom_R1HD_6.5.zip replace system and boot.img with non prime zip and flash.

There are two twrp recoveries one I just made and one made by @lopestom I had to get the rom compliant with both recoveries, @lopestom was the first recovery available for R1HD and allows backing up and restoring of many partitions, I am going to use his recovery.fstab, but remove the partitions backup and restore I don't use.

both recoveries at one time or other would throw an error

ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed

I have now fixed that so neither recovery error, any other recovery that might show up, that person will have to fix his own, for now two recoveries can flash my rom, the one I made and @lopestom I will release rom after more testing.

 

[KazuDante]

Awsome.....ive seen some cm13 related git , is it being worked on since the kernel can be compiled now?

Sent from my R1 HD using Tapatalk

 

[vampirefo]

Awsome.....ive seen some cm13 related git , is it being worked on since the kernel can be compiled now?

Sent from my R1 HD using Tapatalk

There are several people working on cm13 right now, I will build my own device tree soon for compiling roms, right now my device tree correctly builds and packs twrp.

I am not sure how far the people compiling cm13 for R1HD are, I have other goals and projects first, Honestly I am not a big fan of CM, I have compiled cm12.1 for my older phone, mainly cause people wanted it, but I don't continue to update it and so forth far to much time and work for a rom I don't even use.

I wont use cm13 on this phone either, the rom that's on it is great, nothing that cm13 would improve, cm13 would just be another rom I won't use.

 

[KazuDante]

There are several people working on cm13 right now, I will build my own device tree soon for compiling roms, right now my device tree correctly builds and packs twrp.

I am not sure how far the people compiling cm13 for R1HD are, I have other goals and projects first, Honestly I am not a big fan of CM, I have compiled cm12.1 for my older phone, mainly cause people wanted it, but I don't continue to update it and so forth far to much time and work for a rom I don't even use.

I wont use cm13 on this phone either, the rom that's on it is great, nothing that cm13 would improve, cm13 would just be another rom I won't use.

So would it be safe to guess that Android Nougat (stock) would be a possible project for the R1 HD , since Blu wont do it? also is there a huge difference between the MT6753 and our 6735.