yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy Note II] knightfox:
I dont think this is all due to Windows issue. This is what i notice before and after root.

If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.

If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.

If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.

How i notice this, i have root/unroot my device like 20 times since i got my device.

The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.

Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
[Sprint Samsung Galaxy Note II] ceabbott2:
Yep I think you may be on to something. Because when I rooted I tried both TWRP and CWM and then I had to go back to stock to get to apply the LJC update. Ever since I have had the chameleon error and Handsfree activation issues. Oh my counter always says 1 and I can't remove it with triangle away. I think it says custom binary yes and the counter says 1. I am using a laptop with Windows 7 and it now recognizes the device just can't stop the errors on start up.

Charles
[Sprint Samsung Galaxy Note II] GamerOnOne:
Samsungs older drivers: uploaded.net/file/hdh0f1xd
[G2 and Desire Z Q&A, Help & Troubleshooting] Steven How:
So recently I have flash an ics Rom (mimicry 1.5.0),and I tried to use the browser to a flash content site..and all the flash content wont work..any idea ? I have been searching back for the fix,still can't find it..its something gonna do with deleting some file in system I guess..can't be sure..hope someone can help me out..thanks in advance..:o
[G2 and Desire Z Q&A, Help & Troubleshooting] sorgo:
Probably this is what you are looking for:

http://helpx.adobe.com/flash-player...Archived_Flash_Player_versions_for_developers

scroll down for "Flash Player for Android 4.0 archives". You can download an APK file and install it.
[G2 and Desire Z Q&A, Help & Troubleshooting] Steven How:
Thx! :)
[HTC EVO 3D] spurfan33:
i installed [ROM][11/13/12][JB 4.1.2]MiuiAndroid 2.11.9 by lens_flare and loved it except for the poor batter life..

i installed [Kernel] ButteredToasT ICS RLS13.1 by bigwillyg hoping to get better battery results but to no avail...

anyone know of a good kernel that will make my battery last??

evo 3d

hboot1.50

s-on

4ext recovery
[HTC EVO 3D] flashallthetime:
Well I was having a similar issue but on Paranoid, go to system/etc/int'd and there should be some files that can be deleted, and also clear cache in kernel tuner it can i cause issues if you just flash another kernel over another kernel

( Don't ask me for help as I couldn't care if your phone explodes, eh! :D)
[HTC EVO 3D] spurfan33:
here is what i'm finding

here is what i'm finding in the system/etc/int'd folder

.placeholder

00banner

01defaulttheme

90userinit

99anthrax

99buttered

99sweep2wake

beats

Rockodev beats

how do i know what needs to be deleted??
[HTC EVO 3D] flashallthetime:
Well I see anthrax and butter toast, so you have 2 files that are conflicting with each other, do a nandroid and delete anthrax and see what happens

( Don't ask me for help as I couldn't care if your phone explodes, eh! :D)
[HTC EVO 3D] spurfan33:
removed the anthrax item and no issues thus far

downloaded kernel tuner but see no option to clear cache ,,,

i have the paid version of cachemate but dont know if that'll give the same results kernel tuner will
[HTC EVO 3D] flashallthetime:
Ok just set you cpu frequency and any other specs you wish but I would suggest just leaving the settings you set during installation alone, my feeling is with all the kernel flashing and apps that can customize your kernel settings, somehow they conflict causing grotesque battery drain, I use kernel tuner and had it set my frequency with int'd scripts, the last couple of days my battery would drain so fast(I have 3 batteries all drained quickly) so through trial and error I deleted int'd files and bam my battery drain is back to normal

( Don't ask me for help as I couldn't care if your phone explodes, eh! :D)

---------- Post added at 11:54 PM ---------- Previous post was at 11:51 PM ----------

What also made my curious was in would set my frequency to 384MHz but when I would check the frequency in kernel tuner my frequency was always 192 mhz

( Don't ask me for help as I couldn't care if your phone explodes, eh! :D)
[AT&T Samsung Galaxy Note II] billy938292:
I have galaxy note 2 i317 AT&T version. I have unrooted my phone but still have CWM recovery left. How I can remove that. I am new to this. I was able to retrive firmware for my device from samsung open source site but not sure how to deploy or flash back to my i317 model using odin. Can you please help or guide.

I was able to download Samsung galaxy note 2 at&t firmware from opensource samsung com but dont know how to deploy or flash to my phone using ODIN. If someone can please advice on some steps or tutorial I will really really appricate.

I just want my phone to be normal the way it was before. I dont think i need rooting It was just plain stupid of me to go in first place. overall phone works fine it just bothers me to see that CWM recovery to be their and in case I need to return it I don't think at&t will accept it.

Also I did backup my stock rom from phone after rooting. (I am new android user and I dont belive their is way to make stock rom backup before rooting) So any help will be appricated.
[AT&T Samsung Galaxy Note II] holycow1:
I'm just guessing this is the appropriate method:

Re-root the phone.

Download triangle away.

Download the AT&T galaxy note 2 system dump from http://xdaforums.com/showthread.php?t=1983158

Use the toolkit to convert it to a .tar.

Flash it just like you flashed CWM tar.

Run triangle away and reset flash counter.

Un-root using superuser.

Please confirm with other users before doing the steps above. I could not locate the stock recovery.img anywhere, so I believe the system dump is the best thing to flash.

Good luck!
[AT&T Samsung Galaxy Note II] billy938292:
One of the users try converting system dump to tarz and it failed. So I assume may be its not working?

"th3g1z

This is a bit by bit img of the system partition of the att note. So you don't exactly install it. Basically you can adb into your phone and use the dd command to write it back to the system partition (mmcblk0p13). My first attempt at making it a tar to use with ODIN failed I will try an alternative method tonight when I'm off work.
[AT&T Samsung Galaxy Note II] billy938292:
I am gonna give one more try. I downloaded system dump (p12.7z) just fine thanks for the link. But which tool kit you are refering too? Please provide link or name of it. I am new to android and rooting coming and moving from Iphone to android.
[Nexus S Android Development] purian23:
Please stay tuned
[Nexus S Android Development] bbedward:
Reserved
[Nexus S Android Development] Articudos:
I heard this kernel is one of great kernel in GNex forum.:)

I'll flash it right away;)
[Nexus S Android Development] Mawtin:
Cool, I love flashing new releases
[Nexus S Android Development] ScOULaris:
A new challenger appears! I'll have to try this out sometime in the near future, but it will be hard to tear me away from Marmite.
[Nexus S Android Development] Brishen:
Does not boot.

using latest CM10 nightly
[Nexus S Android Development] Articudos:
No Custom IOCTL stuff I guess..;)
[Nexus S Android Development] Big Dog KMc:
Op does not Specify weather this Kernel is for,

CM Based roms

AOSP Based roms

AOKP Based Roms

I Tried it on Latest Paranoid Android (CM Based) and it black screens.
[Nexus S Android Development] purian23:
Is now compatiable with AOSP ROMS Only. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device :)

Thank you all for trying and posting your experiences, we will certainly get you fixed up!

Purian23
[Nexus S Android Development] Pete7ate:
Thank you for your sharing.
[Nexus S Android Development] Big Dog KMc:
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
[Nexus S Android Development] anshumandash:
This is 5.4 MB? Hmmm...need to see how it performs. :)
[Nexus S Android Development] anshumandash:
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage. :)
[Nexus S Android Development] leap_ahead:
also no Crt Fix ..
[Nexus S Android Development] raducux:
Didnt work for me with a cm10.
[Nexus S Android Development] sperelli:
will a cm10 version be available?
[Nexus S Android Development] bbedward:
Its based on aosp source and was tested on crossbones ROM, I'll get the rest of you guys figureld out soon.

---------- Post added at 02:18 PM ---------- Previous post was at 01:22 PM ----------

I understand, looks like CM requires a kernel patch for this http://review.cyanogenmod.org/#/c/23541/

I was unaware as it was tested on an aosp based rom :)
[Nexus S Android Development] bbedward:
We made a decision here, we're not going to support CyanogenMOD officially.

We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.

If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.

The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo

We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler

Only official builds are supported!

Thanks
[Nexus S Android Development] ScOULaris:
Looks like I won't be trying this kernel, then.
[Nexus S Android Development] bbedward:
Stay tunes for V2, thanks for the feedback from some of you. Added bigmem, voodoo color support, usb fast charge support, some more lowmemorykiller upstream updates, and also cifs+fuse FS support.

We're offering this to the community with no expectations that you use it, but for those who do use it we want them to be completely satisfied.

If it doesn't work for you, then I encourage you to use something from one of the other great development teams out there.

I thought of a couple solutions: 1.) creating 2 kernel builds, 2.) creating a sysfs interface so CM users could flash an init script that'd enable the CM ioctl's. Basically it comes down to this - neither solution is up to my standards for now.
[Nexus S Android Development] migueldbr:
what is the point of doing such a post?its because of attitudes like this that devs are starting to get upset. He offers this kernel to us for free, if it does not please you then move along and shut up
[Nexus S Android Development] knzo:
Thank you and kudos for posting the config and toolchain, I really liked that.

So what distinguishes this kernel from all the others? For me they are all the same except thalamus (very simple and minimalist approach) or marmite (tested and proved stuff). I took a glance at the commit list and I saw nothing special to be honest.

Sell it to me! Convince me on why I should try it.

Sorry but I laughed at this. Public relations and creative director? LOL.

-- edit:

Oh, what changes did you make to the toolchain?
[Nexus S Android Development] purian23:
Removal

Removal of information
[Nexus S Android Development] bbedward:
I don't know, I'm not really familiar with any of the others so I can't accurately compare them to this one.

The main goal here is to have a kernel product that is unified across several devices. As you may notice, the features in this kernel and a lot of the tweaks are identical to those in the GNex github, the Grouper github, and soon all of the others. I want to unify it between the ADA brand and the Zen brand (I was formerly the lead dev for the Zen kernel project, until I took too much of an interest in android and became a bit occupied with other things). The connection with Zen is that I have the same philosophy Zen does, just for a different application.

The primary Zen purpose (it has/had more than one, but it doesn't apply here so much) is to take the linux kernel source, which is generally very loosely optimized for any system, but by default has optimizations that are more closely suited for servers -> and not only optimize it for desktops, but to also add in several features that desktop users would find beneficial.

The purpose of the ZenSERIES of android kernels is primarily the same. Although its a bit more tricky since every device uses different drivers that are not officially a part of the linux kernel. But the principle is the same, optimize and include features that are beneficial in mobile applications.

We were initially using linaro, but linaro can be a bit tricky and not necessarily considered quite as stable (some users reported linaro 4.7 caused some issues, so I just decided to go with a stable GCC)

The toolchain consists of:

- Whatever patches the latest crosstool-ng applies by default

- The latest patchset gentoo uses on 4.7.2 (http://mirror.mcs.anl.gov/pub/gentoo/distfiles/gcc-4.7.2-patches-1.3.tar.bz2)

- Build with some basic sane optimizations - including the ones CT-NG uses by default. Aldo added some relevant such as -mtune=armv7-a, vfp intrinsics (vfp intrinsics are generally considered better for compilers than neon intrinsics)

Hopefully this answers everything.

----

"BreakingGround" is a coin phrase associated with the initial version of the kernel. We are "Breaking Ground" into the Nexus S development community so to speak. We did the same thing in the Galaxy Nexus forum, and we will probably do the same in other threads.

We do not mislead users in any way, as you suggest. Everything remains accurate.

Yes it's not a ground breaking compiler - it's still GCC, but I did build it myself and along with the gentoo patchset and crosstool-ng patchset, and some of those basic optimizations that make it well suited for the purpose of compiling an android kernel.
[Nexus S Android Development] knzo:
I saw those "tweaks ported from SGN". Basically you are using same sysctl values both for an OMAP4 with 1 GB RAM (SGN) and a Hummingbird of 512 MB (NS). I have some doubts regarding this. Unification has this downside, it kills specialization which is far more important in smartphones.

Thanks for the details on the toolchain.

It's a coin phrase that misleads users thinking this kernel offers anything groundbreaking or a new feature when it does not. Even the old "unification" ethos is not new here. I call bull**** but if you really want to push flashy words to get your way inside fine, that's on you.

I'll follow this kernel development but I hope you can bring something new here, at least you seem to have the skillset.
[Nexus S Android Development] bbedward:
Specialization is important to an extent, but you're a bit mistaken there.

First of all these changes aren't "ported." They are changes that you could apply on probably every 2.6+ linux kernel, at least most of them.

I think you should read up on those settings to see why there is no downside to them on a device with 512MB of ram and a device with 1GB of ram. Some of them are to minimize I/O operations, which you do not want in excess on ANY mobile device. Theres minfree_kbytes set to ~4Mb, which is also conservative on both platforms.

So you're mistaken a bit on pretty much every sysctl setting.

The only one where device specific settings are more important is the default lowmemorykiller settings. I think the settings are slightly more conservative on a galaxy nexus, and slightly more aggressive on the nexus s which is perfectly fine.

Bottom line is that, the settings translate.

I have no issue answering your questions, but your rudeness is not something I am willing to tolerate.

We will bring what we bring, nobody has the right to tell us what we can and cannot do with any of our projects, unless we are in violation of any licensing or forum rules.

Coming in here and trying to show me up or confuse me by getting technical is definitely crossing the line, I do this sort of stuff for a living and have been a part of the linux community for years.

*edit*

And breaking ground does not mean the same thing as ground breaking. Traditionally you break ground when you get started with anything. People call things "Ground Breaking" when it's revolutionary.
[Nexus S Android Development] BlueHarford:
Ok just to back Brandon up. the only reason we're doing a Nexus S kernel is as a favor for Mike with Crossbones. Nexus S IMO is way outdated and if your running it.. well its time to upgrade lol.

If we get enough of this drama and rudeness we'll delete our source and close the thread just as fast as we created a kernel for you guys. be grateful Brandon spent his free time making a new kernel for what is now a legacy phone (as google even stated they are not supporting it in 4.2)..

Brandon you've done a great job.
[Nexus S Android Development] bbedward:
You're a cancer to this community.

I will keep my development efforts on the Nexus S only to support the Crossbones project. I do not wish to be a part of your community otherwise.

You don't even know what you're talking about, and failed to outwit me - yet you still cause these issues.

Shame on you.
[Nexus S Android Development] bbedward:
I wrote my own I/O scheduler, took every feature a nexus S user could possibly want, and optimized a bunch of system settings.

Sounds like a good kernel option to me, whats wrong with having another kernel?

Oh, i guess i'd rather take an aosp source rom, remove some apps, and call it METAL DRAGON OVERLORD.
[Nexus S Android Development] nibla101:
Just so you know

Deep idle is know to cause instability on JB, other kernel devs had it removed.

EDIT: Aww man, I was just about to test the kernel now its gone
[Nexus S Android Development] bbedward:
The kernel is going to be exclusively available on Crossbones rom. No more public builds will be available for the Nexus S. The kernel source will remain in github of course too.
[Nexus S Android Development] purian23:
We do apologize to those of you that could have benefited from this Kernel. We simply are not just another team trying to operate with users like this. We will move on as it is our goal to not operate in our threads like this. Thank you all.

Purian23
[Nexus S Android Development] nibla101:
Knzo, come on man.

We don't want another _Thalamus raping this forum, Let people do what they want.
[Nexus S Android Development] bbedward:
Hmm, I didn't know there was such thing as Linux I/O scheduler that does not use the elevator struct and elevator_data?

Seems like they all do that.

Silly me.

By the way, waninkoko is a co-founder of the Zen kernel project. I was the lead dev of the Zen kernel project when the SIO scheduler came into existance. I ported and merged SIO itself through several kernel releases as well.

So i'm not sure you should dig into any code, stick to tonka trucks or something.

...

That snippet is pretty dumb obviously since all of the I/O scheduler use elevator_data in multiple places, but

static void deadline_exit_queue(struct elevator_queue *e)
{
struct deadline_data *dd = e->elevator_data;

static void cfq_exit_queue(struct elevator_queue *e)
{
struct cfq_data *cfqd = e->elevator_data;

static void noop_exit_queue(struct elevator_queue *e)
{
struct noop_data *nd = e->elevator_data;

I guess no-op/deadline/cfq are all the same too.

Give me a break, look at some differences that actually matter.
[Nexus S Android Development] M_T_M:
Just cleaned this thread up. I will not tolerate harsh behavior in this forum.

If any of you (including the trolls) needs a more detailed explanation about the development on this thread...PM the OP, otherwise, vacate the premises ASAP!!

Regards,

M_T_M
[Nexus S Android Development] mwielgosz:
I just wanted to thank the ADA team, especially Brandon (bbedward), for his hard work and dedication to building this kernel.

Hopefully the public releases will be available for everyone at some point, but people...calm down. There is no reason to trash anyone's work unless they simply copy another's work without due credit. If you don't like a ROM or kernel, don't use it.

As for now, this kernel will remain the default kernel in my Crossbones ROM project. I have been testing and using ZenSeries from the first release and find it to be extremely efficient and fast. Both Brandon and Josh are good friends of mine and I hope that we can continue to work together in the future to provide more choices for the Android community.

Remember, this is a hobby for us developers, not a paid job.
[Nexus S Android Development] :
Hello again. Good to see crossbones coming back. How's the kid growing up? Mine just turned two! But she's huge like a three year old!
[Nexus S Android Development] peepee999:
No link to download?

sent from my Jelly Bean
[Nexus S Android Development] apatal:
Noticed the change in OP. Does this mean you changed your mind about not sharing the kernel here?

Posted using xda mobile app
[Nexus S Android Development] anshumandash:
Deleted
[Nexus S Android Development] :
Hello, I took the liberty of testing the toolchain vs google's own 4.6 gcc.

I know linpack multi-thread test to be the best indicator of overall performance from some regression testing in previous kernel/ROM benchmarks I performed.

Results: https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdDhjVWYyanhBODViSWhYWG03QldYcXc

To ensure a good quality data I repeated the test 33 times.

Overall:

3 std devs	10.5525210356382	10.5839162157544
median/mean	99.92%	99.95%
average	10.3684848484848	10.4051515151515
google's gcc4.6	ZenKernel_ARCH_armv7a_compiler

When the ratio of the median and mean is less than 0.1% I stopped testing (2nd row)

The top row, "3 std devs" is the mean plus 3 standard deviations. This shows the time we would expect to score lower than in 99.7% of tests. As we can see google's own compiler seems to do a slightly better job of optimising the kernel.

Googles toolchain: https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
[Nexus S Android Development] bbedward:
What kernel did you compile and what compiler flags did you use?

I'm well aware that toolchains have been tested and had differences that are entirely negligible, on our platform, - whether it be linaro, google's, etc., such as those differences you posted which are differences well within the margin of error.

The point is, I wanted a stable GCC 4.7 cross compiler so I built one. Not saying I utilize all of the benefits 4.7 offers, I don't build with graphite loop optimization or anything - but it's not a bad thing to have the latest stable GCC on hand to build embedded arm code, is it?

I chose to build a stable version over using something like linaro, because some users reported regressions with linaro (although isolated, and I can't necessarily prove or find the underlying cause myself).