Develop Bugs

Can we work this into our kernels?

http://www.pcworld.com/businesscent...x_kernel_patch_delivers_huge_speed_boost.html
Could that patch be used on android kernels?
I believe this is development but if not move it.
I figured this article was interesting enough to share and maybe get it into our kernels.

im not a programmer but this sounds pretty amazing what the guy did...ill have to give it a try on my linux computer. also, did anyone read this article as well "http://www.pcworld.com/businesscenter/article/209419/88_highrisk_defects_found_in_android_kernel.html"

I'm really hoping this mixed with the source available for the new stock kernel will produce a ridiculous kernel soon let's keep our fingers crossed
Sent from my Incredible using XDA App

you can do that with 2 commands and 4 lines
http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html

fader01 said:
you can do that with 2 commands and 4 lines
http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html
Click to expand...
Click to collapse
fader - have you tried this and gotten it to work? And if so, do you notice a difference?

Folks over at cm have tried it and don't think it's worth merging into the kernel just yet.
http://review.cyanogenmod.com/#change,417

Reading Steve Kondik's comments convinces me that this patch is not beneficial, due to the way the Android OS works.

Well apparently it is working better now and they have had improvements of over 15% so far. I think it would definitely be beneficial once it is perfected, to work this into our own kernels as well.

[Q] AOSP samsung t989 compile?

Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?

jahrule said:
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
Click to expand...
Click to collapse
You should do it so that we get AOSP rom

jim93 said:
You should do it so that we get AOSP rom
Click to expand...
Click to collapse
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5

Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
It is cool. And yes i would love to do it. With my experience with linux this would be no biggie, but android i have no idea. I think that if it was possible surely someone would have made a flawless 98% AOSP rom with 2% samsung parts....... right?

Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Csb are u done tryna be a mod? Cause reading back to your comment you didn't really contribute anything useful to his question either.
Now as for the question also apks cannot simply be installed on a touchwiz room the framework for both of these is pretty different you have to actually change code and port it over can't simply uninstall =(
Sent from my SGH-T989 using XDA

lilz4life said:
Csb are u done tryna be a mod? Cause reading back to your comment you didn't really contribute anything useful to his question either.
Now as for the question also apks cannot simply be installed on a touchwiz room the framework for both of these is pretty different you have to actually change code and port it over can't simply uninstall =(
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
You did not answer my question at all.

Then I don't u derstand ur question.
Sent from my SGH-T989 using XDA

Okay, it is very difficult to make an AOSP ROM with no device tree. That's why we have barely any 100% working. Remember, if you take kernel apart, you will find yourself with many, many files. You need to look through them all and link all the files. If those linked files don't work, then maybe you have to add some. If it still doesn't work, you will need to rework the drivers/firmwares. It is a difficult process. You also need to link all kernel/ROM together. *APK's HAS NOTHING TO DO WITH THIS PORTING PROCESS*

jahrule said:
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
Click to expand...
Click to collapse
Apparently you have never worked with source and/or compiled from... there are plenty of reasons why that can't happen. Main reason there is no device tree with proper source.
:: DARKSIDE ::

thederekjay said:
Apparently you have never worked with source and/or compiled from... there are plenty of reasons why that can't happen. Main reason there is no device tree with proper source.
:: DARKSIDE ::
Click to expand...
Click to collapse
I only use linux for the past 5 years i sure the hell have compiled and worked with source. I just never had to compile for anything other than x86(_64) cpu before aka no toolchaining.

Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
This is among the useful response for the original question. I was just encouraging him to go try it that is the best way form him to figure out why its not that simple.
This question has been asked before and I have seen how people have responded with different answers of this question. Whenever this question has been responded with technical reasons then it just ends up being followed by a question of why cant you do "A" even though "A" is based on not knowing another technical reason. The problem is the real satisfactory answer involves knowing alot of the basics which would have precluded you from asking the question in the first place.
Asking this question is like ends up like the following
"A: Why cant you fish with potato bits as bait?"
"B: well fishes dont like to eat potatoes"
"A: potato is food though,Why dont they like food"
It has been suggested before so clearly if someone knew how to do it they would have done it. The best thing at this stage is to try it.

alphadog32 said:
Okay, it is very difficult to make an AOSP ROM with no device tree. That's why we have barely any 100% working. Remember, if you take kernel apart, you will find yourself with many, many files. You need to look through them all and link all the files. If those linked files don't work, then maybe you have to add some. If it still doesn't work, you will need to rework the drivers/firmwares. It is a difficult process. You also need to link all kernel/ROM together. *APK's HAS NOTHING TO DO WITH THIS PORTING PROCESS*
Click to expand...
Click to collapse
Yea.. I was not implying that we grab APKs from some random AOSP build and copy on top of some working stock ROM. My question more is that I see on samsungs opensource site they give us kernel source for the t989 (have not looked at it yet) and then they gave us some build files to copy over and overwrite the build environment for AOSP which I did and built (currently trying to figure out how to use the *.img files), but shouldn't that give us a ~90% AOSP build? That or I am completely not understanding the README file from samsung.

jim93 said:
This is among the useful response for the original question. I was just encouraging him to go try it that is the best way form him to figure out why its not that simple.
This question has been asked before and I have seen how people have responded with different answers of this question. Whenever this question has been responded with technical reasons then it just ends up being followed by a question of why cant you do "A" even though "A" is based on not knowing another technical reason. The problem is the real satisfactory answer involves knowing alot of the basics which would have precluded you from asking the question in the first place.
Asking this question is like ends up like the following
"A: Why cant you fish with potato bits as bait?"
"B: well fishes dont like to eat potatoes"
"A: potato is food though,Why dont they like food"
Click to expand...
Click to collapse
I think he was trying to say if you don't want to spend the time explaining the details because you make some asumptions about people and their posts whom you have never met... then it is best you remain silent rather than giving some smart remark as an answer.

jahrule said:
I think he was trying to say if you don't want to spend the time explaining the details because you make some asumptions about people and their posts whom you have never met... then it is best you remain silent rather than giving some smart remark as an answer.
Click to expand...
Click to collapse
I wasnt giving you a smart remarks just pointing out that at this point it is best to just try it because nobody knows all the exact steps because nobody has done it for this device.
You are left seeking genera android kernel advice which ->
If you run into trouble with technical details go here http://forum.xda-developers.com/forumdisplay.php?f=565 since it is a better place to ask questions about using img files than in the same forum where people ask "how do I install custom rom" even the themer section is a better place.

jim93 said:
I wasnt giving you a smart remarks just pointing out that at this point it is best to just try it because nobody knows all the exact steps because nobody has done it for this device.
You are left seeking genera android kernel advice which ->
If you run into trouble with technical details go here http://forum.xda-developers.com/forumdisplay.php?f=565 since it is a better place to ask questions about using img files than in the same forum where people ask "how do I install custom rom" even the themer section is a better place.
Click to expand...
Click to collapse
I was not saying you were being a smart %^& just saying what I think dude was saying. In fact because of your comment I went got the source from samsung and repo synced AOSP and compiled it and have been playing around since just a little stuck now. My question was for more a technical reason. I understand now that we don't have a device tree for the t989 that works flawlessly... at least thats what i get from alpha and darkside. Now my question more is what the heck is the use of the source from samsung then?

jahrule said:
I was not saying you were being a smart %^& just saying what I think dude was saying. In fact because of your comment I went got the source from samsung and repo synced AOSP and compiled it and have been playing around since just a little stuck now. My question was for more a technical reason. I understand now that we don't have a device tree for the t989 that works flawlessly... at least thats what i get from alpha and darkside. Now my question more is what the heck is the use of the source from samsung then?
Click to expand...
Click to collapse
You can actually modify the Kernel it just takes work. For example if for some reason either the t989 or skyrockets ICS kernel was open sourced there would be a rotation fix so quick for the one with broken rotation.
Samsung just throws the source they finished out there but doesnt really provide or I think care to provide any work towards AOSP builds.

Check out this thread.

rynstphn said:
Check out this thread.
Click to expand...
Click to collapse
Hes asking about compiling Kernel from source I think

jim93 said:
Hes asking about compiling Kernel from source I think
Click to expand...
Click to collapse
No i am talking about the userland
Sent from my SGH-T989 using XDA

rynstphn said:
Check out this thread.
Click to expand...
Click to collapse
Yea thats cool and all but i am more intetested in GB. There is sone source that samsung gives us which i thought is the device tree for this phone... So in essence what i am asking is: what is the source that samsung provides and what use is it? I am aware of the kernel source already i am refering to the other package.
Sent from my SGH-T989 using XDA

[Q] Frame Drops, Not at All like "Butter"

So, normally help is plentiful on the Nexus S forums and I thought that here would be even better due to the devices popularity.
So far no matter where what or who the post is for or at, I have gotten no help from this community in any threads, for any issues I have encountered: I am not saying anything here to be a sarcastic idiot, but I am just hoping that I don't get 2 million people saying "WRONG THREAD IDIOT" and then not helping me or telling me where it should be...
None the less, if there is a good soul willing to help I am currently (and always) on the latest CM10 nightly build. My problem is that regardless of which version, or whatever I do, after about 4~ hours of the phone being on (used or not) it becomes very very.... low frame-y. Normally when the phone first re-boots it is smooth as butter and excellent, much like my old Nexus S yet unlike my Nexus S, it then begins to get worse as each hour passes.
It does NOT get slow.... apps take the same amount of time to load, and the phone feels as quick, yet the problem is it looks as if it is running at 5 frames a second. (This happens no matter the build and regardless of what is flashed with the ROM, but often times all I flash on top is just the GAPPS) This problem never existed on my older phones, and I really wish I could get some help for it.
Thanks guys, Eric.

I don't run that ROM so no idea if it would help but have you tried another kernel? Or tried changing governor's or scheduler
Sent from my SGH-I747 using Tapatalk 2

jasvncnt1 said:
I don't run that ROM so no idea if it would help but have you tried another kernel? Or tried changing governor's or scheduler
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I have tried other kernels and same thing happens sadly. I will give the performance schedule a try though.

Damn. Sorry. You have these issues even after a full wipe?
Sent from my SGH-I747 using Tapatalk 2

LGIQEXPO said:
So, normally help is plentiful on the Nexus S forums and I thought that here would be even better due to the devices popularity.
So far no matter where what or who the post is for or at, I have gotten no help from this community in any threads, for any issues I have encountered: I am not saying anything here to be a sarcastic idiot, but I am just hoping that I don't get 2 million people saying "WRONG THREAD IDIOT" and then not helping me or telling me where it should be...
None the less, if there is a good soul willing to help I am currently (and always) on the latest CM10 nightly build. My problem is that regardless of which version, or whatever I do, after about 4~ hours of the phone being on (used or not) it becomes very very.... low frame-y. Normally when the phone first re-boots it is smooth as butter and excellent, much like my old Nexus S yet unlike my Nexus S, it then begins to get worse as each hour passes.
It does NOT get slow.... apps take the same amount of time to load, and the phone feels as quick, yet the problem is it looks as if it is running at 5 frames a second. (This happens no matter the build and regardless of what is flashed with the ROM, but often times all I flash on top is just the GAPPS) This problem never existed on my older phones, and I really wish I could get some help for it.
Thanks guys, Eric.
Click to expand...
Click to collapse
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread

zelendel said:
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread
Click to expand...
Click to collapse
Nightlies are Alpha builds, yes. But how come my single core 1ghz Nexus S handles them nicer then my brand new dual core S3.
Also, This section on the forums is the "Q&A, Help & Troubleshooting" section is it not? In the equal forum over for the Nexus S, I got help from people as busy as the ROM makers them self. Here, barely even random people come on unless it is to say that I posted in the wrong section. As for a log cat, most every issue I have ever had ever with software has been resolved by something very simply, and only twice in my life was a log cat needed. Of those two times a log cat did not help in fixing the problem I had.
Man, I don't mean to sound mad here this is just my honest experience so far. I am very used to coming to XDA with a problem and leaving with the solution I guess. That and well I am a tad mad my phone is doing this. So please, don't take offense.

jasvncnt1 said:
Damn. Sorry. You have these issues even after a full wipe?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yes I do, I also tried the stable releases of CM and the same problem persists sadly.

zelendel said:
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread
Click to expand...
Click to collapse
Nice to see you here Zel!
LGIQEXPO said:
Nightlies are Alpha builds, yes. But how come my single core 1ghz Nexus S handles them nicer then my brand new dual core S3.
Also, This section on the forums is the "Q&A, Help & Troubleshooting" section is it not? In the equal forum over for the Nexus S, I got help from people as busy as the ROM makers them self. Here, barely even random people come on unless it is to say that I posted in the wrong section. As for a log cat, most every issue I have ever had ever with software has been resolved by something very simply, and only twice in my life was a log cat needed. Of those two times a log cat did not help in fixing the problem I had.
Man, I don't mean to sound mad here this is just my honest experience so far. I am very used to coming to XDA with a problem and leaving with the solution I guess. That and well I am a tad mad my phone is doing this. So please, don't take offense.
Click to expand...
Click to collapse
The Nexus S will work better in SOME situations because those that build CM for it have ALL the needed drivers and such since it is a NATIVE ASOP firmware. The problems with any other device (specifically Samsung decices) is that Samsung doesn't share MANY of the hardware drivers and such for important things. So those that build for Samsung devices have to try and tweak things differently to make them work. That is why CM has nightly builds, sometimes with minor advancements in their tweaking and other times major advances. It takes the devs longer to work it out things.
Sent from my SAMSUNG-SGH-I747 using xda premium

As stated above. The nexus hardware was made to work with the open source files and drivers of AOSP. As OEM branded devices have their own closed sourced drivers. With the open source ones work? Yes but not as well.
Wayne Tech S-III

zelendel said:
As stated above. The nexus hardware was made to work with the open source files and drivers of AOSP. As OEM branded devices have their own closed sourced drivers. With the open source ones work? Yes but not as well.
Wayne Tech S-III
Click to expand...
Click to collapse
I see. That makes more sense. So these drivers can't be brought over to other stock builds I guess?

LGIQEXPO said:
I see. That makes more sense. So these drivers can't be brought over to other stock builds I guess?
Click to expand...
Click to collapse
No because the driver rely on other files that only work with files of the same type. So OEM drivers and files or OEM files and drivers.
Wayne Tech S-III

[Q] Chameleon OS

grabbed this and put it on the note1 for my girlfriend, she really likes it
have to admit it looks pretty slick runs well too
I wish I could get it running for us. there looking for people to run it
http://forums.chameleonos.org/threads/device-maintainers-wanted.66/
any takers ?

The tablet UI looks awesome....
not really diggin the phone look from what i saw.

This looks HOT...I'm a fiend for the status bar

Yup can't wait for it to show up for us
Sent from my GT-N7105 using xda app-developers app

It's out for Verizon note 2 and beans said he will port for us soon.
Sent from my GT-N7105 using Tapatalk 2

yes !!!
I saw it for Verizon, was hoping it was a matter of time till it got here WOOT !

anyone sniff this around yet ?

well im going to give it a go and try to port it for our rom.
first time for everything

stuck on boot will play around with it more

Where is this? In Verizon? Do you need someone to just make a quick port for us? I can do it
---------- Post added at 01:59 AM ---------- Previous post was at 01:58 AM ----------
wuelfman said:
well im going to give it a go and try to port it for our rom.
first time for everything
Click to expand...
Click to collapse
Hey bro..if you need any help let me know..

www.chameleonos.org/downloads.php
Got it from here
They dont support porting I was gonna trying building from source. Might be to much for me though
Sent from my SGH-T889 using xda app-developers app

wuelfman said:
www.chameleonos.org/downloads.php
Got it from here
They dont support porting I was gonna trying building from source. Might be to much for me though
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yeh am trying to contact someone from there and there not responding back to my mail even mailed beans ? Im trying to see if anyone has started this or get permission, or see if beans is gonna port?

wish777 said:
Yeh am trying to contact someone from there and there not responding back to my mail even mailed beans ? Im trying to see if anyone has started this or get permission, or see if beans is gonna port?
Click to expand...
Click to collapse
this is from there site
"We want ChameleonOS to run on as many devices as possible and to do this we need help from the community. We're looking for those of you interested in being a device maintainer for devices we will support officially. For us to consider a device to be officially supported it must be able to be built using all of our projects found in the ChameleonOS repo manifest. Devices that require one or more stock projects to be removed and replaced by a modified version that allows the device to function correctly will interfere with our current build system. If this is the case, you are more than welcome to maintain your own unofficial builds
Since we originally based ChameleonOS off of CyanogenMod, any device that has official support for CM 10.1 will be easy to convert so that it builds for ChameleonOS. We'll be putting together an easy to follow guide on how to create the necessary projects to be merged into ChameleonOS in order to get your device into our system. In the mean time let me go over some of the requirements we have for individuals interested in being a device maintainer.
1.Familiarity with repo and git
2.Familiarity with the android build system and building a ROM from source code.
3.Know how to use gerrit code review and be able to submit patches to http://review.chameleonos.org
4.Able to debug, troubleshoot, and fix build issues.
5.Willing to keep all projects related to your device up to date and test new changes to verify everything is working as intended.
If you have a device that meets our requirements and you are willing and able to be a maintainer for a device please contact me 0xd34d(at)chameleonos[dot]org. Make sure to provide a couple of references to projects or work you have done that relates to android development. Some gerrit commits are always nice as well as links to threads for ROMs you have worked on. Please don't include any references to ROMs you may have ported. I've worked on ports myself but I don't consider the work done on a port comparable to working on a ROM from source.
Thanks in advance to all those that contact me!
"

I think this is what you might be looking for:
http://forums.chameleonos.org/threads/4-2-2-chameleonos-chaos-unofficialy-offical-4-8.157/

actually looks pretty cool. Any word on how well it runs? Battery life, etc.?

Traqic said:
actually looks pretty cool. Any word on how well it runs? Battery life, etc.?
Click to expand...
Click to collapse
Faustous said:
I think this is what you might be looking for:
http://forums.chameleonos.org/threads/4-2-2-chameleonos-chaos-unofficialy-offical-4-8.157/
Click to expand...
Click to collapse
yes it is for note 2 but for Verizon not sure how it would run ( not taking any chances of ruining my note lol

I got that but I mean if anyone tried it. Perfectly capable of doing a search

[Q] Build CM (CyanogenMod) for the hltetmo

Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht

gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
It looks like it's progress or at least people are tinkering around with it. However, you would need a full tree for the device if you wanted to build it from source, know enough to get your own tree, or be able to fork from other device tree's to get something going. The new Nexus has the same chip so that may make things quicker with getting a full working device tree. I'm just quoting based on my own understanding of things, so please correct me if I'm wrong.

I've been wanting to know the same. I've built AOSP ROMs before (namely AOKP for my Note 1 pulling from CM's device tree) and would do the same if the files were available for the Note 3. A few devs have teased the community with screenshots, but until they post their code a tease and a cruel joke is all that it is. I really wish these devs would put their source code up even if it is incomplete and let the community at large get this thing in gear since obviously they can't do it fast enough single-handedly. Holding back code until it's "ready" defeats the entire purpose of open source development in the first place! We have the kernel but no one has a full device tree out yet, only a limited one for recovery purposes (mainly the TeamWin one from TWRP).

Any updates on cm10 or cm11 for the note 3
Sent from my SM-N900T

Within hours of any (usable) device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.

CrashTestDroid said:
Within hours of any device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.
Click to expand...
Click to collapse
Sooo... When's this party begin? :angel::fingers-crossed:

Can't wait for this
Sent from my SM-N900T using Tapatalk

Me neither even got rid of my note and went with n5 cause I couldn't wait but im back tk the beast just need cm
Sent from my SM-N900T

Ker~Man said:
Sooo... When's this party begin? :angel::fingers-crossed:
Click to expand...
Click to collapse
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom

gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
Its getting real close. I imagine some other stuff is needed like qcom hardware updates and stuff. I'd give it another few weeks or so. BUT I imagine it'll be available soon.

I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.

CrashTestDroid said:
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom
Click to expand...
Click to collapse
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
gakio12 said:
I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.
Click to expand...
Click to collapse
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!

What blobs do you need? I thought blobs had to be extracted from the TW stock ROM. GPU blobs should be able to come from any other S800 device right (like the Nexus 5)?
Sent from my SM-N900T using xda app-developers app

geekcentercreations said:
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!
Click to expand...
Click to collapse
I'd be more than happy to lend a hand.

ProTekk said:
I'd be more than happy to lend a hand.
Click to expand...
Click to collapse
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?

idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
There's enough on GitHub right now for a starting point. I've just started to poke around this morning so I can't say much. Tbh, I've been fairly content with TouchWiz so that's been one reason I haven't had a strong interest in working on AOSP

idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app

Here is the most likely furthest along tree for anyone.
https://github.com/utkanos/android_device_samsung_hltetmo
It just seems like we might not see stuff on this device. Looking back on this thread people talked like it would be released in a week but I think it's going to be a lot longer than that.

idtheftvictim said:
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
That stuff is 2 months old. Nothing in two months? Man...no progress
Sent from my SM-N900T using xda app-developers app

I've never seen a device of this caliber take this long to receive an AOSP ROM! Wish I knew how guys, I'm tired of the TW ROMS, need some action in this forum already