yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
I just wanted to chime in on the people who brag about 6 hours SOT. What does that even mean? Is that figure even important?

http://www.anandtech.com/show/6440/google-nexus-4-review/2

If you look at Anandtech's review, they do the wifi and 3G/4G browsing tests with screen on. Procedure is explained more in their iPhone 5 review (http://www.anandtech.com/show/6330/the-iphone-5-review/13).

Thus, if the Nexus 4 is hitting 6 hrs in their wifi test, that means they easily achieve 6 hrs SOT while doing something. Unfortunately 3G is much worse at only 4.15 hours.

I guess my point is that a lot of people are getting 4-5 hrs SOT no problem. Not impressive. For those that are hitting 6, which is fewer of you, most likely you are using Wifi. But since Anandtech achieved that already, is 6 hours impressive? They did it on stock. If Franco's kernel is supposed to give you sooooo much better battery life, then shouldn't you be showing off 10 hours SOT?

I'm not trying to diminish Franco's work. I love this kernel, but all this battery talk is almost meaningless if we don't do objective testing. As an engineer, I don't think you can say Franco's kernel doubled your battery life or whatever unless you benched his kernel using an objective test say like what Anandtech or GSMArena or other sites use. Then show that you went from 4hours to 8 hours for example. That would mean something. But all these random screenshots showing 6 hours SOT... ugh. You've contributed nothing to this thread.
[Nexus 4 Original Android Development] Underground_XI:
I am a normal user and i do not care about tests you engineers do. However i am glad i always get 6 hrs screen on time on wifi with franco kernel. What is bothering is the fact that people like you have a problem with it. I bought this phone with my $, can you please let me enjoy it without having to explain to people like you that 6hrs is not impressive since some losers at anandtech claim to have got that on stock kernel? Thank you.
[Nexus 4 Original Android Development] Steven08:
screen off

i've just installed this kernel and it's working great,but i've encounter one problem.when i make a phone call,the screen turns black and i can't turn it on again,at leat,not untill the other person hangs up.does this any connection with the kernel or something else?thanks
[Nexus 4 Original Android Development] Underground_XI:
Remove the screen protector or just cut the top left side so it does not block the sensor.
[Nexus 4 Original Android Development] formicae:
Proximity sensor acting up. Do you have a screen protector without cut-outs for it? It's in the top left corner along with the ambient light sensor.

There are proximity sensor test apps available, but I've never used one myself. Probably the easiest way to check.
[Nexus 4 Original Android Development] stevessvt:
That is one singular parameter of battery life. Gaming will use way more juice than simply browsing with either wifi or 3/4g. To that extent what was his signal strength? Your going to use much more battery if your inside and toggling 1-2 bars vs outside with 4 bars. These are just a few examples of real world usage vs testing in an office in best case scenarios.
[Nexus 4 Original Android Development] resynx:
It's not kernel related. I've never had this problem and it hasn't been reported by anyone else so far. Try doing a full wipe?
[Nexus 4 Original Android Development] MrDarkKV:
I dont know whats happening, have had my battery drain fully within 3 - 4 hours in the last week (strange) then today and yesterday I've been getting amazing battery life, like.. REALLY amazing.

0% drop in the last 4 - 5 hours...

FYI: The large drop is due to a reboot and flash :good:
[Nexus 4 Original Android Development] ctfrommn:
Did you uninstall any apps or change the syncing of any?
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
While screen protector CAN be an issue, it's only an issue if you have crap on your screen protector. I have gone through two N4s BOTH with screen protector covering the proximity sensor and I can tell you that using another app to test the proximity sensor, it works still. Ive used many other phones with the screen protector covering the proximity sensor. Maybe the N4 is more sensitive, but I haven't had issues yet, so I wouldn't say that proximity sensor will fail with a screen protector.

The other thing I ask is do you use the Touch Control app for slide2wake? It's a known bug that the proximity sensor will misbehave and screen will not auto turn back on once you pull your face away. I have to manually power on the phone with the power button (or maybe slide2wake) to turn it back on.
[Nexus 4 Original Android Development] formicae:
Not true. I've had perfect, spotless installs of screen protectors (wet and dry) that exhibited proximity sensor issues. Never had a problem since I got SGPs with cutouts.

The N4 is definitely fussier, as I've had several devices that didn't give a damn if the proximity sensor was covered by something clear.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
I agree that gaming will use way more juice. But what I'm addressing is the hordes of users here talking about their 6 hours of screen on time. If Anand got 6 hours SOT with a stock kernel doing webpage refreshing at fixed intervals, then I'm not sure what we're trying to accomplish here by talking about 6 hours of SOT... I'm pretty sure people aren't getting 6 hours of SOT playing a 3D game like GTA. At least I don't get that impression from reading the posts.

What are you like 15? That's great you can be glad. I bought this phone with $ too and I expect it to run well. Why does it bother you that I have a problem with it? You think Anandtech is full of losers? Bryan Klug does more in-depth reviews than any other reviewer be it GSM ARena, Engadget, The Verge, etc. They know what they're doing. I'm just pointing out to you that they got 6 hours on stock kernel. So my question to you is what does getting 6 hours with all your tweaking even mean? It means you matched stock performance. If you're happy, then be happy.

Once again I'm not trying to take away from what franco's done. I'm just trying to address all the stupid battery posts we get here.
[Nexus 4 Original Android Development] MrDarkKV:
Nope nothing, just updated to 118 from 117.
[Nexus 4 Original Android Development] ctfrommn:
That logic is flawed unless Anandtech does the same tests using Franco. Screen on refreshing web pages is not what a normal user does. I could leave my screen on and do nothing with it and likely get 8-9hrs. Processing is where the drain is....I guarantee you arent getting 4-5 hrs SOT with stock kernel doing normal phone things. Scientific method needs to be employed for results to be meaningful.

---------- Post added at 03:40 PM ---------- Previous post was at 03:40 PM ----------

Franco voodoo then I guess :D
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Well I'm not saying it doesn't happen... it might. I haven't seen it yet. I used the SGP without a cutout as I was one of the initial buyers in the first wave. Even when they offered to send me a new one I didn't replace the screen protector. That was when I purposely used one of those proximity sensor apps to test. It definitely registers my face against the phone or my finger, but with nothing covering it except the screen protector, the proximity sensor worked.

I searched Youtube and saw one video of someone demoing the problematic screen protector, but their video was so bad in that the screen protector had gunk on it. You clearly saw dust and crap trapped under there so without a doubt it would change once you take it off.

Not trying to dismiss your claim, but I see a lot of users claim some bug event, and then it becomes repeated user after user. I'm sure the proximity sensor thing started with 1 or 2 users and then somehow people think it's a rule that proximity sensor covered with screen protector on an N4 = death. Because I can bet you there are hundreds of users who have no problem too. So whether the problem rate is 1%, 10% or 85%, we don't know.
[Nexus 4 Original Android Development] sirxdroid:
I vote that ÜBER™ adds his settings to the spreadsheet, I like his settings.

I also like the recommended gamma settings (by obsanity) from f.Ku with the RGBs lowered to 245.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Refreshing webpages is not what a normal user does, but it's similar to running non game apps. Say reading news articles on Pulse. All of that is just loading webpages too. You're right that it's not what users do, but I think you can find many usage patterns on a phone that are similar to the refresh browser test. Besides reading pulse you could be reading and responding to emails. Or reading Facebook posts. I mean that's what most people are doing to get 6 hours SOT anyway, not playing GTA for 6 hours.... BTW running a browser test does easily ramp up 2-3 cores with 1 around 1ghz typically, so it's not like some 384mhz test only.

Basically, what I'm saying is 6 hours SOT isn't an impressive metric at all. In general 6 is a less common number I see here. I see more 4-5s because they're probably doing something else on the phone too that's more draining. Furthermore, none of these numbers are achieved on 3G. For the 3G/4G users here, the battery drain is WAY more, and they achieve far less SOT. Which goes back to my point. If AT can achieve 6 hours while doing a constant refresh test (whcih isn't some meaningless task because it does task the CPU decently). On the i9300 forums people are talking about much higher screen on times.

Anyway, perhaps the best way to talk about screen on time is for us to run an objective test to compare. Here's one for example:

https://play.google.com/store/apps/details?id=com.battery.utility

The point is just to provide a better reference. If someone shows that stock gets 6 hours for example and Franco gets 8.5 hours, then yeah, that's very meaningful data. With that said I would like to test on this but I don't have unlimited data for the 3G tests... I might go test r111 vs r118 on wifi just to see :)
[Nexus 4 Original Android Development] ctfrommn:
All one needs to do is use the stock kernel for a week or so, do their normal thing.....switch to Franco (or any other custom kernel) and they will immediately notice a difference based on their usage. I agree NO ONE is getting 6 hrs on data, but 6 hrs SOT real world is very good and is usually accompanied by 24+ hrs unplugged. The GS3 has an Amoled screen and a dual core processor (way weaker gpu too) so that is not a valid comparison. Im not sure what point youre trying to make, but custom kernels definitely achieve better battery life, and thats not debatable. I mean no disrespect, I just fail to see the point of this discussion....be well :)
[Nexus 4 Original Android Development] sirxdroid:
Thanks! Is your Max CPU freq 1.3 or 1.5? I see in the governor it's 1.3
[Nexus 4 Original Android Development] leets4uc3:
This is more ROM related but do any prop modder tweaks have any negative affects on the phones performance immediately or after some time?

I flashes xenonhd 2 night ago didn't change any prop modder or anything just flashed r118 and left everything.

My phone get laggy/slow after a while but when I reboot all is well. I am testing ubers interactive setting right now and after a reboot all was well.

Can the lag/slowness be due to a lack of ram or what?
[Nexus 4 Original Android Development] ctfrommn:
Ive never found any of the prop mods to have a positive effect on this phone. I think their value was on GB and below. I would avoid using any of them where possible.
[Nexus 4 Original Android Development] xanthrax:
During those 4 - 5 hours with 0% battery drain I can see 3 times your screen ON and is impossible not to drop at least 1% per screen ON

Most probably you've got a false reading. Your statistics is irrelevant then.

~~~

Below is my battery drainage widget monitor provided by cool tools and you can see 128 mA consumption when on tapatalk over 3g, slim ROM, Franko 117, ondemand, UV by -100

With 111 the drainage used to be about 450 mA average, same settings

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] ÜBER™:
1.5

Sent from my Nexus 4
[Nexus 4 Original Android Development] osm0sis:
Hmm which device, N4 I assume? Might be they updated row and annoyingly renamed some of the tunables. Still 'read' on the GN and N7.
[Nexus 4 Original Android Development] Cantacid:
I just had a crazy lag on my phone. Like stuttering, nav bar responding alteats 5 seconds late. Is there a log somwhere i can see and post here to figure this out? I dint have to reboot niether did it on its own.

R118, CM 10.1 M2, UV -150Mv
[Nexus 4 Original Android Development] formicae:
Yeah, that video made me cranky, he had clearly peeled and repeeled that thing a zillion times. Kind of like that guy in the Accessories forum who said 'this screen protector sucks' when he tried to wet-apply a dry-apply film and it looked like crap.

It's definitely not 100%, I agree, it varies from unit to unit (who knows, both protector and phone, maybe). I also had an initial-run Spigen and waited until I had tried it (didn't have the phone yet) before letting them send me a new one. But it definitely would black out the screen on calls whether my face was there or not.

It was just an easy thing to rule out for the issue the poster was having.

Edit: all this to say 'it's not a kernel problem.'
[Nexus 4 Original Android Development] Underground_XI:
Prove me you get 6 hrs screen on time with stock kernel and i will give you my phone for free. Otherwise shut up and stop trolling.
[Nexus 4 Original Android Development] :
Fancy seeing me here... Where do I know you from?
[Nexus 4 Original Android Development] santeana:
Lighten up a bit on your UV first. See if that helps your reboot issue. UV by 150mV and then say I had a reboot.... Good way to start a flame war in a thread like this one.
[Nexus 4 Original Android Development] Cantacid:
LOL, I tried UV -100 which seemes stable and then went a bit ahead. Took stability tests. Seemed stable enough. And I did not experience a reboot, just switch of the screen and back. But until i dint do that, it was crazily slow and laggy. This happened for the first time since ive been flashing franco.
[Nexus 4 Original Android Development] JarGnex:
First time I get these results on my nexus 4. :)

On latest kernel

Latest cm10 nightly
[Nexus 4 Original Android Development] Gugus38:
Just wanted to share my color profile, I have compared to other profiles and adjusted taking all of them into account...

Color fringes are not destroyed, details in shadows are visible, contrast is not CRAZY as in some profiles, you can still get pretty deep blacks.

IMO it is the way to set up an IPS display.

255 252 253 114 114 114 119 119 119 119 119 119 5 5 5 10 2 5

White point is slightly higher than 6500k, I like it more in the 6750-6800 area like on my imac.

Let me know what you think and share your possible improvements over this :)
[Nexus 4 Original Android Development] trident167:
Fast and smooth with r118. Nothing evil to report.
[Nexus 4 Original Android Development] franciscofranco:
114 is not a valid value O.o
[Nexus 4 Original Android Development] steviewevie:
They don't know what they are doing when it comes to their tests predicting my normal usage of my phone, no. My own non-scientific use of my own phone is a much better test, seeting if I notice a significant difference from when I changed from stock to Franco, and then when I flash different versions of Franco.

That stuff you posted about screen protectors didn't make any sense regarding the N4. I can only assume your are new to the N4 and haven't seen the dozens of posts from users who claimed they had a proximity sensor problem, only to find it was their screen protector.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Gugus38:
lol 0.o That's.. weird, I don't even have 114 in the sliders, but its in the profile file :confused:

EDIT: rechecked everything and "114" never appears in your app, tried to save under a new name, 114 values are still here... Its a hidden cheat code to unlock the godmode's color profile ? :>
[Nexus 4 Original Android Development] miguepereira77:
+1 And to add, they forgot about the signal strength, that sucks battery hard when you are, let's say in the country side and other strange usages like...phone calls??? :p

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] sirxdroid:
Thanks. Looking good.

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

Or a bug? If I reset to default values which sets all the gamma numbers to 0 in the sliders and save the profile, here's what I get:

255 255 255 114 114 114 21 21 21 118 118 118 48 48 48 0 0 80

Where do the 114, 21, 118, 48, 80 come from?

@Franco - you may also want to look at the profiles in this file:

http://xdaforums.com/showthread.php?p=39842448#post39842448

They are also full of 114.
[Nexus 4 Original Android Development] franciscofranco:
But 114 is not valid :/ my app won't like it, I guess I will have to re-work around it.
[Nexus 4 Original Android Development] sirxdroid:
But it's *your app* that saves 114 :) If you put all the sliders to 0 and save with your app, you get 114 in the file. At least it seems to round-trip well, if you load the profile the app doesn't crash and the sliders are at 0.

I noticed this a while back but I thought that slider at 0 meant you had to send 114 to the kernel. And you are saying that's not the case, there's a bug somewhere.
[Nexus 4 Original Android Development] Mercado_Negro:
That might be the cause of some random double reboots I've been experiencing. The PA Halfbreed file someone kindly posted here a few pages ago also have some values that your app doesn't allow and that's what I've been using for about a week. I'll set everything up again and see how it goes.
[Nexus 4 Original Android Development] el_charlie:
I just copied my profile file with Root Explorer, then edited with this values and looks pretty good!

Give it a try.

By the way, loving r118. I was on M1 because I found the newer laggy with many micro stutters when playing Real Racing 3 or by scrolling in Twitter or even the app drawer. 118 is as smooth as M1 and gives a whooping 11000 in 3Dmark.

I'm on stock 4.2.2.

Cheers!
[Nexus 4 Original Android Development] pkelly517:
Perhaps you've never written code.

Dev thinks he can write something better than X. He tries. He sees that's it still not better than X, but getting closer.

Dev will not stop until he truly thinks he can't, or he does.

Obviously, the hotplug coding is in early stages. Those that report that they prefer r111 are actually providing valuable feedback. If everyone reports that the latest kernel is 'smoothest ever', like you will find within the first hours a kernel is released, then development stops. Critical feedback is FAR more valuable than 'even smoother' feedback. Unless the changes warrant.
[Nexus 4 Original Android Development] Hyflex:
I really want to use this Kernel but atm I'm having to use the [Kernel][GPL] msm_hsic_host wakelock fix (Now with WiFi notification fix! because in my room I'm connected to a different router than the one in the main part of the house & I get no wifi with any ROM apart from that one :/

I'd love a version with the wakelock/wifi notification fix or whatever is in that rom what fixes my wifi issue in this ROM.
[Nexus 4 Original Android Development] johann2204:
I have created all these color profiles with francos App. Maybe a bug?

btw all color profils work without crash francos app or something else
[Nexus 4 Original Android Development] hoangtungst:
I have micro stutter in the app drawer when scrolling last page of app to left
[Nexus 4 Original Android Development] SneakyGuyDavid:
phone wont light back up after i start a call , anyone else having this problem ? using franco r118 and cyanogenmod 10.1 nightly from today 4/5/13

EDIT: its a problem i've had with previous versions of cyanogenmod
[Nexus 4 Original Android Development] fkrone:
Got kernel panic. Here is the log: http://pastie.org/private/imxbrr883gh08ut92jajuq

Phone got hot at back and had 2 unexpected reboots.

Happy fixing :beer:
[Nexus 4 Original Android Development] franciscofranco:
Interesting. Thanks.
[Nexus 4 Original Android Development] walkingmike:
+1

---------- Post added at 02:28 AM ---------- Previous post was at 02:23 AM ----------

Yes the argument comparing anandtech and real world usage is flawed.

Stock kernel I get 2-3 hours SOT.

Franco I get 4++ SOT.

---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------

Yes the argument comparing anandtech and real world usage is flawed.

Stock kernel I get 2-3 hours SOT.

Franco I get 4++ SOT.

---------- Post added at 02:29 AM ---------- Previous post was at 02:28 AM ----------

Yes the argument comparing anandtech and real world usage is flawed.

Stock kernel I get 2-3 hours SOT.

Franco I get 4++ SOT.

---------- Post added at 02:30 AM ---------- Previous post was at 02:29 AM ----------

Yes the argument comparing anandtech and real world usage is flawed.

Stock kernel I get 2-3 hours SOT.

Franco I get 4++ SOT.
[Nexus 4 Original Android Development] mammenj:
Appreciate if anyone can post the md5 of r118.

And can this be flashed on paranoid android?
[Nexus 4 Original Android Development] Savant:
It can be flashed on paranoid and just auto flash it from his app or download the IMG and push through trickster.
[Nexus 4 Original Android Development] scream4cheese:
It can be flashed virtually on any N4 rom.
[Nexus 4 Original Android Development] Savant:
You forgot to add that it can speed up any ROM and it gives you freedom from a wall charger. Franco magic is always a good thing.
[Nexus 4 Original Android Development] Shano56:
So much off topic! When will it end D:
[Nexus 4 Original Android Development] franciscofranco:
Its /sys/class/misc/mako_hotplug_control/suspend_frequency
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
yup yup thanks! I think when in doubt I try to refer to CrimsonSmear's init.d script. I just kept searching the wrong stuff in this forum. I thought it would have "screen" in the command... whoops :D
[Nexus 4 Original Android Development] franciscofranco:
Don't worry. I have to ask some Super Mod to give me the second post so that I can add all those sysfs paths.
[Nexus 4 Original Android Development] mammenj:
Just bought the app, but the free app fc'd on me.
[Nexus 4 Original Android Development] vickpick:
118 is pretty nice. Def. Better than 111. :D
[Nexus 4 Original Android Development] franciscofranco:
Force closed what? I just tried, no FC.
[Nexus 4 Original Android Development] mammenj:
When I chose auto flash it fc'd. Also sent a report.
[Nexus 4 Original Android Development] :
Hey, what theme is it if you don't mind?
[Nexus 4 Original Android Development] joshnichols189:
That theme is PCB Blue.
[Nexus 4 Original Android Development] franciscofranco:
Thanks I know what it is. Will change it later today after work, can't do much until I'm home today.
[Nexus 4 Original Android Development] AnthonyAldrete:
Lol I messed that whole sentence up. I meant if I can get some info explaining this feature a little better. I want to know what both really mean please bare with me lol
[Nexus 4 Original Android Development] Nebucatnetzer:
I had a SOD.

Rom: SlimBean unofficial Beta

Kernel v. 17.

Last kmsg:

http://db.tt/XOfr8ACH
[Nexus 4 Original Android Development] franciscofranco:
Your log showed this:

No errors detected

Boot info:

Last boot reason: reboot

What were you doing when the SoD happened?
[Nexus 4 Original Android Development] Nebucatnetzer:
Hm strange. Maybe it's because of the app I'm using (bootlog uptime).

I didn't use the phone. I was having it in my pocket and wanted to check the time but it just showed a black screen.

I'll try next time by hand if it happens again.

Edit: stupid auto correction.