yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

it doesn't have values for black or mid gray...

mako | 4.2.2 factory stock
[Nexus 4 Original Android Development] thesebastian:
Thanks! Downloading!

Did you do this from AOSP? (or another way exists to edit google occam kernel?)
[Nexus 4 Original Android Development] endursa:
AW: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

After I used your kernel on 4.2.1 for a while I have gotten somewhat blind to the fact that the 3g connection suffered from deep sleep issues, after a while I had to re toggle the connection for it to become available again (despite the icon showing a connection)

Just Yesterday I decided to try your 4.2.2 stock kernel with gamma and UV enabled, and I have a fully working 3g connection back again! Unfortunately also the hsic wakelocks have gotten more (obviously) but I think I can life with that if it means that my 3g connection does indeed work without troubles :)

I'm really sorry that the whole patching to reduce said wakelocks doesn't work out so great after all, but I figured there has to be some reasons for Google too, not to include the patches!

Could you compile a 3.40.31 kernel with everything but the caf patches for hsic? I would love to dig deeper into the whole 3g active icon but no connection problem :)
[Nexus 4 Original Android Development] Harsh:
yes that is next thing in that source. I will add them but linux korg merge is creating conflicts so have to solve them one by one.
[Nexus 4 Original Android Development] :
This kernel still uses the faux gamma implementation not the one in Franco with black, brightness, mid etc.
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

oh... any chance to use Franco/moles style? its so much more intuitive

mako | 4.2.2 factory stock
[Nexus 4 Original Android Development] ckret:
it uses them

in this layout

you just have to set the values with a script. there is not other way to set them.
[Nexus 4 Original Android Development] flxdms:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

As far as I know, faux's gamma controls are different from Harsh's. Also, with harsh we have control over all the 27 gamma settings. Franco only lets you change 7 of them(and applies them to all 3 gamma lines) . I'd rather keep the settings we have right now.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

+1

Same here
[Nexus 4 Original Android Development] Lownita:
AW: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Your settings/scripts look the same on 4.2.2 kernel as on 4.2.1? Or do I have to change/switch values? Because I read that whites and greys were switched on TF kernel (and also on franco perhaps?).

Papastalked from my Nexus 4
[Nexus 4 Original Android Development] :
From the argument between Harsh and Motley, I'm sure he implemented Faux gamma and made it possible to edit with scripts in a simpler manner

If you've tried PA with its stock halfbreed colors kernel and then switch to Harsh and use halfbreed values, you'll notice a major difference

The implementation by moles is better by far IMO but I like this kernel too much and the gamma works well enough
[Nexus 4 Original Android Development] 75markus:
gamma scripts look excactly the same on new 4.2.2. harsh build (16.02), nothing gamma related has changed

i have no idea about other kernels, i don´t switch kernels anymore, i´ll stick to this one ;)
[Nexus 4 Original Android Development] flxdms:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

I think the script only gives us access to the p_gamma settings. Since moles implements his modifications directly from the kernel source, he has access to more settings than we do. If there was a way to have access to the n_gamma line the colours would probably look better.
[Nexus 4 Original Android Development] Harsh:
I dont like Franco's implementation of Gamma so I will stick to faux's gamma. And its got more choice than franco for sure.

In franco's gamma, all RGB are set equal while in faux you can control all 27 values individually :D..

If ppl want we can give names to all values for red, green and blue individually in init.d script, for that naming we dont need new implementation.

And for p_gamma and n_gamma, that is same in both gamma settings. everyone is changing p_gamma and copying same values in n_gamma. So its exact difference is not known.

But its possible to expose another 27 gamma settings for n_gamma in faux's gamma settings with little change, but I dont think its necessary. We already have 1000s of possibilities to tweak, dont want to make it million possibilities and more complex.
[Nexus 4 Original Android Development] ckret:
maybe harsh can implement francos code to the gamma values

since its open source it shouldnt be problem is it?
[Nexus 4 Original Android Development] Azurael:
Read the post immediately above yours. :eek:
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

I'd like exposure to all values if it isn't too hard.

mako | 4.2.2 factory stock | harsh
[Nexus 4 Original Android Development] flxdms:
I'd like that as well.

