yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] osm0sis:
Not what I'm talking about.

People are still installing busybox manually, and if you do that to /system/bin or /su/bin (which overrides /system/bin binaries in the path) then WiFi calling breaks (among several other things).

/system/xbin or /su/xbin (like my busybox installer uses) are the only places it can be and have your ROM work as expected.
[Nexus 6  Original Android Development] Jaspreet84:
Friends, Franco+purenexus has been driving my n6 quite well since last 24+ hours.

I see that all 4 cores of my phone are active even without much load. Is this expected?
[Nexus 6  Original Android Development] SunamY:
r42 runs perfect... Tweaked it a bit...

My setup:

-Conservative governor (down threshold 30 and up threshold 95)

-Min cpu set to 1497Mhz

-Touchboost off

-i/o bfq

-50V undervolt

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] franciscofranco:
Yes.

Min cpu to 1497MHz??????? Goodbye battery life ?
[Nexus 6  Original Android Development] icaicm:
hi

been using R41 on my nexus 6 with danvdh stock lite rom. been running superb with very good battery life. over night i use to loose only 2% to 3% of battery life from 10pm to 7am in the morning. i now have updated to R42 and notice that battery life is not too great as i am loosing around 6% to 7% overnight for the same duration. any idea how to retain similar % with R42.

thanks

icaicm
[Nexus 6  Original Android Development] franciscofranco:
Battery life during idle is the same with mostly every Kernels. You must have some app keeping your phone awake for longer times.
[Nexus 6  Original Android Development] SunamY:
[MENTION=3292224]franciscofranco[/MENTION] nope.... Batterylife is good so far... No lags... After some tests, the touch boost drains more battery for me.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] eman630:
Hey Franco, I just wanted to say one thing and ask another. First off: how tf do you get any sleep?? You bust your *** on these updates, and answer noob questions quickly (like the one I'm about to ask), and yet still have time to work on your separate project? Dude you are amazing! Much respect to you. (Personally idk how you deal with the repetitive questions for this long.)

My question that I need to ask is this: how tf do I get Android pay to work without reflashing SuperSU again? Every time I temporarily turn it off, I am told I lost root and need to reflash it. Thank you again!
[Nexus 6  Original Android Development] holeindalip:
Are you on stock rom, if so no reason to disable root if its systemless ap works fine,
[Nexus 6  Original Android Development] icaicm:
hi

will check and see, to be honest i have exactly the same apps and nothing has been change apart from the kernel. from R41 to R42. everything else is exactly the same.

thanks.
[Nexus 6  Original Android Development] Jaspreet84:
Hi Franco,

Using franco+purenexus+purenexus gapps. Since I've moved to Franco, Sat has definitely increased. But I noticed that Google services eating up a lot of battery. Is there anything I can do about it?
[Nexus 6  Original Android Development] franciscofranco:
I don't know how I find time, been hard with both my grandmothers being in a very bad condition, but I manage. Sorry I can't help with Android Pay since it's related to SuperSu and I don't have Android Pay in my country.

So you're assuming that all wakelocks always fire at the exact same ways, same times, same scenarios?

Not much you can do about Play Services.
[Nexus 6  Original Android Development] SunamY:
One problem I notice with r42: my settings in fku app didn't stick after reboot. Some apply, some not...

Is there a solution?

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] raydekok:
I asked before but is there a problem flashing the r42v2 dirty on the r42?

I've done that but no problems so far.

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6  Original Android Development] epagib:
Hey guys, which I/o Scheduler do you recommend? Noop, deadline, cfg? Thx
[Nexus 6  Original Android Development] an21281:
I use fiops 90% of the time, noop is also good. Haven't noticed any major differences but they both run well
[Nexus 6  Original Android Development] bmakk2055:
Thanks! This fixed my WiFi calling
[Nexus 6  Original Android Development] franciscofranco:
The default.
[Nexus 6  Original Android Development] franciscofranco:
Nop, no problems.
[Nexus 6  Original Android Development] cmhjr:
To get Android Pay to work I had to delete xbin folder in the su folder (version 2.66). I used SafetyNet helper from play store to test. If safetynet passes Android pay should work. Reboot after deleting folder.

So far no problems using Android Pay but some programs used to the old way of rooting may have problems until updated for systemless root.
[Nexus 6  Original Android Development] osm0sis:
xbin_bind. xbin is different.
[Nexus 6  Original Android Development] franciscofranco:
There is no FIOPS in FK.
[Nexus 6  Original Android Development] franciscofranco:
Free stuff: https://plus.google.com/u/0/+FranciscoFranco1990/posts/RzCjNdafUHu
[Nexus 6  Original Android Development] instinctkiller:
Great news :) been back with your kernel since r42. Ducking love it !
[Nexus 6  Original Android Development] eman630:
Sorry for the long delay; yes I'm on stock, and its perplexing because it should theoretically have no issues. However.. Here I am having one lol
[Nexus 6  Original Android Development] wmfreak:
CM13 & Franco

I've tried to flash Franco Kernel with CM13 and no matter what I try it won't boot. What am I doing wrong? I have the latest TWRP and SeperSU 2.52.

Any help appreciated.
[Nexus 6  Original Android Development] biglilsteve:
In the change log he mentions that systemless SuperSU 2.60+ is required. I think I have seen people using system root as well though so I'm not sure. Maybe you want to try it out and see if it helps?
[Nexus 6  Original Android Development] holeindalip:
Are you entering the commands in terminal through recovery before flashing the SuperSU.zip??

echo SYSTEMLESS=true>>/data/.supersu

echo BINDSYSTEMXBIN=false>>/data/.supersu
[Nexus 6  Original Android Development] LittleJakub:
[MENTION=3292224]franciscofranco[/MENTION]

I know we gave up on this whatsoever, but I repeated the whole testing section again, and once more it goes that full stock/stock+elementalX - all is well, while stock+r42 - still no SIM card detection :(

---------- Post added at 07:34 PM ---------- Previous post was at 07:16 PM ----------

OMG! I don't know why, but I thought... I'll try once more... I have no idea what I did, but it works! it bloody works! :D

#ALLHAILFRANCO :good:
[Nexus 6  Original Android Development] holeindalip:
Did you flash r42 over the stock kernel or did you flash it over the top of elemental??
[Nexus 6  Original Android Development] franciscofranco:
CM13 or that CM13-CAF build?

You're ducking welcome.
[Nexus 6  Original Android Development] farahzadfarahzad:
Hi franco thanks for the nice kernel , i am just having difficulty of how to activate auto high brightness mode in fku ?Cheers
[Nexus 6  Original Android Development] franciscofranco:
Having difficult how? It's just a toggle.
[Nexus 6  Original Android Development] farahzadfarahzad:
Thanks franco but i donno why i can't find it :(
[Nexus 6  Original Android Development] holeindalip:
It's under settings
[Nexus 6  Original Android Development] deeppans:
WiFi is shown always on, although it's off.

Am I missing something?
[Nexus 6  Original Android Development] holeindalip:
It's a bug as stated multiple tomes
[Nexus 6  Original Android Development] dunjamon:
Should 42 be available through the updater app? I flashed the zip on here, but the app still shows 41.
[Nexus 6  Original Android Development] regisso66:
Check in Settings, about phone, you have r42. Changelog isn't up to date.
[Nexus 6  Original Android Development] anthonyg45157:
Go to location settings click 3 dots in top right. Turn off wifi scanning.
[Nexus 6  Original Android Development] dunjamon:
Kernel version still shows 41. I'll try it again and see.
[Nexus 6  Original Android Development] nathanchance:
No, Franco has stated a few times in here that FKUpdater has to updated to support the new format and that will happen very soon.
[Nexus 6  Original Android Development] mwebb34:
Dang my phone has got a lot faster!
[Nexus 6  Original Android Development] franciscofranco:
FKUpdater 14.1 has been pushed as a staged roll-out (20%). If there's no major issues with it I'll increase it to 100% when I wake up.

Change-log:

1 - Support for the new FK flashing method anyKernel2

2 - File manager re-designed and added feature to auto-flash anyKernel2 zips

3 - Fixed Per-app profiles: fixed losing the applied profile when checking your notifications, fixed CPU max/min apply on non-synch cpu cores, fixed editing a profile and added more options to some devices

4 - Added better display temperature UI

5 - Improved auto HBM

6 - Added more info descriptions (more coming)

7 - Better detection of SD808 and SD810 devices
[Nexus 6  Original Android Development] mwebb34:
I ducking love it lol
[Nexus 6  Original Android Development] ironjon:
yeah, r42 it´s High Level and now with new FKU it´s all what I need :p
[Nexus 6  Original Android Development] mwebb34:
Yup, high tech, when I unplugged my charger last night it was 100% I went to sleep soon after around 9 I believe. I left my nexus on all night and when I woke at 7am I had 94% that's pretty dang good standby time. I'm sure it will get better. Also I really like the fkupdater. I just need to know what all I need to change in the fkupdater app for the best possible performance. I know how to set the CPU but am a little on the dumb side when it comes to kernel settings per app profiles performance profiles. I need to know which ones I need to change and what to leave on default. I know even though we are on nexus 6 everyone's settings are gonna be different, so its probably left up to the individual on what to change and not change right?
[Nexus 6  Original Android Development] TonikJDK:
I got the app update from the store, it still thinks I am on 41 even though I am on 42. It is the 'first' 42, the original one posted in this thread.
[Nexus 6  Original Android Development] mwebb34:
I just ran a speed test on my nexus and scored 39344. I would love to see this upwards to at least 45 or 50.

---------- Post added at 07:41 AM ---------- Previous post was at 07:31 AM ----------

The app updater also says I'm on r41 but I flashed r42. I didn't flash the super user zip, but when opening a app that requires SU it pops up. So do I need to flash su anyway?
[Nexus 6  Original Android Development] hotrodhell:
My antutu score was over 72k [MENTION=4836843]mwebb34[/MENTION] what program did you use?
[Nexus 6  Original Android Development] holeindalip:
No update on play store here
[Nexus 6  Original Android Development] mwebb34:
I ran it again and scored even lower 32. I'm using Antutu
[Nexus 6  Original Android Development] adm1jtg:
I have seen really erratic scores from antutu I was also testing with this kernel some runs i get 32k and others i see almost 80k with no changes.
[Nexus 6  Original Android Development] mwebb34:
More than likely its operated error, because I don't know how to use the updated app. I know how to set the CPU but that's about it. I know nothing about kernel settings, performance profiles,per app profiles. Not sure on what I need to change.

---------- Post added at 08:44 AM ---------- Previous post was at 08:40 AM ----------

Which app do u recommend?
[Nexus 6  Original Android Development] franciscofranco:
Who cares about ****ing antutu benchmarks. There are 293473957 things that can influence a benchmark. If you want something reliable use Geekbench instead, or if you really want something professional just search for hachbench binary for arm and run it on your device.
[Nexus 6  Original Android Development] mwebb34:
I didn't know what to use....now I do.....
[Nexus 6  Original Android Development] franciscofranco:
r42 has been deployed to my server and available for auto-flash and download zip through FKUpdater. Make sure you're on the latest FKUpdater 14.1 release which has been made available for 100% of the user base - I lifted the staged roll-out.

Make sure you read the change-log if you have any doubts and you're still on r41. I know it's a big transition but it's something I should've seen coming earlier.

This new method would not be possible without [MENTION=4544860]osm0sis[/MENTION] so if you're feeling generous send him some $$ through his paypal link.

Thank you for the continued support, I hope you can now enjoy FK on your favourite custom rom.
[Nexus 6  Original Android Development] Prack:
My phone is stock with r41. Now that r42 is out can I just auto flash or do I have to flash a boot.img?
[Nexus 6  Original Android Development] holeindalip:
Did you read the instructions?
[Nexus 6  Original Android Development] Prack:
Yes, but I want to be sure that I understand them. I don't exactly have time to redo my entire phone tonight.
[Nexus 6  Original Android Development] holeindalip:
Flash the stock boot.img then flash r42 on top
[Nexus 6  Original Android Development] franciscofranco:
You only need to flash stock boot.img to be on pristine stock status. Then flash the zip. Then afterwards when new versions come out you just flash new zips on top and be fine.
[Nexus 6  Original Android Development] Prack:
Sounds good, I just did that now and everything went smooth.
[Nexus 6  Original Android Development] goinflyn:
Stock rom sytemless root 2.66. Flashed r42 over stock. Android pay stopped working. I deleted the xbin folder in /su and no luck. Any ideas?
[Nexus 6  Original Android Development] nathanchance:
Google found a way to detect systemless root within the past day. You either need to disable superuser in the SuperSU settings or ditch it altogether.
[Nexus 6  Original Android Development] goinflyn:
Thanks. I temp disabled superuser and it works. Thanks. Funny how android pay worked until I installed Franco tonight.
[Nexus 6  Original Android Development] osm0sis:
It's very simple to test rather than making assumptions. For everyone's information stock rooted doesn't even pass SafetyNet now. Google clearly made a server-side change to SafetyNet that must just make a generic su call to check, so it doesn't matter whether it's system or systemless root anymore.
[Nexus 6  Original Android Development] adm1jtg:
While I understand googles reasoning they just put the final nail in the coffin of android pay. Not like anyone was really adopting it with open arms anyway.
[Nexus 6  Original Android Development] nathanchance:
Well nobody on XDA lol. I know a few people with Android devices that use it freely since they don't know the first thing about modification and they love it.
[Nexus 6  Original Android Development] franciscofranco:
I'll assume it's your fault.
[Nexus 6  Original Android Development] Adam80:
Since updating to the r42 and the latest FKU, I've been experiencing the speaker volume lowering bug. This is the first time I've experienced it in my N6. For those not familiar, audio volume gets normalized to about 50% of what max volume would be if the volume were turned all the way up. I'm not sure whether it even could be tied to the kernel, but the problems started about the same time I updated. I did some searching, but could not find a solution. Is anyone else having trouble?
[Nexus 6  Original Android Development] franciscofranco:
No idea. Never had it and the entire sound subsystem is 100% stock.
[Nexus 6  Original Android Development] Adam80:
Thanks for the awesomely fast response. r42 is fantastic! It's possible the issue could be related to the January security patch as well. There are tons of complaints out there from people who are stock or using any number of ROMs going all the way back to when the N6 first came out. You completely answered my question as it relates to Franco Kernel not being the cause. Thanks!
[Nexus 6  Original Android Development] franciscofranco:
Do you know of a reliable way to reproduce it? I don't know if it's fixable on the Kernel side, but with a reproducible case it helps me.
[Nexus 6  Original Android Development] rignfool:
We have 2 threads about it...

The first is a ***** thread in General started by [MENTION=2872010]danarama[/MENTION]...

Basically... The easy way to reproduce it... Is to let your battery drain below 40% or so... Some phones maybe more... Then play a racing game (Real Racing 3) and during the race... You'll notice the engine sounds getting quiet...

Or

You can fire up any music player... And change orientation... Though that one usually requires an even lower battery... Or maybe battery saver to be on...

There is a second thread in developer discussion and is about the actual hardware DSP for the phone...

That thread has some talk about the hardware automatic gain control...

On a side note... Another by product...

I have noticed at EXTREMELY low battery... (<5%) A crackling can be heard... Reminiscent of speakers not receiving enough power from amplifiers...
[Nexus 6  Original Android Development] Adam80:
Yes, that's what seems to trigger it for most people, according to everything I could find. I've had my N6 for over a year, and within the past week, it's been a constant problem. It never happened before then. As soon as I turn the volume above approximately 50%, it gets normalized right back to approximately 50%, regardless of the level I set it at. There's not a set of conditions I can use to reproduce the problem as it's a constant regardless of battery level or whether the phone is charging. Allowing the screen to rotate does trigger the volume to jump back to the set level for a second or two, then it normalizes back down. This happens regardless of the audio source (Play Music, TuneIn Radio, alarm tones, etc.). In another, thread, it was suggested that the audio amplifier driver may limit output when the battery is below a certain percent, and that completely draining the device may reset the threshold. I did completely drain the battery until the device wouldn't boot, but that didn't resolve the issue.

Changes I made around the same time the problem started are: upgrading from r41 to r42, upgrading to the latest FKU, deleting su/xbin_bind (I'm on SuperSU 2.66), and installing system.img from the January security patch. Lots of stuff, I know. That will make it hard to isolate. When I have a moment, I'll try to reverse the things I can one at a time. I'm not convinced any of the aforementioned things led to the problem, because people that already had the problem didn't get it as a result of any of these actions.

---------- Post added at 03:39 PM ---------- Previous post was at 03:33 PM ----------

Forgot to add that I also reinstalled Busybox.
[Nexus 6  Original Android Development] danarama:
It wasn't a "***** thread". It was trying to figure out the cause and how to reproduce it.
[Nexus 6  Original Android Development] szale9001:
Speaker Issues

Going to go out on a limb here and say the speaker issues might be related to this?

http://xdaforums.com/nexus-6/devs-only/speaker-amplifiers-nxp-tfa9890-research-t3236518

Apparently the driver for that codec is something of an inconsistent mess between manufacturers. Mwis also talks about the speaker amps holding back at lower battery voltages so this driver might indeed be the culprit.
[Nexus 6  Original Android Development] PrimeMinister91:
Is anyone having smart lock issues? It doesn't seem to be working well. Having issues with Swiftkey as well. Stock ROM with r42 and SU2.67
[Nexus 6  Original Android Development] holeindalip:
Just noticed this as well, something is broken in gps
[Nexus 6  Original Android Development] PrimeMinister91:
Doesn't work with Bluetooth either. Using my moto 360
[Nexus 6  Original Android Development] Adam80:
Alright, I found some time to work on reverting things and I have some useful info. Reverting to previous versions of FK did nothing to resolve the issue; however, fastboot flashing from the Jan 2015 security patch (MMB29S) back to MMB29K resolved the issue. At this point I feel fairly certain that the bug is part of MMB29S.

As usual FK is a great piece of work and was not the culprit.
[Nexus 6  Original Android Development] rignfool:
I know... I made the most posts there...

But there was no real technical information... As compared to the other thread I noted...

Didn't mean to offend

EDIT: back on topic...

I did notice... That using mpdecision seems to all but stop all noises down to the >5% issue
[Nexus 6  Original Android Development] bautrupp:
microphone

When in a call with my n6 my dialog partner always complain about me being to quiet. Since I don't find much about this problem in the forum it may be a hardware issue.

In FKU there is "mic volume gain" in kernel settings. Can someone explain what it does and what values I can use. It seems to do nothing for me.
[Nexus 6  Original Android Development] Novakingwai:
i see the message if you're on a custom rom and r41 or older to dirty flash the rom the r42. however, I do not have franco kernel at all. Should I just install R42? Or dirty flash the ROM first?
[Nexus 6  Original Android Development] :
The dtsi that we use is missing the optional taiko speaker driver section for current and voltage. I'm not sure if it inherits it from anywhere else though.

I don't know for sure if by leaving it out it let's the chip control it automatically. Then by including it, possibly forcing the voltage/current in the regulator.

... Just a guess. I noticed that while trying to figure out why fauxsound doesn't work for anything but headphones since mm. This was of course for a different kernel... But probably still similar files. I noticed that the register is sending for adjustments isnt reliable unless the header for the registers is moved to the uapi path in the includes. Then I was able to get the registers to change and actually succeed in the write methods. It's weird to me that headphones boost worked before that, as well as after though.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] rignfool:
I'm sorry... I don't understand...

Are you saying the software that send values to the amp driver is sending junk?

Or are you saying its sending values not rooted in the real world?

Everyone else has blamed hardware... You're the first to say software... If I understand you
[Nexus 6  Original Android Development] :
I was saying that while chasing a different issue, I noticed that.

The dtsi files basically regulate the hardware. They control things like voltage and current regulators.

For the wcd9320 chip, there's an optional field for the speaker driver in the dtsi.

What I'm saying is that it might be possible that if that optional field isn't present, it may let the chip attempt to auto-regulate itself. That might account for the variations. As opposed to the regulator being told to maintain a constant min/max voltage and current.

See the documentation here: https://github.com/franciscofranco/...evicetree/bindings/sound/taiko_codec.txt#L223

But like I said, it's just a guess.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6  Original Android Development] hdtechk:
All is working well but getting tired of message
[Nexus 6  Original Android Development] franciscofranco:
/*

* spkrdrv supply in MTP device is from VPH_PWR which is

* always ON. Give a dummy supply to make codec driver happy.

*/

cdc-vdd-spkdrv-supply = <&vph_pwr_vreg>;

qcom,cdc-vdd-spkdrv-voltage = <0 0>;

qcom,cdc-vdd-spkdrv-current = <0>;

qcom,cdc-on-demand-supplies = "cdc-vdd-spkdrv";

That's what I find inside taiko's i2s dtsi. I admit this is a bit over my head though.
[Nexus 6  Original Android Development] franciscofranco:
How does that happen? It's the most crash-less release yet according to crashlytics.