yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] drawde40599:
This is someone's elses colors(can't remember who) tweaked a lil but if u liked stock like i did our eyes may be similar if u wanna try

R, G, B, 255

Mids, Blacks, 119

Whites, 7

Contrast. 11

Brightness 0

Saturation 6

I run at 70 % brightness.
[Nexus 4 Original Android Development] Tarun95:
Feels like amoled Lol. Anyways thanks :)
[Nexus 4 Original Android Development] rolear8:
Damn. I lose root after flashing 176 JWR franco.. Do you know how to fix? I was using faux kernel.

Tried already to root again with the nexus 4 toolkit but failed.
[Nexus 4 Original Android Development] nileshgr:
The signal issue seems to be more of Nexus 4's inability to pick up extremely weak signals than a software bug. Because flashing .54 radio didn't do much good either. :'(
[Nexus 4 Original Android Development] kypeth:
I know that, but his app is still using the old scale to signify which chip we have, I do not have a "Fast" chip, my chip gives me a return of

dmesg | grep PVS #1

1 being Slow on the new scale, but previously having been "Fast" on the old scale.

I am aware that a software update has not performed magic and changed the binning of my chip, thank you much for having me point that out, my good sir.
[Nexus 4 Original Android Development] limeaide:
reflash superuser.
[Nexus 4 Original Android Development] Redneck Trash:
I realize I pointed out the obvious but some people (and I'm not saying you) get worked up over this.
[Nexus 4 Original Android Development] zorginho:
u already tried this?

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] nachordez:
I would better recommend to flash SuperSu 1.51

It's the only root by now not giving any problem...

Nexus⁴ / Cataclysm / Franco / Viper4Android

GT-p5110 / Carbón / DhollmenCM / Vper4Android
[Nexus 4 Original Android Development] Redneck Trash:
SuperSU > Superuser
[Nexus 4 Original Android Development] Pure Drive GT:
I would not recommend relying on all these toolkits and automated processes. Just flash like already advised the latest chainfire supersu to get root back. If you use these automated processes to often you don't really know what you're doing and if something goes wrong you won't know what may have went wrong :)
[Nexus 4 Original Android Development] Bobtehblob:
The s4 pro was never meant to be used with a gsm radio. It's literally just botched on basically. This is why we've always had to deal with sub par sign strength, wake locks etc... :( Hopefully the nexus 5 or whatever it's called is based on the 800 and had a much more efficient integrated radio!

Sent from my Nexus 4
[Nexus 4 Original Android Development] albundy2010:
No. Just no.
[Nexus 4 Original Android Development] Bobtehblob:
If you believe what I have said is incorrect. Please explain why that is so. Simply saying no, doesn't educate me or anyone else reading this...

Sent from my Nexus 4
[Nexus 4 Original Android Development] albundy2010:
Sorry dude I don't mean to rude. But its not my duty or anybody else's either, to debunk some pure nonsense you made up.

You can go look back and follow all the releases since the s4 was on Qualcomm's road map. Anand is a great place to get all the tech info you want

But think about it for a second, you're saying that one of the biggest players in the mobile /radio space designed its flagship platform for 2012 to not work right on the most popular cell network in the entire world.

.
[Nexus 4 Original Android Development] hellsgod:
The S4 Pro is a Tablet Chip. Why do you think the modem is connected by the USB Host Controller and not integrated in the Chip itself? Right, because it is a Tablet Chip. You can find this answer in many Kernel Threads. Search for it ;)

hells
[Nexus 4 Original Android Development] GForceXIII:
I think they separated the modem from the soc so manufacturers could choose any modem they want for the device?

I am not really sure myself.

But I don't think the S4 pro was not meant to be used in a phone.
[Nexus 4 Original Android Development] Bobtehblob:
All good my friend :) I probably shouldn't have said gsm radio, just any form of mobile network radio in general. As the two posts below yours say it was never intended to be used in a phone with a 3g radio. At least that's my understanding anyway!
[Nexus 4 Original Android Development] jak3z:
This was on the press release about the S4 Pro that uses the Nexus 4:

It was designed like this on purpose, so it was designed as a PHONE chip, to help reduce cost for OEMs, that's why for the Nexus 7 2013, they used a Snapdragon 600 downclocked to 1.5 Ghz and called it S4 Pro as well, but maintaining all the 600 Series characteristics.
[Nexus 4 Original Android Development] GForceXIII:
Nope.

What I meant was, It is a phone chip.

Sorry for the double negatives.
[Nexus 4 Original Android Development] steviewevie:
Another kernel panic on r178, this is my fourth one now since upgrading my stock ROM to 4.3.

