yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] nexusmaniac:
I tried to flash it using file manager in FKU (But it didn't flash? :( )

Best way is either fastboot via PC

OR

Put the boot.img into /sdcard/franco.kernel_updater/kernel_backups and then restore :)
[Nexus 6  Original Android Development] wrongway213:
Why would anyone go into Fastboot to flash a Franco kernel.. unless you don't have FKU? Just open it in file manager and auto-flash, worked fine for me.
[Nexus 6  Original Android Development] GregNexus:
you can easily flash the boot.img with the latest twrp version :)
[Nexus 6  Original Android Development] nexusmaniac:
Yep :) That's another good option
[Nexus 6  Original Android Development] Fauert:
Or you can use "Flashify" from Playstore ... Very easy, user friendly ..
[Nexus 6  Original Android Development] Cwoomer:
I would ask why anyone wouldn't flash a boot.IMG through fastboot? It's the basic way to flash an .IMG. Time tested and proven to work. Maybe I'm too old School.
[Nexus 6  Original Android Development] Mistertac:
Well I agree that's super easy and reliable, just sometimes people aren't at home or by a computer to do so I think that's one reason.. Another would be that some people just don't know how to use Fast Boot [emoji33]
[Nexus 6  Original Android Development] duminduweera:
msm_hsic_host Wakelock

Ok, This msm_hsic_host kernel wakelock is killing me. Most of the time, BetterBatteryStats shows me that this wakelock have kept my device on for hours (2-3 hours)

I've done a lot of research about this, and from what I've seen so far this happens when my mobile radio is kept active by some application. But the thing is even though I'm on Wifi, it this wakelock still appears. In fact,even if i switch off Mobile Data (and connected to Wifi), and use BetterBatteryStats to set a custom ref, I can see the wakelock happening.

I've tested this on a clean install, with no other that gapps apps installed, Ive tested different Roms (Liquidsmooth, CM12, Euphoria), even different Kernels (Lean, Stock Cm, Vindicator, Faux), but without any luck ;(

The only way I can stop this wakelock is by putting my putting my phone on "Airplane mode".

I even have the correct APN configured as well. If anyones interested, my network is Vodafone Australia.

So my question is that is it only me having this problem? or is it something defective about my phone? or maybe related to my network provider?
[Nexus 6  Original Android Development] githyanki:
I have this one at work only. Network related for me.

Try turning off wifi and see if it clears. You can also try turning off cellular by going into airplane mode, then turning wifi back on.

No fix for it really, just have to hope google updates broadcom drivers in lollipop 5.1
[Nexus 6  Original Android Development] christianrance:
Sorry to hear you guys are having these issues; I'm sure it's downright maddening [emoji30] [emoji35]

I'm running [MENTION=426561]scrosler[/MENTION]'s CleanROM with [MENTION=3292224]franciscofranco[/MENTION]'s kernels and can say I've had next to zero problems with any wakelocks on the N6 with the exception of one or two isolated instances with the PowerManagerService wakelock (which a simple reboot immediately fixed).

I'm more than happy to answer any of your questions as far as device setup goes (i.e. device/system settings and app inventory) to help identify what differences we might be dealing with but this [ROM + kernel] combination has been an absolute dream for me (best combo of any device I've owned to date).

via my franco'd CleanROM Nexus 6
[Nexus 6  Original Android Development] Tzfardaya:
My first thought is if they don't know how to use fastboot, they shouldn't be flashing anything to their phones... Fastboot is the most reliable way to recover from a borked setup
[Nexus 6  Original Android Development] wrongway213:
It's definitely easy and the most reliable/tested way to flash a boot.img in general. I am asking why anyone would go through that with Franco Kernel in particular, unless an FK user but not an FKU user.. if you have FKU and you still use fastboot to update, you're honestly just wasting time/using Fastboot just because you prefer the "old school way", in my opinion, as it's not debatable at all that flashing through FKU's built in auto-flash function is much quicker. Basically I am asking why would you intentionally make something take longer than it is intended to? I say intended because Franco kernel is intended mainly to be used with FKU, as most kernels that have a kernel control app accompanying them are "intended" to be used with the kernel control app designed for said kernel.
[Nexus 6  Original Android Development] franciscofranco:
Without that wakelock you won't have data, it's part of the system. But if that makes you happy I can add a toggle to disable it just like we did with sensor_ind. But then again, you'll lose your data connection during screen off I believe.
[Nexus 6  Original Android Development] Cwoomer:
Very good point. I agree. I guess I was hung up in the .IMG part of his question and not relating it directly to franco kernel. If using FKU ( I am) then certainly it is easiest to flash updates using FKU. I was thinking along the lines of any .IMG file in general. I also agree that you should read up on fastboot before attempting to just "flash an .IMG file" not really the place for a fastboot tutorial.

I crackflash so I think my phone spends more time in twrp than anything else. With that being said .zip is the easiest for me as I have to replace the stock cm kernel with every update to avoid encryption.
[Nexus 6  Original Android Development] franciscofranco:
Why the fuss about how to flash a boot.img? Fastboot, dd, recovery, apps, the mechanism and result is the same, it's just writing bytes to a block.
[Nexus 6  Original Android Development] Tzfardaya:
My understanding is it relates to the 3g modem (USB bus connection to the phone iirc) so even voice calls can trigger it... Or a noisy cellular area and the phone has to work harder to maintain 3g (voice) connectivity (even when idle... You never know when a call may come in)

I get hit heavy with that wakelock in the built up areas of the city, in and out of concrete buildings, elevators, etc, and my signal quality suffers because of it. As my signal degrades, the msm_hsic_host wakelock time climbs.
[Nexus 6  Original Android Development] wrongway213:
Ah, that makes sense, for extreme crackflashers I suppose it might just be second nature to fastboot everything.. was just pointing out for general use, if you use FKU there's no real need for it..it's not like with other kernels where your only options are Fastboot, TWRP or Flashify... interesting how we all use our devices just a little bit differently.

---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------

As long as you're only seeing the wakelock when your phone is actually in use it's not a problem if I understand correctly. Is that your understanding as well? I've been wondering about this same wakelock myself over recent days, seems to be high in my wakelocks sometimes but not a problem when not using the phone.. pretty sure that's normal behavior but figured I'd double check as it's already being discussed.
[Nexus 6  Original Android Development] Tzfardaya:
Heh, no I was talking about screen off idle... The phone trying to keep the 3g connection Alive in poor signal areas... . I don't worry about wakelock that are active when the phone us in use.... I just the ones that keep the phone from deep sleep.
[Nexus 6  Original Android Development] Cwoomer:
No fuss really. Someone asked about how to flash a boot.IMG and it sparked a conversation about different ways each of us does it.
[Nexus 6  Original Android Development] wrongway213:
Thanks, that's what I thought myself. I always thought that wakelock (and most kernel wakelocks honestly) was only an issue if it persisted when your screen was off (unless on a call of course), just wanted to double check since it was being discussed.
[Nexus 6  Original Android Development] franciscofranco:
Attached is a boot.img with the option to disable msm_hsic_host. Warning though, I don't know what are the consequences. The lock is enabled by default, to test and disable it go to /sys/module/wakeup/parameters/enable_msm_hsic_ws and change to false, or echo 0 > /sys/module/wakeup/parameters/enable_msm_hsic_ws

Don't mess with it if you don't know what the **** you're doing, as I said, I don't know how mobile data will work with this lock disabled.
[Nexus 6  Original Android Development] Cwoomer:
Can we flash this using fastboot flash boot boot.IMG? :sly::o
[Nexus 6  Original Android Development] Tzfardaya:
No, you need to use adb. :P
[Nexus 6  Original Android Development] Mistertac:
You guys are all wrong, I use Odin
[Nexus 6  Original Android Development] wrongway213:
Odin + Kies = happy Nexus :p
[Nexus 6  Original Android Development] enzoevo:
Is this something we can toggle on and off?

If so, how?
[Nexus 6  Original Android Development] pantmunu:
When a user is using WiFi and Has turned off data .. Disabling that pesky lil wakelock would be awesome. This particular wakelock affects people with bad signal . I have tested it and sometimes it wakes up even when the freaking data is off. Don't have any screenshot to prove it but as soon as I get I'm gonna put it here.
[Nexus 6  Original Android Development] franciscofranco:
It's disabled by default. The path is about 5 posts above...

I posted a boot.img just 5 or 6 posts above where you can disable it...
[Nexus 6  Original Android Development] franciscofranco:
So... did anyone test disabling msm_hsic_host?
[Nexus 6  Original Android Development] Byrd San:
I tried to but when I went to the file it wasn't correctly named. Instead of enable_msm_hsic_ws it says enabke_msm_hsic_ws. I don't know if that has something to do with me not being able to edit the file or run the command in the terminal.
[Nexus 6  Original Android Development] franciscofranco:
It's just a typo on the file name, you can change the command that I posted to the typo'ed file name...
[Nexus 6  Original Android Development] Byrd San:
Yeah I thought that could have been the case. Let me give it another try...

Edit: Just disabled it through the terminal. I'm gonna try it out for the day and let you know if there's any disadvantages to disabling this. Thanks for working so hard to make this beast of a phone even more of a beast! [emoji16]
[Nexus 6  Original Android Development] uhguy:
I'll be curious as to how this works. I have that wakelock at work in one building where the service is awful. Would be nice to not have to worry about it.
[Nexus 6  Original Android Development] franciscofranco:
It most likely will block the constant search for data signal and will save your battery life. More than this, I don't really know, it's a bit of a guessing game.
[Nexus 6  Original Android Development] Byrd San:
Yeah it gets pretty bad for me too when I'm at work and school. So far it seems to not have any problems as far as connectivity goes. But then again its only been a few minutes since I disabled it so I can't really say yet. But hopefully this fix can alleviate this wakelock issue.
[Nexus 6  Original Android Development] mindfever91:
I will also keep testing the effects of disabling msm_hsic_host throughout this evening and tomorrow at work. I have pretty bad cell reception there and naturally the wakelock kicks in pretty hard. Let's see if there's an improvement in battery drain without unwanted side effects.
[Nexus 6  Original Android Development] hdtechk:
[MENTION=3292224]franciscofranco[/MENTION] if you ever get bored there is not a single person working on kernels for moto x 2nd gen XT1095. this kernel rock my N6
[Nexus 6  Original Android Development] zephiK:
Franco doesn't work on devices that isn't a nexus. Oneplus one was a exception.
[Nexus 6  Original Android Development] DPretzelK:
No, I'm on 52% and the value still changes to 17## instead of stay on 26##! How can I fix it?
[Nexus 6  Original Android Development] franciscofranco:
That is not possible unless you have something else doing it for you. Or maybe you did it yourself and you don't remember.
[Nexus 6  Original Android Development] TonikJDK:
No desire to adjust settings, but bought the app to say thanks. You have made this the best phone I can remember having in a long time.
[Nexus 6  Original Android Development] DPretzelK:
Is possible since It's happening, seriously... I didn't do it, I swear, I want my cellphone running at max. CPU speed. ?
[Nexus 6  Original Android Development] jtwlbz:
Very snappy kernel.. great work..
[Nexus 6  Original Android Development] C00lBeanz:
Same it resets to 17## 4 me 2...
[Nexus 6  Original Android Development] Tzfardaya:
Test incoming calls too...

Franco, what are your thermal throttle freqs set at? Could that be tagging these two?
[Nexus 6  Original Android Development] franciscofranco:
Thermal driver is stock. Only change was exporting the thermal throttle point to userspace. It's 70ºC.
[Nexus 6  Original Android Development] suku_patel_22:
Does this also has the sensor_ind thing disabled?

I mean the 2nd boot IMG

Sent from my Nexus 6
[Nexus 6  Original Android Development] EniGmA1987:
Phone doesn't go into deep sleep when on the charger, so maybe that is your issue. You need to check frequency times after the daytime hours of running and see how long it was deep sleeping.
[Nexus 6  Original Android Development] enzoevo:
Yes. Doh! Thanks.

---------- Post added at 09:05 AM ---------- Previous post was at 08:45 AM ----------

Rebooted. FKU settings won't stick. Tried multiple times. Latest SuperSU, and watched message granting su to FKU. Not running any other tweak apps.

Any ideas?

Edit: disregard. I must not be waiting long enough to see the settings register in FKU. Sorry.
[Nexus 6  Original Android Development] paychex:
Kernel isn't even a week old
[Nexus 6  Original Android Development] kEvinErd:
Can anyone comment on how much of a difference they are seeing on Franco kernel out of the box without changing anything vs stock kernel? Still contemplating whether to root.....
[Nexus 6  Original Android Development] wrongway213:
I see a huge difference. In certain less customizes roms that clmd with stock kernel it increases SOT and idle time a lot. In ROM's with custom kernels it improves smoothness and performance, not as much of an SOT boost but still very noticeable, very awesome.
[Nexus 6  Original Android Development] b.huss2:
What would cause this to revert? It stays auto for a while, but eventually switches back to off by itself. Something is restoring the original tsp file.
[Nexus 6  Original Android Development] zephiK:
Out of the box, I can assure you that you will have a better experience with the removal of mpdecision. You can read about mpdecision and what it is by Google, faux explains it well,

For Franco kernel, the kernel uses a different approach by hotplugging cores (activating and deactivating cores based on the current load of the cpu). Comparing the two methods, the cpu is more efficient and most importantly, cooler in temperature. I can continue ranting on and off on why this kernel is better over stock but I won't.

Just try it, it's free anyways ;)

I'm sure down the line well get profiles but right now with just rgb there isn't much to customize.

Gamma controls is not something easy to obtain and is a lot more work than one developer. For the nexus 5, it was done by a group of developers and took a long time to achieve it. Requires reverse engineering. Let's just be hopeful that rgb is here and was ported from LG.
[Nexus 6  Original Android Development] eldedo:
is init.d support going to be added? BTW great work as always.
[Nexus 6  Original Android Development] enzoevo:
Is there a way to set read ahead buffer size with FKU? I'd rather not use another app if possible.
[Nexus 6  Original Android Development] stas333:
Im getting pretty good battery life on the power saving option (max cpu is up to 2.5). i get 20 (+/- 2) minutes of SOT for every 5%. I dont play games at all.
[Nexus 6  Original Android Development] dipdeol:
I am seeing this as well. It was working fine before. I'm running stock other than FK.
[Nexus 6  Original Android Development] franciscofranco:
No, I won't add it, it's pretty much useless.
[Nexus 6  Original Android Development] mgear356:
Franco, I am noticing some gfx artifacts in browser and Chrome.. Will try to get some screen shots.. Wondering if others experienced this?
[Nexus 6  Original Android Development] franciscofranco:
Nope, can't reproduce that.
[Nexus 6  Original Android Development] apogee82:
I can confirm this too. The LED + Light Flow worked on stock. But R1/R2 have removed this capability.

Battery life yesterday with R1 was insanely good! On R2 now. I don't want to ditch back to stock over the LED. A fix would be greatly appreciated.
[Nexus 6  Original Android Development] Skripka:
Light Flow works fine here.

You need to clear the data/databases/cache from Light Flow when flashing kernels or ROMs.
[Nexus 6  Original Android Development] csavino3:
Francisco, is quick charge enabled in r2? If not, when do you think it might be added? Thanks in advance.
[Nexus 6  Original Android Development] Langduscher:
"Soon" [emoji16]
[Nexus 6  Original Android Development] mahst68:
Uninstall & Re-install LightFlow

Yeah... figured this out... Don't know why but it seems if you uninstall and re-install Lightflow, it will work again... I thought the same thing too a few posts ago but can confirm now that it does work fine with Franco! Thanks to everyone that helped solve this little mystery... kinda knew it was something dumb keeping it from working...:silly:
[Nexus 6  Original Android Development] bloodydamnhell:
Yay! Franco kernel! Hopefully soon we'll get some undervolt love so I can continue getting those sweet, sweet 7+ hr SOTs. The extra hour to hour and a half vs stock voltage made me exceptionally happy with my N6's battery life.
[Nexus 6  Original Android Development] tltwelve:
Franco, have you ever thought about transition over to ROM development?
[Nexus 6  Original Android Development] franciscofranco:
Yes. It's boring, takes a lot of time, I don't think there's anything new that I bring to the table, I need a functional device running with stock rom, I don't wanna use recoveries and flash roms all the time to test a single line change, I don't want to have a different partition/VM/machine to build a rom. And I don't have time. I'm sure I would do a kickass work if I only focused on rom development with actual new features, but for the reasons said above - never going to happen.
[Nexus 6  Original Android Development] franciscofranco:
What do you think? :confused:

Yes.
[Nexus 6  Original Android Development] suku_patel_22:
Thanks. I thought its two different test kernels for the two wakelocks. Silly me. Flashing, will disable both and let you know how it goes.

You asked to echo 0 to disable msm_hsic_host wakelock. But all I see is Y and N.

127|root@shamu:/sys/module/wakeup/parameters # cat enable_si_ws
N
root@shamu:/sys/module/wakeup/parameters # cat enabke_msm_hsic_ws
Y
root@shamu:/sys/module/wakeup/parameters #

Should we echo it as N instead or is it okay to have either 0 or N?

Sent from my Nexus 6
[Nexus 6  Original Android Development] laureanop:
Been running the test kernel with the sensor_Ind fix since this morning. Activated every potential trigger known to N6 owners and sensor_ Ind is nowhere to be found in kernel wake locks.

Great job Imo and thank you Francisco for bringing the fix to your kernel.
[Nexus 6  Original Android Development] laureanop:
Screenshot
[Nexus 6  Original Android Development] franciscofranco:
It's irrelevant, the Kernel treats an int 1 or 0 the same as a boolean true or false. It will work regardless, you can echo Y/N or 1/0 or true/false. It will work in any way.
[Nexus 6  Original Android Development] franciscofranco:
You can try and disable msm_hsic_host just to see what happens.
[Nexus 6  Original Android Development] laureanop:
The actual battery usage coming from that wake lock is not significant enough for me to deactivate it. On the other hand, sensor_ ind does signify an extra 2% per hour when it occasionally kicks in ( meaning once it kicks in it doesn't stop till I catch it. The other wake lock is spread throughout the day)
[Nexus 6  Original Android Development] tommy0823:
Has anyone on the test kernel had issues with the screen not turning off during a phone call? The sensor seems extremely sensitive while in a call.
[Nexus 6  Original Android Development] laureanop:
Didn't notice anything but I'll keep an eye on it
[Nexus 6  Original Android Development] mr_clean5953:
+1
[Nexus 6  Original Android Development] tommy0823:
Ty. I was driving myself crazy trying to figure out if it was just me.
[Nexus 6  Original Android Development] laureanop:
I made a few phone calls and the proximity sensor worked as it should. Stock rooted, adaptive on, ambient off.
[Nexus 6  Original Android Development] oOuzzielOo:
proximity working fine here with both ambient and adaptive off on the sensor_ind test kernel.
[Nexus 6  Original Android Development] italia0101:
Anyone having an issues with the msm_hsic wakelock disabled ? ?? intrigued on this one
[Nexus 6  Original Android Development] suku_patel_22:
I am out on vacation, and roaming. No 3g here, but 2g has been fine for me.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Remoteconcern:
I haven't noticed anything yet. I also haven't noticed improved battery life so far, despite my wakelock normally being huge. Anyone else?
[Nexus 6  Original Android Development] suku_patel_22:
Well we should give it at least a day to gauge the battery life

Sent from my Nexus 6
[Nexus 6  Original Android Development] estanenmi:
can u share the tools i have one dead too

Enviado desde mi Nexus 6 usando Tapatalk 2
[Nexus 6  Original Android Development] mindfever91:
I'm not to keen on it either. Have msm_hsic_host disabled since yesterday evening and didn't notice an improvement in battery life so far, it actually seems to be a bit worse. Also the phone feels a bit warmer than usual. I'll give it another day but I don't think it does any good.
[Nexus 6  Original Android Development] suku_patel_22:
With both disabled I am seeing a lot of wlan_rx_wake. I don't think it's related but just wanted to put it here.

Sent from my Nexus 6
[Nexus 6  Original Android Development] paychex:
It probably is. Since it can't look for a 3g signal, is defaulting to trying to find Wi-Fi
[Nexus 6  Original Android Development] suku_patel_22:
I will now enable it and see if wlan rx drops.

Now lets see after an hour.

Sent from my Nexus 6
[Nexus 6  Original Android Development] PeRKoniX:
I'm seeing this huge wakelock consumed by sensor_ind. Not sure if it is the kernel or the rastapop rom I'm currently on. What is this proces?

I'm on r14 with rastapop 2015-01-29.
[Nexus 6  Original Android Development] zephiK:
Read or skim the past 10-15 pages of this thread.
[Nexus 6  Original Android Development] githyanki:
Short answer: general consensus is that it is ROM issue. Franko is having some people test a kernel that will disable that wakelock to compensate.
[Nexus 6  Original Android Development] zephiK:
It isn't fair to blame a ROM is at fault as stock Lollipop rom is affected by this as well, you made it appear that it's a particular roms fault when it isn't.
[Nexus 6  Original Android Development] franciscofranco:
I don't have anything, deleted everything. Just Google it like I did.

wlan_rx_wake is completely unrelated to msm_hsic_host.