yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Koraboros:
I think NFS MOst Wanted performance problem went away on its own... Started it up again and no lag this time.

Edit: NVM it's back again.
[Nexus 4 Original Android Development] evostevo1:
Same here. Phone went from dying all the time when stock. Now I can't kill it.
[Nexus 4 Original Android Development] yokuyuki:
msm_hsic_host wakelock shot back up 15% for me on r28. It was 0.7% on r27.
[Nexus 4 Original Android Development] Luigiesin:
For some reason mine is always at 15% plus... I don't use the Facebook app anymore... Any ideas?
[Nexus 4 Original Android Development] galanakop:
R 28 the best kernel for me...

Thanks very much...

Στάλθηκε από το Nexus 4 μου
[Nexus 4 Original Android Development] techmatlock:
I'm on stock ROM flashed with r28. After unplugging from charger, battery icon still displays the charging icon. Went away after a few hours... Here's my last_kmsg http://db.tt/7trKLTZR.
[Nexus 4 Original Android Development] republicano:
it have to do with provider service?,I live under 500m from my providers tower and its fine, I noticed when I was at a cricket game it was very high, 3 hours on and 55min wakelock, I was sitting underneath thick concrete slabs and I had grey bars.I haven't found a way to disable/enable fast dormacy
[Nexus 4 Original Android Development] yokuyuki:
I have all sync on except Google+, Play Books, Play Mags, and Play TV. I have Latitude on and most of Google Now on. Cell broadcasts off. I do have Facebook running.
[Nexus 4 Original Android Development] Luigiesin:
Might be.... I'm currently out of town in another country.... Even though I always have full bars here I noticed it swaps from H+ to H and to E very often... So that might be my issue..

Once I get back to L. A I would have a better criteria of the battery drain... Even though L. A signal is usually pretty low, at least is H+ more consistent..
[Nexus 4 Original Android Development] UgoBoss:
My CPU settings doesn't stay in place with the lastest beta of FKU :confused:

Thank's by advance :)
[Nexus 4 Original Android Development] franciscofranco:
During deep sleep it doesn't really matter what governor you're using, the cpus are power collapsed. That's just pure placebo.

Because one needs to patch the Kernel to allow the sysfs entry to show the 27MHz when its being used. Its no functionality change, its just to show. The sysfs entry on stock only shows 128 up to 400. I'll say again, its no functionality change its pure cosmetic.

?
[Nexus 4 Original Android Development] asim0:
Hi Francisco, haven't been here since r111 please forgive my felony.

What is the latest default governor in your kernels lately? I am not sure, thanks.

Reading the last few pages I enjoyed the mood of discussion, compared to other filthy threads I frequented

Sent from teh void
[Nexus 4 Original Android Development] UgoBoss:
For example, when I set maximum CPU frequency to 1026 MHz, 2 or 3 hours later my maximum CPU frequency is at 1512 MHz...
[Nexus 4 Original Android Development] hughfollett:
Interactive :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
Are you sure your su is working? Works fine here and no reports of that whatsoever.
[Nexus 4 Original Android Development] defffizz:
Sry if it's been mentioned. On r191 every game lags (riptide gp 2, temple run oz for example). Only possible solution is creating power mode with maxed out frequencies and performance governor. I'm on Aokp (kecinzer), same problem goes to his version of franco kernel and this one, official. No problem, for example, with faux.

Sexy Nexy, Kecinzer AOKP+franco
[Nexus 4 Original Android Development] UgoBoss:
Gonna check that ! Thank's ;)
[Nexus 4 Original Android Development] Savant:
Project Pringles is aka project sexyback. Wonderful app makes me love the nexus line even more.
[Nexus 4 Original Android Development] GavinAshford:
[MENTION=3292224]franciscofranco[/MENTION] any chance there will be an update to the Project Pringles FKU app to add in the "Prepare for OTA update" functionality before the anticipated OTA update comes along to save people from having to unsubscribe from the beta program etc?
[Nexus 4 Original Android Development] JNewms:
What do you mean? Why would you need to unsubscribe from the beta to get 4.4?
[Nexus 4 Original Android Development] DanielQQ:
I think he means, a option to restore the stock kernel when you are on stock rom to get the 4.4 ota

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 4 Original Android Development] fozzie:
He's talking about unsubscribing from the f.Ku beta program in order to install the release version of f.Ku that has the 'prepare for OTA' option that will revert the changes made to the system partition so that an OTA OS update won't fail the asserts that it would do if Franco's changes were left un-reverted.
[Nexus 4 Original Android Development] GavinAshford:
Exactly all of the above.
[Nexus 4 Original Android Development] JNewms:
Ahh, I see. Didn't think about that. I have my own little routine I do before a update. Lol, but I never wait for the OTA, I just completely wipe my device, then push the new factory image.
[Nexus 4 Original Android Development] fozzie:
It's only a couple of files, mind. I always end up with ripping a load of files out of the previous version's tarball and manually copying to the device in order to get all the asserts to pass!
[Nexus 4 Original Android Development] GavinAshford:
Yeah I know, however I have a feeling I'm going to be out of the country with work when it gets announced/released (next week for 2weeks) so having the easy reverse button would be most convenient with limited PC/net access.
[Nexus 4 Original Android Development] franciscofranco:
Dunno, I have other priorities at the moment.
[Nexus 4 Original Android Development] Svarion:
thanks for the explanation :good: I've noticed that i had more screen-on time when showing the 27mhz freq but seems to be only a placebo :D
[Nexus 4 Original Android Development] GavinAshford:
I'm sure, no worries, cheers for letting me know, at least I can pre-prepare if necessary
[Nexus 4 Original Android Development] franciscofranco:
Biggest placebo in the entire universe history.
[Nexus 4 Original Android Development] deltatux:
It seems that the franco.Kernel app isn't letting me cap the GPU at 320 MHz for some reason. Is this an app bug?

I really don't need my GPU scale to 400 MHz, I don't even game on my device.

deltatux
[Nexus 4 Original Android Development] sordna:
Be careful, the prepare for OTA option does not restore the stock kernel, it only renames a file in the system partition back to the original name. You still need to restore your stock kernel in addition to the above before accepting an OTA update. You can use FKU to flash your stock kernel, provided you took a backup of it of course.
[Nexus 4 Original Android Development] hmillos:
It's been years since my last restart with r191, I think I'm undervolting but I am not sure by how much (1025 mV - 1512MHz) Is there any way to know the net value of undervolting?

I ue PA RC2 btw
[Nexus 4 Original Android Development] JNewms:
Yes, you can check it with Franco's app.
[Nexus 4 Original Android Development] yethz:
PM sent.

_____________________________

Device: Google Nexus 4 (LG-E960)

ROM: AOKP JB-4.3.1-MR2-(JLS36I) Kecinzer (Oct-18-13)

Kernel: Franco Kernel #190v2-JWR-Prima (Linaro@LaboDJ)

Recovery: PhilZ Touch (CWM) Recovery v5.15.0
[Nexus 4 Original Android Development] lotherius:
I'm at 1050 mv @ 1512MHz and I believe I'm at -100 if I remember correctly on a Fast core.

You could always just reset to default and see where it goes.
[Nexus 4 Original Android Development] GavinAshford:
Cheers, you make a good point - I did take a backup of the stock kernel so its already and waiting.
[Nexus 4 Original Android Development] blsrbl:
Is anyone noticing lags with notification drawer? Especially when is there some notifications or tasks? It really annoying.
[Nexus 4 Original Android Development] TheDarkDefender:
That's probably your rom/setup. Zero lags here. Underclocked,in fact.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Arstoien:
Project Pringles question/suggestion:

When opening a tunable to change (one that requires a number to be typed in), it doesn't automatically bring out the keyboard and one needs to tap the writing field. Is that something you control from the app, since I've seen many apps that bring the keyboard automatically when there's a typing field? And if so, would you want to make it so whenever the user taps on say timer_rate, it brings out the keyboard at the same time, without the need to tap the entry field?

Sent from my Nexus 4
[Nexus 4 Original Android Development] blsrbl:
I don't know. It's PA form a clean flash. Gonna forget, 4.4 is coming!
[Nexus 4 Original Android Development] David9519:
Double tap to wake is for me enabled by default and I can't disable it
[Nexus 4 Original Android Development] blsrbl:
So, i didn't make a backup. Do i need to flash factory image?
[Nexus 4 Original Android Development] pkelly517:
You may want to rethink that command.
[Nexus 4 Original Android Development] GavinAshford:
You should be able to use the flashable stock kernel from here: http://xdaforums.com/showthread.php?t=2381128

With that and the "Prepare for OTA" file reversal in FKU you should be all set to get OTA 4.4 when it is released - providing you are on the stock (factory/JWR66Y) 4.3 rom in the first place (i.e. not a custom rom or the AOSP/JSS15J branch).
[Nexus 4 Original Android Development] Mantulis:
echo 0 > /sys/module/lge_touch_core/parameters/touch_to_wake
[Nexus 4 Original Android Development] paranoid android85:
Do you know if you also have to be on stock recovery, or just stock rom and kernel?
[Nexus 4 Original Android Development] Tex99:
Yes stock recovey

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] GavinAshford:
Hmm, I'm not sure, I don't think stock recovery is necessary.

I think when 4.3 came OTA (from 4.2.2) and I had TWRP installed it worked fine after the update the custom recovery was replaced with stock recovery as part of the OTA update.

I'm sure someone will correct me if I'm mistaken.

Edit: OK, I might be wrong. Damn, this is spoiling my plans.
[Nexus 4 Original Android Development] shengovind:
You're right...Stock recovery is not necessary.. Twrp will do.. You should be on stock ROM and kernel.. With no mods etc.. No xposed etc..

Once you apply ota stock recovery is flashed..

sent from my Prevert nexus
[Nexus 4 Original Android Development] i860:
Hi

Reboot on r191 using torch

http://pastebin.com/CP327FvX
[Nexus 4 Original Android Development] strapped365:
Torch would be a ROM issue...are you on Carbon by any chance? Nothing against them at all, but that ROM reboots every time i try to use the torch for more than 10 seconds.

Sent from my Xperimental NeXuS⁴
[Nexus 4 Original Android Development] i860:
Hi im on cataclysm. I neve had this reboot on torch so far, how know n4 was in a bad mood.
[Nexus 4 Original Android Development] Drmol:
I'm getting reboots using torch on stock jwr66y as well, very often in fact.
[Nexus 4 Original Android Development] strapped365:
Hmm odd...I don't get them on Paranoid Android linaro builds by Criggs...I also don't get them on PsX... I'm clueless any where else because those are basically the only ROMs I can run without issue.

But r191 is the boss for me!

Sent from my Xperimental NeXuS⁴
[Nexus 4 Original Android Development] jmudrick:
Also on Cataclysm, no torch problems.
[Nexus 4 Original Android Development] David9519:
Doesn't work for me, again
[Nexus 4 Original Android Development] _artem_:
Try to remount / as rw

su

mount -o remount,rw /
[Nexus 4 Original Android Development] David9519:
I am perplexed :/

30 days ago it worked for me
[Nexus 4 Original Android Development] _artem_:
It's doubletap_to_wake and not touch_to_wake
[Nexus 4 Original Android Development] franciscofranco:
My goal is have all editable options to open the keyboard automatically - I just didn't find out how. I had it before, just don't remember how :cool:

Double tap to wake is disabled by default -.-
[Nexus 4 Original Android Development] Testraindrop:
As far as I remember you have to set focus to the edittext when you launching the view with it.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] TheDarkDefender:
edit the second file and change Y to N

And dude! Its doubetap_to_wake !!

Sent from my Nexus 4
[Nexus 4 Original Android Development] David9519:
My goal is have all editable options to open the keyboard automatically - I just didn't find out how. I had it before, just don't remember how ￼

Double tap to wake is disabled by default -.-

Dudes! First tries I used doubletap but it didn't work for me!

Second thing : it was enabled for me by default, I didn't change any settings and the doubletap to wake feature was enabled!

Edit: thank you

I changed the file from Y to N
[Nexus 4 Original Android Development] franciscofranco:
I believe that's not enough but I'll try it again.

https://github.com/franciscofranco/...rivers/input/touchscreen/lge_touch_core.c#L60
[Nexus 4 Original Android Development] Svarion:
post deleted - sorry :D

sent from my nexus 4
[Nexus 4 Original Android Development] franciscofranco:
New beta FKU has been pushed and its live. Finished File Manager functionality, fixed bugs and added Swipe to Delete on the Backup & Restore panel. If you're running the beta release please give me all the feedback :)
[Nexus 4 Original Android Development] fozzie:
You don't happen to have a file like '97sweep2wake' in /etc/init.d (or /system/etc/init.d) do you?

There's something funny going on as a number of people are having issues with this being enabled. It would be good to get to the bottom of what exactly is enabling double tap to wake.
[Nexus 4 Original Android Development] franciscofranco:
I want to shoot the user who did that script when I explicitly stated SEVERAL times that my double to wake code is just for testing and its not near stable. /facepalm
[Nexus 4 Original Android Development] fozzie:
It's odd though, as that script appears to have been around for a long time (if you search Google just for the script name)...
[Nexus 4 Original Android Development] Boosik:
Hi, I have poor battery life thanks to these wake locks (see image) , can anybody tell me what to do to fix it? I'm on franco kernel r191 JWR and PA 3.99 R2.

Odesláno z mého Nexus 4 pomocí Tapatalk 4
[Nexus 4 Original Android Development] Arstoien:
It's an app(s) that keep your phone awake. If you go to the partial wakelocks tab, you should see more info on the different app wakelocks. You could also install Wakelock detector – you might find it easier to read and understand. Furthermore you might want to start thinking about since when it's started and if you've installed or updated any apps that might have caused it.

I'd suggest to go to the proper thread (or make a new one, I'm not familiar with the battery life threads around) for more and answers, since this isn't kernel related. Good luck
[Nexus 4 Original Android Development] GuyIncognito721:
I'm not sure if this has been suggested before, but for the FKU app, I'd love to see the settings changed so you are selecting things such as MHz, GHz, s, ms etc. instead of using absolute values. I think it looks cleaner and is much easier to follow and not F something up if you accidently add or miss a 0 in your value you have to manually enter.
[Nexus 4 Original Android Development] jayRokk:
I wanna say thank you Francisco.

I've got 8hours in so far with 40% left and 4hours screen time.

I know if I were off the screen more I'd make that 8 hours longer lol

Anyways I'm sure it will get better over time. This was my first cycle with this kernel. But thank you!
[Nexus 4 Original Android Development] franciscofranco:
Which options in particular are you talking about? I'm not focusing on those minor things at the moment, I'll only do it when the app functionality is finished and ready for beta.
[Nexus 4 Original Android Development] Boosik:
Problem is, that Partial wakelocks are only 28minutes from audio_out and google play music, but these kernel wakelocks are longer than hour. And in default battery stats, it's shown as OS Android.
[Nexus 4 Original Android Development] GuyIncognito721:
Pretty much everything in Governor and Hotplug controls. Also, it's kind of strange that you have to type the name of the IO scheduler you want as opposed to selecting it from a list. Again, minor things I know.
[Nexus 4 Original Android Development] franciscofranco:
msm_hsic wakelock is for your radio to function, otherwise no GSM/whatever...
[Nexus 4 Original Android Development] franciscofranco:
Yes those minor craps will be ironed out when it enters beta.
[Nexus 4 Original Android Development] The Gingerbread Man:
Everything added so far seems to work. I did encounter a force close on tuna but didn't send bug report. The app only asked for new su permission when I entered voltage control and I tried to change something. The su request didn't come quick enough. The ui seems faster and smoother. I agree with the other user about things being selectable not all punching it all in manually (already saw your response). Other than that I'm looking forwards to more features in the kernel setting being built back in like TCP, headphone boost, battery extender etc. Really coming along nicely so far! Please check 2013 n7 thread as I posted a request specific to that device
[Nexus 4 Original Android Development] GavinAshford:
[MENTION=3292224]franciscofranco[/MENTION] There's a bug I've noticed in the beta FKU app however it's not a crash/force close issue so not sure if you need to resolve it at this point... maybe another one for the proper beta stage.

If you are in the Colour Control section, then navigate to any other section and then press the "back" key to go back to the previous section (should be Colour Control) and it only half navigates back - the "pages" scroll bar indicator appears for it, you can scroll left/right (when going right the On/Off toggle appears), but none of the content and the page title remains as the "other" section name.
[Nexus 4 Original Android Development] SnoopHTC:
Hello, same for me with slimbean 1.9 + r191 JWR (full wipe) + a lot of use root access when 320 MHz is set (for exemple)

Thanks a lot for your work !!!
[Nexus 4 Original Android Development] ben_pyett:
which root are you using, supersu v1.65 is recommended
[Nexus 4 Original Android Development] namurt:
[MENTION=3292224]franciscofranco[/MENTION]

re: showing the keyboard automatically, see: http://stackoverflow.com/questions/5105354/how-to-show-soft-keyboard-when-edittext-is-focused
[Nexus 4 Original Android Development] The Gingerbread Man:
Same happened on flo, bug report sent through play store
[Nexus 4 Original Android Development] blsrbl:
Delete.
[Nexus 4 Original Android Development] franciscofranco:
Can you email me that request? I'm not following any other thread at the moment besides Mako :)

Can you make a video of that? Thanks.

Can you make a video of that **** and post here? Thanks!
[Nexus 4 Original Android Development] corwest:
I've seen you answer this same question no less than 5 times in the last 20 pages or so. Must get old after 5000+....
[Nexus 4 Original Android Development] franciscofranco:
You have no idea.
[Nexus 4 Original Android Development] corwest:
I've been following you for about 3000 pages now and it seems that every 5-10 pages or so the same questions get asked over and over again. Don't know how you do it.
[Nexus 4 Original Android Development] franciscofranco:
Deep breaths, few beers, I a few curses, then I post :angel:
[Nexus 4 Original Android Development] GavinAshford:
Hopefully this works...

https://www.youtube.com/watch?v=hCqvA3kGxJU&feature=youtube_gdata_player
[Nexus 4 Original Android Development] limeaide:
About two months ago there was a video posted on reddit of a rom developer reading his development thread. It started out with him explaining he had answered a question earlier in the day. It shows the question and his answer one post after. Then four hours had lapsed and the same question was asked 10 times over about 5 pages of 10 posts. He quoted and answered the guys in one post. Then the video cuts to the next day and he says it had been 12 hours since his last post. This same question was posted around 30 times. At this point he was frustrated because not only had he answered it twice but over that time people in the thread answered with his quote.

Two users basically told the people to get bent and demanded the dev respond. As he sat there explaining and reading these posts you could see him getting upset. While he was sitting there trying to respond and not be a **** he received three emails from the two guys. Demanding he get off his lazy arse and respond. The guy looks at the camera and says this is what I deal with each time I release a new build. But it had much more colorful words. His browser dinged and it showed he had two pms at the forum and guess who they were from. One of the jerks demanding him respond. All you see is the guy blow a gasket pick up what appears to be a glass bottle and throw it. Then you can hear him cursing and the video stops. From what was said on reddit the guy threw a beer bottle at the wall but instead smashed into his 42inch monitor at which point it spilled and ruined the power supply on the computer.The video was pulled from youtube about a day later. The thread was removed and the guy pulled all his work from all sites it was hosted on.

I imagine you have some similar rage but have never thrown a beer bottle yet.
[Nexus 4 Original Android Development] Savant:
The question is what beers my friend? It's a shame I don't live near you since I would have a good drinking buddy lol.
[Nexus 4 Original Android Development] NYLimited:
I think you could say the same about some of you users .... :D

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] _artem_:
Is color control only accessible while on franco kernel? Latest carbon nightly has a known issue with custom kernels:

Nightly 10-23

Many system changes in telephony and camera from CM. May cause fc on boot if you have a custom kernel with a custom ramdisk.

But it doesn't matter I reverted to the previous ... but just now flashed it again but this time without franco, it uses default carbon kernel... display looks different, colors are a bit different than I see them on franco. So I launched fku Pringles, choose color control (to set the s4 preset which I'm using since on franco) and got FC right after I tap on color control in the navigation drawer.

The point is - is color control working only on franco kernel? There is no FC while I'm on franco kernel
[Nexus 4 Original Android Development] Savant:
Now that's lager and some good stuff around here I'm the only one who drinks it. I have to go to the liquor store because of it.
[Nexus 4 Original Android Development] corwest:
May I suggest a glass of scotch and tobacco pipe? Works wonders for me. ;)
[Nexus 4 Original Android Development] franciscofranco:
What do you think?

I don't smoke, but scotch could do it!
[Nexus 4 Original Android Development] corwest:
Hey brother whatever keeps the mind turning out good ideas.
[Nexus 4 Original Android Development] _artem_:
I definitely think there should be no FC upon tapping on color control. If it's not working with other kernels it just should inform me and not FC the whole app :)

So - what do YOU think?
[Nexus 4 Original Android Development] corwest:
Judging by Franco's work, that is not the intended action and will be fixed with time. Patience.
[Nexus 4 Original Android Development] sNoxious:
You meant patience I suppose. ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
I don't intend it to FC, like it didn't on the stable app, but for now until it goes to beta thats how it rolls ;)

And now I'm off to watch some Castle, Detective Beckett is where my money is at for the rest of the night. Good night fellas!
[Nexus 4 Original Android Development] theclaytons:
+1 on this. Beckett is smoking hot.