yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] damac:
Hi, I'm interested in getting l2m working. Tried editing the file and saving using root explorer, then rebooting, but that didn't work.

Unrelated, I'm trying to get Internet calling working on CM11 nightly (Tried on stock kernel, this one, and kangaroo kernel, same results). I come from Desire HD Unofficial CM11 by Mustavalkosta, in which it worked using same Internet calling settings.

Now on CM11 official for HTC one, but on internet calling, call connects but both parties don't get any sound. Don't know if this is a kernel issue.

I tried an app (CSipSimple) and using that it works, but the sound has delays, and I prefer to get it working in the dialler when it is inbuilt.

Could this be a kernel issue? Anything I can do to help find where the issue lies?

Thanks.
[One (M7) Original Android Development] tiny4579:
I know little on sip calling. Not kernel related. I changed little from cms kernel so it wouldn't be a kernel related change even if the kernel had anything to do with it. All files in sys are generated at boot so you need an init.d file to set it each boot.

Don't worry, with the 2.1 release, you won't have to mess with anything if you use the scripts I'll provide.
[One (M7) Original Android Development] damac:
Thanks [MENTION=3500210]tiny4579[/MENTION].

Another thing, does enabling fastcharge break usb storage access? Also, is it possible to have conventional usb storage rather than MTP (not sure that's the acronym). Again, had that as a choice in CM11 for DesireHD, but that one actually did have an SD card, and IIRC this was added by [MENTION=3382363]Mustaavalkosta[/MENTION] as a small modification to the original CM.
[One (M7) Original Android Development] tiny4579:
No to both questions. Fast charge allows USB access still on this device. Mass storage isn't supported on this device so you're stuck with mtp. Why do you need conventional mass storage?

I could look into the possibilty.
[One (M7) Original Android Development] na2rboy:
I just edited the updater script to m7wlv on my Verizon HTC One and installed. Will let you know how it goes.
[One (M7) Original Android Development] damac:
Don't particularly need it, was just curious about it. I feel that conventional usb storage was faster...
[One (M7) Original Android Development] fluxgfx:
In the short future what are the plans for this kernel? Anything specific?
[One (M7) Original Android Development] sssssbarn:
Anyone try this kernel with cm11 Snapshot m8

Sent from my One
[One (M7) Original Android Development] tiny4579:
On the Galaxy Nexus I started very stock like and didn't merge many commits from outside sources. I will try to do the same on this device unless I come up with/find bug fixes to CM issues from the kernel side.

I need to push another build but there are no actual kernel changes from 2.0 to 2.1 and I wanted to have an actual kernel change. I suppose I could push the zip up with the scripts, but I want to prepare a proper release, so it's not ready yet.
[One (M7) Original Android Development] manups4e:
[MENTION=3500210]tiny4579[/MENTION] may ask you to help us? we are trying to port the L preview to htc one,

the rom boots but it's super glitchy and the logcat shows only 1 error that fills the logcat related to graphics E/qdhwcomposer( 199): Failed to call ioctl MSMFB_OVERLAY_SET err=Math result not representable we are using cyanogenmod kernel and cyanogenmod libs to make the rom boot...can anyone help us? here's the logcat
[One (M7) Original Android Development] tiny4579:
My resources are focused on cm11 and this kernel. I don't have time to look into it, and we may not be able to do anything without an updated kernel source or blobs. How is the nexus 4 doing it? You should be able to mimic the same. I thought they used the same blobs.
[One (M7) Original Android Development] manups4e:
They are using the same blobs but google 4.4.4 kernel
[One (M7) Original Android Development] tiny4579:
Try the blobs for cm11 on m7. That nay be the issue. If they try the aosp blobs for nexus, we also would need kernel changes to work with that. The cm11 kernel and blobs should work in theory.
[One (M7) Original Android Development] manups4e:
yeah but both Nexus 7 and cm11 for m7 blobs give as output that error..
[One (M7) Original Android Development] lamortcroix:
Yeah. Works well.
[One (M7) Original Android Development] fluxgfx:
Tiny4579 thx for the quick update on your progress with this kernel
[One (M7) Original Android Development] tiny4579:
I've been trying to fix bugs on CM (display on lag, flicker, audio skipping, particularly Bluetooth).

So far I have been unsuccessful. I would like to push out an update that actually has a worthwhile change. If my testing goes as planned, I may have a small patch to ondemand later today.

If not, I can still have the boot scripts added.
[One (M7) Original Android Development] tiny4579:
FYI, 2.1 is live finally. This should address some concerns about L2M by adding a script to enable it on boot and modify the keylayout file.

It also adds scripts for USB fast charge and BLN. All scripts require busybox and init.d support to apply automatically at boot.

All scripts are run from terminal emulator or adb shell (need to have root acess).

Type su to make sure that you have the root prompt (# instead of $).

USB Fast charge - doesn't stick on reboot

ffc

Enable BLN

bln enable

or

bln on

Disable BLN

bln disable

or

bln off

Enable L2M

l2m enable

or

l2m on

Disable L2M

l2m disable

or

l2m off
[One (M7) Original Android Development] h4waii:
Been using 2.1 for a few hours now. Great stuff, I was getting excellent battery life on previous versions, and no lag at all. All the other CM11-compat kernels I've used either had massive lag on inputs, or just destroyed battery life holding on high frequencies.
[One (M7) Original Android Development] azndan2:
Ran your kernel on my Verizon GNEX and loved it.

Crossing my fingers that you can fix the audio stuttering over BT. Thank you for your work!
[One (M7) Original Android Development] dog77k:
I have l2m, thanks tiny
[One (M7) Original Android Development] poondog:
Tiny how are you finding those patches from stratos?
[One (M7) Original Android Development] tiny4579:
I like them, but mainly because the scaling seems more accurate. I've noticed stock ondemand in CM seems to scale too quickly even under a lower load. This should allow it to idle at 384 a lot more.
[One (M7) Original Android Development] poondog:
I noticed you only picked half of one of the commits to ondemand too. Good to see it working well. I'm going to try this on sense tomorrow

Thanks for the response
[One (M7) Original Android Development] TheUndertaker21:
Anyone having some screen flickering issues?
[One (M7) Original Android Development] tiny4579:
There is screen flickering in the stock cm kernel. Not new to this kernel. If you want to help please check my post and fill out the spreadsheet. Not sure yet but the issue may be specific to the phones that use a sharp panel.
[One (M7) Original Android Development] tiny4579:
I picked the entire commit initially but it messed with scaling. I may reintroduce the multiphase feature again as the max frequency is still being used more than I thought it would, though I believe this still has some value.
[One (M7) Original Android Development] h4waii:
I haven't had any issues with the screen and this kernel at all.
[One (M7) Original Android Development] fluxgfx:
Ahh I was wondering as well. I'm looking forward to see how it fairs. Going to test it just now.
[One (M7) Original Android Development] kopeko:
I'm running cm m8 on m7 and running tiny2.1 but I don't have logo2menu option in my tricksmod app , I flash the kernel in twrp2.7.1.1
[One (M7) Original Android Development] tiny4579:
That's a trickster mod issue. If you look back you'll see another way to activate logo2menu.
[One (M7) Original Android Development] kopeko:
yep just activate it via terminal, thank you
[One (M7) Original Android Development] mrgwap:
When I activated it thru terminal I got system ui force close on reboot :( any suggestions?
[One (M7) Original Android Development] kopeko:
when i got a problem i always do a clean slate and install everything (format; cache,dalvik,data,system then flash the ROM, reboot to system then flash the kernel and activate it in terminal) if that can't fix ur problem then I got no idea
[One (M7) Original Android Development] mrgwap:
Eh I just activated double tap back button for settings in gravity box. Thanks though
[One (M7) Original Android Development] wRexz:
is it possible for 4.4.2 RUU stock Rom?
[One (M7) Original Android Development] mrgwap:
Can we use this kernel for aosp ROMs like dirty unicorns?
[One (M7) Original Android Development] tiny4579:
No. AOSP and cm and its derivatives only.

It should work but it only works if the ROM uses the caf drivers as the kernel is closely xm based.
[One (M7) Original Android Development] mhejek:
Im folowing you since droid inc tiny :thumbup:
[One (M7) Original Android Development] mhejek:
[MENTION=3500210]tiny4579[/MENTION] could u make kernel for sense ?just like old inc :cool:
[One (M7) Original Android Development] tiny4579:
No plans to make a sense kernel at this time. You already have a good selection. I don't think I'd have anything new to add to the table. When I did it on inc, it was because there was no selection of kernels for sense that ran gingerbread.
[One (M7) Original Android Development] ANDR01DN00B:
I remember you saying that you don't want to include the wake features, but can you please make a separate version of the kernel with them? I really miss them from sense. BTW it's a great kernel and I'm getting really good battery life despite it being kinda feature- heavy.

Thanks in advance
[One (M7) Original Android Development] tiny4579:
I wouldn't call it feature heavy. Not compared to elementalx. I don't.

But the wake features I don't want to do as that introduces a longer delay. Though I played with a recent build, stock kernel. So the screen on delay could be fixed. If that's the case, I may test the wake options.
[One (M7) Original Android Development] tiny4579:
First make sure you are on a recent CM nightly from the last few days (8/2 or 8/3 should be fine). The reason I ask this is I synced with CM yesterday and the screen on delay appears to be improved as of the CM build I flashed last night. Check the CM kernel to confirm whether the screen on delay has been reduced.

Feel free to flash this one to test. It has the wake features added.

I want to know

1. How well it works for you.

2. If the screen on delay is impacted negatively by this.

tinykernel-m7-cm11-2.2-test.zip - 5.73 MB
[One (M7) Original Android Development] h4waii:
I have no issues with screen wake delay using this release. DT2W works perfectly so.

Thanks for providing this test build.
[One (M7) Original Android Development] donatinho:
I also tried the test kernel, with CM 11, build 4th august. and worked perfectly, in two days never had an issue unlocking it with double tap.
[One (M7) Original Android Development] dseries60:
Running your test kernel and s2w+s2s works perfectly with no negative effects. Running 8-6-2014 nightly. Thanks very much for including screen wake options in your kernel!
[One (M7) Original Android Development] Artc0re:
Thank you for the wake option finally a kernel for aosp which has this option and there are no delay on my device.
[One (M7) Original Android Development] badams1:
Does DT2W have a negative impact on battery life? Because I like it...a lot.
[One (M7) Original Android Development] tiny4579:
Some would say yes, others no.

I don't see how it can't impact battery based on the way it works. The question is how much. I don't think its a lot if you do. I've never done a proper comparison for dt2w on vs off but there's probably less than a 1% an hour difference.

I hesitated to include this at all before because there was an inherent screen on delay with pocket detection. Pocket detection is kind of needed to prevent accidental wakes.
[One (M7) Original Android Development] badams1:
Thanks for the info. I'm gonna run with it a bit and see how it goes. Its handy as hell to reach over and double tap the screen while at work as opposed to going for the power button.

Thanks for the awesome work.
[One (M7) Original Android Development] donatinho:
I have 2 HTC One, same rom, same kernel, with and without d2tw. The difference, if any, is so negligible you would need some kind of highly accurate benchmark to determine which one is better.
[One (M7) Original Android Development] ironman76:
Great Kernel :)

Ps.: Logo2Menu doesn't work, will you activate it?

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] tiny4579:
Read back a bit. I showed how to activate it. It was the best way I could think of making it work making it optional and off by default and without using aroma.
[One (M7) Original Android Development] SBColasito:
I'm having a problem with my battery after I flashed this kernel. I have CM11S as my current ROM and there was no problem with the battery after a few days of monitoring. Then, I decided to flash this kernel. I problem basically is the battery percentage isn't accurate. The notification led turns green when the battery is full, right? So, I rebooted my phone and the notification led turns red again and the battery percentage drops down by 10-15 and it starts charging again. Is there anyway that this problem can be solved?
[One (M7) Original Android Development] tiny4579:
Not a kernel issue. Also if you have a ported cm11s, I can't support it. Who knows what kernel they are using or sort of hacking if it was swapping libs.
[One (M7) Original Android Development] jukiewalsh:
My phones done this before even on official sense Roms. I think my battery just might be going bad or something. Try full rebooting 3 or 4 times off the charger and then charge it until it's full and use it.
[One (M7) Original Android Development] Keasby:
Tested your 2.2 kernel with the latest Slim build, work very smooth without any problem!

Thx for your great work!
[One (M7) Original Android Development] twped:
What's the change log for the 2.2 kernel?
[One (M7) Original Android Development] tiny4579:
No change log will be posted until I make a build final. So guys you think leaving the proximity code sounds fine? I don't want to increase wake delay if I can help it.
[One (M7) Original Android Development] CRACING:
Hello tiny4579,

First I would like to thank you for making a nice kernel that is (for) CM11 and supports Sprint HTC ONE.

I'm using your test kernel v2.2 as well as used v2.1 before. I have Sprint HTC ONE which is unlocked and using GSM network. ROM is CM11 M9.

Everything is working fine except when the device wakes up, the screen flickers. I mean screen brightness goes high (100%) and then sets back to auto or manual selected brightness. This happens in less then seconds which looks like flicker. If I manual set screen brightness to 100%, then there is no flicker because brightness is high always.

I see you are working on screen wake up and thought to let you know this issue as well. Sorry, if its already a known issue. I have tried v2.1 and v2.2 test and both have same problem. However, it wasn't present in official CM11 M9 kernel.

Keep up the good work. Thanks...

Best Regards
[One (M7) Original Android Development] tiny4579:
Flicker is an issue on cm11 kernel. Or was. How long did you test? It doesn't affect everyone. Please let me know what screen type you have. I'm aware of this issue. I'll have to see if any kernel changes fixed it but none to my knowledge. Also you may not notice it all the time or do you?
[One (M7) Original Android Development] dseries60:
[MENTION=234019]tiny[/MENTION] Thanks for your kernel work. I have a question.. I am using your 2.2 test kernel that has screen wake features. Is there a file I can modify to increase the vibration when turning the screen on via s2w? Thanks!
[One (M7) Original Android Development] CRACING:
Thanks for responding. Yeah I'm new to HTC ONE as I bought it recently. It was having viperone preinstalled by first owner. Yesterday I have flashed official CM11 M9 and didn't noticed such flickering issue when I turned on the device but I"m not 100% sure because later I have flashed your Tiny Kernel, Just because I wanted dt2w or s2w.

Now have to restore Nand backup to confirm again whether official CM11 kernel also has such issue. Or do you know where I can find official CM11 kernel only? so it would be little easy for me.

My HTC ONE has "mipi_m7_lcd_probe: panel type: PANEL_ID_M7_SHARP_RENESAS_C1" LCD.

Issue is present all the time I wake up the device. Screen goes 100% brightness and dims back to default brightness setting. This happens within seconds, so it looks like one flicker.

Thanks again...

Best Regards
[One (M7) Original Android Development] tiny4579:
Yeah, users with the issue so far have that panel. Just flash cm11m9 again to get stock cm kernel.
[One (M7) Original Android Development] CRACING:
Damn, HTC does this on most of their devices. Putting different brand LCD panels and it makes difficult for developers to diagnose. :(

Is there any solution to it?

Ok, thanks for the tip. I will flash the ROM again without wiping and check the issue again. Will let you know also.
[One (M7) Original Android Development] joelnohnn:
Execute the script with root

Perhaps you should mention that the script must execute with root access,
[One (M7) Original Android Development] CRACING:
[MENTION=3500210]tiny4579[/MENTION] You were right about flicker issue present in official CM11 also. My bad I didn't checked correctly, sorry about that! May be the brightness was high so I didn't notice.

Anyhow, I'm back to your kernel again and enjoying its features. :)

Thanks...

Best Regards
[One (M7) Original Android Development] tiny4579:
2.2 is up. There will be a plus version of 2.2 later once I can add scripts to enable them (or you can take the Trickster MOD route to enable the features if you don't want to wait as long). The Plus version still won't be until tomorrow.
[One (M7) Original Android Development] 4Strings:
Three quick questions before I flash...: :p

Firstly, does the kernel support dt2w (double-tap to wake)? This is the main reason why want to flash a custom kernel in the first place.

Second, how do I make changes to kernel settings?

And finally, if I update my ROM (I'm running nightlies), will I have to reflash the kernel as well?

Oh, I'm running the August 14th CM11 Nightly right now on my AT&T M7... :)

Cheers!
[One (M7) Original Android Development] dseries60:
1.) Yes

2.) Trickster Mod (Play Store)

3.) If you update your rom, you'll need to reflash the kernel
[One (M7) Original Android Development] 4Strings:
Sweet! Thanks! [emoji1]
[One (M7) Original Android Development] 4Strings:
Flashed!

But I can't figure out how to use Trickster MOD to enable dt2w...

Any help?
[One (M7) Original Android Development] CRACING:
Same here, I couldn't find the options either. Then I tried Kernel Tweaker (Free) and found the kernel settings. Side bar -> Kernel Params ->Kernel. Make sure you also tick the round checkboxs so the option is set on boot.

Edit: This is for 2.2 test version only.
[One (M7) Original Android Development] 4Strings:
Thanks!

But where do I enable dt2w (double-tap to wake)?
[One (M7) Original Android Development] CRACING:
Sorry, actually I was on test version 2.2 and it had s2w and dt2w. After flashing v2.2, these two features are gone. Looks like the developer has removed or not implemented in this version.
[One (M7) Original Android Development] 4Strings:
I see. Where can I get the test version? :)
[One (M7) Original Android Development] CRACING:
Page number 9, post #85. Here
[One (M7) Original Android Development] 4Strings:
Thanks!

Flashing now...

---------- Post added at 01:12 AM ---------- Previous post was at 01:00 AM ----------

it works!

Thanks man! :d:d:d
[One (M7) Original Android Development] CRACING:
You're welcome but credit goes to the developer. :)

Actually dt2w isn't prefect yet because the screen wakes up on non finger touches also. i.e while in pocket. In viperone, it was having a feature called pocket detection to prevent accidental wakes. Wish it was present for cm11 as well. I'm also little disappointed about the same issue on different cases. i.e when the phone gets a incoming call while its in pocket, touch screen is operated and random options are pressed. Touch screen is made of capacitive and not resistive so why should it work with cloth touches? My old Sensation didn't had such issue. May be its feature made to work when operated with gloves? and cm11 hasn't got option to disable it. :rolleyes:
[One (M7) Original Android Development] tiny4579:
Pocket detection should be on in the test kernel? What does trickster mod show for it?
[One (M7) Original Android Development] CRACING:
I couldn't find any kernel settings such as s2w, dt2w and fast charge in trickster mod and I don't have paid version.

In kernel Tweaker, I get options to enable/disable s2w, fast charge and dt2w on test kernel. However, no pocket detection option.
[One (M7) Original Android Development] tiny4579:
Oh I have the paid version. The paid version may have those features while the free version does not. I'm at work but maybe someone with the paid version could confirm it.
[One (M7) Original Android Development] Alef_0:
I tried the test version on last cyanogenmod nightly and sometimes I had blackscreen wake-up issue. Is it a proximity sensor problem? How can I salve it? TNX
[One (M7) Original Android Development] tiny4579:
Could be. Have you any logs? I can't just blindly figure or what's going on in the background without logs. The wakeup is weird on this device anyway and the proximity sensor detection may compound things.

May be best not to include it. Wake delay hasn't been fixed on the kernel this one is based off (official cm).
[One (M7) Original Android Development] CRACING:
Isn't it the kernel feature?

If kernel options are shown on trickster mod (paid anyhow) then Kernel Tweaker app should also show it. May be the developer of kernel Tweaker app isn't aware about Pocket detection feature or doesn't know the path of it. :rolleyes:
[One (M7) Original Android Development] tiny4579:
I don't know the node name but most of the touch driver hacks are in /sys/android_touch including I believe pocket mode. I don't have the device nor the source in front of me.
[One (M7) Original Android Development] CRACING:
Ok thanks.

pocket_detect is present in /sys/android_touch and is enabled by default. However, the touch screen still operates on non finger touches.

May be it uses proximity sensor and if its 0 value then touch screen doesn't operate.

Gotta study more about it as I'm still new to HTC ONE.

p.s please implement s2w and dt2w on your next kernel releases. Atleast disabled by default and if anybody likes to have then he/she can enable. :)
[One (M7) Original Android Development] tiny4579:
You might have missed the part where pocket detection can cause lag. The code there itself might. I'll have to do more testing before bringing it into the mainline kernel. If disabling pocket detection in sys improves wakeup lag, I'm all for one kernel.

To test if pocket detection works, cover the sensor (upper left of the phone) and try to wake the phone with s2w or another 2w feature. It shouldn't wake up.
[One (M7) Original Android Development] 4Strings:
I haven't had any problems with it turning on in my pocket yet... In fact, sometimes dt2w doesn't even work when the phone's on a table...

I'm using AcDisplay for lockscreen notifications (with lockscreen mode enabled), so that might be why dt2w doesn't activate in my pocket...
[One (M7) Original Android Development] tiny4579:
It shouldn't activate in your pocket. That's the whole point of pocket detection. Do you think pocket detection is broken?
[One (M7) Original Android Development] 4Strings:
That's not what I'm saying... I'm saying that it doesn't activate in my pocket, so pocket detection is working fine. :)

I didn't specifically enable anything, so that means that it's on be default, right?