yashsingh1/xdaforums huggingface dataset:
[myTouch 4G Android Development] mymeatb18:
I never had any screen flicker on any ROM and it didn't start here either. I'm on aosp and I do confirm heat up and massive battery drain with headphones plugged in.

Sucks cuz I do calls with wired hands free and listen to music while driving around all day but for this ROM have made the sacrifice. Hopefully this issue can be solved one day. But I love the ROM too much to worry about it, just got to dust off the iPod touch. Feels like a dinosaur
[myTouch 4G Android Development] shadowharbinger:
https://docs.google.com/file/d/0Bzf_q79LONzWeE1NVnlnLWF1X28/edit?pli=1 alleviates MOST of the overheating, voice apps work AND the battery life is better. I used it under the AOSP build. I will be testing it under the CM10.1 build later on tonight.
[myTouch 4G Android Development] mybestway:
this is friday he may update the kernel with miui today or tomorrow i think

Sent from my T-Mobile myTouch 4G
[myTouch 4G Android Development] hellmonger:
https://android.googlesource.com/kernel/common.git/+/android-3.0

OH is caused by ioctl... 2 reasons...

MINOR OH due to RAM not being calculated corectly...

Major OH due to HARDWARE JACK not responding with expected responce....

the first is due to bad kernel...

the second is a bug.....

FML..... i need a drink now.....
[myTouch 4G Android Development] coupetastic-droid:
Which mod did you try? The metamorph or flashable zip. I believe for this Rom it would have to be the metamorph method since this Rom doesn't have softkeys settings. Or I might be completely wring and this only works in aokp roms
[myTouch 4G Android Development] jwhood:
I used metamorph it all goes right but after reboot nothing is changed?
[myTouch 4G Android Development] ..Cory..:
From what I'm seeing, the ROM ports are pretty solid. The kernel itself just needs more working on. I wish I could help out but I know ZERO about kernel ****...
[myTouch 4G Android Development] shadowharbinger:
That might be a good thing, though under the CM101 build I noticed worse battery life (1-3% drain every couple minutes). Also under the CM101 build, voice apps do not seem to work. It seems something is using the microphone constantly.

I get "Audio device cannot be accessed, please shutdown any application which is currently using the device" or something like that.

Any one else?
[myTouch 4G Android Development] policeman0077:
aosp is a smooth rom:D

---------- Post added at 01:05 AM ---------- Previous post was at 12:48 AM ----------

aosp is flicking in chrome especially when typing. But default browser works fine.
[myTouch 4G Android Development] mymeatb18:
Is there a way to lock the screen when in a call. I find myself pressing all kinds of things with my face. Unless I actually press the power button.

I'm on aosp
[myTouch 4G Android Development] bas3balman:
I had the same problem last night. I just pulled my phone from my face then when the screen came on I pressed the lock button and it was all resolved
[myTouch 4G Android Development] mymeatb18:
So I guess there is no way of auto screen lock during call?

I've called voicemail while already talking with someone, I've changed time format to 24 hours, and constantly find myself going into settings.
[myTouch 4G Android Development] jwhood:
Cm is merging the weather/calendar back into 4.2 lockscreen i hope when this is merged cnote will provide us with that build??:)
[myTouch 4G Android Development] shadowharbinger:
:fingers-crossed:

I really hope that happens! CNOTE is keeping the MT4G alive and viable!:victory:
[myTouch 4G Android Development] ajbiz11:
Hello,

I just installed the ROM and it works great

The way I installed it I was I had an install of toasted marshmallow v1 -not sure on version #... Anyways, I didn't wipe anything and installed over it

Then I rebooted into system and it was unstable

I rebooted and installed gapps and it became stable after two reboots it is running perfectly

Mic works

Front and back cameras and 720p work

No photosphere

Data calling SMS

I do get a light flash when I touch it when its off...just backlight on a black screen so its really dark grey

