yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] .A.J.:
What is generally considered a safe amount to start under volting our processors? What would definitely be too much? I've never messed with it before but am willing to give it a go. The only thing I know is to not use the set on boot option until I know what my specific phone can handle. I'll be using the faux clock app to do this. Any advice from those with experience is welcome.
[Nexus 4 Original Android Development] Craxx:
I undervold with - 50v

Today i get my nexus4 and flashed xylon15 and latest faux b4. Works great, battery settings like op. One thing... scrolling with Tapatalk stutters more than with my gnex xylon15 and purity 07.

Some advice what to change?

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Nexus 4 Original Android Development] jacklebott:
Start low. Somewhere around -100mV is generally stable medium for anyone though (assuming you're on stock voltages to begin with, and not already undervolted from a different kernel/app). Go up in small increments (12.5mV is the smallest increment) until your phone starts acting up (camera app freezing when rotated is generally a dead giveaway that you went too far), then go back up until it's perfectly stable again. Just to be safe, once you reach what appears to be the perfect bare minimum voltage, I recommend increasing it just +12.5mV higher to prevent unforeseen problems in the future.

Of course, if you want to get advanced, there are other apps/scripts that allow setting each frequency's voltage separately and that allows for much further undervolting
[Nexus 4 Original Android Development] romeoliny:
Hey Paul, (Faux)

Think you can do a r3 candidate with the new intelli-plug 1.1 update or is it already there?

Thanks

Rome
[Nexus 4 Original Android Development] Locksmith81:
It's the app itself
[Nexus 4 Original Android Development] faux123:
I won't revisit mainline releases unless it's a critical bug like s2w issues. intelli_plug 1.1 will be in 004 betas, mainline and beyond.
[Nexus 4 Original Android Development] granduke:
004b04 seems to have fixed my data drops. I have gone the whole day perfectly. Whereas the phone was barely usable with constant drops the previous two days.
[Nexus 4 Original Android Development] Zanr Zij:
Paranoid

Sent from my Nexus 4
[Nexus 4 Original Android Development] dark_ente:
Also having great battery life here

4 hours of screen on time and still has 33% battery left,

too bad I didn't make a screen shot
[Nexus 4 Original Android Development] whittikins:
The app sucks, but it is smooth on stock kernel as well as his setup on his slower phone. That means there are some settings that'll correct his stutters.

He should try using interactive to see if that helps. I really wish they would code the app better though...
[Nexus 4 Original Android Development] resynx:
Edit: never mind found it :D
[Nexus 4 Original Android Development] faux123:
Sweep2wake option worked every time. I install/uninstall many times to test it :(

To enable manually simply

echo 1 > /sys/android_touch/sweep2wake
[Nexus 4 Original Android Development] resynx:
Haha just found your old post of this exact quote right before I posted my question. Should've searched just a little harder xD

Thanks for all Faux, enjoying the kernel and colors are really popping my screen!
[Nexus 4 Original Android Development] djkinetic:
Just wanna say how much I hate the msim_hsic wakelock, removed 004b3 and installed b4 and of course the msim wakelock shot up and is now using around 16 percent over the last 5 hrs, 100-85 with minimal screen on time, its too bad the msim_hsic patches cause data loss...this is the only real problem I find with the n4 =/
[Nexus 4 Original Android Development] raycaster3:
I've been testing trickster since before it was released for mako, and exclusively with this kernel and I beg to differ. Everything sticks for me. If you're referring to the UV values they show 0 after you've lowered them then exited the app. I asked the Dev about it and though I understood at the time I don't recall why. Just gotta remember what you set it at unless you want reboots.

On another note for both 004b3&4 I've had SOD after my device was left charging for an extended period of time. If anyone else has experienced this I'll reproduce and grab appropriate logs but if not, I'll chalk it up to just one of those things that happens when you test beta software .

Thnx @faux123 for all the effort and explanations. Much appreciated.

DARKSIDE
[Nexus 4 Original Android Development] drms12:
For me too.

I charged my phone up to 100% and go to sleep. After 8 hours I lost 30% of battery.

Msm_hsic_host wake the phone for 5.5 hours, and suspend_backoff wake it for almost 3 hours.
[Nexus 4 Original Android Development] Lultima:
Battery drain it's a general problem that afflict ALL NEXUS 4, I'm wondering if google really test is phone or " we are the testers...my friends... ahahahah", i think my second opinion it's the correct, anyway a fix on next update is announced by google. This kernel is limiting my battery drain.Thanks Faux !!!
[Nexus 4 Original Android Development] jassycliq:
Sucks to be kernel devs for mako. Either deal with users complaining about data issues or battery (or lack thereof). Personally staying on b3, the newest beta wouldn't charge while using the phone. Had to turn off screen in order for it to trickle charge basically, came back to b3 and its all good. I'm happy with it honestly, if faux ends up leaving the patches I'll probably keep using it haha
[Nexus 4 Original Android Development] Michealtbh:
It's showed up again for me too (as expected) in the latest beta, and shows top of the list in bbs with 40mins of wakelock, but that only translated to losing around 6% battery overnight.
[Nexus 4 Original Android Development] antih3ro:
I also have massive Msm_hsic_host wakelock with b4. I lost 20% of battery over night , so i go back to b3.
[Nexus 4 Original Android Development] Craxx:
Thx thanx with interactive it works like in gnex :D

And yes i know that the app os very bad programed.

Is the xda app better?

Craxx;)

Send from my Nexus 4 with Tapatalk :)
[Nexus 4 Original Android Development] zimphishmonger:
Is anyone else still having the occasional touch issue? Im also noticing the same extremely sporadic issue on other kernels that fork faux's s2w. Im trying to pull a log from my most recent crash, but its so sporadic that its hard to pull when it occurs. Usually on the go. Just curious as to if anyone else has this??
[Nexus 4 Original Android Development] Michealtbh:
*Showp's s2w
[Nexus 4 Original Android Development] warfexion:
Yeah that wakelock destroyed my battery too :( back to B3 which is awesome since I don't have the data problems some others have.
[Nexus 4 Original Android Development] basshamster:
Hey faux! What about providing some presets in the misc tab for recommended battery or performance settings? It would be easier for all users to switch between them... :)
[Nexus 4 Original Android Development] Ace42:
Beta 04b004 has finally fixed my data issues. :D
[Nexus 4 Original Android Development] smoki3:
Kernel wakelock Msm_hsic_host on b4
[Nexus 4 Original Android Development] Luk_Sch:
Guys, it's very easy:

004b3: more battery, but for some users data issues

004b4: less battery, no data issues

Choose what you want to have. :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] _ice_:
Wake lock is taking up 20% of battery. Looks like it sucks better than my gf :rolleyes: other than that since no data issues on b4, I'm staying on this version. I'm cool with carrying a USB cord around :D
[Nexus 4 Original Android Development] Craxx:
Hmmm sweep2wake didn't stuck anymore?

I enabled in faux app but didn't stick. Any advice? I am on xylon15. With trickster app it stick??

Craxx;)

Send from my Nexus 4 with Tapatalk :)
[Nexus 4 Original Android Development] disq:
I had the same problem for _all_ my fauxapp settings. Switched to SuperSU, started working again.
[Nexus 4 Original Android Development] Mash87:
Faux, thank you for your amazing work! Grab a beer at my cost! 9X792724JB115181J

There is one thing I would be interested in. Would it be possible to disable charging while the phone is connected as media device?

For example I would love to disable charging while the phone is connected to my laptop for picture and music exchange.

IMO this would increase overall battery health.
[Nexus 4 Original Android Development] dispatch:
If this issue is occasionally unresponsive/twittery lockscreen upon wake up-- I did experience this with several faux betas including 4b4, but none on stock kernel. Is this your touch issue or is it different?
[Nexus 4 Original Android Development] Craxx:
I am on supersu...

Craxx;)

Send from my Nexus 4 with Tapatalk :)
[Nexus 4 Original Android Development] basshamster:
From time to time I still have data probs with 004b4. Not complete losses like before, but kind of sleeping for seconds/minutes. Could be network-related as well...
[Nexus 4 Original Android Development] zimphishmonger:
Is anyone else still having the sporadic touch screen lockups? Im noticing I still occasionally have touch screen issues on wake. I know faux saw an earlier log and didnt know why it was still occurring. . Im also noticing the exact same issue on other kernels that incorporate s2w and forked fauxs fixes for it.

Just wanted to confirm if ANYONE else is having issues similar to mine. Most ironically, I cannot reproduce the issues on Bricked.

Any advice???
[Nexus 4 Original Android Development] Jiia:
I have many problems with 004_b4 and b3. Scrolling in any app is glitchy and basic 2D games like angry birds seem to stutter every five seconds or so. FauxClock says the GPU is at full speed when nothing is happening on the screen, and when I scroll the app sideways I can see the GPU clock go down to minimum speed.

The FauxClock app is also behaving weirdly when opened. Sometimes the app just force closes when I open it and sometimes it says "CPU not recognized" and I have to manually kill and reopen the app.

I'm very unsatisfied with my purchase. Franco's kernel had no problems and the app was rock stable. FauxClock has many neat features but the app is not working very well. My ROM is AOKP mr1.
[Nexus 4 Original Android Development] trismegistos:
Believe me, what you are describing is not an faux app bug. I never has those issues and never read anything like that in the thread

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] whittikins:
Interesting. I've had none of those issues running 004b4 with aokp nightly. Must be something on your end.
[Nexus 4 Original Android Development] Jiia:
Thanks for the information. I guess there's something weird going on in my phone. I'll do a full wipe and make sure there are no conflicting apps.
[Nexus 4 Original Android Development] Jake-CT:
I can't get s2w on b4... Says "on" but nothing happening. Am I missing something?

Edit: works using S2W widget from playstore as others have mentioned...
[Nexus 4 Original Android Development] Hrithan2020:
Well as I said, I had tried putting it below 700 mv which apparently is not supported. [check and confirm; -150 mv UV]

Also , I now changed to supersu.

I also got SOD, but thought it was related to UV so reverted back. But, got huge wakelocks [suspend_bs; I think might have been related with enabling the s2w] so have removed the kernel for now. Will wait for the stable vesion to release [with s2w issues fixed] before I try it again.

@faux123,

Why are you having completely different default settings compared to the performance and battery settings you are suggesting. I understand that it might be the balanced settings, but why are the settings which you are suggesting for both perf and battery [for eg. scheduler change, and readahead change] different from default?

By nothing happening, I assume you've properly tried swiping from left end of screen to right end to try waking up the screen. [and similarly bottom right end to bottom left end to sleep]?
[Nexus 4 Original Android Development] dispatch:
Per Faux, the app will lag behind on the display sometimes, so do not always believe it. I did have the "CPU not recognized" issue and the FC-on-open a couple times with his app. I think it was an issue of not being able to acquire root (I'm using SuperSU and always have so I'm not sure why it happens). I also occasionally had an issue where entering faux app caused all 4 cpus to go to max freq until I killed (or exited) the app. Lastly, I had an occasional touchscreen issue upon device wake. I think all of these issues were after the s2w code was implemented (although mine was always turned off when possible). Stock ROM, btw.
[Nexus 4 Original Android Development] Craxx:
Didn't find the app:( please can you give me a link or the exact name:)

Craxx;)

Send from my Nexus 4 with Tapatalk :)
[Nexus 4 Original Android Development] ziggy34:
https://play.google.com/store/apps/details?id=com.reneph.s2wwidget.nexus4
[Nexus 4 Original Android Development] zimphishmonger:
FINALLY, I was able to pull a log off of 004beta4. Touchscreen worked on first boot, second boot touch screen completely locked. I know its rare issue niw, and not many other users are still having touch screen issues, but i would REALLY appreciate you taking a look to see if you see anything obvious. Unfortunately, this "bug" seems to affect all the kernels that forked s2w w faux's fixes (Bricked works fine, never a TS lockup, dumbfounds me) which kills s2w for me, my favorite feature ever :(

PASTE BIN Logcat

Second Logcat - after a reboot

Any help is much appreciated
[Nexus 4 Original Android Development] faux123:
logcat doesn't help me at all... I need dmesg logs. remember, logcat is for apps/ROM issues, dmesg logs are for kernel related issues and sweep2wake is a kernel issue :(
[Nexus 4 Original Android Development] :
Battery life is disappointing on 04b04 :/

Also experienced a data drop while wifi was on on screen sleep (wifi sleep is set to never)
[Nexus 4 Original Android Development] faux123:
Anyone having sweep2wake toggle issues.. can you check the file permission for

/sys/android_touch/sweep2wake?

it should be rwxrwxrwx or 777.... not sure why the toggle in the app doesn't work... I've uninstalled/reinstalled many times just to test this feature and it worked every time and I can't reproduce the issues...

edit: also check the value for me... it should 1 for on and 0 for off.
[Nexus 4 Original Android Development] resynx:
Mine shows up as rwxrwxrwx.
[Nexus 4 Original Android Development] Jiia:
Yep, the entire app is behaving so weirdly that I have to change kernels. I did a clean install of the latest AOKP nightly but I still have the same problems. Additionally opening the app takes a long time because it checks for permission and validation every single time it's opened. Sometimes the CPU frequency sliders move by themselves until I touch them. The "restore settings" function didn't work, I had the default settings after reboot. I don't understand why my phone is having these problems but everyone else seem to be running it just fine.
[Nexus 4 Original Android Development] faux123:
slider will move automatically because of intellidemand's design. read FAQ on the 4th post. You will need to reboot when you restore because many of the settings are only done once per boot.

The app taking a long time getting permissions is my fault. I am in the process of making it more streamline.
[Nexus 4 Original Android Development] faux123:
can you tell me the value as well.. You posted this before I edited my post :D It should be sync'ed with the toggle.
[Nexus 4 Original Android Development] DynamicRam:
if mpdesicion is on your min frequency will jump to 1.02 GHz when you touch the screen, as for the settings not sticking it doesn't happen any more on the latest version 0.9.51
[Nexus 4 Original Android Development] zimphishmonger:
My bad, will pull dmesg and report back.
[Nexus 4 Original Android Development] resynx:
It's 1. But I ran the command in terminal that you posted yesterday that made it work.
[Nexus 4 Original Android Development] faux123:
can you set it zero manually and try to set it with my app again and see if it works or not?
[Nexus 4 Original Android Development] zimphishmonger:
Been trying to pull a dmesg, but when it locks up, it doesnt allow me to pull it via adb. It states the below error. If I try and adb shell, then su, it just freezes on root@androidL/# but doesnt allow anything to be typed. Is there another way to pull that dmesg? I tried in recovery but it just pulls the RECOVERY dmesg :confused:

Error 1

E:\>adb shell "dmesg > /sdcard/dmesg.txt"
klogctl: Operation not permitted

If I keep rebooting, I will almost always get it after 2-3 reboots, so I can reliably recreate it
[Nexus 4 Original Android Development] faux123:
you need to do su first :p This is new in all jellybean... Google changed the permission requirements even for grabbing a simple dmesg log. Now you will need to have superuser privilege before you are allowed access to grab such simple log. Sometimes I don't like what Google's doing with their new "protections"
[Nexus 4 Original Android Development] zimphishmonger:
Thats an issue, it doesnt allow ANY type input after su. I GUESSING cause its waiting for the phone to respond, but thats purely a guess.

I attempted to give it adb shell su, but then its stuck after that. I really wanna get you what you need to fix this, as I seem to be the only one having the issue (at least commenting about it). Im 100% positive its not due to a dirty flash.

EDIT: DAMN! Of course, now that Im all set to diagnose....it wont freeze. I know it would be very strange, but Matrix v5 has the EXACT same error and he forked your TS fixes. I can reproduce much easier on Mv5 for whatever reason, but will that log help you at all (considering the issue is s2w based and not based on hotplugging, mpdecision etc)? I dont want to waste your time w a log from another kernel if it wont help. Only reason I suggest is it has the EXACT same issue, and it occurs just as sporadically
[Nexus 4 Original Android Development] faux123:
open terminal emulator, allow su access there first, adb shares the same request as terminal emulator. Once you allowed su access there, you can do it in adb without needing to click allow.

It's happening with all kernels with s2w enabled except on showp's own kernel.
[Nexus 4 Original Android Development] zimphishmonger:
nice! Ill give that a shot and get back to you. Only issue is when its ACTUALLY frozen, I cant do anything :P. I go "ALLOW" it while touch is working, and then try and recreate the freeze and pull a log. MANY thanks for your help! I know this issue isnt a problem w a lot of people, but SOMETHING is causing the occasional TS freeze.

Exactly, I can confirm this as I ran Bricked for several days TRYING to get it to freeze. Its limited to ur kernel, harsh, and Matrix (as far as I know)
[Nexus 4 Original Android Development] resynx:
Alright set it back to 0 and once I turned it on w/ your app again it worked!
[Nexus 4 Original Android Development] lowrider262:
black screen of death

I had a bsod today. pulled the phone outta my pocket, hit power button,and nothing. had to do a three finger reboot. running cm10.1 nightly (1-8) with 004b2 on all stock frequencies/settings. log attached
[Nexus 4 Original Android Development] lowrider262:
lol, yea I've been dirty flashing nightlies for about 3 weeks:othanks for the response
[Nexus 4 Original Android Development] MasterJam882:
Can anyone tell me why with this kernel my phone only gets 10xxx points in AnTuTu though GPU is overclocked?

All stock setting but overclocked GPU.

With stock I get around 16xxx.
[Nexus 4 Original Android Development] Stryder5:
Read the FAQs of this thread (4th post), specifically #2.
[Nexus 4 Original Android Development] zimphishmonger:
BINGO!!! Finally was able to pull a dmesg log after a touch screen freeze, Occured on boot-up after flashing the reset kernel THEN 004b4. Running AOKP Jan8th build (or Build1, also tested)

http://pastebin.com/8Krr96An

Crossing my fingers you find something useful, trying to grab a log for mathkid as well for the same issue.
[Nexus 4 Original Android Development] Hereisphilly:
I've also been flashing dirty nightlies every day for over 3 weeks...

Does anyone what is best practice in terms of how often I should do a full wipe in between daily flashes of cm night lies & this kernel in order to minimize the chances of the above happening?
[Nexus 4 Original Android Development] lowrider262:
On previous devices I used to do a full wipe every 10 days or so and never had problems for the most part. I've just been kinda lazy lately:banghead: plus I wasn't having any bugs until this happened

:
[Nexus 4 Original Android Development] MasterJam882:
this is regarding intellidemand governor but as I said I'm using stock ondemand governor. So what do u want to tell me exactly?

greetz

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Hereisphilly:
Cool, I might give it a wipe tomorrow then, definitely been at least 3 weeks since I've wiped
[Nexus 4 Original Android Development] faux123:
<6>[ 307.567678] [Touch] WARN: (s2w)Interrupt pin is low (Lockup detected) - next_work: 0, try_count: 0]

<4>[ 307.567678] touch core: (s2w)disable irqs!

<4>[ 307.567678] touch core: (s2w)release all Touch events!

<4>[ 307.567678] touch core: (s2w)enable irqs!

<4>[ 307.567709] touch core: (s2w)force IC init!

<6>[ 331.114054] [Touch] WARN: (s2w)Interrupt pin is low (Lockup detected) - next_work: 0, try_count: 0]

<4>[ 331.114237] touch core: (s2w)disable irqs!

<4>[ 331.114359] touch core: (s2w)release all Touch events!

<4>[ 331.114542] touch core: (s2w)enable irqs!

<4>[ 331.114664] touch core: (s2w)force IC init!

Looks like there were 2 lockups detected.. look at the time stamps... first and 2nd one were about ~30 seconds apart....

Did it work the first time then lock up the 2nd time?

Anyways, showp1984 has disabled his s2w on his own kernel by default and won't take any more bug reports until the 2nd version (which he said he fixed most of the issues anyways).
[Nexus 4 Original Android Development] zimphishmonger:
Sounds good, im really hoping s2w fixes this lingering issue. Strange, i dont think it worked tehn stopped working. It usually occurs right on boot, the lock screen is completely unresponsive. I can turn the screen on and off, but thats it. Could it be registering something during that period where I TRY and unlock it, but its not showing anything on screen (just detecting the touch).

Glad to hear most of the issues have been resolved. Ill wait for v2 before posting further logs \ issues regarding the touch wake lockup. \

Thanks a lot for checking out that log :) Already used all my thanks
[Nexus 4 Original Android Development] _ice_:
I have been flashing Roms since g1 days and usually unless its a total ROM change or base change I don't full wipe. For instance if 4.1.2 got updated to 4.2.2. Or something then yes. Or if I'm moving from aokp to cm, paranoid etc... Even then if I move from aokp to cm, I usually install ROM, gapp package then advanced restore /data partition.

Unless you have major issues and force closes then go back and full wipe, if you are confident you can always flash nightlies on top of what you have, or backup, full wipe, flash, restore /data. I think wiping cache and dalvik cache will always suffice.
[Nexus 4 Original Android Development] resynx:
beta5 is live!
[Nexus 4 Original Android Development] SleemLDJ:
Can't find changelogs on his G+

Swagged out of my Paranoid NeXus⁴
[Nexus 4 Original Android Development] expertzero1:
cause he didnt post it yet
[Nexus 4 Original Android Development] faux123:
Beta 5 will be a blind test for now. It will be revealed in 2 days.

what I am looking for are two things:

Battery drain + Data Loss
[Nexus 4 Original Android Development] morfic:
Not very blind now... People are now biased and it will spoil your feedback.
[Nexus 4 Original Android Development] faux123:
it's better reveal now then have it go off on some wild tangent!