L2_hsic (latest update 12/12/13)

Search This thread

Braxos

Senior Member
Nov 18, 2011
693
144
Yesterday I had this problem with l2_hsic......

Read the rest here

I moved my post because I will need the space for the findings, as I don't see the light at the end of the tunnel.

Here are the findings till now from some users.
I will update this when new ideas/solutions have posted.

what is l2_hsic read the rest here

HSIC is technology for inter processor comminication. Our phone has two main chipsets AP (here snapdragon, thus the name MSM ) and modem chipset (again by qualcomm). They both are connected via hsic, ...........

Yes, HSIC is an hardware along with its device driver used for Inter Processor Communication.

Main principle is Android RIL communicates with help of hsic driver to communicate to the CP (modem) chip. And vice-versa. Modem chip also has the same hsic at there side also.

.............

That L2 does not stand for L2 of OSI layer................ There are 4 states (L0(active),L1,L2,L3) state of power saving in USB link also , hsic also uses the same convention.
................


kernel related? read the rest here


Hello
I've been encountering L2_hsic and a few other related wakelocks for months (even years), ever since updating my I9100T to ICS (which I did the minute custom ICS roms hit web).......

I searched around and found out the l2_hsic wakelocks are generated by a kernel file "/drivers/misc/modem_if/modem_link_device_hsic.c" which is also responsible for rpm_hsic and tx_hsic wakelocks.
From there I went to CM git and with help from their IRC channel I found the source code for their version of this file:
https://github.com/CyanogenMod/andr...rivers/misc/modem_if/modem_link_device_hsic.c

A explanation from anirudhgargi what hsic is! (09/06/12) post 264 :

HISC is the interface that connected the main Soc processor ( Also called Applciation Processor AP) to the modem ( 3G or 4G if there are two modems separately )

HSIC is used the standard USB core library. And it is stanrd given by usb.org. The HSIC by itself consumes very less power and is one of the very power efficient and space efficient ways of interconnecting chips. Currently common to Qualcomm and Sammy Exynos architectures.

The reason you seeing too many HSIC wake lock and other wake us's is due to the fact that the HSIC interface is waken up by modem (Normal scenarios are also so many) .


A find about hsic from becosemsaida (09/06/12) post #107 :

Well i have the wake-lock too and after some digging around i found this:

http://www.synopsys.com/dw/ipdir.php?ds=dwc_usb_lpm_hsic

A article about wakelocks from unthinkable apps(18/06/12) post #126 :

Interesting that academia is researching this issue.
www.theregister.co.uk/2012/06/13/fixing_android_no_sleep_bug/


A sume of what we know from Shaftenberg(20/06/12) post #136

- equal which modem we are using (GB or ICS)
- all available kernels are affected
- all ICS-ROMs are affected
- disable fast dormancy doesn't help(?)
- Wifi settings aren't responsible
- AC charger is equal (maybe a random thing for this user)
- turning airplane mode or data on/off does not help to kill the service

a found on the kernel code from funky81 (25/06/12) post #179

After search codes in the kernel related with this problem, I've found out the conclusion is that this wild uncontrolled wake lock related with data communication (modem)

Code:
./drivers/misc/modem_if/modem_link_device_hsic.c:wake_lock_init(&pm_data->l2_wake, WAKE_LOCK_SUSPEND, "l2_hsic");

I will try to update the code w/ Samsung Galaxy S3 source code in my kernel...

I will inform you if there's any progress with this

Could a app with it's traffic causing it? (26/01/13) post #273


....... I got suspicious. I then forced notifications from Asphalt 7 off in Jelly Beans App Administration. After doing that, I have had no l2_hsic wake lock. ......... Problem solved for me:)

Till now 4.0.4 dbt is not giving high numbers of wakelocks with l2_hsic, 11min in 24 hours cycle


Dates are using DD/MM/UT format

Sent from my GT-N7000 using Tapatalk 2
 
Last edited:

UgloBuglo

Senior Member
Aug 9, 2011
165
35
Gothenburg
I have the same kernel wakelock l2_hsic in my phone when it is otherwise idle... no idea what it is though, but in my feeble understanding it means that the phone never gees into deep sleep - and that can't be good can it? :confused:
 

