yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] nachordez:
Yes, perhaps is the best solution.

Noriega and me were double checking old translations, which were full of little mistakes, or what seem translations from older texts that not fit the English actual ones.

Lots of corrections. I've voted his ones, also, for if been higher in score could give them preference, but it seems that Crowdin system avoids changing them without your explicit consent. Obviously, it's an absurd you have to check and confirm every change by any user in any language... No way!

So, if you could give him (or me if not) permissions for that revision, it would improve much. He did a nice revision work.

And afterwards you can take out the permissions again, if you want.

:thumbup:

Nexus 4, stock ROM, last Franco.kernel nightly
[Nexus 4 Original Android Development] allgsmnetwork:
Please link to me 666 v4 latest?

tnx
[Nexus 4 Original Android Development] PetritH:
For the love of fukin Jesus check two pages back
[Nexus 4 Original Android Development] nachordez:
Page 2923 you have the .IMG and a flashable .zip

But it took me exactly the same time it would take you going back to search for it :rolleyes:

Nexus 4, stock ROM, last Franco.kernel nightly
[Nexus 4 Original Android Development] PetritH:
Flashable zip its actually 2 pages back, but kids are lazy these days
[Nexus 4 Original Android Development] vjales:
After flashing the new RC cm10.1 I'll need to reflash the franco.Kernel correct?
[Nexus 4 Original Android Development] Net.silb:
Yes, after every ROM flash you need to reflash the kernel.
[Nexus 4 Original Android Development] Treatcon:
:rolleyes: For the lazy searchers... :eek:
[Nexus 4 Original Android Development] chrisgtl:
Constructive criticism:

Do we really care about a visual indicator to show us our CPU's are warm? If my CPU wasn't warm it would be because the phone is switched off or my phone is dead. I just see it as another component needing unnecessary power (even if it is tiny) for something we already know.

What I would like to see is some sort of LED colour scheme for the three top tier frequencies so I can see when my phone is under heavy load. Green = 702Mhz, Yellow = 1026Mhz and Red = 1512Mhz.
[Nexus 4 Original Android Development] gpvecchi:
Same for me, I find visual indicator useless... Is there a way to turn it off?
[Nexus 4 Original Android Development] nexusmaniac:
Read a few pages back and you will find your answer, people need to search before they ask :)

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] gpvecchi:
Ehm, I read twice latest pages, but I can't find it...
[Nexus 4 Original Android Development] nexusmaniac:
Read 5-10 pages back :)

Edit: it was about 17 pages back

You may disable it using the command bellow (as su):

echo none > /sys/class/leds/red/trigger

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] Danny.ns:
Hello!

I want to just give some feedback from a, kind of, very new smartphone user (yes a noob, "RUN, you fools!"). The N4 is infact my first ever smartphone, I've had a nokia 6300 up until december last year when I got the N4. As such, I only recently followed efrants excellent guide on flashing stock images, just to get an idea o how things like rooting and flashing parts of the "OS" works on android. I basicly just rooted but kept stock recovery/4.2.2.

But what I did want to change was the kernel, because on PC I can be called a "tweaker". Not a tweaker for the sake of tweaking, but for example I love overclocking CPUs, GPUs and RAM and love the idea that I can do this stuff on my phone as well if need be in the future.

Now, the feedback I promised;

From a new user perspective, the franco application is extremly easy to use, and flashing a kernel could honestly not be easier. Having it both download and flash it automaticly is.. I have no words on how easy it is. Great work!

The recently added overclocking features are also something I will enjoy sometime in the future. At this moment, I still feel the N4 is amazingly fast so I am not really looking into overclocking but still, it's for me a very nice option to have. Of course, no matter how stable I think I am, I would never save the settings to load at boot up ;)

A feature with the kernel that I didn't think I wanted, but ended up with LOVING is the ability to change the colors of the screen. I loaded some pre-set I found here on XDA with very nice colors (saturated - if you will), but I changed RGB values to get 2.2gamma on RGB (used a display tester app to check that). And I honestly feel that I have improved the screen 10x. :good:

A short note on the "recommended settings" for colors; This is obviously SUBJECTIVE. And on top of that, all screens are different so it might look compleatly different on others screens. But the recommended settings had kind of alot of "banding" on my specific screen. Although the colors were very deep/nice (which i liked and hence actually bothered tweaking the screen in the first place). Again, this is very subjective and shouldn't be considered "feedback", just a note from how it looked on my phone.

I've used the R134 kernel for a week or two, and it has been just perfect so far. I feel that your kernel has indeed improved my phone in many ways. I'm basicly using the default kernel options; with the exception of tweaking the colors of the screen and lower the haptic feedback to 0 (disabled).

Oh! A super small note; The haptic feedback option in the kernel app actually renders the option in standard android options mute. It took me a minute (oh, dear god!) to figure out why the phone was vibrating despite me having turned that off in standard android options. I'm not sure this can be fixed even so.. probably is so by design.

Keep up the great work.
[Nexus 4 Original Android Development] ChongoDroid:
It's not actually 1.9ghz, that's why.

Sent from my Nexus 4
[Nexus 4 Original Android Development] 75markus:
For those who don´t like the new LED triggering , here´s a flashable zip to turn it off.

It´s a simple init.d script which is executed every reboot with the code "echo none > /sys/class/leds/red/trigger" to turn it off.

It works with Kernel #666 from 08.05.2013, it won´t survive a ROM flash.

to delete it : use a root file explorer and delete system/etc/init.d/79stopled or reflash your ROM

This file is also available in my mediafirefolder
[Nexus 4 Original Android Development] kyokeun1234:
For people who's keep asking for the latest r666 builds, go to franco's profile, go to statistics, go to show all the posts, find a post that might have the latest test build in it. It's not that hard people. Let's not clog this thread up by constantly asking people for the link to the test build.

On the other hand, even though it has been only a day since trying v4 out, I think it's safe to say that battery life seems to be either same or improved. I still get 4 hours screen on easily with little bit of 3g usage and little bit of gaming. Performance is still amazing. Never have been disappointed and this build doesn't disappoint me either :)
[Nexus 4 Original Android Development] gpvecchi:
That's exactly what I was searching for! Thanks!
[Nexus 4 Original Android Development] Arstoien:
I'm just gonna put this out there because I don't think it's been said enough: the new hotplugging logic is much smoother than the previous (used in the latest nightly and the first r666 after that). Easily visibly smoother.

If it was up to me, I'd keep the new logic instead of the simpler one used previously.

I know some of the elements of the latest r666's can be implemented to the old logic (like the freq boost on touch, 2nd core online on swipe and the 4 cores online on screen on) and improve the smoothness of the old logic without introducing the new threshold for offlining only one core, but I feel this way is smarter and I bet that is also contributing to the reduced stuttering.

The only downside is that it's running slightly warmer (really, not that much) but that's not bothering me whatsoever.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Underground_XI:
UV a bit to run cool.
[Nexus 4 Original Android Development] zephiK:
Agreed lol. Arguing over the internet gets people no where. Especially on XDA, people don't like admitting that they're not right, everybody to their certain extent believes that they're right. Myself included, no one is exempt :p
[Nexus 4 Original Android Development] albundy2010:
What in the world is going on here? So now standby time is irrelevant and is cheating battery stats or whatnot? Smh.

It is a good thing that you can go to work / school take a nap etc and not have your battery just drain away. It is up there with screen on time and voice calls for importance. Depending on the user it may rank at the top.

How in the world would using the phone non stop for a hr. Then idle for 4 hrs use for hr etc inflate screen time anyways.

But now I see this bs oh pshhh standby time and oh you probably had a black image on the screen the entire time crap. Speaking of which. Displaying black consumes the most battery on a LCD display. This is not amoled. The amount of fail and plain stupidity is on the rise today.
[Nexus 4 Original Android Development] mobilehavoc:
You're missing the point. Of course standby matters. But its stupid to count overnight as part of it because you're not using the phone. This inflates the standby and the other people get worried they're not getting the same usage so either the kernel is bad or some nonsense.

At the end of the day how you use the phone is unique and will rarely be similar to someone else randomly on here. What is the point of posting some crazy battery screenshots except as some type of epenis size contest. There's no reason for this in a kernel thread. Let's stop with the battery screenshots.
[Nexus 4 Original Android Development] Devilman539:
Couldn't agree more. I'm not going to respond to pointless flaming or trolling but I as well as many others should and will be reporting this behavior. It's completely unproductive and erroneous. Please lets get back on topic. There should only be posts for bugs/logcat reporting to assist Franco build a better kernel. This isn't a contest on who's phone is better. Thank you.
[Nexus 4 Original Android Development] Testraindrop:
Um okay...

Franco now that r20 is stable, as seen on all the nonsense in here, what are you planning to include in the next few builds? ;)

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] Vanhoud:
I used to enjoy checking on this thread throughout the day too see what's going on with francos awesome kernel....until today :/

Sent from my Franco'd Nexus 4
[Nexus 4 Original Android Development] jarjar124:
Guys take this to somewhere else!!
[Nexus 4 Original Android Development] squadz:
Seems that having LTE enabled is a huge trade off for battery. I'm not getting anywhere near anyones times.

Oh well, I'll take LTE.
[Nexus 4 Original Android Development] derPianist:
Guys. Please. I was offline for about 3 hours.

Then I opened this thread to check it for useful information.

First I thought:

Then I continued reading a few posts:

So, in general a few posts where just so damn useless and i was just like:

A few people should just:

But as always, reading XDA is:

Seriously, when you are not interested in something, don't start a fight. Just move on!

So, we don't have to get angry and just stand there and think:

In general it is always a good advise to act like this:

So, enough of hijacking Francos Thread! Let's get back to the nice and friendly atmosphere as always. PLEASE. :):)

via Nexus 4 from Lampukistan.
[Nexus 4 Original Android Development] jarjar124:
That was one long post Lol!!
[Nexus 4 Original Android Development] ben_pyett:
I'm personally hoping that he removes the battery screen and screen Shot options temporarily so that we can get back to discussing this kernel. Back on topic.... please?

I'm Loving #20 , as someone already said hours and unfortunately pages back now, this versions had the speed of #14 with the battery of #19.
[Nexus 4 Original Android Development] albundy2010:
I am not missing the point. Standby time is standby time period. It doesn't matter if you're sleep or at work or in school etc.

I do not care for the battery stats post myself. I hardly ever do them. I do try and add in my usage when I do those type of posts.

This entire I don't use the phone the way x does, why does x even have a smart phone is absurd. Take that useless crap somewhere else.
[Nexus 4 Original Android Development] ayamary:
hi is everyone having a good christmas in this thread
[Nexus 4 Original Android Development] estallings15:
Apparently not. Some people are fiesty today. Franco is going to crap a brick when he sees his thread. I hope he gets it locked for a week.
[Nexus 4 Original Android Development] scream4cheese:
Lmao. That was excellent!
[Nexus 4 Original Android Development] Ballastatuz:
For me I think the battery is pretty much the same as the stock kernel. This just runs smoother. When I use it heavy I still get like 4hrs screen on 6 hours and some minutes in total.
[Nexus 4 Original Android Development] scream4cheese:
I think everyone should just stop talking their battery life all together. :(
[Nexus 4 Original Android Development] ipnekgs:
This. All the people with amazing battery life have excellent network coverage. I've never had green for network.
[Nexus 4 Original Android Development] superbobup:
Franco, you need to stop making such a great kernel. Seems like certain people get offended because they can't get the same amazing results as others.

You guys realize you're complaining about the REPRESENTATION of BATTERY STATS. Can you get any more ridiculous? Just use your phone as you like it. If you want better performance or battery, come check out the thread to get some advice. Posting in here trying to hate on others for the way they use their phone is one of the most childish ways anyone can act.
[Nexus 4 Original Android Development] alewis2k12:
Lol so tired of hearing about battery.... If you want super excellent battery....keep a charger in your back pocket.....and you too shall have excellent battery!!!!!
[Nexus 4 Original Android Development] hotnikkelz:
Got some severe bugs that I've never encountered before. Was playing around with trinity 125. Every time I tried to go into the red green or blue color categories I get a crash message that the updater stopped. It doesn't however crash the program. It stays in the app but just prevents me from going into the categories. Sorry I don't have a log to give I disabled it.

Went to reflash Franco kernel and got a series of crashes. First from system UI, then gapps process then another which I can't remember. The flashing was successful though it just gave those messages after I tapped bring it on!
[Nexus 4 Original Android Development] pikachukaki:
I think touchscreen drivers is inside kernel so may i ask cause i see a thread for better touchscreen...is franco using E015 or E027 driver??and also if its using 027 anyone using the 015 drivers and notice better touchscreen scrolling??
[Nexus 4 Original Android Development] :
I've just tested the latest r666 and it's pretty good. From smoothness perspective, there's a definitive improvement over r134. Most importantly, it allowed me to undervolt to up to @ -175. The red light temperature indicator is a neat addition.

Cheers to Franco..
[Nexus 4 Original Android Development] Arstoien:
Yes, I have. In fact I cannot get it to hit the thermal throttle threshold in heavier games. I just mentioned that it does run warmer because sometimes I feel the warmth in my hand from things like quick typing for IM and I haven't felt it before.

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
Definitely agree, latest r666 is a step in the right direction with the improvements in performance I'm seeing, can't say anything about battery life yet :fingers-crossed:

Lemme add the LED screws up colors for CM LED kanged in many ROMS, but its pretty neat though
[Nexus 4 Original Android Development] franciscofranco:
Your rom is ****ed, reflash.
[Nexus 4 Original Android Development] franciscofranco:
Just another reason for me to hate CM.
[Nexus 4 Original Android Development] fozzie:
Not for me thanks. I don't give a rats what frequencies the phone's running at; I expect it just to work. It's not like you're going to be staring at the LED and when it goes yellow, go "oh my, the CPU's starting to get busy. I need to investigate". :)

On the other hand, I can see that an indicator that says your phone is about to melt might be more useful.
[Nexus 4 Original Android Development] yethz:
Adding LED feature in your kernel isnt a good idea IMO. No offense but I love your kernel since u added touch sensitivity.

But adding more for me is bloated already.

I want a kernel that works and simple, no fuzz or buzz or what they call it.

This is only my opinion, i dont have the right to what u want in your kernel.

Again, its an honor to have your kernel in my nexus 4.

EDIT:

Theres an app for led functions, not to mention almost custom roms have it also, i think u should just leave it to those apps.

- Sent via Nexus 4 with Tapatalk

- (Sorry for my bad english...)
[Nexus 4 Original Android Development] nachordez:
I'm not sure about that, but I feel like last 666's been a bit better for me on battery draining. And I seem to be in time when I am on bad/no signal. I'm every morning about 2½ hours in a place with very bad signal, many times showing even no one. And that uses to be very draining for battery. But this last days it seem to be better. It's not scientific, of course, and I don't know if there are any improvements that could affect that, probably not, or just random circumstances, but I had this feeling

Nexus 4, stock ROM, last Franco.kernel nightly
[Nexus 4 Original Android Development] rysup:
I'm getting the occasional stutter pushing the back button but so far so good overall :)
[Nexus 4 Original Android Development] pikachukaki:
Bit offtopic..can you share the name of theme/font :P

also [MENTION=470754]Franco[/MENTION] as you are here can you answer me about touchscreen driver?
[Nexus 4 Original Android Development] nexusmaniac:
Which ROM is this?

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] Slymobi:
Been heavy ish usage trying to run battery out. Games,resores and reboots,xda etc etc. Around 40 % brightness with data only. ..... Not too bad.

Sent from my Nexus 4
[Nexus 4 Original Android Development] rysup:
Theme is darkjelly by djdarkknight96 and font is caviar dreams.

Edit: https://www.dropbox.com/s/42gdqaqqntb09rr/CaviarDreamsFont.zip

Jellybro.
[Nexus 4 Original Android Development] LibiSC:
Plz use the spoiler tag for images.... Thanks
[Nexus 4 Original Android Development] scream4cheese:
You're on your phone. It doesn't matter.
[Nexus 4 Original Android Development] nexusmaniac:
How do you do that? Do you just put

Spoiler content hidden.

So that's how you do it :)

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] LibiSC:
Actually it only matters when you are in your phone... It's just common courtesy
[Nexus 4 Original Android Development] steviewevie:
This has come up before and the touchscreen drivers are stock, though with sensitivity improvements. Franco has before warned about problems with using the old driver. Try searching for Franco's posts and "e015" and you should find some stuff.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Kernel works as it is. I just added this new LED code because I like the added functionality. I only cherry-picked and did 0 changes, but my plan is to add more real value from it and make it customizable. I don't add stuff randomly, there is a purpose for this addition. Since this latest r666 is not a real nightly I don't have any problems in throwing whatever I feel like throwing.

Thanks for the feedback nonetheless.

Yeah I don't know how many times I've answered that... Thanks for replying.
[Nexus 4 Original Android Development] pikachukaki:
Im quite boring to search so i stay with your respond i just saw the thread and asked all this time im having n4 with franco noone else ask about this!thx btw
[Nexus 4 Original Android Development] Net.silb:
[MENTION=3292224]franciscofranco[/MENTION]

Hey Franco, I told you that there is a problem with frequency boost on touch and you said you will look in to it, have you?

Anyways, the problem is that on most touches, not swipes, the CPU does not boost you can check for yourself using system monitor as I did, for example touch an empty spot on the screen or type on the keyboard and you will see. I know the code is there, you showed me, but something is not working right...

Here's an example screenshot of the problem:

What do you think?

Thanks.
[Nexus 4 Original Android Development] franciscofranco:
Well... if there is no X or Y variance based on the original touch position I cannot detect a touch event in the work thread that does all the operations. If it moves a pixel at least I can do something, but without a difference its quite impossible, I think there is no driver logic for that. I've looked through the code and either I'm blind or I don't know how to detect that touch like that.

I'm going to do some more debugging.
[Nexus 4 Original Android Development] Net.silb:
Hmm, maybe there is a way you don't know about because as far as I remember from using mpdecision, it knew how to boost the frequency on a touch like that... I'll look in to it...
[Nexus 4 Original Android Development] pikachukaki:
why do you want a boost on single touch to read your fingertip at 1ghz?
[Nexus 4 Original Android Development] kara mustafa:
M2 should work good with cm 10.1 rc1 right?
[Nexus 4 Original Android Development] franciscofranco:
MPdecision is completely different... its tied to the Android framework and communicates with the Kernel via ioctl interface and the PowerHAL using sockets, this is solely based on the Kernel driver and the touchscreen firmware.
[Nexus 4 Original Android Development] nexusmaniac:
Yes, Franco kernel works with any ROM

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] pikachukaki:
Do you find a result on whats better less cores more ghz or more cores less ghz for performance and consumption tha you talking about a week ago?
[Nexus 4 Original Android Development] Net.silb:
This may be a lot to ask and a lot of work for you but, why don't you make your own mpdecision and make it work like you want it to?

Seems like the Qualcomm/Google devs think it's the best way...
[Nexus 4 Original Android Development] franciscofranco:
If I touch the screen without X/Y variance it detects a touch in the Kernel driver. I think all those apps to monitor frequencies in real life are not fast enough when reading from the Kernel exported files to show the boost. I already asked Christian to add a functionality to refresh the monitor every 10ms to debug stuff like this.

Dunno, but current code is 1 core -> 1026MHz boost, 2 cores -> 702MHz, boost. Seems balanced
[Nexus 4 Original Android Development] franciscofranco:
That is what I'm doing here with this driver. I'm not a big fan of userspace binaries managing this ****, I prefer Kernel level above all and I'm currently happy with the current scenario... and I'm having fun.
[Nexus 4 Original Android Development] pikachukaki:
so why im feeling latest 666 bit laggy than 134?
[Nexus 4 Original Android Development] Net.silb:
I understand but isn't it easier to implement it like mpdecision is implemented, doesn't that give you the opportunity for more functionality?

---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------

And, I checked and it's not a problem with system monitor... because if I touch the screen with a very short swipe, system monitor does show the cpu boost, so its really not boosting the cpu on just a touch...