Database Info

[DEV-ROM] HTC Evo Full AOSP rom Android 2.2.1|FRG83

I'm posting a developmental rom for the purpose of anyone and everyone that want's to cook an AOSP rom but is having troubles or doesn't want to go through the hassle of compiling from source. This Rom is completely compiled from AOSP source with the help of the CM team for the HTC Device tree and kernel.
There are many non-working item's. For anyone that uses this rom and tries to fix the issues, if you could please post on this forum for everyone else to do the fixes that would be awesome. I've included the link to the Rom and a link to the Google Apps flashable zip from CM's Wiki.
Click to expand...
Click to collapse
Once again this rom is a Dev-Rom and is completely compiled from AOSP source, this has no sense at all and will never have sense. I will not be maintaining the rom per se, I will however be helping with some of the fixes.
Evo Android 2.2.1 AOSP ROM
Google Apps
Thanks to: Bcnice20, l33tlinuxh4x0r, tjohnsonjr & the CM team.

These are insturctions for making a clean AOSP Rom. There will be issues with the Rom once you finish. These instructions are for Linux(I used Ubuntu). You will have to have adb installed already. Your computer has to be 64bit or you not be able to compile the source.
Please Note. 4G and HDMI will not work. This is not a stripped down Sense Rom. There is no SENSE AT ALL!!! The Camera will work but not the Camcorder. Fixes will come but we are hoping to get contributions from other devs to help build up the AOSP support for the EVO. As great as CM6 is, we need choices. Now let the fun begin!!!
Open the Terminal:
The following needs to be ran as Root
Code:
cd /usr/bin/
curl http://android.git.kernel.org/repo > repo
chmod a+x /usr/bin/repo
Exit root and return back to your home folder. This will create a generic build. This is going to take a couple of hours depending on your internet connection
Code:
mkdir ~/android
cd ~/andoid
repo init -u git://android.git.kernel.org/platform/manifest.git
repo sync
This will download the EVO specific files:
Code:
cd ~/android/device/htc
git clone http://github.com/CyanogenMod/android_device_htc_supersonic.git supersonic
Now the BoardConfig.mk needs to edited
Go to /android/device/htc/supersonic/BoardConfig.mk
Locate
Code:
TARGET_RECOVERY_UI_LIB := librecovery_ui_supersonic librecovery_ui_htc
TARGET_RECOVERY_UPDATER_LIBS += librecovery_updater_htc
Now add a “#” in front of each line
Code:
#TARGET_RECOVERY_UI_LIB := librecovery_ui_supersonic librecovery_ui_htc
#TARGET_RECOVERY_UPDATER_LIBS += librecovery_updater_htc
Save and exit. Then in the terminal type
Code:
cd ~/android
cp ~/android/device/htc/supersonic/supersonic.mk ./buildspec.mk
Now Go to /android/frameworks/base/core/res/res/values and locate the Config.xml file. Open with the text editor and look for this line
Code:
<string name="default_wallpaper_component">@null</string>
Right below this line add. Reference this website to use as an example as to what its supposed to look like http://pastebin.com/mpmpEaKq
Code:
<!-- Handle notifications differently if device only uses an amber/green
LED. This also needs a liblights module that enables them accordingly. -->
<bool name="config_amber_green_light">true</bool>
Save and exit
Now load Cyanogenmod6 onto your phone. Once its loaded, connect your phone to the computer and in the terminal type
Code:
cd /device/htc/supersonic
chmod a+x extract-files.sh
./extract-files.sh
This will download files from the phone. You will get errors at the end. Get a stock Sense Rom and locate the files that came up in error and Copy the files into /android/vendor/htc/supersonic/propietary folder
Now in the Terminal
Code:
cd ~/android
. build/envsetup
lunch
Select option for the supersonic(6th or 7th)
Now type(This will take awile depending on the speed of your computer)
Code:
make
Once it finishes, type
Code:
make otapackage
Lastly, to get the phone to boot, get the libmedia.so file from CM6 and place it in your /system/lib folder before flashing.
This will create your ROM is a zip file. DO NOT FLASH THIS TO YOUR PHONE. IT IS NOT ROOTED AND IF YOU FLASH IT WITHOUT ADDING ROOT PERMISSIONS, YOU WILL LOSE ROOT. YOU HAVE BEEN WARNED.
ENJOY

Might as well grab me a spot n case I come across nething

I like this idea. So this is AOSP compiled for the EVO with no changes at all?

Nice work buddy

illogic6 said:
I like this idea. So this is AOSP compiled for the EVO with no changes at all?
Click to expand...
Click to collapse
Yes. This is completely stock with no modifications

Im no dev but I'd like to learn... would this be a good Rom to start with?
Sent from my PC36100 using XDA App

This looks very promising, AOSP choices are a limited in the evo department

I've seen the aosp rom in the heroc forum, that thing is a beast even compared to cm. So much potential on the evo, thank you so much!
Sent from my PC36100 using XDA App

overthinkingme said:
I've seen the aosp rom in the heroc forum, that thing is a beast even compared to cm. So much potential on the evo, thank you so much!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Can you post the link for this?
Sent from my PC36100 using XDA App

Nevermind I read OP again.

jm5503 said:
Can you post the link for this?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
See my signature
Sent from my HERO200 using XDA App

I assume no 4g?

Am I the only one who can't get titanium backup to work??
Sent from my PC36100 using XDA App

jm5503 said:
Am I the only one who can't get titanium backup to work??
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I believe titanium backup requires Busybox and that rom base does not have it installed. You should be able to install the busybox installer from the market.

wrod7 said:
I assume no 4g?
Click to expand...
Click to collapse
no 4g, no hdmi

I'm having a hard time getting busybox installed and superuser permissions working properly....can someone help me or upload a version with these working?
Sent from my PC36100 using XDA App

jm5503 said:
I'm having a hard time getting busybox installed and superuser permissions working properly....can someone help me or upload a version with these working?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Same Thing Here

Surprised we haven't seen this before.
I thought about trying to strip CM down to AOSP basics, since I've been too lazy to get something running from scratch.
I'm looking forward to messing around with it. At work right now and can't grab it yet, have most/all of the CM Evo specific fixes been added, like notification LED support (I assume the AOSP tree is made for the N1) and camera support?
Kinda separate question, but what is the difference (if any) in the official Nexus One builds that get pushed out to the phones OTA and doing a build from AOSP and flashing the Google Apps?

does hdmi and or 4g work with this

Building Android from source for Nexus S

EDIT: Oops, I meant to put this in General section. Sorry!!!
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
The first one is that there is of course no Google Apps. I understand why, but is there a good source for them? Or do the ones for CM7 work?
Second, I get the regular Android boot animation, not the cool Nexus S one. Is that normal?
Third, my Android version always says something like 3.1.x.x.x.x.x or something crazy. Is that normal? I was kind of expecting it to say GRJ22 2.3.4 or something like that.
I am trying to build full_crespo-user, FYI.

I use the normal gapps whenever I compile an aosp. Try the modded one specific for the nexus s. You would find it in the last pages of the nightlies thread.
Yes. The android marine blue animation is the default one for aosp.
The version number you are getting 3.1.xxzzxxxxxxxxxz is quite normal. This is the actual version of aosp. You can change it in your build.prop if you want to.
Good luck/
Sent from my Nexus S using Tapatalk

matt2053 said:
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
Click to expand...
Click to collapse
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?

Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
no need to pull them. anyway official binaries are available for the nexus s
http://code.google.com/android/nexus/drivers.html

Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
Yes, pull from the gingerbread branch! Master is almost always full of bugs and not the best to build. You know you have master when the build number is pi (the 3.1.4... one mentioned earlier).
To use repo to pull down the gingerbread branch, use the repo init command as usual but add "-b gingerbread" at the end (no quotes).
Sent from my Nexus S

I would love to know more about this master vs gingerbread branch difference. I've been building from master it seems. What purposes do the different branches serve? Can someone shed some light on the Android development process?
Sent from my Nexus S using XDA App

So master basically contains everything, all versions. Master is basically all of android xD
Now, you can do a -b gingerbread to just clone the gingerbread branch, which will give u the 2.3 code for everything on android.
** Note -b can also be used for froyo, eclair, etc. **
I hope this helps!

Not development. Moved to Q&A.

I have another question so I am bumping this up:
I have successfully build Android 2.3.5 for my Nexus S. Is there anyone who might help me adding Google Nexus boot animation and Google Apps, and putting it all into a flashable zip?

I figured out the zip thanks to this awesome thread: http://forum.xda-developers.com/showthread.php?t=732957
Now my problem is the keyboard. The "suggested" words are only names from my contacts, I don't get any regular English language suggestions. Any ideas?

[REF] Github repo for SGH-I997R Source Release

Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos). (Edit: I'm starting to consider doing things a bit differently in order to allow this to stay as a relevant reference - After all there are certain "core" features like Voodoo Lagfix/Sound that have no known detrimental effects and are basically expected from any kernel used by the community.)
One thing is that most of the other ref repos are on a github "team" account - mine is on a personal account. I'm going to look into whether I can change this without breaking the fork relationships.
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r
Initramfs from Wednesday's dump is at https://github.com/Entropy512/initramfs_sgh-i997r
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Update: Merged a pull request from LinuxBozo that has a bunch of .gitignore fixes and Makefile fixes.

Good work! Looking now.

Entropy512 said:
Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos)
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r - There is nothing visible there yet as the push is still in progress. It should be done within 30 minutes or so.
I don't have an initramfs repo yet - we need an initramfs dump from a device first.
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Click to expand...
Click to collapse
Absolutely awesome news :-D
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Oh blast, hadn't even seen that kernel code was available... thanks Entropy!

A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)

Entropy512 said:
A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)
Click to expand...
Click to collapse
Defuse kernel
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

nelomen said:
Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
Initramfs, radio firmware dump, proper /system dump. Ours is incomplete.

Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo

Entropy512 said:
Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo
Click to expand...
Click to collapse
Nice!! Anything buildable yet?

ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
should be buildable since initramfs is available, tomorrow gtg's voodoo commit should be available too. this is all very exciting.

ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
A few more things got pulled in last night.
Kernel - not much
Initramfs - Working CWM - or at least it comes up, it hasn't been fully tested functionally yet
As of last night a few people have custom kernels running including myself, although some people still can't boot them. CWM wasn't working until past midnight...
Next up is voodoo - Not sure if I'll include that in the main initramfs repo or not. Maybe as a branch. It is a fairly standard mod, so it should be in a readily accessible repo

Bad news - as I said before CWM hadn't been fully tested.
Apparently, after further testing, it still does indeed have some pretty severe issues.

Sadface
10c

P1 Wookie said:
Sadface
10c
Click to expand...
Click to collapse
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.

trolls suck.
GL guys.

Entropy512 said:
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.
Click to expand...
Click to collapse
Gotta love the trolls.
Good luck guys. I know you all will figure it out

Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.

bedwa said:
Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.
Click to expand...
Click to collapse
why no use of a client?

drowningchild said:
why no use of a client?
Click to expand...
Click to collapse
Finally got it to work, had to hack a command line client.... urg.

[DEV] CM7.2 Motorola Triumph

More information is listed at the site below
http://androidforums.com/triumph-al...-files-7-09-2012-5-30-pm-mst.html#post4641932

Just love the fact that we're basically redoing this whole phone. Lol.

Yeah I am slowly getting there with the device files. I will be updating the post each time I push back up to github and what works and doesn't.

I am stopping work on this with the gingerbread branch and now going to use the new gb-branch-7.2 branch as it was finally released on June 16th I forgot to check back.
http://www.cyanogenmod.com/category/blog
I will be updating the WX435 github during the day.
Edit: Update is done!

I believe this is the best way to go about doing this! If we can get by on base cm7 code then staying updated with the latest from cm7 shouldn't be a problem. Also it in therory should make cm9/ aokp etc easier to iron out all the bugs!
Whenever I get my laptop set back up to build, I'm going to work on picking out the best suited branch to start with from Code Aurora and try to get a vanilla froyo kernel based off the code Aurora sources working. Then from there try and apply those changes to the newer kernels off code Aurora.
It maybe a good idea to try to contact Motorola and see if they wont give us the branch and possibly even commit tag where they forked there kernel from cause I'm pretty sure they started making cchanges to a code Aurora branch on there kernel source. Just which one and where they forked it from is the question. That way we can apply the Motorola source over top that and get the exact changes moto made to the kernel!
If anyone else has anything to add to this or any insights pleas let us know!!
Sent from my Triumph using Tapatalk

Hey g60 if you cab get some logcats on some of the stuff that ain't working right ill look at em and see what I can find!
Sent from my Triumph using Tapatalk

b_randon14 said:
Hey g60 if you cab get some logcats on some of the stuff that ain't working right ill look at em and see what I can find!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
The stuff that is not working has not been added into the device files yet. There is a lot of missing code and lib files. Once I implement more of the changes and stuff isn't working I will holler at you, I have been really focused on fixing the video drivers. I want them playing all formats as perfect as possible before I start adding more stuff. :good:

Hey on the default.xml under the github remote you just have .. so it causes problems when trying to repo sync. Didn't know if you knew it was like that or not!

It should work fine, I just did a repo sync. Make sure you are running the right branch as CM7 changed it from "gingerbread"
repo init -u git://github.com/WX435/android.git -b gb-release-7.2

I just went back in and deleted my folder, then ran repo init again, copying directly from here and it still did the same thing when I tried to run repo sync.

Hop on IRC

b_randon14 said:
I just went back in and deleted my folder, then ran repo init again, copying directly from here and it still did the same thing when I tried to run repo sync.
Click to expand...
Click to collapse
I just looked at it myself. Under remote it shows "..", shouldn't it be git://github.com/

dsmryder said:
I just looked at it myself. Under remote it shows "..", shouldn't it be git://github.com/
Click to expand...
Click to collapse
Nope this is correct it works fine. There are changes CM Team did.
https://github.com/CyanogenMod/android/blob/gb-release-7.2/default.xml

g60madman said:
Nope this is correct it works fine. There are changes CM Team did.
https://github.com/CyanogenMod/android/blob/gb-release-7.2/default.xml
Click to expand...
Click to collapse
So with that, would you have to setup all of your own remotes?
I thought that was to have a Pre-entry for "git remote"?

If you're having issues with the .. in the manifest, see the comments on this commit from cm/android/ where this was originally introduced. The solution is in there:
https://github.com/CyanogenMod/android/commit/89acec784fd50305cc55d05ecb3416fcd7c3eb0e

Yeah i fixed mine by deleting the .repo folder, curling the latest repo into myh ~/bin folder, then pulling the repo in again.

Man I was surprised. I finally got my cm7-bROM repo setup on my new Linux mint install and finally got everything updated from upstream and added some more open commits from gerrit and built it and to my surprise, it built fine with no errors a d I flashed it and it worked great! I figured it would blow up where it had been over a month or two since I had synced and built my ROM and with all the 7.2 release stuff I thought for sure it wouldn't build and add I was building on Linux mind that I had never built on!
Hey g60 you need any help with the device files? I noticed you ain't even got the triumph device repo in the manifest anymore. If you need me to help with anything my box is up and running great! I built my rom in like 47 minutes first time and I was using ccache so hopefully the next build will be faster!
I am digging into my stock code Aurora kernel nor booting. I thought it built fine but I noticed there were some warning spit out by the linker during the build and I tried with linaro and the included 4.4.3 with aosp and it did the sane thing so I'm gonna try to get the bottom of those warnings because I think that may have something to do with it!
Ill post the pastebin of the warning up in the kernel thread later!
Sent from my Triumph using Tapatalk

No updates for a while, still nothing works?

I have been really busy and have had maybe had 1-2 hours to work on the device files in the last 6 days. I should have some more time this week so will see what I can get out.

headset does not register on boot if plugged in
Click to expand...
Click to collapse
Pretty sure this bug was in all CM7 builds before. I also experiences the same thing with MIUI rom.

Porting CM10 to N7105 variants.

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?

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

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.

DarthPiggie said:
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.
Click to expand...
Click to collapse
That is a proprietary from the i9300...
/proprietary_vendor_samsung/tree/ics/i9300/proprietary/system/vendor/firmware/SlimISP_ZK.bin
https://github.com/TheMuppets/propr.../ics/i9300/proprietary/system/vendor/firmware

Check my github. I've been messing with the t889 and AOKP. It's almost ready. Hopefully tonight I'll get time to finish it up.

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

DarthPiggie said:
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
Click to expand...
Click to collapse
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.

Entropy512 said:
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.
Click to expand...
Click to collapse
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!

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

DarthPiggie said:
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
Click to expand...
Click to collapse
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.

cmenard said:
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.
Click to expand...
Click to collapse
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

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.

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

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

DarthPiggie said:
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
Click to expand...
Click to collapse
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.

Thanks I did not know that. I will definitely take a look. That explains why the build was so broken. Ugh.

DarthPiggie said:
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
Click to expand...
Click to collapse
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.

Entropy512 said:
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.
Click to expand...
Click to collapse
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

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

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.