rigor.m

Member
Nov 27, 2008
47
9
I have the same problem of the l2_hsic wakelock popping up and eating battery. A reset always cures it for some time but it eventually appears again... Very annoying, I hope someone figures out how to get rid of it..
 

frasch42

Member
Jul 14, 2011
28
3
Same here, l2_hsic keeps my phone awake. It's seems to start at some random point and never "switches off" again until I reboot the phone. After a reboot it takes usually takes a couple of hours before this lock reappears.
Never saw this lock on GB, btw.
 

frasch42

Member
Jul 14, 2011
28
3
I gave up.
Went back to Gingerbread using PC Odin and flashed a pre-rooted LA1.
Installed Mobile Odin Pro and flashed official LPY using Everroot and the 2 injects.
So far it has been running nicely with no wakelocks worth mentioning.

Disclaimer: I am a noob, what i have done might be unsafe and stupid.
 

StarterKid

New member
Jan 27, 2011
2
0
same problem here. I also have not found a solution, even though I force-stopped all installed programs it was still there. Bad thing, it reduces my battery life from about 3 days to 14 hrs :/
 

frasch42

Member
Jul 14, 2011
28
3
I gave up.
Went back to Gingerbread using PC Odin and flashed a pre-rooted LA1.
Installed Mobile Odin Pro and flashed official LPY using Everroot and the 2 injects.
So far it has been running nicely with no wakelocks worth mentioning.

Disclaimer: I am a noob, what i have done might be unsafe and stupid.

Update: Phone is doing great now, with uptime of about 36h.
L2_HSIC does show up in kernel wakelocks but only for about 10 minutes in this 36h period.
 

StarterKid

New member
Jan 27, 2011
2
0
Yesterday it seemed like my note cured itself, the l2_hsic wakelock was up for about 10 minutes and after 19 hrs I had 45% left. Without changing anything today it is worse like before. The Samsung-Support did not know what to do except for a factory reset, but I'd really like to find a better solution.

It seems like a restart cures the wakelock for about 24 hrs. I restarted it 1 hour ago and until now the l2_hsic hasn't come up...
 

jrinco11

Senior Member
Jul 7, 2005
114
5
you mention "2 injects" -- what are you referring to there? I did the LPY flash via mobile odin pro, but still have the l2_hsic battery drain issue, so perhaps I can try the '2 injects'?

edit: oh, SU and everroot?
 
Last edited:

bejoanakmami

Member
Dec 16, 2011
37
12
Jakarta
this deep sleep issue is the reason i went back to gb. believe me this issue will keep coming. im aware that rebooting by turning it off could fix it, but once u charge ur note while awake it will lock at 200mhz again. so annoying,..
 

gaddy888

Senior Member
Dec 18, 2011
57
3
this deep sleep issue is the reason i went back to gb. believe me this issue will keep coming. im aware that rebooting by turning it off could fix it, but once u charge ur note while awake it will lock at 200mhz again. so annoying,..

You're right. I have the same problem. A reboot fixes it but it's always back when you least expect it. You only notice it once the battery is down by an inexplicable 20%

How do we bring this to the notice of someone who knows how to fix it.

On gingerbread I have other wakelocks. "gps" and sometimes "fuel_alerted".
 

αкαѕнα

Senior Member
May 15, 2011
266
157
in your fantasy...
I joined the club and have this strange wakelock too ^^

Only 4,6% though, so it's no battery drain but regardless of that i was curious and wanted it removed :

Hope there is a more permanent solution for this than rebooting o_O
 

frasch42

Member
Jul 14, 2011
28
3
this deep sleep issue is the reason i went back to gb. believe me this issue will keep coming. im aware that rebooting by turning it off could fix it, but once u charge ur note while awake it will lock at 200mhz again. so annoying,..
I stand corrected, it DID come back, L2_hsic startet some 4h ago and never stopped again.
I've had it, I'll switch to CM9.
 

nunosm

Senior Member
Mar 4, 2008
51
3
When on charger, it's always awake at 200Mhz...

I've read somewhere that if you unplug from charger with the Note in "sleep mode", it will not enter Deep Sleep.

I had the fuel alerted wakelock because the bat was down to 5% and charged it and unplug it while screen off.

Also had the "no Deep Sleep" problem, but after I've started to wake up the phone prior to unplug the cord, it sleeps like a baby (2 days with usage) and always deep sleep when screen is off (checked by spy cpu).

Hope it helps...

Regards
 
Last edited:

altae

Senior Member
Mar 22, 2008
1,413
222
St. Gallen
When on charger, it's always awake at 200Mhz...

I've read somewhere that if you unplug from charger with the Note in "sleep mode", it will not enter Deep Sleep.

I had the fuel alerted wakelock because the bat was down to 5% and charged it and unplug it while screen off.

Also had the "no Deep Sleep" problem, but after I've started to wake up the phone prior to unplug the cord, it sleeps like a baby (2 days with usage) and always deep sleep when screen is off (checked by spy cpu).

Hope it helps...

Regards

I've also read this somewhere on xda. And when I had the problem it was exactly like this. The problem was there when I unplugged the phone with the screen off.

Sent from my Galaxy Note running ICS
 

guppyworldwide

New member
Oct 7, 2010
4
0
Unplugging while "Awake" is not the solution.

My phone goes into this permanently awake state randomly after upgrading to ICS. (I am stock, and upgraded via Kies...never messed with this phone before). I too noticed the L2_hsic taking alot of time.

I have made a concious effort to investigate this, and I can confirm that unplugging the phone while "awake" as a solution is false.

Not once since I discovered this problem have I unplugged while sleeping, but alas, I am again in a zero deep sleep situation.

Back to restarting this stupid thing every 2 days after finding my battery draining 15-20% in some short minutes.

