yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] shawnchalfant:
Small issue with 4.3 Sence 2.2.5

Once I place a call, then raise the phone to my ear then pull away screen stays off unless I move the sensors toward a bright light or even flick my wrist. Proximity sensor seems to be not registering. Any help thanks.
[One (M7) Original Android Development] Byrana:
I actually think this is a good feature.do not get rid of the bug, or make it as an option, because that would mean, I can finally make calls without the screen turning on. That is the worst,with the HTC one.
[One (M7) Original Android Development] shawnchalfant:
It's a pain when I need to use the dial pad to navigate the many menus in the process of automated phone systems or switch on speaker phone.
[One (M7) Original Android Development] guyd:
The proximity sensor has always been a bit buggy for me. I wonder if HTC fixed it in the 4.3 Kernel source (probably not out yet).
[One (M7) Original Android Development] Byrana:
I just checked with venom and 4.2 kernel.Everything works as it should be. Screen is turning on, if I move phone away from my head.
[One (M7) Original Android Development] stegg:
any help?

I can't get the kernel flashed,the aroma installer suddenly reboots the phone.

I just select "bouble tap to wake", no other options, and when i tap "next" in the last screen, the device reboots.

I have 1.44 boot, s-on, ahrd 22 mounted and working... any idea?

the md5 are correct
[One (M7) Original Android Development] tbalden:
I have no issue with the proximity sensor and never had on any android revisions sense or gpe. But I'm on older firmware, not the new one coming with 3.22.

But previously same thing was reported by some users, I chalked it up as a hw calibration issue which seems to be happening on all kind of kernels and roms, sense, gpe and aosp. Also I think HTC is trying to fix this issue for a while, not sure if they did it successfully in this official 4.3 sense update. Let's hope the kernel source will help, might come in a few months ( usually they release after a few months following the rollout)

Is it working ok on stock kernel? Also have you flashed firmware update?
[One (M7) Original Android Development] tbalden:
Happens for some very rare occasions on some phones. Try from fastboot,

fastboot erase cache

Or try another recovery too as a last resort, or reflash recovery.

Sorry, I know it can be frustrating, but there's no better advice I can tell.
[One (M7) Original Android Development] tbalden:
Yeah, there's always a varying degree of sensitivity coming with these sensors that can lead to issues on some of the phones while others work fine
[One (M7) Original Android Development] nbicho:
I've reported that same issue before, but since I was the only one, I thought it was just with me, so decided to go stock and wait for 4.3 source release to see if it gets better.

With stock it works flawlessly and yes I have updated firmware to 3.22

Enviado do meu HTC One
[One (M7) Original Android Development] tbalden:
Thanks for the heads up. Hopefully we get the calibrated board files soon from HTC when they push it out to htcdev.com.
[One (M7) Original Android Development] tbalden:
hmm, ok, thanks for the report. maybe related to load? are you using some heavier apps while this happens?
[One (M7) Original Android Development] tbalden:
thank you! :)

biggest credits to [MENTION=456600]Flemmard[/MENTION] again, he's the best kernel hacker i know around xda. :)
[One (M7) Original Android Development] :
No just restarted the device before i connected.... My musicplayer is the PowerAmp.... I res it with the stock Player later and Report back

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] tbalden:
im not S-Off yet, and not yet at home. I'd recommend to flash back the touch firmware till this get sorted out (also it's not sure if it can be sorted out, no-one looked at this yet afaik)
[One (M7) Original Android Development] ceelo2008:
Ok thanks. I appreciate all your hard work!
[One (M7) Original Android Development] mettleh3d:
Touch unresponsive.

2.14 firmware

Arhd 10.3
[One (M7) Original Android Development] Muxeu:
I have the latest firmware & TeaMSeven kernel 1.1.2.

My touchscreen works fine
[One (M7) Original Android Development] tbalden:
to clean up confusion regarding Firmwares, what doesnt work is when you upgrade the Touchscreen firmware on an S-Off device.

Otherwise latest custom roms works with non 2.17 touchscreen firmware.

Also please dont report it multiple times, as it's stated in Known issues

thanks
[One (M7) Original Android Development] LorD ClockaN:
LOLOL

Deleted the post because tbalden just answered in the same time :D
[One (M7) Original Android Development] baste07:
How can I check what touch screen fw I have?
[One (M7) Original Android Development] jonata:
+1

:)
[One (M7) Original Android Development] mettleh3d:
If you don't know, then you ARE compatible with this kernel.
[One (M7) Original Android Development] baste07:
A simple "I don't know" is okay
[One (M7) Original Android Development] tbalden:
"if you haven't flash any firmware, fastboot getvar mainver should show your last stock which is same as your firmware."
[One (M7) Original Android Development] baste07:
Thanks!
[One (M7) Original Android Development] Muxeu:
[MENTION=3088420]tbalden[/MENTION]: have one issue. My PC can't see phone by ADB after flashing your kernel. Any solution?
[One (M7) Original Android Development] :
so tried it with the stock player and bluetooth, got the same issues :)
[One (M7) Original Android Development] pigmich:
One more problem I found after I flashed this kernel, that is when I go to phone app and the dialer page, there has a white line between the contact avast and the dialer. I am using ARHD 10.3.
[One (M7) Original Android Development] tbalden:
hmm, no issues here with linux, but i'll have to check this with Windows.
[One (M7) Original Android Development] tbalden:
thanks for reporting! Havent noticed till now, i have this happening on stock 2.17 as well
[One (M7) Original Android Development] stegg:
thank you, i did all of those (fastboot erase, reflash recovery) but nothing changed.

anyway it should be a AHRD22 problem, because i restored the backup of 13.3 and everything works, ie I just flashed your teaMSeven-sense-4.2.2-kernel-v2.2.5 :)

BTW is there a way to disable the vibration after doubletap2wake?
[One (M7) Original Android Development] hoereth:
Seems sweep2wake+*short*tap logo2sleep is not working.

When selecting this option we actually get double tap 2 wake...
[One (M7) Original Android Development] tbalden:
I think ARHD22 shouldn't mean a problem, but it's something related to flashing stuff in a certain manner, the recoveries seems to have some troubles, because there's a couple of users with ARHD22 who were able to flash the kernel. I have tested ARHD22 too earlier.

As for disabling the vibration, you can if you use a script, or set in a root explorer this path to 0:

/sys/android_touch/sleep_wake_vibration_time

like this:

echo "0" > /sys/android_touch/sleep_wake_vibration_time
[One (M7) Original Android Development] tbalden:
will try, thanks for testing, reporting.
[One (M7) Original Android Development] ijob:
Hi there,

Anyone experienced a messed up lock screen when someone calls? I use widgetlocker and with custom kernels it messes up the lockscreen. I also use nova launcher. Would live to use this but if anyone can advise?

Cheers

-----------------------------

Sent from the back of Michael Caine's Mini Cooper S, holding on for dear life....
[One (M7) Original Android Development] tbalden:
which rom are you using? A sense 4.3?

haven't got widgetlocker yet, but lock screen is fine with the standard sense one.

In what way is it messed up? Glitched graphics or what exactly?

thanks for testing and reporting
[One (M7) Original Android Development] ijob:
Latest ARHD, sense 4.3. I have attached two pics, the first with standard kernel and number 2 this kernel. I have tried this kernel in it's various stages of development and all have had this in my phone once installed. S-on but unlocked.

-----------------------------

Sent from the back of Michael Caine's Mini Cooper S, holding on for dear life....
[One (M7) Original Android Development] tbalden:
Might happen, when i get some more time for this. Flick2Wake development is over, so that might be a next major thing to do, but i can't tell you yet when.
[One (M7) Original Android Development] tbalden:
Indeed. I've updated the installers, and uploaded a 2.2.5c1 for you to test:

http://www.whiskey103.nl/OneM7_Kernels/index.php?dir=tbalden/2.2.5c1/

Nothing else changed except the issue you reported should be fixed with the installer.
[One (M7) Original Android Development] tbalden:
Thanks! Looks like there's some changes in the 4.3 gralloc/overlay part, that the GooglePlayEdition 4.3 sources don't cover. Another gap which causes issues that might be around till we get the full HTC sources (my guess is that drivers/video/msm would need some non-trivial fixing)

Maybe try enable disable Force GPU rendering/HW overlay in Development Settings.
[One (M7) Original Android Development] LiquidSolstice:
This has nothing to do with this kernel or your ROM. This is an irritating feature of HTC Sense. If your contact picture images are not of a high enough resolution, it will produce this "dot matrix" style overlay over them to give your brain the illusion that the images are sharper and of higher resolution than they actually are.

Set the contact image manually through the contacts app, and use a decent-res image. You'll see that problem will go away. There seems to be no way to disable this see one post below me to get rid of it!, as it has been happening since the very first Sense 5 ROM.
[One (M7) Original Android Development] stegg:
yes it can be removed! :)

http://xdaforums.com/showthread.php?t=2349329
[One (M7) Original Android Development] LiquidSolstice:
Glad hear that. Edited my post accordingly :)
[One (M7) Original Android Development] Gerton:
Flashed 2.2.5 stable over ARHD 22.

I UV -75 whole range and after playing a game for approx 15 min. Phone hangs and rebooted.

Now set the UV to -50 Hopefully this would help.

Further it's running great!
[One (M7) Original Android Development] FitAmp:
Is the perf edition up to date with Franco's hotplug?
[One (M7) Original Android Development] tbalden:
Yes, that's the way to go, raise a bit if it hangs, but also you can

try lowering the voltage in the lower frequency range, and avoid lowering all across the board. So first a -50mv all over the range, then only the lower parts and see if it's stable, comes off of standby fine, etc... I'm using the lowest freq (81mhz), with ~700mV.
[One (M7) Original Android Development] tbalden:
No, it's not, and most probably won't leave the Milestone now.

n3o and maxwen added Cpuquite to the AOSP teaMSeven kernel and works very nicely, i'll see if we can get the same for sense. Don't know when i'll get some time, but that's next thing planned.
[One (M7) Original Android Development] FitAmp:
Good stuff :) thanks !
[One (M7) Original Android Development] inaudible101:
I had to disable pocket detection completely to fix this and it still seemed to only react to light and not actual proximity. I also have a problem where I can't send mms on the last few builds. I'm on att and it works fine on coinless until I install this kernel and then it just sits on sending until it fails.

I've loved the kernel so far but until these two issues are fi

I'll sadly have to stick with the stock kernel. Keep up the good work and I hope to be able to use these again in the near future.
[One (M7) Original Android Development] tbalden:
i'll have a look at the MMS thing, thanks for reporting.
[One (M7) Original Android Development] Gerton:
I also disabled pocket detection and it's not working like it should. The screen doesn't go on in a call, only when it's seeing bright light.

I needed the incall options so I had to return to stock. With the stock kernel it works.

ARHD 22
[One (M7) Original Android Development] tbalden:
The pocket wake detection is not being used in calls, so it's useless to enable/disable that.

But it still happens on some of the devices with a more sensitive sensors, even if others (like me), can't reproduce it. So thanks for reporting it. I'll have a look at this, whether something went derp when merging 4.2.2 and gpe 4.3 sources
[One (M7) Original Android Development] Gerton:
I didn't use the pocket detection at all so it was easy to say that I disabled it.

I also tried a xposed mod called proximityfix.apk but this didn't help also.

I thought It was a fix for some same problem in the beginning of 4.2.2
[One (M7) Original Android Development] tbalden:
ok, thanks, maybe I'll have something to test tonight (in about 6-8 hours), as i've skimmed through some changes, and maybe reverting them could help. I can check this when i got home later. stay tuned :)
[One (M7) Original Android Development] teorouge:
Hello, quick question out of curiosity: I've seen big GPU frequencies OC in another custom kernel (>580MHz, if I recall correctly), is that something you tried already and decided not to implement?
[One (M7) Original Android Development] astmacca:
As regards the screen staying blank during calls when the phone is away from you ear. Yup, i have that issue as well.

ARHD 22.0 / team 7 2.2.5 Pocket Protection option is off.

Need to play a bit more to find out all the instances where it happens, but during use indoors and out today it was most often, but not always.
[One (M7) Original Android Development] shawnchalfant:
It works ok with the stock kernel, I'm on the lastest firmware also. Your kernel runs like ice, just having the sensor issue is all.
[One (M7) Original Android Development] astmacca:
Does anyone have a link to the stock kernel for a Sense based 4.3 ROM? Flashable zip would be great. :)
[One (M7) Original Android Development] nbicho:
Just flash your rom without wiping anything

Enviado do meu HTC One
[One (M7) Original Android Development] tbalden:
ok, found the problem with the Proximity sensor and phone calls...rooting it out soon.

Thanks for all who reported!
[One (M7) Original Android Development] Denpech:
This updating?

Directory Listing of /OneM7_Kernels/tbalden/2.2.5c1/ ???
[One (M7) Original Android Development] jason27131:
This kernel crashes Modern combat 4 lol. Can't even load the game.
[One (M7) Original Android Development] tbalden:
No. It will be 2.2.6 with the in-call proximity fix.
[One (M7) Original Android Development] tbalden:
Thanks for the report.

It would be very useful, if you told which rom are you using, which android revision etc...or even provide a logcat. Please do give some details
[One (M7) Original Android Development] jason27131:
Oops my bad lol.

I'm on 4.3, kernel version 2.2.5. Running AHRD 22.0. The stock kernel worked perfectly fine. After i flashed this kernel, it crashes everytime during the menu load.
[One (M7) Original Android Development] tbalden:
Thanks, gotta check this
[One (M7) Original Android Development] tbalden:
teaMSeven Sense/GPe 2.2.6

- Changes:

Version 2.2.6 - Sep-30-2013

- Fixing Proximity sensor issues while in call, sreen should wake now. when moving phone from face

- Fixed sweep2wake + short tap logo sleep mapping in installer script

Sense 4.3 - v2.2.6

teaMSeven-sense-4.3-kernel-v2.2.6.zip - http://d-h.st/4Ot

teaMSeven-sense-4.3-kernel-v2.2.6-performance.zip - http://d-h.st/dHn

GPe4.3 - v2.2.6

teaMSeven-gpe3-4.3-kernel-v2.2.6.zip - http://d-h.st/g2X

teaMSeven-gpe3-4.3-kernel-v2.2.6-performance.zip - http://d-h.st/C9z

Sense 4.2.2 - v2.2.6

teaMSeven-sense-4.2.2-kernel-v2.2.6.zip - http://d-h.st/ugi

teaMSeven-sense-4.2.2-kernel-v2.2.6-performance.zip - http://d-h.st/tMu

Mirror: http://www.whiskey103.nl/OneM7_Kernels/index.php?dir=tbalden/2.2.6/

Enjoy!
[One (M7) Original Android Development] Gerton:
Testing in 10...

Edit: Working!
[One (M7) Original Android Development] tbalden:
Thanks for the quick testing and feedback! :)

I've tested MMS issue too (and looked the kernel sources that were merged, couldn't spot yet a fix for it), and tried the other alternative 4.3 kernels released here on xda for htc one, but so far i've found that none of the available custom kernels are working with MMS. (Tho I never tried it on stock, as i never use MMS). For now I've added it to the Sense 4.3 issues list.

Also gonna test the ModernCombat4, but it downloads a crapload of data, so i can't yet start it :)
[One (M7) Original Android Development] bia9977:
Same problem. InsertCoin 4.3/5. Latest versions of all software, your kernel included.
[One (M7) Original Android Development] chong67:
I have s-off. I have only flash firmware and whatever radio comes with it and I use ARHD 22.0

I have no idea if my kernel is every touched or modified. Do I need to flash kernel like this one here?

Sorry for newbie question.
[One (M7) Original Android Development] nbicho:
No, you don't have too. Flash it only if you like to have some more options to play with :)
[One (M7) Original Android Development] lampshade90:
you shouldnt flash anything, if you dont know what youre doing!
[One (M7) Original Android Development] babuja:
I'm always flashing files and introducing weird commands I don't know nothing about :) in the process I'm learning...only side effect is one of this days I'LL probably brick it :)
[One (M7) Original Android Development] jason27131:
Thanks for the MC4 test! I've tried MMS using 2.2.5 kernel, and it does seem to work fine on my end. Though I'm on Rogers (canada), so maybe it's a specific issue with the kernel + provider?
[One (M7) Original Android Development] tbalden:
Hmm I know very little about mms..rarely use it.gonna check my apn settings
[One (M7) Original Android Development] racka:
First of all, thanks tbalden for this great kernel.

It has some really nice features. What I find most exciting is the option to set logo2menu and then swap it with the home button. Of course the flick to wake is awesome as well!

I have an issue though. Im on ARHD 22.0 and whatever I try, I can't get the logo2menu working in the first place.

I tried various mappings with logo2menu but without succes.

Do you guys have any idea what could be the reason, or what I can try?

Btw. long press home does activate the menu.

Thanks in advance.

Verstuurd vanaf mijn HTC One met Tapatalk 4
[One (M7) Original Android Development] tbalden:
Make sure you tap the upper part of the logo near the edge of the screen, the logo itself is not touch sensitive. So just above it around the top of the htc letters. Hope this helps
[One (M7) Original Android Development] racka:
Thanks for the quick reply. I'm sure I touched the right spot at least once :P.

After I've read your reply, just to be sure I flashed the kernel again. Only this time with logo2sleep and that's working fine.

So I've flashed again with logo2menu and again it doesn't work for me.

Could it be some kind of conflict with the home button menu? I tried to find a setting in the phone settings and ARHD toolbox to turn it off but I can't seem to find it....

