yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Vangelis13:
+1

So many people just went -100 straight ahead and just bootlooped.

Testing with -25 steps and testing stability is the only right way.
[Nexus 4 Original Android Development] ciprianruse88:
Yeah...but all my friends on gtalk that have n4 with fast or faster chip and they uv the same without any problem
[Nexus 4 Original Android Development] franciscofranco:
There is a certain fixed allocated Ram memory dedicated to save the Kernel debug log that gets filled over time. I don't exactly remember whats the limit, I think its something like 4Mb. So after a while without rebooting your device the Kernel log gets filled with new debug info and once it hits the limit it starts overwriting the oldest lines. Since the CPU type info is in the first 10 lines or something its one of the first things to get wiped. Thats the reason why users say "reboot" if it doesn't appear, but since no one ever explains this I thought I'd drop a little knowledge :)
[Nexus 4 Original Android Development] ciprianruse88:
Of course.safety first :)
[Nexus 4 Original Android Development] ctfrommn:
Where's your sense of adventure :p

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] pkelly517:
Not strange at all.

The dmesg log can only get so big, so that it doesn't fill the /var partition. When it reaches a certain point, it starts overwriting the beginning. Classic circular buffer.

A reboot starts the process all over, and allows you to see the PVS value, which is only written upon boot.

Edit: ninja'd by franco himself.
[Nexus 4 Original Android Development] nachordez:
Wrong!!! Each CPU is different even with the same binning, you have to try and see.

Mine is also fast, and -100 freezes my camera. I couldn't go more than -75, and I use just -50. For me is enough. Phone behaves rock solid so, and without heating. But everyone is different.

nexus4 / stock / last Franco.kernel nightly

gt-p5110 / CM 10.1 / Dhollmen kernel
[Nexus 4 Original Android Development] Paradoxxx:
[MENTION=470754]fransiscofranco[/MENTION] , do you think there would be a way to have more gain for headset ?

Like adding 12,13,14 levels in Headset gain?

Or pushing some voltages ?

I really wish I could listen my music a little louder than it is at the moment.

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Vangelis13:
Nowadays? Opting for the average spicy dishes at my friend's Mexican restaurant gets my adrenaline going..
[Nexus 4 Original Android Development] Google86:
wow more than 10? im at 4 and at max vol i feel im going to become deaf...
[Nexus 4 Original Android Development] Paradoxxx:
Maybe my device is defective, or my ears are becoming so, who knows :).

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] Google86:
or maybe its just the headphones....
[Nexus 4 Original Android Development] manulemaboul:
The only issue I got with headset is the mic gain.

People don't hear me, so I just don't use it, just the phones to listen to music.

By the way, here's my new record

With my still ****ty signal lol

I'm wondering what it'd be with a good one. :)

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] antunes20:
noise reduction

Hello, is possible for you to increase the quality of audio caption on video recording? audio quality its very poor in situations with lot of noise

here is an example:

nexus 4: https://cld.pt/dl/download/7fa9e269-dc06-4893-83ad-83720be813e6/VID_20130518_220250.mp4

other device: http://youtu.be/KXLp1ACvQc0

another example:

sound distortion: https://cld.pt/dl/download/175c9f2c-39ae-4e01-ba01-a4fad48b3d78/VID_20130511_202854.mp4
[Nexus 4 Original Android Development] Hanny:
franco, feature suggestion:

the customizability of swipe boost frequency (currently hardcoded at 702mhz)

i understand the current setting is optimal for battery for most of the users but me and a minority of them desire a higher level of smoothness :p

currently i found out that 3 cores_on_touch (practically, swipe) + default input_boost 1026 performs better (i.e. give me the least, almost none animation stutter) than the default 2 cores_on_touch + input_boost 1350

i believe thats because the input_boost only modifies the value of single touch but our major animation stutter comes from notification presses.

to further explain this i guess the entering of the first level of an app (gmail list, hangouts/whatsapp conversation list) loads less stuff than the second or deeper level of an app (directly to a conversation/email) so the chat history/content have to be loaded. thats why notification press demand more cpu power than a single touch app launch from homescreen / app drawer.

thats why we can take the advantage of swipe-boost as we surely activate it when swiping down the notification bar, and the cpu can get ready for the upcoming notification app launch, where i think it is essential to raise / let us customize the swipe-boost frequency. i believe 2 cores with a higher freq can benefit my battery than my current setting of 3 cores_on_touch at 702.

and at the meantime i would even try to lower the single touch boost freq to 702 when increasing the swipe boost freq, based on my above theory of app launching at different areas (i tested it and briefly confirmed with system monitor but still cant be 100% sure because it updates slowly at 1sec). 702 should be enough for keyboard typing.

also, back to my unanswered question some time ago - the swipe boost (both cores and freq) listens to min_sample_rate and boosts for 500ms now as well, right?
[Nexus 4 Original Android Development] nadaltennis77:
This kernel doesn't support undervolting, right? Is it pre undervolted at all? My N4 has gotten pretty warm simply playing games for a little while. Now, I know this isn't the highest end phone, but it's very new and has awesome specs so I don't expect it to be overheating playing a pretty low quality game. Nothing intense like need for speed or a fps.

Any ideas? Thanks!
[Nexus 4 Original Android Development] ctfrommn:
You can UV.....down to 700mv I believe.
[Nexus 4 Original Android Development] uploder:
Just coming to pay my respects lol. Finally flashed to see what all the hype was about.... Believe the hype people. Such an obvious battery improvement. No placebo! Thanks Franco:)
[Nexus 4 Original Android Development] jtwlbz:
Ahh wifi is acting up...
[Nexus 4 Original Android Development] Cuzz1369:
No need to bookmark. Someone asks every 10 pages :D

Carbonized and francofied N4
[Nexus 4 Original Android Development] Joloxx9:
I asked many times here , Its only thing that keep me away from this kernel. I sent a pm to Franciscofranco and still nothing . Only thing that can help is change mic gain, fg. Standard is set to 0 so if you set - 5 should be much better. How do I know this? Simple, I use faux kernel and his App to change it and when I call from factory where is loud at - 5 is ok but on 0 second person cant hear me. I posted even link to the source code needed to be add to give us option to change it but idk why Franciscofranco ignored/miss all my posts about it:)

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] Vangelis13:
^^

Francisco does not receive pm's as far as I know..
[Nexus 4 Original Android Development] jassycliq:
He also doesn't use Faux's code. Don't ask why.
[Nexus 4 Original Android Development] PetritH:
Why?:victory:
[Nexus 4 Original Android Development] Shano56:
Sorry to hear that. Get a new router that doesn't crap out or talk to your ISP
[Nexus 4 Original Android Development] gravitysandwich:
¿Que? Wrong thread

That's the only Spanish I know lol.
[Nexus 4 Original Android Development] Shano56:
Oops! Forgot to add the quote. Edited xD
[Nexus 4 Original Android Development] Connor Baker:
I don't know if I posted this already in this thread (it may have been in the color spreadsheet thread).

So. I took [MENTION=2628624]obsanity[/MENTION]'s recommended gamma settings, toned down a few colors, added brightness, and went cray-cray with the contrast and saturation settings. On MY SCREEN, these colors look amazing, and have become the new default for me. This setting is not intended to be accurate, but to provide extremely punchy and eye searing colors, and to be... not precise, but fun, if you would.

Color Multipliers:

255 255 255

Grays:

1 1 1

Mids:

103 103 103

Blacks:

119 119 119

Whites:

7 7 7

Contrast:

23

Brightness:

6

Saturation:

119

And a screen shot of values below

Many thanks for your time,

Connor Baker
[Nexus 4 Original Android Development] warpaper:
Which file should i flash?

question solved.
[Nexus 4 Original Android Development] sNoxious:
The latest one which is Milestone 2.
[Nexus 4 Original Android Development] ÜBER™:
Just the second one.
[Nexus 4 Original Android Development] ctfrommn:
Milestone 2 is the newest and most up to date.

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] warpaper:
understand. sorry for stupid question.
[Nexus 4 Original Android Development] RussianBear:
Anyone having issues connecting their phone as a mtp device? my pc can't install the mtp drivers and the phone itself is giving a "android.process.media has stopped" repeatedly. Tried stock aokp kernel (on 12th and 21st nightlies) and everything works as it should.

Tried the latest R139 and ziddey's modified R137 w/otg support.
[Nexus 4 Original Android Development] TrenchKato:
r139 has restored my battery. Easily getting a extra hour on screen time. This is with 5 gmails, twitter, Facebook, everything sync... Truly awesome..

Nexus⁴ Life
[Nexus 4 Original Android Development] alanwyl:
Finally we see somebody use the phone as a phone.
[Nexus 4 Original Android Development] Panichdi:
vs. Faux

Hi All,

I have been on Faux kernel so far with the Nexus 4.

How does the battery life of the Franco kernel compare?

Thanks in advance! :good:
[Nexus 4 Original Android Development] ÜBER™:
It doesnt :p.

No one can really justify that for you, just try the kernel out. Remember if you want to go back to Faux you need to flash his Reset kernel.. then his kernel zip. :good:
[Nexus 4 Original Android Development] zellleonhart:
guys, using r139 here, noticed that in trickster MOD the governor control for interactive governor keeps changing everytime I enter the setting.

For example the min_sample_time will sometimes change from 500000 to 40000

timer_rate will change from 30000 to 10000

go_hispeed_load from 99 to 80

do I have to care about these settings?
[Nexus 4 Original Android Development] ÜBER™:
Its normal. Don't worry about em.
[Nexus 4 Original Android Development] drawde40599:
Wifi

Nm im a dumba$$
[Nexus 4 Original Android Development] nexusmaniac:
Thanks I much prefer these settings to the recommended ones by obsanity :)

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] alanwyl:
Investigating the microphone

http://www.youtube.com/watch?v=7JPQvh2VVEY

This video is recorded beside a busy road. You can hear the audio is crap.

http://developer.android.com/reference/android/media/MediaRecorder.AudioSource.html

MediaRecorder.AudioSource has several constants inside.

Through experiment, the DEFAULT one is MIC.

http://code.google.com/p/android/issues/detail?id=9913

From #58, somebody suggested that VOICE_RECOGNITION is defined not to do any signal processing.

http://developer.android.com/guide/topics/media/audio-capture.html#example

In this link, I slightly modified the source to let user change the AudioSource, namely MIC and VOICE_RECOGNITION.

The APK is in the attachment.

The experiment is simple, I record an audio clip using either source, then I record a video using the stock camera app. I used a headphone to listen to the recordings. It turns out the "volume" of recording from MIC is muuuch louder, yet with clipping noise; while the raw signal is softer but more natural. So, I suspect it is the processing of audio inside MediaRecorder that worsen the sound quality.

@franciscofranco, does it mean it has nothing to do with the kernel? Maybe the microphone issue can be fixed on the ROM side?
[Nexus 4 Original Android Development] Panichdi:
Hi there,

thanks a bunch. Will give it a go.

Cheers!
[Nexus 4 Original Android Development] kara mustafa:
Is there any easy method to apply those settings in franco app?
[Nexus 4 Original Android Development] nexusmaniac:
Unless someone posts the save file which is something I can't do right now, then no sorry, but it only takes about 30 seconds to do :)

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] kara mustafa:
I have never did it before, so it is not so easy for me and I am afraid that something will go wrong.
[Nexus 4 Original Android Development] mohitgalaxy3:
Do you have tool kit if not download it and install the drivers from it.

It will work I guess.
[Nexus 4 Original Android Development] Foxnov1990:
Hey, I must say I truly enjoy r139 and the battery life is just incredible!

But I'm having a small issue that has been going on since r134.

Say out of 10 phonecalls 5-6 times when I click the button to end the call the notification bar comes down by itself (my fingers not even close to it to slide it down).

I don't call that often so it's not entirely annoying and I can live with it.

Just wondering if other people are still experiencing this issue.

Asking because I thought this was fixed in one of the preMilestone2 builds.
[Nexus 4 Original Android Development] drmclove69:
I experience an issue somewhat similar but instead when I try and hang up sometimes, the end call button doesn't respond after many many click and then finally it does it by itself. Have experienced this in all releases by the way. If a logcat is able to help I will get it.
[Nexus 4 Original Android Development] nexusmaniac:
Don't worry nothing can go wrong, the only settings that your changing are the colours so of you put the wrong settings then it will just be a funny colour which can be easily changed. Just move the slider in the settings to the correct number :)

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] Nethojs29:
Since kernel is relate to battery, hope this question isn't off topic.

Why it drop like 7% when reboot? Two Time and two drops. Even I rebooted at 9% and when it booted it turned off... If it helps, carbon 17th nightly
[Nexus 4 Original Android Development] steviewevie:
It's the battery reporting not working properly, and "catching up" when you reboot.

Sent from my Nexus 4

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

It isn't pre-undervolted by default, no.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Arstoien:
Not exactly a solution but I'm ending a call with the power button (accessibility settings) – maybe you could try and like it?

BTW I'm doing it this way because I like it, not because I've got the same problem. Though I am experiencing some problems with the touch screen accuracy but I've mentioned these already, no point going over it again.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Pure Drive GT:
I've got a question about the kernel flashing process. I generally only do clean installs. Wipe data > wipe chache & dalvik cache > install rom & install gapps > format sd card. Is it a good idea to flash kernel right after rom before the initial setup or is it better to do after. Does it even matter? And is wiping caches after kernel flash recommended/necessary/automated?

PS: I truly believe clean installation every time is a good idea because I seem to encounter like 10% of the issues usually mentioned in these threads. Which means almost 90% of the reported issues are not actually related to the kernel/rom. Please dont quote me on these numbers xD
[Nexus 4 Original Android Development] Dav_prime:
I usually queue it in twrp right after ROM flash.

Sent from my Nexus 4 powered by paranoid ROM and franco.kernal
[Nexus 4 Original Android Development] Foxnov1990:
I used to have the power button mapped but due to touch control (used to use it) the screen remained black in call sometimes so I had to use the power button to wake it up.

So I just tried it and it reacted upon clicking the power button, the notification window came down so I had to slide it up anyway.

It appears to happen right after the call is ended (by End call or Power button), so it's some workaround but it's still sliding down therefore not rly a fix.
[Nexus 4 Original Android Development] baxtandroid:
You should flash the kernel after the ROM because the ROM often has its own kernel so it will erase the previous one.

No need to wipe anything to flash a kernel, and it's not better if you do (unlike for roms).

Sorry for my English.

Sent from France to the best forum ever using my awesome Nexus 4 ;)
[Nexus 4 Original Android Development] Luigiesin:
Mine actually drains slower on 139. I used to see that a lot on 136.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco r139

T-Mobile
[Nexus 4 Original Android Development] dapsANDpoundz:
Agreed. But mobile data drains the battery heavily regardless I guess.
[Nexus 4 Original Android Development] italia0101:
Higher in every section on.139...
[Nexus 4 Original Android Development] BomB@s:
Am I the only one who is still having trouble with the connection delay? I am getting delay in things like Whatsapp messages, Google play downloads (when I download from the computer) etc.

Also, there is a delay in the lockscreen sound, I am not sure if it is a common issue.
[Nexus 4 Original Android Development] kyokeun1234:
Connection/notification delay is common and is a fault of Google.

Lockscreen sound delay is common too I believe. If you don't like it, just take it off. I also had this problem on my Galaxy Nexus but I just ignored it.
[Nexus 4 Original Android Development] BomB@s:
It's not the common delay when the screen is off, it's happening when the screen is on and I have to get into the application to get the message.
[Nexus 4 Original Android Development] kyokeun1234:
Oh. My mistake. I don't have that, sorry
[Nexus 4 Original Android Development] dsmpampis:
Sorry for the off topic, but which Theme are you using!

Tapatalked with my Nexus 4 powered by ParanoidAndroid 3+
[Nexus 4 Original Android Development] manulemaboul:
Lol, each time I post a screen, someone asks what my theme is :).

It's alloy white ;).

Envoyé depuis mon Nexus 4 avec Tapatalk
[Nexus 4 Original Android Development] TheUnreaL:
Hi folks, what version of the kernel do you suggest to flash? I'm interested in a stable kernel cuz I want to change from stock kernel! Milestone 2 is ok or it is too old? I don't want weird bugs, my first priority is to solve msm_hsic and AudioOut_2 wake locks that ruins my battery life
[Nexus 4 Original Android Development] klvnhng:
r139 is very stable, IMO.

Sent by carrier pigeon
[Nexus 4 Original Android Development] mariosraptor:
Is only me which thinks that with 139 the phone gets a bit hotter more easily?

But it is the only issue I have found :D
[Nexus 4 Original Android Development] PetritH:
Undervolt, problem fixed :D
[Nexus 4 Original Android Development] drakexpl:
R139 rly rocks :)

Wysłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] suprano:
I'm really new to Nexus 4 forum as I just got my new nexus three days ago. Rooted it that very night with a custom Rom, of course Slim Bean..after reading through several posts and OP in this thread, this is a great kernel. No issues here and it's really smooth on r139. Great work done man. :D:thumbup:

Slim'D Nexus!
[Nexus 4 Original Android Development] RussianBear:
Can someone on aokp test this, please?
[Nexus 4 Original Android Development] Janne79:
Thank you for mentioning the Audioout_2 wakelocks. I don't know if it has anything to do with the kernel (I doubt that) but this problem exists, no matter which kernel version you are using. I opened a thread inside the N4 Q&A thread but unfortunately no answer yet. Now I see that I am not the only one having this problem.

Sorry for the off topic (if it really is)

Edit:

http://xdaforums.com/showthread.php?t=2288496

That's the thread mentioned above. If you ever find a solution, please post it. Thank you.
[Nexus 4 Original Android Development] TheUnreaL:
I've answered you in your thread, try to disables touch, screen lock and keystones sounds and see if it disappears
[Nexus 4 Original Android Development] DowntownJeffBrown:
As am I :confused:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] DowntownJeffBrown:
Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Ibsonic:
You sure? Stock kernel or faux, doesnt have those warnings.. its not like 20 lines, but pages and pages non stop instant after eachother..
[Nexus 4 Original Android Development] KonstantinKeller:
I'm pretty sure he would know what's causing it ;)
[Nexus 4 Original Android Development] Ibsonic:
i'm sure he will, as a matter of fact it is known..

http://code.google.com/p/android/issues/detail?id=39723

But, i was worried because other kernels doesnt gave me those warnings..
[Nexus 4 Original Android Development] KonstantinKeller:
If I'm correct, this is normal. Its caused by franco disabling mpdecision so it doesn't mess with the min CPU freq and set it to 1026mhz.

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

My guess is those kernels don't use the latest SDK, or they filter the error from the logcat.
[Nexus 4 Original Android Development] Ibsonic:
And for the power_hal warning, franco wrote
[Nexus 4 Original Android Development] DowntownJeffBrown:
Franco n20

Sent from my Nexus 4 using Xparent Blue Tapatalk 2

---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------

Ahhh thank u much my friend

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] elmalote:
Can someone tell me what command I have to use to read the voltage levels used in the kernel in android terminal emulator?
[Nexus 4 Original Android Development] treUse:
Quite OK battery life I'd say :)
[Nexus 4 Original Android Development] Vangelis13:
Flat green signal line in the graph?
[Nexus 4 Original Android Development] Ibsonic:
Thats not signal, thats charging.. he's cheating a bit :D u can also see the graph go up again..:cowboy:
[Nexus 4 Original Android Development] franciscofranco:
There is NO undervolt interface here.
[Nexus 4 Original Android Development] Vangelis13:
No, I mean if his signal reception is good. A constant green line. Without that - lesser battery performance.
[Nexus 4 Original Android Development] jjcandroid2012:
Thanks for sharing your settings! Just want to remind everyone every chip is different with different results. For example i had to raise my governor to 1026 because if i didn't major lag. Thanks again for sharing settings and franco for his hard work !
[Nexus 4 Original Android Development] cpom1:
Just to know what the temperature of the cpu is. Please Franco. I'd greatly appreciate it.

Sent from my Nexus 4
[Nexus 4 Original Android Development] drawde40599:
WOW :/
[Nexus 4 Original Android Development] techmatlock:
There's many apps that will give you this information including my favorite, Android Tuner. However, it is up to Franco whether or not he will consider it.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Dude you know it shows when u charge right?

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] kioshi:
LOL...if the graph goes up its...charging. Everyone went to grade school here...at least i hope so :crying:

I thought we werent posting battery screenshots unless it was a major drain in one of the nightlies...
[Nexus 4 Original Android Development] rahulmaheswari:
For msm-hsic, unfortunately there is no solution to it. As long as it stays below about 30-40 mins for a days use, its ok.

For audioout_2, its directly connected to all system sounds (not music as this is audioout_3) so just disable touch sounds under settings-sound and you should be good to go. :good: