yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] SleemLDJ:
Going back to R26

Swagged out of my NeXus⁴ using XDA Premium
[Nexus 4 Original Android Development] mobilehavoc:
No data drop on r27 and everything is gravy. Then again I've never had them. Anybody think its related to specific bands or carriers. I'm on at&t and never had data issues. Yet.
[Nexus 4 Original Android Development] Richieboy67:
I just installed 27. Using it totally as is right now and no problems so far with GTA or any other games. Have only had it installed for a little while. I am still using the stock rom.
[Nexus 4 Original Android Development] Bill Gamble:
Set it up as an init.d script.
[Nexus 4 Original Android Development] RohanM:
Any one facing issue of songs stutter whenever a whatsapp msg comes in ??

R184 - stock 4.3
[Nexus 4 Original Android Development] kecinzer:
I'm running my own compiled from your latest source - so it's contains doubletap_to_wake.
[Nexus 4 Original Android Development] agascon:
I think have seen that [MENTION=3750240]stratosk[/MENTION] were using the proximity sensor for changing the vibrator strengh in-call or something. I'm going to have a look in case I found something.
[Nexus 4 Original Android Development] franciscofranco:
Sysfs and module_params always revert to their default values on reboot, thats why we use init.d or apps to set values back to user preferences after the reboot -.-
[Nexus 4 Original Android Development] franciscofranco:
That would be golden! Hope he chimes in and shed me some knowledge if thats the case!!
[Nexus 4 Original Android Development] stratosk:
I do it in userspace. As far as I know there are no in-kernel drivers for sensors. Maybe I'm wrong but I couldn't find them.

I also wanted to disable touchwake during calls because the phone app turns on/off screen and interferes with touchwake functionality.
[Nexus 4 Original Android Development] Waldos:
Sorry

Source: http://xdaforums.com/showpost.php?p=45164837&postcount=2989
[Nexus 4 Original Android Development] alanhenrique:
I'm using voltage control to change the frequencies, but with your kernel shows me 1512mhz as max frequency. what i should do in this case?
[Nexus 4 Original Android Development] Bill Gamble:
That's the max for this kernel.
[Nexus 4 Original Android Development] alanhenrique:
i read, this topic again and see this...

thanks !
[Nexus 4 Original Android Development] Cantacid:
Ok been using the new touch 2 wake since a good 93% battery! And jt was mainly light usage! I dint what these drops in the graph are about, plus the phone restarted one too many time while i was on call! Seemed like a soft reboot but i dont know!

I have boot uptime ibstalled and the lastt_kmsg is attached! Dont know what the issue was but well hopefully it will help!
[Nexus 4 Original Android Development] BakaPhoenix:
Imho people that have problem with long press unlock is because swype to wake works with a minimal movement of the finger.

If I press the screen without moving the finger it stay on sleep but if i slightly move it the phone wake
[Nexus 4 Original Android Development] fozzie:
Slide to wake was removed in the last version, so it can't be that.
[Nexus 4 Original Android Development] Treatcon:
9 pages back and only 16 hours ago. A lot of good reading to find this. Thanks for your work!
[Nexus 4 Original Android Development] BakaPhoenix:
Nice, i'm still on the older one XD
[Nexus 4 Original Android Development] SevansD:
My long press wake happened on the current, or second, t2w nightly. But I love the feature and will wait patiently while the bugs get worked out.
[Nexus 4 Original Android Development] David9519:
Once your phone was shutting down because of an empty battery, you have to reactivate the doubletap feature?

Send from my Nexus 4 with**crDroid AOSP** ROM using xda-developers app
[Nexus 4 Original Android Development] Doo Doo:
yes or you could use a script so that you wouldn't have to everytime
[Nexus 4 Original Android Development] Goku80:
guys if i put high threshold to 95 is that to high? what i mean is that good for battery or performance?
[Nexus 4 Original Android Development] agascon:
Ohh, really a pity. I think combining both could have worked really well..
[Nexus 4 Original Android Development] occtec:
Guys I've been using TC for quite some time now. Reading back the last few pages I've noticed that this may not be supported by Franco kernel any longer, is this correct?
[Nexus 4 Original Android Development] pkelly517:
I haven't seen anything that indicates this.

I disabled the Franco option and re-enabled TC when I got the screen freeze.

I seriously doubt that both methods could both be enabled. However, currently, either method is valid.

Of course, as Franco makes more progress, that may change.
[Nexus 4 Original Android Development] occtec:
When you say you disabled the Franco option and re-enabled TC how did you do that? are you saying it's enabled by default in the kernel?
[Nexus 4 Original Android Development] namurt:
i would like to try switching back to interactive with r184, just to see how my battery life fares. i was wondering if i should still leave row as my default scheduler?

[MENTION=3292224]franciscofranco[/MENTION] (or anyone else in the know) should i leave my scheduler alone?

p.s. i apologize if this question is somewhat of a nuisance given the fact that you're trying to fine tune this tap to wake experiment. i'm waiting for a slightly more finished product in that regard. unfortunately, i have to use my n4 for work related purposes quite a bit, so i don't like to flash experimental stuff often. nightlies, well... i can't help myself there. :p
[Nexus 4 Original Android Development] PhantomGamers:
It's not enabled by default.
[Nexus 4 Original Android Development] ziddey:
Hmm, I'm able to wake the phone with up to 6-7 seconds between touches.

The issue is that the digitizer must be on when enabling doubletap to wake. This means the screen has to be on. Otherwise, your phone will be non-responsive. Like you've found, the fix is to disable it while the screen is off.

For those of you using Tasker, you could try using the proximity sensor for your tasks:

1. echo 1 on boot (screen MUST be on for this task)

2. proximity sensor near = echo 0 (disable doubletap to wake when in pocket)

3. proximity sensor far = echo 1 (re-enable when out of pocket)
[Nexus 4 Original Android Development] pkelly517:
It's not enabled by default, so it was disabled when I had to do the power button reboot to get the digitizer to work.

Same kernel, but I enabled TC when the phone rebooted.

Since then, Franco suggested I disable Lux. I did, and haven't seen a freeze since. I did load in the second version of 185 that Franco offered up this morning (Texas time). So, the extremely small sample I've generated is...

Version 1. Lux Running. 1 freeze.

Version 1. Lux disabled, 0 freezes for 14 hours (8 hours on qi charger)

Version 2. Lux disabled. 0 freezes for 12 hours.
[Nexus 4 Original Android Development] Mercado_Negro:
Like 90% of the time I end up adding a number when double tapping (PIN lock). I guess I'll wait for a swipe method.
[Nexus 4 Original Android Development] hern1989:
Im having a problem with the new TC with the kernel. I enabled it with the command " echo 1 > /sys/module/lge_touch_core/parameters/touch_to_wake" and when in on a call my screen turns off and starts to flicker. Im on stock 4.3 with r185. The second release. Any ideas?

Edit: it flickers when my cheek touches the screen only. Or if i touch the screen while on a call.
[Nexus 4 Original Android Development] alanwyl:
Franco I've got a suggestion, you could ignore the touches along the sides of the screen to minimize accidental touches. I carry my phone anywhere in my hands and this gets annoying sometimes.
[Nexus 4 Original Android Development] franciscofranco:
Yes, I haven't been successful in finding a way to prevent that. Need more researching and more testing, but I have a few ideas :)

Nothing I can do for now on that part, cheek touching the display counts and a touch and I cannot differentiate between a finger or a cheek.

Yes, that also went through my mind. Like ignoring 200px in top, 200px on the botton, ignore 100px on the left and 100px on the right. That would get rid of those mis touches due to device handling.
[Nexus 4 Original Android Development] Floydfire:
Also I had a problem with double tap, I plugged my charger and with doubletap on stopped to work the touch I had to reboot... I don't know if can reproduce...

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] dark_ente:
I've been using the new version for 12 hour now, didn't get any screen frozen so far, battery drop around 0,5%/hour (air plane enables overnight) which is more than proximity sensor.

Also during call the screen wake and go to sleep again every few second because my face touch the phone

For screen on during call, you should be in front of a mirror to see it clearly

For screen on during call, you should be in front of a mirror to see it clearly
[Nexus 4 Original Android Development] r00t4rd3d:
Can you code in the option to Lick to Unlock? Sometimes at work my hands are to dirty to touch stuff.
[Nexus 4 Original Android Development] int abacus:
this thread in nothing short of innovation
[Nexus 4 Original Android Development] stankyou:
IF this gets implemented for some goddamn reason and fate would make us meet, remind me not to touch your phone. Ok? :D

via xda app
[Nexus 4 Original Android Development] shubu000:
Anyone got the link to the second version with touch wake? I can't see it, might have been cleaned up by mods
[Nexus 4 Original Android Development] Mercado_Negro:
http://xdaforums.com/showthread.php?p=45930268
[Nexus 4 Original Android Development] hinirang:
wakelock that's killing my battery life

Anyone experiencing msm_hsic_host wakelock? Its been draining my battery life. 24hrs since unplugged, almost 2hrs of wakelock that is caused by msm_hsic_host.
[Nexus 4 Original Android Development] drawde40599:
=O! U might wanna at least attempt to use the search button.
[Nexus 4 Original Android Development] Bobtehblob:
Not much you can do it about it. Try use wifi as much as possible and avoid bad signal as much as you can. It's sadly just the way it is on this phone :(

Sent from my Nexus 4
[Nexus 4 Original Android Development] momomok:
Just experienced touchscreen being completely unresponsive in r185 test 2 (aka double tap to wake version)

here's the last_kmsg:

https://docs.google.com/file/d/0B_dytOv96XeWQVZxcFJLT196UVE/edit?usp=sharing

have to hard reboot to bring touchscreen back online
[Nexus 4 Original Android Development] occtec:
Just wondering is it neccessary to flash super su with this kernel? Im on PSX ROM v7.1 which has (koush) superuser...

cheers
[Nexus 4 Original Android Development] hwies:
Got also unresponsive screen with 2nd version.... hard reboot necessary.... running Stock and use the Lux screen tool.
[Nexus 4 Original Android Development] Minhlachim:
Sometimes I got this when using Touch control :silly:

-----------------

Can you add "slide to wake up"?
[Nexus 4 Original Android Development] Lebo-Wog:
I dont think you need.

If you loose root than reflash supersu, but i never lost root after the 182 version
[Nexus 4 Original Android Development] Pipusz:
Not necessary. However, Koush's Superuser caused some problems to user (not everyone of course) due to it's different implementations contrary to Chainfire's SuperSU.
[Nexus 4 Original Android Development] momomok:
****s happens all the time... :silly:

Let's hope the log contains information vital to debugging :D
[Nexus 4 Original Android Development] AhmedFaiz:
I am not able to save the n to 1 using root explorer when I try to save it showing failed to save. Keyboard is hanging sometimes.

Any workaround.

N⁴| PA3.99_RC2 (nightly) |

FRANCO touch experimental | V4A
[Nexus 4 Original Android Development] 777.300:
Short question:

Switch from Ondemand governor to the fine tuned, by Franco, Interactive governor.

What is the best I/O scheduler for a Interactive governor?

Harald

PA ROM

Franco #184 kernel
[Nexus 4 Original Android Development] Luigiesin:
I'm using deadline right now... But ROM is stock and should give you almost the same thing... I don't really notice much difference aside from a hair of more butter with deadline... Go figure. LOL
[Nexus 4 Original Android Development] Bill Gamble:
Use Terminal for a temporary solution or create an init.d script for one that survives boot.

---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------

Waiter! There's a hair my butter!
[Nexus 4 Original Android Development] AhmedFaiz:
Thanks but I moved on, will come back here when it more stable.

N⁴| PA3.99_RC2 (nightly) |

Matr1x v11 | V4A
[Nexus 4 Original Android Development] HamsterHam:
I'm confused on which version I need to run on PA. Can someone point me in the right direction? Thanks.
[Nexus 4 Original Android Development] cmajetic:
JWR but as far as I remember that is mentioned in the PA description.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] kecinzer:
[MENTION=3292224]franciscofranco[/MENTION]

Few days back I noticed, that my N4 start to be hotter than before.

Then I found this - https://github.com/franciscofranco/mako/commit/712a86bb3cb4a4b5062920da5d62366bb17ef61c I guess this may cause it.
[Nexus 4 Original Android Development] terranox:
Yes

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] gtr-kir:
When will be 185 kernel?
[Nexus 4 Original Android Development] jak3z:
The only thing that change does is: when the temp raises to 70 ºC, CPU speed throttles until phone is below 65 ºC. Being realistic anything below 70ºC is completely safe.
[Nexus 4 Original Android Development] Pipusz:
When it's ready. At the same time, the build number could be different: 187, 199, 455, whatever.
[Nexus 4 Original Android Development] jak3z:
I can recompile 184 for you and name it 185 if you want :cowboy:
[Nexus 4 Original Android Development] Bill Gamble:
http://xdaforums.com/showpost.php?p=45779265
[Nexus 4 Original Android Development] Primey0:
Hey is this kernel for JWR66Y or JWR66V or does it not matter?
[Nexus 4 Original Android Development] Bill Gamble:
Does not matter.
[Nexus 4 Original Android Development] TheDarkDefender:
It does matter. The usual ones are for jwr-anything. The "jss" tagged versions are for jss-anything roms.

Sent from my Paranoid Nexus 4
[Nexus 4 Original Android Development] xFuGiToiDx:
No need to ask for eta. The latest test build that Franco pushed out is labeled as 185 includes the touch to wake option. Read page several pages and you will find it
[Nexus 4 Original Android Development] Bill Gamble:
As you said, "the usual ones are for JWR-anything". So, as far as "JWR66Y or JWR66V" goes, it does not matter.
[Nexus 4 Original Android Development] leets4uc3:
I prefer the name fondle to wake
[Nexus 4 Original Android Development] Bill Gamble:
http://xdaforums.com/showpost.php?p=45930268
[Nexus 4 Original Android Development] franciscofranco:
Did anyone bother to take a look into the new Note 3 benchmarks? For comparison sake to the current technology if the next Nexus phone comes with such hardware, my goodness, I'll be a happy panda. Technology is moving in an incredible pace. Although I wouldn't mind to have an Android device with the new A7 from Apple, its astonishing how performant a dual-core 1,3GHz is if its engineered right. I can't wait until Intel releases a 22nm mobile chip, and then a 18nm, they are so much ahead of everyone else in terms of engineering process. This is gun be gud :)
[Nexus 4 Original Android Development] neluba:
X86 support will probably be officially supported in android 4.4 together with 64bit.

http://www.dailytech.com/IDF+2013+Intel+Distances+Itself+From+Windows+8+Microsoft/article33363.htm
[Nexus 4 Original Android Development] franciscofranco:
Can't fúcking wait.
[Nexus 4 Original Android Development] pawan1993:
x86 architecture CPU's are going to bring a new era of mobile computing in my opinion. Canonical and their dreams of a PC phone are getting closer. CPU's are excelling but I hope GPU's follow suit. While the Adreno GPU's are great, I feel that Qualcomm have only recently begun pushing them further. Excited to see where mobile gaming goes from here especially with NVIDIA concentrating more on mobile devices.
[Nexus 4 Original Android Development] jak3z:
Nothing to wait for. World is ending tomorrow.
[Nexus 4 Original Android Development] Harry GT-S5830:
14nm Broadwell i3 ULV phones yes please :)
[Nexus 4 Original Android Development] Bobtehblob:
Do I need to uncheck dynamic scaling to use my own input boost freq?

Sent from my Nexus 4
[Nexus 4 Original Android Development] spacebar2011:
Don't we already know its a SnapD 800 with 2 GB RAM? Or are we talking about the 2014 Nexus?

The Apple A7 is heavily customised for iOS-specific application. Android does not have that luxury as no chipmaker makes chips only for Android. They make chips for Android, WP and all the other platforms out there. Having said that, the Moto X proved that you don't need HUGE power to perform great. I personally want to see a LOT more optimisation than 100 core chips with 2 dozen GB RAM. Also, Qualcomm needs to up its GPU game if they want to show their future-worthiness in this field.

Btw, I'm also waiting for Intel to bring something mindblowing to the table.
[Nexus 4 Original Android Development] alanwyl:
A330 beats the A7 in some of the graphics tests.

But the A7 really has amazing performance, with benchmark scores close to a 2010 Mac mini.

[MENTION=3292224]franciscofranco[/MENTION] you should look into the LG G2 rather than the Galagy N3.

The guts of the G2 will most likely be a Nexus 5.
[Nexus 4 Original Android Development] Bobtehblob:
Hmmmm, changes don't seem to be surviving a reboot :( I have set CPU settings and governor controlled settings to set on boot.

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
You remember the guy who bricked his Nexus 4? Well.. I'm that guy and I'm back. Cheers to LG for replacing my phone's motherboard for free. Now rocking r184 again!

Sent from my Nexus 4
[Nexus 4 Original Android Development] Krayvon:
i don't remember. what exactly happened to your fone? details please :)
[Nexus 4 Original Android Development] :
I mistakenly flashed Asus Transformer's recovery to my Nexus 4. So careless..

Sent from my Nexus 4
[Nexus 4 Original Android Development] Warbuff:
X86 32 bit has been supported on Android for a couple of versions now. This has been helped by upstream contributions from Intel.
[Nexus 4 Original Android Development] Lebo-Wog:
Yes i have heard they do a great job on warranties, better than Samsung and Apple. I would say better than HTC, but HTC service don't exist anymore.
[Nexus 4 Original Android Development] drawde40599:
So u helped our phones go up in price, congratulations! ;)
[Nexus 4 Original Android Development] StuMcBill:
Quick question, does the app automatically download the JSS version if I am running a JSS rom?

Running CM at the moment, just want to check that the app is downloading the correct version before I flash?
[Nexus 4 Original Android Development] jpde:
In my experience it does (CM Nightlies). Also, if you select "auto flash" it'll show something like "downloading r184-JSS". Not sure if there's a way to cancel the process once you hit auto flash though :D

edit: I've been using r184 for a day or so now and in my experience it's way to easy to accidentally wake up the phone. Pretty much every time I put it into my pocket I accidentally wake the device. The maximum time between taps should be quite a bit lower in my opinion, and another suggestion would be to only register the second tap if it's fearly near to the first one on the display. I don't know if that uses more power or anything, but TouchControl does this and I think it's a great way to eliminate unintended doubletaps (at least in my definition, a normal double tap is tapping pretty much the same point on the screen somewhat quickly. With the current build I can tap the upper right corner on the device once, wait two seconds and then tap the lower left corner and it'll wake the device. (n.b. it's entirely possible that I'm just doing something wrong :) )
[Nexus 4 Original Android Development] cmajetic:
184 hasn't any option to wake by double tap. you are talking about the experimental builds. just wait a bit, I'm sure Franco will fix the issues and give us a perfect feature in the near future.

184 is awesome and stable for me running the latest purity ROM. best kernel (semaphore also great but Franco's app is a bit better) ;)

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] HarbingerIV:
[MENTION=3292224]franciscofranco[/MENTION] Just wanted to report back. I was testing to see if disabling koush's superuser bundled with PA and using chainfire's SuperSU instead would eliminate the random flurry of FK SU toasts that me and other users were reporting. I can definitely say after a few days of use I have not seen the issue show up again. :victory:

So, it seems there's a problem with koush's superuser or the way PA implemented it or something else. Chainfire's SuperSu works like a charm. :D

Cheers!:cowboy:
[Nexus 4 Original Android Development] occtec:
I'm on PSX ROM v7.1 and using Franco r184 using touch control app from play store and double tap to wake works flawlessly for me ;) as well as slide2lock.
[Nexus 4 Original Android Development] zellleonhart:
Just want to report too, that I am having unresponsive screen with double tap to wake turned on. In touch control, turning off the screen and turn back on will solve it, but the Franco kernel one can't.

Beamed from my Paranoid HALO r163 Nexus⁴
[Nexus 4 Original Android Development] winner00:
[MENTION=3292224]franciscofranco[/MENTION] Hey I was wondering if you could implement this patch into your JSS kernel: https://github.com/CyanogenMod/andr...mmit/cee7856cad21feceb16b04e3761069a48b70826c

This should fix lockups on CM and CM based roms that are using CM's latest mako blobs. How they fixed it was use this patch plus some adreno blobs from flo.
[Nexus 4 Original Android Development] franciscofranco:
Now this is going to be a nightmare for me. I don't even...

I'm pretty sure that if I merge that patch in something else will break if the rom is not using the same blobs that CM...
[Nexus 4 Original Android Development] :
What's the difference between what Slimbean Devs did changing a commit and what the CM guys did? Couldn't they have gotten the same result using Slim method
[Nexus 4 Original Android Development] svnhvn:
Care to explain more detail mate?
[Nexus 4 Original Android Development] cjay73:
Lol I just bought FKU 2 days ago anyway it was still a great deal .I always have luck like that I bought my wife a N4 and 2 months later they drop a

$100:crying:
[Nexus 4 Original Android Development] Andre_Vitto:
Buyers remorse.. happens to everybody these days..
[Nexus 4 Original Android Development] :
Nexus is dirt cheap, don't fret. Lol!

Sent from my Nexus 4
[Nexus 4 Original Android Development] theclaytons:
I thought you were going to say "I bought my wife and then 2 weeks later she was on sale"
[Nexus 4 Original Android Development] :
Big LOL!

Sent from my Nexus 4
[Nexus 4 Original Android Development] jpde:
Yeah, got confused, I was using the second experimental build. And I'm sure it'll be tweaked, it's experimental after all and I was just trying to provide feedback :)
[Nexus 4 Original Android Development] pawan1993:
Google have surprisingly great warranty service! My loudspeaker died and I just gave a phone call to their 24/7 customer service centre and they sent an email with relatively easy instructions to get a new N4 and how to package my old one in the box of the new one so they can pick it up on a day convenient to me. So nice and easy.
[Nexus 4 Original Android Development] stratosk:
Could you please avoid using the 'F' word so often?

This is a public forum. We should give a good example to people following XDA rules.
[Nexus 4 Original Android Development] Andre_Vitto:
:Respect: :cowboy: