yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Sblast:
This maybe something quite major so I'm posting this in both threads;

I'm getting soft reboots using phone calls. if the call starts and the call continues while the screen is off, the moment I turn it on I get a soft reboot. This also happen when I let the screen turn itself on. This happens on two ROMs with two kernels (crDroid + AK 0.25, Beanstalk + BCM kernel, W3 R2). I'm having trouble pinpointing exactly what's the cause (maybe related to s2w?). Tell me what log (logcat?) to use and I'll post it.

UPDATE:

FFS this toke me a while...it's in all probabilities TWRP_Framework_Animation_MOD_5.3, maybe because those ROms don't come with busybox? I'm testing. Contacted Dev, I hope he will help.
[Nexus 4 Original Android Development] BytecodeMe:
In laymens terms auto_hotplug is a bit more tweakable and customizable but mako_hotplug performs better IMO
[Nexus 4 Original Android Development] ak:
I have reply to this problem on AK thread:

Softreboot = userspace problems = rom
[Nexus 4 Original Android Development] MasterLinuxer:
Hard decision.. I think the more tweakable and cuztomizeable the better unless the price is performance..

Although I know nothing on this specific issue so I don't really know what I'm talking about :p
[Nexus 4 Original Android Development] BytecodeMe:
I know that the poll is close, "Yes" won by one vote... due to this, I will be keeping the voltages stock out of the box because I don't think that its good practice, it hasn't seemed to be much of a big desire to most at this point, displayed by a 1 vote lead. If any of you would like to give me some reasons you think it should be undervolted by default, I'd be happy to listen.
[Nexus 4 Original Android Development] ak:
it's hard to make a decision now. You are the judge and the last word is in your hands.
[Nexus 4 Original Android Development] :
I don't see why it should be undervolted by default. If somebody wants to undervolt, they can. That's all that matters.
[Nexus 4 Original Android Development] BytecodeMe:
Hmmm... Franco's doubletap or sweep2wake. I'm leaning towards doubetap because it is new and will most likely not have wake issues as the digitizer is kept online.

new weekly should be... tomorrow?
[Nexus 4 Original Android Development] Goku80:
let it be fully checked first before using it...i tested it and works great but sometimes when you are in a call you have to double tap to just open the screen and hang up the phone...other than that great feature..
[Nexus 4 Original Android Development] nileshgr:
sweep2wake is enough, but only thing is it needs some patch so that it doesn't conflict with pie.

On this as well as on AK, I had the conflict problem, pie used to stop working randomly.

But for some reason it hasn't happened yet in many hours on Hells Core B3.

I generally don't talk about other kernels in some different thread, but, [MENTION=4581171]BytecodeMe[/MENTION] & [MENTION=3685904]anarkia1976[/MENTION], check the patches there. You might be able to improve s2w /s2s.
[Nexus 4 Original Android Development] Sblast:
I have done that mistake a few months ago...it keeps waking in your pocket (t2w). Is this a different module? Can't you keep both just in case? :cowboy:
[Nexus 4 Original Android Development] Ace42:
Double tap like the G2.
[Nexus 4 Original Android Development] nileshgr:
It's precisely the reason I'm not in favor of dt2w
[Nexus 4 Original Android Development] Ace42:
You guys don't use cases...? :confused:
[Nexus 4 Original Android Development] nileshgr:
Nope. I use dbrand skin. If I use a case, my hands starting aching because of the increased size and also my typing accuracy drops.
[Nexus 4 Original Android Development] desmoloch:
Nice work :) flashed today
[Nexus 4 Original Android Development] BytecodeMe:
I'll keep both, though I must say, Franco did a great job. It's very responsive and wakes up right away from deep sleep.
[Nexus 4 Original Android Development] :
Is it possible to change the governor settings somehow? Faux's app doesn't let me, but I feel like interactive doesn't need 1,5ghz on screen touch.
[Nexus 4 Original Android Development] desmoloch:
You can use trickster
[Nexus 4 Original Android Development] MasterLinuxer:
Last time I used sweep2wake it drained the hell out of my battery
[Nexus 4 Original Android Development] snak3ater:
It drains battery but not that much.Something else mush have happened.

It will have massive drain only if you put the phone in pocket all the time..Been using Touch control & s2w..No issues in both of them.Only suspend_backoff wakelock of around 10-15mins out of whole 24Hrs..I guess 15mins is nothing
[Nexus 4 Original Android Development] drdrewdown:
Loving the kernel so far, great standby time/life
[Nexus 4 Original Android Development] VIPOA:
Hi :)

I want to download the kernel but I don't know which zip is what...

Can anyone help me or explain to me which zip should I download?

Thanks in advance :)
[Nexus 4 Original Android Development] BytecodeMe:
BCMMako-W3-R2 is the most recent. Download the JSS or the JWR version depending on which ROM you're running.
[Nexus 4 Original Android Development] VIPOA:
:good: Thanks!

BTW

what is BCMMako-W1-T3.zip (from 21-Sep)?
[Nexus 4 Original Android Development] BytecodeMe:
The first weekly I was too lazy to give a more clear name :)
[Nexus 4 Original Android Development] VIPOA:
lol

Flashing the kernel now :D
[Nexus 4 Original Android Development] BytecodeMe:
So in this weekly I spent a lot of time going through all of the patches to 3.4.yy to pick all of the bug, deadlock, crash, and memory leak fixes. Over 100 patches on that end. Noticeable increase in speed just from that. Also enabled -O3 optimization and I didn't take any shortcuts with it. Got all the warnings fixed. also added Franco's Doubletap to wake. Just gotta add sweep2wake back.
[Nexus 4 Original Android Development] Ace42:
Is double tap buggy like the G2's version? I heard it doesn't always respond to taps.
[Nexus 4 Original Android Development] BytecodeMe:
Well... Tbh I feel like its responsive to the point of buginess. It turns on TOO well imo
[Nexus 4 Original Android Development] MasterLinuxer:
So I did my own little research to find which governor is the most battery friendly. I checked Wheatley, dancedance and intellidemand. Weirdly enough IMO, the device couldn't get into deep sleep with Wheatley what so ever, and with DD it was on deep sleep about 50% of the time although I haven't used the device at all! (Screen off, no WiFi..).

Intellidemand on the other hand was 99% of the time on deep sleep. Also, when I was actually using the phone, it was on much lower frequencies.

With UV, underclock and this governor I got a LOT of time without a charger (I have to be outside with no charger for a few days).

Long story short: Intellidemand is highly recommend by me both for performance and juice savings.
[Nexus 4 Original Android Development] TheNerd:]:
So w4 hasn't been released yet?
[Nexus 4 Original Android Development] BytecodeMe:
Nope. Soon tho. (Not tonight)
[Nexus 4 Original Android Development] :
Is intellidemand even integrated? I can't find it.
[Nexus 4 Original Android Development] BytecodeMe:
Yes, I put it in with W3 R2.
[Nexus 4 Original Android Development] MasterLinuxer:
Yup. I did it all through FauxClock
[Nexus 4 Original Android Development] BytecodeMe:
Changelog and OP updated with new builds. Look in Changelog. Flash it and enjoy. :)
[Nexus 4 Original Android Development] Sblast:
Totally sweat. I'm away the next few days in the desert, I hope this kernel helps me ;). THanks for update!
[Nexus 4 Original Android Development] drdrewdown:
good lookin out, i love all the different governor options in this kernel (regardless of what people say about them being useless) i prefer the option to test various configs.

i notice various mentions of faux simple gpu governor, but (like some other kernels) simple gpu is not configurable via fauxclock. I assume it's available in trickster but i won't use that app.

thanks again bcm
[Nexus 4 Original Android Development] BytecodeMe:
In the latest version of Fauxclock faux took out the option to use Simple. Which makes no sense to me but it's his app...
[Nexus 4 Original Android Development] drdrewdown:
lol yea that is weird
[Nexus 4 Original Android Development] BytecodeMe:
Especially since it's his governor!
[Nexus 4 Original Android Development] drdrewdown:
agreed, <sense.made>="0"

got the JSS kernel running on both my n4 & the wife's too. Can't think of anything else in the config/settings that i'd like to see, you got all the good stuff in there.

thanks for sharing this with us.
[Nexus 4 Original Android Development] Ace42:
How should we enable double tap?
[Nexus 4 Original Android Development] BytecodeMe:
Not even Franco's app supports it yet. Gotta do it like this:

echo "Y" > /sys/module/lge_touch_core/parameters/doubletap_to_wake
[Nexus 4 Original Android Development] Ace42:
It can still be copied into an init.d script?
[Nexus 4 Original Android Development] BytecodeMe:
Yep.
[Nexus 4 Original Android Development] QUIETLYloud:
From my understanding simple gpu governor was causing issues with the cam...

But the option is still available
[Nexus 4 Original Android Development] QUIETLYloud:
See...
[Nexus 4 Original Android Development] BytecodeMe:
Let me rephrase, faux took out support for Simple unless the sysfs matches exactly. And as I'm using franco's mods to Simple which takes out laziness it will no longer show. Correct, Simple causes some problems with camera after a short time in the app. Still makes no sense to me.
[Nexus 4 Original Android Development] drdrewdown:
Kernel running good, great battery life. Something happened to me within 24hrs of flashing the kernel & I considered it a fluke. Nova launcher lost all widgets after an unexpected reboot, then the same thing happened to my wife's phone this morning (again less than 24hrs after flashing). It hasn't happened to me again, but thought i'd mention it anyway.

not really any harm done, just thought i'd report it.

Thanks again for great kernel, I lost 3% overnight with everything enabled as usual.
[Nexus 4 Original Android Development] ddloco:
Wow I had this happen on apex last night I wonder if fsync is off or dynamic fsync I thought it was just me but I see someone else having this problem

PS I installed bcm yesterday so its the only thing I've changed in my setup

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] drdrewdown:
that's funny, happened to you in the same 24hr window. I wonder if it'll happen again, i've been running it for a few days now & only happened the once. i know dfsync is enabled for me, via faux

edit: uggh, just looked at my phone & it's at the boot animation bootlooping. Doesn't appear it's going to boot up, likely data corruption. good thing i made a backup the other day
[Nexus 4 Original Android Development] BytecodeMe:
Probably a good idea to turn off Dynamic fsync. I never have problems with it but it seems some of you do.
[Nexus 4 Original Android Development] drdrewdown:
so it's better to have dfsync disabled to maintain data integrity?
[Nexus 4 Original Android Development] BytecodeMe:
Correct 100%.
[Nexus 4 Original Android Development] drdrewdown:
Lost 4% overnight (everything enabled as always) again with 70% deep sleep. Awesome just awesome :good:
[Nexus 4 Original Android Development] ak:
I have see here great support by dev ... But poor thanks quantity .... Push the button guys

reply from Neo revolution kernel :)
[Nexus 4 Original Android Development] BytecodeMe:
Unfortunately it doesn't seem like a whole lot of people look at the thread.
[Nexus 4 Original Android Development] drdrewdown:
keep up the great work & more will come. :good:
[Nexus 4 Original Android Development] MasterLinuxer:
This is by far the best one out there.
[Nexus 4 Original Android Development] BytecodeMe:
Thanks, guys I will. :)
[Nexus 4 Original Android Development] BytecodeMe:
Looking through commits and I'm really starting to like the look of franco's thermal driver....
[Nexus 4 Original Android Development] drdrewdown:
hrrm, intellithermal is awesome IMO.. With that we'd no longer be able to use fauxclock to control it right? My fav thing about this kernel is that I don't have to use trickstermod lol

Mind sharing what looks so nice about it?
[Nexus 4 Original Android Development] BytecodeMe:
I like it better for a few reasons:

Designed in conjunction with mako_hotplug a boost in efficency by itself. A dependency of mako_hotplug is load_stats, which is custom from franco based off of msm's run queue stats, and since I'm using Intelli-Thermal there is a loss of efficiency since both Franco's msm_thermal AND mako_hotplug pull code from load_stats.

Is also just much more intelligent out of the box, less polling when device is cold and more when its hot, dedicated workqueues... overall more refined code imo

Can't say I WILL use it, depends on the temperature on my day of testing, let's see.
[Nexus 4 Original Android Development] BytecodeMe:
I also just tricked Fauxclcok into supporting Simple governor again lol

https://github.com/BytecodeMe/BCM-mako/commit/34eeacb6339c8959e59fc2cd615dbc6dcb2ef146

Just note that value when it shows up in Fauxclock won't actually do anything :)
[Nexus 4 Original Android Development] :
Very small but noticeable bug, sometimes when I move the lockscreen ring on the homescreen, or when I open the app drawer or when I press a softkey it doesn't vibrate when touched. Anyone else experiencing this? Other than that great kernel!
[Nexus 4 Original Android Development] BytecodeMe:
Didn't notice this until you mentioned it but it is there... though it may just be that the vibration is too weak to be felt? I turned the Vibration motor up to 100% and am not getting it so far. Can you try that?
[Nexus 4 Original Android Development] :
Will try it in an hour. Thanks dev, much appreciated :)

How exactly do you increase the vibration motor?
[Nexus 4 Original Android Development] BytecodeMe:
Nevermind, you're correct. It does skip vibrations every once in a while. I'll look into it.
[Nexus 4 Original Android Development] nileshgr:
Enabled dt2w and screen stopped responding, lol
[Nexus 4 Original Android Development] BytecodeMe:
Log please
[Nexus 4 Original Android Development] nileshgr:
/proc/last_kmsg, right? Anything else?
[Nexus 4 Original Android Development] BytecodeMe:
Hmmm last_kmsg and kmsg if possible.
[Nexus 4 Original Android Development] :
Just wanna say thanks bytecode. Your support and passion about the kernel are awesome! Thanks for all the work you put into it.

Considering franco's hotplugging. Maybe you could start your own kernel control app even though It'd be a bit of work. I'd gladly pay for it though.
[Nexus 4 Original Android Development] BytecodeMe:
That would actually be really fun. The most I've done on the app side of things is an app to collect last_kmsg and logcats but I think it would be really fun to do. Very challenging. :)
[Nexus 4 Original Android Development] :
Before I forget: does anybody have an explanation for all the different tunables in the governors at hand? I'd like to test a bit, but unfortunately have no idea what the tunables do.
[Nexus 4 Original Android Development] MaluNoPeleke:
Great work BytecodeMe! I really like your kernel and I have tested a lot of them. Thanks for your work! I am looking forward to Francos thermal control ;)
[Nexus 4 Original Android Development] nileshgr:
Could not get kmsg, cp /proc/kmsg /storage/emulated/0/kmsg yielded an empty file. Though I noticed dmesg and kmsg contains same messages, so here's the dmesg.
[Nexus 4 Original Android Development] BytecodeMe:
Looks to be an IRQ problem, might be some patch of mine that I have applied fault or DuobleTapToWake itself.

I tihnk I know what patches are causing it, but on my first hunch but I can't be sure.
[Nexus 4 Original Android Development] Goku80:
How to enable touch to wake friend
[Nexus 4 Original Android Development] nileshgr:
But it's working for you right?
[Nexus 4 Original Android Development] BytecodeMe:
To be honest the only bug reported I also get is the vibration not happening when touching home keys and stuff every once in a while.

For the 2 days I used DoubleTapToWake it worked fine.

[MENTION=4550577]Goku80[/MENTION] with the script in this post. AFAIK there isn't an app that supports it yet.

http://xdaforums.com/showpost.php?p=45930268&postcount=48150
[Nexus 4 Original Android Development] nileshgr:
Hm. My screen just stops responding when I enable it. And I have to issue reboot from adb
[Nexus 4 Original Android Development] BytecodeMe:
Does it lock up immediately? Just went back to using it and it's working as intended.
[Nexus 4 Original Android Development] nileshgr:
1. Screen off, connect USB

2. echo Y > /sys/modules...

3. Double tap -> nothing

4. Button, try to unlock, not responding.

5. Reboot from adb

:(

---------- Post added at 08:36 AM ---------- Previous post was at 08:25 AM ----------

What min freq do you recommend? I notice that you have enabled support for 162 Mhz but default is 384 Mhz
[Nexus 4 Original Android Development] BytecodeMe:
Try activating while the screen is on. I've been activating it from my phone with a script and its worked just fine. Try replacing Y with "1" as well.

I use 162Mhz as my lowest frequency.
[Nexus 4 Original Android Development] nileshgr:
Bahahaha that helped. I did it by executing command in connectbot.

If you're using init.d script, how it works, because AFAIK init.d script gets executed when phone boots (ie during boot animation?)
[Nexus 4 Original Android Development] nileshgr:
Enabling it made my phone unstable :s

It used to reboot every time I ended a call (randomly).

Some ROM incompatibility I guess. I had to wipe dalvik to get things working back (since things were crashing even after reboot with dt2w disabled).
[Nexus 4 Original Android Development] pardonmyownage:
Neither version boots with latest PA 3.99? Bad download?
[Nexus 4 Original Android Development] Dabaum:
Might be a silly question, or one that can easily be answered by flashing it, but does this kernel have multi-core power saving, like I saw in Neo's kernel? With it enabled, and having min/max cores set to 1 & 3 respectively, I've been getting better battery life for my usage.
[Nexus 4 Original Android Development] drdrewdown:
must be, i'm using latest 1002 PA nightly build & all is well. Kernel is awesome!
[Nexus 4 Original Android Development] BytecodeMe:
Neo's kernel and all kernels with that ability are using auto_hotplug with motley's changes. I'm using mako_hotplug as I think it is higher performing. I can tell you however that this kernel has awesome idle battery drain. :)
[Nexus 4 Original Android Development] BytecodeMe:
Have any of you heard of the ROM Gummy? It's being resurrected and I'll be maintaining for mako. Will be a few weeks but I'm excited. Test builds are very promising. :)
[Nexus 4 Original Android Development] BytecodeMe:
Franco has said this about Double Tap Two Wake... http://xdaforums.com/showpost.php?p=46143298&postcount=48924

So expect problems more or less
[Nexus 4 Original Android Development] Sblast:
Sry if this has been asked...any way to enable s2w via an app (I use Tirckster/Faux)?
[Nexus 4 Original Android Development] BytecodeMe:
sweep2wake was taken out for double tap to wake. Was gonna be a bit of work to get them to work together. So not right now.
[Nexus 4 Original Android Development] BytecodeMe:
I can tell you all right now there is 100% no possibility of me accommodating CM's (stupid) decision to switch to CAF drivers. Creates fragmentation in the one phone there is NO fragmentation. So please, don't ask if I'll pick from them to fix the problems on CM and all ROMs based off of them that won't (make a smart decision) switch back to the AOSP drivers. :)

/rant

P.S: Yes, this pisses me off.
[Nexus 4 Original Android Development] snak3ater:
Why not adding back s2w until the double tap issues gets sorted out. double tap is in its easy stages, having bugs & not ready did every day usage.. It's just a suggestion :)
[Nexus 4 Original Android Development] BytecodeMe:
I'll probably end up spending the time to get both of them.
[Nexus 4 Original Android Development] BytecodeMe:
The downloads are going to be down most likely until morning(EST) so please be patient :)
[Nexus 4 Original Android Development] :
how's the status of the skipping vibrations bug fix?
[Nexus 4 Original Android Development] snak3ater:
Lol..This auto correct messed up what i wanted to say :laugh:
[Nexus 4 Original Android Development] MaluNoPeleke:
The qcom_rx_wakelock keeps my phone awake. Is there anything that I can do to fix that? Thanks
[Nexus 4 Original Android Development] BytecodeMe:
Haven't had time

to look into it tbh

That's a typical kernel wakelock but usually not so bad. Only thing I can think of is get a more stable connection?
[Nexus 4 Original Android Development] senthilrameshjv:
Sorry for OT. But, curiosity got better of me. I've been hearing about CM for all the wrong reasons nowadays. now this? Can you pls point to a link to know more about this incident?
[Nexus 4 Original Android Development] veddandekar:
Idk if im the only one but occasionally my screen appears to tear .... Any help?

There no particular time or event for this thing to happen, it randomly tears...
[Nexus 4 Original Android Development] drdrewdown:
moar info would be necessary to help diagnose.
[Nexus 4 Original Android Development] veddandekar:
The tearing usually appears in the upper section of the screen and it sometimes appears to lag when some animation on playing/appearing on screen.

Latest BCM KERNEL(30 SEPT) AND VANIR ROM ( LATEST)

Anything else?
[Nexus 4 Original Android Development] severectify:
gamma control doesn't seem to be working. definitely turning screen on and off, but screen colors or gamma are not changing with fauxclock.
[Nexus 4 Original Android Development] nileshgr:
Vanir is JLS ROM and you should be using JSS kernel not JWR so that you don't get tearing
[Nexus 4 Original Android Development] senthilrameshjv:
Hi ByteCode,

I was using this Kernel sometime back and even recommending others to use it in ROM forums.This is the only kernel gave me almost flat curve during a night's sleep with all apps installed. I went to various other kernels and I did like only Linaro Franco finally. I used it for one day without any problem. Then I came here and saw all the appreciations. I thought there are lotta ppl to install Franco and support him but a rising dev like you needs support. I moved again back to this Kernel. I couldn't see Franco kernel going to deep sleep. It always stayed at min freq. It could be cos of the App which made the CPU awake all the time (Camera zoom fx) I am expecting deep sleep from this kernel and I am sure i'll get.

Thanks for the great kernel dev, and Im sure you've a great future. Your passion to develop and your support here will be the reason for it.
[Nexus 4 Original Android Development] BytecodeMe:
Just to make it clear I don't mind OT.

CM has decided to build CM for mako off of CAF display and audio drivers. When running with a kernel built from AOSP this causes major video problems, it breaks compatibility for all kernels out. They fragmented the only phone without fragmentation on purpose.
[Nexus 4 Original Android Development] nileshgr:
But vanir is not cm, in case you're referring to that one
[Nexus 4 Original Android Development] BytecodeMe:
Thank you :)
[Nexus 4 Original Android Development] v3n3:
Just switched from PAC to CM10.2 again, set everything up and installed your Kernel afterwards...

So... what are you planing to do ?
[Nexus 4 Original Android Development] snak3ater:
Flash this Fix if you want to get Colors back to normal in CM

color fix

Thanks to 'xxmonsterx' for this flashable zip file
[Nexus 4 Original Android Development] ak:
Can you share with another hosting, i cant download?

thanks a lot
[Nexus 4 Original Android Development] snak3ater:
There you go ..

colorfix_dropbox