Porting CM10 to N7105 variants.

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
Yes I had that same message in logcat. We could be missing a proprietary binary.

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

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. :)
Have you included all of the files on the list in this thread?

http://forum.xda-developers.com/showthread.php?p=34750886

Haven't had chance to try it yet - will try it later on and report back if you haven't tested it by that point. :)
 

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
I need to double check but I definitely did. You should start trying to compile from source. Do you have any experience in that?

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

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
I need to double check but I definitely did. You should start trying to compile from source. Do you have any experience in that?

Sent from my SGH-T889 using xda app-developers app
I have experience in compiling linux distros from source - been an avid user of Gentoo Linux for years. Sadly I don't have any experience in compiling CM from source, not something I've worked with before. Hate to say it but I've been more of a 'consumer' than a contributor as far as code goes around Xda. Although I do donate money to worthwhile projects and this is most certainly a worthwhile project!

I'll look in to building CM from source for this device and let you know if I succeed with that. :) Hopefully if we worth together on this we can make some progress and get things moving! It's a shame really because the only part I've found which doesn't work properly is the radio - everything else seems fine. Although the UI did seem a little laggy with the hacked n7100 build but as I say, that's likely just because it's not a 'true' build.
 

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
My build was definitely smooth. I have some code on github which you can use. I'd be willing to show you how to build from source, assuming you are up to speed on Linux terminal commands.

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

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
My build was definitely smooth. I have some code on github which you can use. I'd be willing to show you how to build from source, assuming you are up to speed on Linux terminal commands.

Sent from my SGH-T889 using xda app-developers app
Sure, that sounds good! Would help me get up to speed quicker! I'm up-to-speed on both *nix and Git already so it shouldn't be too painful. :)
 

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
i don't know if my thread is linked here but i actually got CM10 ported to I317 (Note 2 for AT&T).

http://forum.xda-developers.com/showthread.php?t=2024495

the sources are in the 2nd post. You guys should only replace vendor/samsung/t0att binaries with stuff from the n7105 then "breakfast t0att & make -j8"
Oh my... this build actually worked on my N7105!

As in, it worked COMPLETELY unmodified. I have literally just flashed the unmodified ZIP provided in the previous post and HSDPA signal straight away. I'm not actually on an LTE network at the moment (too expensive in the UK right now!) but I would assume it likely works. The build does appear to reboot randomly so there are still issues but it *does* get a signal.
 

madmack

Senior Member
Dec 23, 2008
3,696
4,751
263
Boston, MA
Oh my... this build actually worked on my N7105!

As in, it worked COMPLETELY unmodified. I have literally just flashed the unmodified ZIP provided in the previous post and HSDPA signal straight away. I'm not actually on an LTE network at the moment (too expensive in the UK right now!) but I would assume it likely works. The build does appear to reboot randomly so there are still issues but it *does* get a signal.
yea, the rilds do work across the US and the EU variants but I had some glitches here and there with that rild socket so I do recommend you switch to your device's proprietary binaries because the slight differences do matter.

try to place a call. can you hear or be heard?
 

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
yea, the rilds do work across the US and the EU variants but I had some glitches here and there with that rild socket so I do recommend you switch to your device's proprietary binaries because the slight differences do matter.

try to place a call. can you hear or be heard?
I did try placing a call and unfortunately cannot hear nor be heard. The only two issues I'm seeing so far, however, are:

