Porting CM10 to N7105 variants.

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
I would like this to be a joint developer effort for porting CM10 and AOSP Roms to the LTE versions of the Note 2. I have a device tree right now intended for the T-Mobile variant on github: https://github.com/SirWellington/android_device_samsung_t0lt3tmo
It is a fork of the n7100 device tree. There are a couple of things that need to be get a working build.

I am currently having issues compiling. There may be some binaries that I'm missing in properietary-files.sh
Anyone willing to help?
 

garyd9

Inactive Recognized Developer
Sep 13, 2006
2,644
2,730
0
50
Pittsburgh, PA
I don't have my build machine available right now, but perhaps if you post what kind of build errors (or more details on the issues) you are getting, some of us can give suggestions.

take care
Gary
 

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
Well I got past the build issues I was having. I had to fork the SMDK4412-common tree and make some changes.
It does some filtering on device models (naturally). I basically had to add the t0ltetmo as an approved device.

I am still having build issues elsewhere now:

firmware/SlimISP_ZK.bin.gen.S:5: Error: file not found: firmware/SlimISP_ZK.bin

It really shouldn't be looking for that file since it isn't a proprietary one.
 

Attachments

Last edited:
  • Like
Reactions: [email protected]

garyd9

Inactive Recognized Developer
Sep 13, 2006
2,644
2,730
0
50
Pittsburgh, PA
  • Like
Reactions: ac16313

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
A few of us have been trying to get this up and running. I still ccan't figure out why the build is looking for the binary when I removed it from the proprietary files list. I'd be willing to push and pull repos as necessary.

Sent from my SGH-T889 using xda app-developers app
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,095
25,085
0
Owego, NY
A few of us have been trying to get this up and running. I still ccan't figure out why the build is looking for the binary when I removed it from the proprietary files list. I'd be willing to push and pull repos as necessary.

Sent from my SGH-T889 using xda app-developers app
Try grepping through the -common device and vendor trees, along with (just to be sure) the smdk4412 kernel tree to see what is trying to pull in that file.
 

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
Try grepping through the -common device and vendor trees, along with (just to be sure) the smdk4412 kernel tree to see what is trying to pull in that file.
Just run through grep -R "<search string>" .

That way you can check every file in your source tree for a specific string. Hopefully you'll be able to track this one down mate! :)
 

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
You guys are correct. I wish we could grep through github sometimes.

Anyway it turns out that the binary is referenced in the Kernel's firmware/Makefile. When I get home I'll do a diff of that one and the stock Samsung one. Correct me if I'm wrong but the N7105 variants do not carry this binary do they?

Sent from my SGH-T889 using xda app-developers app
 

cmenard

Retired Recognized Developer
Dec 31, 2010
475
1,221
0
Atlanta
You guys are correct. I wish we could grep through github sometimes.

Anyway it turns out that the binary is referenced in the Kernel's firmware/Makefile. When I get home I'll do a diff of that one and the stock Samsung one. Correct me if I'm wrong but the N7105 variants do not carry this binary do they?

Sent from my SGH-T889 using xda app-developers app
Where did you fork the kernel from? You can use the smdk4412 kernel on nebkat's github or grab it from my github. I think that will help with a bunch of your problems.
 
  • Like
Reactions: DarthPiggie

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
Where did you fork the kernel from? You can use the smdk4412 kernel on nebkat's github or grab it from my github. I think that will help with a bunch of your problems.
I forked it from TeamHacksung. I'll take a look at yours. Did you fork it from anywhere?

Sent from my SGH-T889 using xda app-developers app
 

cmenard

Retired Recognized Developer
Dec 31, 2010
475
1,221
0
Atlanta
The problem I'm running into is RIL related I believe. I can watch the logs and the modem fires up and goes through all it's processes like it should, even does a transmit and recieve... However it's not being recognized within the OS.
 

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
This has to do with the kernel configuration when you build it. I'm going to upload my defconfig and you can give it a try. I modified the one from the stock samsung kernel config.

Sent from my SGH-T889 using xda app-developers app
 
  • Like
