yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
That's what I hear, but it doesn't actually work on the free version. So with Tinykernel 5.4 you can't use the deprecated PGM and Touch Control free doesn't seem to work (not even on the CM11 kernel itself). If you need PGM 5.3.1 works fine. There aren't honestly new features except for a few requested ones that or or two may use. I can actually reproduce the reboot issue on the CM11 kernel with PGM so it's related to those commit changes.

I don't mind reverting that one commit. It doesn't seem to help anything and breaks PGM.
[Samsung Galaxy Nexus] AuroEdge:
I am using a clean install of ShinyROM with Trickster Mod to set the Tiny Kernel settings. For some reason after boot the kernel is set to run at 1200 MHz instead of what I previously set as max, 1350 MHz. This happens most of the time but not all the time so I really don't know what's causing it.

I haven't tried the frequency lock option in Trickster yet. I will try it out soon.
[Samsung Galaxy Nexus] JohnKuczek:
I had this type of issue for a while, until I discovered that CM's performance settings were causing a conflict. I set a delay in Trickster for the set on boot, and have not had any issues since.
[Samsung Galaxy Nexus] Nephilim:
Setting a delay issue always a good idea just inside case you run into an issue with settings, it helps keep you from accidentally bootlooping.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] AuroEdge:
I had to do some reading to find all the differences between boot delay and grace period.

For the InteractiveX governor in Tinykernel, you can still set a max screen off CPU frequency value in Trickster Mod. Does the governor allow the kernel to run at this frequency, or does the kernel only run at the minimum frequency set anyway?
[Samsung Galaxy Nexus] tiny4579:
The governor will still scale above the minimum frequency if needed but will generally stay at the minimum due to load. You may have to use CPU spy and reset timers just prior to playing music with screen off or another screen off activity if you want to verify if it hits that frequency at all.
[Samsung Galaxy Nexus] lagendbun:
this is first time i want to flash tiny kernel with my gnex...

my noob question is what the different between verizon gnex and gsm gnex?
[Samsung Galaxy Nexus] cujo6801:
There is no difference they're all tuna

Only for the kernel...

sent from the DOG pound
[Samsung Galaxy Nexus] tiny4579:
Taken from rootz thread:

Not a bad idea to have two versions. To be honest, I only included as there were no known issues at the time. I wasn't aware of this. We'll see what people think about two versions. It's easier to maintain one version but as small as this change is i could do it from the configuration side.

About PGM reboots, I am aware and have been for a bit. PGM is a closed source kernel module so it means horrible custom kernel support. I know what change caused it and jag already reverted in testing.

EDIT:

This will happen for 5.5 :wink:
[Samsung Galaxy Nexus] omniatic:
Well, I don't watch a lot of video, so ASRAM version is fine for me. If having two versions isn't too much extra work, then why not. I'll try them both and see which works better for me.

As for the PGM reboots, I got tired of using the button and bought Touch Control...problem solved.

Thanks,
[Samsung Galaxy Nexus] AuroEdge:
It's difficult to gauge TouchControl from the play store reviews. Does it play well with this kernel? It's my understanding only the paid version works
[Samsung Galaxy Nexus] tiny4579:
AFAIK that's the case. I don't know why the free one doesn't, maybe it's behind the paid version in development.
[Samsung Galaxy Nexus] AuroEdge:
A) It appears the paid version is one iteration ahead of the free version

B) Still don't know why the app author sent the previous app kaput and released it under a new name

C) Used the CM 11 module. Is there any reason to add a tinykernel module?
[Samsung Galaxy Nexus] DavidFlory:
A) Inducement to buy the paid version?

B) The new name is much better than the initials it used to be know by. (and it gave him the chance to set up a paid version.)

C) The CM 11 module works fine for Tiny. Dont need another module. What would be nice is some notes as to which module works with which kernel.
[Samsung Galaxy Nexus] tiny4579:
I need a couple testers for 5.5. I have an ASRAM version and non ASRAM version. I need at least one tester for each. I am requesting testers since my Galaxy Nexus is loaned out to a friend due to his failing USB port.
[Samsung Galaxy Nexus] pattyboi:):
ill do ASRAM from tonight till after school tomorrow,roughly 18 hours of testing.
[Samsung Galaxy Nexus] omniatic:
I'll test one...whichever you need. ASRAM preferred, either is fine, though.
[Samsung Galaxy Nexus] johnco1972:
I can do the non asram version. What sort of testing?
[Samsung Galaxy Nexus] Wrath_unleashed:
I'll test whatever you need whenever, just pm me.
[Samsung Galaxy Nexus] djtutis:
Any news about your new kernel?
[Samsung Galaxy Nexus] tiny4579:
Need to get a bit more feedback since I can't test on the device.

Maybe add ram oc but I can't do.the initial test to make sure it boots at least.
[Samsung Galaxy Nexus] ashclepdia:
I'm not working or anything at the moment, so I've got plenty of time to test anything you need.

And tomorrow morning I plan to fully factory restore my Gnex cuz its been forever since I've done it and my Gnex is begging me for a cleanup lol.

The only things I cannot test would be relate to carrier network as I use it strictly on WiFi(vzw ain't getting anymore of my $$$ ever lol)

I'm willing to test on stock ROM, or any ROM you prefer I use so that you get the results/tests/logs you may need. I'm not FULLY versed in adb, but I am VERY familiar with it along with fastboot and my Linux laptop is already setup for easy use. (If I recall correctly, I don't think I would even need you to package the zimage into flashable zip, I thought I used before a fastboot command that allows me to boot a kernel zimage with current ramdisk without even installing it fully at the time of boot until I tell it to)

Dont know if you planned on letting public test or wanted to get small group of 'power-users' together for initial testing if you really wanted to move forward with this kernel development (not trying to put pressure on your decision on whether to continue, just throwing my hat into ring for a tester) :D
[Samsung Galaxy Nexus] memaro_maro:
asram 5.5 for me please...?

galaxy nexus
[Samsung Galaxy Nexus] buhohitr:
The 5.4 Tiny kernel is not battery friendly, but good performance, compared to Leankernel...did the test on Omnimetal and LiquidSmooth.
[Samsung Galaxy Nexus] memaro_maro:
did lean kernel support 4.4.2 roms?? didnt try it since update to kk..

galaxy nexus i9250 > 4.4.2 slimkat
[Samsung Galaxy Nexus] buhohitr:
Yes and it supports all 4.4 custom rom.
[Samsung Galaxy Nexus] memaro_maro:
using tiny bcoz of asram.. but still giving a good battery life so far. i want to try that 5.5 updated version first!!

galaxy nexus i9250 > 4.4.2 slimkat
[Samsung Galaxy Nexus] buhohitr:
Yeah, I tried 5.4 version and battery life is a lot worst than LeanKernel, hopefully, the 5.5 would do better and I willing to try again once it's out!!
[Samsung Galaxy Nexus] tiny4579:
How long did you test it? This kernel tries to stay closer to stock because sometimes tweaks can make things worse. There aren't any battery sapping tweaks here, and at default settings this should be near a stock feel.

Many have reported good battery here. The major drain in most cases is not the kernel. Please check wakelocks and such.
[Samsung Galaxy Nexus] omniatic:
Never had any issues with battery life on 5.4.

Turn off Location Reporting in Google settings. Adjust your screen color settings with Trickster.

Those are the two biggest drains on battery, from what I've seen.
[Samsung Galaxy Nexus] tiny4579:
Uploaded my 5.5 builds (both with and without ASRAM) to my normal goo.im site.

Changes:

ASRAM takes less from the tiler (better video functionality)

Revert of the CM commit that causes PGM to reboot the device - it seems to have caused more problems than it's worth

RAM O/C from Fancy Kernel (bencmarks report ~10% increased throughput in RAM

5,5 will be my last build unless there are kernel updates available for new GPU driver updates or something major (or if something is broken).
[Samsung Galaxy Nexus] buhohitr:
I didn't mean the battery is bad, it's OK, but worst if compared to LeanKernel.
[Samsung Galaxy Nexus] tiny4579:
It defaults to the settings from stock. Have you tried tweaking it?
[Samsung Galaxy Nexus] buhohitr:
Nope I haven't, only compare default with default settings. My opinion the most battery saving is UV, starting out wit -25 across the board then drop down in the increment of 25 until phone started to unstable then go backup 25. Smoothness usually achieved by gov/IO scheduler and gpu settings. Lagginess/stutter usually control by increase min frequency.
[Samsung Galaxy Nexus] memaro_maro:
i can get my 5 hours screen on time.. just enough.. dont need to argued. good bettery life so far

galaxy nexus i9250 > 4.4.2 slimkat
[Samsung Galaxy Nexus] buhohitr:
What is your phone sleeping time? and what rom you're using?
[Samsung Galaxy Nexus] memaro_maro:
reporting.. 5.5tiny (asram) perfect when deep sleep. battery friendly same just like previous built. still fast when optimized (gpu oc was 307mhz, undervolt -175 mpu)

cant tweak my fav governor ( interactive).. ?

tqvm tiny

galaxy nexus i9250 > 4.4.2 slimkat
[Samsung Galaxy Nexus] sajty:
Tiny is able to handle even higher undervolt than -175mV.On some frequencies,i am undervolted up to -250mV.
[Samsung Galaxy Nexus] memaro_maro:
yup.. im running 230mhz as min & screen off freq. but dont put in too low.. it will affected deep sleep, then losing more battery %. ~ just my experiences

galaxy nexus i9250 > 4.4.2 slimkat
[Samsung Galaxy Nexus] johnco1972:
Can you publish your under volts by frequency here? I'd like to experiment and starting with your setting might speed up the fine tuning process for me.

Thanks in advance.
[Samsung Galaxy Nexus] sajty:
Here you go:

230 MHz - 750 mV

350 MHz - 775 mV

700 MHz - 925 mV

920 MHz - 1025 mV

1200 MHz - 1150 mV

1350 MHz - 1200 mV

Sent from my GN
[Samsung Galaxy Nexus] Gabboplano:
Could you share your settings please?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] buhohitr:
Based on his posting, he's running Slimkat rom /5.5 asram Tiny kernel with these settings:

-175mpu across all frequencies (This is the major battery saver here)

Min screen off=230mhz

Max screen off=230mhz

gpu OC =307mhz

Since Tiny kernel can take under volt well, one user reported up to -250mv. Depend on each device, you can under volt even more, so slowly drop down until your device started to be unstable then go backup +25/50 milvolt. On my device I started with -200mv and it's stable, I will let it run for one full day with stress test then, will drop another -25mv. Remember, even if it's stable but if you feel it slows down, you need to stop there and bring up +25volt. unless you don't care about performance. The best settings are giving a good battery life without given up performance!!!
[Samsung Galaxy Nexus] johnco1972:
Thanks. Everything seems good on these settings so far
[Samsung Galaxy Nexus] Gabboplano:
Can not undervolt more than 270. It is crazy though, I've never seen a kernel which can be undervolted by more than 125

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] tiny4579:
The minimum voltage is dtermined by smartreflex. What voltage you set it to can be considered the calibrated voltage. It won't necessarily be the voltage your frequencies actually run at. I believe I've set the minimum smartreflex voltage to 700. I'm not sure as I don't currently have the device but my github should have what I set for smartreflex. If you want to know more about smartreflex, the rootzwiki leankernel thread has some information and there's also Google.
[Samsung Galaxy Nexus] buhohitr:
Make sense!!
[Samsung Galaxy Nexus] stevensoaj:
I just recently flashed tiny for the first time in my search for a stable, battery friendly KitKat kernel with all the features I wanted, and man am I impressed. I love the fact that you set it up very close to stock. I'm just sad I didn't find it before the last release. Thanks! :thumbup:
[Samsung Galaxy Nexus] Gabboplano:
I was getting ~2 hours of screen on before of this kernel, now I'm getting more than 3. This is amazing!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] tiny4579:
New test build to see if it fixes the touch control reboot issues:

https://dl.dropboxusercontent.com/u/31805083/tinykernel-5.5.1-test-ASRAM.zip
[Samsung Galaxy Nexus] omniatic:
Nope. Neither Touchcontrol or PGM2 works with the test build. Just get that nasty pop and a reboot.

Reverted to the 5.5 and using PGM2 for now.

Thanks,
[Samsung Galaxy Nexus] tiny4579:
All I did was revert a memory tweak that wasn't in there until 5.5 even though pgm worked previously. Why I even spending time on fixing the kernel for a glitchy mod?
[Samsung Galaxy Nexus] stevensoaj:
That's a good question. It seems a lot of kernel devs have to break their backs to get that working.
[Samsung Galaxy Nexus] memaro_maro:
going back to tiny after 1 week tried the others. haha.. miss this kernel so much.

i got some request. can we get low iva voltages on smartreflex.. dont know the rationale reason? but i think its offer some good battery life..

#edit* suddenly after i reboot iva on smartreflex going to ~ 860mv. sorry just mess wt tweaked before
[Samsung Galaxy Nexus] Gabboplano:
I read that this is probably going to be the final version, but is it possible to add Intellidemand governor?
[Samsung Galaxy Nexus] tiny4579:
I tried it before and didn't like it so no.
[Samsung Galaxy Nexus] bobbyinboone:
Lazy/Confused

Been flashing for years, and still have a hard time understanding why its so hard for laimen like me have a resource to check what KERNELS can be used on what without digging threws threads... anyone direct me to see if Tiny 5.5 will work with CM latest will work well on GNex? and whats the difference between ASRAM or "no-ASRAM"??
[Samsung Galaxy Nexus] tiny4579:
Kernels are usually global with roms unless stated otherwise. Nexus kernels usually work on any AOSP Rom. Sometimes cm will have changes that break boot.img kernel support and other times, not this phone, kernels need caf specific drivers to work on cm and derivatives. Asram should be discussed in this thread. If you don't know what it is after a bit of research, use the non asram version. You probably won't miss asram anyways.
[Samsung Galaxy Nexus] mauro2390:
whwn I attempt to flash the 5.5NO-ASRAM by means the last release of CWM I receive the infamous message ....STATUS 7 installation aborted

Thanks for your tip and tricks o solve the issue.

I checked the md5 signature of the downloaded zip file and it seems OK

The only suspect that I have it is that today I flashed (successfully) the ShinyROM 4.4.2 galaxy nexus maguro and never had this issue before!
[Samsung Galaxy Nexus] tiny4579:
Do you see the assert error? It could be a bad download.

Nevermind md5 fine. Probably on your end as I've had successful reports from my testers. Also try twrp.
[Samsung Galaxy Nexus] mauro2390:
thx for your reply. So:

here it is the report

....

Installing kernel...

set_perm: some changes failed

E: Error in /data/media/0/Download/tinykernel-5.5-NO-ASRAM.zip

(status 7)

Installation aborted.
[Samsung Galaxy Nexus] tiny4579:
This helps. It's due to the kernel using an older update-binary and the recovery doesn't support that set-perm command. Try copying it from shinys zip into the meta-inf folder in the kernel and overwrite the existing one.
[Samsung Galaxy Nexus] mauro2390:
Hi tiny4579,

here it is what I did as you suggested:

1) copied from the shinyROM the file update-binary onto the related folder of the kernel;

2) I tried to flash the new (renamed/patched) kernel but the assert was

... opening package

... installation ABORTED

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

As you suggested I tried flashing the original kernel also with the trwp recovery with the same result (...STATUS 7 and so on...)

Thx for your welcome reply
[Samsung Galaxy Nexus] tiny4579:
Just to clarify, from Shiny ROM you copied META-INF/com/google/android/update-binary into the kernel zip in the same location? Did you repackage the zip or just replace the file?

It should work but I don't have a way of testing it right now.

Either way, it's worked for me with TWRP 2.6.3.0 without an issue and I've flashed up to 5.4 and some users have had success flashing this.

Is it the same status 7 error (set_perm) since this error can be kinda generic.
[Samsung Galaxy Nexus] mauro2390:
Hi Tiny

>>Just to clarify, from Shiny ROM you copied META-INF/com/google/android/update-binary into the kernel zip in the same location? Did you repackage the zip or just replace the file? <<

I unzipped the package on my PC, I did the replacement in the same location and zipped the new archive just created and I transfered to my sd phone the new created zip file.

After that trying the flashing I receive a very generic message "installation aborted", this time it doesn't contain any STATUS 7 assertion.

It seems to me this time related to an not proper packaging procedure of the zip file!

With the TWRP I receive again the STATUS 7 with the original kernel. Is it worth to test also with the update-binary replacement?

Thx for your patience and support
[Samsung Galaxy Nexus] mauro2390:
SOLVED (thx to the user: OSMOSIS) please read here if you are interested in what is causing the issue! -> http://xdaforums.com/showpost.php?p=49762336&postcount=1497

thx
[Samsung Galaxy Nexus] erghetto:
i can flash this kernel also on nexus (GSM) right?
[Samsung Galaxy Nexus] bluerez79:
Yep. Its a tuna kernel.
[Samsung Galaxy Nexus] djtutis:
Where is the download link for 5.5? I can't find it...
[Samsung Galaxy Nexus] memaro_maro:
stated in thread's OP ...

http://goo.im/devs/tiny4579/gnex/kernels
[Samsung Galaxy Nexus] djtutis:
Sorry about noob question... What's the difference in ASRam and non ASRam version?
[Samsung Galaxy Nexus] AuroEdge:
It is expected when users post a question they at least searched for an answer first. Searching asram shows it's the freeing up of ram from other sources.
[Samsung Galaxy Nexus] erghetto:
hey guys, i'm trying this kernel for the first time, and i've seen that TCP and scheduler by default are differnet from other kernels i usually use.. so which settings do you suggests me?

teorically westwood is the newest as TCP, right? why here there is cubic? instead as scheduler i see cfq..
[Samsung Galaxy Nexus] tiny4579:
They are default android selections. Instead of changing the defaults as others have done, I have left the settings as default. You can use a tweaking app or scripts to ser the settings as you see fit.
[Samsung Galaxy Nexus] tiny4579:
5.5 is official. Nothing changed from earlier. I just thought the OP needed updating.
[Samsung Galaxy Nexus] memaro_maro:
most stabile kernel around tuna device.

no big issues so far.

for me, just some issues to interctive governor's tuneable setting. target_ load didnt stick by trickter change. need to run a script to manually change it.

no problem so far.
[Samsung Galaxy Nexus] adlx.xda:
Line 7 of the updater-script try to set_perm a file that's isn't in the zip nor used anywhere:

...

package_extract_dir("kernel", "/tmp");

set_perm(0, 0, 0777, "/tmp/dump_image");

...

$ find kernel/

kernel/

kernel/mkbootimg.sh

kernel/mkbootimg

kernel/unpackbootimg

kernel/editramdisk.sh

kernel/zImage

There's no such dump_image file in kernel/ , hence the error flashing it ;).

Btw it's in latest tinykernel-5.5-ASRAM.zip:

0e4e774d0384cf043472927e347dec81 tinykernel-5.5-ASRAM.zip
[Samsung Galaxy Nexus] tiny4579:
This is the same base for the zip as I've used for a long time now and no one has issues flashing it. Several users have flashed 5.5 without an issue. It should work with that line failing since dump_image is built into most recoveries.

Have you tested flashing this yourself?
[Samsung Galaxy Nexus] adlx.xda:
I have indeed, and it won't flash the kernel as it fails it left me with the CM11 kernel I had, untouched.

I attach the full recovery.log showing the error, Status 7 and abortion due to the non existing file. Btw it seem you don't even use the dump_image anyway, I'll see if I have some time to remove the line, and reflash:

AnyKernel Updater by Koushminzip: Extracted file "/tmp/editramdisk.sh"

minzip: Extracted file "/tmp/mkbootimg"

minzip: Extracted file "/tmp/mkbootimg.sh"

minzip: Extracted file "/tmp/unpackbootimg"

tiny4579 Galaxy Nexus Kernel...minzip: Extracted file "/tmp/zImage"

set_perm: chown of /tmp/dump_image to 0 0 failed: No such file or directory

set_perm: chmod of /tmp/dump_image to 777 failed: No such file or directory

script aborted: set_perm: some changes failed

Extracting Kernel files...

Installing kernel...

set_perm: some changes failed

E:Error in /data/media/0/Cyandelta/tinykernel-5.5-ASRAM.zip

(Status 7)

Installation aborted.

[/CODE]
[Samsung Galaxy Nexus] tiny4579:
Some recoveries must be more strict as I've flashed several versions without this error.

It will work if you remove the set_perm line it's complaining about since that file doesn't exist in kernel as you have said.
[Samsung Galaxy Nexus] adlx.xda:
Works fine removing this line ;).

Btw, I'm using the official CWM recovery 6.0.4.7.

Fixed file attached.
[Samsung Galaxy Nexus] adlx.xda:
Fast Charge?

I've installed this kernel primarily to get Fast Charge support, but it doesn't seem to work. When I set fast charge (either with an app or with echo 1 > /sys/kernel/fast_charge/force_fast_charge), and then plug the USB cable, it still recognizes the "USB" charging mode, not "AC" :(. Any idea? :silly:

Should I use 1 or 2 when echo'ing to /sys/kernel/fast_charge/force_fast_charge?

Edit: nevermind, seems this kernel still says USB charging while accepting AC charging speed... I'll monitor that and see how it goes.
[Samsung Galaxy Nexus] XxStechxX:
Anyone else notice that with this kernel, no more audio stuttering with poweramp? I just noticed, been going back & forth between the cm kernel & 5.5asram

Sent from my CM11 Nightly Galaxy Nexus:beer:
[Samsung Galaxy Nexus] jcruz767:
Toroplus compatible?

Could I use this kernel on the toroplus? I know the op said carrier independent, but I've had my fair share of mishaps and wanted to make sure.
[Samsung Galaxy Nexus] tiny4579:
It says carrier independent so yes.
[Samsung Galaxy Nexus] ashclepdia:
ALL kernels are Tuna kernels

aka maguro, toro, toroplus

I have YET to see or use ANY kernel listed in ANY Tuna(Gnex) section that didn't work fully and properly on all gnex variants.

ROMs are a different story.

kernel made for ANY Tuna variant should work just fine on any variant.

the ONLY thing I saw that MIGHT not work due to kernel is the "network indicator" arrows located within the signal status icon, but most of the time they are fine, and I THOUGHT they were removed in 4.4(though I keep seeing them for some reason, which I wish I WOULDN'T cuz I read that it takes away from gpu performance to have to display them anyways...I'm hoping Roms aren't ADDING that BACK....I dunno yet tho I haven't done any testing between Roms on that)

TL;DR--YES this will work on your Tuna device :) enjoy!

also, any kernel listed within the "Galaxy Nexus Android Development" section will work as well. those are also seem to be the most active section for kernel discussions

(edit:: this was NOT meant to be a jerk in any way, purely informational, do not take offense, no flaming intended! :D )
[Samsung Galaxy Nexus] redj12:
Hey why this kernel is not very popular ? You should move it in the maguro section ! Just flashed it with SlimKat and all seems really nice !

I really appreciate your work so thanks buddy.

Envoyé de mon Galaxy Nexus en utilisant Tapatalk