Verstuurd vanaf mijn HTC One met Tapatalk 4
[One (M7) Original Android Development] chong67:
I see.

I like my phone to hang onto the LTE signal as long as it can, even if the signal is weak. I like my phone data connection NOT to get hang while it switches between those 3G, 4G or LTE signal.

I guess I should be more concern about the radio then kernel?

I am happy with my phone performance right now and I have update the firmware and use my favorite cook ROM.

It is the kernel thing that I have not mess with it.

From what I said above, done mess with or update to any kernel?
[One (M7) Original Android Development] Gerton:
I would advice: if your happy stay this way.
[One (M7) Original Android Development] gregneal:
in both 2.2.5 and 2.2.6, when selecting logo2wake and logo2sleep with short tap and the rest of the options default, the options for "buttons" in settings > "display, gestures and buttons" is gone.

In that buttons subheading there is normally two options: change the home button action and double tap speed.

also 2.2.6 installer has stopped on 0% twice after clicking install. see http://i.imgur.com/tOdbJBW.png I'm on stock everything else after running the 4.3 RUU.

thanks for the frequent updates and i hope you can get these issues resolved too :)
[One (M7) Original Android Development] eyosen:
Stopping at 0% is a known aroma installer issue. Restarting install as you did makes it work
[One (M7) Original Android Development] tbalden:
Have you selected to "remove the 3 dot menu"?

I thought that only that will give you this missing option thing.

So you haven't selected that? I'll check something related to this.
[One (M7) Original Android Development] hapticc:
flick2wake not working for me :(
[One (M7) Original Android Development] tbalden:
It should if you don't have any extra apps that interferes with this,. Are you sure you flick it with a snappy movement, a bit like a whip.

Have you tried the more sensitive setting ?

Which Rom are you on?

Please provide a dmesg,while you try this grab it:

adb shell dmesg > Log

And paste it to pastebin.com and link here.

Thanks
[One (M7) Original Android Development] hapticc:
I am on Insercoin 4.0.3 and sure thing i will update you with log after some time. And yeah i chose the super sensitive too but it wont work
[One (M7) Original Android Development] horstmanuel:
With 2.2.6.I am getting a huge suspend wakelock. I didn't change any settings. Lost 15 over night. Reverted back to 2.2.5.and everything is fine now. Any ideas?
[One (M7) Original Android Development] Gerton:
May I ask wich wakelock? I am also using 2.2.6 and want to look if I also experience this. I didn't noticed any wakelock but I am curious..
[One (M7) Original Android Development] miten_sheth:
+1

Haven't reverted back.. And also my phone has been getting hotter more than usual.. Dunno why.. :what:
[One (M7) Original Android Development] horstmanuel:
It's the typical chrome tilt wakelock called suspend backup or something like that. Thing is I haven't even installed chrome and I restarted the phone twice. Wakelock was still there.
[One (M7) Original Android Development] tbalden:
In 2.2.6, I have removed the part where the Gyroscope was forced to be switched off anytime the Panel was switched off. In 2.2.6 now it only get switched off as the framework is switching it off, like on stock kernel.

I have checked on 2.2.5, that when the In-call screen off happens with the Proximity sensor based detection, the Gyroscope was disabled together with the Panel off, that's why the phone screen wouldn't come back in-call, when moving phone away from face.

So in 2.2.6 I have reverted that part to the original working, and framework is handling the part where the Gyroscope is being disabled, and maybe the android framework is switching it off vaguely, not always when you switch the screen off, maybe because of some apps (maybe not just chrome, but other apps use it too).

I'll have a look at this again, but I think it's the way it's working on stock, and the suspend back-off is happening as it would normally happen when gyroscope is on like for Auto Orientation.

I'll check if there's a way to separate the case when proximity sensor is used for in-call, and then force the Gyroscope off when screen is being turned off while not in-call, but I'm not sure what else this could impact yet.
[One (M7) Original Android Development] gregneal:
definitely did not select remove 3 dot menu. and even if I did, that shouldn't have caused the settings to disappear.

thanks!
[One (M7) Original Android Development] tbalden:
what do you mean? There are some things, that is not decided by the kernel and can be a side-effect that cannot be worked around, if certain system properties are changed. It's like, it works like that, and a kernel mod won't change a thing that is inside the framework part of the HTC Rom.

Anyway, I'll check if the keylayout file injected can have such an effect on this settings, and whether it can be mended. Thanks for reporting.