yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] yokuyuki:
Just curious, what did you use to measure current usage?
[Nexus 4 Original Android Development] Cuzz1369:
Well logically it should be the updater which is the main purpose of the app. Makes sense to me. Don't worry I won't be mad if you don't use it lol.

Carbonized N4
[Nexus 4 Original Android Development] nachordez:
Yes, both options would be nice.

I not very found of pop-up, personally. I feel this solution more 'aggressive' than my proposal of returning to main screen... But it's just my taste, and both would do. :thumbup:

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] drawde40599:
new beta

Just downloaded the app beta update and its looking better and better , it feels snappier also . thanks !
[Nexus 4 Original Android Development] Luigiesin:
Check your PM

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r146-Linaro

T-Mobile
[Nexus 4 Original Android Development] nachordez:
Bug in FKU upgrading

When I upgraded to new beta version, the app started in default theme, instead of red holo. But, the important thing was that it didn't react when I tried to press any option in the side bar. I could open and close it, and the new start page was there, but when I tried to press any other option, it didn't react. Blue was still marking 'Principal' and nothing happened.

I had to unnistall and install it again. And then, some of the previous settings where still there (like headphone gain), and some other didn't (like fast USB).

Other than that (not too bad, anyway), nice improvements! New principal is nice, going out of system monitor having the side bar is much more logical, color ticks in selections are nice, as are animations... As always, good work.

Sugg:

Remember the LEDs question ;)

What about back button taking you not out of app (I'm mistaking so much trying to go up to a nonexistent previous level) but to principal screen (and then exiting from there) or an 'exit yes/no' popup as [MENTION=5088242]Cuzz1369[/MENTION] proposed?

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] oSandmaNo:
offtopic but fransisco has now exactly 46,000 thanks :D

I made it 46,001. :)
[Nexus 4 Original Android Development] Girn:
I can't wait for you to add gamma control in your kernel Franco.. I can't stand the washed out colors of the stock settings.. I'm using fauxclock on stock kernel and I got gamma set almost perfect... Wish I was on your kernel :(
[Nexus 4 Original Android Development] republicano:
I have been looking all day for information on the governor control in the app, only found a few in the gnex thread, anyone got links for me to read?

first cycle and the battery has been great

thanks

edit

found some info at tweaks/kernel governers.

if you want to save battery life, underclock and change the high speed load to 80-90 and frequency and test foreground ui and cpu load with perfmon from chainfire.I haven't noticed any terrible lag, performance is above 50%,

goal is to easily pass 5.30 hours display on with butter.
[Nexus 4 Original Android Development] gee2012:
These custom colour settings by Monkeybrew work fine for me so far.
[Nexus 4 Original Android Development] tututu08:
Where did you get the source of the patch or the information about this fix ? ;)
[Nexus 4 Original Android Development] co0kie:
Sorry for the newb question but anyone can advise how to play with "alternative UI" as mentioned on Franco's first post? I'd like to bring the menu button to the bottom (next to home just like my Nexus S)

Other than that this kernel is awesome working super smoothly underclicked at 1.25ghz.
[Nexus 4 Original Android Development] biffsmash:
I'd guess from Qualcomm duh lol
[Nexus 4 Original Android Development] Ibsonic:
Yes but where we can see those patches/updates.. I'd like to know that too..

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] Harsh:
You can see all what there is by Qualcomm in here https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary
[Nexus 4 Original Android Development] ahalford:
God bless you, Francisco, I love your work :cool:
[Nexus 4 Original Android Development] Taxiback:
Franco, any chance we can get a notification pop up on the phone for those of us using your app when a new kernel is released?

Only yesterday you said: " r21 is going to be up for a few days without a new build, I would like set up a stable release for users to enjoy if they want something stable and working great. "

Low and behold the very next day we have an update. It would be nice if we didn't have to open the app or log in here every few hours. ;)
[Nexus 4 Original Android Development] Vangelis13:
It is profitable to have users coming in here to (hopefully) read the latest instead of just coming to post their questions about undervolting & swypetowake. No thanks.

P. S. Imagine he'd just post an image instead of a zip, what would you do then..?! :eek:
[Nexus 4 Original Android Development] immunityx:
R22 is perfecto!

I thought my N4 display was perfect before but with monkeybrew's color settings they are perfect. :good:
[Nexus 4 Original Android Development] Taxiback:
All we get here is "wow, it's so smooth" or "wow, great battery life" There's not a lot else except news of a new build. We've purchased his app and there's not a lot you can do in it but update the kernel so a simple notification would be helpful in my view.

This is not a thread with Beta testers giving info on what works and what doesn't, Franco gives it to us when he sees fit, if anyone asks about changing the settings in his app he says default is best so there's nothing to do there either.
[Nexus 4 Original Android Development] Vangelis13:
"there's not a lot you can do in it but update the kernel"..? Come on mate.

P. S. Shame you missed all the other posts in here..
[Nexus 4 Original Android Development] Taxiback:
The app is called "franco.kernel updater" not franco tweeks! All I'm saying is it would be nice if the "kernel updater" notified us of an update without having to open it and check every day.

When he brings out a tweeks app it would be nice to overclock the cores.

So what do you do from within the app? Have you managed to find anything on the www saying what each setting does? It's all a bit hit and miss, if you ask you get a try it and see. He's not even bothered to update the description on the play store as to what you can do on the Nexus 4. All we get is a warning.

I take no responsibility for any fault or damage caused by any procedures of the app. No warranties of any kind are given.
[Nexus 4 Original Android Development] stankyou:
Same here until I swapped the top and bottom values. I was like whoa sh*t!

via xda app
[Nexus 4 Original Android Development] colobos:
Wake lock is still present for me will test throughout day but 3 mins of it from 40 min total up time
[Nexus 4 Original Android Development] CaspaTheGhost:
Same here, crazy yellow for me.

I can't beat my own settings of;

225

240

255

Proper white whites...

Gonna flash r22 now, but from r21s performance and the Qualcomm fix I smell a milestone?!

Thanks as always Franco!

Edit: and on r21 I don't have any lag in tapatalk, just tested on 3 pages and I have mine set to the max number of posts displayed per page.

Sent from my Nexus 4
[Nexus 4 Original Android Development] co0kie:
Great color recommendations! Changed this to my default one. The white is much whiter.
[Nexus 4 Original Android Development] Monkeybrew:
That is really good too if you want a cooler tone. Not as accurate but you get cooler whites. The main thing seems to be to lower the green to get rid of the greenish tint to pictures.
[Nexus 4 Original Android Development] nachordez:
Damm! What has this man done that I have not to get that much?? :confused:

:D:beer::beer::beer:

Good work, Francisco!

Nexus 4, stock ROM, last Franco.kernel nightly, V4A sound
[Nexus 4 Original Android Development] mammenj:
[MENTION=702102]LaboDJ[/MENTION] Were there any changes to the kernel source? If so, could you publish the changes?
[Nexus 4 Original Android Development] sam razzy:
So all is about cleaning the Franco app data ? :D I thought I must clean all the app data... Hmm... I felt agony on my ass.
[Nexus 4 Original Android Development] Burlito:
I don't use the beta-app of Franco's Kernel Updater but i may have a suggestion..

Sometimes when the app tells me there is a new update, i'm so excited that i just hit "flash automatically" and forget to check the option to clear appdata before.

So wouldn't it be nice to give the user a 3rd button after flashing? "reboot now" "no thanks" and "reboot and clear data". Something like that..
[Nexus 4 Original Android Development] sNoxious:
Yea, just FKU if needed or recommended. Yep, you don't need to. :good:
[Nexus 4 Original Android Development] Cuzz1369:
I've asked for that a few times already. No response yet. Maybe he doesn't like that idea.

Carbonized N4
[Nexus 4 Original Android Development] thebryceee:
Maybe before asking to exit, pressing the back button opens the navigation drawer to let the user know that they maxed out the back button before exiting the app.

Edit: the way it behaves when pressing back from System Monitor. But instead of fade transition, the navigation drawer gets pulled out as if the user swiped from the left side if the screen.

Edit 2: the drawer looks much better with just the first letter capitalized :D
[Nexus 4 Original Android Development] The Gingerbread Man:
Latest beta app update screen colour tuning causes force close on galaxy nexus. Create and set power mode galaxy nexus caused force close too. Over all much improved look
[Nexus 4 Original Android Development] nachordez:
I was proposing something related, but that solution is much better than mine!

+1 for that.

nexus4 / stock / Franco.kernel / V4A sound

gt-p5110 / CM 10.1 / Dhollmen kernel / V4A sound
[Nexus 4 Original Android Development] zellleonhart:
With r146 I get a high amount of 1.35GHz despite the same usage manner with r145... See screenshot, almost as high as 384MHz.

Is it normal? Or it is just me being paranoid lol

Beamed from my Paranoid r146 Nexus⁴
[Nexus 4 Original Android Development] thebryceee:
What's your input boost set to
[Nexus 4 Original Android Development] thebryceee:
The order of mine is 384, deep sleep, 702 then 1512
[Nexus 4 Original Android Development] zellleonhart:
1188MHz.. I didn't change it. Maximum CPU frequency I capped it at 1.35GHz instead of 1.5GHz.

Now 42% left with 2hr 13min SOT with 50% WiFi on. Acceptable but r145 was better.

Beamed from my Paranoid r146 Nexus⁴
[Nexus 4 Original Android Development] thebryceee:
Just realized it touched 1620 for a total of 6 seconds and my max frequency is set to 1512 lol

Maybe some people who has random reboots, check your CPU states and see if your processor is touching higher frequencies than your max. Maybe your phone doesn't like OC and those brief touches cause reboots.
[Nexus 4 Original Android Development] ciprianruse88:
Let stock settings.here everything works fine
[Nexus 4 Original Android Development] admiez:
I have not used the beta app yet (I assume Google+ is required) thus I was not sure of what was this a solution being suggested for. But, in general, I don't think the Back button should do what you describe. My comment on this applies to all apps. I think that what Google is trying to do with the Sidebar at this point is to bring consistency to all these different ways of showing/hiding it that current apps are using. It seems to me that their idea is for the Sidebar to be available from anywhere in the app and made visible when there is a:

- Swipe from the edge

- Click on the UP button (only from the Top most activity in most cases).

And to be hidden when:

- Swipe to the left on top of the side bar

- Click once again the UP button

- Click of the Back button

You may have noticed that, currently, apps have other ways to show/hide their implementations of a Sidebar, such as:

- Horizontal swipe (not just from the edge) (e.g. Youtube)

- "Menu" button at the top (No use of UP button or swipes) (e.g. Hike)

- Back button (e.g. Tapatalk 4 beta)

These usually create inconsistencies and the user needs to remember how each app operates in its own way. Even Google is guilty of this, and you see that their latest apps that make use of a Sidebar seem to be moving to be consistent to the way I described above. Their Shopper app is a clean one, the Drive app follows the same with the exception that the UP button has multiple levels, thus it can be used to trigger the Sidebar from other activities down the hierarchy in addition to the swipe from the edge.

In my opinion the Back button should always take the user back to what was the previous view within the app, e.g. go back to previous activity (just like the UP button), dismiss dialog, leave the app, etc. Which is why it makes sense for the Back button to hide the Sidebar when it has been made visible. It should also just take you out of the app when you're at the main screen.

I assume that the issue for which you are suggestion solutions is that you are getting out of the app when you didn't expect that to happen (the navigation flow was inconsistent). I think I read the app opens up with the Sidebar being made visible. I'm assuming that once you enter one of the sections and use the Back button it gets out of the app. I may be wrong, but it is what I pictured from the comments. If that is the case, you're being thrown off because you expect to return to the main screen instead. One always expects the Back button to just go back. I guess the problem is that there is no main screen per se at this point. The solution might be to just have a real main screen, it could be the Updater section itself. But, opinions will differ on that, just like he said, every one has their own go-to section of the app. If it was me, I would probably just use the main screen to display the currently installed kernel version or something of that sort.
[Nexus 4 Original Android Development] nachordez:
I agree absolutely with you. As a fact, my proposal at first was exactly what you say, to go to main screen. But, if you try the beta, you'll see how much useful would be to open the drawer. Anyway, you're right saying that thus would not make too much sense about what the use of that drawer is intended from Google. So... I return to my initial preference of returning to main screen.

But both options are for me better than the present behaviour, so I would love Franco doing whichever of them.

nexus4 / stock / Franco.kernel / V4A sound

gt-p5110 / CM 10.1 / Dhollmen kernel / V4A sound
[Nexus 4 Original Android Development] thebryceee:
In the beta app, when you press back from one of the main screens, it exits the app and it gets frustrating after a couple times. I think it would be more beneficial to pull out the navigation drawer to tell the user that there's no more levels to back out of and presents the menu instead of exiting.
[Nexus 4 Original Android Development] admiez:
What is the present behavior? I don't know if what I gathered from the various comments was correct, since I haven't used it. Have you seen the Tapatalk 4 beta app? It throws me for a loop the way it handles the Up, Back buttons and its Sidebar.

Edit: Previous post answered my question. Thanks!
[Nexus 4 Original Android Development] schmitzekater:
Guys, I'm facing some strange issues running SaberMod from 27-05 with Franco's r146.

Woke up today and had to enter my sim-code to unlock. No biggie, I thought. But in the last 10 minutes i had to re-enter it 5 times without doing anything special. Just reading and texting using my Bluetooth-Keyboard.

Anybody else ever facing something like that?

It's the first time for me, yesterday on r146 I had NO issues, while doing the same stuff.

My settings: Stock values by franco, no UV, no OC.

While typing this i had to re-enter the code 2 times....:( :what:

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] thebryceee:
The way I think the back button should operate is like in Tapatalk 4 when you're in, say, your subscribed threads and you press back, the drawer pulls out.
[Nexus 4 Original Android Development] admiez:
Ok, that's what I thought. I guess the misconception is that of many 'main screens'. There should be one 'main' screen, the one you get when you launch the app. Does the menu items on the navigation drawer change or stay the same throughout the app?

I guess I should just see for myself instead of asking questions. :cyclops:
[Nexus 4 Original Android Development] Utini:
Nope, i uninstall, reboot, install, make my settings..still after another rebot everything is gone :/
[Nexus 4 Original Android Development] thebryceee:
Stay the same
[Nexus 4 Original Android Development] nachordez:
It stays the same.

But try it if you want. It's really nice looking!

nexus4 / stock / Franco.kernel / V4A sound

gt-p5110 / CM 10.1 / Dhollmen kernel / V4A sound
[Nexus 4 Original Android Development] admiez:
Yes, I get you. But don't you think it is odd to do that?

For example, in Tapatalk 4:

You launch it and you get to the 'main' screen which has a list of forums. You tap let's say XDA. You are now looking at a list of threads. If you hit Back, it pulls out that drawer. The expectation would be for it to take you back to the list of forums. You had not seen that drawer yet, you may not even know it existed, why does it suddenly showed up upon a 'go back' operation? It takes two hits on the Back button to return to that screen. That is exactly what I thought the first time I used it.

However, the use of the navigation drawer in that app is somewhat a mess (my opinion). If you pull out the drawer and tap one of the sections, let's say Settings, you are in Settings now and you hit 'Back' it just pulls out the drawer again. The only way to return is to select from the drawer the section you were in.

That's why I when read the idea for the Back button, I jumped in thinking of Tapatalk 4 as a bad example to follow.
[Nexus 4 Original Android Development] thebryceee:
I like that option better than exiting. Personal preference I guess. When you first enter the app, the navigation drawer is out, so in a way, it's like the "main page" because there is no main page. So hitting back at a top level would sort of go back to the "main page"
[Nexus 4 Original Android Development] schmitzekater:
Gotta quote myself, but I guess my problem is (temporarily) solved.

Just rebootet, and the issue seems to be gone. Maybe something was driving nuts on my phone and sucked the hell out of the battery and therefore the modem 'rebooted'.

Maybe it's because of the BT used, but that's just a simple guess...

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] ricey1986:
Don't know if it possible but how about "pinnable" favourites on the front screen that is user defined??
[Nexus 4 Original Android Development] admiez:
It wouldn't be as bad in Franco's app because the drawer is at the moment acting as the 'main' activity, so it does make sense for Back to take you there. In Tapatalk there is a previous 'main' activity so it breaks the flow when it does that.
[Nexus 4 Original Android Development] thebryceee:
Lol I just edited my post to say the same thing pretty much
[Nexus 4 Original Android Development] admiez:
Yes I noticed lol. Exactly what I was thinking, but you said it better.
[Nexus 4 Original Android Development] 3c:
Hey franco,

I was wondering where can I find your paid app thread? Couldn't find it in the paid app section or anywhere else for that matter?

The other day you mentioned UI guidelines from Google, so I am wondering when do you plan on making your app comply to those?

Thanks to your fans, we found out it breaks 3 basic concepts:

- Preference screens are meant to configure the app, while you use it as the backbone of your app.

- Dialogs without action or ok/cancel buttons. Popups are supposed to provide action-based components.

- Spacing across the UI is way beyond the recommended 48dp, except in the preference screens managed automatically by Google's API.
[Nexus 4 Original Android Development] admiez:
Let's remember that guidelines are just that, guidelines, not a fixed set of rules. And his app is not your typical app. And it does look pretty decent as it is, even more if compared to what's out there.
[Nexus 4 Original Android Development] Normola:
I had the same issue. I found that every time the phone locked, I had to reenter the sim pin code. I'm not sure if it was the physical act of locking, or if it was the lock sound playing that caused it to happen.

Running stock ROM with Franco kernel only. No OC or UV. Rebooting also seems to have helped for now.

Still really impressed with this kernel though. First issue I've personally seen, and I've been using it for months now.
[Nexus 4 Original Android Development] 3c:
Agreed, however franco implied it was very important and would make users happier. Not that I don't really care :D
[Nexus 4 Original Android Development] schnuffdroid:
i think you do care, and you care too much... ;)

*nexus4*aokp*franco*
[Nexus 4 Original Android Development] Bill Gamble:
It sounds like you've checked "Automatic data clearing" in Settings.
[Nexus 4 Original Android Development] 3c:
I couldn't care less actually. But as OP initially brought the UI guidelines subject, and a fan actually pointed out fanco's app was not compliant, I was wondering if OP will actually follow them in the future? Interestingly there's no actual reply to such a basic question.

It's interesting how people do not answer questions in this thread, but ***** at each others so frequently. You don't see that in other threads, which makes me wonder what people have in common here that they don't have on other kernel threads?
[Nexus 4 Original Android Development] ryanytchan:
For starters, they probably don't have people like you complaining about irrelevant details
[Nexus 4 Original Android Development] 3c:
Well, "for starter", as mentioned 3 times now, OP complained about this "irrelevant detail" in the first place :D thanks your useless post confirming what I said.
[Nexus 4 Original Android Development] Utini:
Oh god you are right -.- I dont even know why I checked this option...

Anyway thanks to u its working now.

-200mV undervolt doesnt seem to work anymore on r146 while it did on M2. But I guess -150mV is still fine :>
[Nexus 4 Original Android Development] atz6975:
So how does this help with kernel development exactly?

Sent from smooth EOS4 running Nexus4
[Nexus 4 Original Android Development] TheDarkDefender:
Wow man! You did -200 on M2? :eek:

Tried any other nightlies with the same?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Utini:
Nope, I didnt really undervolt until M2 (it got released at the same time where summer began in my country.. so I thought I would give UV a try in terms of lower device temperature). On M2 -200mV was perfectly fine while -225mV caused a crash. Did about 60 minutes of stability test, ran a few 3dmark06 runs and used the device with -200mV until yesterday.

Now on r146 -200mV doesnt work. Also -175mV isnt working. I am not at -150mV and it looks good so far (a bit gaming and random usage.. now trying with stability tests).
[Nexus 4 Original Android Development] 3c:
May I suggest you ask OP instead of answering a question by another question. Question was initially meant for OP.

Considering your reply to my initial question, you won't mind me replying with yet another question then: how does all the posts about a paid app actually help kernel development exactly?