http://pastebin.com/raw.php?i=7CTsq9as

Extract :

[35720.155434] Unable to handle kernel paging request at virtual address 001000f0
[35720.155526] pgd = eec84000
[35720.155678] [001000f0] *pgd=00000000
[35720.155831] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[Nexus 4 Original Android Development] Marcb:
Is that true?

I have a 304B Nexus... So it's actually a Snapdragon 600?

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] Pure Drive GT:
Random reboot

Random reboot with stock rom JWR66Y and r178 second time for me: pasite.org does not allow higher than 64kb how do you guys post your last_ksmg with it ???

last_ksmg attached as .txt
[Nexus 4 Original Android Development] jak3z:
I don't know what's a 304B Nexus, but yes it's true that the Nexus 7 2013 uses a downclocked version of a Snapdragon 600.

---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------

Looks like your charger was going over the max current the phone should handle for quite a bit of time. Maybe system malfunctioned because that.

[35703.247575] adjust_soc: ibat_ua = 44100, vbat_uv = 3954411, soc = 64, batt_temp=507
[35705.199872] batt_temp_monitor_work: decrease current!! state = 3 temp = 505 mvolt = 3931
[35705.200025] batt_temp_set_current_limit: value = 400
[35715.199841] batt_temp_monitor_work: decrease current!! state = 3 temp = 506 mvolt = 3932
[35715.199933] batt_temp_set_current_limit: value = 400
[35720.155434] Unable to handle kernel paging request at virtual address 001000f0
[Nexus 4 Original Android Development] steviewevie:
Interesting, thanks. But looking at that again I wonder if it was overheating? It was on charge and running Ingress (GPS, graphics). Having said that, it shouldn't be panicing though.
[Nexus 4 Original Android Development] Marcb:
304 is the serial number... Produced in April/2013.

You wrote Nexus 4, not Nexus 7...
[Nexus 4 Original Android Development] jak3z:
Well there's no nexus 4 2013 so yeah my bad anyways
[Nexus 4 Original Android Development] Marcb:
oh, ok then! :p
[Nexus 4 Original Android Development] jak3z:
It was a bit hot but I don't see any reason for the temperature to trigger a kernel panic it was at 51 °C
[Nexus 4 Original Android Development] sean222:
For whatever it's worth, UI and a couple games were a bit laggy with r180 test kernel. I definitely enjoyed interactive on r178 more. Battery was about the same. Back on r178 for now. Not having any kernel panics or problems :)
[Nexus 4 Original Android Development] Bobtehblob:
This sums it up the best! Whether it was supposed to be in a phone or not, the radio/modem doesn't perform as well as it really should!

Sent from my Nexus 4
[Nexus 4 Original Android Development] jak3z:
I must be the only one without complains about the modem/radio of the phone.
[Nexus 4 Original Android Development] blueren:
That may be the case, however I've noticed touch to be more smoother with r180. What do you think?
[Nexus 4 Original Android Development] Husy:
Running Stock 4.3 latest version with r178 running good. Battery life is normal and no kernel stresses or anything.
[Nexus 4 Original Android Development] Pure Drive GT:
Well to be honest I also don't have an issue with the radio, but that is because I don't use the GSM network to often (I'm not on a contract ;) ), I see it dropping now and then, but you can never really be sure of the reason. I think depending on your location and service provider you are going to feel the issues more prominently.
[Nexus 4 Original Android Development] nachordez:
I think so!

Nexus⁴ / Cataclysm / Franco / Viper4Android

GT-p5110 / Carbón / DhollmenCM / Vper4Android
[Nexus 4 Original Android Development] jak3z:
I bet it's the weather over here in Spain / Galicia. :victory:
[Nexus 4 Original Android Development] steviewevie:
Another relevant extract seems to be as follows :

[35720.155831] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[35720.155923] Modules linked in:
[35720.156136] CPU: 1 Tainted: G W (3.4.0-franco.Kernel-nightly #178)
[35720.156228] PC is at snd_soc_dpcm_can_be_free_stop+0x30/0x78
[35720.156380] LR is at soc_dpcm_be_dai_hw_free+0x98/0x118

As far as I can tell, snd_soc_dpcm_can_be_free_stop is part of the audio subsystem.
[Nexus 4 Original Android Development] sean222:
Personally I found Interactive (r178) to be smoother than OnDemand (r180 test)...but maybe it's because we have different setups...I run Nova Launcher with a lot of UCCW Widgets.
[Nexus 4 Original Android Development] franciscofranco:
Yes, just yes. This chip was primarily made for tablet use and not for phones, so the current modem implementation through the USB HSIC bus is just rushed and its really bad.

I couldn't see a problem in there, it was the watchdog that was triggered, so something wasn't doing what was supposed to be doing, probably the modem.

You don't need to go back to r178, because on r180 interactive is just the same as before.

I really don't know what caused that. Truth is that the program counter (PC) was at that function, but why it derped it could be something else. I really don't know. It could really be [34645.199842] batt_temp_set_current_limit: value = 400 the battery temperature might've reached its safe limit so the device simply shut down to prevent damage. I'm just guessing here, I have no clue.
[Nexus 4 Original Android Development] steviewevie:
OK thanks, though it was a panic, not like it just shut down. I've had this a few times now, but I think it's always been when charging in the car and running Ingress. Never had it with 4.2 though.
[Nexus 4 Original Android Development] franciscofranco:
There has been a big change on 4.3, Google rebased the Kernel, so its like a totally different Kernel than before with cleaner drivers etc, and they merged new code for the charger driver, so something might be conflicting with your car charger for some reason. If you can reproduce it everytime with your car charger, then you've found the culprit.
[Nexus 4 Original Android Development] sean222:
Ahh ok thanks. Wasn't sure if r180 included 'other changes' geared towards ondemand. Will go back to r180 and choose interactive.
[Nexus 4 Original Android Development] akyboy:
Not sure if this is kernel `issue` or ROM `issue` , but i like those `IssueS` :P

p.s. nightly 180

GJ!
[Nexus 4 Original Android Development] LibiSC:
That's a fact of life there will always be people that know more of some subject than you :beer:
[Nexus 4 Original Android Development] xanthrax:
That's right , I know kung fu , you can count on me :D

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] i860:
Hi i have same problems while i am using my n4 on charging with the gps on on my car. First i have a mesage that my battrey temperature is high ( i never had that on 4.2.2) and then the reboots ( i didn't think to take a log ). I try 2 chargers and still the same.
[Nexus 4 Original Android Development] franciscofranco:
Probably some derp from Google/CAF, I have no clue.
[Nexus 4 Original Android Development] i860:
I am sure is not your fault. Just to let Steve is not the only one with that problem ( regardless of the kernel or of the charger i had try 2 car chargers).
[Nexus 4 Original Android Development] sordna:
then maybe we should keep interactive as it is? Some folks mentioned they'd like to see the new features from the flo ONDEMAND governor ported to INTERACTIVE as well, but that would probably make the 2 governors too similar (and prone to the same bugs) ?
[Nexus 4 Original Android Development] drawde40599:
I no my battery has taken a hit with 180 completely stock kernel settings. Haven't tryed interactive yet see if i get it back . Haven't seen others mention battery loss so it may be this build of cyanogen killing it also,
[Nexus 4 Original Android Development] sordna:
my batter behaving the same so far... currently 2 days, with 3 hours SOT and 25% battery left.... it should last me till tonight. DISCLAIMER: I leave all networks off and only turn them on when I want to check email, and also use airplane mode at night. On r180 with ONDEMAND and 100mv undervolting. No other tweaks except gamma/color.
[Nexus 4 Original Android Development] drawde40599:
Ya its probably this build of cyanogen because 180 on Cataclysm rom on my other N4 battery not an issue, i dont have a clue how much different jss and jwr kernels r tho
[Nexus 4 Original Android Development] Bobtehblob:
Guys on cm 10.2, the 29th nightly has a wakelock issue. Latest build fixes the problem. So if you're on that build that's probably the cause of your battery loss :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] schmitzekater:
Show me. :D

(Sorry, couldn't resist ;) )

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] SevansD:
I've been following this thread for some time now trying to pick up on the lingo and learn a thing or two about the world of kernels. Mostly it's still just mystifying but I wanted to say in my untechnical way that this r180 smokes! I under clocked the cpu and gpu for battery and it's still much smoother than anything before it.

Obsanity's color values look far better than anything I was able to concoct.

Great job Francisco!

PA+Franco on a not yet Nexus 5
[Nexus 4 Original Android Development] psycho693:
So I noticed after I searched the thread that someone had said mp decision is no longer in the kernel. So is that still true or should it be enabled in settings?
[Nexus 4 Original Android Development] steviewevie:
Still trying to work this out. Do you know why we don't seem to have a kernel stack backtrace for this panic?
[Nexus 4 Original Android Development] Devilman539:
Can I use this kernel with cm nightlys?
[Nexus 4 Original Android Development] xanthrax:
me neither :cool:
[Nexus 4 Original Android Development] franciscofranco:
It should stay disabled, otherwise I wouldn't have disabled it.

I disabled Stacktrace in the Kernel config.
[Nexus 4 Original Android Development] hrzeyni:
Yes, use JSS version with CM10.2
[Nexus 4 Original Android Development] steviewevie:
I see, thanks. Can I ask why?
[Nexus 4 Original Android Development] franciscofranco:
Heres another Kernel r181 test. I merged some Ondemand patches with fixes from CAF, two workqueue fixes from 3.4.60 and I fixed the bug that blocked the CPU if a user underclocked to 1026MHz or 918MHz. Also increased up_threshold to 95. This release should be a bit easier on the battery as CAF fixes a few things on the patches I merged.

Attached are the zips one for JWR and the other for JSS.
[Nexus 4 Original Android Development] franciscofranco:
Well, I don't really like too much debug options enabled, but now that I think of it Stacktrace is pretty useful and its good in case of a crash. I'll re-enable it.
[Nexus 4 Original Android Development] i860:
R181 very smooth in beach buggy even uc to 1.3 and gpu to 320.
[Nexus 4 Original Android Development] RainGater:
I am on CM 10.2 (4.3). Does it work for CM 10.2 (4.3) and build number is JSS15Q?

Thank you and appreciate all your work.
[Nexus 4 Original Android Development] franciscofranco:
Your build number is JSS, I attached a version with a "-JSS" tag. What do you think? :cool:
[Nexus 4 Original Android Development] RainGater:
Thank you and appreciate the quick response. Installed it and looks good so far.

Btw, what do you recommend for the Governor to save battery? I guess OnDemand is the best one for saving battery out of the three available? And, I/O Scheduler?
[Nexus 4 Original Android Development] pjdona:
sleep2wake on 180 does not work with Touch Control 1.8.1 (JSS). Why? Thx u Franco
[Nexus 4 Original Android Development] Luigiesin:
Hey Franco... After a couple of days using 180 my phone started to get laggy again.. Tried interactive and same results. Went back to 176 and magic again!

Currently trying 181.

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] pjdona:
Touch control not work with your r180 test kernel..

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] andyli1985:
You need to ask in the Touch Control thread. And next time please read the OP first.
[Nexus 4 Original Android Development] franciscofranco:
It works on r178 so it works on r180. If it doesn't work for you then you fúcked something up. Try asking on TC's thread ;)
[Nexus 4 Original Android Development] jak3z:
Testing r181 as we speak sir. I will report to you tomorrow the results sir.
[Nexus 4 Original Android Development] tarroyo:
Under power modes my 'Hotplug High load threshold' level is always being set back to 0% no matter how many times I change it, anyone know why this is?
[Nexus 4 Original Android Development] yoyoz808:
Do you hit save after you change it?....
[Nexus 4 Original Android Development] tarroyo:
Yes, I get the settings saved message then soon after I'll check and my changes have been reverted to 0%
[Nexus 4 Original Android Development] franciscofranco:
Depends, what do you want to edit, an Application powet mode or a system power mode? The first tab is only for creating and modifying Application modesx the second updates system modes.

Nothing bad at all, it just bootloops if you flash the wrong Kernel and you only have to either reflash the correct one through the recovery or through the bootloader.
[Nexus 4 Original Android Development] yoyoz808:
Do you have disable per-app power mode service checked?
[Nexus 4 Original Android Development] tarroyo:
Looking at it now, It's the first tab 'set per app modes' what's weird is it'll change the high load threshold setting back and forth from 50% to 0% every so often.

No, that options unchecked.
[Nexus 4 Original Android Development] yoyoz808:
That's weird. It's still does that even when you clear the app data?
[Nexus 4 Original Android Development] desiromeo719:
Damn im loving 181 so far :)
[Nexus 4 Original Android Development] Luigiesin:
Same here!

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] svnhvn:
****, 181 even smoother on me. Fantastic job [MENTION=3292224]franciscofranco[/MENTION]!!
[Nexus 4 Original Android Development] franciscofranco:
Hey guys have a beer with me, todays disco is awesome, so many awesome hot chicks!
[Nexus 4 Original Android Development] svnhvn:
The weather so freakin hot in here, no good for beer. Enjoy your day mate..
[Nexus 4 Original Android Development] DutchDogg54:
Good thing your girl doesn't read your threads ;)
[Nexus 4 Original Android Development] GuyIncognito721:
On 181. Cleared all data. When I go to per app power settings and hit "Choose Application", nothing happens...
[Nexus 4 Original Android Development] franciscofranco:
I approve this message.
[Nexus 4 Original Android Development] Luigiesin:
Hahaha totally!

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] maulich:
Bow wow wow yippie yo yippie yay.....
[Nexus 4 Original Android Development] GuyIncognito721:
Nevermind I'm stupid. Didn't set default first
[Nexus 4 Original Android Development] swirly05:
Really new to the app... Any custom settings recommended??
[Nexus 4 Original Android Development] jamel_tza:
Depends on what you want to do. The stock settings are franco's personal recommended settings but depending on what you want out of your device we may be able to further help you
[Nexus 4 Original Android Development] swirly05:
I knew in the older app the power modes were already preset. This one is new to me. Thanks for the reply
[Nexus 4 Original Android Development] sean222:
181 is so smooth :) All lag from UI and a couple games on 180 is gone! Too early to gauge battery tho. We'll see.

Sent from my Nexus 4
[Nexus 4 Original Android Development] costarican:
181 ? But how come the app says 178 ?

sent from my nexus 4 at the jellybean factory
[Nexus 4 Original Android Development] Redneck Trash:
R180 and r181 are test builds so not available through the app.
[Nexus 4 Original Android Development] Mercado_Negro:
r181 is a test version posted a couple of pages back:

http://xdaforums.com/showthread.php?p=45147202
[Nexus 4 Original Android Development] jamel_tza:
Oh okay ,i understand what you mean now. In the old app power modes where more or less CPU presets. A great all around preset is 1512 max, 384min with a 1026 touch boost.

My settings are the same except touch boost is 1134. Others get good performance and battery from a 1350max. Play around with it and see what you like.
[Nexus 4 Original Android Development] TofuJoe:
This one's for franco: At risk of being clobbered into the ground. Would it be possible to expose the max-current/full-scale current setting for the LM3530 driver? (backlight controller).

Something along the lines of this (Github)
[Nexus 4 Original Android Development] franciscofranco:
Sure, I think CM has a commit for that - I'll check.
[Nexus 4 Original Android Development] i860:
I didn' test 180, but Touch Control 1.8.1 is working just fine with r181.
[Nexus 4 Original Android Development] mendozaram:
Any way to get working only one core when idle or very low use?

Send from my Slimmed N4
[Nexus 4 Original Android Development] sordna:
With r180 got 2.6 days & 4 hrs SOT. Will go back to stock kernel for next cycle to compare, although I don't like the LG screen colors :)

EDIT: Oh crap, looks like I forgot to turn airplane mode at night this time, otherwise would have been over 3 days again.
[Nexus 4 Original Android Development] dex2grigg:
+1 this build is unbelievably smooth!!!
[Nexus 4 Original Android Development] blsrbl:
Delete
[Nexus 4 Original Android Development] whittikins:
Franco, doesn't the up_threshold_multi_core at 60 negate the up_threshold of 95 since any core hitting 60 will make the other core jump to 1026 (sync_freq)?

Also, on test 181 and using interactive, cpu2 (3rd core) is always at 1512mhz. I set hot plug load for all cores to 0 to force 4 cores, and it's easy to confirm this.

With ondemand, I believe the up_threshold_multi_core and up_threshold_any_core are basically keeping cpu1, 2, and 3 higher than they need to be (maybe even cpu0 as well). Apps like CPU spy only show how much time cpu0 spends at each frequency, but the other cores are staying at higher frequencies much more (seen with Perfmon).
[Nexus 4 Original Android Development] blueren:
Somehow, the ui animations are jittery on R181. Testing the same with interactive.

Sent from a Nexus
[Nexus 4 Original Android Development] alanwyl:
Isn't the whole point for r180/r181 testing the new onDemand:confused:
[Nexus 4 Original Android Development] blueren:
I was on on demand only. Saw some stutters here n there. Just wanted to see if they persist on interactive as well. That's what I meant.

Sent from a Nexus
[Nexus 4 Original Android Development] co0kie:
The 1st post only talks about JSS15J but I'm wondering if i can also flash this JSS version on JSS15Q. I'm not entirely sure if there is a difference. Can someone advise?

Thanks!
[Nexus 4 Original Android Development] clshack:
I also will wait for your question.
[Nexus 4 Original Android Development] steviewevie:
The differences between the two are minuscule, so you should be fine.
[Nexus 4 Original Android Development] emanoj.i9103:
Here's your answer. It works great...
[Nexus 4 Original Android Development] co0kie:
Thanks :) been missing the color tuning so much!