CM10 ported from the n7100
THIS IS A WORK IN PROGRESS, IT WILL BOOT BUT IT IS NOT FOR DAILY USE, I AM ONLY POSTING IT BECAUSE I NEED HELP MAKING THE REST OF IT WORK.
I AM NOT A DEV. SO DON'T GET MAD AT ME IF THIS BRICKS YOUR PHONE BECAUSE YOU CAN'T READ SIMPLE INSTRUCTIONS
What's not working
Cellular connection (wifi works fine)
Sound (It was working but somehow I broke it)
That should be it.
Q&A thread
Installation instructions
Download Rom below
Save to SD Card
Reboot to recovery (only tested with TWRP)
WIPE SYSTEM AND FACTORY RESET
Flash Rom
Flash GAPPS
Wipe Dalvik and Cache
Reboot
Wait (It may take a while at the welcome screen)
DOWNLOADS
CM10
gapps
This is a direct port of cyanogenmod 10 for the n7100 source can be found here
reserved...
one more just in case...
There is no way I could build on my PC it would take a week just to finish, by then we would be on CM 11, but yes this is a port of the n7100 CM10 nightly from today, the connection issues are because there is no modem I am sure, or at least not one that I can find, and I can't make it stick, and the sound is because it is set up for the n7100, that should be an easy fix that I will work on tonight.
Thinking about this, I'm not sure it will ever get cell network. Because there needs to be a compiled kernel with the Qualcomm modem enabled. And since this is the 7100 it doesn't have lte. So even with the correct ril files, it won't work.
We need an aosp kernel with Qualcomm modem support.
If someone wanted to look at the quicnyatt defconfig on cyanogenmod's site, you might get inside for the defconfig needed for the smdk4412
Also
Can I ask that we keep this thread to development purposes.
Please do not post OMG THIS IS AWESOME. That does nothing for helping.
If you have a development finding or fix, post it up. Otherwise please do not post.
Thanks.
antiochasylum said:
Thinking about this, I'm not sure it will ever get cell network. Because there needs to be a compiled kernel with the Qualcomm modem enabled. And since this is the 7100 it doesn't have lte. So even with the correct ril files, it won't work.
We need an aosp kernel with Qualcomm modem support.
If someone wanted to look at the quicnyatt defconfig on cyanogenmod's site, you might get inside for the defconfig needed for the smdk4412
Also
Can I ask that we keep this thread to development purposes.
Please do not post OMG THIS IS AWESOME. That does nothing for helping.
If you have a development finding or fix, post it up. Otherwise please do not post.
Thanks.
Click to expand...
Click to collapse
Are the kernel modules similar for the Quincy as it has the Qualcomm S3 SOC and we have the Exynos? Would it not work to compile a kernel with the open source files from Sammy?
I may be way off on this, I am below a rookie at kernel compilation.
Sent from my SAMSUNG-SGH-I317 using xda premium
Possible kernel ?
I am watching this one like a hawk, just earlier they said that they are testing an aosp kernel for the n7105 (international version with LTE). I already use the tw variant
forum.xda-developers.com/showthread.php?t=2000328&highlight=7105
id10terrordfw said:
Are the kernel modules similar for the Quincy as it has the Qualcomm S3 SOC and we have the Exynos? Would it not work to compile a kernel with the open source files from Sammy?
I may be way off on this, I am below a rookie at kernel compilation.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
The quincy has the old snapdragon 1.5, it does not have the new msm8960 as the S3's do. Also its not about modules. I've downloaded source and its pretty horrible, as most Samsung crap is.
Compiling a kernel would work from sources, it just has to support aosp, since CM uses its own ramdisk too.
Bout10bucks said:
I am watching this one like a hawk, just earlier they said that they are testing an aosp kernel for the n7105 (international version with LTE). I already use the tw variant
forum.xda-developers.com/showthread.php?t=2000328&highlight=7105
Click to expand...
Click to collapse
I'll check it out.
Am I the only one really doing anything here? Seems like no one cares about pure aosp. Everyone doesn't want to loose stylus features.
antiochasylum said:
The quincy has the old snapdragon 1.5, it does not have the new msm8960 as the S3's do. Also its not about modules. I've downloaded source and its pretty horrible, as most Samsung crap is.
Compiling a kernel would work from sources, it just has to support aosp, since CM uses its own ramdisk too.
I'll check it out.
Am I the only one really doing anything here? Seems like no one cares about pure aosp. Everyone doesn't want to loose stylus features.
Click to expand...
Click to collapse
I am all for pure AOSP I just don't know how to do much. I am happy to help test but that is about the extent of capabilities right now. I love my stylus but don't need all the stylus "shortcuts". I ran AOSP on my note one and the stylus worked great even did good for the harder you pressed on the stylus the darker it would write. The only thing I lost were all the button and shortcuts integrated with touchwiz. I used papyrus as my snote/smemo replacement and actually prefer it over the Samsung crap that lost my memos every time I flashed anything.
Sent from my SAMSUNG-SGH-I317 using xda premium
All I want is AOSP, maybe a little Paranoid Android. S-Pen lost it's novelty for me after a couple of hours. I also must have misread the kernel post. NEAK only has a Sammy kernel
Sent from my SAMSUNG-SGH-I317 using xda app
Yeah, I'll chime-in, too. Only thing I'm missing on this phone is AOSP ROM's. TouchWiz is TouchJiz. Specific features or not, AOSP is where it's at, and I would seriously consider returning this device if AOSP development was to do anything on the lines of cease. Frankly, it's killing me that there hasn't been more AOSP dev'ing up to this point. Devs are all we end-users have, and believe me, if I had any talent in that realm, I'd be offering my limbs towards development. Only thing, is I'm merely a user. I will test anything I'm able to, though! My precious phablet is my personal lab rat! Hehe...
You need to replace system/etc/firmware with yours. That's your modem. And make sure your ro.telephony.ril_class path is correct
Sent from my SGH-I927 using xda premium
dman3285 said:
You need to replace system/etc/firmware with yours. That's your modem. And make sure your ro.telephony.ril_class path is correct
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
This guy^
Sent from my SAMSUNG-SGH-I317 using xda premium
Does this mean dman has a note2 that would be sick
Sent from my SAMSUNG-SGH-I317 using Xparent Red Tapatalk 2
otisman said:
Does this mean dman has a note2 that would be sick
Sent from my SAMSUNG-SGH-I317 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
No.. but.... One of my team members does and we are compiling cm10 from source for the note 2..
Sent from my SGH-I927 using xda premium
dman3285 said:
You need to replace system/etc/firmware with yours. That's your modem. And make sure your ro.telephony.ril_class path is correct
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
There is no firmware in /system/etc. The only firmware is vendor/firmware.
And isn't ro.telephony back from gingerbread? Or is than an aosp thing? Its not in stock Samsung firmware.
Also even with those correct, we still don't have a kernel with Qualcomm modem support. So until we get that. Its dead in the water.
Your better off trying the 7100 rom on the 317. Since we already have a supported kernel.
Also remember DEVELOPMENT ONLY. Ask yourself. Will this aid in the development of this rom before posting!
antiochasylum said:
Thinking about this, I'm not sure it will ever get cell network. Because there needs to be a compiled kernel with the Qualcomm modem enabled. And since this is the 7100 it doesn't have lte. So even with the correct ril files, it won't work.
We need an aosp kernel with Qualcomm modem support.
If someone wanted to look at the quicnyatt defconfig on cyanogenmod's site, you might get inside for the defconfig needed for the smdk4412
Also
Can I ask that we keep this thread to development purposes.
Please do not post OMG THIS IS AWESOME. That does nothing for helping.
If you have a development finding or fix, post it up. Otherwise please do not post.
Thanks.
Click to expand...
Click to collapse
Quincyatt won't be useful. There's a HUGE difference between a complete integrated Qualcomm SoC such as found in the quincyatt and d2 family, and a Qualcomm modem hung off of the Exynos4.
So far, no one has yet to figure out the proper defconfig for this. Although probably you could get it by looking at the Perseus N7105 defconfig.
Looks like CONFIG_QC_MODEM might do the trick?
antiochasylum said:
The quincy has the old snapdragon 1.5, it does not have the new msm8960 as the S3's do. Also its not about modules. I've downloaded source and its pretty horrible, as most Samsung crap is.
Compiling a kernel would work from sources, it just has to support aosp, since CM uses its own ramdisk too.
I'll check it out.
Am I the only one really doing anything here? Seems like no one cares about pure aosp. Everyone doesn't want to loose stylus features.
Click to expand...
Click to collapse
I care! 1000%! I've never used that crappy pen. AOSP is the only thing I care about.
I am also all for aosp just let me know how to help. What we've tried already is replacing the entire vendor and csc and build.prop from i317 and dropping into a n71xx ROM and flashing. In addition have tried a large number of random RIL associated files from i317 into n71xx ROM and still no dice with the modem. Have made sure that no modem or kernel are being flashed while doing this. Logcat -b radio still spits out RIL related crap. I don't know enough about kernels to mess with defconfig unfortunately but I'm willing to help however I can. Fwiw replacing vendor/CSC/build.prop was enough to get a sprint note 2 ROM to work on T-Mobile thanks to someone who did that already.
My time is limited but let me know if some of you guys want to chat about this together on irc or something. I'm on freenode a few days a week after 9pm EST.
Edit: I should clarify all the things above that we tested (lpsi2000 and I) were TW based ROMs but getting the modem to fire up in whichever sense when porting things from n71xx I would guess should apply.
Thanks Entropy for pointing out that. I have to add kernel to my long list of things to learn more about in detail.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Trust me, you're not alone. AOSP would make this phone absolutely perfect.
Related
I have been looking for an AOSP ROM for the SGH-T889, but I have not found one yet. Does anyone know of an AOSP build for the Note II?
I haven't found any, so I wanted to build my own. It seems like all that I need is to:
1) get the AOSP source from google
2) copy drivers from opensource.samsung.com/ (search for sgh-t889) into the AOSP tree.
3) build
4) install
Is this all that needs to be done? Or is there more that is needed to do this? I have built ASOP for Nexus S, but not for anything else.
im pretty sure it's more complicated than that. but again i don't know **** about that lol.
I wish I had some free time to try it out. Hopefully this weekend I can explore it more.
NeilMonday said:
I have been looking for an AOSP ROM for the SGH-T889, but I have not found one yet. Does anyone know of an AOSP build for the Note II?
I haven't found any, so I wanted to build my own. It seems like all that I need is to:
1) get the AOSP source from google
2) copy drivers from opensource.samsung.com/ (search for sgh-t889) into the AOSP tree.
3) build
4) install
Is this all that needs to be done? Or is there more that is needed to do this? I have built ASOP for Nexus S, but not for anything else not that easy .[/QUOTEhttp://rootzwiki.com/topic/31166-tutorial-so-you-want-to-build-aokp-jb-ubuntu-1204
Click to expand...
Click to collapse
Thanks for link. It looks like aokp doesn't have note II support yet though. Or did I miss something?
Just found this which may be helpful.
http://forum.xda-developers.com/showthread.php?t=1977993
Does anyone think there would be any problem running this on an sgh-t889 instead of a n7100?
I wish xda wouldn't limit you to 10 posts before you can post in development threads.
NeilMonday said:
I wish xda wouldn't limit you to 10 posts before you can post in development threads.
Click to expand...
Click to collapse
They should make it 30 so you can't do stuff like this.
Sent from my SGH-T889 using Tapatalk 2
No, if it was 30 I would just make 20 more BS posts. If it was 0 then I could immediately make posts that were relevant.
NeilMonday said:
No, if it was 30 I would just make 20 more BS posts. If it was 0 then I could immediately make posts that were relevant.
Click to expand...
Click to collapse
brashmadcap said that cuz where you posted btw fail lol j/k -------->Mods sorry
@NeilMonday - Chit-chat posts do NOT belong into the development boards. I suggest you make yourself familiar with our rules before posting fancy stuff into the wrong sections.
Thread moved to General.
How about you educate yourself so you don't have to rely on others? Js
NeilMonday said:
I have been looking for an AOSP ROM for the SGH-T889, but I have not found one yet. Does anyone know of an AOSP build for the Note II?
I haven't found any, so I wanted to build my own. It seems like all that I need is to:
1) get the AOSP source from google
2) copy drivers from opensource.samsung.com/ (search for sgh-t889) into the AOSP tree.
3) build
4) install
Is this all that needs to be done? Or is there more that is needed to do this? I have built ASOP for Nexus S, but not for anything else.
Click to expand...
Click to collapse
Unfortunately its not that easy to build AOSP ROMs for devices like these. Source from samsung may contain some drivers but not all of them since OEMs tend to hold some back. You would have to fix such problems which honestly is a headache. You would also need to build a working kernel.
If you want an AOSP ROM just get a Nexus because this is not a device for AOSP ROMs. You will lose the functionality of the s-pen or other features you liked when you got this device unless they are ported(which again, is a headache to do!).
Sent from my SGH-T889 using Tapatalk 2
minhajmsd said:
Unfortunately its not that easy to build AOSP R
for devices like these. Source from samsung may contain some drivers but not all of them since OEMs tend to hold some back. You would have to fix such problems which honestly is a headache. You would also need to build a working kernel.
If you want an AOSP ROM just get a Nexus because this is not a device for AOSP ROMs. You will lose the functionality of the s-pen or other features you liked when you got this device unless they are ported(which again, is a headache to do!).
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Here is a post from codeworx explaining why he won't support Samsung any http://forum.xda-developers.com/showpost.php?p=31873214&postcount=7773
deeznutz1977 said:
Here is a post from codeworx explaining why he won't support Samsung any http://forum.xda-developers.com/showpost.php?p=31873214&postcount=7773
Click to expand...
Click to collapse
Damn, wish i would have read that before I got this phone. Still UBER happy with my selection, just wish I would have researched on that a little more.
Too bad about sammy not providing any documentation on the exynos chip.
rahilkalim said:
Damn, wish i would have read that before I got this phone. Still UBER happy with my selection, just wish I would have researched on that a little more.
Too bad about sammy not providing any documentation on the exynos chip.
Click to expand...
Click to collapse
Good news is samsung is already starting to open source the exynos chipset, they listened to the developer community and have already responded.
Edit: link
http://git.insignal.co.kr/samsung/e...hardware/samsung_slsi/exynos4/?h=s-ics-exynos
Sent from my SGH-T889 using xda premium
After installing a couple of the N7100 roms (CM 10 and an AOKP versions), It seems like there are a few things that don't work so far like the camera and cell/data. I think the cell/data should be fixable since the Nexus 4 and the SGH-T889 use the same baseband (MDM9215)?
http://www.anandtech.com/show/6386/samsung-galaxy-note-2-review-t-mobile-/9
http://forum.xda-developers.com/showthread.php?t=1964850
Sure this isn't the only problem, but its a start. Thoughts?
Based off of madmack's CM10 port and his kernel/audio changes for our device, I've compiled the latest ParanoidAndroid from source based off of the N71000 and modified it for our device.
There are... more than a few issues. This is more of a practice build for me, as it's one of the first I've built from source. The issues with my build on top of madmack's CM10 port are:
- No audio (I'm not sure why, I included all of madmack's audio modifications in my build, and even directly copied the audio framework files from his latest CM10 zip)
- No data: I'm 99.9% sure this is due to a non-existent APN, but when you try to edit the APNs in Settings, it just brings you back to the main Settings screen.
- No call audio issue is back - madmack, what did you do to solve this, and did you commit the changes to your github?
If someone could take a look at my build and discover why the audio won't work, and why the settings kicks you out of the APN screen, that would be great. I can't figure out what's wrong. Everything else works just as well as the CM10 build, however.
Download: http://www.mediafire.com/?2yxh5575ynbi8ao
First! Thanks for testing it out, now just to make it happen captain(wish i knew how to help)
Reserved
Looking forward to this!
Sent from my Samsung Galaxy Note II
Moose0704 said:
Looking forward to this!
Sent from my Samsung Galaxy Note II
Click to expand...
Click to collapse
Thanks! It's mostly working, I just really need to figure out the audio issues. Can anyone with more knowledge than me compare the audio framework of this ROM against the framework in madmack's CM10?
Sent from my GT-N7100 using Tapatalk 2
IMHO and no dis respect to other ROM developers, PA is the most wanted rom I want to flash on my GN2. subscribed!
Just a heads up, later tonight I'm going to rebuild this ROM fully from source and see if I can integrate a form of madmack's audio fix.
Sent from my SGH-I317 using Tapatalk 2
What are are the chances of this getting to work on tmobile. This is the only rom I want.
Sent from my SGH-T889 using xda app-developers app
philupjfry said:
What are are the chances of this getting to work on tmobile. This is the only rom I want.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
It should already work!
Sent from my JellyBean Galaxys3
Sounds good cant wait till all the kinks are worked out
Sent from my SGH-T889 using xda app-developers app
Awesome. I'm assuming that the s pen will not work on this Rom right?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Hey, thanks for directing me here.
In my build im almost positive I had the audio working, but it was really late so im not 100% sure.
Still the same exact issue as far as wifi/no data/cant edit apn's...but I have to assume part of that may be a kernel problem, or like you said, due to possible lacking apk's. I'll mess around with it more tonight though
heroskyy said:
Hey, thanks for directing me here.
In my build im almost positive I had the audio working, but it was really late so im not 100% sure.
Still the same exact issue as far as wifi/no data/cant edit apn's...but I have to assume part of that may be a kernel problem, or like you said, due to possible lacking apk's. I'll mess around with it more tonight though
Click to expand...
Click to collapse
I'm not so sure it's a kernel problem, because all three of those things are working on the CM10 build. Even when I flash madmack's newest kernel over this build these issues are still not resolved. I'm trying to figure out how to build the APN settings into the ROM to bypass the settings issue.
I'm letting Ubuntu compile straight from PA source at the moment, combined with madmack's git modifications for our phone. However, any recent fixes he made (including fixing call audio) will not be present until he uploads newer versions to his git.
ShotSkydiver said:
I'm not so sure it's a kernel problem, because all three of those things are working on the CM10 build. Even when I flash madmack's newest kernel over this build these issues are still not resolved. I'm trying to figure out how to build the APN settings into the ROM to bypass the settings issue.
I'm letting Ubuntu compile straight from PA source at the moment, combined with madmack's git modifications for our phone. However, any recent fixes he made (including fixing call audio) will not be present until he uploads newer versions to his git.
Click to expand...
Click to collapse
Ahhh, good point. I hadn't gotten to try his newest kernel or updates yet.
While building the APN settings to the ROM may work, I still find it disheartening and a tad irritating that you cant even edit any mobile network selection. That indicates to me that there's a problem more so in the frame work of the ROM (lacking apks, kernel malfunction, etc) that isn't allowing any data to be edited or retrieved.
I've also wondered about flashing an AT&T modem over top the Paranoid ROM . I feel that may be another thing that would explain the inability to edit APN setting and to not have any form of data or WIFI. Though...I don't know why that wouldn't be the case for the current CM10 build...unless its because the Paranoid build was solely intended for the N7100.. Thoughts?
ohhhhh
this would be very good
Just a heads up:
Im planning on merging all the newest material for the most recent cm10 build with paranoid, as well as modifying the att modem to (hopefully) integrate it into the paranoid frame work tonight. If my theory is correct, it should solve most issues with this rom, but may retain some of the most current cm10 issues. If it works ill post a thread in the development section for testing.
Compiling a new build right now.
Waiting
Sent from my SGH-I317 using xda premium
If you get a chance Can you port jellybam?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
mardos said:
Waiting
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Sorry about the delay, I haven't compiled too many ROMs before... I keep getting the error
Code:
In file included from external/zlib/gzclose.c:6:0:
external/zlib/gzguts.h:21:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make: *** [/Volumes/t0att/paranoid/out/target/product/t0att/obj/STATIC_LIBRARIES/libz_intermediates/gzclose.o] Error 1
(standard_in) 1: illegal character: N
(standard_in) 1: illegal character: N
(standard_in) 1: illegal character: N
(standard_in) 1: illegal character: N
Anyone have experience with this error? This error didn't come up last night, I haven't changed anything since.
http://www.androidpolice.com/2013/0...e-files-is-this-the-google-edition-galaxy-s4/
Sorry if this is a super noob question/Thought
If We Download This And Flash It In The "Download Target" Screen or "Download Mode" (power + Volume Down + Home Button) Does This Mean I Can Upgrade To Google edition (Or Are we somewhat close to the port) ?:fingers-crossed:
Once again i apologize for the thought:angel:
Slicktune said:
75 views and no feedback? Damnnn..:thumbdown:
I thought we were excited about this. ..
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I would not expect too much interest in a kernel that can't be used on this device for TMo service.
luckyduck69 said:
This has "I9505" in the link. What is the model number of you T-Mobile GS4?
Second thought, please go ahead & flash it. Then post back here with the results.
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Would be funny but that's kinda mean to break a $650 device o.0
Sent from my SGH-M919 using Tapatalk 2
luckyduck69 said:
This has "I9505" in the link. What is the model number of you T-Mobile GS4?
Second thought, please go ahead & flash it. Then post back here with the results.
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
First off, you should not even joke about telling someone to flash something they shouldn't. EVER. Some people will take you seriously. Please don't do that...
Second... you and others should realize by now that our M919 can flash 95% of all software items made for the international i9505. M919 is simply the Tmo version of the 9505, as you should know....the hardware is identical. So many people still think they are different phones just because ours say M919. The only catch is you can never flash another carriers modem...it's that simple.
99% of the ROMs from the international i9505 forums and all other carriers...Verizon, AT&T, Sprint etc, run perfectly on our M919....ya just gotta flash a universal kernel directly after flashing the i9505 ROM....ie, Faux or Ktoonez etc. Aside from people who have to have certain Tmo specific software (WiFI calling, visual VM etc)...I have no idea why people are still using the old and outdated MDL firmware.
To the OP...wait for the ROM and kernel to be released in the international forums and then wait again for Faux or Ktoonez to make the kernel universally compatible with multiple variants of the i9505.
Seems there are still peeps out there that think they are stuck to using only Tmo M919 software. I'm surprised more Tmo users are not using the latest and greatest firmware for the i9505. Smearing, camera lag...you name it, was fixed long ago on the international firmware.
My M919 is FLYING with Wanam's 1.2 MF2 ROM, Faux v6m kernel.
@ Hoggles
Thanks for that informative post.
Regarding the WanamLite ROM you installed, is Call Recording operating properly?
Skvalex from CallRecorder asked me to try this
http://galaxys4root.com/t-mobile-ga...i9505attt-mobilecanadianapp2sdcall-recording/
to see if CallRecorder works. It's version 1.1 but I read it may break 4G LTE.
I see the ROM you installed is 1.2 and just wanted to know what your experience was with either the call recording feature native to that ROM, or if you've perhaps tried CallRecorder, and if 4G LTE is working without issue.
@ luckyduck69
The op was just trying to be helpful.
Everyone is learning, and not just on xda, but in life in general.
Hoggles just didn't want the op or anyone else to Bork their new, expensive S4 and was passionate about that.
As we all know, sometimes things are said that are taken literally, and considering their are millions of xda members, there may have been several that would have flashed something they're not supposed to, and have a brick in their hands.
The above is just my observation. Nothing personal
Hoggles said:
To the OP...wait for the ROM and kernel to be released in the international forums and then wait again for Faux or Ktoonez to make the kernel universally compatible with multiple variants of the i9505.
Seems there are still peeps out there that think they are stuck to using only Tmo M919 software. I'm surprised more Tmo users are not using the latest and greatest firmware for the i9505. Smearing, camera lag...you name it, was fixed long ago on the international firmware.
My M919 is FLYING with Wanam's 1.2 MF2 ROM, Faux v6m kernel.
Click to expand...
Click to collapse
Thanks my brother, I appreciate you understanding my point of view
Sent from my SGH-M919 using xda app-developers app
Pulled the source code for the T-Mobile Note 3 from the Sammy website (Model #N900T).
Includes the kernel and platform source folders.
Download and play....or fix.....your choice.
Link is from Google Drive and can be downloaded below.
https://drive.google.com/file/d/0B5BEzKcGiwjpN1plb2t1U1JZbGM/edit?usp=sharing
Cool. DL now. Hopefully can use this to figure out wifi-calling.
Finally, AOSP here we come
I thought source code was released back on October 4th?
idtheftvictim said:
I thought source code was released back on October 4th?
Click to expand...
Click to collapse
It was released a while ago. I just didn't see it uploaded here and some of the stuff in the kernel and platform folders can be useful to people for tinkering or fixing so I uploaded.
idtheftvictim said:
I thought source code was released back on October 4th?
Click to expand...
Click to collapse
Well awesome! Thank you so much dude! How is AOSP coming along? Any progress?
Sent from my SM-N900T using xda app-developers app
I know this question is out of this thread, but anyone knows when kikat be available for note 3??
Sent from my SM-N900T using xda premium
I'm finally going to try and tinker with this
Sent from my SM-N900T using xda app-developers app
iakeco said:
I'm finally going to try and tinker with this
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
i wish i knew HOW to tinker with this! lol
do you need a linux box to build a rom and/or kernel or is it something that can be done just as well on a windows box?
chipis said:
I know this question is out of this thread, but anyone knows when kikat be available for note 3??
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
if you know that it has nothing to do with this thread then why ask? And if your asking about a touchwiz 4.4 no one knows samsung usually takes forever to do this. For example they just started rolling out 4.3 for the note 2 so my guess would be about a year lol. And as for a AOSP KitKat...yet again no one knows btw never ask for ETA's
geekcentercreations said:
Pulled the source code for the T-Mobile Note 3 from the Sammy website (Model #N900T).
Includes the kernel and platform source folders.
Download and play....or fix.....your choice.
Link is from Google Drive and can be downloaded below.
https://drive.google.com/file/d/0B5BEzKcGiwjpN1plb2t1U1JZbGM/edit?usp=sharing
Click to expand...
Click to collapse
I downloaded this from Sammy a few weeks back, and I was struck by how little is there. Yes, the full kernel sources are there - though of course a lot of stuff is still hidden in binary firmware blobs (presumably the TIMA/KNOX interface falls in this category). What struck me though was how little *platform* stuff is there. Is anyone else surprised by this? I would've thought they built more of their work on open-source foundations, but maybe not.
Is becoming more TizenOS with each new phone if you ask me
Sent from my SM-N900T using XDA Premium 4 mobile app
Qwallace70129 said:
Is becoming more TizenOS with each new phone if you ask me
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can agree with this.
pyrilium said:
I downloaded this from Sammy a few weeks back, and I was struck by how little is there. Yes, the full kernel sources are there - though of course a lot of stuff is still hidden in binary firmware blobs (presumably the TIMA/KNOX interface falls in this category). What struck me though was how little *platform* stuff is there. Is anyone else surprised by this? I would've thought they built more of their work on open-source foundations, but maybe not.
Click to expand...
Click to collapse
Well you have to remember, 4.3 Samsung is 4.3 samsung. If you ever looked inside the apks, there is a ton of stuff not used. Reason that's so, it's more generic across devices.
The only real changes are drivers/libs. A lot of those get pulled from the device when building anyway.
As far as I've ever seen, an individual cannot build a lib. You cannot reverse engineer them. Nothing.
If the specific libs needed to make things work are not available, then they just won't work yet. It's that plain an simple. I've helped out a lot in source building threads.
I wish it was easier, but sadly it's not.
Sent from my SM-N900T using Tapatalk 2
cbucz24 said:
Well you have to remember, 4.3 Samsung is 4.3 samsung. If you ever looked inside the apks, there is a ton of stuff not used. Reason that's so, it's more generic across devices.
The only real changes are drivers/libs. A lot of those get pulled from the device when building anyway.
As far as I've ever seen, an individual cannot build a lib. You cannot reverse engineer them. Nothing.
If the specific libs needed to make things work are not available, then they just won't work yet. It's that plain an simple. I've helped out a lot in source building threads.
I wish it was easier, but sadly it's not.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I've done a lot of work administering standard linux machines and it's a completely different world. They may be using an open-source core OS, but it's clear that none of the vendors treat their development itself as a process that contributes to free software.
By libs, do you mean the kernel modules and/or binary firmware blobs that are needed to support different bits of hardware? Or actual system libraries? I guess in this case, both are frequently closed. I heard a couple months back that the Android lead engineer at Google actually stepped down over the issue of OEM-supplied firmware blobs - specifically how un-transparent the process is, and how it's hard to even get access to the binaries for distribution, let alone the source D:
I have 4.4.2 source. Github. Linux building environment. Now I'm making a stock ROM to upload to XDA. Anyone with time to explain how to do so. All info accepted (-_-).
Sent from my SM-N900T using xda app-developers app
Since it appears I am the only one to build (working) kernels for the LEAKED kitkat touchwiz rom - I figured I would post some "helpfull hints" here.
I know people INSIST that kernels are either AOSP or TW - this is 100% UNTRUE - kernels are specific to the version of android - the sooner people accept this, the sooner we can get MORE KERNELS for the leak.
HINT: CM is NOT AOSP - CM IS CM
Source used was Samsung KitKat Source for the i9505g
Below is the STOCK defconfig file as pulled from the leaked kernel from samsung
WiFi Fix involves edits to the ROM, to the RAMDISK and to the source from the i9505g
<removed attachement as requested by CM members>
Thanks for all your help. We need someone with your knowledge to stick around. You are appreciated.
Sent from my SGH-M919 using Tapatalk
[email protected] said:
Thanks for all your help. We need someone with your knowledge to stick around. You are appreciated.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Totally agreed thanks again op!
Sent from my GT-I9505G using XDA Premium 4 mobile app
So I just flash the zip with t.w. Kit Kat 4.4. Thanks
Sent from my SGH-M919 using xda app-developers app
xda23 said:
So I just flash the zip with t.w. Kit Kat 4.4. Thanks
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This isn't a kernel, it's merely a defconfig used to build the kernel.
erid2thed said:
Since it appears I am the only one to build (working) kernels for the LEAKED kitkat touchwiz rom - I figured I would post some "helpfull hints" here.
I know people INSIST that kernels are either AOSP or TW - this is 100% UNTRUE - kernels are specific to the version of android - the sooner people accept this, the sooner we can get MORE KERNELS for the leak.
HINT: CM is NOT AOSP - CM IS CM
Source used was Samsung KitKat Source for the i9505g
Below is the STOCK defconfig file as pulled from the leaked kernel from samsung
WiFi Fix involves edits to the ROM, to the RAMDISK and to the source from the i9505g
Click to expand...
Click to collapse
What there be any way that you could help me try to build a building rom for the note 3 t-mobile USA 4.4.2 based on Mexico N900W8 official 4.4.2
Sent from my SM-N900T using Tapatalk
ktetreault14 said:
What there be any way that you could help me try to build a building rom for the note 3 t-mobile USA 4.4.2 based on Mexico N900W8 official 4.4.2
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Not to sound like an ass, but ask CM
their developers are requesting (in a not so nice way) I pull all my work, including the STOCK SAMSUNG DEFCONFIG file in the OP above.
I removed the attachment in the OP, as requested by 3 CM developers, as threats of legal action where made.
I qm sorry man. That sucks. Its a lost cause asking CM to help with TW so I guess ill be stuck waiting on tmo
Sent from my SM-N900T using Tapatalk
ktetreault14 said:
I qm sorry man. That sucks. Its a lost cause asking CM to help with TW so I guess ill be stuck waiting on tmo
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Funny thing is they claimed my kernel was kanged from them. A TW kernel ...
Sent from my GT-I9505G using XDA Premium 4 mobile app
erid2thed said:
Funny thing is they claimed my kernel was kanged from them. A TW kernel ...
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A Touchwiz kernel kanged from a CM kernel. Thats ridiculous. The only time I ever heard of that was the devil dualboot on note 2
Sent from my SM-N900T using Tapatalk
this is the best way to kill forum... sholudn't it ment to be here for sharing? and educational pourposes..?
you fixed the problem and have shared to everybody just to let all use it and this is the money with you get paid for..
this should be an hobby, not a sort of childish competition, or ment as a work..
forcing somebody to quit this way is very bad.. plus forcing to remove even stock samsung stuff that i and lots of other people, surely also out of xda, does have already on they're phone sounds really as an uncovered personal attack and plus we are all suffering for this as we can't use and try the very best and innovative kernel i've ever had on my phone!!!
i was about to start learning and maybe build a kernel in the future but sounds like no way i'm going to be into this..!!
anyway if you are going to develop again for your personal use please fil free to pm me or to to add me to a mailing list maybe
i'll pm you (again sorry) my mail, and please if i'm bothering you just tell me, i understand
erid2thed said:
I was told Steve from cm worked for Samsung and has rights to the file and I am to pull all kernels and related files ...or else legal action will be taken. They even claimed GPL violation for me posting the leaked kernel in a stand alone installer. Yes.. I am the one who posted it so I am the one required to post source ... So I pulled it...
This makes every ROM with a leaked kernel a violation as there is no source. But they only target me and my team.
Do I got your email address... Don't remember if I do or not.
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They can't claim GPL violation on that. Thats just ridiculous
erid2thed said:
I was told Steve from cm worked for Samsung and has rights to the file and I am to pull all kernels and related files ...or else legal action will be taken. They even claimed GPL violation for me posting the leaked kernel in a stand alone installer. Yes.. I am the one who posted it so I am the one required to post source ... So I pulled it...
This makes every ROM with a leaked kernel a violation as there is no source. But they only target me and my team.
Do I got your email address... Don't remember if I do or not.
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, it's petty stuff like this that drove me away from CM. It's a great rom, but they've forgotten where they came from.
TOUCHWIZ 4.4.2 kernel source is out for Note 3 http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-N9005
Maybe this can help with making a kernel for the S4?
BoboBrazil said:
TOUCHWIZ 4.4.2 kernel source is out for Note 3 http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-N9005
Maybe this can help with making a kernel for the S4?
Click to expand...
Click to collapse
I wish but it doesn't
we need those sources like a fish needs the water to live
Wuby986 said:
I wish but it doesn't
we need those sources like a fish needs the water to live
Click to expand...
Click to collapse
Oh well, soon. I think the first S4 official 4.4.2 rom is supposed to be out by the end of this month based on that roadmap from before so we should get it soon
erid2thed said:
ext sd card does work, its just at a different path - i posted the path in the leak'ed rom's thread (dbkat or something like that).
Click to expand...
Click to collapse
You mean the platform.xml?
Wuby986 said:
You mean the platform.xml?
Click to expand...
Click to collapse
no
the card wasnt at /extSDcard but was at
mnt/media_rw/extsdcard or something like that - i dont remember the exact path, but I did post it in the past...
For those who cant "find" their external sd card
have a look here ==>
/mnt/media_rw/extSdCard
Thread cleaned
Save the inciting drama for G+ posts and OFF XDA
If you have code to share please do without adding that to it
Thank you for your cooperation
Friendly Neighborhood Senior Moderator