yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Stryder5:
How is your reception? I'm assuming you get some great reception.
[Nexus 4 Original Android Development] Reatret:
Do tell how :)
[Nexus 4 Original Android Development] expl0it4:
I do I get full 4G bars.
[Nexus 4 Original Android Development] MiG123:
quad might be more efficient in a sense as more cores working on a task would allow it to be finished faster, thereby reducing cpu on/usage time and thus energy consumption.

dual makes up for the lack in efficiency with less overall package power draw.Therefore, both modes might end up displaying very similar power consumption profiles
[Nexus 4 Original Android Development] faux123:
I finally experienced a complete lockup with touch screen :victory: :victory: :victory:

Got an interesting log from it as well... :fingers-crossed: :fingers-crossed: :fingers-crossed:
[Nexus 4 Original Android Development] Reatret:
Yesterday I got 17hrs but today I only got 10? :s and yesterday I gamed but today I did not wth?
[Nexus 4 Original Android Development] zimphishmonger:
haha bout time :good:
[Nexus 4 Original Android Development] aSquard:
Abut the screenshot earIier, for shiggles, I just decided to run with eco off today (though I understand that eco on gives better battery). I get crappy signal at work (the screen shot earlier) so I only had close to 2 hrs screen on time. As I'm looking on at my phone now, 10% battery remaining 2hrs 30mins screen on time - If eco mode is on, I'm certain I'd have more battery life left. I was just curious today :silly:

Looking forward to the next beta :good:
[Nexus 4 Original Android Development] SIGUEL:
Why is always donwclocking to 1.13Ghz when my max is set to 1.35Ghz?

Sent from my Nexus 4
[Nexus 4 Original Android Development] 0.0:
mine is the opposite. i have it at 1.2GHz, but it keeps going back up to 1.5GHz :confused:
[Nexus 4 Original Android Development] faux123:
read FAQ on 4th post. Intellidemand will auto underclock under constant load for > 3 minutes.
[Nexus 4 Original Android Development] faux123:
make sure you have snake charmer enabled.
[Nexus 4 Original Android Development] 0.0:
since intelldemand does this, i assume if i want to play games, i should switch to interactive or a similar governor?

---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------

i do have it on, but it still spiked up. right now, it is behaving, so i will keep an eye on it
[Nexus 4 Original Android Development] faux123:
yeah, interactive or ondemand. Intellidemand isn't really made for games, it's for general purpose overall battery / performance balance. For best gaming performance, I would use interactive.
[Nexus 4 Original Android Development] faux123:
Kernel 003 is official!

read here for complete details:

https://plus.google.com/u/0/109078966818501160423/posts/Zp7FD4q3afd

Kernel 004 Beta 1 is released as well. 003 mainline DOES NOT have any wakelock fixes. all of them have been moved to 004 Beta 1.
[Nexus 4 Original Android Development] 3bs11:
Thanks for all the work faux! Ran out of my 8 thanks for the day :p

Is that the hsic wakelock causing excessive battery drain while on data connection?

Edit: sorry just read the G+ post and noticed that's a yes. I guess it's best it stays in beta since so many people have been having issue with their data connection on the newer betas of 03.
[Nexus 4 Original Android Development] jacklebott:
For me, Intellidemand underclocks when under stress for a much shorter time than 3 minutes, and doesn't go back up to the former max clock
[Nexus 4 Original Android Development] faux123:
it does for me.. that's weird. I just played battlecats (<== really stupid graphics yet addictive game) and id underclocked it, then when I stopped playing it went back to max for me. Max being the LMF value under intellidemend governor panel in fauxclock.
[Nexus 4 Original Android Development] jacklebott:
Speaking of lmf_max_active_freq, any idea why it won't set by script any more (last few betas, I think v3b7 is when it started)? Your app sets it correctly though
[Nexus 4 Original Android Development] 0.0:
the faux app did it again...or the kernel did. i had it at 1.2GHz, but it ended up going to 1.5GHz when i checked :confused:
[Nexus 4 Original Android Development] faux123:
it could be a display issue. Do this, set to any cpu freq of your choice, then enable "set on boot", reboot your device and use CPU Spy, you will see that the CPU frequencies ABOVE snakecharmer max aren't used.
[Nexus 4 Original Android Development] qpqpqp:
I recently downloaded the kernel 002 from faux dont' know wy but i'm stuck on the "Google" boot screen. I'm on stock ROM and came from franco kernel. Any idea how i can get out of this?
[Nexus 4 Original Android Development] 3bs11:
Try flashing you the reset kernel in the OP then flash faux's kernel.

Edit: here it is http://faux.androidro.ms/mako/mako_421_reset_kernel.zip
[Nexus 4 Original Android Development] qpqpqp:
how do i transfer the file into teh phone when it can't get past the booting screen?
[Nexus 4 Original Android Development] Michealtbh:
Read OP
[Nexus 4 Original Android Development] trismegistos:
Boot in recovery. Then do from your pc: ad before push filename /sdcard/

The file is on the root of your sdcard

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Michealtbh:
Can someone give me the md5 sum for 4b01? Thanks.
[Nexus 4 Original Android Development] 0.0:
alright, i'll test it out once more. when i see the freq go to 1.5GHz in the app, i will check cpu spy to determine if it's a display problem
[Nexus 4 Original Android Development] mundixx:
Go to recovery. Then you need to flash the reset kernel found in the first post.
[Nexus 4 Original Android Development] qpqpqp:
Can you be more specifics. I"m kind of a noob.
[Nexus 4 Original Android Development] Der_Schubi:
What recovery system do you have? Clockwork, TWRP?

Gesendet mit Tapatalk 2
[Nexus 4 Original Android Development] j3di:
If you still have the Franco kernel zip file on your phone do this:

Hold power button (>3 sec) and release once it starts to reboot, then press vol down as it reboots - you'll be presented with 3 options, using vol key up/down select 'Recovery'.

Wipe cache, then in advanced wipe Dalvik.

Reflash the Franco kernel and reboot.

You can now download and flash the reset kernel from Faux before flashing the required faux kernel of your choice.
[Nexus 4 Original Android Development] qpqpqp:
Thank you very much for everyone's help. After much work fiddling around I've used mskip's toolkit to attempt to push the files onto the phones during that proccess i selection the option to perform an insecure boot and managed to boot back into android where i download the file and flashed it. Now everything is working again.
[Nexus 4 Original Android Development] Zanr Zij:
Open it by winrar, extract img file and flash it after put your phone in bootloader mode

Sent from my GT-N7100
[Nexus 4 Original Android Development] ftarules:
a90c39734cb0be305d31edd06fb56655
[Nexus 4 Original Android Development] MrMagic:
I found an app called Pimp My Rom in the Play Store.

It has an option to lock an app into memory. I'm testing it at the moment to see if it will keep Faux' kernel utility in memory and thus make my color and gamma settings stick.
[Nexus 4 Original Android Development] remydlc:
Hi Paul,

I have a lockscreen issue now with 004b1, which i had with one of the 003betas, maybe 8 and 9, i didnt have it with 003b11. Is that when i slide to unlock the phone locks up, it freezes. I think im going to flash 003M if a reboot doesnt work it out and will report back to this same post.

Thanks for all you do and im gonna send something your way later on.

PS: im pretty sure you know about this, Im just reporting in case you want me to test something else or provide you some logs.

update: flashed 003M and it is now fine. A reboot did not help, though before it helped. I will install 004b1, get the logcat app or ssh into my phone and gather some logs.
[Nexus 4 Original Android Development] faux123:
Always send logs :p
[Nexus 4 Original Android Development] zimphishmonger:
oh man! Was working great on 3beta11, hadnt had any touch screen issues w 3main. Tested 3m stable still morning, and on first boot....touch screen unresponsive :(:(:( Didnt have a chance to pull a log, already late for work :eek:

I thought we nailed it between b9 and b11. Ill try and recreate and pull a log tonight. Hoping the log u pulled from ur freeze will help, this issue is super annoying to troubleshoot (not sure if its more annoying for me or the women "My phone froze again! Last stable version please" lol). Think you nailed it, and bam! it shows upn again....

Anyway, hopefully will have logs later.....
[Nexus 4 Original Android Development] romeoliny:
Paul,

I must say this this latest 4b1 kernel is really proving to be amazing. On one of your earlier kernels I got 7 hours if you can remember and this is trending the same if not better thus far. And that's without eco and using ondemand with intelliplug.

I found a way around the sticking colors issue for FauxClock. I never had an issue with the settings sticking on the latest FauxClock build. In fact my gamma sticks but the color scheme goes away if not in recents. However Trickster mod does not, so when I accompany trickster mod and set the colors for remember on boot and only apply that one setting I get the colors and gamma to perm stick.

Just wanted to thank you and maybe that's also a way to look into how trickster locks the colors so FauxClock can too in the future without being held in recent.

Thanks again!

Rome
[Nexus 4 Original Android Development] ziggy34:
What I found to work best at least for me is turn off sweep2wake before flashing an updated kernel. After booting up, turn n sweep2wake if you want it and I have not had any more problems with the touch screen. Now that I have posted this, I'm sure I will have a problem.
[Nexus 4 Original Android Development] remydlc:
lol, i will try this!!! thanks for the tip. It becomes almost impossible to capture some logs unless i can ssh to the phone. Well, i can adb to it but i hate it for some reason.

edit: found some ssh server that does what i need.
[Nexus 4 Original Android Development] icemasta31:
Having an issue with the CPU and S2W settings not sticking.

I set my max at 1.3Ghz and choose Interactive. As soon as I touch anywhere on the screen the min CPU changes to 1Ghz (from 384Mhz) and sometimes with the max moving to 1.5Ghz. My S2W setting moves back to OFF as soon as I exit the FauxClock app (I managed to fix this with the S2W widget but still).

I did change from SuperUser to SuperSU.

Anyone have any ideas?
[Nexus 4 Original Android Development] Sucalakafufu:
turn off mpdecision to stop the min freq from jumping. the max freq jumping is something ive experienced as well and may be a visual glitch. though i havent been able to test it recently since ive been testing performance settings so my max is already at 1.5 :p

im not sure about the s2w. mine seem to stick but i dont use s2w most of the time
[Nexus 4 Original Android Development] remydlc:
I flashed back 004b1 and couldnt unlock my phone. tried to get logs from adb and the phone showed as being offline and connected.

Faux, do you suggest me doing anything else? I can get really dirty on this. Im a linux guru, do this for living, though android is a little bit difference, but i want to learn as i go.
[Nexus 4 Original Android Development] Thorsten_de:
Hi!

Today I was on journey and I have one touchscreen freeze with enabled S2W on beta 11.

Next freeze I will send an Log.

Thorsten.

Send with Nexus 4 CM10.1 and faux 003 beta 11 Kernel.
[Nexus 4 Original Android Development] faux123:
Android is just Java on top of Linux, but the core is still Linux so nothing new there ;)

I am trying to find showp on irc. He said a simple "release" of touch inputs should fix it which is what I've done already but it still lock up for some people. I have very specific kernel debug messages (s2w) so you should be able to find them in the dmesg logs. I have seen a few times that my reset code caught the "lock up" condition (ie, interrupt pin not cleared), then I saw my reset routine being called (confirmed by dmesg log) and my touch screen is working (so at least for my phone, that a "touch release" + re-init of IC is sufficient to unlock it), but for some reason (I've seen with other people's log) that the "touch release" and re-init of IC is NOT enough to reset the touch hardware.

Post of your findings here as well so we can all look at the debug log that I've created.
[Nexus 4 Original Android Development] Reatret:
Sorry off topic but this is killing 42% of my battery right now. Not blaming newest beta because this was happening before but just. Information :)
[Nexus 4 Original Android Development] remydlc:
I disabled S2W and flashed back 004b1 and it came back fine as Ziggy34 mentioned one page back. I will see if the syslog from previous boot up is still there. Not sure how it is handled after caches wipe.
[Nexus 4 Original Android Development] codesplice:
Logs? Screenshot of your battery usage? Hard to diagnose it without any information.
[Nexus 4 Original Android Development] codesplice:
Mediaserver is not related to the kernel. It's an android core process that sometimes gets hung up (particularly if you have any corrupt data on your "sdcard").

You can kill it with the following script (or just type the "killall" commands into your terminal emulator of choice):

#!/system/bin/sh
killall -9 android.process.media
killall -9 mediaserver

There is some discussion in this thread about perhaps setting that script to periodically kill the mediaserver process to keep it from running indefinitely.
[Nexus 4 Original Android Development] remydlc:
My dmesg. Im not sure exactly how many reboots it has, but i think it has 3, where the first one is the one with issues, then i flashed 003m, then disabled S2W and installed 004b1 which booted it fine.

https://dl.dropbox.com/u/5635442/phone.txt

actually i think there is only one boot as i only see this once, which is normal:

<5>[ 0.000000] Kernel command line: console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677 uart_console=enable lcd_maker_id=primary lge.hreset=off lge.reset=mode_reset gpt=enable lge.kcal=0|0|0|x lge.rev=rev_10 mdm_force_dump_enabled androidboot.emmc=true androidboot.serialno=00256cd8dcd2a5cc androidboot.bootloader=MAKOZ10l androidboot.baseband=mdm bootreason=reboot
[Nexus 4 Original Android Development] eep2378:
Exactly. Nothing to do with the kernel. That's a rogue app that's wakelocked. Did you use music app, gallery app before that happened?

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] Mahdi786:
I'm not 100% sure what showp meant but I added add release_all_ts_event(ts); to line 2105 check it out

I reapplied all the msm_hsic patches and I haven't had any lockups, whereas before I got locked up the first time I switched the screen off.

This is with source built bricked kernel by the way.
[Nexus 4 Original Android Development] faux123:
your log is clean, there are no sweep2wake lockups found in this.
[Nexus 4 Original Android Development] faux123:
This was done quite a while ago. It doesn't work all the time for everyone :p

https://github.com/faux123/mako/commit/03d21e19bf4983995b1fc27dfbd59a1037fe6a2d#L0L2179
[Nexus 4 Original Android Development] brar.arsh:
A bit Off Topic, but The SwiftKey Flow beta for smartphones APK is available at: http://bit.ly/skflowbeta2..

A nice Update, if interested, please download.. :D
[Nexus 4 Original Android Development] Mahdi786:
Ah Ok, I've only added release_all_ts_event(ts); to line 2105.

Your patch seems slightly different.
[Nexus 4 Original Android Development] lightningstalon:
Have you enabled Snake Charmer and disabled mpdecision?
[Nexus 4 Original Android Development] faux123:
This occurs randomly.. it's very difficult to reproduce. It only happened to me exactly 1 time and that's all. I haven't been able to reproduce it since but some users here still experience those issues with my latest mainline/beta versions so it means that the "fix" is not working for all.
[Nexus 4 Original Android Development] Mahdi786:
I'm going to try build without that line and see if it locks up, thanks
[Nexus 4 Original Android Development] Godaemon:
Hello just run antutu bench from curiosity GPU gov performance CPU same with max mix freq to 1512...!!any ideas causing this?
[Nexus 4 Original Android Development] faux123:
I don't understand what you are asking or trying to say... :angel:

Can you say again in another way?
[Nexus 4 Original Android Development] Godaemon:
Sorry faux :) I meant that the score is unusually low compared for example to the 17500-17800 stock . Is this happening cause of settings you have done to generate less heat when it reaches max load resulting to change freq from 1512? Thx for your replay keep up the good work o/
[Nexus 4 Original Android Development] whittikins:
Hey faux, couple questions.

1. Now that you've gotten rid of mpdecision for all governors, what are some differences between interactive and intellidemand at this point? Does interactive lean more towards performance and intellidemand is more for battery, mainly staying at lower frequencies more aggressively?

- do you ever implement new Google interactive patches into intellidemand, or are they too different to be applicable?

2. Any plans to lower the 800 mv limit, perhaps in a test build? 650 or 700 has been fine for me on a kernel that allows that low.

3. Great kernel! Battery life has been very good, and the gamma controls are pretty much essential for me at this point :).

Edit: I just saw your updated post #2, but still curious about any other information you could offer about it!
[Nexus 4 Original Android Development] jarjar124:
Quadrant or anything like that doesn't really matter...
[Nexus 4 Original Android Development] r4yN:
I'd say the low benchmark scores are due to the intelliplug (mp decision replacement)

On demand + intelliplug = 11000-12000

On demand + mpdecision = 17000-18000

(Antutu Benchmark scores)

But that doesn't have to be a bad thing, intelliplug just seems to be more battery friendly (by a lot), so you logically have to suffer in performance

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] faux123:
are you using intellidemand? if so, I would switch over to interactive or ondemand. Intellidemand will BENCHMARK lower than others due to its design. When you benchmark, you generate a constant load (full max, but constant regardless), and when ID governor detects that, it will automatically UNDERCLOCK your CPU... this is great for battery savings but poor for benchmark :D I would switch over to ondemand or interactive :D
[Nexus 4 Original Android Development] troffers:
Version 003 is running smoooooooooth.

Good work Faux

:laugh:
[Nexus 4 Original Android Development] Godaemon:
Maybe in evey day usage not but there is a problem if the CPU cannot perform his actual capabilities due to heat etc...that's why um asking faux to see if there's a problem with me...:)
[Nexus 4 Original Android Development] faux123:
1. intellidemand will auto-underclock under constant load. So it's definitely different from interactive (which was built for performance by Google)!

My interactive governor is in SYNC with Google's absolute latest... (Intellidemand is based on ondemand and I have been patching it with fixes and performance enhancements from ondemand governors.. check my github for all the details).

2. Yes at some point, but not high on my priority list

3. MOAR stuff coming later.. I've been swamped recently with life+work. not much time remaining for Android.
[Nexus 4 Original Android Development] Godaemon:
I tried everything from performance till interactive and ondemand...the thing is that CPU always underckocks or never goes to full load...anyway its kind off topic thank you anyway for your replies and your hard work that we all enjoy!
[Nexus 4 Original Android Development] faux123:
Then your case you were hit by thermal throttling
[Nexus 4 Original Android Development] zimphishmonger:
I'll flash 3 mainline and try to grab another log tonight, hopefully that will give you some good info. It locks up only on one of my n4s lol.

Sent from my Nexus 4
[Nexus 4 Original Android Development] FSRBIKER:
I get the lockup as well but(knock on wood) only happens after I reboot and if I don't unlock that first time, if I let the screen go black then I'm stuck. I'm on the latest mainline, mpoff, eco/snake on using intellidemand and swipe to wake.
[Nexus 4 Original Android Development] Ace42:
Beta 4 contains the patches for wakelocks, right?

Edit: found it
[Nexus 4 Original Android Development] ZeroDefined:
I have to say 004b1 is running phenomenally well for me. Settings seem to stick and the throttling doesn't seem to be much of an issue.

Battery life has been the best on this beta as well. 40% left having been discharging for 10 hrs and screen on time of 2 hrs. I don't have the greatest reception at work either, with service fluctuating from 2 to 4 bars all the time

Note: I'm running Faux's recommended settings UV'd to -150. Eco mode off b/c I notice a considerable increase in terms of overall fluidity with 4 cores running. Battery life doesn't seem to have been impacted, and seems to have gotten better actually

Solid job Faux! Keep em coming :)
[Nexus 4 Original Android Development] leventccc:
Thank you for your awesome kernel. I'm using your kernel on every device i have.

I have a question. I want to learn kernel developing, but I don't know where to start. Everyone at the internet says something different and gives a different guide and since I want to develop kernels for the android, I thought I had to ask you for your opinion. Do you know any guide that can show me how to start from simple things? I know how to compile roms for devices from sources and how to use git and I can develop java applications. Do I have to be a advanced C programmer to develop kernels? Thanks in advance.
[Nexus 4 Original Android Development] superleeds27:
First cycle with Latest Beta's and CM10.1 Nightlies.

4 hours 45mins screen time, 1 day 12 hours uptime.

1 hour 11 of that was listening to music.

Expect it to improve a little too. Only had the phone 2 days ;)
[Nexus 4 Original Android Development] whittikins:
Hmm that doesn't seem very good because you're on track for less than 4 hours screen time. I've been getting over 5 hours screen time even with his performance recommendations. Maybe it's because I'm on wifi?
[Nexus 4 Original Android Development] 0.0:
Faux, it was a display problem. Even though the app displays 1.5GHz when my max is set to 1.2, CPU spy doesn't show 1.5 being used

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
yeah... Java app always lag behind kernel, so they sometimes get out of sync unfortunately... :highfive: :victory:
[Nexus 4 Original Android Development] faux123:
Google recently updated their guide:

http://source.android.com/source/building-kernels.html

read it and follow it to build from source.

Knowing git and java will help you because all programming are similar. Knowing C is a major + on kernel development because kernel is written in C (for performance of course).
[Nexus 4 Original Android Development] 0.0:
Can the app be fixed? Setcpu, for example, doesn't seem to have this problem. Just wondering

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
yes, I just need time ;)
[Nexus 4 Original Android Development] 3bs11:
How many do you have and why :confused: :p
[Nexus 4 Original Android Development] zimphishmonger:
I have one, and the girlfriend has one = 2. They are both fast binned chips BUT one is way more sensitive to kernel changes, and happens to be the one experiencing touch screen issues \ unresponsive. My other one (ironically the one Im using) hasnt had any touch screen issues since the s2w was added the first time (beta3 i think :P)

WHY do I have more than 1? Well,. GF seeing Im two phones ahead of her, she's tech savvy, decides If I get an upgrade, she gets one....Im not gonna argue haha