yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] CoolApps:
Ok so I recently installed franco.Kernel Updater.

So while flashing the JSS version which was downloaded from the updater without really noticing, I was just enjoying the humour of what was getting echoed onto the TWRP output, I wiped the dalvik cache and the cache partition and then rebooted to the system.

The first thing I noticed was the colours where just amazing, after scrolling around the system I have noticed major graphical glitches and then realised that I need the JWR version since I have PA so I flashed the JWR one manually.

After doing that and wiping all those caches I noticed a little lag at the start and then it got smoother.

Of course I got the "Starting Apps" dialogue box on every boot (I have to reflash the rom to fix this which I will do later -.-).

So far I found some nice features in the Updater BUT I have some suggestions to say for the next release:

PLEASE make sure there are options such has JWR and JSS when pressing the update button!

Make sure the Misc section is in the slide menu thingy for easy access since the option within misc is REALLY important for stock ROMs.

Suggestions for your server/website:

Please tag the JWR kernels to avoid possible confusion.

My question is: Do you need to wipe the dalvik cache and cache partition when you install/update Franco.Kernel? (Hope not because it caused that annoying starting apps thing every boot).

Overall I love the humour within the updater and the flashable zip, the performance is just so incredible and of course we all love the features of the kernel. :)

And yes I did promise and I did it Franco. ;)
[Nexus 4 Original Android Development] hmillos:
No, You don't.
[Nexus 4 Original Android Development] svnhvn:
r193 with stock ROM (mobile data always on and no wifi at all).

Great battery life span franco.
[Nexus 4 Original Android Development] rosswaa:
Is there a new colorfix? I'm using cm and it used to work fine with the color fix but now when I flash fk then the color fix of won't boot just sots at the Google bit. I know fk isn't the problem as I can flash that and it works fine but colors are messed up :/
[Nexus 4 Original Android Development] blttalas:
What is the difference?
[Nexus 4 Original Android Development] ticiano_arraes:
You could just read one page back and see that this fix don't work anymore. Someone is compiling the kernel with the commits needed to work, just search and you'll find the thread.
[Nexus 4 Original Android Development] ChavitoArg:
Hi, i have a problem with 193_jwr, simple gpu gobernor is not working, trickster rejects it and take me to the previous set governor. Also MP-decision doesnt "stick" also whit trickster mod, can anyone confirm this? Thanks in advance
[Nexus 4 Original Android Development] zorginho:
It's because mpdecision and simple gov are dropped?

;)

Inviato dal mio Nexus 4 utilizzando Tapatalk

---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------

Inviato dal mio Nexus 4 utilizzando Tapatalk

---------- Post added at 06:47 PM ---------- Previous post was at 06:47 PM ----------

Inviato dal mio Nexus 4 utilizzando Tapatalk

---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] ChavitoArg:
didnt knew that, since i couldnt find it on changelog. But thanks sir, have a nice day ^^
[Nexus 4 Original Android Development] franciscofranco:
No mpdecision since day 1. No simple governor, I wrote my own GPU governor. Its sad that trickster doesnt load data dynamically, instead it hardcodes stuff (as far as I can see).
[Nexus 4 Original Android Development] ChavitoArg:
Im gonna email trickster mod app dev and report what answer i get from them, if a kernel doesnt have some stuff then shouldnt be available as an option.
[Nexus 4 Original Android Development] zephiK:
Or you can just buy franco kernel updater and not have to deal with any of those problems ever again. FKU UI is so much intuitive than Trickster as well, even in the older version--the project pringles just sweeps Trickster away in terms of layout. Trickster is nice but it won't have the fullest functionalities since it is attempting to be a universal kernel control app.

Support your preferred kernel developers :good:
[Nexus 4 Original Android Development] X DoZ3R:
I missed 1 month from xda. I know its not the best place to ask but can someone explain or gimme a link what that CAF is? Thanks you
[Nexus 4 Original Android Development] eluspo:
How do i set the value to activate fast charge?
[Nexus 4 Original Android Development] Savant:
Best thing is to Google it since cm likes doing their own thing.
[Nexus 4 Original Android Development] DesertVelo:
CAF stands for Code Aurora Forum and is based upon AOSP code to optimized the Qualcomm chipsets. The take away from all of the discussion is how CM is implementing the CAF changes to the project and negatively affecting kernels used on some AOSP ROM's (based upon CM). When a ROM contains CAF code is used with a custom kernel, inverted colors and phones not completing the boot sequence are the typical results.

There are patches/fixes (colorfix.zip) that try to address the issue but are not longer valid since CM development continues. If you like using CM 10.2 ROM's and this kernel, there are ROM variants (Carbon for example) that have removed the CAF merges so custom kernels, like Franco, can still be used.

If you want to try non-CAF ROM's, please read the developer's OP to determine the ROM variant (JSS or JWR) and apply the correct kernel. By all means, read their threadto give you some clues to how the ROM is built and custom kernel compatibility.
[Nexus 4 Original Android Development] eluspo:
Color profilw doesnt atick after a reboot?
[Nexus 4 Original Android Development] blttalas:
What is the difference between 3.40 kernel and 3.67

Nexus 4 Beats™ Audio Edition cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 4 Original Android Development] Doo Doo:
0 = disabled 1 = enabled

do you have set on boot enabled for it?
[Nexus 4 Original Android Development] eluspo:
Thanks for the info. Im just using fk app for setting the color profile, idk if it has a set on boot option
[Nexus 4 Original Android Development] Doo Doo:
are you using the alpha version of fku?
[Nexus 4 Original Android Development] eluspo:
Im using project pringles. I dunno how to revert back to the old one lol
[Nexus 4 Original Android Development] Doo Doo:
ok well open up project pringles then open up color control now you should be on the main page of color control

slide to the right 1 time & in the top right hand corner there should be a on/off toggle that is set on boot for color control
[Nexus 4 Original Android Development] eluspo:
Thanks buddy i didnt know lol. What profile is best to use?
[Nexus 4 Original Android Development] Doo Doo:
i use halfbreed fix
[Nexus 4 Original Android Development] franciscofranco:
Well the first time you run the app there are some help tutorials all over the place, and in the last color tab the help explains how to set color on boot. Theres really no excuse to not know what to do with Pringles ;)
[Nexus 4 Original Android Development] nadavar:
Is Pringles a closed alpha or is there a download link somewhere?
[Nexus 4 Original Android Development] Savant:
The links been mentioned plenty of times search the thread or do a Google search .

---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------

Didn't mean to spam you with force close reports Franco but it should tell you what's going on. Yum bock.
[Nexus 4 Original Android Development] nadavar:
Pringles is awesome, can't believe I only now jumped to it, was even in the community for a long time.

Love the franco color profile
[Nexus 4 Original Android Development] limeaide:
Technically it is a open beta. However unless you own Franco kernel updater it's not available.

Sent from my Nexus 4
[Nexus 4 Original Android Development] max4wdc:
Hey franco ,i had a reboot.

i'm listening to recorded voice in whatsapp and boom my phone rebooted .

Thank you for all great work and i hope you can find anything from my log file .

Log:

http://pastebin.com/GEn6R1NU

Sry for my en .
[Nexus 4 Original Android Development] lotherius:
Looks possibly like a Bluetooth bug. I've seen reports, and experienced myself, random reboots when connected to certain bluetooth devices. Seems to be something Nexus 4 specific not necessarily Franco kernel.

Anyone else have ideas?
[Nexus 4 Original Android Development] ChavitoArg:
Ive just purchased the FKu app, its awesome :D

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] Savant:
Its vundabah. :p
[Nexus 4 Original Android Development] ChavitoArg:
Franco this is the response from trickster team about simple gpu gov and mpdecision:

The app does build the GUI dynamically, to answer your question:

- Franco's kernel does not support simple gpu governor but it has interactive gov instead. The list of these governors is hard coded inside the kernel and there's no way to read that AFAIK.

- MPDecision depends on /system/bin/mpdecision binary and kernel support. The existence of the former can be detected but the latter is hard coded inside the kernel again without a way to detect it at runtime AFAIK.

If you do know anyway to do the above, please do tell me.

--

Team Trickster Support

I really dont care now that i use FKu :P

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] mendozaram:
i have the same question

Nexus 4 - Slimrom Build 2.0 - Linaro FK r193
[Nexus 4 Original Android Development] alanwyl:
Ya dynamic yet hard coded
[Nexus 4 Original Android Development] bigeyes0x0:
TM is built to read device config at runtime but AFAIK there's no way to detect mpdecision supporting code in kernel being removed or available gpu governors on the S4/S600 unless, for the latter, this hard coded stuff https://github.com/franciscofranco/mako/commit/652b148aa9c572b621d7d93078dfea1c26c913ea suddenly readable somewhere at runtime.

Please do enlighten me as I have been quite vocal about detecting stuffs at runtime myself and how kernel devs tend to force app to hard code due to their own hard coding. It's a quite sad state of affair really.

On unrelated note, as I saw a dev proposed a classic case of thread polling where it should not be used here's how to do it correctly http://pastebin.com/A9gP1R9K as a "thanks in advance" if you can enlighten me about how to detect the two issues above. Really hope this dev can code more reliable code ;).
[Nexus 4 Original Android Development] hamad138:
Franco do u have to start again for kitkat because 193 is amazing
[Nexus 4 Original Android Development] nachordez:
Francisco: i think I've found a bug in proyect Pringles or 193

The vibration is much much softer now, even in 100. Some times nearly no noticeable, or even no vibration at all!

Nexus 4 / Cataclysm / Franco / V4A
[Nexus 4 Original Android Development] nadavar:
Might be a bit counter intuitive, but it's there any plan to support faux color profile in fku?

Whenever I try different kernels I have to freeze defrost fku and trickster.

Although I always come back to this kernel because it's so good, but I do get curious .

I know the app is for franco kernel but it would provide a much beget service if it would support other kernel solutions.
[Nexus 4 Original Android Development] hamad138:
I have the best display settings for nexus 4 here. Iphone 5 calibratet with perfect whites and dark and punchy colours

And franco did u do something with the screen? Its a little bit sharper and clearer or is it just me
[Nexus 4 Original Android Development] CoolApps:
Ok Franco, how long did it take you to get the perfect default colour profile? :rolleyes:
[Nexus 4 Original Android Development] nadavar:
I meant and option to change color profiles using faux's system
[Nexus 4 Original Android Development] pitjago74:
Well when I use Franco I use FKU

Faux kernel with Faux control and Semaphorekernel con SemaphoreManager....thats The way The Dev. Would like The users use it;)

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] combatdeity:
Ignore, bad post
[Nexus 4 Original Android Development] Cantacid:
Hey i just flashed multi rom on my.phone, i was wondering if you guys could suggest a rom other than purity(primary for me) that is jwr.. And is stable with franco?

I havent following any other thread other than purity and franco so not sure what all developments have taken place!

---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------

Its going to be hard for me to update to 4.4 until purity updates it to 4.4, slightly broken power button! :(

---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

I was about to post this, somtimes the vibration while typing would scale hogh and low! Im not sure if this is because of francos or purity's latest, coz i updated both at thesame time!

I guess franco can clarify this! Not much of an issue anyways, plus im not using pringles either so thats out pf question!
[Nexus 4 Original Android Development] Bill Gamble:
Cataclysm.
[Nexus 4 Original Android Development] Cantacid:
Tapatalk acting funny. Delete Please
[Nexus 4 Original Android Development] arcticrobot:
SlimBean
[Nexus 4 Original Android Development] eluspo:
Are you using the bundi profile?
[Nexus 4 Original Android Development] hamad138:
Slighlty tweaked because of the blueish tint
[Nexus 4 Original Android Development] eluspo:
Can you share it here? :)
[Nexus 4 Original Android Development] hamad138:
Same as bundi but whites set to 1
[Nexus 4 Original Android Development] nachordez:
So it's clear its something r193 related... I'm on Cataclysm, so different Rom.

Nexus⁴ / Cataclysm / Franco / Viper4Android

GT-p5110 / Dhollmen / Viper4Android
[Nexus 4 Original Android Development] Bill Gamble:
Maybe not. I'm on r193, Cataclysm, no Pringles and haven't noticed any loss of haptic feedback. I keep mine at 80%.
[Nexus 4 Original Android Development] gregorypeg1000:
Is this kernel undervolted by default?
[Nexus 4 Original Android Development] Savant:
No.
[Nexus 4 Original Android Development] franciscofranco:
There is no Kernel 3.67.

The difference between 3.4.0 and 3.4.67 is just fixes that upstream Linux Kernel guys push. Most of the times its only fixes to x86 and other stuff that we don't use, so its mostly pointless "most" of the times for us.

You're actually right on the governor account, I forgot the trustzone governors are not exposed anywhere besides the one that is selected by default.

About MPDecision however I think differently. You can check if the service is running, and you know that, so in my opinion if X or Y boot.img does not start the service by default it means the Kernel has some other Hotplug driver so there is no need to have the option to turn on/off MPDecision visible. That's what I think about it. I disable the service start on my ramdisk - users of FK should not have the option to turn it on/off in your app, users don't know anything about that so they'll create a bigger mess with it. That is my opinion - its your app, your choice.

Now about that Thread polling... well I don't see the reason for your sarcastic "some dev" mentions. If you want to come forward and criticize my code at least have the decency to call me from my name, I got no problems with that. About the code itself:

1 - I don't see a problem in polling a thread state - it may not be the prettiest code around but in some special cases I use it depending on what I want to do. Programming is not X is right, Y is wrong - sometimes we use different ways to achieve specific goals. The code is not wrong, and if its treated correctly (eg. removing callbacks after is done) its just fine;

2 - So you have a a bunch of lines (in your so friendly and warm "thank you in advance" link) when you could write basically the same thing in less than 10 lines creating a Thread and a handler inside to post things to the Main UI thread.

3 - I don't like AsyncTasks and I'm by no means obligated to use that kind of code and advocate it.

Vibration code on the Kernel is the same as ever, no changes. Pringles only echos the value to the sysfs location, there is no magic.
[Nexus 4 Original Android Development] Cantacid:
Might this be a faulty hardware?
[Nexus 4 Original Android Development] nachordez:
So vibration is probably broken on my phone? What a pity, I use it really more than ring sound...

Perhaps I could have found an excuse for the N5 when it's out, then...

Nexus⁴ / Cataclysm / Franco / Viper4Android

GT-p5110 / Dhollmen / Viper4Android
[Nexus 4 Original Android Development] sordna:
I'm not surprised, on my N4 the vibrator feels really "loose". I keep it at 60 so it doesn't annoy me. The difference between the vibrator on Samsung phones and the N4 is day and night. On the samsung, the vibrator is quieter and yet the whole phone makes you feel the vibration. I hope the N5 has this thing improved, the Galaxy Nexus was super good in that depratment.
[Nexus 4 Original Android Development] franciscofranco:
Yes, exactly!
[Nexus 4 Original Android Development] jtwlbz:
I like samsung vibrator bettrt as well
[Nexus 4 Original Android Development] santeana:
Lol i think my wife has a Samsung vibrator... She loves it too! ;)
[Nexus 4 Original Android Development] Bobtehblob:
Franco, few suggestions for project Pringles. Not really sure how much of what I'm saying has already been answered/or the features are just simply incomplete but here's what I've noticed.

The ui feels a lot more complete on the phone version. I feel like the tablet version needs some kind of highlight showing the user where they currently are. Also is it possible to make the left tab disappear or just be slightly smaller? Feels like it's oversized with the right tab being where the majority of the user input will be done.

On both versions I feel like the voltage control section is a bit awkward with the buttons in the top right. Doesn't really tell you what they do and they're a bit small. It's fine if you've used the app in its previous versions but might be a bit confusing for some.

In the colour control section why do I have to select a button to set on boot when everywhere else it's a long press? Just feels a bit disjointed. Also not sure about the 3 different swipable sections within colour control. Not sure what's a better way to do it but it just feels a bit off for me. Maybe just like how it is in the current production version?

Also under CPU manager, hotplug control. Long pressing first level gives you cores on touches description and vicar versa :) I'm also just going to assume the per-app power modes just isn't complete yet.

Overall though project Pringle is a lot faster and looks a lot cleaner, really excited to see what the finished product looks like! I would have included more pictures too but it's a pain in the ass across two devices on tapatalk!

Sent from my Nexus 7 (2013)
[Nexus 4 Original Android Development] franciscofranco:
Thats the tablet UI its best used in landscape mode. I cannot change that behaviour, thats done by the SlidingPaneLayout from Google. Unfortunately I have not added the logic to change the ActionBar title when a new tab is selected (in the Tablet layout), but don't worry that will be done.

About the Voltages section that +/- buttons will change to "Plus 25mV" & "Minus 25mV" or something like that, so also don't worry.

About the Color section - I started to hate menus inside menus inside menus, and I think it looks better and is more functional just how it is, in tabs. I'm still not 100% sure I like the layout of the bats (with the little blue indicator at the bottom) and I'm still thinking about it. About the set on boot on Colors... well that was one of the my brain deadlocks a few weeks ago. There is no way to add a long press to this Color section just how it currently is so I thought having that Switch on the action bar made sense (just like the Wi-Fi tab on/off in the ActionBar). I'm always listening for constructive feedback so if anyone has a better idea I'm all ears.

The CPU Manager question - The only section that I want, and makes sense, to add a global set on boot is voltages, you just won't go inside and add set on boot for different freq voltages right? The other panels makes more sense to have a more finer control instead of a global set on boot.

The PerApp Modes is certainly not complete at all I just shipped it like that because that was the current work state at the time and I was still thinking about the functionality.
[Nexus 4 Original Android Development] :
I've had multiple reboots out of the blue by running your latest r193 kernel and fabi's 25th of october PA nightly.

I've already posted this in the pa thread, might just post this in the nightly thread too but I don't exactly know where it really belongs so Ill just go ahead and post it here too.

here's the last_kmsg:

http://pastebin.com/iEwCZYLd

Cheers and fantastic kernel keep it up mate ;)
[Nexus 4 Original Android Development] arlenwoot:
[ 20.199267] Restarting system.

[ 20.199481] Going down for restart now

No errors detected

Boot info:

Last boot reason: reboot

Don't think its kernel related. I could be wrong though.
[Nexus 4 Original Android Development] franciscofranco:
That's the recovery Kernel log.
[Nexus 4 Original Android Development] X DoZ3R:
Im running r193 jwr franco kernel with purity rom, my cpu four core stuck online untill i turn off the screen, turn on and normal again but all 4 core go online again because off hotplug so... Is it a feature or im doing sth wrong?
[Nexus 4 Original Android Development] franciscofranco:
Are you using a live wallpaper?
[Nexus 4 Original Android Development] X DoZ3R:
No, i just did a clean install

---------- Post added at 11:07 PM ---------- Previous post was at 11:03 PM ----------

Now i realized that its only happen when i charge the phone, when i disconnect everything go back to normal :) strange....
[Nexus 4 Original Android Development] franciscofranco:
Are you using the stock charger?
[Nexus 4 Original Android Development] X DoZ3R:
Deleted

---------- Post added at 11:11 PM ---------- Previous post was at 11:07 PM ----------

Absolutly, stock charger and cable, it happens when i charged from usb and ac too
[Nexus 4 Original Android Development] limeaide:
You win the post of the week. So many people are thinking that when reading the other post and wish they would have beaten you to the punch.

Sent from my Nexus 4
[Nexus 4 Original Android Development] santeana:
Lol :)
[Nexus 4 Original Android Development] sordna:
pics or it didn't happen !!!
[Nexus 4 Original Android Development] jimbohurt:
Franco is there a way to see what color profile I am on currently?

I know its just trivial but I really like the color profile im currently using and want to remember what it is
[Nexus 4 Original Android Development] NeverBackDown:
What version of Franco apk are you using.. If you are using project pringles then I guess it's still not implemented (last when I tried it) if you are using the previous apk then you should find your color profile in status section..
[Nexus 4 Original Android Development] noobiekins:
if my phone's screen stops working at around 5% battery life, is it my cpu undervolt conflicting with the screen or does it require an RMA to fix?
[Nexus 4 Original Android Development] franciscofranco:
If you're using pringles nop, but I'll add that!
[Nexus 4 Original Android Development] jimbohurt:
Yeah, Pringles. Great thanks man!
[Nexus 4 Original Android Development] Savant:
That would be a wonderful addition to the application.
[Nexus 4 Original Android Development] franciscofranco:
Sure thing.
[Nexus 4 Original Android Development] blueren:
Hi - I'm on the latest nightly. I find that sometimes, opening apps makes the animations stutter a but. Same thing happens while scrolling g+ or play store. Is there any settings I can change to even this out? Up to this point, I've done no changes in the kernel.