yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
Anything change beside the kernel in your setup? It really doesn't seem kernel related. J only switched to asram which has no bearing on Bluetooth. I wonder if the new Linaro chain could be at fault. I haven't heard any other issues yet.

Can you try to get a dmesg log after the issue happens?
[Samsung Galaxy Nexus] wmarcin:
I don't think anything about my setup is different, other than what I mentioned (apps & kernel).

I'll get a dmesg log and post it here.

Thanks for your support!
[Samsung Galaxy Nexus] wmarcin:
Sent you a pm with the dmesg log.
[Samsung Galaxy Nexus] tiny4579:
You know you could have posted it here as I'd consider it development related. I didn't see anything of note when searching for BT or Bluetooth. I also used my phone so my searching is more difficult and time consuming.
[Samsung Galaxy Nexus] wmarcin:
I wasn't sure if there was any sensitive info included, thus the pm. I'm not sure why there was no BT related info - I did exactly what you requested. I'm sorry you took extra time to investigate it. The fact that is not there suggests that:

1. The issue is not kernel related?

2. I somehow goofed, and I need to try again?

3. Both of the above?

4. Neither of the above?
[Samsung Galaxy Nexus] cuboc:
question

I have two questions for the creator of this kernel.

It is possible to create an image file of the kernel type "boot.img"?

This kernel will be updated to 3.0.101?
[Samsung Galaxy Nexus] tiny4579:
1. Why do you want a boot.img based kernel?

2. There really isn't anything for this device that would benefit from a higher kernel version.

It seems you may have seen this on leankernel and wanted it here. Correct me if I'm wrong.
[Samsung Galaxy Nexus] cuboc:
because I wanted to include this kernel in the installation as standard but this can not in folders.

when to update, and only a matter of efficiency and corrections that had the community, so I think it is like the last build of 3.0 versions, it would be best to have the most current. but it was only an idea / sujestao. your kernel is very well built.
[Samsung Galaxy Nexus] sajty:
About Linux versions.I am not requesting update,i dont care,but i am curious,why you stayed at 3.0.72.All devs are updating Linux version - only you and morfic not.Why?Whats the pros and cons?
[Samsung Galaxy Nexus] tiny4579:
You can include the zimage in the build but yeah its more work. The whole point of zimage is being universal and allows it to work on both cm and aosp.

I used to update the kernel version in the 4.x kernels and lower. Part of the reason I don't now is we have 3.0.72 which is a fairly new 3.0 kernel. The other reason is kernel updates are work for no noticeable gain also with an increased chance of breaking something. I may do it down the road but there really isn't a point as far as performance is concerned.
[Samsung Galaxy Nexus] Punkiderma:
just wanted to give my feedback:

Very great kernel! On maguro, with BLX set to 89, I think I'm having the best screen on performances I've ever had.

Now I'm trying to find the best for me between dyninteractive and wheatley.

Interactive and InteractiveX drain more battery for me.

Thanks!
[Samsung Galaxy Nexus] creepinm3:
If I delete "editramdisk.sh" would this fix the issue of (com.android.phone) when running CM10.2 nightly builds.
[Samsung Galaxy Nexus] tiny4579:
Try it but I dont think its the cause.
[Samsung Galaxy Nexus] creepinm3:
What do you think it might be? Before it worked after the whole ramdisk change.
[Samsung Galaxy Nexus] tiny4579:
What do you mean, before it worked after the ramdisk change? You mean it used to work with this script? I've not had phone fc issues on 5.3.1 and I always flash cm 10.2. It may be an issue on the build you flashed or an issur with the gapps or how you might have dirty flashed. Do you have the problem if you just flash the ROM?
[Samsung Galaxy Nexus] creepinm3:
I am on 11/09 nightly and it worked after the ramdisk change. This and special.

My order

Flash stock rom - wipe dalvik + cache - restart - let it settle for 10 min - flash xxxxxx tiny - wipe dalvik and cache - com.android.phone error
[Samsung Galaxy Nexus] mauro2390:
Dear Developer/s,

first of all I want to thank for your precious work.

Tinykernel 5.3.1 is GREAT stable and GREAT battery life -> PGM and Xlouder are working and supported.

Thanks again.

Nevertheless I need a little (perhaps big) favour from all of you.

I need the following modules/drivers to get working the PPPWidget app

cdc-acm.ko

option.ko

usb_wwan.ko (built automatically with "option.ko")

ppp_async.ko

The PPPwidget developer (he supports only the stock kernels) suggests the following:

http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=6&t=1612

The quoted thread concerns another device, but the issue is shared and common with our gnex.

The app was perfectly working just before the 4.3 android updating, after that, due the well known loadable modules issue, the PPPWidget can't work unless we resort to a custom kernel (in this/my case the Tinykernel)

Is there a possibility to get the above drivers compiled by you ?

Thanks a lot in advance
[Samsung Galaxy Nexus] a121232:
Can I use this kernel for ROM CM10.2 SNAPSHOT M1 - maguro?
[Samsung Galaxy Nexus] tiny4579:
Yes. Be sure to use 5.0 or higher for 4.3/cm10.2. This kernel works on all Galaxy Nexus versions.
[Samsung Galaxy Nexus] mnbrightblade:
Will this work on KitKat?
[Samsung Galaxy Nexus] Pkt_Lnt:
Answered ~25 posts before you asked.
[Samsung Galaxy Nexus] tiny4579:
Since this is your request, can you find out if they are sharing the source for these modules? If not its a pain in the rear to get them to work with kernels with different version magic signatures. I don't like the idea of binary closed source kernel modules and I won't ship them with my kernel.
[Samsung Galaxy Nexus] mauro2390:
THX very much for your answer, I'll check the issue.

thanks again
[Samsung Galaxy Nexus] mauro2390:
Probably It is not necessary to have any particular source only:

You need these drivers enabled in the kernel (listed with the respective folder in the kernel source tree):

http://www.draisberghof.de/usb_modeswitch/bb/report.php?f=6&p=11255

********************************

quoted by the above link:

You need these drivers enabled in the kernel (listed with the respective folder in the kernel source tree):

"cdc-acm" in drivers/usb

"option" in drivers/usb/serial

"ppp_async" in drivers/net

Every other setting of the stock kernel can be left untouched.

********************************

But please I'm not a developer and I could have missed everything!

Following there is a post of the developer stating his availability to be contact for any further clarification

http://www.draisberghof.de/usb_modeswitch/bb/report.php?f=6&p=11018

As always a big thanks for your work and availability
[Samsung Galaxy Nexus] JFDee:
Hi - developer of PPP Widget here.

The drivers in question are part of the standard kernel source. See "drivers/usb/class" and "drivers/usb/serial" folders.

The respective kernel config options look like these (from memory):

- Drivers/USB/"USB Modem (CDC-ACM)"

- Drivers/USB/Serial/"Driver for 3G and GSM modems/phones"
[Samsung Galaxy Nexus] pattyboi:):
Dear tiny:great work! Smoothest kernel yet :) question tho,can you implement the "badass" governer, it allows the GPU to process work and also locks the frequency of the CPU to retain more power...if you want I can link a article explaining it..thanks!-IF you do decide to add it,I'll take the plunge of testing and etc
[Samsung Galaxy Nexus] tiny4579:
If it's part of the kernel source it shouldn't be too bad. I'll see about adding it.

I don't know. I've been trying to stay away from adding random governors, and I've kind of felt it's pretty complete now already. They're all closely related to other governors with a few tweaks generally and despite what some think, generally don't do much good for battery life.

Go ahead and link an article as it won't hurt to read up on it. I don't have the time to work on this kernel like I used to so no guarantees.
[Samsung Galaxy Nexus] pattyboi:):
hey man i completely understand,and considering your probally a busy guy,i just copy and pasted-22: BadAss Governor:

Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing)

Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu. (credit to stempox for the article on cpu governers)
[Samsung Galaxy Nexus] phaze one:
I'm using 5.3.1 on Shiny ROM 4.4 11/27 with no issues.
[Samsung Galaxy Nexus] cujo6801:
I see you updated your kernel

To 5.4 .....

Will give this bad boy a try..

Thanks.....

O saw it on RootzWiki

sent from the DOG pound
[Samsung Galaxy Nexus] tiny4579:
Does this work for you in 5.4?

Also, sorry guys for the delay in updating my xda post. I would have had it updated last night but currently there's an issue accessing xda forums on my home ISP but nowhere else. I'm working on getting that resolved. I'm not sure where the issue lies quite yet.
[Samsung Galaxy Nexus] mauro2390:
Dear Tyni4579,

first of all I'would thank you for you effort. As soon as I'll be at home (I'm working abroad now for a couple of days) I'll check everything!

Thanks again

Mauro
[Samsung Galaxy Nexus] mauro2390:
i can not test the PPP widget now as explained before, nevertheless i flashed 5.4 for regression testing, but as soon as I start PGM I had froze and reboot!

the for your assistance
[Samsung Galaxy Nexus] tiny4579:
With a last_kmsg maybe I could figure out why there's a reboot. It should be a requirement with posting issues. Does PGM freeze on the previous version? Is this the old PGM or newer Touch control app by bponury?
[Samsung Galaxy Nexus] mauro2390:
hi,

I was always using the old PGM, with previous releases of the kernel never had a problem

thx
[Samsung Galaxy Nexus] tiny4579:
The app is deprecated. As soon as I wake the phone with PGM I get watchdog reset.

The old PGM had always been kind of inflexible with some kernel changes.
[Samsung Galaxy Nexus] mauro2390:
i tried the new Touchcontrol by ponury, but it ask me to download a set of possibile module and there is not the yours!

In any case, as soon as I can I have to learn how to generate the dmesg log

I'll appreciate your suggestions

thx
[Samsung Galaxy Nexus] jh13:
You need to choose CM 11 module and it will work.
[Samsung Galaxy Nexus] mauro2390:
no way man. tried all proposed modules, either tiny5.3.1 and 5.4 fail to load them
[Samsung Galaxy Nexus] jh13:
Yes way man....

Don't know what to say then. I'm running Tiny's latest 12-13 CM11 build with Tiny's 5.4 kernel and Touchcontrol (paid version) works perfectly fine using the CM11 module. I don't have ART enabled if that matters. See attached screenshots
[Samsung Galaxy Nexus] mauro2390:
thanks for the answer. maybe I'm using the free version and/or stock ROM 4.3?!
[Samsung Galaxy Nexus] DavidFlory:
I am also using Touch Control and the CM-11 module with Tiny 5.4. Shiny 4.4.2 12\11\13. Working fine. You may be trying a deprecated version.
[Samsung Galaxy Nexus] Nephilim:
Well it appears the normal kernel I use (Mpokang 4.4 SuperRam) is out of commision until metalspring updates the ramdisk. In the meantime I am going to try out Tiny, for a couple reasons. One, because I've been getting people on and off coming to my custom kernel settings thread asking me to review and post custom settings for Tiny and two, because I like what I've read in the OP and I am a fellow former Droid Incredible owner. I am preparing to be dazzled as we speak while "Android is upgrading....." 87 out of 137 apps so far lol.

Update* Everything booted without issue, I seem to have the same amount of free ram as with Mpokang SuperRam, very happy to see InteractiveX on here, that was something I missed on Mpokang. Doing a quick benchmark right now with Antutu just to see the difference on my custom settings with Tiny as opposed to SuperRam. I will keep running this kernel no matter what until tomorrow nights CM11 Nightly, the main test I am looking to give is battery life. If Tiny gives me better overnight idle drain and better daily usage battery life I am going to stick with it, especially since there is a developer still actively working on it. Either way, those of you Tiny Kernel enthusiasts can expect my first iteration of Nephilim Custom Tiny Kernel Settings sometime tomorrow on my thread. ;)​
[Samsung Galaxy Nexus] itasoulas:
you were on Mpo's kernel right? Cause I am planning to flash tiny over that. I tried Tiny in the past with Cataclysm and I was very pleased. As far as benchmarks goes I remember that Mpokang gave me higher results but of course this doesn't have to do with the overall system stability. Looking forward to your findings at your thread! :good:
[Samsung Galaxy Nexus] xxSAKISxx:
so to flash tiny 5.4 in cMetal 4.4.1 with mpokang superram i can just flash it over or i must do something else?
[Samsung Galaxy Nexus] Nephilim:
Two things:

1. DO NOT flash Tiny over Mpokang, make sure to reflash your rom first to get the stock ramdisk back before flashing Tiny, otherwise you will have issues.

2. My benchmark was a couple hundred points lower on Tiny but I see no difference in performance. Battery however is much better on Tiny so I think I'll be sticking with it for the time being. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] xxSAKISxx:
ok good neph i follow you but the cMetal comes with mpokang kernel included. so what i must do so i be able to try tiny?
[Samsung Galaxy Nexus] antypas:
Disagree with Nephelim. Tested Tiny. It's pretty good but:

1) Mpokang is clearly faster. I cannot stress enough how clear it is. Not only in benches. It is particularly obvious when opening apps...

About battery ... I cannot tell yet.

2) Free RAM? Free RAM is irrelevant. It doesn't constitute an usable memory space index.

Android will use your free RAM for app storing and caching until a certain point. The relevant is "Available RAM to developers", where Mpokang SuperRam is almost 30MBs more. So the free RAM may be the same but more apps are staying in memory with SuperRam...
[Samsung Galaxy Nexus] Nephilim:
Looks like metalspring is now using ASKP kernel as his stock, as long as you haven't flashed a custom kernel after flashing your current rom you should be fine to flash Tiny. As of right now though Mpokang is not working right with CM based roms as of last night's Nightly of CM11. It causes weird glitches with the battery percentage, battery charge meter and it for some reason removes the battery section from the quicksettings panel as well as the actual android settings.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] xxSAKISxx:
he use ASKP kernel in omnimetal rom but if i am not making a mistake in cMetal he use mpokang. At least that kernel i have and i dont remember flashing a kernel in this rom. Again maybe i dont remember right.
[Samsung Galaxy Nexus] Nephilim:
Isn't Omnimetal the next version of cMetal? I thought he switched over to Omni base now. Or are there 2 seperate roms hes overseeing?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] itasoulas:
maybe a stupid question but...if I want to clean install a rom and then flash tiny do I need to let the rom boot once and the flash kernel or can I do the kernel flashing right after rom flash and still in recovery? Does any of the two makes a difference? Just curious....
[Samsung Galaxy Nexus] Nephilim:
If its a clean install you can flash Tiny right away. If you are just dirty flashing your rom over again to get stock ramdisk I recommend reflashing the rom, wipe dalvik/cache then boot the device. Once booted reboot into recovery and flash Tiny, this will help make sure stock ramdisk is back fully.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] xxSAKISxx:
yeap you are right. he turn to omni base rom but as he say he continue to develop cmetal with 1 build per week. thats why cMetal is still in 4.4.1 state. Bottom line omnimetal and cmetal is 2 different base roms.
[Samsung Galaxy Nexus] cujo6801:
He's still doing both..

sent from the DOG pound
[Samsung Galaxy Nexus] Nephilim:
Thanks for the info guys, i wasnt sure. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Nephilim:
First iteration of Tiny Kernel custom settings has been officially added to my thread along with proper thanks to tiny and a link to this thread. Enjoy. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] joeygutz:
Rom

Nephilim thanks for all your recommendations and work you have put out.. ..what would be a good rom to run with tiny?
[Samsung Galaxy Nexus] Nephilim:
Until we see a Paranoidandroid 4.0 beta for Galaxy Nexus I've been bouncing back and forth between the official CM11 nightlies and Swordrunes unofficial CM11 builds. They are very stable.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] xxSAKISxx:
+1 for PA 4.But you believe we see one soon because the Pa thread is really quiet the last days.
[Samsung Galaxy Nexus] joeygutz:
Download

Where can I download the official cm11 nightlies as I have only seen the unofficial or are they one in the same...hope that's not a dumb question! thanks for the response.
[Samsung Galaxy Nexus] BOY_:
On Mmuzzy's and haven't cahnged anything but the kernel update :confused:
[Samsung Galaxy Nexus] tiny4579:
No other user has reported it and the issue you are describing is related to an issue with the OS itself not the kernel. This leads me to definitely believe it's not the kernel. It's likely not even the fault of the ROM dev either. If the dirty reflash of the ROM doesn't fix the issue you may have to wipe. Oh yeah your ROM doesn't need separate gapps so a reflash of the ROM should fix it and if it doesn't you may need to wipe.
[Samsung Galaxy Nexus] BOY_:
Looks like it was the WiFi optimization being selected. I turned it off and my battery is back to normal. Just wondering, does WiFi Optimization turn off the WiFi radio or decrease the broadcast rate? I'm betting that Google services was trying to sync and couldn't get a connection or got a slow connection and was causing the drain.
[Samsung Galaxy Nexus] tiny4579:
It doesn't turn off the radio. I'm not quite sure what it does actually but its supposed to help battery. Which build of mmuzzys are you using? Are you using one that has a WiFi tweak?
[Samsung Galaxy Nexus] BOY_:
I'm on the 2nd newest, didn't see the need to reflash just to change the volume sliders back down. What I think is weird is I rebooted, recharged, reset the battery log and it was the same issue since I flashed the kernel last night but; you're right, the kernel shouldn't be the cause. Normally I'm quiet on these type of annoyance issues but this one stumped me.

As I'm thinking back, I can't use yesterday's performance as a benchmark as I was on the road with the phone on the charger almost all day (GPS on, Google Music streaming) and last night I was recording video of my kids xmas concert in a gym with NO signal (seriously, military grade jamming!).

I'm gonna jump over to Mmuzzy's thread and share my findings.
[Samsung Galaxy Nexus] gt5oh:
Hows the battery running this kernel with MMuzzy 4.2.1 latest build?
[Samsung Galaxy Nexus] tiny4579:
I'd say the same as stock as I haven't made any changes for battery life (some linaro optimizations) but nothing that should affect battery life.
[Samsung Galaxy Nexus] gianton:
Gonna give this a try, thanks.
[Samsung Galaxy Nexus] Jose Viegas:
Flashed 2.3.1, working as well as before :good:
[Samsung Galaxy Nexus] poena:
is it supposed to show that the phone is awake for a long time even if the screen on time is so little? not sure if I'm looking at Better Battery Stats correctly
[Samsung Galaxy Nexus] evilssj4:
What settings are you guys using for maximum battery life? Do you guys lower the GPU to the lowest setting?
[Samsung Galaxy Nexus] aggrophobik:
I just run default settings. No complaints here at all. Well, maybe one, that there isn't Tinykernel for grouper... ;)
[Samsung Galaxy Nexus] evilssj4:
Cool, I'll give it a go with default settings. I saw someone here got 4 hours of screen time which is crazy.
[Samsung Galaxy Nexus] kevdliu:
i believe that was with extended battery
[Samsung Galaxy Nexus] Thyria:
Can this kernel also be used by free/open gnex? So no verizon gnex...
[Samsung Galaxy Nexus] nitsua98:
I think gnex kernels can be used on all nexuses, someone correct me of I'm wrong
[Samsung Galaxy Nexus] tiny4579:
Yes.
[Samsung Galaxy Nexus] revolt1:
Your kernel with gsx updated rom is money
[Samsung Galaxy Nexus] ashclepdia:
Hello Tiny, first off I want to say great work!

I put your kernels on my buddies incredible a while back and was always impressed. Its good to see ya over here also. And also huge thanks for continuing the 4.1.2kernel updates, there's just something about 4.2 I'm not quite into so have been back on 4.1.2 again. Its great to have kernel still being updated for that!

There is just one thing I would love to see

That is the ability to change the CPU throttle temperature like leankernel has. I am a pretty heavy user, and I have found throughout my experiences that being able to raise the CPU throttle temp to 75-80°C gives me a MUCH smoother experience due to it not throttling back when it gets a bit warm.

Would like to know your thoughts on this.

Thank you again!
[Samsung Galaxy Nexus] tiny4579:
I released 1.9.0/2.4.0 with support for leankernel's temperature control. I'd rather discotinue 4.1.x support like the rest of the main Gnex kernel devs are due to the extra time involved adding changes to two bases and verifying.
[Samsung Galaxy Nexus] xxSAKISxx:
this link takes you to maguro variant. if you have another one (toro or toro +) i think you can find it through this link

http://download.cyanogenmod.org/?device=maguro
[Samsung Galaxy Nexus] Nephilim:
Go to cyanogenmod.com and then click on "downloads" and find your device. ;)

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 01:26 PM ---------- Previous post was at 01:24 PM ----------

I think it'll be another month at least before we see a PA4 with features reintroduced on the Gnex. I can wait though. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] joeygutz:
Found it .....
[Samsung Galaxy Nexus] mauro2390:
here it is the log generated after a systematic freeze and reboot as soon as I load PGM free (DEPRECATED).

NO reboot and freez with previous your release until 5.3.1 stable and perfect.

As you suggested, I tried also the NEW Touchcontrol FREE, but as I already posted it ask me to choice to download a set of modules.

I tried all of them without success (it fails to load).

Thx in advance for your work
[Samsung Galaxy Nexus] tiny4579:
I think Touchcontrol paid works but I don't want to buy the app when I won't use it. That's kind of silly.

I have two options here to fix it.

1. Revert the commit I believe is causing this issue - https://github.com/tiny4579/tinykernel-gnex/commit/4991498b2e8c04b163d16bb521393098a1c2b2e9

2. Try to figure out which config change is the culprit. This is more time consuming but it's most likely GPU/graphics related from the last_kmsg.

EDIT: Reverting the above commit works. I can activate the modules and select them and even turn off the screen and trigger a wake by sliding to the right.
[Samsung Galaxy Nexus] mauro2390:
Dear Tiny4579,

take your time to decide about the fix options.

As always, my best regards
[Samsung Galaxy Nexus] modernbummer:
Touch Control is working for me. You have to choose the CM 11 module.
[Samsung Galaxy Nexus] DavidFlory:
Same for me. Works fine with the CM 11 module.