I abslutely love this phone!!! Best in the world hands down!!! I love ICS!!! But if this problem doesn't go away, I am giving up! Samsung is both the best...and the worst!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Yesterday I had this problem with l2_hsic......

    Read the rest here

    I moved my post because I will need the space for the findings, as I don't see the light at the end of the tunnel.

    Here are the findings till now from some users.
    I will update this when new ideas/solutions have posted.

    what is l2_hsic read the rest here

    HSIC is technology for inter processor comminication. Our phone has two main chipsets AP (here snapdragon, thus the name MSM ) and modem chipset (again by qualcomm). They both are connected via hsic, ...........

    Yes, HSIC is an hardware along with its device driver used for Inter Processor Communication.

    Main principle is Android RIL communicates with help of hsic driver to communicate to the CP (modem) chip. And vice-versa. Modem chip also has the same hsic at there side also.

    .............

    That L2 does not stand for L2 of OSI layer................ There are 4 states (L0(active),L1,L2,L3) state of power saving in USB link also , hsic also uses the same convention.
    ................


    kernel related? read the rest here


    Hello
    I've been encountering L2_hsic and a few other related wakelocks for months (even years), ever since updating my I9100T to ICS (which I did the minute custom ICS roms hit web).......

    I searched around and found out the l2_hsic wakelocks are generated by a kernel file "/drivers/misc/modem_if/modem_link_device_hsic.c" which is also responsible for rpm_hsic and tx_hsic wakelocks.
    From there I went to CM git and with help from their IRC channel I found the source code for their version of this file:
    https://github.com/CyanogenMod/andr...rivers/misc/modem_if/modem_link_device_hsic.c

    A explanation from anirudhgargi what hsic is! (09/06/12) post 264 :

    HISC is the interface that connected the main Soc processor ( Also called Applciation Processor AP) to the modem ( 3G or 4G if there are two modems separately )

    HSIC is used the standard USB core library. And it is stanrd given by usb.org. The HSIC by itself consumes very less power and is one of the very power efficient and space efficient ways of interconnecting chips. Currently common to Qualcomm and Sammy Exynos architectures.

    The reason you seeing too many HSIC wake lock and other wake us's is due to the fact that the HSIC interface is waken up by modem (Normal scenarios are also so many) .


    A find about hsic from becosemsaida (09/06/12) post #107 :

    Well i have the wake-lock too and after some digging around i found this:

    http://www.synopsys.com/dw/ipdir.php?ds=dwc_usb_lpm_hsic

    A article about wakelocks from unthinkable apps(18/06/12) post #126 :

    Interesting that academia is researching this issue.
    www.theregister.co.uk/2012/06/13/fixing_android_no_sleep_bug/


    A sume of what we know from Shaftenberg(20/06/12) post #136

    - equal which modem we are using (GB or ICS)
    - all available kernels are affected
    - all ICS-ROMs are affected
    - disable fast dormancy doesn't help(?)
    - Wifi settings aren't responsible
    - AC charger is equal (maybe a random thing for this user)
    - turning airplane mode or data on/off does not help to kill the service

    a found on the kernel code from funky81 (25/06/12) post #179

    After search codes in the kernel related with this problem, I've found out the conclusion is that this wild uncontrolled wake lock related with data communication (modem)

    Code:
    ./drivers/misc/modem_if/modem_link_device_hsic.c:wake_lock_init(&pm_data->l2_wake, WAKE_LOCK_SUSPEND, "l2_hsic");

    I will try to update the code w/ Samsung Galaxy S3 source code in my kernel...

    I will inform you if there's any progress with this

    Could a app with it's traffic causing it? (26/01/13) post #273


    ....... I got suspicious. I then forced notifications from Asphalt 7 off in Jelly Beans App Administration. After doing that, I have had no l2_hsic wake lock. ......... Problem solved for me:)

    Till now 4.0.4 dbt is not giving high numbers of wakelocks with l2_hsic, 11min in 24 hours cycle


    Dates are using DD/MM/UT format

    Sent from my GT-N7000 using Tapatalk 2
    3
    L2_HISC Wake lock explanation summary

    This is getting ridiculous. Nobody knows what triggers l2_hsic, nobody knows how to kill it without rebooting. C'mon man... Somebody do something already! This is so frustrating! Please please please!!! Samsung, Android, xda-developers... Anyone! For the love of everything sacred! *end of rant*

    HISC is the interface that connected the main Soc processor ( Also called Applciation Processor AP) to the modem ( 3G or 4G if there are two modems separately )

    HSIC is used the standard USB core library. And it is stanrd given by usb.org. The HSIC by itself consumes very less power and is one of the very power efficient and space efficient ways of interconnecting chips. Currently common to Qualcomm and Sammy Exynos architectures.

    The reason you seeing too many HSIC wake lock and other wake us's is due to the fact that the HSIC interface is waken up by modem (Normal scenarios are also so many) .

    Also one imp reason is EFS sync. A concept : that the new modem architectures doesn't support a flash storage.(Saves lot of cost to manufacturer) .So every time modem needs to store something , it wakes up hisc interface and ask the AP (Main processor) to store it for him.

    So this CP storing via AP is a fairy frequent activity.

    I see the concern over this L2_hsic wake lock. I can say at this point that it is quite naturally and a necessary evil for smooth working of your modem( network 2g,3g,4g ) subsystem.

    Hope this is of some help. :good:
    1
    I got a 6h wakelock from l2-hsic today and I never installed neither nova or chrome. So I assume they can be ruled out

    Main reason is unplugging the charger without unlocking lockscreen (swipe to unlock) or unplugging when screen is black.

    Sent from my GT-N7000 using Tapatalk 2
    1
    How do you kill the settings service?

    Sent from my GT-N7000 using XDA

    I have a german Phone. Don't know if the english Names of the Items are right. Perhaps someone who has a english GT-N7000 can translate ?:

    Kill the Settings (german: Einstellungen) Service:

    Go to Settings (german: Einstellungen)
    => Applications (german: Anwendungen)
    => Running (german: Ausführen, Third Tab !)
    => Choose The "Settings" Entry (german: Einstellungen)
    => Hit the "Stopp" Button
    1
    http://forum.xda-developers.com/showthread.php?p=41338478#post41338478

    l2_hsic root cause
    Analysis of kmsg files provide a consistent pattern. Function if_usb_suspend(..) from modem_link_device_hsic.c does not call wake_lock_timeout(..) in wakelock.c in case of l2_hsic is running amok.
    The missed call to wake_lock_timeout is obviously caused by a non cancellable USB-connection.
    It is a single non expiring wakelock, what makes trouble.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone