yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Reatret:
Are you planning to implement OTG? :)
[Nexus 4 Original Android Development] lazer155:
How is the screen on time for you guys who are using the bricked kernel? I looked through the previous thread posts and saw a couple 2.5-3 hour screen on times but overall not as many mentions as in some of the other kernel release threads. I'd like to get some more examples of screen on times, if possible.
[Nexus 4 Original Android Development] undercover:
2 cycles so far with 18-19h off charger with just over 4h screen on time. On the third cycle now, looks promising too. Most stable results on this kernel so far, other ones fluctuated between 3 and 4h screen on with 12-14h off charger.

Edit. Also, the coolest running kernel of all I've tested.
[Nexus 4 Original Android Development] Reatret:
Yesterday on first cycle I got about 10 hours with 4 hours screen on time. I'll post today's cycle.
[Nexus 4 Original Android Development] undercover:
If things don't change, today I could get 12h with 5h+ screen on. All depends if drain doesn't change though (not unheard off).
[Nexus 4 Original Android Development] Flynny75:
Nobody has it working. It is still being investigated. http://xdaforums.com/showthread.php?t=2048545

[Dev] USB OTG Tests
[Nexus 4 Original Android Development] lazer155:
Is that with data on or just wifi? What kind of apps are you using when the screen in on (chrome)? With the stock kernel I can only get about 3 hours of screen on time browsing over wifi with chrome and all other services on (google now, gmail syncing, gps, ect.).

I'll have to install this kernel later today since it seems to improve screen on time pretty significantly. I was deciding between this kernel and Franco for improved screen on time.
[Nexus 4 Original Android Development] undercover:
Wifi. Screen on time is superb. I still have stupid Android OS eating at my battery when sleeping though, but that's not kernels fault :(
[Nexus 4 Original Android Development] :
Harsh supposedly fixed msm_ hsic_host could you integrate that fix?
[Nexus 4 Original Android Development] Harsh:
We can't say that it is fixed until we test it for a day or two. And its from caf so showp must already have those commits in remote repo somewhere :p...

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
What exactly is causing it in a noob terms if possible? :)
[Nexus 4 Original Android Development] undercover:
People wanted some stats. As I mentioned, previous 2 cycles around 18h off charger with just over 4h screen on. 3rd cycle, just hit 50 percent.

Pretty much all the time on wifi, and Android OS still being a bastard when asleep, i just don't give it a chance to raise with keeping screen on. Will update with end of the cycle results.
[Nexus 4 Original Android Development] jarjar124:
Here are my screenshots for my battery. I'm at the Poconos and there is no reception for me, but luckily there is WiFi at the hotel. It's great battery life with WiFi. Wouldn't be as good with just HPSA.
[Nexus 4 Original Android Development] FirelordAzula:
I have fast. Perhaps I'm misremembering the stock voltage table, then. Sorry about that, show. Just out of curiousity, what's your opinion on SIO?
[Nexus 4 Original Android Development] Reatret:
Ganna end up posting my cycle tomorrow due to ROM change. Not really fair to include this cycle :P
[Nexus 4 Original Android Development] aLNG:
show, I would like to know your opinion about these:

1) ROW Scheduler: http://lwn.net/Articles/509829/

2) F2FS: https://lkml.org/lkml/2012/10/5/205
[Nexus 4 Original Android Development] show-p1984:
I am testing it for a few days already, mixed results though. (maybe because I am flashing new stuff like clockwork)

Currently I am not interested in both, but I am experimenting with a third relatively new and promising variant.

Don't waste my breath :p
[Nexus 4 Original Android Development] redeyes717:
Hi Show-p! first of all, this is best kernet out for our Nexus-4, in my opinion.

I know you've been discussing this previously, could we expect a 487/512 GPU OC sometime in the near future?

thanks.
[Nexus 4 Original Android Development] AppReviewBros:
No offense but why would you ever need that high of a clock? Isn't 400 MHz enough?
[Nexus 4 Original Android Development] show-p1984:
I'm finishing this feature up now (measured in Valve Time)
[Nexus 4 Original Android Development] tndb:
Anyone have issue with screen not locked during calls? Not sure if its rom or kernel related? Using v0.7 along with modaco Jr5.

Also had touch screen unresponsive on two occasions, I could lock and unlock with power button but screen didnt react at all on touch until I rebooted. Using ondemand governor and 192MHz min / 1512MHz max with no other settings touched.. any ideas?

Otherwise a really nice kernel :)
[Nexus 4 Original Android Development] show-p1984:
Will be fixed with the next version.

First time this issue was mentioned here.

Bug reports => Issue tracker.

With a log and as much information as humanly possible please.
[Nexus 4 Original Android Development] FirelordAzula:
No issues like that here. Running ondemand (UV too) at 192MHz/1026MHz on stock.

Ah, thanks!
[Nexus 4 Original Android Development] redeyes717:
no offense at all alwaysbboy; I don't even need of a custom kernel with this Nexus-4; 'overclocking' is a kind of 'proof of concept' for hardware (il)limitation.

thanks my friend (Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law.)
[Nexus 4 Original Android Development] meangreenie:
I can see gpu overclocking only causing more heat problems, thermald triggers will just be hit that much quicker.. will all the thermal routines throughout the system be adjusted to accomadate it ? what happens when a thermal trigger (battery or cpu) calls for downclock to 325 and it's not there ? for example
[Nexus 4 Original Android Development] :
Update: franco integrated the patch from qualcomm and said it fixes the msm_hsic wakelock :)
[Nexus 4 Original Android Development] show-p1984:
I am already testing it since christmas eve, mixed results though.
[Nexus 4 Original Android Development] zyonee:
It certainly seems to work. I integrated it on the CM10.1 stock kernel and it surely seems to work on that one too.
[Nexus 4 Original Android Development] show-p1984:
Update:

I am relaying the contents of my conversation with him here.

Faux said that he won't open source it (because of the developer redacted) and goes the way of a pre-compiled lib which can be included into the kernel at compile time. He provided this lib, but since it is a GPL infringement in my point of view I won't include it.

(There has to be source to everything that is needed in order to built the kernel in the repo and especially routines that the kernel uses, otherwise we are not GPL compliant which is a big deal to me.)

No hard feelings towards Faux, don't misunderstand this post.
[Nexus 4 Original Android Development] Mahdi786:
Hi show-p, I'm trying to compile your kernel from source but I keep getting an error with fs/nameie.c file in line 2885.
[Nexus 4 Original Android Development] show-p1984:
Without the error, the used toolchain and build environment I can't help you.
[Nexus 4 Original Android Development] Holo_:
How is this ok GPL? So called linux devs using open source now for fame and glory pathetic. show you rock keep up the awesome work dude keep the tradition of using skills to help others but not for financial gain going thanks ;)
[Nexus 4 Original Android Development] Harsh:
1+ completely, this should not happen in something which is GPL. If he makes changes to kernel source those should be available according to open source nature of this community or he should find another way to do it without kernel changes.

If you wanted you could do similar with sweep2wake but you did not do it, and provided proper sources. Salute you for that.

Faux can use sweep2wake but can't give gamma control changes. Seems unfair.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mahdi786:
I'm using Ubuntu 12.04, Google GCC 4.6

The error: fs/namei.c: In function 'do_unlinkat':

fs/namei.c:2885:2: warning: 'name' may be used uninitialized in this function [-Wmaybe-uninitialized]

error, forbidden warning: namei.c:2885

Thanks for your help
[Nexus 4 Original Android Development] ghostrid3r:
Agreed, which is why I personally do not support his development and/or products due his lack of GPL compliance among other reasons (closed source for profit) which doesn't evolve our community as a whole the way open source was intended to do.
[Nexus 4 Original Android Development] Holo_:
s2w will now require a special glove to work email me for prices on my new s2w proof gloves ;D
[Nexus 4 Original Android Development] jhericurls:
+1
[Nexus 4 Original Android Development] show-p1984:
I don't use the google toolchain, (I use the linaro baremetal) but simply initializing 'name' would probably get you one step further. The compiler is telling you everything you have to do :)

Haven't looked at the code, but I suspect it looks somewhat like this:

function(name);

Look at the beginning of the function in which the above line is, you should see something like this

char *name;

Change it into

char *name = NULL;

(I guessed char as type since the variable name suggest a string, the pointer makes sense in namei.c. Check if my assumptions are correct)
[Nexus 4 Original Android Development] Mahdi786:
Thanks I'll be with my PC in about 30mins, I might try compiling with linaro instead, I've fixed errors compiling ROMs before but I'm new to compiling kernels, just a quick question can you tell me which file I can specify the toolchain in other than .bashrc.

Thanks
[Nexus 4 Original Android Development] show-p1984:
ensure it's in your PATH and then just feed CROSS_COMPILE to your make command.

But I prefer the .bashrc method, it has a few advantages.
[Nexus 4 Original Android Development] Mahdi786:
Thanks show-p, your very helpful.
[Nexus 4 Original Android Development] undercover:
I see. Well, I'll refrain from comments.

I support your stand in regards to compliance with GPL 100% of but is it possible to include the lib file post compiling? Ie add to kernel zip before flashing, or just flashing it after? This way users can benefit from it, Faux would get his profit since you need his app to control it and you would stay GPL compliant. It is obviously questionable wherever this is right or wrong, but in the end of the day, everyone gets what they want. Profit.
[Nexus 4 Original Android Development] show-p1984:
Even if I could somehow squeeze it into a module and provide it post compile insert-able I wouldn't.

I am not spreading/using infringing binaries.

Last comment on this issue from me, I didn't expect to kick loose a sh*t war about this with a simple status update regarding the gamma control feature.
[Nexus 4 Original Android Development] undercover:
Understood. :)

No war.
[Nexus 4 Original Android Development] Mahdi786:
Hi show-p, I got it working. Its still compiling but I got through that part, will putting a NULL on those parts cause any adverse affects or is it just to stop the compiler throwing errors? Sorry if I'm doing your head with all these questions.
[Nexus 4 Original Android Development] faux123:
The library DOES NOT modify the kernel in any way. Not a single line of change was made to the kernel. It is more of an Extension to the capability of the kernel (This is HOW I got it to work with STOCK kernel since STOCK kernel is a pre-compiled binary, no further changes can be made to it). I provided this library to Showp as a binary only solution but showp has made his decision and I respect him in that.

I originally had an open source solution which modified the LG's video display driver but I decided to remove it because of certain individual and made me to seek a proprietary solution around it. It is unfortunate that I had to resort to proprietary solutions instead of open source but I had my reasons and had discussed with showp about my reasons.
[Nexus 4 Original Android Development] show-p1984:
The compiler usually complains about those issues because there is a possibility that this code is reached without the variable/pointer being initialized first, which would throw a npe. The compiler assumes that you are an idiot and that this shouldn't have happened. Show him (I like my compiler to be a person) that you aren't and set an initial value for the variable/pointer. Even though it is now NULL, which would throw a npe too, the compiler now knows that this is probably intended, eg: We want to catch a bug, or do some special error handling in this case.

Indeed, that it is.
[Nexus 4 Original Android Development] Mahdi786:
Ok, I got another error from drivers/media/common/tuners/xc5000.c something about id not initialised, so I thought forget googles toolchain, I downloaded linaro 4.7 binary version, changed my .bashrc and its compiling now and it went straight past namei.c so looking good, thanks for all your help show-p.

Just to say I was following your work even before I got my n4, I've got a galaxy s2 and I'm sure your code was used to port sweep2wake to it.

Edit: compiled without any errors with linaro toolchain thanks
[Nexus 4 Original Android Development] Reatret:
I return with my first cycle on CM 10.1
[Nexus 4 Original Android Development] Reatret:
About 12 hours with 3 hours screen on.
[Nexus 4 Original Android Development] mbolinao:
flashing over another

Im interested in trying this kernel because of sweep2wake.

im currently using another non-stock kernel (franco) and im wondering if i can just simply flash the zip of Bricked kernel from recovery, or do i need to go back to stock kernel first before i flash Bricked kernel?

thanks!
[Nexus 4 Original Android Development] w0dash:
You have to flash the stock boot image before that (can be found in the #1 post).
[Nexus 4 Original Android Development] eep2378:
Flash the kernel reset zip from Faux's op, then flash bricked. :D
[Nexus 4 Original Android Development] mbolinao:
thanks!

is it always like that even with other kernels, flash stock before a new one?

or just with bricked-kernel?

---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------

thanks! downloading that now :good:
[Nexus 4 Original Android Development] Harsh:
You have to flash reset kernel only if coming from franco. Other all kernels have no problem in swapping from one to another.
[Nexus 4 Original Android Development] eep2378:
^^^this. Franco kernel uses a modified ramdisk. Hence the need to flash stock when coming from his.
[Nexus 4 Original Android Development] mbolinao:
thanks man!

haven't flashed the reset yet but problem is, the reset kernel says it's only for stock roms... forgot to mention im on a custom rom (ParanoidAndroid). yikes! have to sort things out.
[Nexus 4 Original Android Development] eep2378:
Shouldn't matter. If you're currently on franco, the reset zip will only change the kernel back to stock settings(franco kernel is based on stock, as are all kernels here).
[Nexus 4 Original Android Development] mbolinao:
ah cool! thanks!

lemme flash Reset and Bricked then. will post update! ;)

---------- Post added at 11:23 PM ---------- Previous post was at 11:01 PM ----------

sweep2wake is cool!

will observe this kernel for a few days. i hope battery and speed/smoothness is good.

thanks guys!!
[Nexus 4 Original Android Development] zimphishmonger:
Here's my feedback, been using v.7 since its release. Quite stable, no reboots or kernel panics. runs really well using on-demand, not so well with interactive (scrolling, lwps and other ui movement is significantly delayed, exec with a a 384 min). No heat issues at all, def cooler than stock when stress tests. Able to keep a universal 50mv undervolt no problem, I'm sure others can handle lower voltages. Battery life has been between 10 and 14 hours depending on usage even using 1.134 / 384 on-demand. Idle power usage is excellent (no exact rating, just observation via leaving the phone chilling on my desk for hours)

S2w working well also. Noticed it seems to have an issue with detecting your face touching the screen during a phone call, such causes done strange, unexpected results lol. No difference that I can notice between s2w enabled or disabled:)

It's not brick related, but I have been having issues with touch screen response even using s2w on faux, but no such issue with bricked. Simple observation, not comparing one better over the other. Been trying to pull a log for that to see if s2w has anything to do with it. More of an fyi, as I know it's for fauxs kernel

Sent from my Nexus 4
[Nexus 4 Original Android Development] chiensibut:
does bricked has play store app?
[Nexus 4 Original Android Development] show-p1984:
Very soon(tm)

I felt that getting the kernel ready was more important and therefore paused developing the app.
[Nexus 4 Original Android Development] Somairotevoli:
Finally phone feels just right. Running interactive at 1.5. Undervolted by 150. No need to overclock. Zero lag, bye throttle.

Sent from my Nexus 4 using Xparent ICS Tapatalk 2
[Nexus 4 Original Android Development] yyz71:
Gonna dl now.
[Nexus 4 Original Android Development] Imperticus:
Will you be making a cm10.1 compatible version?
[Nexus 4 Original Android Development] show-p1984:
Last time I checked it was compatible :)
[Nexus 4 Original Android Development] Imperticus:
Oh, just that people were complaining about non-booting. Thanks, will try it :D
[Nexus 4 Original Android Development] boykioy:
Thanks loving it so far.Any chance to tweak the RGB color to reduce greenish-yellow tint? :confused:
[Nexus 4 Original Android Development] batman368:
unfortunately the same for me, no wifi, id flashed stock kernel and modules from motley thread, then bricked, and i wiped caches before and after every flashing action. i'm using PA 2.99b8, could that be the issue?
[Nexus 4 Original Android Development] vanhouche74:
many reboot on CM10.1 ...
[Nexus 4 Original Android Development] show-p1984:
The zip adds init.d support to your ramdisk, if that fails for some reason the wlan module cannot be inserted.

if

adb shell lsmod

doesn't show this:

tun 14701 0 - Live 0x00000000
cifs 275399 0 - Live 0x00000000
wlan 2964650 0 - Live 0x00000000 (C)

Then init.d support is missing from your ramdisk.

You can test it by going to /system/etc/init.d/ and executing 00wlan.

adb shell
su
. /system/etc/init.d/00wlan

Wait a few seconds and try to enable wifi and repeat the above lsmod command (should now show wlan, you can execute 01cifs and 02tun too).

If wlan now works, init.d support is missing from your ramdisk (still).

I would ask you to give me a dump of your /boot partition so I can adapt for that special case, do:

adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/boot.img
exit
exit
adb pull /sdcard/boot.img

Upload it to DB, or send it as an email.
[Nexus 4 Original Android Development] air2k57:
So far so good on stock ROM. My only problem is with aroma.... Literally froze 3 times on one of the next screens.
[Nexus 4 Original Android Development] show-p1984:
Let me guess, twrp?

It has atm no thermal limit( + performance governor if you have an old version, check the thread), in other words it cooks your cpu. Might not have anything to do with aroma :)

I built a special kernel version just for Dees_troy and he will release an updated, thermal limited twrp version with Bricked some time today.
[Nexus 4 Original Android Development] italia0101:
Hows the thermal limits for people using this on .. on stock clocks ... is it throttling later ? smoother in games etc?
[Nexus 4 Original Android Development] show-p1984:
Limits are:

/sys/kernel/msm_thermal/conf/allowed_low_freq 1350000
/sys/kernel/msm_thermal/conf/allowed_low_high 70
/sys/kernel/msm_thermal/conf/allowed_low_low 64
/sys/kernel/msm_thermal/conf/allowed_mid_freq 1026000
/sys/kernel/msm_thermal/conf/allowed_mid_high 72
/sys/kernel/msm_thermal/conf/allowed_mid_low 67
/sys/kernel/msm_thermal/conf/allowed_max_freq 384000
/sys/kernel/msm_thermal/conf/allowed_max_high 76
/sys/kernel/msm_thermal/conf/allowed_max_low 71
/sys/kernel/msm_thermal/conf/check_interval_ms 250
/sys/kernel/msm_thermal/conf/shutdown_temp 80
[Nexus 4 Original Android Development] GabrielSousa:
luv to see you here,

on my old sensation, i used your great kernel ;)
[Nexus 4 Original Android Development] Somairotevoli:
Gaming with music in background. Smooth all around. Like it should.

Sent from my Nexus 4 using Xparent ICS Tapatalk 2
[Nexus 4 Original Android Development] italia0101:
looks sweet!

i take it no ones had any issues on the OC ? i saw a lot of hardware failures last time there was OC , even if people wernt using it it would ramp up , but looks like its fixed here
[Nexus 4 Original Android Development] ragiut1:
Are you using AOKP?
[Nexus 4 Original Android Development] GabrielSousa:
@show-p1984

how we do UV ?
[Nexus 4 Original Android Development] westernmg:
I wanted to try out this kernel on the newest Rasbeanjelly ROM, but unfortunately the wifi will not start.

I Installed Rasbean 2x with complete wipe anf flashed the kernel afterwards, but with the same results.

The included kernel and Matrix does not have this problem.
[Nexus 4 Original Android Development] jan.ringas:
Did you try the steps mentioned in the second post (http://xdaforums.com/showpost.php?p=35667484&postcount=2) labeled with "

Why do I have no WLAN?

"?
[Nexus 4 Original Android Development] westernmg:
No i haven't, sorry for having not enough coffe in my brain this morning :cyclops:

Thank You!
[Nexus 4 Original Android Development] Thorsten_de:
Hi!

With the Bricked Kernel v0.7 I have trouble with my Bluetooth connection in my car.

The connection works with phone and audio but the phone show always change between "audio connected" / "audio disconnected".

About the continues connection errors my battery drains very fast in car.

Thorsten.
[Nexus 4 Original Android Development] Holo_:
Happy new year world who can't wait for more awesomeness from show-p1984 in 2013? ;)
[Nexus 4 Original Android Development] Thorsten_de:
Hi!

With the faux 003 beta 7 Kernel my bluetooth works fine...?

Send with Nexus 4 CM10.1 and faux 003 beta 7 Kernel.
[Nexus 4 Original Android Development] show-p1984:
Hi, Thorsten.

With a log I could actually do something about that, since my Blauzahn works fine too.

Bug reports => Issue tracker with as much information as humanly possible.
[Nexus 4 Original Android Development] undercover:
You are not drunk yet? Bloody Germans, have to do everything on time. :D

Have good 2013 show. :thumbup:
[Nexus 4 Original Android Development] show-p1984:
You too!

I am not drunk, yet. But I just opened my supplies for tonight :)

7.25L of Coke, 2 bottles of Wodka, a few kilograms of potato salad and some Ciabatta :)

So I am out now :P
[Nexus 4 Original Android Development] Holo_:
In case you want to know if the bin within is win thanks to show-p1984 this can be known at any time using this command

cat /sys/kernel/debug/krait_variant
[Nexus 4 Original Android Development] grisha1:
Very anxious about upcoming goodies :cool:
[Nexus 4 Original Android Development] show-p1984:
Yeah me too.

#hangover
[Nexus 4 Original Android Development] sideeffects:
Me2 been waiting all year.
[Nexus 4 Original Android Development] cheapskate88:
Has anyone figured a way around this bug? I was hoping it was CMs fault but apparently it might not be.

I did a full wipe and I haven't tested to see if this issue is still around, but I wanted to hear you to guys.
[Nexus 4 Original Android Development] show-p1984:
Actually it is not a s2w bug but an Android bug.

For some reason jellybean does not deactivate touchscreen inputs when the screen is offline, it relies on the kernel to do that which in the case of s2w would prevent us from sweeping when the screen is offline.

However since the kernel should never break userspace I have a fix for that in my local repo which will come as a package with s2w 2.0 which will fix and extend a lot.
[Nexus 4 Original Android Development] jarjar124:
Can't wait for s2w 2.0 :D