I'm pretty sure this :

static char p_gamma_r_setting[10] = {0xD0, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char n_gamma_r_setting[10] = {0xD1, 0x40, 0x44, 0x76, 0x01, 0x04, 0x02, 0x30, 0x20, 0x01};
static char p_gamma_g_setting[10] = {0xD2, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char n_gamma_g_setting[10] = {0xD3, 0x40, 0x44, 0x76, 0x01, 0x00, 0x00, 0x30, 0x20, 0x01};
static char p_gamma_b_setting[10] = {0xD4, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char n_gamma_b_setting[10] = {0xD5, 0x20, 0x23, 0x74, 0x00, 0x1A, 0x10, 0x50, 0x33, 0x03};

won't look the same as

static char p_gamma_r_setting[10] = {0xD0, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char n_gamma_r_setting[10] = {0xD1, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char p_gamma_g_setting[10] = {0xD2, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char n_gamma_g_setting[10] = {0xD3, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char p_gamma_b_setting[10] = {0xD4, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};
static char n_gamma_b_setting[10] = {0xD5, 0x40, 0x44, 0x76, 0x00, 0x19, 0x04, 0x42, 0x20, 0x01};

and it doesn't hurt to at least try!
[Nexus 4 Original Android Development] Lownita:
So there are 2 sorts of gamma implementations at the moment, franco+trinity and harsh+faux+motley. With the second one being more accurate?
[Nexus 4 Original Android Development] faux123:
@harsh

Check here for complete explanation of Gamma and its relationships :D

http://xdaforums.com/showpost.php?p=38155717&postcount=6086

http://xdaforums.com/showpost.php?p=38134041&postcount=666
[Nexus 4 Original Android Development] djvoleur:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Ohai Harsh :p
[Nexus 4 Original Android Development] abufaka:
i have to admit i couldn't get rid of the SOD however hard i ramped up the voltages or deleted apps. so i'm off to franco's (uv'ed it to the same values) and SOD is completely gone. don't wanna start any bashing and would have sticked to harsh's as it's a tad bit smoother at least subjectively, but the frequent SOD killed it for me.

i was also unable to get any logs, as it wouldn't happen if something was active in the bg (e.g. writing logs to sd.)

anyway, hope i can return if this issue can be identified ;)

all the best!

PS: one last thought, how is the deep sleep voltage determined? is it hardcoded or the same as min freq?
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Hi, good to see old mates here. Many of us got N4, from 512 ram to 2gb is awesome feeling.

No worries mate. I hope it can be fixed. Did you try running it on PA or any other(codefirex or liquid) non stock based ROM? It solves sod somehow.

Deep sleep voltages are not adjustable. And frequency is between 19mhz to 47mhz in deep sleep. But my information could be incorrect.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Most accurate interface at the moment is faux's.
[Nexus 4 Original Android Development] djvoleur:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Amen to that...I think I'm just gonna intake this and the nexus feeling before I dive into anything :p can't wait to try this kernel...I'm using faux's enhanced kernel atm... I tried yours a couple days ago but ran into a SOD...running stock and rooted, of course...what kind of logs do you need specifically?
[Nexus 4 Original Android Development] nycelitemaster:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Hey dj, whats good bro? I havent flashed any kernel except harsh, so far loving it.. Mad this is great.

Sent from my Nexus 4
[Nexus 4 Original Android Development] djvoleur:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Sweet...things are good...I gave in and bought one :-/ what ROM do you have installed?
[Nexus 4 Original Android Development] JeanEatsWorld:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Just my feedback:

I tried pretty much all the kernels and I can say that so far this kernel is the one who gives me more battery life..but...the phone is terribly slow... even the keyboard is horrible to use..

I tried wiping dalvik and fixing permission but still lags every second...
[Nexus 4 Original Android Development] Lownita:
[KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Would be awesome if in some future a common interface is developed so that it gets easy for us to exchange colors between users/kernels in no time :) ATM this is difficult.
[Nexus 4 Original Android Development] estallings15:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

My experience is the opposite. You should probably flash the stock kernel, then flash harsh kernel again.
[Nexus 4 Original Android Development] djvoleur:
LOGS...

On Bigxie OTA...with your 16/02 release...

I was messing with turning the screen on and off after it booted...I turned if off and it would not turn back on...but the screen did light up (black dim screen) but did not show the lockscreen...after messing with the on and off button it eventually showed me the lockscreen...got a logcat...

I just rebooted and this time I did get a SOD...got a kmsg...
[Nexus 4 Original Android Development] wizshaw:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

My experience has also been the opposite. Best kernel that I gave ever used by far.
[Nexus 4 Original Android Development] nycelitemaster:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Stock recovery, stock rom, harsh kernel. Perfect.

Guys need to install stock kernel before installing harsh kernel and revert stock files such as mpdecision and etc. Works flawless.

Sent from my Nexus 4
[Nexus 4 Original Android Development] JeanEatsWorld:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Actually I flashed this kernel after a clear installation of pa 3.0... now I'm running the stock one.. I couldn't stand anymore such a slow motion experience.... I'm really disappointed.. I can't understand why for real....
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

:eek: how you do that? My n4 is flying with this kernel, and battery life is pretty good too.

Uninstall all kernel app, like trickster, franco kernel updater, or faux kernel enhancement if any. Then reboot.

Or wipe system and cache then reflash your rom, let it boot, reboot to recovery then flash this kernel.
[Nexus 4 Original Android Development] bleuf1sh:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

thought you guys might me interested in this

http://xdaforums.com/showthread.php?p=38163537

mako | 4.2.2 factory stock
[Nexus 4 Original Android Development] :
I'm also using PA 3.0 just updated to Feb 18 build and the performance is even better than the PA stock kernel, your experience is polar opposite of mine, doesn't make sense to me, there must have been something else that happened
[Nexus 4 Original Android Development] astrall:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Can anyone provide me with the init.d + addon script with moles' halfbreed colors. (im using xda app so I can't search) Thanks. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Lownita:
AW: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

http://www.mediafire.com/?mnttdfpgqnoey all there

Papastalked from my Nexus 4
[Nexus 4 Original Android Development] Crisisx1:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Can those be flashed over any kernel or just over harsh kernel
[Nexus 4 Original Android Development] DowntownJeffBrown:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Just Harsh
[Nexus 4 Original Android Development] Crisisx1:
Re: [KERNEL][UV][Linux 3.4.31] Harsh Kernel build Feb-16 - JB 4.2.2

Thanks..

I think IMA try all of those presets and see which one is best ...lol I hope that's not too much flashing..

Which preset are you using with harsh kernel?
[Nexus 4 Original Android Development] flxdms:
Personally, I'm using

#!/system/bin/sh

# RGB colours
echo "175 175 175" > /sys/devices/platform/kcal_ctrl.0/kcal

# Gamma settings
# -------------------$$$$$$------------------
# Based on
# g_white 0
# g_mids 100
# g_black 255
# g_contrast 0
# g_brightness 0
# g_saturation 200
# g_greys 20
# --------------Setting gamma presets--------

echo "208 0 100 255 0 0 0 200 20 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 0 100 255 0 0 0 200 20 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 0 100 255 0 0 0 200 20 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_b

# -----------------end-----------------------

I didn't check if the colours were "correct" or not. I just like the way they look.
[Nexus 4 Original Android Development] Lownita:
Please help me to understand this:

echo "208 g_white g_mids g_black 0 g_contrast g_brightness g_saturation g_greys 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 g_white g_mids g_black 0 g_contrast g_brightness g_saturation g_greys 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 g_white g_mids g_black 0 g_contrast g_brightness g_saturation g_greys 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_b

1. What do the "208", "210" and "212" at the beginning of each line stand for? Are they always the same?

2. What do the numbers ("1" in my example, "2" in your script) at the end of each line stand for?

3. At position five, it is always "0"?

4. With my example posted (I found it in this thread) I can easily adapt every profile from franco/trinity to harsh?

5. In your script, values for each color (kgamma_r/g/b) are the same. But they could also be different, right? But that is not possible in francos implementation, so we have to have them all the same if we adapt a profile from his kernel/thread, right?

edit: 6. I read that whites and greys were mixed up? So would I have them to switch positions in my example? That would not fit the script you posted though. Another thing that confuses me!

edit2: Alright I found that visceralpsyche was the one who mixed up whites and greys, not harsh in his kernel :) Compared viscerals original post to your script in 75markus mediafire.

Thanks a ton!
[Nexus 4 Original Android Development] ftarules:
USB Host Request

Harsh,

Can you try to implement this in your Kernel? It would be great.

http://xdaforums.com/showthread.php?t=2151159
[Nexus 4 Original Android Development] :
+1 for OTG USB
[Nexus 4 Original Android Development] flxdms:
1. 208, 210, and 212 are always the same on Harsh. These values do not change.

2. No one really knows what the last digit is for. According to this post the last digits represent midpoints.

3. No. I've seen gamma settings that had it set to something other than 0. Harsh has 0x01, 0x01, and 0x03 by default at that position for r, g, and b respectively. Again, according to this post, the fifth position (4 if you count from 0) represents the gamma grad(iant?).

4. You should be able to do so. Please note that franco's g_greys value is Harsh's g_whites value. (Technically, though, Harsh doesn't call the first/second position anything. So the real layout would start with g_greys and end with g_whites if you're converting from franco and it'd be the other way around if you were to convert moles' values)

Something like this on franco :

Whites [B]42[/B]
Mids 68
Blacks 118
Contrast 20
Brightness 6
Saturation 7
Grays [B][COLOR="red"]32[/COLOR][/B]

would look like this on Harsh

echo "208 [B][COLOR="Red"]32[/COLOR][/B] 68 118 0 20 6 7 [B]42[/B] 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 [B][COLOR="red"]32[/COLOR][/B] 68 118 0 20 6 7 [B]42[/B] 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 [B][COLOR="red"]32[/COLOR][/B] 68 118 0 20 6 7 [B]42[/B] 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_b

6. You are right. You can have different values on kgamma_r/g/b, but if you're converting a colour preset from franco, kgamma_r/g/b will be identical.

For example, this is what molesarecoming's holoblue would look like on Harsh

#!/system/bin/sh

# RGB colours
echo "249 249 255" > /sys/devices/platform/kcal_ctrl.0/kcal

# Gamma settings
# -------------------$$$$$$------------------
# Based on
# g_white 0x38
# g_mids 0x44
# g_black 0x74
# g_contrast 0x1C
# g_brightness 0x00
# g_saturation 0x38
# g_greys 0x0A
# --------------Setting gamma presets--------

echo "208 56 68 116 0 28 00 56 26 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 56 68 116 0 28 00 56 26 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 56 68 116 0 12 02 88 26 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_b

# -----------------end-----------------------
[Nexus 4 Original Android Development] suua:
Are these flashable zips? i mean can i flash these in recovery on top of the kernel?
[Nexus 4 Original Android Development] drdrewdown:
yes, in fact that's the only way they work
[Nexus 4 Original Android Development] Harsh:
Guys new build updated

Changelog Build Feb-20

:

Linux 3.4.32

Updated RAW to caf latest sources

Download links in 1st page OP.

As usual, If you like my work, hit thanks :D
[Nexus 4 Original Android Development] icemasta31:
I hear init.d script for undervolting, but have no idea how to create the script and have the phone use those values on boot. Does anyone have a tutorial?
[Nexus 4 Original Android Development] DynamicRam:
I use the attached script, it will undervolts all the frequencies with the same value (50mV) you can edit it with any other value
[Nexus 4 Original Android Development] freaksamael:
be aware the above script will work only for fast binned CPU (already harsh's kernel is undervolted by 100mV on all freqv)
[Nexus 4 Original Android Development] DynamicRam:
That's true, you should create another script to reset this undervolting in case you get bootloops
[Nexus 4 Original Android Development] Lownita:
@flxdms Thank you!! Whites and greys switching in franco would also adapt to trinity, right?
[Nexus 4 Original Android Development] undercover:
Matrix 3.5 which i believe doesn't have fix in that version.
[Nexus 4 Original Android Development] dwang:
tried your datatest kernel, it seemed to be running ok, but after 15min, i couldn't turn the screen back on so I went back to motley exp10. Not enough time to determine if the issue is fixed or not.
[Nexus 4 Original Android Development] Harsh:
do not UV as you do in other kernels, and remove uv on boot if you have it. My kernel have different voltages by default. So need to UV accordingly.

If there is kernel with stock voltage I can uv -150

but when kernel is already at -100 uv or more, we cant uv -150 as it would add up.
[Nexus 4 Original Android Development] dwang:
didn't uv at all...

also flashed reset kernel first before flashing yours.

my cpu is also fast binned, so default -100 uv shouldn't cause any issues.
[Nexus 4 Original Android Development] Harsh:
Okay. Incase if you flash newer kernel and find problems, try getting logs next time it helps a lot in finding a solution or if you are near computer you can pull dmesg and last_kmsg using adb with computer even when screen off :confused:

I am using datatest build since i compiled, no problems at all. Restarted my wifi router many times as I was adding few mac addresses in ban list, so i had many 3G/wifi switches. all was working fine.
[Nexus 4 Original Android Development] zhuozhi211:
I am in Singapore with operator Singtel.

Logging since morning... will report when available.
[Nexus 4 Original Android Development] Mahdi786:
Hi Harsh,

I built bricked kernel without these commits and I have no screen lockup.

https://github.com/CyanogenMod/lge-kernel-mako/commit/3ac662c19e058a47cd1558c60e7d7fd2513406bc

https://github.com/CyanogenMod/lge-kernel-mako/commit/bfe53ea7921a62230ef322afb6fc208045d10d8a

https://github.com/CyanogenMod/lge-kernel-mako/commit/c9b11ac098889d48d84d2de12e1893a44d90a4d4

https://github.com/CyanogenMod/lge-kernel-mako/commit/4e819b43445a39c6cfad4b897ab77d015eccf814

https://github.com/CyanogenMod/lge-kernel-mako/commit/51f7fa242f886c1467da40d7f6051b4ffd1c4d45

https://github.com/CyanogenMod/lge-kernel-mako/commit/cd92faa44a032782b6ecaa42ba40597bc3c92d38

before when I built with all of cm's hsic patches I had the same screen lock up like everyone else, I've read in faux thread people are having the same problem.

The msm_hsic wakelock is still there but its been drastically reduced and idle battery drain is much better with s2w enabled.
[Nexus 4 Original Android Development] Harsh:
Those are qualcomm's patches so there should be some patches missing which are causing troubles, we can fix it without reverting above commits by adding more patches :confused:. Screen lockup never happened to me yet, nor i have data problems. Need to solve data issues first.
[Nexus 4 Original Android Development] Mahdi786:
Faux just said he had a lock up and he pulled a log
[Nexus 4 Original Android Development] faux123:
As I have been saying in my own thread, s2w has an irq bug to begin with. The EHCI wakelock fix just expose it more. I believe I have fixed it, will update my github when I am home :p.

Edit:

Here's my latest patch to fix this.

https://github.com/faux123/mako/commit/03d21e19bf4983995b1fc27dfbd59a1037fe6a2d
[Nexus 4 Original Android Development] show-p1984:
It's not a s2w bug.

The touch controller is sometimes not sending the last interrupt which tells us that all touches have been released. There is an easy fix for that (which is already in my code for the next release): Just use the touch release function of the driver on early suspend :)
[Nexus 4 Original Android Development] zhuozhi211:
not sure if log still needed... this was on build 02Jan.

I experienced a few incidents of data stuck. but am not sure which was related to service provider, or the kernel issue.

If need to pinpoint 1, i think around 630pm i had a data stuck.

update: just happened again, this time i am very sure it was not the telco fault.

see screenshot - i triggered off data, but the icon still stuck as H for a good 5 mins. it comes back again after some time when i triggered the data back on.
[Nexus 4 Original Android Development] eep2378:
http://d-h.st/om9

http://d-h.st/s59

Just experienced data drop on 1/2 build dmesg and logcat attached