yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] _artem_:
Hehe not new but I've never touched volting and frequency, used the default settings and was quiet happy with those, but r201 is kinda more battery hungry. I noticed it when connecting phone for charge every (late) night. Before r201 I had about 30-15% (depending on which time I go to sleep) when I go to bed... with r201 with the same settings and with the same usage I have about 10-4%. I can't watch YouTube and read some stuff without connecting the charger. Before r201 I could without issues watch or read over couple of hours, now I have to connect it immediately when I go to bed. But with undervolting it's better now (just noticed it today), I just regret that I haven't played with those settings before :)
[Nexus 4 Original Android Development] shakatu:
Okay today got a call and it lit up almost the same time the ringtone played. Anyway, I guess the delay people were referring to was a SIGNIFICANT delay that makes it hard to even answer the call... Haven't had that ever with the N4. Just sometimes can't get it out of my pocket in time but that's not a kernel issue! Lol
[Nexus 4 Original Android Development] ken_alpha24:
Can I overclock this kernel?
[Nexus 4 Original Android Development] soumoks:
No
[Nexus 4 Original Android Development] ken_alpha24:
Lol that explains why. Thanks
[Nexus 4 Original Android Development] foxguard:
Its long, I had my phone in my hand and got a call, the screen took about 3-4 secs before it came on so I couldn't answer it let alone know who was calling. So every one is happy its not a kernal issue?

Is it a ROM issue then?
[Nexus 4 Original Android Development] Bill Gamble:
I can't speak for everyone, but I've never experienced it with Cataclysm and f.K.
[Nexus 4 Original Android Development] Nicolae-Daniel:
Can I flash F.K. if I run ART?
[Nexus 4 Original Android Development] karthi89:
Yes
[Nexus 4 Original Android Development] reikar:
Same setup, but I experience it.
[Nexus 4 Original Android Development] jaison thomas:
For your info matrix kernel doesnt has that delay. I too was a franko user till 198. But my old galaxy y doesnt suffers such a screen on delay when a call comes
[Nexus 4 Original Android Development] arpitnathany:
Maybe its network related. One of you might be on 3g while other might be on 2g. I dunno I'm just throwing ideas out there. Try switching 3g off.
[Nexus 4 Original Android Development] TheDarkDefender:
Running cm11 on your galaxy y I presume?

Sent from my Nexus 4
[Nexus 4 Original Android Development] jaison thomas:
For your quick information galaxy y never had a stable cm9 with at least gsm conectivity.
[Nexus 4 Original Android Development] svnhvn:
Neither with Purity.

Starring: Mako

Also starring: Purity, r201, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] foxguard:
Nope, makes no difference. So frustrating!
[Nexus 4 Original Android Development] svnhvn:
FC when applying colour profile on latest FKU update.

Starring: Mako

Also starring: Purity, r201, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] hughfollett:
Download Display Control from xda, it works fine.
[Nexus 4 Original Android Development] ken_alpha24:
Any recommendations on what app to use for Kernel Tweaking?
[Nexus 4 Original Android Development] fozzie:
https://play.google.com/store/apps/details?id=com.franco.kernel of course!
[Nexus 4 Original Android Development] Rohit02:
FKU or Trickster free app or Fauxdisplay app(Paid version). :good:
[Nexus 4 Original Android Development] ken_alpha24:
Well looks good cause I'm using trickster
[Nexus 4 Original Android Development] Puneet Singh Chauhan:
Same here, but on latest beta update. Tried clearing the FKU data a couple of time, it didn't help so I reverted to stable version and now all is good as before.
[Nexus 4 Original Android Development] Arstoien:
It's because of CPU thermal throttling. Increase its value for good scores and crack an egg on the back of the phone.
[Nexus 4 Original Android Development] RockBoyEmy:
Impossibile to load any kind of color profile of the last update of fku. App crashes every time.. :/

---------- Post added at 10:38 PM ---------- Previous post was at 10:31 PM ----------

I am pretty sure that the temperature didn't even reach the throttle limit when the test benchmark ended :/
[Nexus 4 Original Android Development] deltatux:
Clear app and try again

deltatux
[Nexus 4 Original Android Development] deltatux:
Uninstall and reinstall it then. fku works perfectly here.

deltatux
[Nexus 4 Original Android Development] _artem_:
Confirm latest beta crashes when applying color profile.

Btw I like the new on boot icons! No more Google play's wishlist icon
[Nexus 4 Original Android Development] RockBoyEmy:
And what's with the newly added google play games sync? I keep getting an error
[Nexus 4 Original Android Development] RockBoyEmy:
Funny thing is that now I realize that it actually applies the color profile after screen off, but it just keeps crashing.
[Nexus 4 Original Android Development] deltatux:
Try deleting /sdcard/franco.kernel_updater/ folder, uninstall the fku app and then reinstall it.

deltatux
[Nexus 4 Original Android Development] gtanner00:
I just had Franco update to the latest beta version and also found that color profiles crash when you select them.
[Nexus 4 Original Android Development] jimbohurt:
Same!
[Nexus 4 Original Android Development] karthi89:
Maybe that beta is exclusively for n5 :-|

Started feeling jealous of n5 users ;)
[Nexus 4 Original Android Development] franciscofranco:
Hey guys, sorry for a small absence. I had a food poison last week and then took a couple days after that to catch up on my stuff, thus the lack of updates since then, so here's r202 that I've been cooking since 5th of January, has a couple of important fixes, so hope you like it:

* Update the workqueue subsystem to improve hotplug latency

* Improvement in the Hotplug driver suspend/resume mechanics, now using the standard platform device subsystem to deal with suspend and resumes. Should remove the call income screen on lag

* Merged a patch to make deadline deal faster with read IO and make it default

* Merged a patch that improves TCP download/upload speed

* Fix a bug where the cores would stay online if the min freq was > a certain threshold

* Fix a bug in the touchboost implementation where the device could reboot due to a race condition

Happy flashings!
[Nexus 4 Original Android Development] gtanner00:
Thank you so much. Glad you are feeling better after taking time off and also thinking of us "flashers" to :)
[Nexus 4 Original Android Development] deltatux:
Glad you're back, hope you are feeling much better man. Can't wait to flash r202!

Oh and I was wondering, would we see these Nexus 5 improvements in the next revision?

Cheers,

deltatux
[Nexus 4 Original Android Development] franciscofranco:
The first one I believe its fixed on r202 and the second I forgot!
[Nexus 4 Original Android Development] deltatux:
Oh goodie, hopefully it'll help with my audio situation. You forgot the second one as in forgot to merge it in r202 or forgot if you did it or not?

Hopefully it's in r202, if not, hopefully it'll be in r203 :)

Also, I noticed with r202, the Hotplug Control is missing two parameters, like the suspend frequency and cores online with screen on. Is this normal or is fku broken on my end with r202?

Cheers,

deltatux
[Nexus 4 Original Android Development] randras83:
Same here.

Tapatalk-kal küldve az én Nexus 4-el
[Nexus 4 Original Android Development] fajarlazuarding:
Confirmed here.
[Nexus 4 Original Android Development] Mercado_Negro:
Those two lines in the changelog make me think these two parameters we're missing aren't needed anymore.
[Nexus 4 Original Android Development] albundy2010:
Can anybody confirm that 202 is entering deep sleep normally for me?

I flashed it and let it boot and idle to the screen went off and it didn't enter deep sleep. Flashed back ti 201 and did the same and after competed boot it did enter deep sleep as expected.

Same rom / same set up. Only difference was kernel. Please let me know if it's working normally on your device.
[Nexus 4 Original Android Development] spicediablo:
Same here. Mine is not sleeping after 202

Sent from mako⁴
[Nexus 4 Original Android Development] attaint:
Yep, r202 definitely not sleeping for me either.
[Nexus 4 Original Android Development] Togno85:
No deep sleep for me... :(

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] RealSlimShadyMC:
deep sleep busted for me on r202
[Nexus 4 Original Android Development] Kimbaroth:
Same goes for me :(
[Nexus 4 Original Android Development] spicediablo:
Let's give him some time, he might fix it on the next release. Meanwhile if it's too consuming perhaps revert back to r201 first

Sent from mako⁴
[Nexus 4 Original Android Development] :
well, seeing so many people are having problems I guess I'll skip 202 for now.
[Nexus 4 Original Android Development] underskyzx:
No deep sleep here too, attached some logs hope it helps

https://www.dropbox.com/sh/v09zri1ldw0looq/loo4x91R__
[Nexus 4 Original Android Development] Ümit:
I reported deep sleep problem on r200 and r201. apparently that is not solved?

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 4 Original Android Development] :
Same here, zero deep sleep in r202. But for some reasons, exchange services draining my battery seems gone. I know it's not related, just saying.
[Nexus 4 Original Android Development] underskyzx:
r201 was working perfectly here
[Nexus 4 Original Android Development] abalam:
+1

Sent from my Nexus⁴ machine
[Nexus 4 Original Android Development] Jai3:
Zero Deep Sleep in r202

Same issue..!! Zero Deep Sleep in r202...!!:(

I reverted back to r201..!! And, now Nexus is sleeping..!! :)

Hope it will get fixed soon..!!! Till then I am on r201:cool:

Anyone facing the same issue....??:confused:

But, Franco Rocks...!!:good::good::D
[Nexus 4 Original Android Development] :
I restarted my phone several times, and terminated some apps and processes, then waited for several minutes to check whether my phone will enter into deep sleep, but still not. I'm on trickster mod, does FKU app shows the same? This could be just wrong reading because franco changed some parameters.

Google Nexus | Android 4.4.2
[Nexus 4 Original Android Development] Jai3:
[MENTION=5060406]xdarenzzio[/MENTION]

I don't think its wrong reading..coz i can see the '0' Deep-Sleep time and 384Mhz frequency time is increased constantly.

Also, i checked the Franco App there also i can only see 384Mhz freq taking maximum time.
[Nexus 4 Original Android Development] albundy2010:
You just said you have the same issue. Then followed that with anybody having the same issue?

Come on everybody! We already reported the issue, many users confirmed they see the same behavior.

Just let it be. We don't need 5 pages of being confirmed over and over again.
[Nexus 4 Original Android Development] :
Any problem? We are here to discuss and explore. At least on our humble end, we're trying to know what might be the problem. This is a forum. That's self explanatory.

Google Nexus | Android 4.4.2
[Nexus 4 Original Android Development] Ümit:
sinds how many hours is your phone open (without restart)?

The problem starts from 90 hours.

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 4 Original Android Development] svnhvn:
I can confirm that r201 works just fine for whole damn week.

Starring: Mako

Also starring: Purity, ART, hells-Core, TWRP, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] 777.300:
Confirmed r202 and has no deep sleep on PA 4.0 beta 3.

R201 working fine.

Sent from my Nexus 4 with Tapatalk 4
[Nexus 4 Original Android Development] cAase:
Using 201 and my device sleeps beautifully

Skickat från min Nexus 4 via Tapatalk
[Nexus 4 Original Android Development] BigDig:
+1 stock no deep sleep with r202
[Nexus 4 Original Android Development] perrocaliente:
Darn I was just starting to like 202 too :( no deep sleep whatsoever. I checked my wake locks too and it isn't that.
[Nexus 4 Original Android Development] ZULU2189:
Deep sleep works just fine on 200 and 201. That's definitely on your end. 202 is a different story.

---------- Post added at 05:34 AM ---------- Previous post was at 05:20 AM ----------

Thank you Franco, aside from the no deep sleep; 202 is fantastic!!

---------- Post added at 05:35 AM ---------- Previous post was at 05:34 AM ----------

Thank you Franco, aside from the no deep sleep; 202 is fantastic!!
[Nexus 4 Original Android Development] ieatacid:
Could the deep sleep issue on r202 have something to do with "suspend_backoff" kernel wakelock? The time that is active seems to coincide with the time my phone should otherwise be sleeping.
[Nexus 4 Original Android Development] SpasilliumNexus:
Really guys? How many more posts are we going to get of the same report?
[Nexus 4 Original Android Development] manulemaboul:
Doesn't seems to drain much for a non sleeping state tho.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Original Android Development] Penacal:
Couldn t make or receive calls after update to 202 nightly(full signal):confused:.Back to 201 and back to normal.Anyone else experiencing this??
[Nexus 4 Original Android Development] dapsANDpoundz:
37. Yup, 37 sounds about right.
[Nexus 4 Original Android Development] sordna:
Come on, I lost 23% overnight (compared to my typical 2%) and I was in airplane mode.
[Nexus 4 Original Android Development] deltatux:
Audio seems to be fixed in r202 which I'm very happy about, but the battery drain gotten worse in r202 compared to r201. Dropped to 79% with only 2 hrs off charger, I have my screen off most of the time and mobile data is off, so this doesn't make sense for this kind of drainage. Never happened with r201. Not sure what changed that caused this to happen.

Yup, I notice a pretty big drain, not as bad as your drain, but not that good of a drain compared to normal...

Yup, no deep sleep, it only goes to 384 MHz instead of deep sleep, that's quite concerning. Might be forced back to r201 if not fixed soon. I love the no audio stutter that r202 brings, but battery life is more important...

deltatux
[Nexus 4 Original Android Development] bertans:
My Nexus 4: stock Android 4.4.2, CWM recovery, su and Xposed.

With r202 proximity sensor doesn't work... during a call, if I put the phone near my ear the screen doesn't go off.

Thank you for your work Francisco! :cool:
[Nexus 4 Original Android Development] deltatux:
Looks like r202 has a few power and screen related bugs. Could it relate to the touch boost driver patches he merged into r202? Hopefully Franco can fix this soon :).

Cheers,

deltatux
[Nexus 4 Original Android Development] jimbohurt:
Does anyone have an apk for an older FKU? I can't live without colors :(

Edit: oh yeah, it's a paid app, I forgot. Definitely don't post it.

I hope it gets fixed soon.

I cleared all app data uninstalled rebooted, the whole nine, and still the colors tab force closes when you pick a profile. I'm on the beta program.
[Nexus 4 Original Android Development] thebest:
Suit yourself ;)
[Nexus 4 Original Android Development] nbeebe24:
Have you tried that mod? I have and it made my phone completely unresponsive to touch and broke cwm touch as well. Its not that great
[Nexus 4 Original Android Development] 0.0:
Well cwm touch unresponsive was stated, but being unresponsive to touch while using the phone is definitely something I haven't really read. Good thing its not implemented. Besides, older codes can only help for so long. Things should be focused on the future, and how to make things better imo

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Build 8 is compatible with CM and I also changed some constants to see if it fixes the msm_hci something wakelock reported a few times. Let me know how it goes!
[Nexus 4 Original Android Development] illuzi0n:
op still showing beta 7 link, i believe the correct link is

http://minooch.com/franciscofranco/Nexus4/boot-8.img

btw thanks franciscofranco for your hard work
[Nexus 4 Original Android Development] franciscofranco:
Fixed thanks!
[Nexus 4 Original Android Development] albundy2010:
Speaking of thermal stuff. A couple of days ago Brian from anandtech said he spoke to Qualcomm and they are looking into the thermal issues. They believe it is a overly aggressive governor and so does Brian. Also stated that Qualcomm says it should not be throttling.

Source is Brian Klug's twitter @nerdtalker.
[Nexus 4 Original Android Development] Mahdi786:
Hi, is build 8 still compatible with aosp or just cm?
[Nexus 4 Original Android Development] ssauger:
To get default vibrator value back, i have to edit or delete this file?

And i am on CM10.1, runs great, Thanks!

Edit: I think the value for default is 70, caus after i updated to last nightly with stock CM kernel this was set.
[Nexus 4 Original Android Development] visceralpsyche:
Just flashed it to CM10.1 Dec 4th build and it's working fine :) Feels smoother than stock CM kernel. Great work! Looking forward to having your app compatible with the Nexus 4, whenever it's ready :) Cheers!
[Nexus 4 Original Android Development] inh:
Would it be possible to get the first post updated with this kernel features and a changelog, please :)
[Nexus 4 Original Android Development] leets4uc3:
I set mine to 80 and i like it a lot.
[Nexus 4 Original Android Development] ssCISengineer:
Hey franco....ill buy you a note 2....
[Nexus 4 Original Android Development] Perilla_:
Is ALSO compatible with cm (means still compatible with aosp)

Btw, can somebody report about msm_hic_host?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] SleemLDJ:
I learnt that to flash a kernel we have to wipe cache and dalvik cache.

But this is a boot.img through flashed bootloader.

How do i go about it? Just fastboot flash boot?

Thanks.
[Nexus 4 Original Android Development] resynx:
Yup, that's all you have to do.
[Nexus 4 Original Android Development] lnfound:
If you do the zip, twrp is fine. Similar to boot, unresponsive for 10seconds,no big deal.

I also disagree on the later comment of using old code being some issue, I mean it's a fix to 1 particular area its not exactly a trade off for anything unless you reboot hourly and the 10s of un responsiveness is an issue.
[Nexus 4 Original Android Development] baristaman28:
could anyone make a zip file for this, or direct me how to do it myself?
[Nexus 4 Original Android Development] ragnarokx:
You should take the advice in your sig - just pretend "Fastboot" comes Venti sized ;)
[Nexus 4 Original Android Development] baristaman28:
well where should i partition the file to?

EDIT: Never mind, i found my mistake....
[Nexus 4 Original Android Development] jundii:
Exactly. Too many variables. You got people flashing back to stock that fixes it and got people that flash back to stock and it doesn't. Some issues are kernel related. Some could be carrier related. Some could be both. Some could be degrading hardware if that is even a valid variable at this point. Phones have been out for a bit.. Getting used.. And all of a sudden a select few have hardware issues and the radio starts to get Botchy. Who knows.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Vangelis13:
Latest rasbean +r28, flawless combination.
[Nexus 4 Original Android Development] undercover:
I would not consider hw since Gnex is getting that too. It's just too random. I'm looking into it to the best of my (lack of) knowledge.