Don't know if this helps at all
[myTouch 4G Android Development] jwhood:
Did u install aosp or cm10.1 build 5??
[myTouch 4G Android Development] imabrokendownload:
Curious on how you discovered this
[myTouch 4G Android Development] ajbiz11:
oops...didnt notice the cm10.1 link...i wondered why it didnt have any cyanogenmod wallpaper...i installed AOSP

one question, is photosphere enabled in the AOSP rom?
[myTouch 4G Android Development] jwhood:
It wont work on are phone cause it doesnt have a gyroscope,correct me if im wrong anyone??
[myTouch 4G Android Development] imabrokendownload:
Gps status can detect pitch and yaw so I don't really know
[myTouch 4G Android Development] THEindian:
you are correct
[myTouch 4G Android Development] my2sense:
I'm on the AOSP rom and I can't seem to adjust brightness. Tried it in settings, brightness app, auto, manual and no change. It looks like it's always at maximum brightness. Anyone else have this issue?

As always, a big thank to cnote and all the other developers for keep our phone alive and current!
[myTouch 4G Android Development] EMcTx:
I installed the aosp , and it seemed to work great except for the bluetooth. I could pair, but not connect to my digital cordless bluetooth phone. This is a dealbreaker for me, because I prefer to talk on the cordless phone when I can, since it keeps the glacier from getting dirty as quickly and it's easier to look up something on the phone at the same time. This connection works great on the Toasted Marshmallow ROM. I unzipped both ROMs on my computer, and it looks like the bluetooth files in the aosp ROM are older than the ones from the Toasted Marshmallow ROM. Would replacing the bluetooth files from aosp with the Toasted Marshmallow ones work to fix the connection issue? I really would like to have a newer kernel to use until the Toasted Marshmallow is updated.
[myTouch 4G Android Development] mybestway:
look at this kernel

Sent from my myTouch 4G
[myTouch 4G Android Development] mybestway:
no over heating with headphone~

Sent from my myTouch 4G
[myTouch 4G Android Development] coderzs:
From where you get that kernel ?:confused:

Отправлено с моего MyTouch 4G через Tapatalk
[myTouch 4G Android Development] leo32x:
Does mic work in apps?
[myTouch 4G Android Development] gkpk:
I just want to thank CNote and all who made this possible....awesome work.

I installed the 10.1 version about 3 days ago and no screen flicker whatsoever, verrry smooth rom.

But mic is a no go, gives some kind of error.
[myTouch 4G Android Development] cnote74:
Yes if you would please share the kernel.
[myTouch 4G Android Development] mymeatb18:
Would a kernel that works on 4.1 work for 4.2
[myTouch 4G Android Development] leo32x:
Yes.
[myTouch 4G Android Development] THEindian:
Please share that kernel
[myTouch 4G Android Development] coderzs:
Cnote build 6 ready or still have bugs with gallery ? Can you share ?

Upd. That kernel is from desire s

Всех с наступающим :p

Отправлено с моего MyTouch 4G через Tapatalk
[myTouch 4G Android Development] cnote74:
I was hoping to have am updated kernel but if I cant get one I will release it.
[myTouch 4G Android Development] coderzs:
update ... !!!!!!!!!!!!!!!!!! CNOTE CHECK PM !!!!!!!!!!!!!!!!!!! I FIND THE new rom with new KERNEL !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

with love from Ukraine
[myTouch 4G Android Development] mybestway:
i found it here bbs.gfan.com/forum.php?mod=viewthread&tid=5587561&mobile=yes

Sent from my myTouch 4G

---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------

but i dont have the permission to use the kernel and pm zeng to get the permission is a good idea

Sent from my myTouch 4G

---------- Post added at 12:23 AM ---------- Previous post was at 12:19 AM ----------

i tested the new kernel in cm10.1 build 5 turned a com.android.phone fc. i think something need to modified. but it worked very fine in 4.1.2

Sent from my myTouch 4G

---------- Post added at 12:28 AM ---------- Previous post was at 12:23 AM ----------

yes it's the download page. i sharerd is the rom released page. it said “donnot use the kernel unless you get the permission”

Sent from my myTouch 4G
[myTouch 4G Android Development] coderzs:
Do you have problems with camrecording ?
[myTouch 4G Android Development] mybestway:
480 and 720 all work fine on 4.1.2

Sent from my myTouch 4G

---------- Post added at 12:45 AM ---------- Previous post was at 12:44 AM ----------

of cause it will work fine on 4.2 like the aosp 4.2 here

Sent from my myTouch 4G

---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------

sorry no test yet

Sent from my myTouch 4G
[myTouch 4G Android Development] coderzs:
In MIUI ROM camrecorder force close . Mic work in sound recording
[myTouch 4G Android Development] mybestway:
sorry i just test the kernel so let you spend some hours for waiting

Sent from my myTouch 4G

---------- Post added at 12:53 AM ---------- Previous post was at 12:49 AM ----------

the kernel support 480 720 recordind if there is fc i think it's rom related

Sent from my myTouch 4G
[myTouch 4G Android Development] coderzs:
Mic works great in apps !!!!! tested on sound recording and google now :o

p.s hey cnote .. cm10.1 build 7 is up !!!))
[myTouch 4G Android Development] cnote74:
You are porting the same ROM as I was so I don't need to port it anymore.
[myTouch 4G Android Development] coderzs:
MMM ??? I ported cm10 rom ... not cm10.1
[myTouch 4G Android Development] cnote74:
I thought it was cm10.1 sorry.
[myTouch 4G Android Development] coderzs:
))) So .. what about update ??? ))
[myTouch 4G Android Development] cnote74:
Just downloaded it will port it over soon and release it very soon.
[myTouch 4G Android Development] ..Cory..:
Wait, so about this kernel... this just came out of no where and its compatible??
[myTouch 4G Android Development] mymeatb18:
So with this new build and kernel everything should be working???

If so will be changing from the aosp to cm10.1
[myTouch 4G Android Development] jwhood:
Thanks bro this rom is great already cant wait for build 7 too get out the oven!!!:)
[myTouch 4G Android Development] cnote74:
Having to repair grub so I can port it.
[myTouch 4G Android Development] cnote74:
On it now gallery works cm added a few new things, Bluetooth if it doesn't connect right is an upstream issue not a a porting fault. App kill button is finally added into it.
[myTouch 4G Android Development] simplyrafa8:
Hey cnote, I clicked on a "donate to me link" earlier but the gmail said blindndumb. Is that your gmail? Just want to make sure I'm donating to the right person! :)
[myTouch 4G Android Development] cnote74:
Nope mine is in my signature. androidinsomnia@gmail.com
[Verizon Samsung Galaxy S III] Rath1on:
Envy Kernel
​

Kernel Purpose

This was previously the Galaxy KOR.

Must there be such a difference in perspective between stock and custom? My objective is to squeeze everything there is to squeeze out of what would be expected of a proper "stock" kernel. There is no required user input, everything is defaulted as it should be. The TouchWiz kernel is built on the VRBMB1 platform for this reason. Think of this kernel as an augmentation of the stock.

Kernel Features and Specifications

Based on VRBMB1 source code.

Patched to the latest linux kernel (v3.0.70).

Used the linaro toolchain built with gcc 4.7 (13.02).

Removed some unnecessary features.

ROW scheduler (v4) defaulted.

Implemented urgent request handling.

Integrated a "stock" 256mhz/1.62ghz cpu freq table (see 2nd post).

Added NTFS r/w support.

InteractiveX V3 governor added (thanks imoseyon).

Updated lowmemorykiller values.

Ondemand governor from CM10.1 defaulted.

Lightened kernel modules and memory resources.

Ramdisk optimizations.

420Mhz GPU OC applied to high frequency.

Imoseyon's USB Fast Charge added.

PegasusQ governor added.

Not Working

Nothing that I'm aware of.

Closing Statements

This is my first kernel. The more I get into it, the more I appreciate and enjoy working on this stuff and I have every intention of making this a priority in my life. Looking around at development, I see I have much to learn (thankfully). I imagine, as time passes, my efforts will change and, with that, so will my kernels. Therefore, I cannot promise the best there is at any time, only the best I can offer at that time. And that, my friends, is where the fun lies.

Anyone is free to add this kernel to their ROM. Just be sure to give credit and let me know so that I can check out your work. :D

Source.

Special thanks to Yank555 for helping me out on one or two or several occasions.

Thanks to imoseyon for letting me use the InteractiveX governor from his lean kernel.

Thanks to the Cyanogenmod team for their awesome source code.

Thanks to the linaro team for their toolchains and compilers.

Special thanks to remf4i. RIP, my friend.

Cheers,

Rath

PS - Downloads and stuff in post #2.
[Verizon Samsung Galaxy S III] Rath1on:
Downloads

Stock TW LK3 Kernel

Envy Kernel r1 (3/26/2013)

Instructions

Flash kernel in recovery.

Wipe cache.

Wipe Dalvik.

Fix permissions.

Relevant Information

Everything is defaulted

As stated in the OP, this kernel is principled on stock functionality. Like Samsung and Google kernels, there is no necessary user involvement. The proper scheduler (ROW), governor (ondemand), and cpu clocks (1.62Ghz) are defaulted in the kernel. Just flash and enjoy. That said, you can always use a CPU app to get some control if you like. Imoseyon's interactivex governor is in there too.

New "stock" CPU frequency table

The 1.62ghz comes at a much lower power cost with the frequency/voltage tables I have set. All phones (so far) have been able to run 1.62ghz with the same voltage needed for 1.512ghz (stock). I have applied this and adjusted down the rest of the voltages accordingly. I have not added voltage control and will likely not.

There is also an adjustment to the low end frequencies. 384Mhz has been clocked to 256Mhz and voltages have been lowered.

The ROW scheduler

As you may know, the scheduler assigns work to the CPU and hardware. Most schedulers were developed to work on desktop kernels that use hdds and different architectures. Unlike desktops, our phones use flash memory. The ROW scheduler was designed to optimize scheduling on flash memory devices.

USB Fast Charge

To use imoseyon's usb fast charge script, you must have BusyBox installed. See his thread for more details.

To turn it on, type in terminal emulator: ffc. Off is the same command. Remember, to give the terminal root access you need to type: su.

Flashing and settling

Keep in mind, kernels need time to "settle" in place. Especially after you just wiped the cache. After your first boot up on the new kernel, use the phone until it loads 100% (as in no "it's still booting up lag" which would be like 5 minutes) and then reboot. Sometimes you don't get optimum usage until after a battery charge or overnight.

For Those Using 64GB SDcards

Those 64GB sdcards are formatted to exFAT by default. exFAT is owned by Microsoft and licensed for Samsung to use. However, Samsung cannot release the exFAT support in their source codes because they are proprietary. There's nothing I can do about that. All you can do is format the sdcard to a supported file system. Plug your phone into your computer, get all your files off the sdcard, and format it to fat32. I have added NTFS support to the kernel, so that is also an option. Neither does fat32 nor NTFS suffer the performance of the cards. With fat32 however, you are limited to 4gb per file.
[Verizon Samsung Galaxy S III] Rath1on:
Galaxy KOR Changelog

v1.0

Initial release.

v1.1

Rebuilt from the ground up on LK3 source code.

Lots of bad coding fixes on my end (I'm getting better at this; I promise).

Added interactive and conservative governor.

Added BFQ hierarchical support (basically more control for the BFQ scheduler.

v1.2

Implemented the undervolt and overclock table.

Removed KSM support (unneeded).

Enabled the block-io cgroup controller for use with BFQ.

Fixed the stupid naming convention thing on the past kernels (the -00009-asdlkfnasd).

v2.0

Fixes. Fixes everywhere.

Readjusted the slow and nominal PVS clock tables for stability.

Trying out some entropy related things (it won't hurt anything even if it's not effective).

Added NTFS support and experimental exFAT support (I'm going to need to some people with exFAT sdcards to help).

More fixes.

Edited the OPs for relevancy.

v2.2

Reconfigured the toolchain and binaries.

Rebuilt linaro with GCC 4.6 instead of 4.7 for stability reasons.

Some optimizations for less lag and more responsiveness.

v2.3

Added the InteractiveX governor from the lean kernel.

Dove into the ramdisk a little.

Added an init.d script to set the minfree values (I will need feedback on this).

Reconfigured the BFQ scheduler.

v2.6

Merged latest linux kernel v3.0.59.

Reconfigured the linaro toolchain (hopefully for the last time).

Modified the voltage tables.

Removed the minfree tweak (it may have been the cause of some people's battery drains. The stock lmk values will suffice).

Patched up some code.

Changed compression mode to LZMA.

v2.7

Merged linux-v3.0.60.

Allotted more L2 cache to 1.62Ghz.

Finalized some optimizations.

Re-implemented the minfree tweak.

v3.0

Started from scratch (getting my github in proper order).

Patched up branches at a time to Linux 3.0.61.

Merged the ondemand governor from CM10.1.

Defaulted the ondemand governor.

Lightened up the kernel modules.

Freed up unnecessary memory resources.

Decided that kernels aren't the place for minfree tweaks (especially via script).

v3.1

Rebuilt with latest linaro release 13.01.

Minor code changes.

Further kernel memory tweaking.

New naming scheme implemented.

v3.2

Merged Linux 3.0.62.

Added the ROW scheduler; updated it; defaulted it.

Vamped the block layer for urgent request handling.

Removed BFQ and CFQ for now (need to fix coding issues with new block layer).

Optimized the VRBLK3 ramdisk.

Added linaro gcc optimization flags.

v3.3

Flagged more gcc optimizations.

Added imoseyon's USB fast charge script (be sure to thank him!).

Set the "high" GPU freq to 420Mhz instead of 400Mhz.

I kept the slow and nominal GPU freq at stock. There should be no more than standard power draw.

Freed more kernel memory resources.

v3.4

Patched up to Linux 3.0.66.

Further optimizations to building code.

Further memory resource optimizations.

Envy Kernel Changelog

r1

Patched up to Linux 3.0.70.

Updated linaro toolchain 13.02.

Patched VRBMB1 source code and ramdisk.

Added pegasusq governor from international s3.

256Mhz cpu freq edit and undervolt.
[Verizon Samsung Galaxy S III] cell128:
Just as I was snooping around here looking for a kernel :D
[Verizon Samsung Galaxy S III] remf4i:
Gonna try it now bro thanks for your work
[Verizon Samsung Galaxy S III] epicroot:
Ruining good so far
[Verizon Samsung Galaxy S III] Rath1on:
Great! Let me know if anything seems amuck. I've been using it on Rem's Executioner ROM and everything seems good. Be sure to set the BFQ scheduler. It should be defaulted, but there's always other factors.
[Verizon Samsung Galaxy S III] dbornack:
That's exactly what I'm running.. Do you know if I'll have issues with the CPU clock settings sticking? On Executioner 2, I can't get them to stick on a reboot.
[Verizon Samsung Galaxy S III] cell128:
I use system tuner pro on cleanrom 5.5.1 I can't find how to check on schedulers should I use a different kernel manager app?

Edit: never mind I think I found it. Mine was set at cfq. What's the difference?
[Verizon Samsung Galaxy S III] Stran93r:
This is awesome to see! Gotta love seeing more and more development for our beloved S3!
[Verizon Samsung Galaxy S III] jucytec:
isn't Rath spelled with a W? Wrath?

which would make this a Kow Kernel.

I clicked on this thinking this was a Korean Kernel... lol.

나이스!
[Verizon Samsung Galaxy S III] Rath1on:
It depends on how I set up the clock table. We'll see.

You can look up the differences between schedulers with some Google. BFQ aims at divided workload using hierarchy scheduling. I think I'm going to pair it with a form of the interactive governor.

;)

It's a play on the word core and a play on my name at the same time. I thought it was clever. :(
[Verizon Samsung Galaxy S III] jucytec:
It is... :good:
[Verizon Samsung Galaxy S III] dbornack:
Issues I've been able to reproduce:

- Reboot when video is initiated within an app like Tango, GChat, etc.

- CPU Control FCs 2-3 times before I can get in to check CPU settings

On Executioner 2.0
[Verizon Samsung Galaxy S III] Rath1on:
What are your using to check the CPU settings with? I use ROM toolbox and have had no issues.

I'm not sure what's going on with the video. I don't use video chat, so I can check. Do any other kernels work for it?
[Verizon Samsung Galaxy S III] dbornack:
I've had good luck with CPU Control Lite for a long time on multiple phones. But I can give another one a shot.

I've just uses the stock and IMO kernels so far. Those don't give me any issues.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Phone boots up and runs for a minute or so then resets... boots up and runs for a minute or so then resets again... Just stays in that cycle... Tried doing a clean install... Tried flashing stock kernel then KoR... tried installing with absolutely no CPU apps n the phone... Not sure what else to try... Any thoughts?

Samsung Galaxy SIII powered by CleanROM 5.5.2
[Verizon Samsung Galaxy S III] countryfolk07:
I got the same thing on this. Constant reboots. Doing nothing. I tried.
[Verizon Samsung Galaxy S III] Rath1on:
Alright, guys. Thanks for the info. I'm looking into it. Running Clean ROM? I'll flash it and check it out. I've been itching to get back to work on it, but this week is a little here, there, and everywhere.

Are you running Clean ROM as well?
[Verizon Samsung Galaxy S III] countryfolk07:
No. I am stock odex at the moment.
[Verizon Samsung Galaxy S III] AegonTheDragon:
This is a TW kernel, correct?
[Verizon Samsung Galaxy S III] Wyvern49:
Yes it is a TW kernel.
[Verizon Samsung Galaxy S III] PsiPhiDan:
Re: [KERNEL][3.0.60][TW JB] - Galaxy KOR v2.7 - [1/22/2013]

Your "edit" makes me very happy. :D

CAN'T WAIT!!
[Verizon Samsung Galaxy S III] Rath1on:
I'm expecting to get a build up today if everything cooperates and such. However, since that rarely happens, it may be tomorrow.

It may be a separate thread, though. The AOSP and TW sources are different, it's not a port. So, they're going to have different changelogs and version numbers (hence the different thread).
[Verizon Samsung Galaxy S III] Rath1on:
I have a working AOSP release now. It's, more or less, the same as the TW Galaxy KOR, just built with CM10.1 source and not Sammy's.

Galaxy KOR AOSP v1.0 can be downloaded here.

v1.0

Initial release.

Rebuilt with CM10.1 kernel source.

Merged latest linux v3.0.60.

Merged everything from TW Galaxy KOR.

No minfree for AOSP right now.
[Verizon Samsung Galaxy S III] PsiPhiDan:
Re: [KERNEL][3.0.60][AOSP/TW JB] - Galaxy KOR - [AOSP v1.0][TW v2.7] - 1/24/2013

Awesome!

I'm trying out a new kernel today, but once I get a good feel for it I will test out your new AOSP one! Thanks for posting this!
[Verizon Samsung Galaxy S III] Rath1on:
I think AOSP has WAY better battery life than TW. I left the phone alone with wifi and the radio on for 2.5 hours and it dropped 3%. Is AOSP always like that? I was running a self-compiled CM10.1 with v1.1 (not uploaded yet) of the kernel. But I was getting similar battery life on stock liquid ROM/kernel, too.

In any case, I'm working diligently on this ROM. I want to get an alpha build up soon, but there's still a long road ahead.
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [KERNEL][3.0.60][AOSP/TW JB] - Galaxy KOR - [AOSP v1.0][TW v2.7] - 1/24/2013

Yeah, AOSP is like that for me. I left my phone alone for 10 hours and it only went down 8%:P but I was using Lean Kernel at the time.