- Random rebooting (but the SD card reports as corrupt in CM until it's reformatted, seems to be a common issue with CM builds on this device so far.) I'm thinking that could be causing the reboot - will format the card and see if it behaves after that once I reboot it to recovery.

- When placing a call I cannot hear nor be heard sadly.
 

madmack

Senior Member
Dec 23, 2008
3,696
4,751
263
Boston, MA
I did try placing a call and unfortunately cannot hear nor be heard. The only two issues I'm seeing so far, however, are:

- Random rebooting (but the SD card reports as corrupt in CM until it's reformatted, seems to be a common issue with CM builds on this device so far.) I'm thinking that could be causing the reboot - will format the card and see if it behaves after that once I reboot it to recovery.

- When placing a call I cannot hear nor be heard sadly.
yea.. we don't share the rild files with N7100 and I'm afraid the audio issues will be a pain in the ass to fix. I'll ping imilka and see if he can offer any help at all.

the sdcard. it's not corrupt, it's probably formatted as exFAT which CM roms don't support. format it to fat32 and it'll work. If you have an adapter, plug it into your PC and you'll see your files so they're intact.
 

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
yea.. we don't share the rild files with N7100 and I'm afraid the audio issues will be a pain in the ass to fix. I'll ping imilka and see if he can offer any help at all.

the sdcard. it's not corrupt, it's probably formatted as exFAT which CM roms don't support. format it to fat32 and it'll work. If you have an adapter, plug it into your PC and you'll see your files so they're intact.
Yeah I know about the SD thing - seen it before. Thankfully I don't really store anything vital on the SD card so that's not a problem. Even with that removed, however, it's still rebooting frequently (every 4-5mins.) I will have to try merging the n7105 'rild' and associated libs over in to your build to see if that resolves the reboot issue.

The audio issue, however, is something I'm sure was fought when CM10 on the N7100 so I'm guessing it's possible that the N7100 fixes will also work for the N7105 but I realize despite the numbers associated with these devices - there are a fair few differences between them.
 

madmack

Senior Member
Dec 23, 2008
3,696
4,751
263
Boston, MA
Yeah I know about the SD thing - seen it before. Thankfully I don't really store anything vital on the SD card so that's not a problem. Even with that removed, however, it's still rebooting frequently (every 4-5mins.) I will have to try merging the n7105 'rild' and associated libs over in to your build to see if that resolves the reboot issue.

The audio issue, however, is something I'm sure was fought when CM10 on the N7100 so I'm guessing it's possible that the N7100 fixes will also work for the N7105 but I realize despite the numbers associated with these devices - there are a fair few differences between them.
I'm actually using the exact same N7100 files for audio.. I'm thinking our RILD files have different APIs so these audio files will have to be modified.

I contacted imilka. Let's see if he'll provide us with any help :)
 
  • Like
Reactions: mojorisin7178

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
I'm actually using the exact same N7100 files for audio.. I'm thinking our RILD files have different APIs so these audio files will have to be modified.

I contacted imilka. Let's see if he'll provide us with any help :)
Haven't added the N7105 rild binary yet, will let you know the results once I do. It's not really a fair test until I'm running on a N7105 intended rild. :)

---------- Post added at 07:58 PM ---------- Previous post was at 07:12 PM ----------

Ok, now added the rild binary as well as all of the /system/lib/*ril*.so files from an N7105 ROM and this appears (early yet) to resolve the reboot issue. The remaining issue is the audio issue which sadly this did not fix but I may be missing some times. Do you think it's worth copying all of the files from your forum post over here?

http://forum.xda-developers.com/showthread.php?p=34750886
 

madmack

Senior Member
Dec 23, 2008
3,696
4,751
263
Boston, MA
Haven't added the N7105 rild binary yet, will let you know the results once I do. It's not really a fair test until I'm running on a N7105 intended rild. :)

---------- Post added at 07:58 PM ---------- Previous post was at 07:12 PM ----------

Ok, now added the rild binary as well as all of the /system/lib/*ril*.so files from an N7105 ROM and this appears (early yet) to resolve the reboot issue. The remaining issue is the audio issue which sadly this did not fix but I may be missing some times. Do you think it's worth copying all of the files from your forum post over here?

http://forum.xda-developers.com/showthread.php?p=34750886
copy the files you see in here:
https://github.com/madmack/proprietary_vendor_samsung/tree/jellybean/t0att/proprietary

from the n7105.

but that wont' fix the audio. the audio issue is a deeper problem and might take a while to get resolved. i'm taking a break from that for now. might come back and have a look in a few days.
 

DarthPiggie

Senior Member
Jul 31, 2010
173
41
0
Foe the audio issues, strangely enough this was not a problem in some of my earlier builds. Right now I see in logcat : error to create audio stream or something like that. I'll take a look through the defconfig and also through the Board Vendor nakefiles to see what could be causing it.

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

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
Sounds great Darth!

It's strangely only when on a call that I experience that issue. I hear the standard DTMF dialing sounds perfectly so audio does work - it just doesn't work during a call (don't even get the ringing) sadly.

Will create an updated ZIP with all N7105 proprietary files to see if I can fix this constant reboot issue though - that's the most annoying bug at the moment! :)
 

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
Unfortunately no matter what I tried I wasn't able to get rid of the reboot issue - the device just seems to completely reboot every 5mins or so. I did replace all of the files in the ZIP with the N7105 files which were mentioned in the previous post but unfortunately this still didn't resolve the crash. I also found a file named libaudio-ril.so which the build above didn't have, added that but still no difference. When I fiddled with the build.prop (to replace it to the N7105 values for product, etc.) audio stopped working entirely.

Not really much progress sadly! :(

Edit: Ran out of time working on this last night but unfortunately I have still not made any progress. At this point the remaining issues are:

- Rebooting every 5mins (roughly)
- No audio on calls (TX nor RX)

I suspect both of these are radio related and that one will hopefully solve the other. This is, however, a slightly optimistic view and may not be the case. For now, however, I'd be happy if I could just get the reboot issue resolved. The audio issue I can work around by forwarding all calls to my work blackberry for now. What I can't live with is my phone rebooting every few minutes. I did notice, however, that the reboot only seems to occur where the radio is actually being used. If I simply connect it via WiFi it will sit there for an hour or so. As soon as it is forced to use mobile data that's when the reboots are more likely and placing a call almost always triggers this after a minute or two so it does appear to be modem/RILD related.
 
Last edited:

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
Quick update on this:

Still working on getting a valid build environment to build this ROM - once I get a successful ROM built, I will then work on patching the audio and hopefully that in turn *may* fix the reboot issue.

We'll see.

Edited: Rebuilding my dev environment based on the sources from http://forum.xda-developers.com/showthread.php?t=2024495 since this allows the radio to work properly. Then we just have audio and the reboot issue to fix. I say *just* but actually those two may require code to be written which would be a bit of a blocker but with the combination of time and money (my own) I'm sure I'll be able to get this working!

Edit 2: Completed my dev environment rebuild and built off a test image but unfortunately the kernel didn't boot properly. Will get back to this tonight and hopefully get a working build environment using the new sources (now completely modified for our N7105.) Once I get this working I'll post a working image in the dev section. It will very likely have broken in-call audio and a reboot issue, however, but let's get what we have working so far posted publicly and see if we can get some people interested in helping on this! :)

Edit 3: Right, my two objectives for tonight are get a working build and eat pizza! Added a potential fix to my build environment to get the first objective done and planning to order pizza while this is re-compiling. Will keep this post updated of any progress I make. I appreciate all the thanks I've been getting and hope I can deliver a semi-functional build tonight, then we can work out the remaining issues after that!

Edit 4: Had my pizza so I achieved one of my two tasks I guess! I'm taking a 20-30min break from this to tweak my VMWare Fusion config in the hopes of being able to build these faster (rebuilding my disk image as SCSI, assigning more cores and throwing 12GB of RAM at this so hopefully we'll get faster builds! I am working with a few devs from around the scene to get the various parts working and DarthPiggie has been kindly helping me with the dev environment issues so all being well we'll have a build tonight - though it will likely be published tomorrow now. :) As I said though, still has the audio and reboot bugs sadly. Those are next on my list to look at and are being looked at by other devs too.

Edit 5: Still unable to get this to build properly yet - facing a new error now, Christ this stuff is poorly documented CM - sort it out! >_>

Edit 6: Got a lot further this time, getting an adb connection to the kernel - looks like I'm missing a few binaries which I now have a fix for thanks to DarthPiggie so we're once again moving with this! Here's hoping I get a successfully booting build this time!

Edit 7: Looks like we may be making progress here - will update shortly depending on the results of the build I'm running now.
 
Last edited:

chrisaw

Senior Member
Jun 12, 2007
289
210
63
Edinburgh
Hi folks,

Two updates - firstly I did manage to get a working dev environment which I am now experimenting with but I have based my new environment on the following:

http://forum.xda-developers.com/showthread.php?t=2024495

For now, I will not be posting updates to this thread since I feel that the development news on this really belongs in madmack's thread since he is the one really doing all of the work here! :) Just FYI - you can actually use the madmack build on our N7105s. Your build.prop values will, obviously, switch from N7105 to the AT&T version but from what I can tell this is purely network branding and there does not appear to be any negative effects to running macmack's build on our N7105s - we can always revert back to TW at the drop of a hat.

Warning: I *highly* recommend making a backup of your EFS partition and uploading it to dropbox. The dropbox part is a little paranoid I admit but it will give you a great 'disaster recovery' method just in case and this is all experiemental stuff we're doing here, doubtful it will ever harm your efs partition but if it did and you don't have a backup then good luck explaining how it happened to Samsung.
 
Last edited:
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