yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Accessories] dbett4:
Xbox controller

I know you said wired 360 controller will work but what about a wireless one with a plug-n-play cable connected becuz i dont have a wired controller
[Nexus 7 Accessories] NZtechfreak:
Not sure, don't have one of those, but I expect it will work.
[Nexus 7 Accessories] bricewgilbert:
Pretty sure it won't work. Wireless 360 controllers do not send a signal through the USB charging cable. Only power. Same reason you can't use a wireless controller on the PC without buying the wireless transmitter thing that they don't make anymore.
[Nexus 7 Accessories] redmonke255:
Yup confirming this is correct. Didn't know they stopped making it, good thing I got one.
[Nexus 7 Accessories] Eagle1337:
They still make the wireless transmitter but you need to buy the controller with it.
[Nexus 7 Accessories] munkimatt:
Not sure if I'm missing something here but I've picked up a USB OTG cable today. If I plug in my PS3 controller it just flashes, I don't seem to be be able to do anything. What am I doing wrong guys?

EDIT

Ignore that, working fine.
[Nexus 7 Accessories] tkelly0727:
i have an sixaxis ps3 controller and i didnt need a ps3 to active it.
[Nexus 7 Accessories] beastech:
Do games natively support controllers, must they be mapped, or do you need an app of some kind to get it to work?
[Nexus 7 Accessories] magui43212:
It depends on the game. Dead Trigger and GTA 3 have native gamepad support, but NOVA 3 doesnt.
[Nexus 7 Accessories] h3r3tic:
Sixaxis was updated last night works amazing as always. And dead trigger has native support for sixaxis?
[Nexus 7 Accessories] RMXO:
Try this mapping from the S3 for NOVA3. Let me know how it works for you.

I can't remember where I got it from but it works great on my S3. You might have to config for larger screen though.
[Nexus 7 Accessories] XTM16:
From what I remember reading, no Gameloft game has native controller support.
[Nexus 7 Accessories] WinDroidGuy:
That's correct unfortunately :(

Sent from my Galaxy Nexus
[Nexus 7 Accessories] magui43212:
Ya, gameloft is not my favorite developer. Games are so much better when I can play with my sixaxis.
[About XDA developers] AndroidGreg:
Ok so for months, I had this link bookmarked, http://xdaforums.com/forumdisplay.php?f=1360.

It would always take me to the page for the moto razr that displays, General, Q&A, development, ect.

Well recently this now gives me a 404 page not found error, I have tried using the link from the forum page with the list of all phones, if someone can bring the link or a new one back to life that would be greatly appreciated. Using Google Chrome
[About XDA developers] AndroidGreg:
Bump for a fix
[About XDA developers] cdesai:
Works fine here.
[Samsung Epic 4G Touch] agat63:
Credit goes to Chris41g.

Other credits:

Gokhanmoral, rujelus22, Sweetwaterburns, droidphile, Tallustus.

I've decided to clean up a little and organize kernels starting from most recent.

All features described are for latest kernesl and I'll update the list as new features will be added.

This kernel is build from newly released source.

All kernels for TW (stock) based roms only.

This kernel can NOT be used with AOSP/AOKP/CM roms.

Kernel features:

Fixed slow charge problem.

FI27 source based

I/O schedulers: NOOP, Deadline, CFQ, SIO, VR.

EMMC CAP_ERASE bug disabled from source

Optimized initramfs to support Rom Updatertool.

Readahead tweaks.

Governors: Smartass, pegasuss, userspace, ondemand, performance, hotplug, lulzactive, powersave, lagfree, ktoonservative, Hyper

OC/UC/UV support.

ExTweaks enabled.

/data/.agat folder will be created (if not there) for ExTweaks profiles.

Voluntaree Preemption enabled.

SD card read speed increased

CPU can be clocked from 25 000 to 1 600 000 (removed higher frequencies)

I'm sure few other minor edits that I'm forgetting.

Linux kernel version 3.0.42​

Here are links:

Links:

v0.6.8

Fixed apps to sd (I hope) error. Moved couple movable of apps to sd. After several reboots apps were there and were working

Fixed mounting in recovery. ADB shell works. Mount USB storage from recovery menu works.

AGAT_v0.6.8.tar

AGAT_v0.6.8.zip

v0.6.7

Fixed back up error issue in recovery.

AGAT_v0.6.7.tar

AGAT_v0.6.7.zip

If anyone wanna try to build kernel himself/herself you can find source at my github here:

E4GT ICS kernel source

And my initramfs files are here:I

Latest Initramfs

I'll try to keep my repos up to date as I go and will update with all changes I do.

Enjoy.
[Samsung Epic 4G Touch] agat63:
Moved all previous versions here

to clean up OP.

Updated busybox Binaries.

AGAT_v0.6.6.tar

AGAT_v0.6.6.zip

Added ktoonservative governor.

AGAT_v0.6.5.tar

AGAT_v0.6.5.zip

AGAT_v0.6.3

Added missing governors.

AGAT_v0.6.3.tar

AGAT_v0.6.3.zip

AGAT_v0.6.2

fixed adb logcat issue

AGAT_v0.6.2.tar

AGAT_v0.6.3.zip

AGAT_v0.6.0.

FI27 source based.

Includes all features from the list above.

AGAT_v0.6.0.zip flash in recovery.

AGAT_v0.6.0.tar flash with ODIN or Mobile ODIN.

AGAT_v0.5.4.

Fixed slow charge issue.

AGAT_v0.5.4.tar flash with ODIN or mobile ODIN.

AGAT_v0.5.4.zip flash in any unlocked recovery.

AGAT_v0.5.3.

With help from Rujelus22 ExTweaks has been fixed. Now all values can be set and they will stick after reboot.

AGAT_v0.5.3.tar Flash with ODIN or Mobile ODIN

AGAT_v0.5.3.zip flash in recovery.

AGAT_v0.5.2.

Special thanks to Rujelus22. I have used his modified and updated ExTweaks script.

AGAT_v0.5.2.tar flash with ODIN or Mobile ODIN

AGAT_v0.5.2.zip flash in any unlocked recovery.

AGAT_v0.5.1 is FH13 based kernel and has almost all features listed above. UV/UC/OC, ExTweaks, few new governors etc.

Next will be adding new I/O schedulers and update to Linux 3.0.41.

AGAT_v0.5.1.tar Flash with ODIN or mobile ODIN

AGAT_v0.5.1.zip Flash in recovery.

AGAT_v0.5.0 is FH13 source build kernel.

It has no tweaks yet. No OC/UV/UC, governors or schedulers.

This is clean stock build from source with updated recovery. I'll add tweaks one by one.

This is to make waiting easier.

AGAT_v0.5.0.tar flash with ODIN or mobile ODIN

AGAT_v0.5.0.zip flash in any unlocked recovery.

AGAT_v0.4.4

1. AGAT_v0.4.4.tar flash with ODIN or mobile ODIN

2. AGAT_v0.4.4.zip flash in recovery.

AGAT_v0.4.3

1. AGAT_v0.4.3.tar flash with ODIN or Mobile ODIN. (Mirror comes soon)

2. AGAT_v0.4.3.zip flash in any unlocked or custom recovery. (Mirror comes soon)

Older verions:

AGAT_v0.4.2

1. AGAT_v0.4.2.zip flash in recovery (Mirror)

2. AGAT_v0.4.2.tar flash with ODIN or Mobile ODIN (Mirror)

AGAT_v0.4.0

1. AGAT_v0.4.0.zip to flash in recovery (Mirror)

2. AGAT_v0.4.0.tar flash with ODIN or mobile ODIN (Mirror)

AGAT_v0.3.0

1. AGAT_v0.3.0.zip flash in any unlocked recovery. Mirror

2. AGAT_v0.3.0.tar flash with ODIN or mobile ODIN Mirror

AGAT_v0.2.3

1. AGAT_v0.2.3.zip flash in any unlocked recovery.

2. AGAT_v0.2.3.tar flash with ODIN or mobile ODIN.

AGAT_v0.2.2

1. AGAT_v0.2.2.zip flash in any unlocked recovery.

2. AGAT_v0.2.2.tar flash with ODIN or Mobile ODIN.

AGAT_v0.2.1

1. AGAT_v0.2.1.zip flash in recovery.

2. AGAT_v0.2.1.tar flash with ODIN or mobile ODIN.

AGAT_v0.1.1

1. AGAT_v0.1.1.zip flash in any unlocked recovery.

2. AGAT_v0.1.1.tar flash with ODIN or mobile ODIN.

AGAT_v0.1.0

1. AGAT_v0.1.0.zip flash in any unlocked recovery.

2. AGAT_v0.1.0.tar flash with ODIN or mobile ODIN.
[Samsung Epic 4G Touch] revamper:
First!
[Samsung Epic 4G Touch] KingKong86:
O ya

Flashed in recovery worked perfect

Edit i flashed on boa is that bad lol it works perfect and fixed install problems
[Samsung Epic 4G Touch] someguyatx:
Excellent
[Samsung Epic 4G Touch] sniper:
Wow, very nice :)

Click here for custom mods for your E4GT
[Samsung Epic 4G Touch] Febby:
Sweet! do you know if a source built kernel fixes the issue where we can't install certain apps without unmounting the SDcard?
[Samsung Epic 4G Touch] agat63:
Haven't try that yet but there is another permanent (almost) workaround that problem.

If you can't install apps to sd just flash stock kernel with mobile odin boot to system and flash kernel with custom recovery via mobile odin as well.

You will be able to move apps to sd and install apps to sd till next flash.

Edit: Just successfully downloaded wheres my water. No problems.

Moved couple of apps to sd - no problems.

As usual you can only move apps that have "move to sd" buttom active and not grayed out.
[Samsung Epic 4G Touch] leaderbuilder:
VERY NICE! Thanks Agat and Chris41g.

One question. I read on another post that Chris had said that we could not flash modems. But wasn't sure if he was talking about your last FF18 kernel or something else.

Will this kernel allow flashing modems? I mean it should shouldn't it.
[Samsung Epic 4G Touch] sjsharksfan420:
Great work Agat & Chris!!

Thank you!

sj
[Samsung Epic 4G Touch] Darrien13:
so I can flash between GB and ICS with no problems now!?
[Samsung Epic 4G Touch] Idolhands86:
"If you find problems please let me know and I'll try to fix them."

Not a problem anymore, but thought I'd say.... Flashed with Mobile Odin. Started right back up. Updated Profile and PRL, then got stuck on boot animation; roadrunner on Goodness. Did usual to get into your new recovery, reboot system, very fast startup. No problem for me and running great since, like I said, just feedback. Thanks a ton to you and Chris; everyday, a new phone.
[Samsung Epic 4G Touch] dcowboys2184:
Flashed thru mobile Odin and f/c's
[Samsung Epic 4G Touch] CyberpodS2:
So far no problems after flashing through mobile Odin... Will be putting it through the motions today. Thanks guys!
[Samsung Epic 4G Touch] Sloth:
This may be a dumb question but is this kernal already rooted? Still kind of a noob haha.
[Samsung Epic 4G Touch] chris-allen:
+1
[Samsung Epic 4G Touch] MiguelHogue:
Not sure what you mean by rooted kernel lol.. But it's safe to use in your Rom.. As long as it's not one of the ROMS listed in the OP
[Samsung Epic 4G Touch] bigpeng:
Great job Agat! Now, how we can under clock and over clock to our phones full potential!
[Samsung Epic 4G Touch] donsh00tmesanta:
Safe to use for.any rom? Ics of course? Even aokp and cm9?
[Samsung Epic 4G Touch] timmetal6669:
I love you guys, thank you!

Oh forgot to ask, just making sure, what build number is this built from? Stock (source) ff18 ?
[Samsung Epic 4G Touch] caspersfi:
Thank u sir. Exactly the info I was looking for. I'm in the middle of transferring apps to SD but I think I'll stop and take a closer look of which apps I transfer.

I have 20 gigs left on my external SD. I have around three left on my internal. From here I'm gonna get into transferring what ever I can from my internal to external.

Thanks again bro.
[Samsung Epic 4G Touch] blackcanopy:
You are very welcome.

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] blackcanopy:
I flashed the zip and it didn't add the smart governor. I mobile Odin'd the tar and now have the smart governor. Something must be missing in the zip version Agat.

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] cas8180:
Anyone have any thoughts on how the new governor might interact with tegrak and the module it loads + undervolting?
[Samsung Epic 4G Touch] agat63:
For those of you who wants to know what is smartass governor:

2.7 SmartassV2

---------------

The CPUfreq governor "smartassV2", like other governors, aims to balance

performance vs battery life by using low frequencies when load is low and

ramping the frequency when necessary, fast enough to ensure responsiveness.

The implementation of the governor is roughtly based on the idea of interactive.

The idle loop is used to track when the CPU has idle cycles. The idle loop will

set a relatively high rate timer to sample the load when appropriate, the timer

will measure the load since it was set and schedule a work queue task to do the

actual frequency change when necessary.

The most important tunable is the "ideal" frequency: this governor will aim

for this frequency, in the sense that it will ramp towards this frequency much

more aggresively than beyond it - both when ramping up from below this frequency

and when ramping down from above this frequency. Still, note, that when load is

low enough the governor should choose the lowest available frequency regardless

of the ideal frequency and similarly when load is consistently high enough the

highest available frequency will be used.

Smartass also tracks the state of the screen, and when screen is off (a.k.a

sleep or suspended in the terms of this governor) a different ideal frequency

is used. This is the only difference between the screen on and screen off

states. Proper tuning of the awake_ideal_freq and sleep_ideal_freq should

allow both high responsiveness when screen is on and utilizing the low

frequency range when load is low, especially when screen is off.

Finally, smartass is a highly customizable governor with almost everything

tweakable through the sysfs. For a detailed explaination of each tunable,

please see the inline comments at the begging of the code (smartass2.c).
[Samsung Epic 4G Touch] agat63:
Here is another zip file with new kernel:

AGAT_smart_test.zip

This should work.

I guess I forgot to replace zImage in first zip I made.

Was about 2.30 am when I made it.
[Samsung Epic 4G Touch] proxy0:
I can flash this from rooted stock ff18?
[Samsung Epic 4G Touch] agat63:
You can flash this with any TW based ICS rom.

No restrictions.
[Samsung Epic 4G Touch] proxy0:
Nice now I can finally ics to ics.
[Samsung Epic 4G Touch] MiguelHogue:
Wow see you got it working ;). . So basically grab this zip.. Flash it.. Download rom tool box (just using what you used in your previous post) .. Select smart ass governor option.. And be good from there?
[Samsung Epic 4G Touch] duce415:
Has anyone been able to successfully underclock with this kernel? I like using setcpu to control the cpu and govs and like to set profiles but so far only been successful on gb roms
[Samsung Epic 4G Touch] agat63:
Undervolting/underclocking/overclocking is on my to do list.

But give me some time. I'm tapping in dark here and learning as I go.

It takes a lot of reading and then failing and then reading and failing few times till I get something working the way it should.

So time consuming.

Once it's confirmed the new governor is working I'll push modified source to github and move to next project.
[Samsung Epic 4G Touch] duce415:
Agat don't mind lil ol me lol... you do beyond great work for the community... I wouldnt care if it took you a year to do it cuz I know when its done, IT'S DONE AND WORKING.. so take your time and do the great work you do... if no one thanks you I will.. THANKS AGAT..
[Samsung Epic 4G Touch] WhiteZero:
Dumb question: Can/should I flash this Kernel if I'm running GB currently? I'm using Calkulin's E4GT 3.0 (EL29) with Kernel 2.6.35.14-rouge_ET-1.4.1+

Should I try using the autoroot package here and choose "Install BootImg FF18-CWM-agat-src" ? Would it be safe to use that on my current ROM/Kernel?

I'd like to get on AGAT before trying to go to any ICS ROMs.
[Samsung Epic 4G Touch] duce415:
Been running calks 3. 0 all week... was thinking of diving into wicked land and trying your kernel out also... I use to use smartass gov on my evo with the sbc option so I know smartass is a good gov to use... also interactiveX
[Samsung Epic 4G Touch] duce415:
This kernel is only for touchwiz based roms... calks is gingerbread so flashing this kernel could lead to the end of the world lol
[Samsung Epic 4G Touch] agat63:
You can't try this kernel with your current rom.

This is ICS kernel for ICS roms only.

You phone won't boot if you flash this kernel with you current rom.
[Samsung Epic 4G Touch] weltwon:
Works perfectly with Calkulin V1.6

For anyone concerned, I just flashed this kernel after installing Calkulin's_E4GT_2_ROM_v1.6.zip and aside from it working flawlessly, when I booted it found my WiFi and Bluetooth connections faster than ever!

Thanks Agat!

Glenn :)

P.S. Just donated enough so you can buy a pint of Lemon Sorbet at Vons. Tastes great during Vegas summer heat!

P.P.S. Without me digging, are there any pluses or minuses with your CWM vs. CWM5.5.0.4 ?
[Samsung Epic 4G Touch] agat63:
Thanks for donation bro.

But I'll go for large coffee today.

We are in our monsoon season now and it's quite good and cool at the moment. Bout 82 and humidity in 50s-60s I would say.
[Samsung Epic 4G Touch] zarthan:
Which ROM updater app does this apply to? and does it support your ROMs?

Thanks
[Samsung Epic 4G Touch] times_infinity:
It's the same thing.

calling format in recovery to erase a partition calls the MMC_CAP_ERASE command, which triggers the bug in the wear-leveling code.

If calk's script simply rm -rf'd everything in the partition, that'd be a different story.
[Samsung Epic 4G Touch] GWashington:
Just in case you need it:

http://www.youtube.com/watch?v=_vmEmheJnyg

I've used the included .tar file & it worked just fine, not because I was actually bricked though :eek:

Good Luck!
[Samsung Epic 4G Touch] vanberge:
Appreciate the effort but that is for a soft brick - Blue LED only = hard brick where jtag is the only recovery.
[Samsung Epic 4G Touch] sniper:
Jtags can't always fix it.

Click here for custom mods for your E4GT
[Samsung Epic 4G Touch] vanberge:
Well, they are the only option you have to try if you need to resurrect the device.
[Samsung Epic 4G Touch] agat63:
I don't think it's kernel related.

Guys I'm not saying I'm perfect nor I'm trying to defend myself.

my v0.5.4 has been downloaded:

tar format 569 times

zip format 587 times.

This totaling over 1100 times.

If kernel/recovery wouldn't be safe we would of have more of this problem.

More bricks.

I think there's something went wrong.

I can't say what and I can't say why. But knowing that the kernel has been used so many times without any hick ups or problems

makes me think there should be something not kernel related.

I really feel sorry for the brick and I hate the fact that it happened wile using my kernel.

I'll gladly fix any problem and/or brick cause.

Just checked source on my laptop.

CAP_ERASE command is not there.

Unless something went terribly wrong and it came back somehow it should not be there.
[Samsung Epic 4G Touch] times_infinity:
https://github.com/agat63/E4GT_FH13_kernel

if that's the kernel source you're using, and I'm assuming it is because listed as a feature it says it's a FH13 base, and as of version 0.5.0 it says it's build using a FH13 base,

then line 1881 of https://github.com/agat63/E4GT_FH13_kernel/blob/master/drivers/mmc/host/mshci.c#L1881 is the culprit.
[Samsung Epic 4G Touch] im0rtalz:
this sounds like the same mismerge patch that also caused a few bricks when everyone was flashing dk jb port
[Samsung Epic 4G Touch] PhAkEer:
Funny...

I hadnt seen that last little part of your post and was thinking "yeah but wasnt format all safe because it was actually rm -f everything"... figured Id go check for myself... not only was my thought wrong but you had already posted the it..... and it was quoted on my screen... lmao

edit: interesting. I never looked into Ecap in its true form... I knew it was a programmed failsafe.... but I didnt realize it was request related...

I know this isnt a class room... but what the hell do (Im assuming this is the same SDIO Om familiar with) secure digital In/Output and interupt requests have to do with wear level? I think samsung just wanted to flip us off....

dont get me wrong, I see the potential IRQ conflict in format/parting... but to assume the best course in absolutes from the programming level is flat out bad science... "uhh hi.. im MMC thats worn down so naturally my next request will be on Modems road...." ...

(sorry tired enough this is funny.... awake enough to already regret posting it...]
[Samsung Epic 4G Touch] GWashington:
Yeah, thought that might be the case.

Please do keep us apprised, as I have used both 0.5.2 & 0.5.4 w/o issue. I am no developer, yet times_infinity's findings have me just a bit concerned:eek: However, if you follow Agat's link in the OP https://github.com/agat63/E4GT_ICS_kernel, the MMC_CAP_ERASE; line of code is not here:

https://github.com/agat63/E4GT_ICS_kernel/blob/master/drivers/mmc/host/mshci.c

Again, not a dev, but if I'm looking in the right place, MMC_CAP_ERASE; is not there...

Curious to see what those who know more of what there talking about say! :)
[Samsung Epic 4G Touch] vanberge:
I'm not trying to play a blame game by any means. I take the responsibility when I flash and I'll handle it... but, it'd be crappy for this same thing to happen to another person.

I used your kernel personally to flash CM9, CM10, Paranoid, and AOSP Jellybean. I felt really comfortable using it for flashing.

but, the point is that I bricked when flashing AOKP. So, something went wrong somewhere between these two things that many people have used. Just sharing my experience so others can use the information to not have the same thing happen.
[Samsung Epic 4G Touch] times_infinity:
The same thing happened with Chris' kernel too. For the longest time, it still had the MMC_CAP_ERASE command in it. everyone used it for flashing, wiping, etc. No one had problems.

And then once sbrissen started releasing his Vanilla Jellybean builds, people started bricking.

What I think it is, is that most all of everyone's zips, touchwiz ones anyway, use a Gingerbread update-binary which has been known to help alleviate bricking. While I do believe, aokp and sbrissen's jellybean both use source generated update-binaries (someone correct me if I'm wrong).

I'm not trying to play the blame game either, I'm just trying to help keep other's phones from falling victim to simple mistakes.
[Samsung Epic 4G Touch] PhAkEer:
figured Id do you a favor and capture this typo in time for ya :p

also sending a pm
[Samsung Epic 4G Touch] GWashington:
Hey times_infinity,

Did you see my post 1991? Curious, am I wrong here?

Thanks!
[Samsung Epic 4G Touch] PhAkEer:
well both yours and his both lead to agat git but the one TI posted was I believe for a specific build
[Samsung Epic 4G Touch] times_infinity:
Yeah, I saw it.

Idk what source he's using though, although he links to the one labeled E4GT_ICS_Kernel.

Yet, on his github he does have a repo labeled E4GT_FH13_Kernel.

As you stated though, the one labeled E4GT_ICS_Kernel does have the MMC_CAP_ERASE command removed, while the one labeled E4GT_FH13_Kernel does not.
[Samsung Epic 4G Touch] PhAkEer:
Well this is all fascinating for me...

because Im pretty sure I remember that the coding was impossible to replace...

the best option was to remove the ics trigger that was accidentally shooting emmc in the head..

as in.. the failsafe itself itself was/is/will always be in our phone....

may be abke to find a reference in a bit here to post but yeah, I think its mmc firmware that no amount of editing ics source can get rid of

just a WHOLE LOT less likely without that misfiring trigger.
[Samsung Epic 4G Touch] GWashington:
Thanks guys! I'm learning here too, so I appreciate your replies. I thought I was correct...first time all day according to my wife!
[Samsung Epic 4G Touch] CyberpodS2:
I am sure others are like myself and using other builds Agat made along the way. I for one use 0.4.5 with great luck in other regards. If someone who knows how to do it could take the time to go through the lists on http://rwilco12.androidfilehost.com...y Kernels/ICS/Agats Source Built Recovery/ZIP it might help establish where something might have changed and when it did...
[Samsung Epic 4G Touch] JamesEh408:
Thanks for the killer 5.4 man!

I have noticed that sometimes the kernel is taking up to 30+% using gsam to monitor. This seems really high.

I have heard that some kennels dont play well with some modems...any recommended modems?