yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ddschmidt:
I am having troubles with the fuss command. I go to terminal, type su, and then type fuss after hitting enter. I get a sh/fuss: not found error. Is there a step that I am missing? Do I need to download the permissions fix?

Thanks
[Samsung Galaxy Nexus] boype:
Do you have a file named 'busybox' in /system/xbin/ ? If not, the files cannot have been copied over where they belong.
[Samsung Galaxy Nexus] phishn:
FWIW its also worth noting what hardware is being used reporting problems. I'm on a Toro cdma galaxy Nexus, others may be on maguro. So some things reported may do different things based on the type of hardware, especially when antenna type stuff is mentioned, like the airplane mode toggle someone previously mentioned.

In the meantime I'm going to try the 128 read ahead buffer size with sio, bluetooth, and screen off.

Edit - with 128 read ahead buffer, bluetooth, screen off still skips.
[Samsung Galaxy Nexus] Toushiro Hitsugaya:
I'm having this problem with su/fuss (see attached image)

Also, I'm having the Bluetooth audio issue, is it possible to fix if I'm using Play Music instead of Poweramp?

Edit: I'm using maguro.
[Samsung Galaxy Nexus] ddschmidt:
I had busybox in that folder, but a reinstall of busybox fixed the issue. Thank you very much for the quick reply.
[Samsung Galaxy Nexus] boype:
That looks like a DNS problem to me... Nothing I can do about :(

I don't know if Play Music fixes the bluetooth issue, can you test and report back?
[Samsung Galaxy Nexus] Toushiro Hitsugaya:
Sorry, my English isn't very good. Actually I'm using Play Music and have the Bluetooth issues, and it doesn't have any option for audio buffer.
[Samsung Galaxy Nexus] boype:
Your English was perfectly okay, but the sentence could be interpreted in two ways. I just got it wrong :eek:
[Samsung Galaxy Nexus] kinfolk248:
anyone else getting lots of phone idle eating away at the battery on 21? if so, how to fix it?
[Samsung Galaxy Nexus] boype:
With WiFi enabled? If so, I already have a clue what may be wrong ( something I need to fix)
[Samsung Galaxy Nexus] jesssiii:
Thanks, noticed the same thing today with Wi-Fi on, not being used the whole time but mostly.
[Samsung Galaxy Nexus] mangusZen:
Seems all good here, wifi all day, very good battery drain when idle, wifi high perf off

sent from Vega gnex
[Samsung Galaxy Nexus] kinfolk248:
wifi and 4g actually... ;-(
[Samsung Galaxy Nexus] thebogy:
Yeah, i also noticed it. :(
[Samsung Galaxy Nexus] mangusZen:
I correct myself..phone idle *is draining..

Bsttery life is good however, slimbean Rom

sent from Vega gnex
[Samsung Galaxy Nexus] Riekr:
+1

Yes

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] phishn:
No WiFi drain idle here, usual 1.2% per hour overnight, but I leave WiFi high performance enabled all the time if that helps pinpoint things.
[Samsung Galaxy Nexus] Riekr:
Btw i don't use WiFi high performance but WiFi is set to always on but during the night the device is not connected. With r20 no problems that way

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] kinfolk248:
what do you mean by not connected?

if you mean wifi is on but when u wake the phone wifi has to reconnect really quick then yea i see that sometimes too...
[Samsung Galaxy Nexus] dratif:
Hey boype... you've done an amazing job. My device never deep slept better. Just imagine up to 8 hours deep sleep and only 1% charge is utilized with 98% deep sleep . I'm using mirage rom*fancy 21.. thanks for the awesome job:thumbup:
[Samsung Galaxy Nexus] Riekr:
In an uncovered WiFi area. Anyway, this night it happened again while the phone was connected. I'm rolling back to r20 to see of the problem persists.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Argasil:
I would try this kernel cause i see that the developer, not like other that transposed their works on N4,gives attention and make a lot of innovation :D

I would know if thereis a best rom for this kernel, probably CM based cause the kernel it's complied by the kernel of Cm right?:) thx a lot :)
[Samsung Galaxy Nexus] kinfolk248:
i have no idea what you mean by and uncovered wifi area. my router reaches the whole house and if the phone goes to deep sleep and i wake it you can see where wifi is grayed out and reconnects really quick. dont know if that is by design or not.

last night on r21 lost 10% overnight in 8 hours time, dont know if that good or bad on 4g

still trying to get 2 hours screen time with this kernel b/c 2 hours with standard battery is good life...
[Samsung Galaxy Nexus] fr4nk1yn:
Over the last couple years I've amassed 6 standard batteries and two extended batteries.

I have batteries that last 3.5 hours screen on time and one, that I need to isolate and get rid of, that gets only 1.5 hours.

Before this kernel I could only get 2 hours as my best so I know it's fantastic.

If you have another battery try swapping it.
[Samsung Galaxy Nexus] kinfolk248:
no i dont have another battery but i usually try to get 2 hours screen time b/c i consider 2 hours as the measure of decent battery life with the standard 1850mah battery...
[Samsung Galaxy Nexus] mangusZen:
I usually get 3.5 screen hours with slimbean, standard battery ,greenified and optimized system, no music no video always wifi, just chat, browsing calls tapatalk etc.

Stay away from chinese cheap batteries or samsung copy, they wont last like original ones

sent from Vega gnex
[Samsung Galaxy Nexus] kinfolk248:
see im almost all 4g with moderate browsing and texts, email, gv....so 2 hours is good for me
[Samsung Galaxy Nexus] fr4nk1yn:
Use wakelock detector to see if any app is giving you issues.

There's no reason you shouldn't do 2 hours. Like I said I get over 3 with no special apps or procedures.

I stream music to and from work, tweet, check g+, text, browse all day with GPS on, signed into latitude, etc, etc.
[Samsung Galaxy Nexus] kinfolk248:
what size battery, 4g/wifi, etc etc whats your set up??

now im getting about 2.5 hours screen on 4g had to increase threshold to 95% on ondemandplus
[Samsung Galaxy Nexus] fr4nk1yn:
Here's the thing, I have no set up. Everything is default, I turn nothing off, in on Wi-Fi at work and home to save data that's it.

Maybe it's my usage maybe I'm just lucky. ROM is Shiny
[Samsung Galaxy Nexus] kinfolk248:
exactly wifi all the time will do that and save battery for you...you gotta give info my friend
[Samsung Galaxy Nexus] Riekr:
R20 dropped only 6% over night

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] agritux:
for mine, r21 is better than r20

%2 for all night. only wifi active. gsm 2g.
[Samsung Galaxy Nexus] Riekr:
3g here

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] zoomy942:
Screen still seems dim but its probably cause of the blue hue.
[Samsung Galaxy Nexus] Toushiro Hitsugaya:
Is there any fix for the negative green gamma? I can live with it, but just to know.

BTW, anyone have an issue waking the screen while Bluetooth headset is connected? Sometime it happens, sometime not.

This aside, this kernel is the best by far, excellent battery life and very smooth.
[Samsung Galaxy Nexus] bolanrox:
Nope, never had an issue with using a headset and waking the screen here. Do you have to keep pressing the power or volume buttons to wake it?
[Samsung Galaxy Nexus] Toushiro Hitsugaya:
No, it just doesn't wake till I turn off the headset. Then it start working perfectly again. But this is uncommon this issue. I use Nokia BH-505
[Samsung Galaxy Nexus] bolanrox:
using a jawbone here. I need to turn on / off /on the bt on the phone to get it to not drop connection when the screen goes off. joy of the 4.2.x BT stack right?
[Samsung Galaxy Nexus] Argasil:
Great!!!! With this kerne i made 18 hours and 3 band half hour on screen on, with one hour WI FI,a little of 3g band a little of gaming!awesome man!!congratulation!!!!:good:
[Samsung Galaxy Nexus] Riekr:
[MENTION=4615478]boype[/MENTION]

i was back to r21 to test again the battery drain overnight and if i set wifi sleep policy to something different than "never sleep" the battery drain doesn't happen.

in brief, it seems it only happens (to me at least) when wifi sleep policy is set to "never sleep" either the phone is connected or disconnected from wifi.

r20 with wifi policy "never sleep" performs much better (~6% overnight).
[Samsung Galaxy Nexus] aHecticLife:
I bought a Samsung copy one and max screen on I get is 4 hours

---------- Post added at 02:01 PM ---------- Previous post was at 02:00 PM ----------

Change your contrast and play around with the gamma offset
[Samsung Galaxy Nexus] mangusZen:
And I bought one the lasted one week (1!) in term of usage, and died. Who wanna bet? :p

sent from Vega gnex
[Samsung Galaxy Nexus] kinfolk248:
is 22% drop in battery in 10 hours of idle ok? all 4g time

r21, sourcery rom 5.2

384/1036800/537600/ondemandplus
[Samsung Galaxy Nexus] boype:
r22 coming up

Hi all,

just wanted to announce that r22 is gonna hit your phones later today.

Regards
[Samsung Galaxy Nexus] momomok:
nice timing!

Perfect cure of my flash-withdrawal symptom :p
[Samsung Galaxy Nexus] boype:
r22

Hi again,

as announced, here is the result of last week's efforts. My main concern was to iron-out the phenomenon that the phone was getting slower the higher the system-up-time was. I think I succeeded ;) Here is the change log:

- updated to Linux 3.0.77

- backported staging driver (including lowmemorykiller) from 3.4 kernel (introducing superior memory handling in my opinion)

- added Hyper CPU governor

- several scheduler tweaks

- read_ahead_kb down to 256 (this may appear very low, but it is still twice as high as the stock setting and improves responsiveness imo)

- several block and file system tweaks

- fixed dirty_ratio behavior that was increasingly filling up the RAM with 'garbage' (thus slowing down the phone)

- revert attempt to fix Wifi disconnects (was apparently responsible for some idle battery drain)

- fix deadline and SIO read / write expiring (caused lags and jerky UI sometimes)

- increased voltage for 1.4 GHz CPU OPP by 0.02V (someone reported a laggy phone with 1.4 GHz, probably caused by too little voltage)

- SDRAM power management fix from TI repo

- bcmdhd: workaround broken AC video queue in IBSS mode (from CM10.1 upstream)

- pulled-in latest updates from CM10.1 ramdisk

- added automatic APK zip-alignment on boot

- moved many previously hardcoded settings to ramdisk init script

- init.d support is now independent of the ROM having busybox included or not

Even though phishn was helping me with some testing to cure the bluetooth audio issue, I am not sure I was successful here :(

Best regards
[Samsung Galaxy Nexus] agritux:
thanks fussing :)
[Samsung Galaxy Nexus] scooby25:
Thanks boype for your hard work:)
[Samsung Galaxy Nexus] Argasil:
Great for hyper, i heard a lot about it, and now i try with this awesome kernel! thx!!:good:
[Samsung Galaxy Nexus] morpheus620:
The new kernel is very very slow.

I have RootBox ROM.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Charmacas:
Let it settle down a bit. Also if you use Trickster clear the cache of the app. My Trickster settings were totally confused after flashing r22.

[MENTION=4615478]boype[/MENTION] r22 works fine here. So far it is fast and stable but only time will tell about the slowdown behaviour. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] morpheus620:
The boot animation is very slow.

the phone takes forever to start.

sorry for my english.
[Samsung Galaxy Nexus] gwindlord:
Pretty smooth after the boot (on r21 some tiny lags with interface appeared in a some time or after launching several heavy apps - ilke opening notification drawer and it went not directly under finger, but shivering a bit above, dunno if this happens here too and if this depends on kernel or ROM). Also one small mistake: I've downloaded and installed std version, settings are for std one, but kernel version in About phone says, that it is ext - just a bit inaccurate. Other things work fine, thanks!
[Samsung Galaxy Nexus] Riekr:
R22 works good and is very fast indeed! Tomorrow will report about idle battery drain.

All stocks freq and schedulers with cm10.1 rc1 (a lot faster than cm stock kernel for sure)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] boype:
Thanks for notifying me, something must have gone wrong then...

Is this every time you boot your phone? I suppose this is because the automatic zipaligning is doing its work on first boot, but this definitly should not happen on second or any further boots.
[Samsung Galaxy Nexus] jesssiii:
On r22, many different stock settings. Read-ahead on 128, not 256 as you stated. GPU gov at performance. Multicore saving at 0. CAB on. 192 set for both max screen off and min screen on. Also, my initd has one file called 98tweaks which is for SD read/write speedup.

As stated already, it did take extra long to start, I'll let you know about 2nd boot in a few. And the info says ext when I used the r.

Not complaining- just giving info because it wasn't as expected.

Edit: Reboot didn't go long so that's as you intended.
[Samsung Galaxy Nexus] chiwou:
happens on every reboot for me too, even after boot the phone takes forever to do anything

didn't happened on the r21

FYI: Carbon rom
[Samsung Galaxy Nexus] nihalot:
No offence but the colours look absolutely pathetic. The screen has a tint of purple everywhere and changing the multipliers doesnt help. This had happened on franco kernel also and it was found that setting the colours using init.d or before the system booted, gave different results as compared to setting using trickstermod. I tried finding the script that sets the colours at boot but couldn't,,, would be greatful if you could tell me where the script setting colours could be found.... Thanks!
[Samsung Galaxy Nexus] boype:
Wow, that's a lot of messed-up stuff I'm reading here. I would not have thought that such problems would arise across different ROMs.

After the reboot, are the settings (readahead etc) in place as intended?

The script is in /sbin/fancyinit.

Also, funny and unexpected stuff as everything is working fine on my end.

Anyway, looks a lot like this needs fixing.
[Samsung Galaxy Nexus] lesclark:
(r22) locked up during boot while starting apps on me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jesssiii:
Sorry Boype, I set everything as I prefer and set-on-boot with trickster before my second reboot.

If you'd like, I can purge trickster, clear cache, and reflash the kernel. Then I could reboot without changing anything to see if it's different.
[Samsung Galaxy Nexus] momomok:
feedback on r22:

everytime i reboot, part of the boot animation is lagging (in the beginning) but would resume normal speed after around 15 seconds

boot time did take longer, by longer i mean it stays A LOT longer after the screen brightness dims when the boot is almost finished

CPU frequency seems to be hardcoded to be running @ 192MHz, thus the phone is laggy as hell before Trcikster kicks in and loads my own setting

Confirms. Except there is no 98tweaks in my init.d folder, the path is /etc/init.d right?
[Samsung Galaxy Nexus] aosp:
Why not use the anykernel format and make boype tweaks init.d optional?

Sent from my Vanir-ize Galaxy Nexus using a AK
[Samsung Galaxy Nexus] buckmarble:
I can see this solving a few issues for sure. Since every ROM creates a different ram disc, packaging your own ram disc with the kernel can create issues with some ROMs. On the other side of this, the ram disc compiled with the ROM may not be sufficient for permissions required for various features in the kernel. As a kernel developer myself, I use the any kernel format. However I do not load the kernel up with a million and one options, like every governor/sched on the planet, and in turn most ROMs out there have all the necessary permissions built into their own ram disc already. So unfortunately it is a juggling trick trying to get everything functioning 100% on all ROMs.
[Samsung Galaxy Nexus] jesssiii:
Right, that innitd was not from the kernel.

Boype, I did try again fresh and second reboot settings were even wonkier than the first-everything set to max/min 192. Then SOD, had to restore my nandroid of JBSourcery 5.2.4 with it's kernel (very good one by Buck Marble!).
[Samsung Galaxy Nexus] aosp:
If the rom does not have the proper permissions that is not your fault I say focus on the kernel code and let the rom devs focus on permissions etc but seriously I know if the rom devs can't set proper permissions well it might be time to rethink your choice of rom ;)

Sent from my Vanir-ize Galaxy Nexus using a AK
[Samsung Galaxy Nexus] boype:
Okay, to all the folks experiencing slowdowns and other fukkups on boot:

I checked how franco handles things with his kernel. Please test this and report...

Sorry for the inconvenience!!!
[Samsung Galaxy Nexus] bolanrox:
Is it possible that it rom related? I had no issues at all with r22 speed at start up was more or less the same same as it had been. No issues with the settings in trixters, or lags / SOD'. On a CM10.1 based rom personally if that helps narrow down the possible issues.
[Samsung Galaxy Nexus] lippol94:
Well, I'm on Purity, which is 100% AOSP-based, and I had problems.. so ;)

I know Fancy is synced with CM sources, but it must be compatible with AOSP :)
[Samsung Galaxy Nexus] Fabur87:
Paranoid Android is also spending all its time on 192 MHz.

Will try your test kernel and report back.
[Samsung Galaxy Nexus] boype:
Oh it's definitly a ROM problem. However, I cannot handle this by saying "Got problems? Change your ROM."

The kernel needs to accommodate all ROMs.

From my understanding, there are two potential possibilities that cause the recent problems on some ROMs, and they can definitly be fixed. All I need to know is which one of those two possiblities is the right one to fix the issues. That's why I posted the test version above.

Thanks a lot!!! As indicated: If this one won't work, I'm positive that I know what will fix the issue.

[EDIT] Also, please tell me if the other settings are applied correctly (just check if the readahead_kb is 256 or not).
[Samsung Galaxy Nexus] lippol94:
UPDATE: Optimizing process is taking a lot! Definitely slower than usual.

Something is going on under the hood that makes device slower.

I/O slowdowns?

Too low frequencies at boot?

Just suggesting :)
[Samsung Galaxy Nexus] boype:
I think it's already narrowed down to the circumstance that the CPU doesn't go above 192 MHz... Fix incoming. No worries... In the meantime, I should mention in the OP that the build is broken
[Samsung Galaxy Nexus] Fabur87:
As far as Paranoid Android is concerned, with the last update for the PA ROM I am getting a much more stable speed even after a longer usage. I guess they fixed some ROM related bug that decreased performance over time.

As far as the test kernel is concerned:

Intro is still lagging as hell for the first few secs on the first boot.

App optimization is also really slow.

I am still waiting for it to finish starting up but looks like that can take a while.

Once it is up and running I will give you an update on the Trixter values.

\Update1:

Tried to start Trickster Mod. Crashed because it could create the GUI. :D

Will try again and report back. ^^

\Update2:

TCP: westwood

read ahead: 128

max freq: 1228800 (the correct value is in there?)

max screen off: 1920000

min screen on: 1920000

CAB: on

GPU: performance

if you need more values just tell me. :)
[Samsung Galaxy Nexus] lippol94:
Trickster reports these default settings:

No RAB values (it's blank)

Noop scheduler

No Frequence Profile (not even the string 'none' appears.)

Min, Max, Screen on Min, Screen On Max are all set to 192Mhz

Hyper as default governor

GPU Governor is performance

Extended Battery and Vibration control spots are blank.

All color values are blank.

It looks like Trickster can't read values from you're kernel.

Something is messed up.

EDIT: I'm running Purity
[Samsung Galaxy Nexus] boype:
Thanks, I'll just flash PAndroid and fix this up myself. Thanks for testing :)
[Samsung Galaxy Nexus] Fabur87:
It looks like different ROMs give different values in Trickser.

lippol94 has different values than me (e.g. my scheduler is still sio).

\Update:

I just tried to set new values using Trickster and when I applied the changes my screen went off and stayed like that...
[Samsung Galaxy Nexus] momomok:
trying to flash the test kernel on Purity (AOSP based AFAIK)
[Samsung Galaxy Nexus] jesssiii:
^Exact same results on JBSourcery.
[Samsung Galaxy Nexus] mpokwsths:
Everything is working GREAT here ... except the colors. The color values are way off and they cannot be fixed with the same tuning as other kernels.

The other default values are the intended ones. SIO sched., 256KB, Ondemand GPU governor, CAB disabled, multicore 2, etc etc

And everything is super-smooth and snappy. CM10.1 RC1
[Samsung Galaxy Nexus] momomok:
TEST kernel takes more than 15 minutes to optimize apps...

i'm still waiting :P

EDIT:

finally get it booted

RAB: EMPTY

IO scheduler: noop

Min Max Max Screen off Min Screen on: all 192000

CPU governor: hyper

wifi HP: off

CAB: off

FFC: off

MP: 0

Vibrator strength: EMPTY

Battery life extender: EMPTY

FSYNC: off

GPU governor: performance

GPU OC: 307MHz

SR: off for all

cannot see voltage

color setting is screwed up (though the screen looks normal, i mean, normally a bit cool-tone)

I'm on Purity 5.4
[Samsung Galaxy Nexus] boype:
This is harder than expected. For some reason I have yet to find, many ROMs (like PA) cannot execute shell scripts at boot. CM10.1 does this without any problems.
[Samsung Galaxy Nexus] momomok:
can't you put the shell script in init.d?

(I am not sure if it will work, just asking :P)
[Samsung Galaxy Nexus] Argasil:
With beanstalk base cm10.1 no problem Also hyper working well!
[Samsung Galaxy Nexus] Lancez:
I've had zero problems after flashing r22, everything went smooth. Cleared data for both pgm and trickster before flashing kernel. I'm on latest AOKP nightly May-9 build. dank boype :thumbup:

Edit: color dose seem a bit weird tho
[Samsung Galaxy Nexus] boype:
I have found the issue for everything now. Turns out the busybox binary I included in the kernel's ramdisk apparently was only made for CM ROMs. I suppose some shared libraries were missing or something.

The "weird colors": I will hardcode them into the kernel again.
[Samsung Galaxy Nexus] boype:
r23 (hotfix)

Hi all,

r23 is up. This fixes all the problems that were previously reported with r22. Here's the change log:

- replaced busybox in ramdisk with a binary file that works as a standalone version (fixed all the fukkups ppl experienced in r22)

- fixed std version reporting itself as ext version

- hardcoded color settings again (ppl reported weird colors)

- disabled ro.adb.secure (adb wasn't working; this was recently added to the CM ramdisk)

- everything should be fixed on any ROM. Sorry for the trouble :(

Best regards

(and sorry for double post)
[Samsung Galaxy Nexus] un.droid:
thanks for the hard work and fixing the issue.
[Samsung Galaxy Nexus] Riekr:
How can i keep it enabled? I'm concerned about security at work since i use it for development. Isn't it implemented on any 4.2.2 rom?

Edit: will keep USB debugging disabled but the question remains for curiosity :)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] mangusZen:
R23 so far so good for now here, normal behaviour at boot and stuff with trickster..will see later how good is battery life..Im on slimbean.

Thank you boype :D

sent from Vega gnex
[Samsung Galaxy Nexus] Blackcrx:
Please keep me posted on your results with slim