[DEV] T710 CyanogenMod 12.1 Development thread

Edgrr000 · Dec 8, 2015 at 6:39 AM

Edgrr000 said:
Thanks! It's a big learning curve for me this is the first time i try to build a rom, but Google does a pretty good job at answering most of my questions.
i'll keep a close eye at your progress.

cheers

ok so i started from scratch building from the TeamEos tree. I set up all the files and parameters accordingly, and i followed the cyanogenmod wiki quite successfully up until i try to build a recovery image, or as a matter of fact whenever i try to build anything. It gives me an error in the cm.mk file; "PRODUCT_NAME must be defined.. stop." i tired changing that value to various different names and formats but i just can't figure it out. I'm sure it's something simple and the answer can be found here http://elinux.org/Android_Device but i have another problem, I'm running out of disk space haha!
I'll upload my sources to Github shortly

CTXz · Dec 8, 2015 at 7:00 AM

Edgrr000 said:
ok so i started from scratch building from the TeamEos tree. I set up all the files and parameters accordingly, and i followed the cyanogenmod wiki quite successfully up until i try to build a recovery image, or as a matter of fact whenever i try to build anything. It gives me an error in the cm.mk file; "PRODUCT_NAME must be defined.. stop." i tired changing that value to various different names and formats but i just can't figure it out. I'm sure it's something simple and the answer can be found here http://elinux.org/Android_Device but i have another problem, I'm running out of disk space haha!
I'll upload my sources to Github shortly

You're not defining the PRODUCT_NAME variable in cm.mk.

It should look like this

Code:

 PRODUCT_NAME := cm_gts28wifi

Edgrr000 · Dec 8, 2015

This is what's in my cm.mk file

Code:

PRODUCT_NAME := cm_gts28lte
PRODUCT_DEVICE := gts28lte
PRODUCT_MANUFACTURER := samsung
PRODUCT_MODEL := SM-T715

PRODUCT_BRAND := samsung
TARGET_VENDOR := samsung
TARGET_VENDOR_PRODUCT_NAME := gts28lte
TARGET_VENDOR_DEVICE_NAME := SM-T715

and this is the error i'm getting

[email protected]:~$ make recoveryimage cm_gts28lte-eng
build/core/product_config.mk:243: *** device/samsung/gts28lte/cm.mk: PRODUCT_NAME must be defined.. Stop.

#### make failed to build some targets ####

CTXz · Dec 8, 2015 at 8:48 AM

Edgrr000 said:
This is what's in my cm.mk file

Code:

PRODUCT_NAME := cm_gts28lte PRODUCT_DEVICE := gts28lte PRODUCT_MANUFACTURER := samsung PRODUCT_MODEL := SM-T715 PRODUCT_BRAND := samsung TARGET_VENDOR := samsung TARGET_VENDOR_PRODUCT_NAME := gts28lte TARGET_VENDOR_DEVICE_NAME := SM-T715

and this is the error i'm getting

[email protected]:~$ make recoveryimage cm_gts28lte-eng
build/core/product_config.mk:243: *** device/samsung/gts28lte/cm.mk: PRODUCT_NAME must be defined.. Stop.

#### make failed to build some targets ####

Could you push your code?

Edgrr000 · Dec 8, 2015

CTXz said:
Could you push your code?

device

Kernel

Vendor

This is it from me for now. i'm going to wipe my virtualbox as it already took up all my my storage space. I'll continue when i get a bigger drive or a different computer. Maybe a fresh build environment will solve my problems

Cheers

CTXz · Dec 8, 2015 at 7:47 PM

Edgrr000 said:
device

Kernel

Vendor

This is it from me for now. i'm going to wipe my virtualbox as it already took up all my my storage space. I'll continue when i get a bigger drive or a different computer. Maybe a fresh build environment will solve my problems

Cheers

You're missing the android.mk. This results it starting at CM.mk which skipps a bunch of stuff. Check out the android.mk from my tree.

CTXz · Dec 10, 2015 at 8:49 PM

We're getting there guys! First Bootloop!

suzook · Dec 10, 2015 at 9:08 PM

CTXz said:
We're getting there guys! First Bootloop!

WOW!!! Keep at it!

bassie1988 · Dec 10, 2015 at 10:08 PM

Hell yeah! It seems like my T810 is going to be a lot more fun to play with..? keep up the awesome job guys!??

Verstuurd vanaf mijn SM-G925K met Tapatalk

CTXz · Dec 10, 2015 at 10:22 PM

bassie1988 said:
Hell yeah! It seems like my T810 is going to be a lot more fun to play with..? keep up the awesome job guys!??

Verstuurd vanaf mijn SM-G925K met Tapatalk

suzook said:
WOW!!! Keep at it!

Thanks guys. It seems to be boot looping because it tries to load the IR blaster HAL even though this device doesn't have one. I fixed this and i'm running a new build right now. Who knows if it will be our first boot. If there are allot of bugs I will make a buildbot and release nightlies until things seem to be stable. However I have a good feeling that CM will work quite well because after all, my sources are based on raymans sources for his note 4 rom/roms.

bassie1988 · Dec 10, 2015 at 10:24 PM

CTXz said:
Thanks guys. It seems to be boot looping because it tries to load the IR blaster HAL even though this device doesn't have one. I fixed this and i'm running a new build right now. Who knows if it will be our first boot. If there are allot of bugs I will make a buildbot and release nightlies until things seem to be stable. However I have a good feeling that CM will work quite well because after all, my sources are based on raymans sources for his note 4 rom/roms.

You just made my day.. Santa!? i'll be happy to be a tester!

Verstuurd vanaf mijn SM-G925K met Tapatalk

CTXz · Dec 10, 2015 at 10:27 PM

bassie1988 said:
You just made my day.. Santa!? i'll be happy to be a tester!

Verstuurd vanaf mijn SM-G925K met Tapatalk

Remember this build is for the t710 only. However I will probably need you when porting to the t810

thedanks · Jul 17, 2012 191 51 0

CTXz said:
Remember this build is for the t710 only. However I will probably need you when porting to the t810

In that case, I will be a happy tester!

suzook · Dec 11, 2015 at 3:17 AM

CTXz said:
Remember this build is for the t710 only. However I will probably need you when porting to the t810

I can test for 810 once you get the 710 booting.

kisypher · Dec 11, 2015 at 4:12 AM

In the OP it was stated that 12.1 was being worked on. It's this still the case or have you moved on to Marshmallow? Just curious.

Sent from my not-so-stock SM-T810

CTXz · Dec 11, 2015 at 5:24 AM

kisypher said:
In the OP it was stated that 12.1 was being worked on. It's this still the case or have you moved on to Marshmallow? Just curious.

Sent from my not-so-stock SM-T810

Hey, i'm still at cm 12.1 until I can get it boot and fairly stable. But no worry, i'll mlove to 13 too.

kisypher · Dec 11, 2015 at 5:26 AM

That's great! Appreciate you working on this. ?

Sent from my not-so-stock SM-T810

CTXz · Dec 11, 2015 at 7:01 AM

First CM 12.1 boot! Enjoy it guys!

https://youtu.be/Qtf46oKO8fE

What's not right/working

- Wifi
- Resolution
- Internal SD card mount
- Sound

I'll release the ROM soon!

workdowg · Dec 11, 2015 at 7:02 AM

@CTXz - Just to let you know when 810 testing comes I want in, this will be great with my future plans! One(maybe 2) quick questions... I'm looking to run Linux with Android in the chroot (see my thread) and need to know if the cwm-recovery has adb shell support? And do you by any chance know, at boot, what the kernel names the external sd card? is called something other than /dev/mmcblk1? Sorry for the little off topic.

From my LG-G4, Rooted running Stock 5.1

CTXz · Dec 11, 2015 at 7:08 AM

workdowg said:
@CTXz - Just to let you know when 810 testing comes I want in, this will be great with my future plans! One(maybe 2) quick questions... I'm looking to run Linux with Android in the chroot (see my thread) and need to know if the cwm-recovery has adb shell support? And do you by any chance know, at boot, what the kernel names the external sd card? is called something other than /dev/mmcblk1? Sorry for the little off topic.

From my LG-G4, Rooted running Stock 5.1

Hey, last time I build CM recovery I had no adb permission. However that was still on my old kernel. I will rebuild a cm recovery and tell you

[DEV] T710 CyanogenMod 12.1 Development thread

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Inactive Recognized Developer

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer