yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] hellsgod:
Don't use JSS roms.

hells
[Nexus 4 Original Android Development] Arstoien:
For ease of use, for those who can't or don't want to use terminal commands, and generally for support for the dev. This is xda, it's encouraging people to learn more about all these stuff. Plus I haven't mentioned even half of the stuff one can do with franco's app.

Also there are a lot of uses for these commands outside of francos app. I for example use Tasker to switch between different predefined power modes because I can quickly activate it from the homescreen, and because I change some stuff that aren't available in franco's app – that, and I use the alpha, which doesn't have this option yet.
[Nexus 4 Original Android Development] steviewevie:
Sorry but I completely disagree. Honeycomb was a separate fork for tablets. But from ICS onwards it was all meant to be the same version. This was the case up until 4.3 when Google messed up (which they admitted) and at the last minute forgot to put some changes for the 2013 Nexus 7 back into the Nexus 4 code.

It was a mistake and it is a big mess. Hopefully it will be all sorted with KitKat.
[Nexus 4 Original Android Development] getaceres:
I've read that it was a mistake and that they admitted it was so but I haven't seen a link to the admission, only developers swearing that google admitted it. Even if it was then they could have fixed it with any other release (there was a security patch for Nexus 4 and two or more releases for Nexus 7) but they didn't so my guess is that Google know what it's doing. There is some code in JSS that could work in the Nexus phones but also introducing some other problems so the strategy has been to let it as it is and not force JSS code into the Nexus 4 unless it works correctly (which it doesn't).

The real problem here is that we want the latest code and the most updated one no matter the cost and the cost is this mess. I maintain what I said, no matter if Google made a mistake or not, JSS is code for tablets, JWR is code for phones. The mess is ROM developers forcing JSS code into phones.
[Nexus 4 Original Android Development] Svid:
I had random freeze and i had to force reboot the phone. What file i need to see for troubleshooting this weird issue?
[Nexus 4 Original Android Development] aimcr7:
JBQ is already admitted it, it happened before he resigned from google.
[Nexus 4 Original Android Development] cgulliver:
I just went from CM to slimbean (JLS) and am enjoying Franco and stability again. JSS and now CAF are the issue with CM. When CM sorts through the DLs and goes stable with 10.2 I will go back. By then 4.4 will be out though so who knows.
[Nexus 4 Original Android Development] getaceres:
Could you put a link to some post in which JBQ admits himself the error of creating two different branches? As long as I know, he resigned because they weren't able to publish factory images reliably due to licenses with Qualcomm.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] steviewevie:
Hopefully someone can find a link for you. I think it was on Google Android community but I could be wrong.

Basically he admitted that they did the testing for 4.3 for the N4 assuming it was ask the same stuff as for the 2013 N7, but it was to late once he found our there had been some late changes.

Google haven't fixed it yet because it's probably too much effort considering 4.4 is just around the corner, not because they didn't think it was a mistake. Just a mistake they could live with.
[Nexus 4 Original Android Development] fozzie:
You could try getting /proc/last_kmsg
[Nexus 4 Original Android Development] GretaLewd:
Also having problems with the '+' and '-' buttons in "Gamma tables":

The '-' button will not work until you have pressed the + button

There seem to be pre-defined steps without the ability to get to an intermediate figure

Aslo, the "Contrast" values do not allow/align with the values suggested in this spreadsheet .
[Nexus 4 Original Android Development] quiquegabriel:
Any recommended values for the new gamma implementation?
[Nexus 4 Original Android Development] pkelly517:
Wrong.

Look at the latest source code for mako

https://android.googlesource.com/device/lge/mako/
[Nexus 4 Original Android Development] zephiK:
Correction: Don't use JSS ROMs that use JSS Kernels.

Carbon is a JSS ROM but uses a JWR Kernel. Same with PA/Slim,etc
[Nexus 4 Original Android Development] blueren:
Frankly, I don't see what the entire deal is about the whole JSS/JWR variants. Yeah, JSS suffers from micro freeze ups. But I think we've all become inured towards it. I mean, it hardly lasts a couple of seconds which by itself is quite rare. We're not flying mission critical space ships with our phones.
[Nexus 4 Original Android Development] markd0wn:
Do you know if any of the JSS ROMs with JWR Kernels, whether it's one of those you listed or a different one, use the CM keyboard?

CM's keyboard is not a 100% pure AOSP keyboard, but a modified one. It has language dictionaries that aren't available for the Google Keyboard from the store or the AOSP keyboard, and swype gestures work on more languages on CM's keyboard as well. So I was wondering if any JSS-with-JWR-kernel ROMs are using the CM keyboard.
[Nexus 4 Original Android Development] David9519:
Can somebody post a Screenshot with settings of interactive governor , please?
[Nexus 4 Original Android Development] Mercado_Negro:
And that, my friend, is a mess.
[Nexus 4 Original Android Development] getaceres:
Great. Has it been released for Mako?

When you have one release based on a newer branch that works flawlessly (as fas as software can work flawlessly) then use it for your custom ROM. Until then, stick with the code that works for your device.

---------- Post added at 03:55 PM ---------- Previous post was at 03:53 PM ----------

Why? Because people want to use code which wasn't tested on a device for that same device?

---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------

Why? Because people want to use code which wasn't tested on a device for that same device?

---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------

Why? Because people want to use code which wasn't tested on a device for that same device?
[Nexus 4 Original Android Development] pkelly517:
Yes. It's released.

What was never released was the source code to build a JWR ROM.

Correct me if I'm wrong.
[Nexus 4 Original Android Development] Mercado_Negro:
Exactly.

Google made a mistake, a few hours later they admitted it (sorry, I don't have a link at hand where JBQ talks about it), devs decided to go for it anyways and later on they discovered some problems but decided to tackle them down using different approaches. A couple of months later CM played Indiana Jones and made things worse.

It's one of the worst fragmentations ever in Android. Blame it on Google, ROMs Devs, CM and/or users; it doesn't take away the fact it is a mess.
[Nexus 4 Original Android Development] :
The beauty and curse of open source OS. This fragmentation/mess as you guys called enabled our devs to be more creative and the end-users more careful. So why the complaints. Let's have fun. It's Android, meant to be enjoyed this way. Cheers! :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] getaceres:
I don't find where they admit they made a mistake. I've found however this:

https://groups.google.com/forum/#!msg/android-building/sDovKMKTAiQ/u2BIcCmCtk0J

in which he states clearly:

Here are the details, with the builds that matter most:

JWR66L is 4.3_r0.9

JWR66N is 4.3_r0.9.1

JWR66V is 4.3_r1 - that's the one that goes on existing devices.

JSR78D is 4.3_r2

JSS15J is 4.3_r2.1 - that's the latest one, on the new Nexus 7.

The JW builds were split early, to shield existing devices from the risk of destabilizations introduced by last-minute changes for the new devices.

JBQ

which I think it's clear. The code of JWR (the one on existing devices) is based on 4.3_r1 and everything else has been towards the new Nexus 7. It might work or not in the Nexus 4 but try at your own risk. Well, it turns out it doesn't work well.

Then ROM developers came and thought new=better and all this mess. And yes, it's a mess but it's not something that Google needs to fix, it's something that developers need to fix (and some like PA did) while others (like CM) decided to carry on with the mistake instead of admitting they were mistaken.
[Nexus 4 Original Android Development] CMNein:
I can't recall a time where CM didn't use the latest branch, no matter what device it was "released" for. Nobody has "fixed" anything at this point, that's a workaround. As for running Franco on CM I've just forked CM's kernel prior to the commit that borked colours so when I do want to run Franco, I can without having to flash an additional zip.
[Nexus 4 Original Android Development] ticiano_arraes:
Sorry for the off topic, but anybody remember the color values for the s4 profile? I'm not so good changing this stuff
[Nexus 4 Original Android Development] marhensa:
made my day.. :D

Sent from Android device using Tapatalk Pro
[Nexus 4 Original Android Development] franciscofranco:
The values present in the gamma table are the only valid values. All the numbers in the spreadsheet that are different from the ones I have on my app are f****** wrong.
[Nexus 4 Original Android Development] GretaLewd:
Did I touch a nerve or say something to upset you :confused: or is it usual for the Mighty Franco to respond with language like that :rolleyes:

I only had a short time to post my original comment and I was trying to provide some feedback (as you have been requesting) based on my initial observations.

I was aware that the behaviour of your Gamma settings may be due to the fact that only those pre-defined values are valid. I just didn't have time to say so. I just posted what I saw.

If you are going to blow your top over this, I think you seriously need a holiday.:(
[Nexus 4 Original Android Development] dougiefresh36:
The new update is awesome! Love the intro and how it highlights and explains what's what like the android launcher. Very user friendly! I was thinking for the gamma tables. What if you grouped the grays,mids, blacks, whites into their own pop up box. So if I click on grays a pop up box will show to change grays for red, green, blue all at the same time. Since all red, green, blue get the same grays, mids, blacks, whites, why not be able to change all grays and so on at once in one box.

I hope that makes sense. I think it'll make it look cleaner maybe more user friendly too? Maybe?
[Nexus 4 Original Android Development] limeaide:
Spend a day in his shoes and you will see why its frustrating.

People like to blame and ***** but those same people hardly ever praise and apologize.
[Nexus 4 Original Android Development] franciscofranco:
?

What did I say wrong? :confused:
[Nexus 4 Original Android Development] franciscofranco:
Thanks for the nice words. Well, there might be users who want to change the colors of different channels, adding more dialogs etc is something I don't want to add :/
[Nexus 4 Original Android Development] The Gingerbread Man:
I think he got upset over your use of F word lol

[MENTION=3616704]GretaLewd[/MENTION] it's cool Franco's language is sometimes a little colour full but he's not mad, he just hasn't used any language for a while to multiple user complaint
[Nexus 4 Original Android Development] limeaide:
Spend a day in his shoes and you will see why its frustrating.

People like to blame and ***** but those same people hardly ever praise and apologize.

This is ridiculous not sure why this bug is not fixed. In the xda feedback forum its been reported several times.
[Nexus 4 Original Android Development] hughfollett:
[MENTION=3292224]franciscofranco[/MENTION] congrats on project pringles, it's really great.. With the previous stable version, I couldn't imagine something better! I'm curious to know something about colour profiles. I've just set up PA halfbreed on slim with the latest alpha following the spreadsheet. Obviously, I couldn't get the same numbers as the app didn't let me put them manually, but still I got the profile using similar numbers. Could you please explain how this is possible? Thanks in advance!

Also, I'm not blaming the app as I got the result I need, I just don't know how to motivate it :)

Inviato dal mio Nexus 4 con Tapatalk
[Nexus 4 Original Android Development] GretaLewd:
Ok, maybe I have taken your original reply the wrong way… that's always a problem with posts, tweets, emails :silly:

So, sorry if I have got the wrong meaning ;)
[Nexus 4 Original Android Development] limeaide:
Very big stick usually works to motivate lazy peons. :D
[Nexus 4 Original Android Development] franciscofranco:
I answered that a few posts up. If the spreadsheet values are not the valid then you gotta find some other profile. Thats how the hardware in this device works.
[Nexus 4 Original Android Development] franciscofranco:
Yes I've been constraining myself in my colourful language, I've already got a bunch of infractions and the Developers comittee told me to be careful. Might as well not piss them off or I'll probably end up banned sooner than later.
[Nexus 4 Original Android Development] The Gingerbread Man:
https://www.youtube.com/watch?v=N9qYF9DZPdw&feature=youtube_gdata_player

Meant in the best possible humour ;) was the first thing that came to mind :)
[Nexus 4 Original Android Development] magote:
Actually, I don't have the /sys/module/msm_otg folder.. How is it supposed to be created? I'm also experiencing severe battery drain and no usb connection, could that be because of not having some params defined on this folder that I don't have?
[Nexus 4 Original Android Development] ziddey:
You should read the post that you quoted....

/sys/kernel/fast_charge/force_fast_charge
[Nexus 4 Original Android Development] csunny95:
Will this kernel works for MIUI V5? If yes, which version shoud I flash?
[Nexus 4 Original Android Development] franciscofranco:
Read the OP. No MIUI.
[Nexus 4 Original Android Development] sordna:
I think FAQ #2 in the OP needs revising.
[Nexus 4 Original Android Development] known2u:
My experience with r191: Its draining too much battery, I checked the wakelock and not a single second of deep sleep. no app is causing this as I was using r184 before this and that was giving pretty decent battery time, at least when I was sleeping :) . I always use your kernel with default settings (maybe because I dont know how to change). Anyway flashed r189 for now, lets see how it goes.

Attaching picture, notice how its draining the juice when screen, wifi is off. Stock 4.3 JWR66Y rom
[Nexus 4 Original Android Development] DutchDogg54:
I would agree if this wasn't part of the OP & directly above the FAQ:
[Nexus 4 Original Android Development] franciscofranco:
You have something keeping your device awake, not Kernel related.
[Nexus 4 Original Android Development] Pipusz:
You must have something turned on or running in the background. Here's mine.
[Nexus 4 Original Android Development] sordna:
It's not just MIUI but CM also and other CAF based ones that have trouble lately. Saying that the kernel works with any ROM you can imagine is asking for trouble :)

Actually a *very* frequently asked question lately is indeed why the colors are broken in CM. So I think this should be added to the FAQ, and the references to CM higher up in OP should also add this disclaimer, perhaps even with a link to colorfix.zip

Anyway, some FAQ updates will save from a lot of repeated posts in this thread.
[Nexus 4 Original Android Development] DesertVelo:
Thanks for entertainment break... Amazing that Weird Al is still doing his thing!
[Nexus 4 Original Android Development] MaxFTW:
+1

Updating OP would be nice

== Sent from my CarbonMako ?? ==
[Nexus 4 Original Android Development] Arstoien:
Actually the path you wrote is the correct one. The one in the initial post I took from the changelog without checking it, and it's apparently old and non-existing.
[Nexus 4 Original Android Development] ziddey:
Yes, and right in what he quoted: "as some of the paths/instruction you have happen to be specific to other kernels."
[Nexus 4 Original Android Development] frozst:
I was experimenting and I noticed that limiting the GPU at its minimum I can't see any difference in performance... :what:
[Nexus 4 Original Android Development] drmspidi:
I can`t apply either over the 4.3.1 from CM right ?
[Nexus 4 Original Android Development] krazeecracker:
Not a chance, either it won't boot, or your colors will be corrupted.
[Nexus 4 Original Android Development] arlenwoot:
You can use the JSS tagged one if you also flash the colorfix zip linked in my signature.
[Nexus 4 Original Android Development] jmudrick:
Don't blame the kernel. 6 hrs SOT /17 hrs on for me, wakelocks minimal. Look elsewhere.
[Nexus 4 Original Android Development] franciscofranco:
Updated OP with red color text about CM and the colorfix thing - I'm not gonna answer any more questions about the matter.
[Nexus 4 Original Android Development] drmspidi:
Thanks Franco !!

Love your job !
[Nexus 4 Original Android Development] combatdeity:
Would it be possible to get a list of the commands required to revert the speaker back to stock values?

I find the speaker a bit loud on quietest setting, and mine distorts relatively easily.
[Nexus 4 Original Android Development] franciscofranco:
The commands are all over the place, I'm sure a simple search will tell you - I don't know them from the top of my head. I will reduce the gain to 14 or 13 the next time. 15 still distorts for me in the max too.
[Nexus 4 Original Android Development] Arstoien:
For the speaker you can use this:

echo 12 > /sys/devices/i2c-0/0-0058/fixed_gain

Or whatever value you choose. Current default is 15. If you want to look for other commands just do a search in the thread for "/sys/" and you'll probably get a bunch of results in the last 10 pages or so.
[Nexus 4 Original Android Development] sordna:
I would vote for something safe for all like 12, since we actually have users with unrooted devices using franco.kernel, so they can't change any settings :)

Speaking of, is it possible to have some of the kernel control files have fully writeable permissions (rw-rw-rw-), so that even unrooted devices can change some settings ?
[Nexus 4 Original Android Development] jimbohurt:
So sorry this is off topic but how do you know this information? Does he have an unofficial thread or something?

Also, R191 running great for me!
[Nexus 4 Original Android Development] franciscofranco:
Sure I can change the permissions :)
[Nexus 4 Original Android Development] sordna:
Wow, next step is make FKU not require root for at least some settings. Imagine the extra folks that will get the app !
[Nexus 4 Original Android Development] franciscofranco:
Pushed another FKU Alpha, this time with a new navigation drawer implementation which I think its better looking and easier to use all around. Also fixed a FC in the Backup&Restore. Tablet layout is also included in the new drawer :) Feedback is welcomed.

Well, most options in the app I can make them not use root, but then almost anyone who flashes Kernels is rooted so I see no point in doing that in the long run. Its a good point though!!
[Nexus 4 Original Android Development] Mercado_Negro:
I agree, 12 seems more appropriate but I've come to think "ok, but people can just decrease the volume" so maybe 15 is the best compromise between those who want a higher volume (keep it at max) and those who want it lower (just turn your device volume down until you're satisfied).
[Nexus 4 Original Android Development] SpasilliumNexus:
Personally I liked the previous layout better. It really suited with what Google is doing with the "hamburger" sidebar setup.

Maybe I'm becoming too spoiled with the redesign :p
[Nexus 4 Original Android Development] franciscofranco:
This is Google's layout too.
[Nexus 4 Original Android Development] NYLimited:
(sigh) I miss the old Francisco. It has been positively subdued around here. :D:D:D

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] jimbohurt:
So color control does work we just need to put the values in ourselfs now, correct?
[Nexus 4 Original Android Development] franciscofranco:
Until I release an update with working profiles - yes.
[Nexus 4 Original Android Development] TheKaptone:
How do I change to root access mode to be able to enable touch to wake
[Nexus 4 Original Android Development] ticiano_arraes:
so you will put the old profiles on Pringles? Great! Btw, I like the new interface better
[Nexus 4 Original Android Development] franciscofranco:
su

But please don't use that - the code is unfinished. I guess I'll remove that code until I can finish what I started.

Sure am. I'm mostly merging most functionality back until I can call if FKU again :) and while merging I either code from scratch or find a way to improve what I had written before ;)
[Nexus 4 Original Android Development] nexusmaniac:
Does anyone else have this problem? I've tried reinstalling the app, clearing data, rebooting
[Nexus 4 Original Android Development] nexusmaniac:
I kind of miss the 'hamburger menu' too :)
[Nexus 4 Original Android Development] anandbibek:
There's a difference between having distortion free max volume and volume lowered to avoid distortion

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
And that's the whole point of my comment. People have asked for a higher volume and that's why Franco increased it again but there's distortion so how can you please everyone? Well, for now, I think it would be good to find a sweet spot to start with and 15 seems to be a good compromise. Of course, we can look at it from a different point of view and say that Franco should just set it to 12 (real default) and those who want it louder will just have to get used to scripts for the time being (until we get controls in FKU). It's a tough decision either way.
[Nexus 4 Original Android Development] anandbibek:
You mean people like to listen distorted broken output at high volumes? Is it even legal? ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] wolf230:
Sorry, any option or idea on how to disable "doubletap to wake" ?

I've searched in tread, and in app...but nothing...
[Nexus 4 Original Android Development] ziddey:
not enabled unless you enabled it. look for init.d scripts
[Nexus 4 Original Android Development] nachordez:
Personally, I love the new one...

Nexus 4 / Cataclysm / Franco / V4A
[Nexus 4 Original Android Development] kingofcomedy:
Maybe a problem with your network or dns-server?!
[Nexus 4 Original Android Development] wolf230:
I've just downloaded it from franco's app and it'enable by default

Edit: anyway... how to disable it?
[Nexus 4 Original Android Development] philosophics:
Just a warning to everyone. Do NOT try PAC-man ROM in combination with this kernel. The latest nighties do not allow franco kernel to be used in conjunction. I learned the hard way, all day long. Forced to wipe device and not use the kernel of my choice. Looks like I'll be finding a new ROM to use. I just don't want to miss out on all the features I have grown to like/use. Ayone out there using AOSPAL?
[Nexus 4 Original Android Development] rosswaa:
Yeh mines the same mate
[Nexus 4 Original Android Development] Bill Gamble:
Franco, please don't remove it. I know you're not satisfied with it, but I've been using double-tap-to-wake since the beginning, and have no problems with it. I love not having to use any buttons to wake the phone.

---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------

echo 0 > /sys/module/lge_touch_core/parameters/doubletap_to_wake
[Nexus 4 Original Android Development] wolf230:
Please Sir,

be more specific how to...i'm not so used with programming code... :crying: