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
Related
why couldn't we just develop an android base rom and then add the files for each type of phone/device separately. kinda like having a flavor of linux and just adding the drivers for your machine to the one you like ...I don't know if its possible ...but it really would make things a lot easier IMO
cm10.zip+SGS3.zip(drivers+kernel)=sgs3Rom
cm10.zip+SGS2.zip(drivers+kernel)=sgs2Rom
AOKP.zip+SGS3.zip(drivers+kernel)=sgs3Rom
and so on......
Probably bc not every manufacturer is so generous with hard ware and kernel source it'd be difficult to have universal like Roms it was tried I believe I forget which device possibly the us s3 or I'm just flat out wrong still a great idea though
Sent from my SPH-L710 using xda premium
ks2332 said:
Probably bc not every manufacturer is so generous with hard ware and kernel source it'd be difficult to have universal like Roms it was tried I believe I forget which device possibly the us s3 or I'm just flat out wrong still a great idea though
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I got the idea today as i was trying out windows 8 (lasted about an hour btw) ....if we can put windows/linux/android/chromeos/osx86 on just about anything ....this really shouldn't be that hard ....at least with the devices that we already have all this for ...
If that was possible what's stopping people from building a custom phone like they do for computers
Sent from my SPH-L710 using xda premium
The problem is that with all the different manufacturers and different versions of Android. They also use different file systems and file paths. Also the addition of the different system partitions doesn't help this issue at all. As was said earlier, if windows 8 was ported, it may be possible.
Sent from my SPH-L710 using Tapatalk 2
RedXXII said:
The problem is that with all the different manufacturers and different versions of Android. They also use different file systems and file paths. Also the addition of the different system partitions doesn't help this issue at all. As was said earlier, if windows 8 was ported, it may be possible.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Its very sad then....I guess this is one of the reasons android is so fragmented..
xlinth said:
Its very sad then....I guess this is one of the reasons android is so fragmented..
Click to expand...
Click to collapse
Yeah google only lays the framework but doesn't seek to enforce a standard of implementation. Curiously allot of PC Linux strongly adheres to the industry and often source standards..... example x11
Sent from my SPH-L710 using Tapatalk 2
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?
UPDATE: Jeffakajeff has an alpha out, see his post, reproduced here:
jeffakajeff said:
I got it....uploading now!
Sent from my SAMSUNG-SGH-T989 using xda premium
http://www.jeffreygabbard.com/cm-10.1-20130117-UNOFFICIAL-hercules.zip
Apn is empty, no service, did not try to input.
wifi works
bluetooth does not work, I will fix later, I think I know why
Not sure what else is working or not working, but so far it runs great.
I will create a github tomorrow as soon as I can, getting late though.
I will also give proper thanks for all the sources tomorrow.
I flashed straight over a nightly, I did not do a complete wipe and install, feel free to try.
Click to expand...
Click to collapse
Hello XDA'ers,
Its been a while, and I've been busy studying for the bar exam and looking for a job. Nevertheless, I decided to take a stab at compiling 4.2 for our device. Right now ADB is recognized, but there is no display output. I have to get back to studying, but please feel free to use this in any way you believe will help.
REMEMBER THIS IS NOT FUNCTIONAL, DEVS and ASPIRING DEVS ONLY
UPDATE Source:
https://github.com/abematthew/lawyermod
LINK http://sourceforge.net/projects/romchicago/files/JB/full_hercules-ota-eng.abe.zip/download
1.1.13-Added some suggested edits
Evervolv Tree Hack:
http://sourceforge.net/projects/romchicago/files/JBhttp://sourceforge.net/projects/romchicago/files/JB//
LawStud3nt said:
Hello XDA'ers,
Its been a while, and I've been busy studying for the bar exam and looking for a job. Nevertheless, I decided to take a stab at compiling 4.2 for our device. Right now ADB is recognized, but there is no display output. I have to get back to studying, but please feel free to use this in any way you believe will help.
REMEMBER THIS IS NOT FUNCTIONAL, DEVS and ASPIRING DEVS ONLY
LINK http://sourceforge.net/projects/romchicago/files/JB/full_hercules_debug-ota-eng.abe.zip/download
Click to expand...
Click to collapse
Sweet!!! Hope someone can Check it out!!!!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I'll take a look at it, thanks. Do you have a GitHub source for it?
Edit: If you guys want me to try to get a booting CM10.1 build, then can someone please pull a logcat for me through ADB?
Sent from my SGH-T989 using xda premium
Step Closer!..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
:good:LOL Android you are all over the place:good:
LawStud3nt said:
Hello XDA'ers,
Its been a while, and I've been busy studying for the bar exam and looking for a job. Nevertheless, I decided to take a stab at compiling 4.2 for our device. Right now ADB is recognized, but there is no display output. I have to get back to studying, but please feel free to use this in any way you believe will help.
REMEMBER THIS IS NOT FUNCTIONAL, DEVS and ASPIRING DEVS ONLY
LINK http://sourceforge.net/projects/romchicago/files/JB/full_hercules_debug-ota-eng.abe.zip/download
Click to expand...
Click to collapse
Did you use the new Sk8witskil recovery that i ported from the skyrocket? it was meant for use with Cm10.1 also,
is this added to BoardConfigcommon.mk?
BOARD_USES_QCOM_HARDWARE := true
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Will definEtly take a look. Thanks man.
Tmogalaxys2 said:
Will definEtly take a look. Thanks man.
Click to expand...
Click to collapse
lol can someone setup a github with the coding lol, i would love to fork this to my git and play around with it
ayysir said:
lol can someone setup a github with the coding lol, i would love to fork this to my git and play around with it
Click to expand...
Click to collapse
Once I get home, I'll try setting up a GitHub.
Sent from my SGH-T989 using xda premium
blackwing182 said:
Did you use the new Sk8witskil recovery that i ported from the skyrocket? it was meant for use with Cm10.1 also,
is this added to BoardConfigcommon.mk?
BOARD_USES_QCOM_HARDWARE := true
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Yes, it is.
I set up a GitHub for it: https://github.com/xdaandroid88/CM101Dev
Somebody else please add the files and stuff. I just did the easy part .
android88 said:
I set up a GitHub for it: https://github.com/xdaandroid88/CM101Dev
Somebody else please add the files and stuff. I just did the easy part .
Click to expand...
Click to collapse
Sweet!! Great Job!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
LawStud3nt said:
Yes, it is.
Click to expand...
Click to collapse
did you try something with legacy? msm8660 are now in thta legacy term, ill see what i can find, cuuz our jb blobs should work for 4.2, that multi user thing kill us all!
edit: take a look at this
https://github.com/CyanogenMod/android_device_samsung_qcom-common
this needs to be re factored
blackwing182 said:
did you try something with legacy? msm8660 are now in thta legacy term, ill see what i can find, cuuz our jb blobs should work for 4.2, that multi user thing kill us all!
edit: take a look at this
https://github.com/CyanogenMod/android_device_samsung_qcom-common
this needs to be re factored
Click to expand...
Click to collapse
Added, but still no boot. You can DL in OP
the problem is that everything 4.2 related on aosp, cm, and on code aurora for qualcomm SoCs is all based on the msm8960. I played around a bit before I went out of town for the last 2 weeks. I posted some info that might be useful in the Skyrocket forums here:
http://forum.xda-developers.com/showthread.php?t=1990891
I don't know if the issue is with the device repos, the kernel, or both, but as it is now, none of the msm8660 drivers/libs are getting compiled during the build (display, audio, bluetooth, among other stuff). Adding them in from a cm10.0 build also did not work. I'm also not sure if the current msm8660-common device repo or msm8660-common kernel repo is compatible with the current implementation of "ion" rather than pmem and ashmem. My best guess is that the device_samsung_msm8660-common, device_samsung_celox-common, device_samsung_skyrocket, and device_samsung_hercules all need some significant refactoring/hacking to get it inline with 4.2 and that's beyond my knowledge in this area. I also dont know if it might be possible to incorporate the device_qcom-common repo and trim redundant/conflicting code in those other repos, but like I was saying before, that repo currently just supports the msm8960.
m4570d0n said:
the problem is that everything 4.2 related on aosp, cm, and on code aurora for qualcomm SoCs is all based on the msm8960. I played around a bit before I went out of town for the last 2 weeks. I posted some info that might be useful in the Skyrocket forums here:
http://forum.xda-developers.com/showthread.php?t=1990891
I don't know if the issue is with the device repos, the kernel, or both, but as it is now, none of the msm8660 drivers/libs are getting compiled during the build (display, audio, bluetooth, among other stuff). Adding them in from a cm10.0 build also did not work. I'm also not sure if the current msm8660-common device repo or msm8660-common kernel repo is compatible with the current implementation of "ion" rather than pmem and ashmem. My best guess is that the device_samsung_msm8660-common, device_samsung_celox-common, device_samsung_skyrocket, and device_samsung_hercules all need some significant refactoring/hacking to get it inline with 4.2 and that's beyond my knowledge in this area. I also dont know if it might be possible to incorporate the device_qcom-common repo and trim redundant/conflicting code in those other repos, but like I was saying before, that repo currently just supports the msm8960.
Click to expand...
Click to collapse
Thanks, that is just the information I needed. I should be able to dig in again on the weekend.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I tried hacking the evervolv tree, the HTC amaze and HP touchpad are booting currently.
It compiles but does not boot.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
So this is kind of a pain in the ass...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Sucks :/
I'd wanted to give a shot at trying to build this, but I have not much knowledge and I have no idea how to do it lol.
Also, does logcat work at all?
LawStud3nt said:
So this is kind of a pain in the ass...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
What's the status now bro
Im working on porting CyanogenMod to the T-Mobile Samsung Galaxy Note 3.
I have the CM source code and I have been experimenting with all sorts of files and reading build and porting guides BUT to no avail.
Without the proper blobs, I have found this to be an impossible task.
Looking for a few people who are interested in giving me a hand doing this without the blobs.
^I had to clarify this just so everyone was on the same page.^
You can reach me here on XDA.
geekcentercreations said:
Im working on porting CyanogenMod to the T-Mobile Samsung Galaxy Note 3. I have the CM source code and I have been experimenting with all sorts of files and reading build and porting guides BUT to no avail. Looking for a few people who are interested in giving me a hand doing this.
You can reach me on twitter (nikkdotcom) or skype (nikolas_pereira1) or here on XDA.
Looking forward to some good teamwork!
Click to expand...
Click to collapse
sure count me in
the cm guys (behind closed doors) only have call mic not working , the rest is working, i figured with 4.4 the note3 development got halted , wanted to work on it about a month ago but was told "stuff will be shared once its working" ..
last i checked they had a kernel up .. no blobs list nothing .
DAGr8 said:
sure count me in
the cm guys (behind closed doors) only have call mic not working , the rest is working, i figured with 4.4 the note3 development got halted , wanted to work on it about a month ago but was told "stuff will be shared once its working" ..
last i checked they had a kernel up .. no blobs list nothing .
Click to expand...
Click to collapse
Get in touch with me on Skype or Twitter. Im working on this right now. My info is in the OP.
I cant wait to see progress
Sent from my SM-N900T
@geekcentercreations I added you.. What's your github? Gtalk would be better or irc. . When I'm around
Sent from my SM-N900W8 using XDA Premium 4 mobile app
You guys rock!
So glad to see some activity on this from community members! I would help, but have no computer available to me, nor the knowledge to even attempt this.
You guys are the best!
If you need testers, let me know. I LOVE messing with my phone!!
^^Same here. Will test any of it on my tmo note 3
Sent from my SM-N900T
After try many edit rom of Note 3, I prefer to original rom by Samsung for stablility.
Sent from my Note 3 using Tapatalk
iamwrong said:
After try many edit rom of Note 3, I prefer to original rom by Samsung for stablility.
Sent from my Note 3 using Tapatalk
Click to expand...
Click to collapse
OK, then you keep using stock from Samsung.
MANY people are waiting for CM10/11 though. I just want to be able to unleash this phones true potential.
I'm up for building and testing. I'd really love to get OmniROM running on the Note 3 so if you have a device tree repository set I'd be interested in it.
Sent from my SM-N900T using xda app-developers app
CalcProgrammer1 said:
I'm up for building and testing. I'd really love to get OmniROM running on the Note 3 so if you have a device tree repository set I'd be interested in it.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Check This Out. https://github.com/utkanos/android_device_samsung_hltetmo
Also do a general search on github for "android_device_samsung_hltetmo" (without quotes of course)
My github is here. Has some files in there but not too much. Would love some more people to contribute.
https://github.com/nikkdotcom/android_device_samsung_hltetmo
DAGr8 said:
@geekcentercreations I added you.. What's your github? Gtalk would be better or irc. . When I'm around
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
https://github.com/nikkdotcom/android_device_samsung_hltetmo
You won't find anything on git hub ... cm brought n3 development behind closed doors...
fun stuff.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
DAGr8 said:
You won't find anything on git hub ... cm brought n3 development behind closed doors...
fun stuff.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This new corporate sellout version of CyanogenMod sucks big time, throw all their community spirit out the window for the chance to profit off open source software. Sad state of affairs indeed, especially trying to lie and cheat devs into relicensing GPL software so they could sell it to third parties. What the heck CM team?
Sent from my SM-N900T using xda app-developers app
I was scared of this happening to the android root community. Things went from fun open community development to whatever the hell is going on now. I miss when it was like 7 people working the same type of rom for the same phone and having options. TOUCHWIZ SUUUUUUUUUUCKS. I'm dying for some aosp or aokp for this beast
nighthawk626 said:
I was scared of this happening to the android root community. Things went from fun open community development to whatever the hell is going on now. I miss when it was like 7 people working the same type of rom for the same phone and having options. TOUCHWIZ SUUUUUUUUUUCKS. I'm dying for some aosp or aokp for this beast
Click to expand...
Click to collapse
I really want Paranoid Android for this beast but CM is easier to build. Easier to build if I could figure it out that is
geekcentercreations said:
I really want Paranoid Android for this beast but CM is easier to build. Easier to build if I could figure it out that is
Click to expand...
Click to collapse
I'm with you on that, I need that halo back.
Sent from my SM-N900T using xda app-developers app
Actually omni pa pac aokp slim whatever rom type u prefer..
All we need is the proper blobs to be used .. The device tree from one rom to another don't differ much
That's the hard part .. cm will share once it works. That's for sure. .
Ofc we can hate on them for not sharing truth is if making this work was an intermediate level of difficulty we would already have aosp based on our phone ..
Sent from my SM-N900W8 using XDA Premium 4 mobile 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