yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] LaboDJ:
The only changes to the code are in

mako_hotplug.c, to make it compile with gcc-4.7,

makefile, to change toolchain path,

mkcompile_h & defconfig to change version and kernel name.

There isn't any "functional" change, credit for all of the code is Franco.

News: [MENTION=3750240]stratosk[/MENTION] (Semaphore Kernel coder) made a new version (1.2.0), compiled with latest linaro prebuilt toolchain, gcc-4.8.1 and O3 optimization.

Due to the fact I'm not able to build gcc-4.8.1 from scratch to cross compile for N4 architecture, I'll wait until it will be present HERE or if someone can give me a hint, a guide, a link, anything would be much appreciated.

BTW I'm trying to compile it O3 optimized...

Let's see what happens! :victory:

PS: [MENTION=3292224]franciscofranco[/MENTION] your beta app is much better now, please change the back button behaviour to not exit so easily

EDIT: Guys I have successfully compiled with optimization O3 ... this time I do not think Placebo ... my N4 flies.

EDIT2: To compile with gcc-4.8.1 we have to change the allocator from SLUB to SLAB (don't know why, if you don't change it it stuck @ google boot logo), I think it's not a good idea (see HERE), SLAB allocator is very old, it's deprecated in favour of more efficient and simpler SLUB...
[Nexus 4 Original Android Development] TheDarkDefender:
Great. So faster binned,I'm guessing?

And let me know how it goes. I'm running r140 with -150. Faster binned.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] 3c:
Can you list actual voltage levels, I'm currently on another kernel so -150 doesn't mean much having no reference. I'll probably flash franco's kernel tomorrow and I'd like to compare stability of both kernels at their lowest frequencies.
[Nexus 4 Original Android Development] BrandoHD:
You keep trying, but FF isn't falling for it

Keep it up FF
[Nexus 4 Original Android Development] Arstoien:
It's strange, it happened to me yesterday too. Had to reboot to fix it. No problem since then. Could it be something weird with the kernel? I'm on AOKP (the latest milestone, not a nightly).

I won't be bothered if it doesn't happen again, could be just a weird one time issue.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Utini:
Nope its "fast" binned. Well -150mV seems to work fine so I will stay with it :)
[Nexus 4 Original Android Development] TheDarkDefender:
Nice.

Reduce voltage levels for each frequency level by 150mv.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] nachordez:
Seeing some of the last pages, I have to remember one of the most useful sentences in the cyberworld: don't feed the troll.

:D

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] scream4cheese:
You're on it right now. :p
[Nexus 4 Original Android Development] steviewevie:
54 is much better in what way? A bit OT, but interested in your views.
[Nexus 4 Original Android Development] franciscofranco:
1- No. PreferenceScreens have no real functionality. Even Google uses them to provide navigation in their settings apk.

2- Popups dont need ok/cancel buttons. Check screenshot.

3- Where is the spacing bigger than 48dp? Can you show me? I dont recall but I wouldnt be surprised if I had slipped something.

Sent from my device
[Nexus 4 Original Android Development] 3c:
Thanks for replying, first this refers to this initial post from another user and a my first reply trying to use actual facts.

1- Agreed Google use them in settings APK, but it's for settings, guidelines extract, very first line: "Settings is a place in your app where users indicate their preferences for how your app should behave". So if we consider the app being the kernel, then it starts to make sense, but then your app is no longer an app, barely a kernel settings, however I believe your app has functionality, which based on guidelines should be exposed through activities.

[ EDIT: Navigation in settings is a feature provided by API and is part of the guidelines to ease the app behavior configuration. Navigation can be used in apps too, but content and functionality must be activity-based. ]

2- Dialogs must have ok/cancel, popups don't have, but from guidelines: "Popups are lightweight version of dialogs that require a single selection from the user."

3- Taken from this.

Here is my own view on this:

1- Understandably, using preference fragments makes it extremely easy to develop an app very quickly automatically following standards and looking very good (the 48dp is definitely for something there!). What I find regrettable is that many users believe it's the standard, some call it HOLO/UI/Android guidelines, etc. But it's definitely not, this only provides content-less apps and is initially meant to configure app behavior. One of my users asked me to be HOLO compliant at some point and after investigating he wanted a settings-like app! Which is impossible when you offer actual functionality.

2- I still probably have a few button-less dialogs in my apps but getting rid of them along the way (80+ screens in the app, not counting dialogs). But I totally agree it's best to have ok/cancel in dialogs. However for the gamma selection, maybe a separate fragment would be best suited. I'm sure you have issues adding OK/CANCEL in that dialog for space considerations ;). Maybe not?

3- The 48dp is a very precise figure, so I made some tests, and it's definitely spot on: smaller makes the UI too skinny and hard to use, bigger the UI becomes dull and empty. Be it on any screen sizes or any devices.
[Nexus 4 Original Android Development] peikojose:
Thanks [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 4 Original Android Development] patsmike:
Hey guys, I noticed that when you just let your phone sit without touching it and watch the CPU freq (like in the device monitor of fku), it fluctuates quite alot with Franco's new hotplug driver - sometimes it even shoots up to 1.51ghz, etc (but mostly to 702, 1030) without being touched for like 10 seconds. On the other hand, the old mpdecision (eg. r111) would always just stay at 384 if you weren't touching the screen. Did frano mention whether this is done on purpose (maybe to get better scrolling, when you're not touching the screen) or is he still just ironing out the kinks in his new hotplug?

Also, I used "show CPU usage" in developer options and there wasnt anything taking up CPU other than background system stuff.

PS. I've noticed this more on the newest nightlies... Maybe that's what makes them so smooth!

Thanks, and thanks for the great work Franco
[Nexus 4 Original Android Development] Bill Gamble:
Just tried this. Mine sits on 384 MHz. I'm on r146, default settings.
[Nexus 4 Original Android Development] patsmike:
Appreciate it. Must be some app that looks inconspicuous but is actually causing CPU spikes. Its weird b/c its so reproducible in literally every nightly since r111

EDIT: must be something weird with my setup, I literally force closed every app in the background that is not a system app and I'm still getting spikes up to 1.18, 1.51 ghz. Running CM RC3.
[Nexus 4 Original Android Development] Cuzz1369:
Beta app:

Still getting bug where the back button writes the previous screen over top of the current one so two pages show at once.

Carbonized N4
[Nexus 4 Original Android Development] Danny.ns:
His point was that some nexus4 has 900mV as lowest voltage (for 384mhz), others have 850mV and some even have 950mV.

If you only say -150mV, he cannot possible know if you are rocking 800mV on 384mhz or 700mV on the same speed.
[Nexus 4 Original Android Development] Bill Gamble:
I'm on stock ROM, wifi. Actually, it's hard for me to reproduce my initial result. Most of the time, as you said, it rests on 384 for a couple of seconds then jumps up to some random frequency, then back to 384 for 2 or 3 seconds, then jump up, then 384, etc. Hmm...it might just be that it takes a while to calm down...I've just looked over at my phone and it's now been resting on 384 for more than 30 seconds.
[Nexus 4 Original Android Development] Leegalaxy:
I have a question. Where does this .54 radio come from? I really doubt it is any better than any other radio. And unless Google released it as part of a ROM upgrade, it is probably a radio for some other region. I have found radio performance to be mostly placebo... That said, I use .33 for the LTE.
[Nexus 4 Original Android Development] cobyman7035:
Dual core at 1026mhz vs. Quad 1500mhz... Night and day... But quad drains battery faster... 45mins SOT decrease

Google Voice via my r72 NeXus⁴ using XDA Premium
[Nexus 4 Original Android Development] manulemaboul:
Better gsm reception in bad signal situations and it comes from the indian N4.

Trust me, it's not placebo.

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] LibiSC:
O3 it's too much bugs will appear
[Nexus 4 Original Android Development] patsmike:
Yea its very finicky, once in a while it will just stay at 384 and not jump, but most of the time it does after maybe 10 seconds of inactivity. I think it could actually be the device monitor in fku, b/c if you monitor the CPU during inactivity in Trickster, you don't see any spikes at all!
[Nexus 4 Original Android Development] Bill Gamble:
That's interesting
[Nexus 4 Original Android Development] Cuzz1369:
Agreed

Carbonized N4
[Nexus 4 Original Android Development] zellleonhart:
Using trickster mod to monitor the activity really have less spikes but in my case, I have one spike to 1.35GHz (my max freq) every 10-12 seconds.

Beamed from my Paranoid r146 Nexus⁴
[Nexus 4 Original Android Development] franciscofranco:
1- I don't really understand what do you mean by content-less apps. So by having Preferences in your point of view the app doesn't have any content? You do know you can call a dialog from a PreferenceScreen using a clicklistener don't you? You know you can use a ViewPager to navigate between fragments in tabs? You can use a PreferenceFragment in Tab1 then use a different layout in the next fragment? I don't really understand what you mean.

2 - Why would I need to add stupid OK/CANCEL buttons in a dialog that has sliders to change values? The sliders gives you automatic feedback when you change them, so no need for a OK button for anything. Why would I add a CANCEL button if we have a BACK button in the nav bar in the bottom of the screen? I don't want the dialogs cluttered with non-sense. Heck I'm probably going to ditch any ListPreference/EditTextPreference in the future and use my own custom dialogs to match my theme. In the Backup/Restore function when you backup a Kernel you need to input the name you want for the file, so in that dialog I have a OK and a CANCEL button for obvious reasons.

3 - But those 48dp are used in what context? I don't really get it. I don't use many Linear/Relative/Frame whatever layouts in the app, so in my case I don't have that 48dp problem as everything is mostly handled by the Preferences interface.

If you can create a beautiful app following Holo Design why wouldn't you do it? I must be missing something in your posts, so if thats the case, I'm sorry.
[Nexus 4 Original Android Development] vjales:
franco, idk if this is rom related, hardware related, or kernel related, but does have any way to reduce the dead area of pinch to zoom? Because it justs starts zooming after some distance between the two fingers. Thanks if you know how to reduce/disable this! Keep going on f.k!
[Nexus 4 Original Android Development] TheDarkDefender:
Oh my bad. I really don't know much about uv'ing. Just recently ventured into it after a friend recommended. So what I did was, flashed the kernel and just changed the universal settings of voltages for all frequencies with Trickstermod. My point was reduce 150mv from the stock values (r140).

Sent from my Nexus⁴
[Nexus 4 Original Android Development] schnuffdroid:
same here. :confused:
[Nexus 4 Original Android Development] yethz:
6hrs SOT on my Nexus 4 is more than enough for me.

Thanks franco, though i get stutter while scrolling...

° Sent from Nexus 4 via Tapatalk

° Rom: AXI0M (5/31/13) / Kernel: Franco #146(Linaro)
[Nexus 4 Original Android Development] Traxex_:
You've got several reboots or?
[Nexus 4 Original Android Development] nachordez:
This is the point: there are no common stock values. For each one are different depending on the binning of your CPU. If your CPU is fast or faster, the stock for you is 850 for the lower speed. If you are on slow, it'll be 950. So, -150 means nothing for other people without knowing your binning (or the stock for your lower speed)

nexus4 / stock / Franco.kernel / V4A sound

gt-p5110 / CM 10.1 / Dhollmen kernel / V4A sound
[Nexus 4 Original Android Development] patsmike:
Yea now that I'm retesting, it looks like there are spikes sometimes, but it is correlated with a increase of CPU usage (although I'm not sure why it gets so high when its been idling for 10-20 seconds). I think that its just more sensitive to increases of CPU usage (unlike mpdecision was in r111) but this probably helps give the smoother scrolling, which was not really the case with r111 with mpdecision.
[Nexus 4 Original Android Development] fozzie:
My out of WiFi/in 3G battery is back to bring great with r.146 (after it seemingly being really poor with the last r.999 test build).
[Nexus 4 Original Android Development] nachordez:
... Or he has being flashing kernels crazily... :D

nexus4 / stock / Franco.kernel / V4A sound

gt-p5110 / CM 10.1 / Dhollmen kernel / V4A sound
[Nexus 4 Original Android Development] TheDarkDefender:
Well, I did mention the binning multiple times before. But i get your point. Didn't know it differed for different binnings. That cleared a lot. Thanks. :)

Sent from my Nexus⁴
[Nexus 4 Original Android Development] zellleonhart:
Despite the spike, I am still getting reasonably good battery (pure wifi of course, 2hr SOT and 54% left) with really smooth scrolling.

If it doesn't impact the battery much (and no excessive heat) I think I am fine with it.
[Nexus 4 Original Android Development] drawde40599:
Just ignore him, he's trying advertise his app on this thread knowing it gets millions of views ...
[Nexus 4 Original Android Development] franciscofranco:
Does it **** your user experience? If not then dont worry and enjoy your device. Its probably spiking because to read the freqs in real time it needs cpu work to read a file every second...

Know nothing about that.

Sent from my device
[Nexus 4 Original Android Development] 3c:
1- Doesn't change the fact that the guideline explicitly says: "Settings is a place in your app where users indicate their preferences for how your app should behave". Obviously your settings are not about how your app should behave. Sorry you felt offended by content-less app. As you point out settings have no functionality, hence I call that content-less, that's all I was referring to.

2- Why? Simply because it helps user decide to keep their choice or not. And again the guideline clearly states "Popups are lightweight version of dialogs that require a single selection from the user". There are no single selection in this particular popup to configure gammas.

3- The few places you don't use preferences, it's around 96dp. If you actually try to build a UI without using preferences/settings, you'll understand what this guideline means. Preferences are set to use 48dp consistently.

The point being? You tell me, you are the one who mentioned how some other app could benefit from following the Google's UI guidelines. Turns out it's the other way around.

As you seem to care a lot about Android UI guidelines, I'm surprised your own app doesn't follow them more consistently - Not talking about the settings-based UI, even a noob wouldn't be able to break the UI guidelines using those. However having a settings-only app is not following UI guidelines in the first place ;)
[Nexus 4 Original Android Development] drawde40599:
Ya mine stops and sits at lower freq also , it may bounce to 702 once every 30 sec or so but its not doing like what u described
[Nexus 4 Original Android Development] 3c:
At last, something that would make sense :D if it was not for the discussion I'm trying to have which will definitely turns bad on the app I'm trying to advertise. However I originally wanted to discuss those UI guidelines with Franco's, but ended-up with numerous useless replies.

As Franco points out UI guidelines have been made for a very good reason, so any discussions around those would benefit any developer, including Franco's app which is only discussed here.

EDIT: My single original post was about offering an alternative for a feature asked by a user not included in Franco's app. I've posted in other threads about the new gamma control in the app. faux123 replied himself to give me more information on gamma controls (very nice dev by the way), same on others threads.

Here, it looks like a sad story :(
[Nexus 4 Original Android Development] realfelix:
Sorry 3c, but this is a development thread for a KERNEL, not an app. It's not up to you to decide how he has to design his app. Those Guidelines are just guidelines, not strict rules in the first place. Second, if it was strict ruled and the app was that bad as you state it would get removed from the Play Store. Third, why do no apps get removed? Cause Google doesn't care about the design so why would YOU do? If it looks that bad, don't use it and don't look at it. End of the story. Continue and you will get reported.
[Nexus 4 Original Android Development] Testraindrop:
One thing I want to mention, Franco uses the Holo style in his app, that's why it looks good to the users and why they like it.

Simple as that.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] 3c:
Feel free to report me, I'm just trying to discuss an app that's being discussed here only. Don't forget to report the whole thread then.

Never said Franco's app is that bad, ever. I never mentioned any personal comment on the app. On the contrary I think it looks very good.
[Nexus 4 Original Android Development] exb0:
Honestly 3c, I couldn't be bothered about who follows guidelines and who doesn't. All that matters is that it looks good and it performs. Sadly yours looks like ****, to be honest. I've never tried it so I'm not sure how useful it is, but it looks horrific. The franco app on the other hand, looks really good. Especially with the new betas.

Sent from Halo.
[Nexus 4 Original Android Development] lorolouis:
Aha

That's right ... 3c. Basically, this is Franco's thread, kernel and app, he is the "Chuck Norris" or the "God" here.

Nothing else matters ...

You'll have many troubles if you go against, regardless how reasonable you think you are :)
[Nexus 4 Original Android Development] franciscofranco:
I will answer to your previous post accordingly when I get home ;) by the way this is not personal.

Yeah, faux, great guy.

Sent from my device
[Nexus 4 Original Android Development] realfelix:
My words.
[Nexus 4 Original Android Development] vjales:
http://www.youtube.com/watch?v=EU-N3mEOwU0 at this video this guy shows perfectly it.
[Nexus 4 Original Android Development] franciscofranco:
?

I don't even...
[Nexus 4 Original Android Development] Treatcon:
Just typing out some feedback and by no means is it meant to be disrespectful... sorry no logs so take it for whatever it's worth.

I had to go back to 140 for one reason... 145 and 146 was giving me constant network drops. Not sure about 142-143, but 140 surely works great for my network. I had to reboot my phone or go into airplane mode and back to get my signal back entirely and this is in areas where I normally have 4 bars of HSPA. I'm running the latest PA 27 May. My network signal since going back to 140 has been absolutely perfect for the past 5+ hours. I would lose signal when the phone went to sleep for extended periods of time. I did all the normal wipe Franco app cache, reboot, flash new kernel, wipe cache/dalvik cache and then reboot.

Not sure why, but only sure about how it affects my Nexus.

Thanks for all your work Franco!!
[Nexus 4 Original Android Development] lorolouis:
Check gain

IMO, the only difference between FireFox and the rest is the size of the screen area, considered as 1-finger touch.

I just tried the same thing (like the video) but instead of joining two fingers together on first touch I left 1cm between them.

In this case the zoom starts immediately - it doesn't "wait" ...
[Nexus 4 Original Android Development] akiv:
I thought that maybe T-mobile is messing with their antennas or something but I can confirm the same behavior:

Lots of network drops on 146 and 145, when I went back to 143, it's all good.

stock rom
[Nexus 4 Original Android Development] drawde40599:
Not saying going to magically fix your issue but the new 54 radio has been working great for me , maybe install it and see if 146 works better , i dont have a link but a search here for radio will bring it up
[Nexus 4 Original Android Development] franciscofranco:
I can vouch for this.
[Nexus 4 Original Android Development] trueblueram:
Just saw your g+ post. Conspiracy theories galore :D
[Nexus 4 Original Android Development] steviewevie:
All the N4 radios, including the new 54, are at http://xdaforums.com/showthread.php?p=36400943

Sent from my Nexus 4
[Nexus 4 Original Android Development] Karlo666:
[MENTION=3292224]franciscofranco[/MENTION] I just had reboot screen was freezed while switching trough tasks(Rayman jungle run ). I found last_kmsg but it's empty 0 bytes.
[Nexus 4 Original Android Development] franciscofranco:
Undervolting, overclocking, touch control? Need moar info.
[Nexus 4 Original Android Development] Karlo666:
[MENTION=3292224]franciscofranco[/MENTION] I use recommend values for color no undervolting, fast USB charge

, and governor set to boot (slightly speed), thermal throttle set to 50, haptic 50
[Nexus 4 Original Android Development] franciscofranco:
I don't have a clue. What rom?
[Nexus 4 Original Android Development] Karlo666:
[MENTION=3292224]franciscofranco[/MENTION] PAndroid but older version so maybe that's the problem
[Nexus 4 Original Android Development] alen1901:
Alpha/beta roms are great source of problems. And PA is one of them. I suggest some more stable ones. ;)

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] Karlo666:
[MENTION=3579148]alen1901[/MENTION] well I'm running pre HALO release see my sig for version in using ATM
[Nexus 4 Original Android Development] Treatcon:
http://www.krazyimage.com/android/N4/cwm-radio-mako-JDQ39E-m9615a-cefwmazm-2.0.1700.54.zip

MD5

0D556693DE6C6AF086D8D9A74A5DC164

Trying it out and uploaded to my site for ease of sharing.
[Nexus 4 Original Android Development] alen1901:
One more croatian here, good to know. :P

If i remember correctly that was like stable version, 3.15. But, it probably has some cm codes in it, and cm deffinetly wasnt "stable", until now, soon final version will pop out.

EDIT: also, did you have your phone pluged in charger when playing?

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] TheDarkDefender:
[MENTION=3292224]franciscofranco[/MENTION] Just read your g+ post. Sorry to hear this. I shall see what I can do about this in the RC forum.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Karlo666:
[MENTION=3579148]alen1901[/MENTION] no
[Nexus 4 Original Android Development] italia0101:
Yea I saw that too , ridiculous!
[Nexus 4 Original Android Development] alen1901:
Wierd, maybe one time glitch. See if it happens again. If it does and theres nothing in last_kmsg, reboot manually immediately again and check last_kmsg, attach here, maybe it will help.

Sent from Sparkling Nexus 4

What the.. XDA is really becoming strange place. No words to say.

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] lorolouis:
Isntclear

Isn't evident who did this ...

I mean ... check several pages back. Some (basically mediocre) people could never accept that the genius guys can be rude :) sometimes.

But only them though ... no one else is allowed.

Don't worry Franco ... this is the part of the game being unique.