yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] franciscofranco:
Its already done for the next patch, I'm wrapping this up for release today.

Temperature comes from the sensor, I don't know what is the sensor doing, if its CPU, or if its CPU + battery and GPU. Its probably just the CPU though.

Fire up dmesg, cat /proc/kmsg then turn the screen off, whats the frequency number that appears in the log?

Someone is ****ing with you because nobody ever said that you need to change any values. The defaults work great, although if you're a power user and you want to experiment you're more than free to try new ones and share with the group your findings.
[Nexus 4 Original Android Development] samwebbo1990:
OK thanks for the quick reply, the default values do seem perfect that's why I was unsure :)
[Nexus 4 Original Android Development] ki2luminati:
Thanks.. You do awesome work. The reason nexus phones are awesome is because of guys like you
[Nexus 4 Original Android Development] reaper000:
Agreed on low volume. You can try Misledz' Nexus Louder mod to improve both loudness and quality

http://xdaforums.com/showthread.php?p=34921922
[Nexus 4 Original Android Development] miguepereira77:
OMG this kernel with the 102 audio functionalities will be EPIC!!!

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] drawde40599:
Try different charger, but for reference my phone is at 70% every day at lunch i charge to 100 takes about 30-40 min. This seems normal to me.
[Nexus 4 Original Android Development] obsanity:
All I can see is cpu0 frequency limit being set to 0?

I have it set at 384

Sent from my Nexus 4
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Not 100% clear on the technical side, but if we flash CM 10.1 M3 or any newer versions for example, and then flash Franco kernel, we still have some partial fixes for the ARP issue? Meaning we have to fix the WCNSS_qcom_cfg.ini in that flashable zip above?
[Nexus 4 Original Android Development] franciscofranco:
Yeah then its the same bug I encountered yesterday. Fixed it on my build.
[Nexus 4 Original Android Development] PetritH:
For me it didn't work flashing the zip from that thread but I modified myself and its working great.. battery life is the same.. didn't really lose more than before.
[Nexus 4 Original Android Development] teamjm:
Franco, on your next patch you will be adding the sound patch?:)
[Nexus 4 Original Android Development] Beremus:
Like he said earlier, it's planned on the next patch! (Well I hope too!)
[Nexus 4 Original Android Development] pikachukaki:
What's wrong with the sound exactly I find it great!except when the phone is laying on his back then it can't be heard :/
[Nexus 4 Original Android Development] Connor Baker:
I'm guessing your phone doesn't have "nipples".

Connor Baker
[Nexus 4 Original Android Development] Cuzz1369:
His patch includes an option to have the speaker moved to the front.
[Nexus 4 Original Android Development] jarjar124:
What sound patch?
[Nexus 4 Original Android Development] miguepereira77:
I guess "headset boost" enable on FK app again, like in 102

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] Beremus:
Exactly.
[Nexus 4 Original Android Development] franciscofranco:
Yeah it was a nasty bug grrr, took me a while to figure out since yesterday night.
[Nexus 4 Original Android Development] jarjar124:
Can't wait :D
[Nexus 4 Original Android Development] Beremus:
You said earlier that you'll release 9.2 tonight? Am I right?
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
well if you modify everything back to how it was pre CM 10.1 with the patch, plus flashing Franco, you should be getting the same battery as before right?
[Nexus 4 Original Android Development] Savant:
You're quite devoted sir.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Arite. Since users know me as the troll regarding battery life, here are my test results.

Franco Kernel r121 versus Cyanogenmod 10.1 04072013 nightly (Stock Kernel)

I ran https://play.google.com/store/apps/details?id=com.battery.utility to run a battery test. I believe it refreshes 10 webpages using a fixed interval using the stock browser. The screen is kept on while webpages are refreshing. The interval is a bit short which is probably why a lot of CPU power is tested here.

At min screen brightness, wifi, etc. I got for run times from 100% battery down to 14%:

Franco: 03:21:07

CM: 03:46:53

I'm not sure why the results are so as a Franco fan I'm not happy with these results either. I'm willing to retest these tonight again.

Oh and who was that one dude who yelled at me challenging me to get 6 hrs SOT on Stock? here you go. Disclaimer: This was when the browser test got stopped because a calendar notification came up, and so while my screen remained on, it wasn't refreshing webpages. I caught this when battery went down to 51%, so I dismissed the entry and resumed the test from 51-14%. So it wasn't like I wasn't doing anything. 37% of the battery was doing a browser test while the rest was just idling on. Anyhow, this isn't hte test that I used to produce the time above. Because of the failed test I had to RETEST last night on stock in which no interruptions were met.
[Nexus 4 Original Android Development] dzap:
Ah, okay so now I know something is seriously up with this new revision. The past few days on r120 and r121 my phone would just freeze out of nowhere. Like no response to the touchscreen at all and if I was on the homescreen, my live wallpaper would stop moving. Oddest thing to have happened, as it has never happened before. I was also experiencing SODs on r120, where the screen is clearly on (black screen) or the screen would completely not turn on at all (as if the phone was off). Had to hard reboot with the power button.

Now I just had a short nap my phone was about 67% before I went to sleep (about 2 hours) just woke up felt it was very warm on the back, but the screeen was completely shut off. I tried to hard reboot it...nothing. Put it on the Nexus wireless charging mat, nothing. Plugged it in, and the dreadded red light of death starts blinking at me, and I start panicking. Gave it a few minutes and it shut off. Unplugged and pressed power and saw the Google logo. Phew.

But I've been uninstalling apps and everything the past few days to figure out what was causing the SOD and my phone completely freezing. I get the kernels from frankos official app as always, and I do not change anything except the color preset values which franko has set. Other than that, stock everything.

I guess I'm rolling back to a way earlier kernel or M1 as I didn't originally think it would have been franko, but I'm thinking it might be.

I'm not sure if I could post a logcat or something, because like I said my phones completely freezes up. Any advice?
[Nexus 4 Original Android Development] franciscofranco:
Thats fixed on the next one, its the bug I talk about few posts back.
[Nexus 4 Original Android Development] JNewms:
The test you used isn't close to real world results. I believe this kernel does much better than stock when it comes to how a device is actually used

Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
[Nexus 4 Original Android Development] dzap:
Ah, thank you very much, franko. I just flashed M1 for the tme being. I've been racking my head trying to find the cause of what it was as your kernel doesn't usually cause me issues like that.

Thanks! :highfive::good:
[Nexus 4 Original Android Development] mammenj:
I get the below error for enabling high performance sound ?
[Nexus 4 Original Android Development] ÜBER™:
LOL, those are for the galaxy nexus...
[Nexus 4 Original Android Development] yokuyuki:
The major difference between stock kernel and Franco in terms of battery use is going to be the hotplugging. There isn't going to be a difference in how the hotplugging is used in real world and a test like this.

Also how would you devise a test that reproduces real world results?
[Nexus 4 Original Android Development] michael_ta315:
you can't because it's different for everyone. Can we stop with the SOT war? It should ONLY be for showing off. It DOES NOT showing how good a kernel can be.

Sorry for the bad grammar lol. US is not my mother languages.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Tests aren't used to simulate real world results. Everyone's usage is different. Even if I modeled a test after Franco's usage, hundreds of other users would say that's not representative of real world results.

The point of benchmarks is for comparative measurement. You think Antutu is how we use our phones?

---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------

You're right. I'm firmly against showing off SOT. It's meaningless.

And yes while tests will be different from everyone, the point of the benchmark I ran was to compare two kernels. You can say it doesn't represent your use (which it isn't supposed to anyway), but what I'm interested in is the results...
[Nexus 4 Original Android Development] pedxing:
What??? SOT posts are my favorite. Since 1998.
[Nexus 4 Original Android Development] michael_ta315:
I'm extremely strongly believe that it could get more than 10hr SOT easily :silly:
[Nexus 4 Original Android Development] drawde40599:
I still have 2 of those :D
[Nexus 4 Original Android Development] alanwyl:
I would be more grateful if somebody posted a test result for us. Similar to the gaming tests, every one of us play different games; it is the same case for battery tests, we use our phone differently. But an experiment needs to be controlled. A battery benchmark is good for comparing battery usage on the same pattern of use on different software. The keyword is different software.

While we are satisfied about the battery life, wouldn't it be great to let Franco know how efficient his code ran?
[Nexus 4 Original Android Development] HB66:
So when I booster the headphone volume it also boost the in call volume. What can I do to fix that? Thx
[Nexus 4 Original Android Development] drawde40599:
With every phone being different right out the box i dont see test being useful, i have 2 Gnex and when i used them daily one was always ran cooler then the other running exactly same setup and hotter one always got less battery, tests may help get idea but i dont see being very accurate . My opinion...
[Nexus 4 Original Android Development] vickpick:
nothing other than decrease in call volume.
[Nexus 4 Original Android Development] DarkRyoushii:
After buying your premium app and enabling USB fast charge option. I have been getting very unreliable results.

On my retina macbook pro with a USB3 port (can supply enough power for fast charge) I plug my stock nexus 4 cable in and attach it to the phone. Sometimes the phone picks it up as Charging (AC) but other times it picks it up as Charging (USB) and then almost immediately goes back to Not Charging. This repeats everytime I unplug and reconnect the USB cable from the laptop. Then there is another issue where it somestimes shows up as Charging (USB) and shows up in USB mode.

I was about to get a logcat for the issue, but I just realized that you need to be connected to computer to do that, and sometimes it doesn't even connect.

Any help would be greatly appreciated.

Thanks
[Nexus 4 Original Android Development] Connor Baker:
I use this sometimes on my phone:

https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en

In fact, here's another one:

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en

It's logcat: for your phone :P

Connor Baker

Mrow.
[Nexus 4 Original Android Development] franciscofranco:
When I activate fastcharge (I also have a retina macbook) my device charges around 4 faster. If you open up adb shell and do cat /proc/kmsg you can see the kernel log and every X seconds you'll see a battery log like this:

<6>[ 7803.152313] adjust_soc: ibat_ua = 500, vbat_uv = 4334544, soc = 100, batt_temp=311

Take note how many seconds before it jumps 1% (with the screen off) with fastCharge on and then with fastCharge off. The seconds is [ 7803.152313] being 7803 the seconds since I booted up last time. The string soc is the battery level, in this case 100%.

Good luck.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
That's why I posted my battery benchmark results. I spent 2 nights testing. One testing CM kernel, one testing Franco kernel. I'm not trying to say A is better than B, but I think it's important for us to know in a more objective sense how kernels are performing, rather than to base it off of "impressions" when people post SOT and brag because that data is pretty much not counted as data.

I think it's important for Franco to have feedback and to be able to know how is code is working.
[Nexus 4 Original Android Development] pedxing:
10 is all I could get playing Snake. :p
[Nexus 4 Original Android Development] DarkRyoushii:
Hey franco thanks very much for the quick reply.

After logging the results it seems like fast charge is working with it taking around 200 seconds to raise from 89 to 90% battery. When I attempted to log the results with fast charge disabled, while leaving phone and laptop sitting on my desk. The connection to adb and the USB connection overall kept dropping before I could even log 1% movement.

I am recording a logcat to try and capture the disconnect.

EDIT: got a capture. The device was connected the entire time this log was running. I've tried different PC, different USB cable and different USB ports. It's almost definitely the phone and I can't tell if it's hardware or software. As I'm typing this the android file transfer program is popping up and disappearing almost constantly.
[Nexus 4 Original Android Development] fauzi_91:
For those who were having push notification delay on screen off u can try app push notification fixer on google play..i think it works..but not so sure..lol :p
[Nexus 4 Original Android Development] Arstoien:
Yeah, it's helping with the push notification delay, but it's addressing a different problem – nothing to do with your screen on/off ;)
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
I don't think that's the same thing. That's to deal with the heartbeat setting but not the nexus 4 arp issue.
[Nexus 4 Original Android Development] franciscofranco:
180-200 seconds means its working yes. I don't know about the rest you reported though.
[Nexus 4 Original Android Development] TheeWolf:
I flashed Franco kernel after flashing a new rom. I have TWRP recovery. After rebooting to the recovery I get vertical grey and white lines, and after that the screen started flickering. It resorted itself after I shutdown the device and powered it up a few minutes later.

It happened two or three times.

Is the bug you mentioned here in my quote and my bug related?
[Nexus 4 Original Android Development] franciscofranco:
Nope, has nothing to do with that.
[Nexus 4 Original Android Development] franciscofranco:
Finally just pushed the app update that I've been working on. I hope it is available soon :) Here is the changelog (I blame the 500 chars limit, I updated much more than what I wrote):

9.2

* Re-designed a lot of UI elements to be more Holo like, specially the Dialogs and other elements that are present through all the UI navigation

* Cleaned a lot of old code and re-write a lot of of pieces

* Add back the ActionBar and now clicking the icon brings you to the home page

* Add headset gain option to the Nexus 4

* Update translations

* Add button to rate the application from the Menu

* Lots of other small changes and improvements
[Nexus 4 Original Android Development] noobdeagle:
i don't know if this is a kernel issue or not maybe people could test as i have never noticed this before the latest few nightly builds.

when in a call the screen turns off like it should when your talking but the touch screen is still accepting inputs this has caused me to hang up twice on people.

i only discovered it because once i went to hang up and i noticed that i had opened a random application while i was talking on the phone.

is this isolated or do other people notice this to ?
[Nexus 4 Original Android Development] i860:
Hi Franco

I think you should mention on the n4 description on playstore about the Headphones volume boost, rather then lots more.
[Nexus 4 Original Android Development] franciscofranco:
Done.
[Nexus 4 Original Android Development] elite_gamer04:
Awesome, thanks for the update mate :D. You made mention of a few changes/fixes to kernel today, are we to expect a 122 to drop tonight?
[Nexus 4 Original Android Development] franciscofranco:
Nope, tomorrow, can barely open my eyes.
[Nexus 4 Original Android Development] elite_gamer04:
Np man, love your work - go rest!
[Nexus 4 Original Android Development] cAase:
Can somebody explain how the gain feautre works? Love music :) (franco)
[Nexus 4 Original Android Development] _Johnito_:
Some ROMs also propose multiple sound sliders. For exemple in my CodeFireX ROM (SR15 _ dont choose SR19), i can set a different volume for in-call, alarms, notifications, headphone ...
[Nexus 4 Original Android Development] thebryceee:
Just had my first kernel panic ever. Rebooted as soon as the kernel app was done downloading the update of all things.

state 4

[ 127.191802] usb usb1: USB disconnect, device number 1

[ 127.191925] usb 1-1: USB disconnect, device number 2

[ 127.196746] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0

[ 127.197174] qcserial 1-1:1.2: device disconnected

[ 127.200500] rmnet_usb 1-1:1.5: rmnet_usb0: unregister 'rmnet_usb' usb-msm_hsic_host-1, RmNET net device

[ 127.226348] rmnet_usb 1-1:1.6: rmnet_usb1: unregister 'rmnet_usb' usb-msm_hsic_host-1, RmNET net device

[ 127.232299] rmnet_usb 1-1:1.7: rmnet_usb2: unregister 'rmnet_usb' usb-msm_hsic_host-1, RmNET net device

[ 127.241699] rmnet_usb 1-1:1.8: rmnet_usb3: unregister 'rmnet_usb' usb-msm_hsic_host-1, RmNET net device

[ 127.265563] msm_hsic_host msm_hsic_host: USB bus 1 deregistered

[ 127.541259] mipi_lgit_lcd_shutdown finished

[ 127.541412] Restarting system.

[ 127.541473] Going down for restart now

No errors detected

Boot info:

Last boot reason: reboot
[Nexus 4 Original Android Development] i860:
Sorry i meant in the main page description for n4

Nexus 4:

* franco.Kernel's auto-flash

* Detailed franco.Kernel changelogs

* Kernels backup/restore on the go interface

* CPU clocks interface

* Governor Control

* Color Control

* Power modes

* All the kernel settings (disable logging, changing IO scheduler, TCP Congestion algorithm etc)

* CPU's online/offline live feed

* Color Control interface

* Full and deep IO scheduler tuning

* Display Gamma interface

* Cores Management

* Lots more
[Nexus 4 Original Android Development] Bobtehblob:
Just updated to 9.2 now, looks great!
[Nexus 4 Original Android Development] Audioboxer:
New app looks great Franco.

Can someone explain briefly to me the difference between volume boost and gain?

Thanks
[Nexus 4 Original Android Development] Luigiesin:
Gain is how much input signal from source is going into the preamp of the headset.

Volume boost is the output signal from the preamp of your device to your headphones or headset...

At least that would be in the audio world.

If you input too much gain, you might get amp distortions.. Doesn't matter how much you lower your Volume boost.... So one works with the other one... Gain (input), volume (output).

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.1 (Mar07)

Kernel: Franco r121

T-Mobile
[Nexus 4 Original Android Development] hospital349:
FRANCO! The new app is wonderful. Thanks for all of your hard work. :)

For anybody using XLOUDER + EIZO+ r121, I'm using Headphones Volume Boost: 2 and Headset Gain: -6 (which counteracts any clipping/distortion/background noise.) The sound through my earphones is particularly great using these values, after plenty of playing around.

My EIZO settings are attached for those who would like to try them. (EDIT: For the Bass lovers out there. You can adjust the second option in EIZO - PSYCHOACOUSTIC II, to medium or large, to gain extra umph in bass tones.)

Furthermore, I noticed a difference in sound quality after rebooting. I would recommend it, though I'm not sure whether it's essential. (AKA; set EIZO values, kernel values & reboot!) :good:
[Nexus 4 Original Android Development] CamoGeko:
Thanks!

Where do you have Headset Gain though as I don't see that in Franco's app anymore...

EDIT: Nevermind, had to update the app. :p
[Nexus 4 Original Android Development] jarjar124:
Did you update your franco app? New update has it
[Nexus 4 Original Android Development] Sparco_92:
EDIT: I was late :P
[Nexus 4 Original Android Development] CamoGeko:
Got it now mate, thanks for your input!

@hospital349 The OP in the mod thread recommends not using compression btw as it can cause fluctuating volume levels. ;)

"Don't use compression in EIZO. Causes massive volume fluctuations as it was set to be an AVLS."
[Nexus 4 Original Android Development] hospital349:
I saw. :)

Though, I've never experienced any issues with it, myself. (I've been using XLOUDER & EIZO since the first release.) It only adds to my experience and doesn't deduct anything from it. I know Misledz has software to read sound operations, etc. So probably from a technical perspective, the fluctuations are visible. For me, it only makes sound output feel 'fuller' and more 'dynamic' overall. I personally recommend it, through it might not be for everybody.

Cheers for info, dude. :good:
[Nexus 4 Original Android Development] buster041284:
which music player u using pal
[Nexus 4 Original Android Development] hospital349:
I stream all of my music from Google Play Music.
[Nexus 4 Original Android Development] buster041284:
u every tried the sound mod with player pro or jet audio or poweramp
[Nexus 4 Original Android Development] hospital349:
Apparently it works very well with Player Pro. Not sure about Jet Audio. There are difficulties getting it to work with Poweramp, I'm not really sure how successful it has been.

Okay guys, I'm really sorry about triggering the OT. I started it, so I should finish it. :laugh:

For more info and conversation regarding XLOUDER, EIZO and all other audio MOD related stuff, the XLOUDER thread is definitely the place to be. :good:

Plus, Misledz (OP) is an awesome guy. Please stop by and say "hi". :)
[Nexus 4 Original Android Development] TheByteSmasher:
@Franco, I didn't see this reported: The Action bar doesn't work for Color Control on the new App update... does everywhere else. Great APP!!!! Thanks for all the hard work!
[Nexus 4 Original Android Development] hospital349:
Hey Franco,

Just alerting you on an additional app bug to the one above this post:

I've noticed that many of the built in colour profiles (including my own; 38_hospital349), have grey values reading 114, 114, 114, (my defaults are 0, 0, 0). However, I don't think that they're actually set to these values, I think they just show as them. My profile colours seem absolutely fine when loading them up. I've noticed 114, 114, 114 are reoccurring grey values on many colour profiles.
[Nexus 4 Original Android Development] buster041284:
its my fault should of PM you my apology franco
[Nexus 4 Original Android Development] LuisLAN:
It is caused by Touch Control
[Nexus 4 Original Android Development] Shano56:
Will r122 turn my speaker into a subwoofer? I'm hoping for dual 12" please
[Nexus 4 Original Android Development] farmerbb:
You're still using the incorrect profiles from version 9.1. 9.2 has the correct profiles, try deleting them from /sdcard and reloading them.
[Nexus 4 Original Android Development] CamoGeko:
Ah I see, maybe they are just inaudible to the human ear. Who knows lol
[Nexus 4 Original Android Development] Pilatus47:
Of course no, due to hardware capability. But maybe a dual 10" could be :D

Enviado desde mi Nexus 4
[Nexus 4 Original Android Development] hospital349:
Amazing. Thanks man. Worked like a charm. :good: