yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] undercover:
I know, nixing is very good for N4! :thumbup::p
[Nexus 4 Original Android Development] zimphishmonger:
Good news and bad news...

Bad news....Touch screen was responsive for the first boot. Upon reboot, it was unresponsive. Unable to unlock, only I can do is force reboot.

GOOD News!

I was finally able to pull some logs. REALLY hoping this helps

logcat : http://pastebin.com/6rsyJfqC

dmesg : http://pastebin.com/jyj6n9iZ
[Nexus 4 Original Android Development] fnf:
@faux123: Can you please modify touch_boost() in hardware/qcom/power/power.c so it doesn't log error messages for every touch event when mpdecision is turned off?. Or perhaps avoid calling touch_boost() altogether in power_hint()?.

I want to try intellidemand but flooding the log is undesirable for me and I'm afraid it may have an adverse effect on battery life.
[Nexus 4 Original Android Development] faux123:
you error is like extremely improbable or impossible!!! :(

Because:

1493.<6>[ 330.696047] [Touch] WARN: (s2w)Interrupt pin is low - next_work: 0, try_count: 0]

1494.<4>[ 330.696261] touch core: (s2w)force safety reset!

1495.<4>[ 330.696596] [Touch D]touch disable

WTF... where's the touch enable part??????? (you should have a log like "[Touch D]touch enable" but it's completely missing!!!

1501.<4>[ 331.133129] touch core: (s2w)force IC init!

Here's the Code:

/* Interrupt pin check after IC init - avoid Touch lockup */
if (ts->pdata->role->operation_mode == INTERRUPT_MODE) {
int_pin = gpio_get_value(ts->pdata->int_pin);
next_work = atomic_read(&ts->next_work);

if (unlikely(int_pin != 1 && next_work <= 0)) {
[COLOR="blue"]	TOUCH_INFO_MSG("WARN: (s2w)Interrupt pin is low"
" - next_work: %d, try_count: %d]\n",
next_work, ts->ic_init_err_cnt);
pr_warn("touch core: (s2w)force safety reset!\n");
[/COLOR]	[COLOR="red"][B]safety_reset(ts);[/B][/COLOR]
/* safety_reset
*
[COLOR="Blue"] * 1. disable irq/timer.
* 2. turn off the power.
[/COLOR][COLOR="red"] * 3. turn on the power.
[/COLOR] * 4. sleep (booting_delay)ms, usually 400ms(synaptics).
* 5. enable irq/timer.
*
* After 'safety_reset', we should call 'touch_init'.
*/
[COLOR="blue"]pr_warn("touch core: (s2w)force IC init!\n");
[/COLOR]	[COLOR="blue"]touch_ic_init(ts);
[/COLOR]	}
}

It's like safety_reset just literally DIED in the middle of its function call :( That's quite amazing and odd at the same time :(
[Nexus 4 Original Android Development] meangreenie:
having a problem with 'touch (formerly pingchat)'

If you leave the programme for 5 minutes or let the phone sleep it loses ability to recieve messages... maybe something to do with the wake lock fix ? it was fine before.

anyone having similar problems with other msg programmes ?
[Nexus 4 Original Android Development] gknnn':
Since beta 5 but He dont listen.. So i dont use the New betas.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Ace42:
What are you talking about? :confused:
[Nexus 4 Original Android Development] wolfboy1984:
I've just looked at your 5 previous posts to see what you are on about but saw nothing but vague posts.

Your setup and screenshot on beta 5 has 8hrs20 screentime! If it ain't broke don't fix it my friend.

I'm still dreaming of > 6hrs... I hope it happens for me soon.
[Nexus 4 Original Android Development] raycaster3:
Oh yes! First time since s2w that I didn't boot to an unresponsive screen! I don't have any desire to even try another kernel.

DARKSIDE
[Nexus 4 Original Android Development] jassycliq:
Faux, I sent you a tweet yesterday with the same exact error. It was a pastebin link. I can post here also if it'll help any, looked like same error though.
[Nexus 4 Original Android Development] expl0it4:
Just happened to me on the latest beta.
[Nexus 4 Original Android Development] Ace42:
Anyone know what's in beta 003b8?
[Nexus 4 Original Android Development] :
"Beta 8 is out. Added a minor fix for those still experiencing complete lock up with touchscreens when using Sweep2wake features."

It was one page back........

Faux, I am still experiencing total unresponsiveness at boot from beta 8 with s2w enabled... happened two reboots in a row.
[Nexus 4 Original Android Development] faux123:
I'm outside right now. I will write my own reset code to reset the lock up condition.
[Nexus 4 Original Android Development] wera750:
Wow! Loving this!

It does seem Wi-Fi slows or stops during deep sleep though. I notice my talk messages not arriving until I wake the phone.
[Nexus 4 Original Android Development] leventccc:
7H of screen time and %50? Are you setting sleep timer to off and wait at launcher for 7h or is there something that I do wrong with my n4?
[Nexus 4 Original Android Development] wera750:
I didn't have 7 hours screen on lol
[Nexus 4 Original Android Development] jarjar124:
ur screen shot says so

edit: nvm
[Nexus 4 Original Android Development] Ace42:
That's a 2. ;)
[Nexus 4 Original Android Development] meangreenie:
I'm not sure that it is wifi going off, i have the same trouble with my 'touch' messenger but gmail works fine... shrugs, i think it's something to do with the wakelock fix, because i noticed the same behaviour on another kernel i tried yesterday.

it's always the same.. fix something/break something else lol
[Nexus 4 Original Android Development] Thorsten_de:
Hi!

Same with my phone too!

After a second reboot the touchscreen didn't work, only reflash an previous Betakernel solve it.

Now I'm back to the faux non beta kernel 002 and all works fine.

Thorsten.
[Nexus 4 Original Android Development] m7ia:
Quick question: does this kernel include a CIFS module? Thanks,
[Nexus 4 Original Android Development] zimphishmonger:
Not sure how to explain, was just lucky enough to grab the log.this is a fresh install of aokp followed by your kernel, controlled by your app.

I've been jumping back and forth between 2m and the newest beta to test this issue. Using bricked on one n4, and yours in the other atm to test s2w. Let me know if I can provide anything more to help.

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
It seems you can consistently reproduce this issue with your phone/setup. It will be handy if I can get you on gtalk so you can give me faster feedback than forum postings. I can't reproduce this bug matter what I tried.
[Nexus 4 Original Android Development] quierotacobell:
Beta 7 really good so far. Cfx Sr1, 918mhz, -150mv UV, Eco snake and intelli.
[Nexus 4 Original Android Development] bongostl:
Quick question for faux...if my voltage at 702 is the same as it is at 384, is there any reason not to make 702 my minimum cpu speed?

Thames!
[Nexus 4 Original Android Development] jacklebott:
Still uses more energy at a higher frequency, even at the same voltage
[Nexus 4 Original Android Development] wera750:
Still going.... :D

No eco mode, intelli, fiops, uv -100, s2w disabled.
[Nexus 4 Original Android Development] faux123:
Beta 9 is here:

This is for those who EXPERIENCED COMPLETE touch screen lock up issues (I tried and tried and CAN NEVER reproduce this on my own! :( It seems there are more than 1 type of touchscreen out there :( )

http://faux.androidro.ms/mako/beta/mako-jb-kernel-003b09.zip
[Nexus 4 Original Android Development] bongostl:
Why would this be true?
[Nexus 4 Original Android Development] faux123:
with @ same voltage, higher frequency will use more current than lower frequency because of switching frequency and more "current" leaks at higher frequencies than lower frequencies.

As long as you don't have a rogue background app / service running. Higher min freq is not a big deal because as soon as the tasks at hand are completed, the cpu should go into deep sleep and so the min freq is irrelevant.

However if you have a background app/service is running all the time, idling @ higher min will drain more quickly than lower min even @ same voltage value.
[Nexus 4 Original Android Development] wera750:
Does this only have s2w changes?
[Nexus 4 Original Android Development] faux123:
It has ONLY s2w changes to fix/narrow down the lock up issue. This should fix it but I am not sure until those who can reproduce this report back to me :(
[Nexus 4 Original Android Development] wera750:
Ok, beta 7 is rocking for me! Awesome work!
[Nexus 4 Original Android Development] zimphishmonger:
Thanks, happy New year! Testing now on the known phone with issues

Sent from my Nexus 4
[Nexus 4 Original Android Development] raycaster3:
I haven't got lock up for two betas in a row. Before that I got em on every new flash(of the kernel builds in question) Looking good here.

DARKSIDE
[Nexus 4 Original Android Development] faux123:
I have some thermald fixes queued up... but I won't release them until the current issue is fixed with s2w lockup :p So hopefully this issue is resolved so we can move forward :D
[Nexus 4 Original Android Development] Ash88:
I can consistently reproduce.. Happens after a reboot if I do not touch the screen right away. If I let the screen go off w/o touching it it is non-responsive when I turn it back on. If I touch it right away it does not freeze up.

Hope that makes sense...
[Nexus 4 Original Android Development] faux123:
then download http://faux.androidro.ms/mako/beta/mako-jb-kernel-003b09.zip and see if it still lock up or not! I CANNOT reproduce this problem AT ALL with my N4

also grab me a dmesg log if you can.
[Nexus 4 Original Android Development] Ash88:
I'm on 003b09. How do it grab a dress log? :) I can Google it..
[Nexus 4 Original Android Development] nbeebe24:
+1 tried this just to see if it's the same on my device, and it is. This is on the latest beta.
[Nexus 4 Original Android Development] Ash88:
I emailed the log file to your gmail account. Let me know if you need more.

And thanks for the kernel!
[Nexus 4 Original Android Development] D3m0x:
First than nothing, sorry for my bad english pals!

Stop talking sh*t about disgrace of the other people, only when you live that situation you can talk about it.

In the case of this mate, he OC his N4 and run a benchmark.

I had the Red Light issue too and this its not funny, and cant be considered a "noob experience" have some respect and be happy that this problem don't happened to you.

In my case, I don't OC the device, I UNDERCLOCK the goddamit SoC and also do an undervolt but the more stupid part is, when I configure all the stuff in the kernel, UC, UV, Downgrade the GPU, change the Screen settings, all that sh*t, when I finished all, my phone was STABLE for at least 1 day, and yesterday I plug in to ac charger while im taking a shower, when i finish i noticed that N4 was charging so slow, but that night was new year eve, so i just charged the n4 till 30% and when I was in gf house my phone was discharging incredible fast and also getting overheat so i decide to plug again to ac charger but still charging so slow and the overheating continues, then I get in Recovery mode to wipe everything and install the ROM again, I did it, but problem SITLL THERE, AFER WIPE EVERYTHIN! Then, my n4 just got totally discharged because I had to go out and celebrate, and when I come back to my house, when I plug the N4 in AC or USB , the red led appears, but the device dont turn on, no matter what I do...

Bro, its not funny when that sh*t appears from nothing, and its even worst when you came here to ask for some help and people like you just talk some sh*t about it. I pretty sad about it, I got my nexus 4 since 13/nov. I dont going to cry now, I will contact Google to see what can I do, and the biggest problem for me, I live out of USA so... it will be very complicated to RMA, if there is nothing to do, buy a new one. But remember, dont joke with this problems, you never know when that can happend to you, dont talk like you are the boss or something. b*tch.

Other though:

ROM: Xylon

Kernel: Faux last beta relase for this date (12/31/12)

-Underclock: min 384 mhz - 1.0ghz max

-Undervolt: 137mv

-GPU downgraded to 200mhz

-SnakeCharmer ON

-EcoMode ON

My N4 status:
[Nexus 4 Original Android Development] faux123:
I didn't see your email... why not post it here?
[Nexus 4 Original Android Development] Ash88:
Couldn't find the attached option from the app. Should be attached now.
[Nexus 4 Original Android Development] faux123:
there are NO touch driver errors at all in your log? Did it lock up or not?

you need to let it lock up, then capture a dmesg log via adb (since the screen is locked up you would have no other choice)
[Nexus 4 Original Android Development] zimphishmonger:
Beta9 has resolved this issue for me (knock on wood) :D. Been on it a few hours, havent noticed any issues w touch screen (yet). Will pull a log if anything happens as I know ur fixing this issue "blind".

EDIT Blind as in he cant reproduce it, not that he doesnt have the device
[Nexus 4 Original Android Development] 3bs11:
Faux doesn't have a Nexus 4?
[Nexus 4 Original Android Development] faux123:
blind as I can't reproduce this bug on my N4 no matter what :(
[Nexus 4 Original Android Development] Jur1nator:
Why not already work on the thermal stuff?

Isn't showp looking into a s2w recode and bugfix anyway, wich you could implement?
[Nexus 4 Original Android Development] faux123:
because this problem will affect the new s2w code base as well.. this is problem that needed to be solved regardless.

Didn't you read my post earlier? I have thermald stuff queued up already.. I didn't want to release it until this stupid s2w issue was resolved.

Maybe I will release my thermal stuff tonight... if I don't see anymore complains on s2w lock ups!
[Nexus 4 Original Android Development] Jur1nator:
Yes i read the earlier post, like every other post in this thread, but i didn't know that you meant completely done when saying queued up :)

That is even better :D

And also did not know the lock ups would affect showps recode.. I thought that was his whole purpose of the recode

But thanks for the clarification

Btw.. No lockups for me since flashing b3.09
[Nexus 4 Original Android Development] Ash88:
Ok, here's the log pulled while the screen was locked up.
[Nexus 4 Original Android Development] faux123:
You sure your screen is locked up? I saw my updated reset code successfully reinitialize the touch driver in the log :(
[Nexus 4 Original Android Development] 0.0:
Releasing thermal stuff would be awesome! I hope the lock ups stop for people. I want that thermal stuff! :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] wera750:
Guess I'll finally plug it in now :D:D:D

Awesome work faux
[Nexus 4 Original Android Development] Gustave17:
Hi,

I have had this issue 2 days ago.

For getting back my N4 I just plug it to pc via usb and don't touch anything for 5mins.

It should bootloop with battery icon and red light ...

Then, just press Vol- until entering in bootloader...

By miracle I just had to select recovery then reboot device...

Let it charge full with AC for 3h

Envoyé depuis JB-CMX by Bruce sur mon HTC Sensation avec XDA premium
[Nexus 4 Original Android Development] MiG123:
anyone else has encountered massive lag and redraws in the recents menu with the latest kernel? switched to reset kernel and issue seemed to be resolved, suspect has to do with some setting in fauxclock.
[Nexus 4 Original Android Development] basshamster:
No problems here...
[Nexus 4 Original Android Development] t0ph0id:
What are the standard colour settings?

I accidently changed them and they seem to have stuck, even though I don't have set on boot on and have done a reboot.
[Nexus 4 Original Android Development] Jur1nator:
Standard is 255 on all of them and 0 on the gamma settings
[Nexus 4 Original Android Development] fnf:
I'm afraid one of the recent patches for the HSIC wake lock or 3G battery saving have caused problems with data connectivity. Using 3 (UK) I have speed of 18Mb/2Mb U/L. But from kernels beta 5 onwards (tried beta 9) the phone struggles to download at more than 100 KBps with frequent interruptions. Can anyone confirm?.
[Nexus 4 Original Android Development] Hereisphilly:
Ah so its not just me imagining things. I'm on tmobile UK and mine struggles with maintaining a connection. Not noticed an impact on speed, but then again I'm often on WiFi

Going in and out of aeroplane mode seems to sort the immediate problem out until it drops off again.

Faux, have you experienced this/do you need any logs? And if so which ones?
[Nexus 4 Original Android Development] nateysmith:
I am on beta 3 v8 and I was wondering if there is anything special I need to do to enable to sweep2wake. I am using AOKP nightlies by Roman.
[Nexus 4 Original Android Development] undercover:
Same on Harsh kernel. Aeroplane mode doesn't fix it though for me, quick toggle of data off/on does. I seem to get that when exiting wifi range and phone switches to data.
[Nexus 4 Original Android Development] Ash88:
Removed
[Nexus 4 Original Android Development] Harsh:
You both have different things. Philly have 3g problem in speed and connection, while undercover you have switching from wifi to 3g problem.

Undercover do you experience slower speeds on 3g too? For me I am on Germany o2 which states that it provide upto 7.2 mbps never upto those speeds, its always floating around 4.7 to 5.3. Not just on nexus 4, its same speeds on iphone 4s and Optimus 2x too.
[Nexus 4 Original Android Development] Ash88:
Yes, it is locked up... I cannot do anything except hold down power to reboot. I turned the screen on and off several times trying the touch each time with no success.
[Nexus 4 Original Android Development] undercover:
I have a feeling it's a similar issue. I'll compare speeds to my wife's s3,which was identical before.
[Nexus 4 Original Android Development] Hereisphilly:
Trying to recreate the problem, i think my issue is more like undercover's, as i didnt notice any speed problems before, only connectivity.

When i leave my house and go out of range of the wifi (but wifi is still enabled), mobile data doesn't allow any data through, until i cycle aeroplane mode on/off.

When i arrive at work, the phone hops back onto work wifi, but if i turn wifi manually off, mobile data still doesnt work until i cycle aeroplane mode on/off
[Nexus 4 Original Android Development] Harsh:
I just checked walking out of WiFi range, my mobile data got working just fine. No problems at all. Typing this on mobile data out of Wi-Fi range

Edit1: editing this again on WiFi l. Auto connect as soon as I am back in range

Sent from my Nexus 4
[Nexus 4 Original Android Development] t0ph0id:
I'm on latest Faux kernel also on Three UK network and not experiencing this problem at all, auto connect in and out of my home wifi is also working fine, triggering back on the data as soon as I leave the area.

Currently getting 23mbps down on data at work.
[Nexus 4 Original Android Development] undercover:
Just tested some more. It's intermittent. Just went to work and data was fine. Most of the time it struggles though. Run speed test alongside wife's s3 and mine was considerably worse and acted weird.
[Nexus 4 Original Android Development] abz54:
Same here its very intermittent speeds can go from a couple of mb to 10+ in the same room never had this before the 3g battery saving updates.
[Nexus 4 Original Android Development] :
Im getting a constant buzzing noise in my earpiece, that only gets louder as I get on a call.... like a clicking sound.... anyone get similar symptoms?
[Nexus 4 Original Android Development] drdrewdown:
stop posting the same thing in multiple threads. it's a known hardware issue. google it
[Nexus 4 Original Android Development] Redmed427:
Forgive me if its been said in the last few pages but what was added/changed in 3b09?

Sent from my Nexus 4
[Nexus 4 Original Android Development] drdrewdown:
only tryin to fix unresponsive touch screens for a handful of people.
[Nexus 4 Original Android Development] Zanr Zij:
I still got unresponsive touch problem with beta 9. I have to flash other kernel and flash back beta 9 to fix it.
[Nexus 4 Original Android Development] Redmed427:
Ok cool. I get the unresponsive touch but it doesn't really bother me. Staying at 07 for a while

Sent from my Nexus 4
[Nexus 4 Original Android Development] superleeds27:
Unpacked Nexus 4.

Unlocked, Rooted, CM10 + Faux Kernel. Now to find some settings!
[Nexus 4 Original Android Development] zimphishmonger:
If you have the issue, it makes the phone unusable. When they say unresponsive, u literally cannot do anything. U can use power and volume keys, thats all. Not that its not sensitive enough,

For what its worth, Ive not had any touch screen lock ups since I flashed beta9. Knock on wood, but the other times, the issue was very easy to reproduce and occurred immediately most of the time.

Pull logs guys :) its the only way we'll get this issue fixed (if ur still even having it)
[Nexus 4 Original Android Development] housry23:
That is not a problem with the kernel. It is a problem with the phone. Call Google support and RMA it if it's really bad. I can hear it on mine, but only if I'm listening for it. It's not bad enough for me to try to get a replacement for.
[Nexus 4 Original Android Development] Redmed427:
The phone isn't unusable, it just needs a reboot, in my case at least. Seeing as I rarely reboot my phone it isn't really an issue for me.
[Nexus 4 Original Android Development] superleeds27:
Im having a few issues with the App and this Kernel.

Doesn't seem to be keeping settings on reboot, even though I have it to set on boot.

Some settings stick, some don't, its strange!

CM10. Latest Nightly
[Nexus 4 Original Android Development] faux123:
superuser -> superSU == done!
[Nexus 4 Original Android Development] superleeds27:
imusing superuser or do you mean use Supersu?
[Nexus 4 Original Android Development] rayford85:
Yes.....
[Nexus 4 Original Android Development] zimphishmonger:
Hmm, thats interesting..Id pull a log and see whats going on. That sound slightly different from the error I was getting.
[Nexus 4 Original Android Development] lbtc777:
I was having similar issues even with SuperSU. I then cleared data on Faux app, booted into recovery, wiped cache and dalvik, flashed ROM (did not wipe data), flashed gapps, flashed faux kernel, and then rebooted.

Since then all settings stick after reboot except for sweep2Awake. For some reason s2w wont stick at all when I enable it on app. What I mean is that I am able to enable it in the Faux app, but as soon as I exit the app it won't work anymore. I have to open terminal and run the following for it to stick.

echo 1 > /sys/android_touch/sweep2wake

However once I reboot s2w is disabled again :( . All other settings do apply on boot as selected on faux app.

I've been having this issue on all beta kernels since s2w was implemented.

Xylon 14 beta 2

Faux kernel 3 beta 9

SuperSu

TWRP recovery

Any suggestions?
[Nexus 4 Original Android Development] faux123:
weird... it works with fauxclock app.. are you running the latest version?
[Nexus 4 Original Android Development] lbtc777:
I believe so, running version 0.9.49.
[Nexus 4 Original Android Development] Locksmith81:
Anyone's auto rotate broke?
[Nexus 4 Original Android Development] jacklebott:
Mine's good. I don't think it has anything to do with the kernel though
[Nexus 4 Original Android Development] Locksmith81:
Just troubleshooting.. Process of elimination
[Nexus 4 Original Android Development] Reatret:
This is what I got on my 3rd cycle with a little bit of gaming ~12 hours and ~3 and a half screen on :):):):)
[Nexus 4 Original Android Development] Jur1nator:
Faux, what do you think about the whole cpu binning uv tables.. Worth implementing?