Development Status / Support?

[vampirefo]

Is this something you want to elaborate on. I have a few success cases bringing this device back to life. It is only long shot.

Not really, phone apparently has been upgraded so preloader doesn't work. My guess phone was damaged during an upgrade.

Not a big deal, I have sent the seller an email waiting for his reply.

Update seller gave me a refund and told me to keep the phone.

Sent from my Life Max using Tapatalk

 

[vampirefo]

my noob may be showing on this statement, but here goes.

there are lib files inside the stock camera apk.

I am not for sure what you are trying to show me, a camera app is a camera app nothing more delete it install another camera app, and you will see camera works just fine.

You are rooted? Delete the camera app folder from system/app, go to playstore install any camera app you want reboot try new camera app it will work just fine.

I replaced stock camera and other apps as soon as I root a device most stock apps aren't very good.

Sent from my Life Max using Tapatalk

 

[mrmazak]

I am not for sure what you are trying to show me, a camera app is a camera app nothing more delete it install another camera app, and you will see camera works just fine.

You are rooted? Delete the camera app folder from system/app, go to playstore install any camera app you want reboot try new camera app it will work just fine.

I replaced stock camera and other apps as soon as I root a device most stock apps aren't very good.

Sent from my Life Max using Tapatalk

That is basically what I have done. Other camera app from playstore just works. and I removed the priv-app folder for camera, and new camera still works.
I was trying to get the same results of the op in the thread I linked to before, but I cannot. His result was after removing stock camera app (removed with titanium backup) now no camera app will work.
I made backup in titanium to see what was being removed.

there is one apk in the priv-app folder called "MyosCamera.apk" and in the back-up there are two apk's "camera2" and "camera3"
still dont know where these two apks really are stored and probably not important at all


The files I attached were un-packed from the stock camera apk, using 7zip.

 

[vampirefo]

That is basically what I have done. Other camera app from playstore just works. and I removed the priv-app folder for camera, and new camera still works.
I was trying to get the same results of the op in the thread I linked to before, but I cannot. His result was after removing stock camera app (removed with titanium backup) now no camera app will work.
I made backup in titanium to see what was being removed.

there is one apk in the priv-app folder called "MyosCamera.apk" and in the back-up there are two apk's "camera2" and "camera3"
still dont know where these two apks really are stored and probably not important at all


The files I attached were un-packed from the stock camera apk, using 7zip.

I don't think you can duplicate what happened to other user until he tells you everything.

He removed much more than he is telling, else you could duplicate his results by removing just the camera.

I knew that was false information I have at least 10 Androids, none not one of them uses stock camera app.


Just checked my wife's R1HD, it's not using stock camera either.
Sent from my Life_Max using Tapatalk

 

[linuxsociety]

Depending on how the ROM is built from source will impact how the .APK files are packaged and accessed. ON MOST ROMS /system/apps .apk files are simply apps, however at compile time depending on per device configurations .apk files can also be packaged as simply framework containers that are obviously ran as a UI app when tapping the .apk from a launcher, however unique system calls CAN depend on needing access to the framework / library contents within the .apk without actually loading the UI to the user. This isn't typical behavior for well put together roms from good OEMs, but lower budget devices sometimes implement methods that aren't standard as opposed to OEMs who have a much more professional development team.

Simplest true test to this would be to compile a 6.0.x AOSP rom with the same Vendor / Device Overlays used to build the 7.x and see if it duplicates the camera issue on 6.0. If not then the problem is a compatibility issue with the Vendor / Device used on AOSP >= 7.x due to a core change in framework.

 

[vampirefo]

Blu makes great ROMs, I have several blu devices and have built custom ROMs for all of them.

Blu for some reason or other decided to use Sony parts on R1HD, which prevents camera from working, one needs Sony source which isn't available.

Everyone that has built a custom ROM similar to R1HD using Sony parts has the same problem no camera.

However you can build android 6 ROM if you like, slimrom is great also, I built that ROM also for my Blu Life Max.

Which is very similar to R1HD minus the crappy Sony camera parts.

Actually if you build a ROM with working camera on this Sony camera you will be not only the first, but the only dev to do it none of the rest of us could do it.

I can of course ports ROMs between devices using Sony camera, as I already did with Zen, I gave up on compiling a ROM for R1HD as did other devs with similar devices.

I was going to see if the new libs allowed camera to work, I was going to port my Blu Life Max ROMs to R1HD provided the 8.3 libs allowed camera to work.

However the phone I bought was bad, I got a refund and get to keep the phone so no real loss there.

Look forward to seeing someone get farther than I could, if you can do it that puts hope back into other similar devices.

Good luck, I don't have this phone won't be ordering another one, my wife said she might just get another Blu phone, without Sony camera so I can make her a ROM on any other Blu device just not R1HD.

Sent from my LIFE X8 using Tapatalk

 

[yepi15]

I would like to contribute and recently there was a patch of May I do not know if it will do anything

 

[Hic_Svnt_Dracones]

Re: OP

I love my r1 hd, and was ecstatic when Lineage came out, but since the projects went discontinued I haven't found any updates. I can live without the camera, but still haven't gotten rotation to work, my hotspot does work though... Anyways, I was going to do a custom build of Resurrection Remix, but got too busy and switched to just a port, but got too busy to do that also. I would love to see a proper 7.1.1 custom build that can get lineage updates, well, would prefer RR.

If you want to work on it, I do have an unused 4gb/2 core/48gb SSD/1gb/s cloud server on Linode that I usually use just for LEMP stack builds and testing and I don't need it for a few weeks, if that will help with your computing resources. It's not the fastest machine, but it is available.

Im not sure on rules of contact info, but here is my mail, in case you want to reach me, 3rd party notifications don't reach my often: [email protected] the offer is open for anyone that wants to build a proper rom. I might have some other resources also, as I work in IT. Oh, how do you enable rotation? I know they disabled it while porting to lineage os, and didn't turn it back on, and the thread with the info got too long.

Also, I would, and sure others would also, be willing to make donations to have an always updated, latest version rom for the Blu R1 HD.


I

 

[jianC]

@Hic_Svnt_Dracones If the rom you are using has a custom kernel, you will need to set CONFIG_MTK_BMA222E_NEW=y in the kernel config in order for accelerometer/rotation to work.

For some reason, it is disabled by default in the kernel source BLU released.

 

[vampirefo]

@Hic_Svnt_Dracones If the rom you are using has a custom kernel, you will need to set CONFIG_MTK_BMA222E_NEW=y in the kernel config in order for accelerometer/rotation to work.

For some reason, it is disabled by default in the kernel source BLU released.

Yes, or he can use stock kernel, I prefer rotation disabled during testing, once ROM is ready for every day use I enable rotation.

Sent from my LIFE X8 using Tapatalk

 

[darkensx]

As far as wip development i have tried to build the stock kernel using the kernel source that's available but it seems to always fail to build. Also seem when trying to build it always wants to configure for x86_64 version shouldn't be asking for ARM configuration? It always States it can't find configuration for P6601 uh well yeah because it's ARM and it's dead set on building x86_64 :-\ I am on BBQLINUX I just want to build a Overclockable kernel with some better governor's then the stock ones

 

[jianC]

As far as wip development i have tried to build the stock kernel using the kernel source that's available but it seems to always fail to build. Also seem when trying to build it always wants to configure for x86_64 version shouldn't be asking for ARM configuration? It always States it can't find configuration for P6601 uh well yeah because it's ARM and it's dead set on building x86_64 :-\ I am on BBQLINUX I just want to build a Overclockable kernel with some better governor's then the stock ones

before compiling

$ export ARCH=arm

 

[darkensx]

before compiling

$ export ARCH=arm

I have been doing this :

 export ARCH=arm ARCH_MTK_PLATFORM=MT6735

Should it be? :

 export ARCH=arm
export ARCH_MTK_PLATFORM=MT6735

 

[jianC]

I have been doing this :

 export ARCH=arm ARCH_MTK_PLATFORM=MT6735

Should it be? :

 export ARCH=arm
export ARCH_MTK_PLATFORM=MT6735

Yes, but why not just try it out to see if it works or not? A lot can be learned through trial and error.

 

[darkensx]

Yes, but why not just try it out to see if it works or not? A lot can be learned through trial and error.

ok im getting errors in the ouput. (different then before):

[email protected]:~/kernel/kernel-3.18$ export ARCH=arm
[email protected]:~/kernel/kernel-3.18$ export ARCH_MTK_PLATFORM=MT6735
[email protected]:~/kernel/kernel-3.18$ export CROSS_COMPILE=/home/louis/kernel/tools/arm-eabi-4.8/bin/arm-eabi-
[email protected]:~/kernel/kernel-3.18$ export DEFCONFIG=/home/louis/kernel/kernel-3.18/arch/arm/configs/p6601_defconfig
[email protected]:~/kernel/kernel-3.18$ make -j4
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
  CALL    scripts/checksyscalls.sh
cat: /home/louis/kernel/kernel-3.18/../../../../../../build.ini: No such file or directory
cat: /home/louis/kernel/kernel-3.18/build.ini: No such file or directory
  CC      init/main.o
  CC      arch/arm/mm/dma-mapping.o
  CC      arch/arm/mm/extable.o
  CC      arch/arm/kernel/irq.o
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/interrupt.h:12,
                 from include/linux/kernel_stat.h:8,
                 from arch/arm/kernel/irq.c:24:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/kernel/irq.o' failed
make[1]: *** [arch/arm/kernel/irq.o] Error 1
Makefile:938: recipe for target 'arch/arm/kernel' failed
make: *** [arch/arm/kernel] Error 2
make: *** Waiting for unfinished jobs....
  CC      arch/arm/mm/fault.o
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/ftrace_event.h:8,
                 from include/trace/syscall.h:6,
                 from include/linux/syscalls.h:81,
                 from init/main.c:18:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'init/main.o' failed
make[1]: *** [init/main.o] Error 1
Makefile:938: recipe for target 'init' failed
make: *** [init] Error 2
  CC      arch/arm/mm/init.o
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/highmem.h:9,
                 from arch/arm/mm/dma-mapping.c:23:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/mm/dma-mapping.o' failed
make[1]: *** [arch/arm/mm/dma-mapping.o] Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from arch/arm/mm/fault.c:14:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/mm/fault.o' failed
make[1]: *** [arch/arm/mm/fault.o] Error 1
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/memcontrol.h:24,
                 from include/linux/swap.h:8,
                 from arch/arm/mm/init.c:12:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/mm/init.o' failed
make[1]: *** [arch/arm/mm/init.o] Error 1
Makefile:938: recipe for target 'arch/arm/mm' failed
make: *** [arch/arm/mm] Error 2

not sure what to make of this..

 

[mrmazak]

ok im getting errors in the ouput. (different then before):

[email protected]:~/kernel/kernel-3.18$ export ARCH=arm
[email protected]:~/kernel/kernel-3.18$ export ARCH_MTK_PLATFORM=MT6735
[email protected]:~/kernel/kernel-3.18$ export CROSS_COMPILE=/home/louis/kernel/tools/arm-eabi-4.8/bin/arm-eabi-
[email protected]:~/kernel/kernel-3.18$ export DEFCONFIG=/home/louis/kernel/kernel-3.18/arch/arm/configs/p6601_defconfig
[email protected]:~/kernel/kernel-3.18$ make -j4
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
  CALL    scripts/checksyscalls.sh
cat: /home/louis/kernel/kernel-3.18/../../../../../../build.ini: No such file or directory
cat: /home/louis/kernel/kernel-3.18/build.ini: No such file or directory
  CC      init/main.o
  CC      arch/arm/mm/dma-mapping.o
  CC      arch/arm/mm/extable.o
  CC      arch/arm/kernel/irq.o
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/interrupt.h:12,
                 from include/linux/kernel_stat.h:8,
                 from arch/arm/kernel/irq.c:24:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/kernel/irq.o' failed
make[1]: *** [arch/arm/kernel/irq.o] Error 1
Makefile:938: recipe for target 'arch/arm/kernel' failed
make: *** [arch/arm/kernel] Error 2
make: *** Waiting for unfinished jobs....
  CC      arch/arm/mm/fault.o
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/ftrace_event.h:8,
                 from include/trace/syscall.h:6,
                 from include/linux/syscalls.h:81,
                 from init/main.c:18:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'init/main.o' failed
make[1]: *** [init/main.o] Error 1
Makefile:938: recipe for target 'init' failed
make: *** [init] Error 2
  CC      arch/arm/mm/init.o
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/highmem.h:9,
                 from arch/arm/mm/dma-mapping.c:23:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/mm/dma-mapping.o' failed
make[1]: *** [arch/arm/mm/dma-mapping.o] Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from arch/arm/mm/fault.c:14:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/mm/fault.o' failed
make[1]: *** [arch/arm/mm/fault.o] Error 1
In file included from ./arch/arm/include/asm/hardirq.h:6:0,
                 from include/linux/hardirq.h:8,
                 from include/linux/memcontrol.h:24,
                 from include/linux/swap.h:8,
                 from arch/arm/mm/init.c:12:
./arch/arm/include/asm/irq.h:7:23: fatal error: mach/irqs.h: No such file or directory
 #include <mach/irqs.h>
                       ^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'arch/arm/mm/init.o' failed
make[1]: *** [arch/arm/mm/init.o] Error 1
Makefile:938: recipe for target 'arch/arm/mm' failed
make: *** [arch/arm/mm] Error 2

not sure what to make of this..

I keep getting similar errors.
shows included file does not exist. but it really is in the same dir .

mine is at a different part than yours. I have used three different prebuilt toolchains, and in omni sourse. All ways same problem. I think source has dependecy on specific build setup.
But this is my first attemt at kernel build.

 

[mrmazak]

I keep getting similar errors.
shows included file does not exist. but it really is in the same dir .

mine is at a different part than yours. I have used three different prebuilt toolchains, and in omni sourse. All ways same problem. I think source has dependecy on specific build setup.
But this is my first attemt at kernel build.

I was able to get past my errors.

I had not read the "readme" from the source, that says after extracting the kernel source you must do "make mrproper"

When I did that I also got some errors saying certain files did not exist. This time is was true. The files were being called from a make file as "obj" but they we're not in the source. When commented out of the make file in question the make completed . Just read the output from :make mrproper" carefully , and find the make file the error is refering to. Open the file in gedit look for the lines calling the file that error says, and if there is not a device folder in the parent location, put a "#" in front of that line and run "make mrproper" again, see if it goes further this time. I nedded to go through it 15 times to get all the lines commented out, now it built and boots.


In my case (building for different device than you) I had multiple calls for touchscreen drivers and one call for a fingerprint print driver, all of which are hardware my device does not have.

Once those errors cleared and make mrproper finished, so did the kernel make finish.



This guide was helpful. In the proper steps to build, but fixing the error took some figuring out.

just note that the link for toolchain goes to v 4.7, And for me it did not built with it.

I just changed the link to 4.8 ,so toolchain was compatible with source and build completed just fine.

https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057