yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ephestione:
I just noticed this clitch today, for the very first time.

Not actually the first time I notice l2_hsic taking up more than the fashionable amount of wakelock time, but today has been the hardest: 7.5hours wakelock that drained my battery after 10hours uptime with low to none usage for the day (the only other time I saw l2_hsic was the one before this, and it was about 2hours total, with a normal/average battery duration).

I don't think I can pinpoint it to something special, I have been using RocketV5 + FrancoV6 for a while now, and I didn't install anything fancy lately that I remember about. Also, my last battery run was pretty normal.

What I notice is that sometimes the pegasusq governor from Franco kernel goes crazy and sticks to 1400MHz even if the phone is idle, until I reboot, but I think this is totally unrelated, since after this l2_hsic showdown the phone has been awake, yes, but at 200MHz.

So my experience says this is apparently totally random, also because my connectivity is aready scheduled: data/wifi off at night, and on during the whole day, always in 3g mode, and I haven't changed the data usage pattern as of late.

@OP

Very good you update the first post with news about the thread, even better would be if you lso updated the title by adding the date of the last update, so we know from the subscribed posts list in Control Panel if there's anything new to read ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] adamskoc:
I had that issue just after using the non official charger... The only difference was that...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ast2001:
I'm still extatic :-)

I know that I must not rely on appearances but nearly three days (minus 6h) after the installation of LQ3 (from LPY without any data loss), l2_hsic wakelock are not going wild and I have not rebooted my Note :-)

With LPY, I have to swith into airplmane mode and reboot two or three times _a day_ to stop wild l2_hsic.

Even if LQ3 is not _the_ solution, it's a far better firmware than LPY.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] frasch42:
Like I said: I can reproduce the wakelock reliably by using the Motorola charger.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
I second that, LQ3 is faster and more stable, but I'm still wondering... Even with LPY I had only two l2_hsic issues, so I'm thinking of a different setting in your case. Can you tell us a difference in your setup? Maybe a small change?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Psxtreme:
Hi everyone, I've tried everything and nothing seemed to work until I came across this thread where some posters mentioned disabled samsung dive or whatever it is. I went into the settings and after disabling it I haven't had any crazy l2_hsic wakelocks since.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ast2001:
Four days later, I still have no problem with h2_lsic. But I've found another problematic wakelock 'multipdp' (less problematic than l2_hsic)

Since my phone was unplugged (18h ago), I have 27m of l2_hsic and 1h10 of multipdp...

To answer to your question, I don't have changed anything in my configuration. I've just flashed LQ3 on LPY.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] suhasn46:
Even I've multipdp and power manager service running about an hour on an average battery life of about 20 hours. But neither of these stop the phone from getting into deep sleep.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shchiam1978:
what is samsung Dive?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
The Samsung services aren't responsible, I have mine always freezed and wakelocks anyway.

Got some news: Today l2_hsic went wild out of nothing. Hours of standby (while on HSPA) and in the middle of the time l2 locked. So, yes, fast dormancy is not the reason.

I do the next test: I disabled geo location via Wifi/GSM, as I feel it must have a connection to the "settings".

If you really want to help pin down: When you discover the l2_hsic wakelock going wild, reboot and change ONE setting and observe. Maybe we can nail it.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] gaddy888:
I uninstalled fring. And there was an aborted download in opera which missed my notice, and I stopped it.

Apart from that I didn't do anything.

So far it hasn't raised its ugly head.

Just saying.

Every time I feel like I've nailed it, it shows up again.

Is anybody else using fring?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Braxos:
Hope it is better I will add the dates of the quoted posts too.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
This is not problematic, it only indicates that you have data transmission from some app.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Braxos:
Had same issue all night 8 hours last things I did with kies to check for updates, then I charged with wall charger not USB, I unlocked and unplugged it, then I did go to sleep! On the morning I had 9 hours wakelocks of l2_hsic.

Sorry made the last post with "fast and furious VI, xda drift" I do that slot forgetting , and . all the time plus the word suggestion isn't helping sometimes.

Hope this made it a but clearer.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
What?? :D

To clarify: don't bother testing 3rd party apps. I freezed/deinstalled everything with Touchwiz/Samsung, l2_hsic doesn't depend on that and I got wakelocks anyway.

As one user said, killing the "Settings"-Service would help killing the l2_hsic wakelock, I am sure we'll find the problem in there. And it must deal with data transmission over GSM/HSPA, no other thing makes sense.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Braxos:
As I have said before, on some posts, you can easily reproduce it with the app "TuneIn Radio" when you use it the l2_hsic kicks in for the same time as you have streaming a radio station. When you close the app the l2_hsic closed too that's the weird on it. Plus on bbs or better bbs counts the l2_hsic as a, let's say, external wakelocks and it adds it, so having audioout wakelocks for 2hours and l2_hsic the bbs says you has 4 hours wakelocks even the phone is ONLY 2 hours on.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Psxtreme:
I also had all the samsung services frozen and it didn't make any difference. The samsung dive is a service to find your phone, it's baked into the settings.apk under the security section. I'm guessing that it must operate on a lower level than the other services. All I know is that the l2_hsic wakelock has not come back since I unchecked the box "find my phone" or whatever it was.

Although today I had another wakelock which was the powermanager running crazy, for that one pulling the battery worked. One wakelock down at least?...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] miniharo:
does anyone have any exact ideas as to what the wakelock l2_hsic really points to?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] becosemsaida:
Although i already tried to figure out WHY it appears and with what app i still think it's related with data transfer on wi-fi or 3g.

Let me explain: i work all day so i only activate data connection when needed if i don't use any data transfer i have my phone in deep-sleep all day and can do about 2 days with a full charge (just calls and sms, some music). Don't have to reset or pull battery etc. etc. If i use data (wi-fi or 3g) it will only last (almost) a day.....

If i use data transfer i will get the wake lock but just for a short time (5% all day usage) i don't do resets, battery pull outs or any of the other stuff. I just clean up cpu spy log. My phone after a while goes into deep sleep, no wake locks what so ever. NO MORE RESETS FOR ME !!!!

Ok, why it happens?? Don't know, i know its related with data transfer for sure (at least on my note) and i also know it must have to do with some app that wants to go online and keeps trying untill it's timed out.

Currently i'm on 135 hours without reset, charged with wallcharger (original). Have a deepsleep count of 60% (slow week) and during the last cycle of charging had the l2_hsic for 45 seconds. Last charge was (unplugged) at 7:00 and it's now almost 15:00

Since i'm home i have wi-fi active all the time. Untill monday it will stay like this, no disconnecting from wi-fi during sleep or charge.

Once again i leave here my info about this wake lock, still ICS, LPY no root....plain stock with Apex launcher and some other apps from the (black) market

becosemsaida
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] gaddy888:
It most certainly to do with data transfer.

In fact I think the wife equivalent of the same wakelock is wlan_rx_wake. Try it next time.

When you do have he l2_hsic wakelock, don't reset the phone till you get to a wife hot spot. Just set a custom reference in BBS. L2_HSIC will be replaced by wlan_rx_wake.

I think if you then happen to turn off the wifi and switch back, the wlan_rx_wake will be henceforth referred as deleted_wakelock.

If someone could confirm this....
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Braxos:
Had 9 hours wakelocks at home with wifi on, three days ago and it was l2_hsic!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] miniharo:
Anyone has any ideas for my wake lock!? I set the custom ref when i woke up. Anyway, it seems like l2_hsic only took a small percentage out of last night
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ephestione:
Great, thanks :good:

Sorry, your problem is not related to this thread :cyclops:

Also, BBS never gives you idea of the application issuing the wakelock, so we mostly are as clueless as you are; the audiooutlock has afflicted me in the past as well, one of those weird things that disappear after a reboot with you none the wiser.

Anyway, reporting in.

I am on RocketV7, hence LQ3, and I had l2_hsic going wild yesterday; up until now, it's been once on RocketV5, and once on RocketV7, so LQ3 kernel is still not the magic pill :(

After reboot, it's slept all night long with no problems whatsoever, CPUSpy has an almost full deep sleep bar, a slightly coloured 200MHz, and the rest if blank, as would be expected since I used it close to none after yesterday evening.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] miniharo:
it seems reboot always solves everything, though the wakelock l2_hsic always returns.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ast2001:
Yes. It's time to made a resume I think :-)