Sent from my fridge. Make:LG Model:N4
[Nexus 4 Original Android Development] Chochiwpg:
Flawless with MiNCO as well. I think I will give rasbean a try again, nice ROM.
[Nexus 4 Original Android Development] jmejiaa:
Finally started getting some data drops on r28, from blue to grey.. It comes back after a bit..
[Nexus 4 Original Android Development] benrees21:
Why was my post deleted? I was trying to help!

A Nexus b!tch called Ben (Work that one out :P) AOSPA!! Franco Kernel!!
[Nexus 4 Original Android Development] nellisere:
20 minutes after flashing r28 I have a data drop, the bats stay blue but no data is received, aeroplane mode fixes it.
[Nexus 4 Original Android Development] krook6023:
Thread cleaned, I would remind everyone to stay on topic and make sure that bug reports contain enough information to help development.

krook6023 (mod team)
[Nexus 4 Original Android Development] calanizzle:
R28, no data problems yet.
[Nexus 4 Original Android Development] Net.silb:
Maybe a "Franco Kernel Discussion Thread" should be created in the General section for discussion regarding the Kernel, making this thread for development purposes only. If you approve of this, I am willing to open the thread myself and maintain it.
[Nexus 4 Original Android Development] derPianist:
No !
[Nexus 4 Original Android Development] undercover:
It will quite happily fit into ot thread. Any real bugs can be reported here.

Sent from my fridge. Make:LG Model:N4
[Nexus 4 Original Android Development] hallucynogenyc:
Happened again. Suddenly the phone acts as there's no SIM, I have to reflash the kernel to repair it. Didnt happen with r23.
[Nexus 4 Original Android Development] franciscofranco:
Nope:

One Thread to rule them all,

One Thread to find them,

One Thread to bring them all

And in the darkness bind them.
[Nexus 4 Original Android Development] pitjago74:
That's right Fran:D

Great job...r28 perfect at the moment.. Since yesterday:cool:

www.teregalounpoema.com
[Nexus 4 Original Android Development] Nebucatnetzer:
Could this be the data drop problem?

W/GoogleAnalyticsTracker( 6651): Problem with socket or streams.

W/GoogleAnalyticsTracker( 6651): java.net.ConnectException: failed to connect to www.google-analytics.com/127.0.0.1 (port 80): connect failed: ECONNREFUSED (Connection refused)

W/GoogleAnalyticsTracker( 6651):	at libcore.io.IoBridge.connect(IoBridge.java:114)

W/GoogleAnalyticsTracker( 6651):	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)

W/GoogleAnalyticsTracker( 6651):	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)

W/GoogleAnalyticsTracker( 6651):	at java.net.Socket.connect(Socket.java:842)

W/GoogleAnalyticsTracker( 6651):	at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)

W/GoogleAnalyticsTracker( 6651):	at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)

W/GoogleAnalyticsTracker( 6651):	at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)

W/GoogleAnalyticsTracker( 6651):	at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingHits(Unknown Source)

W/GoogleAnalyticsTracker( 6651):	at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)

W/GoogleAnalyticsTracker( 6651):	at android.os.Handler.handleCallback(Handler.java:725)

W/GoogleAnalyticsTracker( 6651):	at android.os.Handler.dispatchMessage(Handler.java:92)

W/GoogleAnalyticsTracker( 6651):	at android.os.Looper.loop(Looper.java:137)

W/GoogleAnalyticsTracker( 6651):	at android.os.HandlerThread.run(HandlerThread.java:60)

W/GoogleAnalyticsTracker( 6651): Caused by: libcore.io.ErrnoException: connect failed: ECONNREFUSED (Connection refused)

W/GoogleAnalyticsTracker( 6651):	at libcore.io.Posix.connect(Native Method)

W/GoogleAnalyticsTracker( 6651):	at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:85)

W/GoogleAnalyticsTracker( 6651):	at libcore.io.IoBridge.connectErrno(IoBridge.java:127)

W/GoogleAnalyticsTracker( 6651):	at libcore.io.IoBridge.connect(IoBridge.java:112)

W/GoogleAnalyticsTracker( 6651):	... 12 more

Because I'm getting quite a lot of them. Haven't seen them before AFAIK.
[Nexus 4 Original Android Development] franciscofranco:
Thats just a connection error to the Google Analytics.
[Nexus 4 Original Android Development] undercover:
When problem occurs run

logcat -b radio

In terminal.

Sent from my fridge. Make:LG Model:N4