yashsingh1/xdaforums huggingface dataset:
[EVO Shift 4G Android Development] nfinitefx45:
Check in the dhd and dz threads as there source is very similar to ours
[EVO Shift 4G Android Development] nutrapi:
You rule
[EVO Shift 4G Android Development] -somebody-:
uploaded them to my dev-host account too for future use
[EVO Shift 4G Android Development] jwigley24:
anyway you could post a link to your dev-host account? or is anybody able to re-up the 1.6 ext4 kernel? thanks to anyone that can help!
[EVO Shift 4G Android Development] -somebody-:
sorry, i got sick of the bullsh!t with files vanishing from dev-host so i deleted my account, if i have a chance to upload them to somewhere else today i will.
[EVO Shift 4G Android Development] jwigley24:
Thank you! I appreciate the help!
[EVO Shift 4G Android Development] trsix:
x2

i was looking for the dodge kernels last night :(
[EVO Shift 4G Android Development] YoungCorruptionV2.0:
If no one uploads it tonight then I should have it on my computer and I'll upload it for you but not until I leave this bar-b-que
[EVO Shift 4G Android Development] trsix:
frick

had been keeping it on my sd card in case needed it again. sd went south last week. arrgh.
[EVO Shift 4G Android Development] prboy1969:
Here you go guys. Re-Uploaded all the Links;) . Enjoy :D .

Ext.3 fs Conversion zip

Ext.4 fs Conversion zip

Ext.3 Dodge Kernel v1.5

Ext.4 Dodge Kernel v1.5

Ext.3 Dodge Kernel v1.6

Ext.4 Dodge Kernel v1.6
[EVO Shift 4G Android Development] jwigley24:
thank you!!!
[EVO Shift 4G Android Development] prboy1969:
Always here to help :D .
[EVO Shift 4G Android Development] deerkiller11:
i've got to say that one of the best OP i've seen, well thought out and organized. good job sorry i'm so late to the thread.
[EVO Shift 4G Android Development] -somebody-:
thank bro, i managed to lose em all that i had >.>
[EVO Shift 4G Android Development] prboy1969:
Always here to help :) .
[EVO Shift 4G Android Development] prboy1969:
Very nice :) . Thanks :)

+1 on the call recording if possible.
[EVO Shift 4G Android Development] dodgejcr:
Yeah after a little research, it doesnt seem too hard. Ill give it a shot.
[EVO Shift 4G Android Development] dodgejcr:
Updated: SEE OP

You asked for ext4 support so you shall receive. Sorry it took so long. Ran into a few problems with TWRP not having a complete busybox including mke2fs. All is well and should be good to go.

I will be starting on call recording in the next few days.

Hope you guys enjoy.
[EVO Shift 4G Android Development] :
Thanks Dodge,will give it a workout and report back. Thx again !
[EVO Shift 4G Android Development] strapped365:
Thanks for this dodge ext4 is so freaking smooth. I have honestly never seen a smoother phone and im all setup and loving it

Sent from My Team Supreme/MikSupreme Shift
[EVO Shift 4G Android Development] nfinitefx45:
Very good job dodger, fantastic especially after ext4 alignment. Couldn't have asked for better.
[EVO Shift 4G Android Development] crump84:
+ 1 the ext4 kernel is running super smooth. Great work dodge!
[EVO Shift 4G Android Development] jwigley24:
so i flashed the ext3 version the other day, and now i go ahead with the ext4 version, will i see much of a change? what does it really do? and to strapped, since i'm usuing supreme, does this affect anything with using the A2SD version of ur rom?

just curious in finding out the differences between the 2 versions! thanks guys!
[EVO Shift 4G Android Development] alher591:
Yeah i also want to know what this ext4 means
[EVO Shift 4G Android Development] :
If you would like answers to your questions you can get ahold of Dodge on the IRC channel #gen-dev or #sdx-developers.
[EVO Shift 4G Android Development] jwigley24:
cool, thanks...

do you know if we need to wipe anything after flashing the conversion .zip but before restoring the backup?
[EVO Shift 4G Android Development] drob311:
Running the ext4 kernel and its so smooth. Thank you very much for building a kick a$$ kernel. Smooth and stable! Thanks again!
[EVO Shift 4G Android Development] crump84:
Me personally, I didn't wipe anything before the conversion. I flashed conversion > restored nand > wiped dalvik and cache > flashed kernel > enjoy a badass kernel
[EVO Shift 4G Android Development] sdk234:
Fantastic!

+1
[EVO Shift 4G Android Development] strapped365:
It only affects it in a way to make it smoother

Sent from My Team Supreme/MikSupreme Shift
[EVO Shift 4G Android Development] dodgejcr:
There is no difference in the kernel itself, just the optional support for ext4. You shouldnt run into any problems with A2SD but let me know if there is and Ill be glad to find and implement a work around.

Ext4 is the latest linux filesystem. It is better than Ext3 (stock) in both read and write speeds. I dont think benchmarks will change much but people are noticing performance increases. If you want to know more about filesystems, a quick google search will reveal tons more. Its great info to read up on.

Wiping is not necessary. The conversion zip wipes system, data, cache, and devlog which is why you restore the nand. I dont have much experience with CWM and TWRP backup procedures in order to safely do it as one zip but my good buddy joeykrim might help me with that as he knows about the recoveries better than I. Hopefully we can get it down to one zip that will do it all but the current method should be solid untill then.
[EVO Shift 4G Android Development] nfinitefx45:
No the conversion formats to ext4 this is why you need a backup.
[EVO Shift 4G Android Development] sdk234:
Running Mik 1.76 on the ext4 flavor of the kernel. Runs fantastic. Many thanks!!

I understand from a question I started over on Mik's thread that if I flash say an updated version of Mik's rom, I wouldn't need to do the conversion from ext3 to ext4 again after flashing that new rom and before flashing the ext4 kernel --that is, the change to ext4 is permanent.

Could I get into trouble if I flashed an ext3-type kernel - say I flashed a stock rom (with stock kernel built in) -- first would I need to convert back to ext3? Thanks for your help :-)
[EVO Shift 4G Android Development] dodgejcr:
Yeah Im getting that question alot. I will probably write up a FAQ for situations like this

The answer is, If you flash another ROM (sense or aosp) you will not have to revert back to ext3. You will however, have to flash an ext4 supported kernel after the ROM flash in order for it to boot. So in your scenario above, you would download the new update, flash thru recovery and before rebooting, flash an ext4 kernel. If indeed you need to return to stock ROM for say a sprint visit or something, you would need to flash the 'ext3 conversion' zip and then the stock rom.

If you want to try another kernel, converting to ext3 is also necessary. At the moment, there is no other ext4 kernels so you will have to revert back in order for the new kernel to work. Maybe a few of the other guys can get some ext4 kernels out there :D

The same goes with most aosp ROMs. I believe they all use ext4 filesystem so the kernel included in the ROM should mount the filesystem fine. I havent flashed everthing to say if this is true 100% of the time as I mostly stay on stock sense with a few tweaks I put in myself, but as far as I know, all aosp ROMs use ext4.

If there is any exceptions to this, please let me know and I will include the notice in the FAQ I write up later.

I have also received several questions regarding backups and restores. There should be no issues backing up and restoring the filesystems. The backups just pull the data off of the partition and doesnt reformat it as a different filesystem. You should be able to backup and restore normally as if you were on ext3. If for some reason this doesnt work, again, let me know and I will do my best to find any workaround and make sure there is information out there that will ease the process.

I hope this answers any questions but if you arent sure of someting, please post your questions. Dont restrain from posting a 'noob' question in fear of being made fun of or looked down on. That will not happen with me. I try to my hardest to inform users of everything that is happening in order to 1. build their knowledge of how all this works and 2. make sure everything goes smoothly. If you still have questions that you dont want to post, email me at dodgejcr@gmail.com. I will get back to you.
[EVO Shift 4G Android Development] tambourineman86:
Actually a lot of roms include the commands to format system which may actually complicate the conversion process. Cfor example, I applied the conversion zip and then tried to flash nfx's rom, then flashed the ext4 kernel. It booted, but almost all system pngs were "missing" and system fonts were all messed up. Everything was completely functional, just fugly as hell. The best I can tell is that if you flash a rom that formats system, data or cache, you will probably run into problems because the updater script command will format the partition back to ext3. The reason the nandroid backup restore method works is that there is no format command contained, thus leaving your partition in tact. In order to fix my phone I followed dodgejcr's flashing instructions (imagine that).

Also, cwm will format back to ext3 so data wipe and the format commands in the "mounts and storage" section cannot be used unless you are doing a full conversion back to ext3. At least that's the way it seems to me from trying to fix my phone last night at work. If I am wrong, please correct me. I don't want to be responsible for distributing false information.
[EVO Shift 4G Android Development] dodgejcr:
I have not noticed this in my tests. The recovery's 'format' option for the updater-scripts are basically doing a rm -rf command and not actually reformatting the partition from what I have seen. I am no expert in the way the recoveries work but as far as I can tell, they are not reformatting the actual filesystem. Just removing all information in it.

I use CWM and tested both nandroid backup and restore and it works fine. I did not actually test the wipe features. I could be wrong on that instance but I just figured that since the restore did not reformat the partition and just wiped it, that the 'wipe' option did as well. I will test it as soon as I can.

Unrelated: My first test of kingdom actually had the missing png issue and a reflash fixed it all. I assumed it was just a bad flash. That was on ext3 before I ever started working on ext4 kernel. Since then I have flashed several times for random tests and all have gone fine without a hitch.
[EVO Shift 4G Android Development] nfinitefx45:
Ok well the updater script is not changing the format of the ext but the mount points will be incorrect for the ext4. I am actually supprised it even installed as it was trying to mount like this

mount("ext3", "EMMC", "/dev/block/mmcblk0p26", "/system");

and needs to be for ext4

mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/system");

same for all other mounts also

All Devs should create and ext3 and ext4 version of there roms this way it will be up to the people to choose the correct on for there phone.
[EVO Shift 4G Android Development] dodgejcr:
I thought about this as well. I cant force people to change their updater-scripts lol. It's strange that it works...

I think a better way of going about it would be to use busybox mount commands like we see in alot of CM universal zips like their gapps zip since both recoveries have busybox. Something like:

run_program("/sbin/busybox", "mount", "/system");

I think it would be a little cleaner method of mounting universally no matter what filesystem the partition is on. I havent tested it of course, just a suggestion. Developers will obviously use what ever method they choose. I cant be responsible for that :D Just wanted to make it possible to use ext4 if a user chooses too since it was suggested.
[EVO Shift 4G Android Development] nfinitefx45:
Agreed I will check this out tonight, may build my next version of Kingdom this way, Hope to have a release out tomorrow.
[EVO Shift 4G Android Development] dodgejcr:
Awesome. I was reading you were having someone build you an ext4 kernel for Kingdom, if that fell through you are more than welcome to package this up with Kingdom. If you want let me know and I will build you a custom version, or at least explain how to change the 'dodgekernel' in the bash lol.
[EVO Shift 4G Android Development] drob311:
After converting fs we restore a nandroid. Im assuming that is why we did a nandroid before everything, because a restore writes to the partition not looking for ext3 or ext4.... Sorry to butt in...

Yes i agree, the option to choose between ext3 or ext4 ROMS would be gnarly!

edit: you two are super fast typers... Wow... :)
[EVO Shift 4G Android Development] nfinitefx45:
Thanks , I was planning on using your kernel with it, and yes Zenulator was going to build one for me also , but work has been keeping him busy at this time.
[EVO Shift 4G Android Development] dodgejcr:
Precisely the reason. The actual mke2fs command that I have scripted wipes the partition completely. In order to get that information back I found it easiest to just restore a nandroid as im sure it uses busybox to mount the partitions regardless of filesystem type. Maybe I can get a script that will do it all automagically with the help of joeykrim but you should be safe with the current method until then.
[EVO Shift 4G Android Development] drob311:
Im not too worried :) ... I had a moment and an intercept this procedure is child's play compared to the flaming hoops we jumped through to get the crapsung's converted... Awesome work... Good to see the shift community work together as well. Best community in the xda world, i.m.o... Looking forward to more from both of y'all. Thanks to both!
[EVO Shift 4G Android Development] tambourineman86:
Thank you, I'm sorry that's what i meant when i was referring to the updater script. And i returned to ext3 by simply formatting system, data and cache in cwm since i was at work and didnt download your reversion script, dodge. Restored my ext3 rom and kernel and ran just fine.
[EVO Shift 4G Android Development] dodgejcr:
Okay when writing up the FAQ (when every my tired lazy self gets to it) Ill be sure to add that information. Thanks tamb
[EVO Shift 4G Android Development] prboy1969:
Well decided to try out the Kernel with EXT.4 . Must say I am not sorry I did. Uber SMOOTH, and Stable :D . Hellua nice work dodgejcr ;) . Clocked my Shifty all the way to max on every setting :D . Just smooth sailing. Now about that 1.9 Kernel :p
[EVO Shift 4G Android Development] dodgejcr:
Ha! It will be here eventually. Before adding insanity, need to get stability down. Glad you like it.
[EVO Shift 4G Android Development] prboy1969:
Hell yes :) . Smooth as butter, even decent battery life after running it hard. Like 1.8 Performance for regular usage hard. Can't wait for the 1.9, or day I dream 2.0 Kernel. But yes stability must definately come first ;) .

TEAM MiK

Mik Roms Since 3/13/11
[EVO Shift 4G Android Development] Aaargh!:
First time I have used one of your kernels and things are great. Running Supreme Sense with your ext4 version and as of now at 1.6 and 245 smartass. Last rom I used, will not mention names, and another kernel, I could not over-clock passed 1.1. Thanks for the great work.
[EVO Shift 4G Android Development] linkosffl:
Agreed.

______

Supreme since day one.

aka.. Loser
[EVO Shift 4G Android Development] dodgejcr:
Updated OP with FAQ section to help answer the repetitive questions. Let me know if something extra needs to be covered as well.
[EVO Shift 4G Android Development] jesusice:
The FAQs suggest that the conversion zip should be run on AOSP ROMs as well but the OP only refers to Sense. So I can ssume that while the kernel is only for Sense (for now) the ext4 conversion will work on AOSP too?
[EVO Shift 4G Android Development] dodgejcr:
HA! Look at you putting two and two together LOL. Yes while I did make it clear that AOSP is technically using ext3 partitions mounted as ext4 I intentionally left that information out as to keep any confusion to a minimum. You could use ext4 conversion to convert to ext4 and run AOSP as the kernels for AOSP already mount as ext4. It will work fine.
[EVO Shift 4G Android Development] drob311:
This is good to know. Will there be any performance/stability gains by running a legit ext4 with aosp?
[EVO Shift 4G Android Development] dodgejcr:
There should be, but probably very little. Mounting ext3 as ext4 is pretty quick so true ext4 is probably not much faster.
[EVO Shift 4G Android Development] jesusice:
Yup, I can think just don't know anything ;)

And true to your word the ext4 conversion zip worked fine on CM7. Probably placebo but it does feel slightly snappier.
[EVO Shift 4G Android Development] strapped365:
So i know i said thanks for the work already when you first released and everything.....But i have now had the joy of absolutely stressing the system and bashing it and this thing just keeps coming back for more, there is one downfall though(JOKING there is zero downfalls) and that's if I never get another ext4 device(money issues) I wouldnt know what to do with myself let alone what i would do about a phone. The shift already runs great, but since I made the change to ext4 it feels like a brand-new phone all over again!

Sent from My Team Supreme/MikSupreme Shift
[EVO Shift 4G Android Development] blakeatl:
Trying the ext4 out now. Just to make sure....Supreme Sense v7.5 a2sd is ext3 right?
[EVO Shift 4G Android Development] dodgejcr:
It is but you can still use the ROM while on ext4, just have to flash an ext4 kernel after the ROM
[EVO Shift 4G Android Development] blakeatl:
Thanks. I went with the full conversion to ext4.
[EVO Shift 4G Android Development] prboy1969:
A2SD Supreme Sense definately runs noticebly smoother with the EXT.4 Kernel :D
[EVO Shift 4G Android Development] nunook:
I did the ext4 on shiftdeck 1.3 with scary kernel and the write speeds increased but the read speed decreased alittle. about .25-.5mbs on each according to antutu and devicemark, using demand ioscheduler. Im gonna try with noop to see if its any better.

Thanks for the work,
[EVO Shift 4G Android Development] VICODAN:
Nice work dodge. Got a few questions for you... will hit you up on irc.

Sent from my brick
[EVO Shift 4G Android Development] blakeatl:
Very smooth on ext 4. Looking forward to adding more to make this phone better.
[EVO Shift 4G Android Development] travanx:
Being unfamiliar with using Sense. How do you overclock using this Kernel?
[EVO Shift 4G Android Development] blakeatl:
You can use setcpu or antutu. There are others...I've just used those two.
[EVO Shift 4G Android Development] jwigley24:
Install setcpu or nofrills and choose ur governor and min/max speeds from within the app
[EVO Shift 4G Android Development] galaara98:
Wante to pipe in, ext4 sense kernel in SS 7.5 running wonderful.
[EVO Shift 4G Android Development] jesusice:
Still taking requests? Having HAVS or SVS enabled would be cool so we could use Incredicontrol or Vipermod to adjust the voltages.
[EVO Shift 4G Android Development] Cambienta:
This kernel is AMAZING! I haven't set up the EXT4 yet, but that's because I've been having spotty luck with my back-ups, so it makes me nerrrvous. But even without that advantage, this kernel has my phone running like butter on Mikshifted-G 1.76, and I'm underclocking!

I'm just curious, how possible would it be to add extra divisions in future updates? I'm not talking about extra over-clockage, I mean intervals between the ones which already exist? I have no idea how complicated a request this is, but I would be more than happy to make an attempt at it if it's something someone of my level could manage (and if I could be informed/pointed to directions on how XD).
[EVO Shift 4G Android Development] dodgejcr:
Sounds feasible, never figured many people would benefit from this but I dont see it hurting anything.

This is something that has been asked a few times now so it will most definitely be something I will work on. I have been working on 1.6 for a few days including 1.9ghz OC and this just gives me a new excuse for re-working the clock table.

For the guys that have been wondering, I have slowly been working on the call recording and while it seemed simple enough on paper (screen?) actual implementation is not going so well. Im not sure it will be in the next release but I will not give up until it drives me just short of crazy (might not be that far considering my current state). Also, I do have an AOSP kernel floating around for some users, I promised a good buddy of mine that he would have first release exclusive for his ROM. Just an FYI. Thanks for the suggestions, keep them coming :D
[EVO Shift 4G Android Development] jesusice:
FYI: It's well worth the wait ;)
[EVO Shift 4G Android Development] Cambienta:
Is there a chaaance that one of the intervals you add could be the 184, and maybe even one of the 400 or 600 ones (I should have those speeds memorized, but I can't remember the exact...). Obviously I'm just throwing these out there based on my preferences; please feel no pressure on my behalf! especially since this is probably not easy to do!
[EVO Shift 4G Android Development] drob311:
In no way am I answering for dodge, but, its not as simple as just adding the clock speeds... But, if anyone can do it, it would be dodge. :)
[EVO Shift 4G Android Development] dodgejcr:
Ill do some calculations and see where they fit in my clock table. They wont be exactly what you are used to as my values are ones I found are best for me and this kernel, I believe several other kernel developers here are building off of the frequencies that were pulled from someone (Im not sure). I have a few reasons I used the ones I did but mainly they are pretty much equal multiples of a variable which makes it easier for me to use. Ill see if I can add a few steps below 806mhz. Thanks for the suggestion.
[EVO Shift 4G Android Development] prboy1969:
Me and my Shifty can't wait for that 1.9gHz Kernel :D . Want to see how it performs OC'd at 1.9gHz. Should be fun :) . Thanks again dodgejcr , nice work.
[EVO Shift 4G Android Development] dodgejcr:
Updated: SEE OP

Implemented a few more requests including HAVS/SVS support, 1.9Ghz overclock, more frequencies in the clock table and enabled init.d scripts.

I did not add any frequencies below 245mhz in this release as tests were showing me that scaling down and back up was a little on the rough side. I will continue to test and play around with it until I am happy.

I am still working on call recording. Hopefully I will get it figured out.

Keep these suggestions coming, they do not fall on deaf ears.

Hope you guys enjoy.
[EVO Shift 4G Android Development] jesusice:
I'm not sure how it works on Sense but on CM7 on certain kernels (Scary's and Sparksco's) there's an additional setting in Performance Settings for compache percentage. I always kept it disabled but I wouldn't mind still having the option. Enable all the things, right?
[EVO Shift 4G Android Development] dodgejcr:
I messed with compcache a bit with my 2.2 kernel and was not happy with the results at all. If course, this is a whole new source so who know. I will obviously look into it and see how it plays out. Thanks for the suggestion

Also, Im kinda thinking you HAVE to switch back to sense now you have all the requests lol. Or are you one of those lucky fews that have some of this on AOSP? :D
[EVO Shift 4G Android Development] jesusice:
*checks... Well, I do appear to be running a superbadazz 1.9ghz AOSP kernel with call recording and SVS on smartass =)
[EVO Shift 4G Android Development] notsointeresting:
Reallly nice man! Great work!
[EVO Shift 4G Android Development] prboy1969:
Thanks man :D . Flashing now :D . 1.9gHz here I come :D

EDIT:

Smooth and Stable :D . Great work :D . Running 1.9gHz on smartass :D . No heat issues, or reboots :)
[EVO Shift 4G Android Development] bluezr1:
Will this work with mik v1.6?

It's for my daughter phone and she'll only give it up for a few minutes - reason why I don't have enough time to upgrade her phone to mik v1.76.
[EVO Shift 4G Android Development] drob311:
Yes sir... Shouldn't be an issue