Reactions: twolfekc

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
Cmenard have you made any progress? I mamaged to get a successfuo build using your kernel. Thanks for that.

What do you think about pulling the .rc scripts from the stock phone and using those untouched?

Sent from my SGH-T889 using xda app-developers app
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,095
25,085
0
Owego, NY
I forked it from TeamHacksung. I'll take a look at yours. Did you fork it from anywhere?

Sent from my SGH-T889 using xda app-developers app
Anything on teamhacksung github related to 4412 devices is old. I know there were some kernel patches related to some sort of firmware stuff...

Teamhacksung github is only used for early bringups/bleeding edge work on large repositories. Once a bringup is complete, repos get forked over to the main CM repos.

Anything related to 4412 devices currently (Nov 30, 2012) is in CM's main repos (other than of course themuppets for prop blobs) and managed via gerrit.

Edit: General rule, if a device is receiving nightlies, and you're looking anywhere other than CM's github repo and TheMuppets for props, you're looking in the wrong place.

SOMETIMES when bringing up a new Android version, things get forked to THS then merged back, such as with 4.1 (due to us doing a lot of repo reorganization and such), but all 4.2 work is currently in gerrit. (And, right now, it's a total ****ing mess...)

Seems like the big difference for LTE devices in the kernel is replacement of CONFIG_SEC_MODEM with CONFIG_QC_MODEM and some related items. (I've seen 3-4 different defconfig variants with different stuff turned on/off...)

the RIL blobs will of course be different

The RIL Java interface in frameworks/base might be different.
 
Last edited:

cmenard

Retired Recognized Developer
Dec 31, 2010
475
1,221
0
Atlanta
Cmenard have you made any progress? I mamaged to get a successfuo build using your kernel. Thanks for that.

What do you think about pulling the .rc scripts from the stock phone and using those untouched?

Sent from my SGH-T889 using xda app-developers app
Havent had a chance to mess with again. Just make sure you change gps, add all the mdm stuff, tombstones mount, and all the binaries are in bin and called in the .rc. My modem is working just need to figure the ril out.
 
  • Like
Reactions: deeznutz1977

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
Anything on teamhacksung github related to 4412 devices is old. I know there were some kernel patches related to some sort of firmware stuff...

Teamhacksung github is only used for early bringups/bleeding edge work on large repositories. Once a bringup is complete, repos get forked over to the main CM repos.

Anything related to 4412 devices currently (Nov 30, 2012) is in CM's main repos (other than of course themuppets for prop blobs) and managed via gerrit.

Edit: General rule, if a device is receiving nightlies, and you're looking anywhere other than CM's github repo and TheMuppets for props, you're looking in the wrong place.

SOMETIMES when bringing up a new Android version, things get forked to THS then merged back, such as with 4.1 (due to us doing a lot of repo reorganization and such), but all 4.2 work is currently in gerrit. (And, right now, it's a total ****ing mess...)

Seems like the big difference for LTE devices in the kernel is replacement of CONFIG_SEC_MODEM with CONFIG_QC_MODEM and some related items. (I've seen 3-4 different defconfig variants with different stuff turned on/off...)

the RIL blobs will of course be different

The RIL Java interface in frameworks/base might be different.
I did a diff on all the kernel configs and you're definitely right about that. I think one of the main things is figuring out the proper partitions for things.

Sent from my SGH-T889 using xda app-developers app
 

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
Flashing is still blowing up my IMEI amd signal. I feel that I may need to update my device tree to use the one you suggested (not just the kernel). I'll try that tomorrow thougj. It's so hard to dev on your daily phone though, ugh. Wish I had it as an aside.

Sent from my SGH-T889 using xda app-developers app
 
  • Like
Reactions: darkierawr

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
Was there any updates on this? I did manage to get as far as getting the latest n7100 nightlies running on the N7105 and ported over the libs and binaries from TW ROM for rild, etc. I also had a tweaked kernel imilka kindly built for the QC radio. Unfortunately I was just getting:

Diag_LSM_Init: Failed to open handle to diag driver, error = 2

Would be interested to hear what is happening for you guys with your real build instead of my 'hacky' attempt at a modified n7100 build. :)
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone