yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] technojinn:
will do thank you.
[Nexus 4 Original Android Development] chrone:
dude, care to share your franco gamma/color profile for stock colors in 4.3?

i really love the darker tones on stock 4.3 colors. it makes my display now the same as the wallpaper in www.google.com/nexus/4, used to be so washed out like lack of contrast or saturation. :)
[Nexus 4 Original Android Development] street675:
Thanks for looking into this.

Verstuurd vanaf mijn Nexus 4 met Tapatalk 4
[Nexus 4 Original Android Development] maddyreddy:
r 182

I am on PA 3.99, there seems to be a problem with all the versions except milestones 4.2.2. My screen is distorting while scrolling be it facebook, web pages etc..can somebody help me out with this.. thank you.
[Nexus 4 Original Android Development] Alexandre83:
For PA 3.99 use JWR66V version.
[Nexus 4 Original Android Development] Drmol:
You're most likely not using the correct FK version. Download the one for JWR builds if you're on PA. :)

/ I'm too slow :( :D
[Nexus 4 Original Android Development] yoyoz808:
No jwr on r182
[Nexus 4 Original Android Development] vastac13:
USB DAC

Wow hoping our N4 get some love with these.... Almost all of USB DAC's are externally powered or run by batteries so no need for our N4 to supply power to the gadget.. Finally got to use my Fiio E17 if this will get merged...
[Nexus 4 Original Android Development] defffizz:
4.2.2 gamma = 4.3 gamma. It really should be put in OP, cause it appears people in here can't or won't acknowledge what franco and other devs said thousand times: gamma is the same.

CM 10.2 + franco
[Nexus 4 Original Android Development] Cantacid:
Nah I remember it had like 3% battery, and i plugged it in and then opened the keyboard on whatsapp...boom Restart! Out of the blue. Ive been seeing a lot reboots on r182 On Demand, default settings, no UV. Not sure if the kernel's at fault or CM Nightlies. I m not very concerned with reboots as much as i am concerned with randomly loosing network on the latest nightly. But i believe that may be the ROM at fault. Anyhow its all a step towards a stabler build.
[Nexus 4 Original Android Development] dzap:
I'm on stock 4.3, r182 OnDemand, default settings, no UV as well. It's not CM nightlies. Definitely something with franco. I've had random reboots happen for seemingly no reason ever since r182. This time, it just rebooted again after I sent a text message to a friend, so I'll pull the last_kmsg now and try to get it on here. Hopefully it can help franco squash whatever is causing this. Oddly though sometimes I'm getting I think (probably using the terminology wrong) the UI just crashing (I'll just be browsing or reading something on an app and the Nexus bootanimation appears, but not the Google one), and other times, like now, it's a full on reboot with the Google logo and the boot animation Nexus logo.

I am also using Chrome Beta...I will try switching to Chrome stable and see if issues resolve.
[Nexus 4 Original Android Development] drawde40599:
Yes but [MENTION=2116368]steviewevie[/MENTION] post http://xdaforums.com/showpost.php?p=45288276&postcount=45846 is dead on

---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------

After seening your post this a. M. I updated to latest cm build and stuck with there kernel all morning , the Freezing Deadlock still happening :-\
[Nexus 4 Original Android Development] jpde:
So, how do we get the 4.3 default colors then?
[Nexus 4 Original Android Development] dzap:
Here it is. last_kmsg log of most recent reboot (within the last hpour)?

http://pastebin.com/HAtjSVcw

Let me know if it helps. And if anyone sees what's the problem.
[Nexus 4 Original Android Development] drawde40599:
U cant get googles default colors unless u build the kernel yourself and remove what franco did 10 months ago (build 14). U can play with gamma control and get close tho. Its not really that much different, i think its better personally
[Nexus 4 Original Android Development] franciscofranco:
Sure, I'll take a looksie!

Don't count on that - thats a specific N10 patch only.

I concur there is something up with r182, I got a few problems the last 2 or 3 days that were not present while I tested r182. Thats going to be my focus for the rest of the night.
[Nexus 4 Original Android Development] dzap:
Thanks franco. :highfive: Good luck! I hope my kernel log will be of some use. You're the best. :good:
[Nexus 4 Original Android Development] eep2378:
I'm not having any issues with r182. It's actually quite nice. I used to get microstutters/lag on your(franco) 4.2 kernels. I thought my device just didn't like your kernels, but maybe not :)
[Nexus 4 Original Android Development] davidbar93:
Same here... r182 Works like charm :good:
[Nexus 4 Original Android Development] Testraindrop:
Yeah saw that later in the CM thread also, guess they need a few tweaks here and there to find the real culprit. :(
[Nexus 4 Original Android Development] blsrbl:
Just had a reboot while using torch. Here is last_kmsg attached.
[Nexus 4 Original Android Development] franciscofranco:
Rom derp.

No errors detected

Boot info:

Last boot reason: hw_reset
[Nexus 4 Original Android Development] drawde40599:
Yep, they did add /change alot of stuff in to there mako kernel the last few days looks like tho, looks like maybe they do believe its kernel related , its funny tho casue it happens to me less on francos kernel than cm or stock. coincidence maybe? Who no's
[Nexus 4 Original Android Development] zephiK:
It is in the kernel, PA uses a JWR kernel on a JSS build (fixed the artifacts.. hence hybrid) and theres no deadlocks.
[Nexus 4 Original Android Development] franciscofranco:
I think that its a combination of Kernel GPU driver commits (KGSL driver) and the HWcomposer (Rom side).
[Nexus 4 Original Android Development] franciscofranco:
Ok just fixed that bug that made cpu1 stuck on 1,5GHz while using interactive. Also reverted some patches that I merged for r182 and I'll test for 24h to see if ****'s better.
[Nexus 4 Original Android Development] franciscofranco:
https://plus.google.com/u/0/106873500108976028532/posts/5amPArspsb3
[Nexus 4 Original Android Development] arlenwoot:
Congrats man!
[Nexus 4 Original Android Development] defffizz:
My girlfriend thinks you're cute. She was tired of me flashing and tweaking your kernels all day long until today she looked at the laptop when I was checking out your posts on the g+. Now she's all like: when the new kernel is coming?? And I'm like: YOU DO NOT ASK ABOUT ETA's *****!! So, thanks, I guess

CM 10.2 + franco
[Nexus 4 Original Android Development] franciscofranco:
I approve this message!

Tell your GF I say hi :)
[Nexus 4 Original Android Development] PetritH:
Hope your GF doesn't read your xda posts bro =P
[Nexus 4 Original Android Development] mkfort:
I also get this running JWR66Y. Maybe can't be fixed with kernel but did not happen with 4.2.2. Perhaps I should test with stock kernel to see.
[Nexus 4 Original Android Development] svnhvn:
Just try it and so far so good.
[Nexus 4 Original Android Development] Luigiesin:
Hey Franco... Do you know if Minco has a 4.3 ROM yet? I've being thinking about going simpler... But don't want to go stock.. I rather a lean ROM like Minco which you support... Thanks buddy!

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] thuynh022:
[MENTION=3292224]franciscofranco[/MENTION] just had another reboot on 182.

Was using goo manager to download and update recovery.

http://pastebin.com/HHRwyBNL
[Nexus 4 Original Android Development] jmudrick:
Might want to try Cataclysm. Was looking for same and Cataclysm fits the bill for me. JWR rock solid.
[Nexus 4 Original Android Development] 00Droid00:
I've been using Purity rom. Really like it. Works great with this kernel. Has just enough features but not too much.
[Nexus 4 Original Android Development] saintsinner25:
sorry,please delete.wrong thread :| apologies.
[Nexus 4 Original Android Development] ihancioglu:
[MENTION=3292224]franciscofranco[/MENTION] There were random reboots with r182 on my device. So installed a purified kernel to check if it rom or kernel related. No more reboot for 48 hours. Also purified kernel has your latest patches but no reboots so far. Maybe will help you for identify that problem.
[Nexus 4 Original Android Development] ensboarder:
Nice but wrong thread
[Nexus 4 Original Android Development] saintsinner25:
Thanks! And yeah i was posting it in another thread but i didn't notice in my haste :| sorry.

Sent from my Nexus Lightsaber
[Nexus 4 Original Android Development] Dark Emotion:
Looks like latest kernel got some problems since you people got reboots etc. I have been using r176 for two weeks now and I haven't got a single issue. I even undervolted the cpu.
[Nexus 4 Original Android Development] zephiK:
r182 doesnt have any reboot problems. its because of user fault.
[Nexus 4 Original Android Development] Krayvon:
!

still can't boot up 182 on my n4, i feel so left out :(

just keeps showing up the boot up screen

i wiped cache and even tried it without wiping but still no go. i wonder what i'm doing wrong.
[Nexus 4 Original Android Development] Nocturnal86:
looks like there is a fku update! Wonder whats changed
[Nexus 4 Original Android Development] mylord92:
You don't have to need wipe cache or anything. Just flash right kernel. If you're using 4.2.2, you need to flash milestones on the top.

Nightlies version for 4.3 JSS, need to flash JSS (r182-JSS) tagged version. For JWR flash untagged version(r182)
[Nexus 4 Original Android Development] drawde40599:
Not really true i haven't had any issues with default settings jwr or jss. Running on Cm10.2 and . Img of 4.3

---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------

What rom?
[Nexus 4 Original Android Development] svnhvn:
Everything went smooth on your latest FKU [MENTION=3292224]franciscofranco[/MENTION].

Thanks man.
[Nexus 4 Original Android Development] drawde40599:
What rom?
[Nexus 4 Original Android Development] Krayvon:
cm nl.

had the wrong kernel flashing but got it fixed :) bootted
[Nexus 4 Original Android Development] AhmedFaiz:
how to get the default pa colours back tried trickster mod but cant find colour profiles there anymore! do we have to change the values one by one. can someone share the colour values to use with trickster to get the pa default colour back.

help thanks in advance.

Edit - changed it using fku.

n4|pa 3.99|franco r182
[Nexus 4 Original Android Development] nachordez:
I forgot to say: very nice file explorer in last FKU!

Good work Franco, improvements are fine!

Nexus 4 / Cataclysm / Franco / V4A
[Nexus 4 Original Android Development] ben_pyett:
hello also like the simplistic look and feel of the new file explorer.

Could you also enable it for folder selection within settings->downloads

Cheers
[Nexus 4 Original Android Development] drawde40599:
Oh NM then ;)
[Nexus 4 Original Android Development] Arstoien:
The file explorer looks great but it'd be nice to have a filter option, just so we don't have to go through many folders to navigate. Or bookmarks. But I don't know how that would fit your idea for simplicity.
[Nexus 4 Original Android Development] saintsinner25:
You can also use this http://xdaforums.com/showthread.php?p=45093038

Sent from my Nexus Lightsaber
[Nexus 4 Original Android Development] ihancioglu:
[MENTION=1978554]zephiK[/MENTION] are you sure about random reboots related users? Because i am at JWR stock without any modification and without supersu. No chrome beta, etc. R182 is causes random reboots on my device. Other releases and kernels does not that problem..
[Nexus 4 Original Android Development] Mantulis:
*

You deserve it!.
[Nexus 4 Original Android Development] CamoGeko:
+1

Best app and kernel combination!!
[Nexus 4 Original Android Development] soocold:
Only read about the last 100 post and didn't see any reference to this. But is their no deep sleep on r182?
[Nexus 4 Original Android Development] fozzie:
That'll be because there isn't a problem with it.

43.7% here since unplugging the phone this morning,
[Nexus 4 Original Android Development] rjunraj:
I was on previous nightly kernel and i could not transfer files between phone and computer via data cable then i did some setting in franko kernel app and it started working

Now i am on r182 and cm 10.2 and again facing the same problem

But i forgot what setting i did to solve the issue

Any help will be highly appriciated
[Nexus 4 Original Android Development] SpasilliumNexus:
Fast Charge. It would be wise to read the descriptions in the app instead of pushing random buttons.
[Nexus 4 Original Android Development] franciscofranco:
* Improved the look & feel of the File Explorer

* Added a Refresh option in the Kernel Updater tab that will query the server if you tap on it. Its useful when it gets stuck on "Fetching...". Works wonders

And other fixes for Galaxy Nexus users.

I think thats pretty much it. Now I need to fix some bugs, finish the functionality of the File Explorer (its still missing some important features to work just great with FKU options and Kernel operations).

Yes, thats a great idea.

Bookmarks is not a bad idea. I'll think of a good implementation that doesn't fúck up the simplicity that I'm aiming for.
[Nexus 4 Original Android Development] franciscofranco:
You'd be amazed by the amount of users that randomly select stuff and then email me complaining about problems they created in the first place.
[Nexus 4 Original Android Development] shubu000:
Quick report on 182, I was using the jss version with rasbean and I get no reboots, but random lockups. With purity and the jwr build. I get random reboots but no lockups. But sure it's it Rom related
[Nexus 4 Original Android Development] franciscofranco:
Lockup is the registred trademark of JSS roms.
[Nexus 4 Original Android Development] CamoGeko:
Lol!
[Nexus 4 Original Android Development] cobyman7035:
Plz make kernel compatible with fauxsound app

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 4 Original Android Development] mkfort:
Not true. You not having a problem doesn't mean there isn't one. r182 doesn't sleep for me properly after a while, and I did uninstall chrome beta. Hope it is fixed in next release.
[Nexus 4 Original Android Development] jak3z:
Please move along, nothing to see here.
[Nexus 4 Original Android Development] fozzie:
Indeed, but the fact that they said they looked and couldn't find anyone else talking about it, is probably a stronger indicator that there isn't one (and that there's a problem on the device).
[Nexus 4 Original Android Development] mkfort:
I'm not the person you originally replied to, and the issue has been mentioned many times.
[Nexus 4 Original Android Development] franciscofranco:
Deep sleep means that the device is idling, and for that to happen the device needs to not hold any wakelocl. In your case its definitely holding a lock from an app somewhere.
[Nexus 4 Original Android Development] fozzie:
True - as has the answer that it's much more likely to be an application issue stopping the device going in to deep sleep than the kernel...

As above ^.

(I typo'd my earlier post so corrected.)
[Nexus 4 Original Android Development] mkfort:
Well Franco, it never happened before with any other version using the same apps. I uninstalled Chrome Beta, which was the first thing you blamed, and that did not help. You should not be so quick to dismiss reports of problems by passing the blame.
[Nexus 4 Original Android Development] dapsANDpoundz:
Hey Franco not sure if you're still adding stuff for the app, but how about some new themes? Most of the themes use Holo Light with another color how about some Dark Holo themes like Black/Red or Black/Orange and then maybe some new light themes like White/Yellow or White/Purple. Your call.
[Nexus 4 Original Android Development] nachordez:
Plz use faux kernel

Nexus 4 / Cataclysm / Franco / V4A
[Nexus 4 Original Android Development] drawde40599:
hes not passing the blame hes telling u its not the kernel, both jss and jwr Deep sleep fine on my phones, just because it didn't happen before 182 dosent automatically make it 182 fault, sounds like u been chasing this issue? Whatever app u have controlling the kernel clear data for it and reboot if u haven't done yet, and make sure u dont have more than one app controlling the kernel. Good luck
[Nexus 4 Original Android Development] mkfort:
No, I only use FKU. The problem doesn't manifest directly after a reboot, only after a couple hours of use. Currently testing with r176. Nothing abnormal is listed in BBS partial wakelocks. Perhaps I could diagnose better with kernel wakelocks but Franco removed that functionality.
[Nexus 4 Original Android Development] Drmol:
The thing is it seems very unlikely that r182 would cause deep sleep problems only to some people, doesn't it? I mean if it was a kernel thing it would probably affect everyone or at least that's what seems logical to me and I'm not having any deep sleep problems whatsoever.
[Nexus 4 Original Android Development] drawde40599:
Ok well clear data for it, just because its Francos app dosent mean it cant take a dump somewhere and needs a fresh start, im not saying its the app but dosent hurt to try..... I don't no anything about bbs or any other those apps because they will just drive u crazychas ing **** thats not there, but install this https://play.google.com/store/apps/details?id=com.bvalosek.cpuspy open it hit reset shut off your screen go do something else for 10 min then come back.... If it shows deep sleep then leave your phone alone its working correctly
[Nexus 4 Original Android Development] mkfort:
I clear data on FKU before installing every kernel.
[Nexus 4 Original Android Development] dsbrohan:
Seems to me that you should be focusing on your partial wakelocks from apps and not the kernel. I have every known wakelocking app known to man and I still have good results using r182.
[Nexus 4 Original Android Development] drawde40599:
K, uninstall that bbs and try that cpy sp i linked u to , ive been using it for years, its the best app for testing deep sleep no foncy bull**** just simple
[Nexus 4 Original Android Development] fozzie:
I may have missed the comment you're referring to, but I think you'll find Chrome Beta was being discussed in relation to random reboots and not deep sleep; two totally different things.

---------- Post added at 04:25 PM ---------- Previous post was at 04:23 PM ----------

You don't need any other app for CPU states (if you're using f.Ku); they're right there in the built-in System Monitor.
[Nexus 4 Original Android Development] franciscofranco:
I'm not dismissing or blaming anyone - I simply stated what is the Deep Sleep state and what prevents the device to enter it. It can also be a numerous other things, but 99% of the Deep Sleep problems is caused by an app wakelocking. It could also be the Google Services which have been causing **** for a while. I also re-enabled the Wakelock Kernel stats again on my local build, I'm growing tired of users asking me to add it back.

More themes are planned, but not for this next version :)
[Nexus 4 Original Android Development] mkfort:
Well, I know what wakelocks are and I think this is the 1%. It seems to happen after a bit of use, not directly after reboot. I just mention that because I know you reboot more than the average user when doing your testing. Device will stick at 384mhz with screen off and not deep sleep. I know you made some reverts in the next version so I look forward to testing that. I tested r182 with both governors and got the same issue. For now I'm happy with r176.
[Nexus 4 Original Android Development] whitedragonz83:
Mkfort,

Are you noticing it shortly after charging your phone?

I.E., unplug phone, continue about your day, notice it is not deep sleeping.
[Nexus 4 Original Android Development] fozzie:
It would help if you provided more information so that other people can try and reproduce the issue e.g. do A, B, C and then X, Y, Z happens, otherwise you're pi$$ing in the wind...
[Nexus 4 Original Android Development] mkfort:
No. I'm using the stock charger (not QI, know that is known issue), and have not noticed any correlation with charging.

---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------

I've provided tons of information. I use my phone, which is factory JWR66Y rom, factory .84 radio, and at some point the deep sleep state timer will not move. It's usually between 30-60 minutes of deepsleep, then it will be stuck on 384mhz with screen off. I have not noticed any correlation with app usage, and the wakelock is not reported under partial wakelocks.
[Nexus 4 Original Android Development] BrandoHD:
[MENTION=5179357]mkfort[/MENTION] it's not the kernel I assure you, is your Android OS usage high?

Here's what in did, I flashed stock kernel, installed Better Battery stats so that I would be able to see partial wakelocks and kernel wakelocks, after some time, I realized that the problem was suspend_backoff (kernel wakelock) was keeping my phone awake.

This time the suspend_backoff was not related to Chrome, after a lot of research, I changed a few things with regards to WiFi, and it stopped, my phone was sleeping well again, now I am back on Franco kernel

Now this may not be your issue, but you need to put your phone back to a stockish state and use the necessary tools to Troubleshoot the issue.

In case you're wondering, I changed my WiFi IP settings to a static address and I placed a checkmark next to WiFi optimization, don't know which one fixed it, but the suspend_backoff wakelock disappeared completely

Sent from my Nexus 7
[Nexus 4 Original Android Development] fozzie:
You need to look at what you've got installed, what syncing etc Maybe start by disabling Google sync (for all the services) to see if that makes a difference.

What app(s) are you using to manage the kernel?

What app(s) are you using to look at the wakelocks? BBS, WLD, Dr Power?

I'm on stock rom/radio/r182 and right now have 22% @ 384MHz, 11% @ 702MHz, 3% @ 1.5GHz and 64% (5h11m) Deep sleep.

Good luck on finding the rogue app(s).
[Nexus 4 Original Android Development] s1m4an:
Had a hard reboot, seems like it's kernel panic?

http://pastebin.com/xMrtupax

Using r182 on PA 3.99a3
[Nexus 4 Original Android Development] mkfort:
Does it with Wifi On or Wifi Off (HSPA+). With Wifi optimization on and off. I've tried to eliminate as many variables as possible.
[Nexus 4 Original Android Development] BrandoHD:
Flash stock kernel and use the BBS, you are not using all tools available to you!

Sent from my Nexus 7
[Nexus 4 Original Android Development] fozzie:
Sound advice.

I've seen a few comments elsewhere relating to WiFi being a cause (but I don't recall if was when changing the OS settings e.g. WiFi optimisation, or making changes to the modem driver config in http://xdaforums.com/showthread.php?t=2072930).
[Nexus 4 Original Android Development] mkfort:
Turning google sync off is not useful to me. I use FKU and BBS. I'll continue to test with r176 to make sure it's not an app update, but I've never had trouble before r182.

---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------

According to Franco he will enable kernel wakelock reporting in next version. Very kind of him.
[Nexus 4 Original Android Development] fozzie:
Will there be a new thread "kernel wakelock discussions here" ? ;)
[Nexus 4 Original Android Development] giovaorama:
Uhm... Do I misunderstand or you (and the other user) mean that fast charge has influence on data connection to the pc and this is well stated in the setting description?

Because in the italian description this is not true.

I think is better that i double check the translations on crowdin.

I really like to be able to set for some app (fku and titanium for instance) their original language instead of relay on approximate translations

EDIT: I check the translations and it seems correct. Then i really misunderstood.

Inviato dal mio Nexus 4 con Tapatalk 4