yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aperseghin:
D-loading now and installing. \

FYI i tested test-1 and it was working just fine.

Excellent work and attention to the issue.

Thanks !
[Samsung Galaxy Nexus] normanx:
I wasn't having any issues at all..... Deep sleep of 97 percent.... With 4.0
[Samsung Galaxy Nexus] tiny4579:
What ROM though? If you're on CM10 or any Android 4.1 ROM it should be ok.
[Samsung Galaxy Nexus] slider112:
Deleted.
[Samsung Galaxy Nexus] normanx:
CM10.0 foot in mouth again....
[Samsung Galaxy Nexus] tiny4579:
In that case don't upgrade to 4.0.1 or you may find yourself with broken Bluetooth.

Does MAP (message access profile) work on CM10? If so, I might go back to it. I don't really have anything I like better in 4.2 itself but there are a few nice features like with MMS. I might just pull the 4.2 MMS into 4.1 and have what I want.
[Samsung Galaxy Nexus] BOY_:
Tiny, which test did you make official? I installed the test from last night and even though I'm still getting a lot of wlan wakelocks, I didn't have nearly the battery drain today that I've been plagued with the last month or so. Kudos!
[Samsung Galaxy Nexus] tiny4579:
The only one that allowed deep sleep for people. The first one.
[Samsung Galaxy Nexus] tiny4579:
In case anyone wants it, I have a JB 4.1 version of V4.0.1. It should work properly on Jellybean 4.1 as I've reverted the tuna bluetooth changes back to the 4.1 state and I know 4.0 worked with JB 4.1. Let me know if there's any issue. I'd like to make two releases going forward based on the 4.2 code as this allows 4.1 users to still be happy and me to deprecate the 1.x branch.

I forgot to mention I uploaded it to the regular location.
[Samsung Galaxy Nexus] SirBindy:
I wouldn't mind trying the 4.1 version of 4.0.1.

I was under the assumption that those of us on 4.1.x HAD to stick with the 1.xx versions of your kernel.
[Samsung Galaxy Nexus] tiny4579:
Well, you assumed correctly. That has been the case for a while due to bluetooth being broken on 4.1. Since I found the commits that break Bluetooth on 4.1 when using the newer kernels, I reverted them. I'm using two branches this time due to the deep sleep issues this revert caused on 4.2. The issues shouldn't be present on 4.1 though.
[Samsung Galaxy Nexus] kmcrane:
Just a quick reminder... Zram on or off?
[Samsung Galaxy Nexus] ba_hamilton:
Running Tiny's ROM with tinys kernel. Just had to try it. I think I'll be sticking with this combo for a while.

I notice that there is a new build out but can't really tell if it applies to toro, even though some ROMs have already updated. Does it really apply?
[Samsung Galaxy Nexus] Txwolf1980:
Tiny's rom?

I thought you were running cm, Tiny.
[Samsung Galaxy Nexus] tiny4579:
You mean the r1.2? It is global but updates are for mako.
[Samsung Galaxy Nexus] tiny4579:
I am running CM10.1. I assume he means my CM10.1 builds.
[Samsung Galaxy Nexus] Txwolf1980:
Ok. I was wondering. I scanned through the threads, and didn't see anything. Thanks for the clarification
[Samsung Galaxy Nexus] tiny4579:
The ROM is updated to 4.2.2_r1.2 by the way. I merged CM Thursday night or Friday after the 4.2.2_r1.2 merge took place.

Latest frandom script for those interested - I put mine in /data/local/userinit.d:

#!/system/bin/sh
if [ -c /dev/frandom ]; then
chmod 666 /dev/frandom /dev/erandom
mv /dev/urandom /dev/urandom.ORIG && ln /dev/erandom /dev/urandom
mv /dev/random /dev/random.ORIG && ln /dev/frandom /dev/random
pkill system_server
fi
[Samsung Galaxy Nexus] joqsan:
Is the latest kernel 4.0.1 for 4.2.2 jb? I'm confused

Atom v13

AK Kernel inside

JG-Wentworth
[Samsung Galaxy Nexus] nitsua98:
Yes
[Samsung Galaxy Nexus] kmcrane:
On? Or off?
[Samsung Galaxy Nexus] tiny4579:
Yes but there's also 4.1 version as well.
[Samsung Galaxy Nexus] tiny4579:
What do you mean? You want me to tell you which your should use?
[Samsung Galaxy Nexus] ATTACK:
It's your choice if you want to use it or not. I use it. (Zram-on)
[Samsung Galaxy Nexus] joqsan:
I tried to flash Tiny 4.0.1 and i got a bootloop so the search continues

Atom v13

AK Kernel inside

JG-Wentworth
[Samsung Galaxy Nexus] tiny4579:
Sounds like the problem is on your end or the roms fault. My kernel is not picky about the rom and doesn't have any custom files that would cause an issue. Though if you're kernel jumping and not providing the dev any helpful feedback you probably won't even check back on my response. I have many users using this kernel without issue.
[Samsung Galaxy Nexus] kmcrane:
I remember reading a while back and on different kernels that zram is good and have it on.. But it seems to be off whenever I wipe and flash.. So I was just confused and was asking what was preferred.

No big deal, just curious.
[Samsung Galaxy Nexus] tiny4579:
That would be because it defaults to being off. This is a debated topic on android. Personally I think it shouldn't be used but if memory starts to become an issue I could see it being useful.
[Samsung Galaxy Nexus] kmcrane:
Ok.. Default is off. Good enough for me.

Thank you.
[Samsung Galaxy Nexus] zoomy942:
Hi. I'm trying this kernel with cm10. Good job.
[Samsung Galaxy Nexus] normanx:
build.board: tuna

build.bootloader: PRIMELC03

build.brand: Google

build.cpu_abi: armeabi-v7a

build.cpu_abi2: armeabi

build.device: toro

build.display: cm_toro-userdebug 4.1.2 JZO54K eng..20121113.080038 test-keys

build.fingerprint: google/mysid/toro:4.1.1/JRO03O/424425:user/release-keys

build.hardware: tuna

build.host: cyanogenmod

build.id: JZO54K

build.manufacturer: Samsung

build.model: Galaxy Nexus

build.product: mysid

build.radio: unknown

build.serial: 0149AD700101400D

build.tags: test-keys

build.time: 1352822468000

build.type: userdebug

build.user: unknown

version.codename: REL

version.incremental: eng..20121113.080038

version.release: 4.1.2

version.sdk_int: 16

04-21 21:58:06.630 F/libc (8900): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 8932 (WebViewCoreThre)

04-21 21:58:43.935 F/libc (8957): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 8990 (WebViewCoreThre)

Tiny any idea what this is... Since upgrading to 4.0 running CM10 when I click on my browser it starts to load and closes. Then when I click it again it loads right up.
[Samsung Galaxy Nexus] zoomy942:
Holy crap this kernel us fast
[Samsung Galaxy Nexus] Alton (Halo 2):
Hmm? Tiny ur kernel doesn't boot for purity 5.3.1
[Samsung Galaxy Nexus] tiny4579:
Ask them what they changed that messes with kernels. I can't think of anything.

I responded to someone saying it wouldn't boot on atom and they haven't gotten back to me yet.
[Samsung Galaxy Nexus] tiny4579:
I actually just switched back to cm10 last night running my 4.0.1 kernel. No issues loading browser. Above looks like a logcat but not very complete.

This isn't kernel related by the way.
[Samsung Galaxy Nexus] Mystique:
Hey all,

Fwiw; PA here, using settings below and getting amazing battery life and responsiveness.

No problems with anything..

Latest 4.0.1
[Samsung Galaxy Nexus] zoomy942:
So far. 350 1350 interactive and not a hint of screen redraw
[Samsung Galaxy Nexus] KommodoreHeinz:
Maguro user here.... Tried both 4.0.1's on PA 3.15. Wiped delvik and cache but got the Google screen bootlooping.

I read that it was working on the maguro. :confused:
[Samsung Galaxy Nexus] tiny4579:
Can you get into adb to get a logcat?

There's no reason it won't work on Maguro. Tuna kernels work on both boards since 4.03.
[Samsung Galaxy Nexus] KommodoreHeinz:
Unfortunately ADB does not recognize the phone is connected. ADB does work after flashing a different kernel.
[Samsung Galaxy Nexus] tiny4579:
Bad download?
[Samsung Galaxy Nexus] KommodoreHeinz:
MD5's check on both.. Ill try another download later on today. Thanks.
[Samsung Galaxy Nexus] tiny4579:
Even adb reboot recovery?
[Samsung Galaxy Nexus] 00negative:
I compile jellybeer for toro and had an issue with your latest. It went into a boot loop after I switched to it. But I was coming from anarkia's latest experimental and I think purity uses his kernels as well. Not sure if there is some settings or scripts that conflict each other that get left behind during the change over or what but might look into it from that angle.
[Samsung Galaxy Nexus] EvilDobe:
If I remember correctly anarkia uses his own ram disk & if you are leaving his kernel is is recommended highly that you re-flash the ROM & then a new kernel otherwise it causes bootloops.
[Samsung Galaxy Nexus] 00negative:
Ah there you go. Think purity is compiled with ak so they wouldn't be able to do that.

Edit: maybe purity doesn't use ak anymore didn't see any mention of it in their op. So they maybe able to reflash rom
[Samsung Galaxy Nexus] jekern77:
Tiny...amidst all of the complaining and drama...let me just say thanks for all of the work you put into this! Love this kernel.
[Samsung Galaxy Nexus] tiny4579:
Logs in any way possible are helpful. I can't test every rom. If the dev messes with the ramdisk it may cause funkiness. Could always try flashing LeanKernel then mine. My kernel will always use the roms ramdisk so if there is an incompatibility there flashing the rom again won't help.
[Samsung Galaxy Nexus] 00negative:
Double post

---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------

I got it working on jellybeer on a semi clean install. So must of been what evildobe had mentioned. I can recreate and get a log if you want one though

Do you compile your kernel in your cm builds? Or you use the cm stock? Any tips for linaro compiles? Mine get stock at whatever kernel source I am trying to use
[Samsung Galaxy Nexus] tiny4579:
Neither. I use a prebuilt. The kernel makefile needs to be updated to work with the linaro toolchain. The best linaro source I found is dri84's thread on linaro.

I still need to post instructions on linaro but it just may make people more confused.
[Samsung Galaxy Nexus] 00negative:
OK. Figured there was something in there that needed changes just wasn't sure what. I think I have read through that, at least part of the thread, so may need to go back and look at it.

Put it out there, there aren't many threads on actually setting it up. Might help others and improve your setup along the way. The different flag settings is something else I am still reading info on so I can better understand them.
[Samsung Galaxy Nexus] ashclepdia:
I was going to mention this and of course you beat me to the punch.

One thing I see mention all the time is "flashing a reset kernel"(usually people say a stock boot.IMG or reflash ROM) to get past/fix boot loop issues. But very rarely do I see mention of using a different kernels ramdisk.

If the ramdisk that came with a ROM is incompatible reflashing the ROM of course wouldn't work. So the next best thing is to try another kernel(lean/Franco off top of my head)

Actually, this is something that I enjoy playing with. I purposely install a different boot.img before an "any kernel" update zip just to see how the combinations work/run on my device. Right now I'm using your kernel, on Franco's ramdisk, on elementalX ROM. And its Very nice.

I will be switching to the lean kernel ramdisk later today I think though. Only because I know on my device that imoseyon's ramdisk with your kernel has always produced AWESOME results on my device. Aaannnd now I'm starting to ramble lol.

Thanks for the great kernel! (AND FOR FIXING MY UNKNOWN IP ADDRESS ERROR ON WITH IT!)
[Samsung Galaxy Nexus] modernbummer:
Tiny, running 4.0.1 on Slim Bean 4.2 and it is working very well with stock settings. Thanks for your work.
[Samsung Galaxy Nexus] KommodoreHeinz:
Nope. I get no devices while in the Google screen boot loop. I'll try on a fresh install when an update comes out for my rom
[Samsung Galaxy Nexus] :
Tiny bravo.

I used to have a DINC and used chads kernels and loved them. Then you took over and loved them. I then retired my DINC for GN and when I saw you on the boards I was so happy. The latest version of your kernel is a masterpiece. My phone has never been so fast. Thank you for all your hard work.

Martin
[Samsung Galaxy Nexus] zoomy942:
Love the interactive gov and screen off max. Thats a nice touch.
[Samsung Galaxy Nexus] Mystique:
Hey tiny..

How do you run your kernel?

What do you use to tweak your settings?

And what do you tweak?
[Samsung Galaxy Nexus] tiny4579:
As requested, there is now a build of 4.0.1 that uses the older WiFi drivers.

Now pay attention to the zip file you download as there is a build for Jellybean 4.2.x with the new drivers, the regular build, but there is also a build for Jellybean 4.1.x with the new WiFi drivers and a build for Jellybean 4.2.x with the old drivers.

These special builds are appended -jb41 and -oldwifi respectively. The standard kernel for Android 4.2.x with the new drivers is designated with -newwifi.
[Samsung Galaxy Nexus] KommodoreHeinz:
Update: fresh install of PA 3.16 and newest newWiFi kernel works perfectly. No more boot loops or issues. :)
[Samsung Galaxy Nexus] tiny4579:
The New Wi-Fi kernel is the same released one that has been out so I bet the clean install fixed it for you.
[Samsung Galaxy Nexus] zoomy942:
Great final (?) Kernel tiny. I bounce around but always come back.

Using the ROM ramdisk is my favorite feature. Nice work.
[Samsung Galaxy Nexus] artjef:
I hope even though Tiny has a HTC One he will continue to make kernels for the Galaxy Nexus. :D
[Samsung Galaxy Nexus] zoomy942:
I remember him saying this kernel was pretty much exactly how he wanted it. So not a dead kernel per say. Just a solid final version. And I'll agree. It works great.
[Samsung Galaxy Nexus] JonBsbB:
Anyone one using this kernel with the cm10.1 rc1? what kind of Battery life on a lite/moderate use, bout 75% wifi connection, and no slim to non 4G
[Samsung Galaxy Nexus] jekern77:
Didn't try with RC1, heard horrible things about battery life with it. However, RC2 with Tiny's latest...is...epic. Only on day 2, but NO issues.

Now if only I could somehow get a Tiny kernel for my N7...my world would be complete...*hint* *hint*:D
[Samsung Galaxy Nexus] fcisco13:
Wish i could help but my use is moderate/lite to semi-moderate/ultra-semi-moderate-lite.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] TMFGO45:
Fantastic. That's how it's done everybody!

Galaxy Nexus+Baked+Lean+TWRP=BOOM SHAKALAKA
[Samsung Galaxy Nexus] tattedupboy:
What are the recommended trickstermod settings for for this kernel?
[Samsung Galaxy Nexus] tiny4579:
Try default. There's a reason it exists as it works. In other words, try leaving it alone and not change wig trickster.
[Samsung Galaxy Nexus] normanx:
This is just the best...
[Samsung Galaxy Nexus] tiny4579:
Test build with a really neat feature (USB fast charge can be used with MTP). Hopefully music performance is better. New wifi version only for now.

tinykernel-4.1.0-newwifi-test.zip - 3.54 MB
[Samsung Galaxy Nexus] parkson:
Can anyone confirm if the patch works? It flopped on AK exp
[Samsung Galaxy Nexus] zoomy942:
Its installed. I'll report back in a few hours.
[Samsung Galaxy Nexus] tiny4579:
Nevermind, I found it. Since you're saying it flopped, do you have any information about why it flopped?
[Samsung Galaxy Nexus] parkson:
Tried it myself, and others reported the same. With FC enabled, file transfer works, but phone still charges at USB rate

[edit] just noticed he released another version that supposedly fixes fix FC.
[Samsung Galaxy Nexus] Citizen_Snips:
AFAIK, that patch was added to v255 and it was pulled out of v256. Reasoning is that it broke fast charge (would only charge @ USB rate).

So I think it was removed, not fixed. Don't quote me on that though. Going to give tinys a go and see if it works
[Samsung Galaxy Nexus] laur3n.newm4n:
I don't understand the difference between "old wifi" and "new wifi". Could someone please try to explain the difference between the two sets of drivers?
[Samsung Galaxy Nexus] zoomy942:
In the simplest sense old WiFi let's you utilize wep. New WiFi does not
[Samsung Galaxy Nexus] tiny4579:
That makes it sound like you should always use old. But that statement is correct. The New Wi-Fi kernel uses WiFi drivers from the 3.4 kernel which have better performance and battery life for me but don't work in WEP security. Unless you need WEP go with new. If you need WEP use old.
[Samsung Galaxy Nexus] artjef:
Remember that WEP is being phased out and it will be dropped from all new drivers during the coming year.
[Samsung Galaxy Nexus] n0yd:
I read the entire OP and specifically the changelogs. I didn't see a mention of him adding the patch HERE which enables fast charging while still keeping USB access (MTP/MHL) enabled. I saw in the thread for the kernel patch that tiny showed interest and said he would probably include it in his kernel, and that was about 2 weeks ago or so.

So I'd like to see if tiny or anyone could chime in and answer whether or not that patch is now included.

Thanks
[Samsung Galaxy Nexus] kmcrane:
He has a test build a page or two back that has the patch. The files says test build in the title
[Samsung Galaxy Nexus] tiny4579:
Can people someone test BT music streaming or music in general on 4.1.0 test and check for audio skipping?
[Samsung Galaxy Nexus] jesssiii:
Sorry Tiny, I'm using your kernel but seldom use BT or listen to music on my phone. I can try but never noticed any skipping the few times I've listened so probably no use to you. Love the kernel, though!

Toro GNex
[Samsung Galaxy Nexus] cujo6801:
I downloaded your test kernel to test for you..

Bluetooth connected no problem to my Jambox.

Streamed music from Pandora for about 20 minutes..

No skips..

Hope that helps...
[Samsung Galaxy Nexus] midnightdevil66:
Downloaded it and will test it out tomorrow. Will let you know.

Sent from my AXI0M Toro
[Samsung Galaxy Nexus] midnightdevil66:
The kernel is rocking. BT connected no problem in my car, steamed music via BT no issues whatsoever.

Sent from my AXI0M Toro
[Samsung Galaxy Nexus] DoctorZaius68:
No problems streaming music or podcasts, using Bluetooth, with your test kernel.
[Samsung Galaxy Nexus] Matt Devo:
same, but not getting USB fast charge with it either
[Samsung Galaxy Nexus] tiny4579:
So you're only getting about 500ma charge rate after plugging it back in with it enabled?
[Samsung Galaxy Nexus] Matt Devo:
didn't realize it needed to be explicitly enabled - that would do it. How does one enable it?
[Samsung Galaxy Nexus] midnightdevil66:
Via app like trickster. Fast charge works fine here.

Sent from my AXI0M Toro
[Samsung Galaxy Nexus] tiny4579:
I like interactive for project butter and don't really mess with governors. But ondemand should in theory provide a bit better battery.

Is sound control on? I've not had that issue. Also I don't use sound control.
[Samsung Galaxy Nexus] Txwolf1980:
I noticed that, using trickster mood, on setting 3. Kicking it down to 2 fixed it, for me.
[Samsung Galaxy Nexus] tiny4579:
Kernel updated for Android 4.2 only:

2.2.0

enable fsync control (Ezekeel)

add BFQ I/O scheduler

add ffc script (toggle fast charge. run from terminal emulator)
[Samsung Galaxy Nexus] phydo:
Tiny, I'm going to give this a go. I've been a devout Franco fan for a while. I'm on muzzy's 4.2, a maybe 11-24 build. Gonna update now. I get horrible lag at times and its just time for me to see what's causing it.
[Samsung Galaxy Nexus] jlvlawrence:
This kernel has been rock solid for me.
[Samsung Galaxy Nexus] techspecs:
Just found this thread. Epic. :p
[Samsung Galaxy Nexus] tiny4579:
OP updated: Please read disclaimer about fsync.

Also, I am not sure if I'll want to keep BFQ as some benchmarking with AndroBench was disappointing compared to the others available.
[Samsung Galaxy Nexus] kmcrane:
Where's the disclaimer? I want to play it smart.
[Samsung Galaxy Nexus] tiny4579:
it's at the top of the first post.
[Samsung Galaxy Nexus] phydo:
If you don't understand that much about fsync, you definitely shouldn't be changing the setting. What do people think the kernel just has added bloat routines to slow it down? Lol.

Anyways... Tiny thanks so much for your kernel. I'm having amazing luck with it on 4.2. Very responsive and no slowing down over time.
[Samsung Galaxy Nexus] :
For some odd reason, I get a random reboot when the I/O scheduler is on cfq and I set the max screen off freq. to 700000 MHZ. I'm using Trickster Mod by the way. Anyone else? Oh, and I also want to add I also had ZRAM enabled if that contributes to anything.
[Samsung Galaxy Nexus] nitsua98:
Don't enable zram although that probably isn't the cause of your problem. Are you undervolting any?
[Samsung Galaxy Nexus] :
Nope, but now the problem isn't occurring anymore so no worries :)
[Samsung Galaxy Nexus] kmcrane:
Haha it's greyed out! I was skim reading the bright white letters! Using the xda app on dark theme! I just missed it. :o
[Samsung Galaxy Nexus] tiny4579:
From my rootzwiki thread but I wanted to make sure the xda users knew about this too:

I had another touch screen not responding incident though I could wake the phone using the touch screen or power button. I checked the kernel and logcat and didn't see any errors. I'm tempted to remove the linaro tweaks but I know I'm using PGM and that may have caused it. Does anyone have this issue that wasn't using PGM? I've honestly never had the freezing that I remember until I added the Linaro CFLAGS and built with the toolchain but I'd love to hear if anyone ran into the issue I'm describing and do not have PGM installed.
[Samsung Galaxy Nexus] cmajpwc:
I would like to try this kernel but I can't because of one main issue: upon rebooting the phone I find my MAC address for WiFi has changed. The only kernel that this doesn't happen with is Franco's. I would love to try your kernel but I need WiFi! Hopefully you can fix this issue.

Btw I'm referring to the 4.1.2 kernel. I don't have 4.2 on my phone yet.
[Samsung Galaxy Nexus] tiny4579:
I forgot about the wifi resetting thing. That's a standard feature in stock and there's an explanation behind it that may be in the leankernel thread somewhere. LeanKernel has fixed this and from what you're saying franco did too.

It's not something I cared about or really ever noticed as I don't use networks that restrict by MAC address.

My kernel wouldn't have that fixed on 4.1 or 4.2 if stock didn't change it which I doubt they did.
[Samsung Galaxy Nexus] tiny4579:
So it will be fixed in the next build. I made an update for 4.2 tonight (I found leankernel's commit) and it seems to work fine but I'm going to bed so I'll have both branches updated this week, likely tomorrow evening.
[Samsung Galaxy Nexus] cmajpwc:
I've tried searching everywhere and can't find an explanation. The only thing that makes sense from what I found was Google/Samsung couldn't find the money or didn't want to find the money to buy dedicated static hardware addresses. Even then, why in a kernel that was static before, it changes now? It's frustrating for those who use and need MAC filtering. Not that I blame you, though! This one is Google's fault.

And thank you! Much appreciated.
[Samsung Galaxy Nexus] nate6138:
Great battery life so far with Mmuzzy's ROM. Changed from Franco kernel just to see.
[Samsung Galaxy Nexus] nikulogical:
Why hasn't the kernel been updated to latest Linux version? Is there no benefit for our device?
[Samsung Galaxy Nexus] tiny4579:
The drivers for the device are designed for a 3.0 kernel. While there may be benefits to a later version, it breaks more than it improves. No one had done a full kernel on anything newer than the latest 3.0 kernel build.
[Samsung Galaxy Nexus] nikulogical:
Yeah I meant the latest 3.0 linux, I think its on what 3.0.82 right now?
[Samsung Galaxy Nexus] tiny4579:
No particular reason. I haven't released in a bit. Still not enough feedback on the fast charge. I don't think the updates to 3.0 will matter. A few rough spots attempting to apply the patches. I probably will update the patches for the next release.
[Samsung Galaxy Nexus] schukje:
Hi Tiny, im using your 3.4.1 kernel is this the latest and best for 4.2.2 rom? I use it on my maguro.

grtz from the crazy basterd from holland. powered by AK and DT