I've tried (without success) the following things:

Firmware

LPY

LQ3. The better in terms of l2_hsic but not totally l2_hsic free

Modems

LPT, LR1, LB2

System / foftware functions

Samsung Dive (tracking system in parameters)

Google geolocation

Google Latitude

Exchange push mail

Twitter (native application and Samsung Social hub)

Facebook (native application and Samsung Social hub)

Fast Dormancy

Wifi enabled / disabled

Killing Settings service

GSM Only Mode

The only thing I've noticed is that the more I use data intensive applications / services, the more I have a risk to have l2_hisc going wild.

[Edit] Added GSM Only Mode
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] poopiest:
Trigger L2_hsic without charging

I'm new here but keep following you guys about this problem.

I would like to share you some of my experience.

When I first in stock UK ICS, this wakelock start after phone was charged.

Then flashed Speedmod, it didn't help.

Then moved to Criskelo v7, it worked fine for 4 days even unpluged with screen off. Until today, I unpluged my phone, went out of home, turned wifi off, and let my phone screen off.

3 hours after it was on 3G and screen remained off, this L2_hsic came back, and it started bring my phone to 100% no deep sleep. So reboot and it gone.

So I found difference Rom has difference way to trigger this bug.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
This is normal as l2_hsic is bound to data transmission.

The lock itself ("going wild") is not normal and this we are still finding out. If you are under or at around 1% of l2_hsic, everything is pretty normal.

At this time I wished, the lock came more often as after my last change (disable location over GSM) it never came back.

[edit]

As a reminder, here's something about l2_hsic: http://en.wikipedia.org/wiki/LAN_switching

That leads me to a question: Has anyone chosen "GSM only" mode? My note is at "GSM/HSPA auto", maybe there's an option?

This will be definitely my next test if testing "GSM location service" fails...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] poopiest:
I forgot to mention this....only one thing that happen during bug was activated is my friend keep send me messages by FB messenger, but I didn't turn screen on to see those message at all during that time.

---------- Post added at 08:57 PM ---------- Previous post was at 08:50 PM ----------

I will try this one too. but in my phone there are 2 menus about this.

-Google location service

-Location and Google search

Which one should I try turn it off?

Thanks
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
I disabled Google Location Service (GSM/Wifi) and turned GPS on for the time of checking.

But as I read from Ast2001, this doesn't help, but I will prove this for myself as I'm in the middle of testing.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] silverstream:
Hi shaftenberg, me again :)

When you say "go wild", what do you mean ?

Also under Kernel Wakelock, there's Time, (c/wc/ec), which should we focus on ?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
Always the same guys, hi silverstream... :D

"go wild" means: l2_hsic rises its wakelocks massively up to x percent usage resulting in draining battery in very few hours.

Only a reboot (and maybe killing the "Settings" service) will help to stop this. No one knows at this point, what exactly is triggering the lock.

But to be honest, I don't know who started "go wild" using the first time... :)

You can see this in BBS, when l2_hsic is at top position in kernel wakelocks with much more than 1 percent. To check this in a fast way, I use SystemPanelApp with its monitoring service. Under normal conditions the "system" process uses almost no CPU time, but when l2_hsic starts to hang, the CPU bar (lower third) is constantly between 1-3% - easy to see exactly, if and when l2_hsic starts.

I attached a normal behaviour of the last 2 hours in standby, if l2_hsic will annoy me again, I'll post another screen.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ast2001:
I've tried and it's not the solution.

You can switch from auto mode WSDA (3G) / GSM (2G) to GSM Only in the settings.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] silverstream:
Will try out SystemPanelApp.

I uses BBS to do some logging using different modem, and here's my findings:

Modem: LR1 (Test duration: 60min)

BBS Kernel Wake lock for l2_hsic: 258/11/258 41sec

Modem: DXLP5 (Test duration: 48min)

BBS Kernel Wake lock for l2_hsic: 400/11/400 38sec

Modem: ZCLP5 (Test duration: 57min)

BBS Kernel Wake lock for l2_hsic: 232/12/232 42sec

Modem: LB1 (Test duration: 63min)

