Database Users

Nexus S Development 4G/GSM

Hello everyone. Allow me to introduce myself first off. I'm a long time xda member, an acs member (Android Creative Syndicate), a themer, and a developer. I originally started on the Samsung Moment, learned themes, and shortly after moved up to the Samsung Epic. I created quite a few themes for the Epic, and then began working with ACS devs testing and learning what they were doing for the ACS roms.
I've got some plans for my Nexus and hopefully everyone can benefit from it. My first missing piece upon buying the nexus was the widgets in the status bar ie bt, gps, wifi, etc. soon as I got my phone that was a high priority. I ported a theme immediately from the Epic so I could have my eye candy back while working on bigger and better projects. The theme is in Nexus Themes and Apps called H.R. Giger and can be found here: Thread. My second project, the Samsung Touchwiz Quick Panel port, which is also the same thing as the power control widgets on the Cyanogen Mod roms, is now mostly complete and can be found here: Thread. Also there is a subsequent thread that I turned into a guide on how I did the mod as well as actively answer questions to anyone looking to do the same for their roms located here: Thread. I say the mod is *mostly done because I would like to replace the auto rotation widget with the Wimax (4g) for us Sprint Users. The problem is Sprint has made the Wimax modular and placed it into an apk where it links itself into the settings menu, as well as the framework. The problem with this is I can't access the wimaxmanager inside the apk from the SystemUi.apk because of what seems to be a security issue. Most likely this was done intentionally by Sprint to protect their proprietary software, but I'm not 100% sure. I like to believe that we can get around it and get this working but it's def on the back burner now.
My current port is the TSM Lockscreen Parts. This mod allows you to go into settings, under the option for About Phone, there will be a new choice called Lockscreen Parts. From there you can choose between now 8 different Lockscreens. You can also turn the music controls on the different lock screens. I have the Mod 100% working with 3 of the lockscreens ported. I will have one more this afternoon and 4 more however long it takes.
I have released the Quick Panel mod to the public already since it's such a useful mod, but all of these things will be going into my rom which will include the quick panel, lockscreen chooser, and reboot options. The rom will be based on stock NS4G 2.3.4 GRJ22 AOSP build. There is absolutely, in my eyes, nothing wrong with the stock rom running on our Nexus. I feel adding as little code as possible to it to enable these features will send it over the top.
The reason for this thread is two fold. I would like to announce myself to the Nexus community for those coming from something other than the Epic and might not be familiar with my work, and to let any other developers out there what's on my plate if they care to take part in it or were planning on doing the same things. I hate to see someone start on the lockscreen today as much work as it is, and I'm more than half way through. Also I wanted to reach out to the GSM devs, as all this work should transfer over to your phones very easily.
Future projects are already on the backburner including a new theme complete as Giger that takes over every aspec of the phone but this time instead of replace the GB theme, I plan to accent it. Porting over a slew of nice themes is in the works as well. Also I plan on working on getting most of the Transparent and Blacked out apps the Epic has available over to us as well. Anyone else, I know Mikeinid was planning on a transparent gtalk as well so feel free to post here upcoming plans and we can build mods together as one instead of each other doing the same thing.
I hope there are more people out there that will join me in working on the Nexus because the more options the better!. I get asked plenty of times why am I working on porting smali code for the Nexus when we have full source. I'm a reverse engineer by heart. I work backwards a hell of a lot better than forwards. After this rom is complete and I'm set up building NS4G code from source, (I'm mostly done getting set up for that as well) I plan on playing with java code and seeing what apps/mods I can build right into source so in the future I hope my releases will be in source code and anyone can add the code and build it right into their roms.
Sent from my Nexus S 4G using Tapatalk

Hope some devs will jump in. Great job dreamsforgotten. Big fan here
Uncle Jimmy says hello

Thanks for the support!
Sent from my Nexus S 4G using Tapatalk

Thanks for reminding me about the inverted gtalk I know how to do it now thanks to jatxwne, a themer from the OG droid.

Absolutely awesome post. I just got the nexus s 4G (coming from an EVO) and have been just getting a feel for these forums. I'm really happy to see a Sprint dev for the nexus s doing really exciting things. Thanks and I'll be really watching your stuff!!

Tuffgong4 said:
Absolutely awesome post. I just got the nexus s 4G (coming from an EVO) and have been just getting a feel for these forums. I'm really happy to see a Sprint dev for the nexus s doing really exciting things. Thanks and I'll be really watching your stuff!!
Click to expand...
Click to collapse
I've put in a majority of the last 48 hours on on the epic lockscreen and still don't boot. This one requires modding the framework.jar. Each time I logcat the boot I'm finding more methods not present in the aosp so I'm definitely incorporating some new features. Music controls already work but the epic lock is going to display the tw controls I'm guessing. Regardless the end if near hopefully tomorrow then I have the ***** the puzzle lock then its more framework additions for the muiu lock. A couple weeks away I'm betting
Sent from my Nexus S 4G using Tapatalk

dreams you are amazing. you already have my support (for what its worth..) and here is to hoping that you port puzzle lock to cm7 afterwards >.> or at the very least get nemith to include it

Cool, glad to see this stuff being ported. I am coming from the EVO and was used to so many devs working on themes, Roms and what not and the NS4G feels so bare. It's always nice to get new minds working on our device. You seem to know what you are doing and I can't wait to see your finished products. Thanks for the introduction.

I'm calling it quits for the night. Touchwiz files in this one require heavy modding of the smali. I have to add in tons of features not in. aosp and make it work together. I know most of what needed but this will take some time. Should be easier for the rest of the locks when I get our policy up to par with the sgs one.
Sent from my Nexus S 4G using Tapatalk

ICS Nightlys

Hi All
Seems to be a bit backward to not be able to post in the development section, but rules are rules I suppose.
I bought a Xoom a couple of months ago and put on Moray on a UK wifi Xoom. Very impressed and jumped onto ICS with the initial ICS release then played about with nightlys up to version twelve today.
OTG still not working for me, it crashes USB watcher OTG as well.
Music app does not get mentioned, but its terrible. Only small icons and no proper options ?
Camera and Mic were not tried as they are obviosly broken due to missing binaries.
It also seems backward to have widgets only on the apps page.
Battery options made the battery read zero, then made it disappear from the tray as well.
Browser does seem slicker, but back to Moray and its not a huge difference to be fair.
Have issues with various Apps. This makes sense as they still need to get up to speed with ICS. But it does concern me when people say its the best thing ever, when nothing can work as advertised. HW videos are hit and miss. I am also sure I read a while back that ICS would be all singing, why do I need a Ext mount app to write to an external card, same as OTG ? I thought that this would be part of the main build ?
So from my own personal experience, its a change, but until you have a full package with working apps, hardware, then I think people need to calm down with their plaudits for ICS.
I think I will leave the nightlys for a while, but it was great to try, and thanks for the guys putting the effort in making/updating these things.

I'm going to say this with as much respect as I can:
You have zero idea what the development section is about with statements like that.
Stick to stock software if you want a device that works as intended.
Development and custom roms always have caveats and pitfalls.
Thanks for stopping by!

Regarding not being able to post in dev section - it's for development only not questions and a lot of new users start new threads and ask a lot of questions! It makes sense the way it s.
You have to remember that these are alpha builds which are not supposed to be complete or fully working. A lot of devs wouldn't even put these out at this stage because of instability issues. But I am SOOO glad that the EOS team have decided to share these awesome ICS build with us because it may take weeks or even months to get to a full build release or an official Moto release. I know you aren't trying to bash the devs but I have to disagree with your opinions. I love ICS so far. It's fast, fluid and looks great.
Agreed with the widget option. Think the HC way was better but it's a minor issue compared to the speed improvements.
In essence though, I think if the full product is what you want you should stay away from alpha or even beta builds. Stick with full or official releases. Most people who test these roms understand this.
Sent from my Xoom using xda premium

aside from the camera and the mic i have had zero problems with anything i do on the xoom on a regular basis.
if it's an alpha build, it's a hell of an alpha build.
the only thing was it took me a bit to get all the gapps working and to the most current versions

Hi
Well my point was I don't have to be a Dev to know when things are not working. OTG is not working, and this is not a statement saying it has to, but merely a way of reporting it.
Nobody has mentioned the battery dissapears if you change the settings.
People seemed to be obsessed with Google Maps working, but since this is a great media player the bugs seem to be getting left out of the threads.
Now I know there is a lot missing, but why no OTG support built in ? Is this just a Motorola thing ?
I think there has to be a devils advocate here, everyone saying its fast is great, but if you are just using this as a browser, then its not a great indication about how good ICS is.
And to the chap who said I had no idea about Dev things, you are 100 % correct. But this is not aimed at anyone doing the nightlys, this is an ICS comparison. I am sure if Motorola release a version of ICS! Then it would get mentioned, how there are also some annoying new things not hardware or nightly release related. As I said the Music player is abysmal, the widgets is hidden away. The apps selector looks smaller, and some other little things.
So all I am trying to say is yes it seems faster, but since its only partly there, and we shrug when things don't work correctly, does not mean that is is the best thing ever. When we have a full version and all the binaries are working, then we will see the real speed ?

xoom68 said:
Hi
Well my point was I don't have to be a Dev to know when things are not working. OTG is not working, and this is not a statement saying it has to, but merely a way of reporting it.
Click to expand...
Click to collapse
I haven't tested it but others in the thread have and say it's working.
Nobody has mentioned the battery dissapears if you change the settings.
Click to expand...
Click to collapse
It's in the official bug tracker.
Now I know there is a lot missing, but why no OTG support built in ? Is this just a Motorola thing ?
Click to expand...
Click to collapse
At this point the ICS builds are all straight from source so not a moto thing but see above.
So all I am trying to say is yes it seems faster, but since its only partly there, and we shrug when things don't work correctly, does not mean that is is the best thing ever. When we have a full version and all the binaries are working, then we will see the real speed ?
Click to expand...
Click to collapse
That's all well and good but if that's the way you think then stay away from alpha and beta builds. If you are only interested in the full working product wait for official release.
Sent from my Xoom using xda premium

Worst thread ever.

Alpha build!

Thanks for replying.
I don't know what defines a working OTG, but with Moray I used USB Mount watcher and I mounted a 1tb HD no problem. I thought I would not need an app, but no joy. This time when I tried the App it says it was built in. But it hangs at any attempt to identify the HD. Another mount app sees the HD, but can't mount it.
The battery thing I just noticed in the bug tracker, but no one mentioned it in the thread.
No one mentions the poor ICS music player or widgets.
I just see people obsessed with calendar and Google maps ?
And to all saying Alpha Build....considering Motorola never added OTG support to HC, but the custom roms did. My point is who is to say they will add it to ICS. I thought it was supposed to be standard. If people have to Root their device to get OTG and towrite to External SD. We have not come that far forward. And in fact the threads I readprevious to buying a Xoom had people waiting months for updates, are people really expecting a Motorola Ics within the next 6 months. This alpha build will not get any better until there are binaries, soapart from a few settings tweaks, it will stay Alpha for a long time I reckon.
I understand you saying stick to stock, but the built in things to ICS are poorer in relation to HC, I suppose no one mentions things in case they appear to be rude, but I think its better if people know the negatives as well, as it just seems to be people with Ice Cream tinted glasses at the moment

xoom68 said:
I understand you saying stick to stock, but the built in things to ICS are poorer in relation to HC, I suppose no one mentions things in case they appear to be rude, but I think its better if people know the negatives as well, as it just seems to be people with Ice Cream tinted glasses at the moment
Click to expand...
Click to collapse
Again though, this is an alpha build so you cannot expect this to be fully working or all "built in" functions to be bug free.
If the current builds don't work for your daily needs that's fair enough, wait for a more complete build. But you cannot burn ICS on the strengths, or weaknesses, of an alpha build.
Sent from my Xoom using xda premium

Be happy that we are the only tablet that has a ICS build to be bug free enough to be a daily driver for a good portion of users.
(Wifi, GPU acceleration, netflix work perfectly, browser is very much improved)

I can't post in the development section either.
But a thread like this is just the place to boost my post count.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
Ten characters.

Honestly, all I can really say to this... one step at a time, one day at a time.
You, as well as others, must understand and respect the fact that the developers here are putting in their own free time and effort to bring us these ROMs and extras, at absolutely no cost to you, the user.
Trying to tear apart tons code that has already been written to troubleshoot, fix problems, and test is hugely tedious and very time consuming.
Right now, I suggest not trying to put the cart before the horse. Simple things like asethetics, minor functionality (I.e. OTG, etc.) that is not crucial to the operation of the device is going to have to wait.
Important parts, like 3G/4G radio functionality, Google apps, video playback - the essentials come first.
Truthfully, I would not waste my time reporting the smaller issues, we know that they are there. When the developers get the foundation built and stable enough to work with, THEN will they ask for help with bug reporting and suggestions and such. No need to overwhelm the developers at this stage of the game.
Just my 2 cents.

xxspark89xx said:
Honestly, all I can really say to this... one step at a time, one day at a time.
You, as well as others, must understand and respect the fact that the developers here are putting in their own free time and effort to bring us these ROMs and extras, at absolutely no cost to you, the user.
Trying to tear apart tons code that has already been written to troubleshoot, fix problems, and test is hugely tedious and very time consuming.
Right now, I suggest not trying to put the cart before the horse. Simple things like asethetics, minor functionality (I.e. OTG, etc.) that is not crucial to the operation of the device is going to have to wait.
Important parts, like 3G/4G radio functionality, Google apps, video playback - the essentials come first.
Truthfully, I would not waste my time reporting the smaller issues, we know that they are there. When the developers get the foundation built and stable enough to work with, THEN will they ask for help with bug reporting and suggestions and such. No need to overwhelm the developers at this stage of the game.
Just my 2 cents.
Click to expand...
Click to collapse
Thank you for the great work you are doing on this. I can see that it can be slow going but you seem to be making good progress.

CyanogenMod 9 Build Help

Ok Team, I am trying to build CyanogenMod 9 for the p6800 but I am running into errors when I run . build/envsetup.sh && brunch p6800 and cant get past this error. Please see attached.

u making a wifi version too ? (p6810)

this is all still new to me, let me get the 6800 working first then I will try a 6810 just not I do not have a 6810 to try it on

First make sure to resync, I just pushed a change that you need in order to build a working rom. Also, the target you are looking for is cm_p6800-userdebug (not cm_p6800).
Just warning you, you will have major artifacting and screen discoloration issues, since I never merged in the change to mostly get rid of them in the alpha 2 build. I need to get a build up and running on the i815 before I can look into this (because the i815 is the only working tab I have on me at the moment).

Thank you locerra everything is building out and I will see what I can do

I am SUPER excited about this tablet. I have virtually no development experience, but here's what I HAVE done:
1) Built an xml driven flash gallery (by franken-coding), but basically from scratch. Experimented with motion, orientation and gravity in AS2. Built a couple of rolling flash animations.
2) Designed four websites, so have basic html/css/xml/php pipleine understanding and implementation.
3) artist gone linux enthusiast: I'm willing to learn what I have to in order to reproduce the visual effect I'm imagining. Which brings me to the gTab 7.7......
If I can help in anyway, I'm down for looking through code, file compare, digging through directories, etc. I'm certainly willing to learn.m
There are a few apps i'd like to build just because they're not out there, but could be, so any knowledge that gets me more up close and personal with my tablet, I'm totally down.
Do you guys mind kind of cliff's noting your progress and obstacles as you go? Is this the thread to ask development questions when they're specifically in regards to how the build porting process works?

aletheus, I am very new to this, last time I coded for anything android was the G1. I have setup the build environment, java, adb git, pulled the CM9 git and with the help of locerra the git they had setup for the device, I am going to try and pull the ICS Proprietary Files for my next build. I have started a build but I am sure it will be very UN-stable so I may not post it yet. If you want to help in any way im always glad to have the extra help. Iocerra has the verizon model now and I don't know if it will be easy for him to code for the 6800 but I want to help as much as I can and try to get this up and going. I am off work the next few days so this is all im going to work on

Very cool. I am only working from the p6800 right now, no laptop, no desktop. Just the tablet. It's humbling. I have found to some extent, SDK's for many different languages can operate straight from android. For example, i've got "AIDE" installed and have just begun to even wrap my head around what android is doing, as far as functionality stacks and how they go about deciding a new build version.
I'm getting an iFaraday stylus (capacitive fabric instead of rubber---i keep ruining rubber styli because i draw ALOT)--and i'm getting the keyboard dock. So this will be alot more usable as a work station all around.
Can this thing run ubuntu with an hdmi out adapter?

Moved To General​
Please do not post question threads in the development section.​

original_ganjaman said:
Moved To General​
Please do not post question threads in the development section.​
Click to expand...
Click to collapse
Its a question within a development thread, if I'm off topic then reprimand me, but don't mive the wntire thread because of me.
Sent from my GT-P6800 using XDA Premium HD app

Looking For Tablet ROM With More Complete S-Pen Support

Hello. I have written an app that helps to improve the accuracy of the S-Pen. It works only on Note phones because Samsung has compiled some S-Pen device driver interfaces out of the tablet ROMs. It is not clear why they did this. I have asked Samsung but gotten no replies. I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). It seems that the tablets suffer from the same issues related to the S-Pen as do the phones and I have many people asking me to make my app work on their tablets. I cannot do so with the stock ROMs because of the missing interface files.
So I am wondering if there any non-stock ROMs in which the S-Pen is more fully supported. The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation. If anyone knows of any ROMs for the S-Pen equipped tablets that provide these interface files, I would appreciate knowing and may be able to direct some folks to using them.
Thanks

I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack

JSale said:
I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack
Click to expand...
Click to collapse
Jack, some replies to postings in the Note 8 section indicate that the two files are present on the stock ROM there. Interesting... I am downloading a dump of the 10.1 now to see if I can see anything. Thanks

Any progress on this? It looks quite promising in the note 8.0 forums.
Regards
Jack

whitedavidp said:
I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). ... The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation ...
Click to expand...
Click to collapse
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1

kcrudup said:
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1
Click to expand...
Click to collapse
Hello and thanks for responding/helping out. I am certainly no kernel programmer. But I have downloaded the kernel sources for a couple official Note devices/versions. I have been reading files located in kernel/drivers/input/touchscreen/wacom paying particular attention to the file wacom_i2c.c. I cannot help but note that some of the functions which appear to reference the driver i/o files that are missing are #def'ed out of certain devices - see line 837 #if defined(CONFIG_MACH_P4NOTE).
I have no idea if the Wacom devices used in the various Note models are the same (except for size) or are similar enough to be treated as the same by programs like mine. Heck, I am not even sure if Wacom devices are being used in all the Note models. So I am afraid I am not much in the way of technical help here.
What I do know is that some custom ROMs for Note I and II phones seem to have been created with drivers that DO support and create the needed driver i/o files but which lack the device settings and other mechanisms which actually take advantage of these i/o files. Basically, they do not offer a dominant hand setting nor do they seem to communicate to the Wacom device when an orientation change is detected. I have been able, through my app, to compensate for these lapses on those devices and thereby improve the SPen's accuracy.
I have had users wanting to get the same effect on Note tablets with my app. So I presume they are experiencing the same type of problem on their tablets that I experienced on my Note I phone that led me to get into all of this. But I know that my app cannot help them unless the i/o files are there.
I was surprised to hear, over in the Note 8 forum that the files do exist on those devices. I know from a tester that my app at least runs on the Note 8. But I don't know if it helps any since that tester was not seeing the problem my app is designed to fix. But I read here that the files are not on the larger Note tablets. I don't know why and have asked Samsung and get basically no answer. My underlying assumption is that the Wacom devices are basically the same but I cannot answer why Samsung treats them as different.
I am sure all of this doesn't help much. Sorry. All I would like to do is try to find a way to offer support to the tablet users who want it.
Cheers!

Try this kernel: http://goo.gl/OBJ4O (PM also sent).

kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Im going to quickly revert from baked to android revolution to test this
I will let you know what I think.
Regards
Jack

JSale said:
I'm going to quickly revert from baked to android revolution to test this
Click to expand...
Click to collapse
No, this is just a kernel- you won't have to change distributions to try this.

kcrudup said:
No, this is just a kernel- you won't have to change distributions to try this.
Click to expand...
Click to collapse
But baked is based on CyanogenMod, unless this kernel is compatible?

kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Sadly, I don't own one of these tablets (yet). But I have passed this on to a user who previously asked me (and got this thread rolling as a result). So perhaps he can check it out and try my app on it. If he does, I will certainly report back here. Thanks for your efforts.

JSale said:
But baked is based on CyanogenMod
Click to expand...
Click to collapse
Oh, then yeah- as I suspect CM won't have any of the SPen goodies. My bad.
In any case, let me know. It was a very trivial fix and didn't appear to break anything. I don't use the SPen much at all, but a quick test with SNote appears that everything still seems to work OK.
(But I did notice that the stock Samsung ROM (CMD2) does set these variables, which is unusual as these sysfs entries "shouldn't exist", but it seemed to (re)set them to default values. I wonder if this is used as part of a version check of some sort?)

Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack

JSale said:
Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack
Click to expand...
Click to collapse
Wow! Thanks for the testing and for the feedback on your results. This is quite interesting. I am not quite sure I can integrate this sort of thing into my app although it may be possible. The kernels for the Samsung devices I have looked at seem quite monolithic rather than modular. But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand. So perhaps. I would sure need help and direction. But it would be very cool indeed.

JSale said:
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked ROM?
Click to expand...
Click to collapse
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
whitedavidp said:
But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand.
Click to expand...
Click to collapse
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.

kcrudup said:
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.
Click to expand...
Click to collapse
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks

whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them?
Click to expand...
Click to collapse
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).

kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
Thanks very much once again!

whitedavidp said:
Thanks very much once again!
Click to expand...
Click to collapse
The app seems to work with this kernel :good:
kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
I really want to know what are the features of this kernel ... would i keep it or there are other ones that have this functionality right now?? OR could just this changes be added to the Stock kernel to only have Spen support .. as i dont want any OC or custom governers :good: :good:

whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks
Click to expand...
Click to collapse
May I ask you what application you are talking about?
@kcrudup Have you already decided to release your kernel in a separate thread or not?

[ROM][SM-T800] stock Deodexed FN8

[LSD] Proudly Present​Galaxy Tab S 10.5 Stock ROM Deodexed [Rooted]​
Code:
Bla bla your warranty is void and you know that :rolleyes: or is it?
*Screenshots are taken from a note 10.1 (2012 edition) but apps are from Tab-S!
For changelog go to post 2
For information go to post 3
*Stock Modified Boot.img
*Stock Kernel
*Deodexed
*Zipaligned
*Init.d support
*Busybox
*Unsecure Kernel
*More stuff i don't remember
*Knox Removed Partially [Not sure if its in kernel as well]
*SE Linux Enforcing [Kernel sources ins't out or?]
Install Instructions
Extract updater-script to desktop and edit the partition details
repack the zip and flash using CWM Recovery
Special Thanks to
@open1your1eyes0
Download
P.S If you succeeded downloading the torrent please feel free to upload it to a host, i don't have access to any good file hosting service

Changelog
v0.1
Initial relase once CWM is available please report

Feel free to use this package however you wan't to.
You can even improve it however you wan't to i don't mind. No credits are needed i'm just here for sharing

Can't wait to try this
Sent from my SM-T800 using Tapatalk

Thanks for this....BUT...custom recovery would be nice. Anyone working on it?

Patiently waiting for custom recovery! Look forward to trying this.

iMJets said:
Patiently waiting for custom recovery! Look forward to trying this.
Click to expand...
Click to collapse
Well I don't think anyone is working on it, so we are stuck with stock. I'm sure eventually we will, but Dev action on this thing is poor.

suzook said:
Well I don't think anyone is working on it, so we are stuck with stock. I'm sure eventually we will, but Dev action on this thing is poor.
Click to expand...
Click to collapse
Have you heard something? I never owned something that did not have cool stuff.

One of the problems facing the S model is that Samsung just came out with the Pro model and most of the people who wanted a tablet of this caliber already bought that. If there never had been a Pro model I feel confident we would be getting a lot more activity.
Anyway we already have root and at least the 8.4 guys have a kernel.

mitchellvii said:
One of the problems facing the S model is that Samsung just came out with the Pro model and most of the people who wanted a tablet of this caliber already bought that. If there never had been a Pro model I feel confident we would be getting a lot more activity.
Anyway we already have root and at least the 8.4 guys have a kernel.
Click to expand...
Click to collapse
Only reason we have root,is beanstown did us a favor. If he had a tab, We would have custom recovery and custom ROMs already. I really don't understand why people won't donate a device.

mitchellvii said:
One of the problems facing the S model is that Samsung just came out with the Pro model and most of the people who wanted a tablet of this caliber already bought that. If there never had been a Pro model I feel confident we would be getting a lot more activity.
Anyway we already have root and at least the 8.4 guys have a kernel.
Click to expand...
Click to collapse
indeed

suzook said:
Only reason we have root,is beanstown did us a favor. If he had a tab, We would have custom recovery and custom ROMs already. I really don't understand why people won't donate a device.
Click to expand...
Click to collapse
Because xda is based wholly on developers doing others favors and not on being compensated in advance to do so. Anyone who enjoys bean's work is free to donate to him after the fact. Xda is a volunteer network, not a marketplace.
Just be patient. We'll get our share of kernels and roms eventually. It's not like the Tab S is a worthless brick without it. For me this performs better than any tablet I've ever owned as is.

Exactly. And it isn't as though you can't get much of what you would want from a custom ROM via Xposed, launchers, and the like.

HughesNet said:
Exactly. And it isn't as though you can't get much of what you would want from a custom ROM via Xposed, launchers, and the like.
Click to expand...
Click to collapse
Exactly. Other than CM, most roms are just themed debloated stock with some Xposed thrown in.
** Edit: I put this badly. What I meant was that roms seem to people like themed debloated stock with some Xposed thrown in. They are not the game changers they used to be when these devices had weak processors and a few hundred extra benchmark points really meant something.
Roms are awesome, but they aren't as vital as they once were.

mitchellvii said:
Exactly. Other than CM, most roms are just themed debloated stock with some Xposed thrown in.
Click to expand...
Click to collapse
I couldn't disagree more. That's ridiculous.

mitchellvii said:
Exactly. Other than CM, most roms are just themed debloated stock with some Xposed thrown in.
Click to expand...
Click to collapse
Couldn't disagree with you more. There are alot of edits done to system files that you don't know about. Alot of work goes into incorporating those mods that people like you take for granted. Please don't be ignorant.

mitchellvii said:
Exactly. Other than CM, most roms are just themed debloated stock with some Xposed thrown in.
Click to expand...
Click to collapse
I have built & released custom ROMs based on Samsung official firmware.
There is a huge amount of work involved to create these ROMs and even more to support them. That's why I quit. ... (Not enough time in the day). I rarely used Xposed except for unsupported DPI changes.
Samsung "stock" ROMs are based on official Samsung firmware.
CM is "stock" ROM based on official Google source.
Based on the above, both CM and Samsung "custom" ROMs are both "stock" and "custom" (as in customised)..... If you customise anything, then it is "custom"
I am sure though that your post doesn't exactly read what you really meant.
Sent from my SM-N9005 using XDA Premium 4 mobile app

Let me clarify. I think I put that badly.
While roms are quite an bit more work than just debloating, theming and using xposed, many of them feel to the user like that was all that was done, especially with these incredibly fast new processors that can overpower and make even not the best code run fast and smooth. I recall years ago when the HTC Evo came out. A good rom could make a HUGE difference in performance. Now take the Note 3. Using a great rom there by Freeza. Sure it's a little better than stock but the improvement isn't nearly as dramatic as in the past.
I guess my overall point is this. The Tab S is such an excellent device that even if if no one ever creates a rom for us, we will still be able to have a fast solid machine. Roms are awesome but they are not the game changers they once were.

mitchellvii said:
Let me clarify. I think I put that badly.
While roms are quite an bit more work than just debloating, theming and using xposed, many of them feel to the user like that was all that was done, especially with these incredibly fast new processors that can overpower and make even not the best code run fast and smooth. I recall years ago when the HTC Evo came out. A good rom could make a HUGE difference in performance. Now take the Note 3. Using a great rom there by Freeza. Sure it's a little better than stock but the improvement isn't nearly as dramatic in the past.
I guess my overall point is this. The Tab S is such an excellent device that even if if no one ever creates a rom for us, we will still be able to have a fast solid machine. Roms are awesome but they are not the game changers they once were.
Click to expand...
Click to collapse
I couldn't more then agree with you.
We already got the horse power of the tablet I never over clocked my s4 or note 10.1 because I don't feel the need to. Basically its the New features of other devices I'm curious to try out. that's why note 10.1 (2012) got the file manager from this tab and it's beautiful. A Rom is fast with a good options to choose for the user so he can make it his. Speed isn't anything that's basically needed of course its fun to use the max power but for the love of your tablet be careful. that's why I haven't included anything of these kind of apps.
Also just to mention one app is missing because it didn't deodex successfully. will add it as an optional package.
Again this is just a pure stock deodex rom I don't own this tablet but I decided since i used it for porting and there was no deodexed rom I'd make one. Does anyone know what partition boot image is at?
Sent from my LG-D855 using Tapatalk

Wasn't Xposed designed to give the average user access to customizations they would typically only get in a rom previously? Sort of like a WYSIWYG editor instead of writing out the code by hand? And launchers speed up your experience in many of the ways only roms used to. With root and a decent app anyone can debloat their rig.
So many of the things we used to need roms for we no longer do. Of course roms like CM make a bigger difference but then again you give up some cool functionality. It's like taking the surround sound out of a racecar. Yeah you go faster but you miss your tunes (or split screen as the case may be).
Anyway, for me root and a good kernel are essential. Roms? A luxury but no longer the staple they used to be. That's not to say luxuries aren't nice and I'm sure I'll indulge if a certified developer cooks one up for us, but even if they never do I'm ok. This tablet still rocks.
DISCLAIMER: Everything I've written here is simply my opinion and the viewpoint of a non developer. I am not attempting to pontificate some greater truth, it's simply how I see it. If you disagree with me that's all good. It's a big tent here and room for lots of different viewpoints. ☺