BBS Kernel Wake lock for l2_hsic: 194/9/194 65sec

Modem: LB2 (Test duration: 37min)

BBS Kernel Wake lock for l2_hsic: 352/8/352 20sec

Modem: LPT (Test duration: 38min)

BBS Kernel Wake lock for l2_hsic: 381/14/381 51sec

Modem: LC1 (Test duration: 60min)

BBS Kernel Wake lock for l2_hsic: 314/10/314 65sec

Noticed that LPT and LB2 were a bit high even at 30+min, thus I stopped the test, I suspect that's what you referred to as Wild.

Also I'm taking the middle number as reading, since it's c/wc/ec (count/wakecount/expirecount).

Am I right ?

So based on the above, LB1 seems the BEST ?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shaftenberg:
Short answer? No. :D

In fact the l2_hsic usage varies and 60 minutes is too short to say l2_hsic is behaving bad, because it is bound to data usage, thus it is normal to have kernel wakelocks of l2_hsic if you use data.

Meanwhile several users found out that, regarding the wakelock issue, it is pretty equal which modem you use.

I am not sure I did understand: You have tested "GSM only" and l2_hsic was behaving bad also?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ast2001:
Absolutely

Envoyé depuis mon GT-N7000 avec Tapatalk
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] silverstream:
Am getting ~3% CPU at idle........ no good .....
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] funky81:
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)

./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
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ast2001:
For my usage, LQ3 is the best choice...

Envoyé depuis mon GT-N7000 avec Tapatalk
[Off-topic] The-Last-Hylian:
Has anyone else seen on HTCs FB page they're talking about what happens at 10:08?

Anyone got any clues as to what they're talking about?
[Off-topic] surfer1000:
The end of the world is nigh:)

Or HTC's update server blows a fuse
[Off-topic] Evil-Dragon:
HTC announces they're bankrupt due to the One X returns.
[Off-topic] surfer1000:
All of the Quality Control staff are getting sacked via a text message
[Off-topic] Nubzori:
They're gonna release 1.98 firmware with android 5.0 jelly bean
[Off-topic] tkolev:
Don't know what happens at 10:08, but I know what happens after that. 10:09.
[Off-topic] goulies:
10:08 in what country?
[Off-topic] tkolev:
Even more important - 10:08 which day :)
[Off-topic] ShyamSasi:
Good one. Desire C announcement maybe?
[Off-topic] twistedh:
Guess their clock broke...
[Off-topic] Dmitry N:
HTC Sync Manager will be out.

Any more guesses?
[Off-topic] surfer1000:
10.31am.....nothing, late as usual for UK
[Off-topic] tadas_max:
well in my opinion it probably has nothing to do with getting anything new. its the time they use on all official htc phones photos. just check gsmarena htc page and you will see they all show 10:08
[Off-topic] The-Last-Hylian:
Well it's the HTC Facebook page US I think, not the UK one so it could be 10:08am or 10:08pm USA time...
[Off-topic] westwood749:
I may be totally missing the point but if you guys are asking what it means then it means this.

Basically they always used to use 10:08 on an analogue clock because it looked like a smile, but as everything evolved into digital clocks they obviously decided to keep the same time, although it obviously doesn't look like a smile anymore, but I guess it's just one of those traditions they wanted to hang onto.
[Off-topic] graemeg:
10:08

According to the pic on various diff days

Perhaps its when their customer support go on their 5 hour coffe breaks, DAMN, that be why no-one answers the phone!!!!
[Off-topic] Goku80:
10:08 is hammer time

[YOUTUBE]WIHAkqCls4A[/YOUTUBE]
[Off-topic] jupppo:
I just got an firmwareupdate (10h in Germany)...installing it now
[Off-topic] craggybuk:
It could actually be the date when HTC get their act together and fix all the problems 10:08 - 10th August :)

Dont envy our American subscribers though, they won't get the updates until 8th October.
[Off-topic] leventccc:
Look at the dates. 26 Feb HTC One X Event. 6 October XL Release Event. Is it means anything?
[Off-topic] theliquid:
Haha, that might be a case for myth busters :D

OT: I twittered them yesterday that they might roll out S-OFF for everyone at this time? :D
[Off-topic] The-Last-Hylian:
Some articles on 10:08

http://www.birdsontheblog.co.uk/what%E2%80%99s-the-significance-of-1008/

http://www.blogcadre.com/blog/stella/10_08_why_analog_watches_are_set_to_this_time_in_advertisements_2006_12_12_12_04_34
[Off-topic] skywalker1970:
Funniest but apt. I hope HTC stays on though. Don't want the world to be iPhone or Sammy using phone drones. Competition is good.
[Off-topic] AFCAjax:
Remove Sense from their ROMs? And give us the preview build from Android 5.0 as OTA?

Edit: typo
[Off-topic] exocetdj:
10:08 seems to be the time on the sense clocks that they show on promotional photos etc

http://www.htc.com/www/smartphones/
[Off-topic] The-Last-Hylian:
>.<

Sorry!
[Off-topic] TheSkinnyDrummer:
Hmm...funny. clocks sold in stores usually display 12:08 for some reason.

Sent from my coffee pot.
[Off-topic] goulies:
So what happens? nothing?
[Off-topic] ursubpar:
10:08 - october 2008

The month and year the G1/dream, the first android device, was released
[Desire General] sypack:
Hi,

I'm having wifi problems on my Desire. I can no longer connect to wifi. When i turn my wifi on it turns itself off after about 15 seconds.

Sometimes i see the message: Obtaining IP address and then it turns itself off.

I've tried the "FXR WiFi fix and rescue" app and sometimes it fixes my wifi and i'm gold. But the next day or a couple of hours later the wifi no longer works.

Flashing a new radio doesn't help, deleting the wpa_supplicant.conf file sometimes works.

I'm currently running Mildwild CM 4.5. Have tried many other roms but to no avail.

Anyone experiencing the same problems?

thank you !
[Desire General] Spierbal:
Tried rebooting your wifi hotspot or router?

What is your current radio? You could maybe change your ril? Do you have good 3G, calls signal etc?

Also, check your WiFi sleep policy, and set it to never. Perhaps try changing channels on your router.
[Desire General] sypack:
Rebooted my router, tried another router, have the same problem at work or at my parents.

I have radio 5.11.05.27, have tried numerous other radio's too. Wifi sleep policy is set to never.

I have good reception on 3g and call signal.

Is there a way you view a detailed log to find out where the wifi flips?
[Desire General] Spierbal:
On the day of the occurence did something change? your router, your phone, new tariff, reach the maximum number of connections. Did you do any updates, flashing new rom etc. Maybe there was a update to your router ISP?

In terms of logging, this can be really good way to find out what happening behind the scenes.

If you got ADB installed, plug your phone in usb, enable usb debugging mode. Once this is done, type the following command:

adb logcat

This should initiate the logcat and your command prompt will begin to fill with a bunch of text.

Once the logcat is running, please RECREATE the wifi issue you are having. to stop the logcat on your keyboard press ctrl+c.

If you don't understand the text, you can right click, choose select all then press enter on your keyboard, this will copy the entire log to the clipboard. Once this is complete visit www.pastebin.com and paste your log there and submit. Then grab the link from the address bar and paste it on xda forum with your bug.

Finally, if you are not comfortable with command prompt, install alogcat or logcat app in the play store.
[Desire General] sypack:
I'll try logcat when i get home tonight.
[Desire General] Spierbal:
If you already tried different kernels, I am afraid you might have to reflash back to stock, if it still happens, lock your bootloader and send it back. I am sorry I could not be of more assistance.
[Desire General] sypack:
Your help is much appreciated.

Sending it back is no option, cannot live without a smartphone :p

Going to stick with the mobile connection and buy a new Nexus round christmass.
[HTC Amaze 4G] DeadWestern Shogun:
Need help! My camera closes everytime I open it, doesn't force close or crash etc, screen just goes back to home. I stopped it, rebooted it, battery pulled it, nothing works. Is it my Rom? Running unofficial ics leak sense 3.6. Anybody know???
[HTC Amaze 4G] glacierguy:
Maybe u debloated too many apps/odex files? I would just retry flashing ics, or restore the backup u made once flashing ics. :D

Sent from my HTC Ruby running Sense 3.6