yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] zooster:
Since I flashed Vipers 3.1.0 I got touchscreen problems. It's not accurate in the lower part of the screen, sometimes it detects over touches. But cause these issues at the lower part of the screen I cannot easily unlock the ring and often scroll too. Unfortunately it's the most annoying bug together with incall audio level/quality.
[HTC Sensation] Ballesss:
Where is the download link?
[HTC Sensation] topjohnwu:
This is a developer thread, it only have source code.
[HTC Sensation] zcdg:
This is quite good kernel. Thanks for hard work! But it is very far from perfection. Sound quality and loudness, camera problems and random reboots... I know it is very difficult to fix this all because related to real hardware of Sensation.

But question is - will we ever have any JB sense or no sense kernel with the level of quality/stability we have with current ICS roms? What are our chances without real drivers for our Sensation ?
[HTC Sensation] bitaktus:
[MENTION=2212152]SebastianFM[/MENTION] Thanks again for the hard work.

If I were to have 2 wishes for your kernel, I'd probably be:

- SIXAXIS-support

- fastcharge

Keep up the good work. Sensation-users love you!
[HTC Sensation] GROGG88:
Most likely, no.

It's not just the kernel you need to worry about either. ICS works well because it was officially released for our device. Even AOSP or CM ICS roms are still somewhat buggy in comparison to official sense based roms. Porting a rom from another device (although this runs pretty well) normally results in sacrificing some important working features for newer less important features.

My prediction is that if/when this ever makes it to 100% then you'll find 99% of sensation users have moved on to other devices already.

I often laugh because most users will sacrifice stability in order to have a higher version number of android or sense. Although the xda started as a developer's forum, it has definitely transformed into a user's forum.
[HTC Sensation] Hobox10:
What I don't get is why really old phones like the Galaxy S1 have perfectly working 4.2.2 JB roms? And will probably get perfectly working Android 4.3 and eventually 5.0 roms? In fact I've noticed it's pretty much just Samsung devices that have this going for them. Is there something inherently different about HTC that makes this impossible?
[HTC Sensation] padvou:
I do not usually respond to other people's opinions, but I seem to miss your point here.

As per the "newer less important features" this is hardly the case here, IMHO.

The users may move to wherever they choose to move, but the breakthrough of this kernel and its dev is and will be a given fact that will remain.

I agree with you on the last paragraph, however, what do you mean "turned from dev forum to users' forum"? And if it were so, so what? Do devs develop for themselves only? Users play a very important part that should not be overlooked by anyone.

Anyway, what does all this have to do with this kernel and the discussion about it?
[HTC Sensation] zcdg:
I asked my question about JB here because looks like this developer, SebastianFM, one of the best, with best knowledge of all around. This is the best JB kernel for present time - still not perfect(i can't use it as daily driver, but some people can). Just ask how developer feels about future. But i think i know answer now.
[HTC Sensation] szotaa:
Thats because SGS have completly the same hardware as galaxynexus s. But they wont propably get updates to newer android because nexus s was abandoned by google.

Wysłane z mojego HTC Sensation za pomocą Tapatalk 4
[HTC Sensation] pc boy:
Is there any download link for the flashable kernel itself?!
[HTC Sensation] rzr86:
nope

this thread is only for devs

nothing yet for flashing
[HTC Sensation] m.m.m:
and another question: does it support wall usb adapter fast charge too? thanks.
[HTC Sensation] Beast Power:
Fast charge not active on this kernel yet, but would hope it will be sorted out soon !
[HTC Sensation] Bastaerd:
There is a github posted so go fork it and make a pull request :)
[HTC Sensation] Beast Power:
I thought this is a thread on XDA, and how do you make a pull request ?
[HTC Sensation] commencal661:
Pull request is made so that you need to do your additions or fixes in source code and then you send a pull request to the developer from which you forked the repository. If the developer is happy with the changes, he will merge those changes in his own source. But since you are asking how to do that, I guess you never used GitHub and/or did a lot of programming. No offense.
[HTC Sensation] Emmanuel U:
I noticed in your source,

https://github.com/SebastianFM/Seba.../arch/arm/mach-msm/board-pyramid-audio.c#L396

msm_set_voc_freq(8000, 8000);

for the for the top in-call speaker, shouldn't that be

msm_set_voc_freq(48000, 48000);

Edit: nevermind
[HTC Sensation] johnnyslt:
[MENTION=2212152]SebastianFM[/MENTION], by any change can you explain in more detail how you managed to make the camera & panel board files? I'm trying to port this kernel to the HTC EVO 3D and I'm stuck at these files...
[HTC Sensation] SebastianFM:
For Sensation camera sensor s5k3h1gx driver I used as a base driver from Ville C2 kernel 3.4.10 for similiar sensor s5k3h2yx. I compared old drivers for both sensors from kernels 3.0.16 to find the differences.

LCD panel driver is based partially on driver from Ville C2 kernel 3.4.10, Sensation kernel 3.0.16 and One S kernel. What do you want to know about it?
[HTC Sensation] m.m.m:
I am not a developer, but can you make the kernel more compatible with "kernel tuner" and such apps?

thanks.
[HTC Sensation] Burth67:
Vibration feedback

Vibration feedback is not working with update. :confused:
[HTC Sensation] SebastianFM:
Kernel is compatible with those apps, but ROMs aren't.

In all ROMs based on HTC JB Sense there is new tool, system daemon called PnPMgr. It controls CPU and GPU frequency and has defined several rules and policies for various cases, e. g. limit maximum CPU frequency when navigation is running, also when power saver is enabled or when screen is off, enable both cores and increase CPU frequency when app is launching, enable both cores and increase minimum and maximum CPU and GPU frequency when benchmarks are running. It adjusts values at run-time and it may override your settings.
[HTC Sensation] yazzabo:
Thanks so much!!!

Swap is really ncessary for heavy task or game (expecially if they are modded!!) And stats are really usefuo to make tests!!

htc Sensation XE - ViperS 3.1.0
[HTC Sensation] johnnyham89:
Thanks for the update SebastianFM. Any word if the random reboots due to cpu frequency are fixed?
[HTC Sensation] zooster:
Sebastian, have you looked into touchscreen sensitivity issues?
[HTC Sensation] sjknight413:
No touchscreen sensitivity issues here,

I ran revelation 1.0.0 until viperS 3.1.0 was released, then ran that until today when i switched to revelation 1.0.1 and my touchscreen has been perfect throughout.
[HTC Sensation] hinxnz:
Yes same here but it did happen once, only once though when I turned screen on lock ring was hard to move and same with scrolling homescreens, pulling down notification bar etc. It's like the bug that was in the ICS kernel has come back to haunt some of us :D I think showp was the first to fix this in his kernel. I just turn screen off for a min or two and then it was fine just like I use too in the early stages of ICS, I use to thought it was related to WiFi, probably wasn't though and also related to the silver pin having bad contact but that wasn't the case. It also fixed the issue where people were having trouble with answering calls from lockscreen.

Sent from my HTC Sensation
[HTC Sensation] zooster:
It's not related to silver pin, it's not hardware issue. Many ppl in vipers thread have this problem, if needed I'll make a video to make it clearer.
[HTC Sensation] jsjjcky:
Hello. Which app should I download to control the PnPMgr？
[HTC Sensation] TookeX:
Glad to see new version of kernel

and swap is available in this version

but how about random reboot issue?

i dont find reboot fixed in changelog

is that means someone who experienced reboot should still use userspace governor for workaround?

finally im ViperS 3.1.0 user

could someone update a flashable kernel for this version of kernel

i cant wait to try swap with Sense JB
[HTC Sensation] SebastianFM:
Not yet. What can I say? I'm still trying to find what may cause that it occurs on some devices.

Yes and I didn't find anything.

I may be wrong but I think that this bug was fixed in ICS not by showp, but by HTC when they released updated kernel touchscreen driver.

I used in my kernel touchscreen driver from newest HTC kernel for Sensation and I didn't modify anything in it.

To test my touchscreen I enabled touchscreen driver debugging and I created simple command prompt script to capture kernel log at real-time. Also I tested everything on ICS with stock kernel. Really I don't see any differences. To enable reporting touches to kernel log you may use command adb shell "echo 2 > /sys/android_touch/debug_level"

There is no app to control PnPMgr, it uses configuration file /system/etc/pnp.xml. You can change profile from my installation package.
[HTC Sensation] elvisypi:
I used to have problems answering calls in ICS with sultan's kernel, and now they are gone. The kernel is absolutely perfect. Been using the rom since it was released and not a single freeze or reboot. Focus is much better than in ICS before I had to focus manually 3-4 times for objects near, now it auto focuses very well.

I only wish you could add S2W
[HTC Sensation] SebastianFM:
I would like to see it. Could you also enable touchscreen kernel driver debug and check if touches which aren't recognized by system are reported in log.
[HTC Sensation] hinxnz:
I saw this in logcat, is cpu1 maxing out occasionally and causing reboot on some devices that can't handle this frequency or does this not adjust scaling_max_freqency? I set max frequency to 1674000

[ 07-18 14:32:03.739 955: 959 E/ThermalDaemon ]

notify PnPMgr CPU1 frequency recover to 1836000

Thanks, I will run this command, hopefully I will get a recurrence.
[HTC Sensation] zooster:
Sure... But how to enable this debug?
[HTC Sensation] hinxnz:
Well this is how I do it, I use terminal emulator and enter code below this will record to sd card as long as terminal is open.

Once error occurs you can close terminal and post kmsg.txt found on root of SD card :)

su
echo "2" > /sys/android_touch/debug_level
cat /proc/kmsg > /sdcard/kmsg.txt
[HTC Sensation] PopaStefanx:
Here no touch problem, everything fine [MENTION=2212152]SebastianFM[/MENTION] which model of sensation do you have?

and also for user that have touch problem which is model of your sensation?

i got the touch problem a few months back, because i carged my phone with a Chinese charger, now i switch to the HTC ONE X charger and is very good, and i never get this problem.
[HTC Sensation] pogs24ever:
s2w

+1... i will come back to Sense Rom once s2w is implemented again... AFAIK HTC phone is the only phone who can do this stuff which makes us unique!. Please add them Sebastian! Thanks! :laugh:
[HTC Sensation] SebastianFM:
I have non Xe Sensation. I don't have any issues with touchscreen.

You don't need to worry about that. System daemon thermald sets recover frequency to 1836 MHz but my modified rules for PnPMgr doesn't allow it to increase CPU frequency to higher value than defined maximum. I checked in kernel cpufreq driver that CPU frequency never is set to higher value than defined in pnp.xml.
[HTC Sensation] VekiCRO:
Thank you for your excellent work Sebastian :good:

Will you enable voltage control in future?
[HTC Sensation] Sorin90:
Is there any way to change CPU voltage for the various frequency?( VDD support)
[HTC Sensation] zooster:
Ok, I've taken a video of some of touchscreen issues: https://www.youtube.com/watch?v=-OJUZOt1nhQ

The one depicted in the video is related to the most annoying issue: low or incorrect sensitivity in the lowest part of the touchscreen. But I've also experienced hyper sensitivity especially while swiping left-right at the edge of the screen, and sometimes I've seen SwiftKey first not responding correctly and after typing and swyping itself like there was ghost. I've also attached kmsg.txt as requested.
[HTC Sensation] ivicask:
I had exactly 100% the same issue, and also while swiping home screen it was actually lagging as touchscreen inputs where not correctly recognized.Or pressing on icons did nothing 2 even 3 times than pushing 4th time opens app, or scrolling in app drawer would some time open apps..

Putin aluminium foil to contact DID fix it, and now touch performs beautifully without even a single issue!

Your Kernel log doesn't show any errors, what is strange as i see it, it detects lots of little movements/touches in very short times, thats why you get unlock problems.

Thats just proves again its hardware issue,maybe your digitizer is getting bad, you have bad charger, or your phone has grounding issues and you must try that aluminium foil trick!
[HTC Sensation] MidnightDevil:
Can you tell me where you put the foil ? In which contacts? :)
[HTC Sensation] Sprint82:
I had the touch issue several times, mostly when the charger was plugged in or something else was connected to the micro USB port.

why and why not if nothing was plugged I don't know.
[HTC Sensation] Bastaerd:
Grounding issue.
[HTC Sensation] Sprint82:
You mean wrong wired cable or something?
[HTC Sensation] zooster:
Despite I was quite sure it wasn't pin's fault I wanted to give it a try.

I just used the tiny aluminium foil (trick usually needed when the WHOLE touchscreen is not responding and not part of it) and I can confirm again that the touch issue is still exactly there.

The odd thing is that only lower part of touchscreen doesn't correctly detect touches, while the rest seems to work quite fine (beside some casual oversensitivity).

This issue occurred SUDDENLY with the flash of 3.1.0, previously I was using 1.6.3 and it was just fine. But if you have doubts about that I can try to restore previous nandroid to show you it's not hw fault.

Just my 2 cents, maybe there are several types of touchscreen revisions, and the ported kernel, as it is, works fine only with those touchscreen revisions with a sensitivity closer to the one of newer villec2, therefore it needs to be adjusted on sensation's one...
[HTC Sensation] Bastaerd:
Jup, but if it happens only when you plug in something, it's probably a circuit in your phone.
[HTC Sensation] Sprint82:
I've read about the aluminium foil trick (1 or 2 pages above) to cover the grounding pin on the side of the backcover. could that help in my case?
[HTC Sensation] Sherlocks:
I know that method is fix touch issue.

First. You prepare to pg58img.zip gingerbead ruu.

And you try to copy pg58img.zip in sdcard.

Go to bootloader. After installed gb, you try to ota ics update. Do not try ics ruu. Very important ota update. After finished ota update, you flash recovery and install revelation or vipers.

I exprienced to this issue as changed LCD or mainboard.

Above solution is perfect fix method.

Good luck. Feedback me :)
[HTC Sensation] zooster:
Nope no way... Too much hassle :)

But again, with vipers 1.6.3 it's absolutely fine, while with 3.1.0 doesn't.
[HTC Sensation] Sherlocks:
I recommend you to my opinion. Maybe it help your issue like magic.
[HTC Sensation] faultytowersdude:
I had issues a while ago turned out to be a dodgy digitiser dropping it finally killed it, bought a new one off the net for about £15 squid. Replaced it bish bash bosh good as new.
[HTC Sensation] dub2012:
Does anyone seem to have noticed the high number of touchscreen issues RECENTLY?

Most people are suggesting grounding or other hardware as the cause yet it seems most are on JB sense roms.

My problem was fixed by flashing screen calibration file and updating firmware.

Maybe I just got lucky but its worth looking into.
[HTC Sensation] sacid55:
still low battery life with vipers
[HTC Sensation] Mark376:
[MENTION=2212152]SebastianFM[/MENTION]

We have serious low memory issue

since our phone have only 768mb ram with heavy Sense 4+ jellybean rom

we could try optimizing the minfree the parameters should be lower or higher

this is my value maybe this is not perfect

1536,2048,6656,7168,7680,8192

or use this

echo "1536,2048,6656,7168,7680,8192" > /sys/module/lowmemorykiller/parameters/minfree
[HTC Sensation] hinxnz:
I also think it is to coincidental that the problem arises with many as it has once again. I can use the touchscreen without any issues with responsiveness with no back cover at all, have been so for the last hour.

Edit: Just some more thoughts but I have now put the back cover back on as this thought came to my mind but doesn't explain the coincidental popularity of people reporting the issue, that maybe it's static electricity that is caused by swiping etc building up and not able to ground causing unresponsiveness and even causing damage eventually. This is just a thought and nothing else though, it could be a lot worse for some with type of screen protectors or similar factor. You would think if this is the case though it would cause many random touches instead of unresponsive/sticky like screen actions. If it's a grounding issue, how does it ground via backcover? Is it connected to negative terminal on battery and if so having a faulty earthed battery cause it...

Then again if it certainly not happening on different rom/kernels after the issue arises and testing for a decent period of time then the issue must lay with software.
[HTC Sensation] The_Hamster:
DSLr-controller is still not working with this kernel.. Logs from ViperS 3.1.1 attached

Logcat:

Line 4961: V/UsbDeviceManager( 439): [USBNET] USB UEVENT: {SUBSYSTEM=platform, DEVPATH=/devices/platform/msm_otg, EVENT=DEV_NOT_SUPPORTED, MODULE=msm_otg, SEQNUM=3452, ACTION=change, DRIVER=msm_otg, MODALIAS=platform:msm_otg}
Line 4963: D/UsbDeviceManager( 439): [USBNET] update2: 6,0
Line 4965: D/UsbDeviceManager( 439): [USBNET] handleMessage: 6; mConnected=false, mConfiguration=false
Line 4969: D/UsbDeviceManager( 439): [USBNET] sendStickyBroadcast ACTION_USB_HOST_MODE
Line 9879: V/UsbDeviceManager( 439): [USBNET] USB UEVENT: {SUBSYSTEM=platform, DEVPATH=/devices/platform/msm_otg, EVENT=DEV_NOT_SUPPORTED, MODULE=msm_otg, SEQNUM=3476, ACTION=change, DRIVER=msm_otg, MODALIAS=platform:msm_otg}
Line 9881: D/UsbDeviceManager( 439): [USBNET] update2: 6,0
Line 9883: D/UsbDeviceManager( 439): [USBNET] handleMessage: 6; mConnected=false, mConfiguration=false
Line 9885: D/UsbDeviceManager( 439): [USBNET] sendStickyBroadcast ACTION_USB_HOST_MODE

Dmesg attached to post
[HTC Sensation] zooster:
Disable Google now.
[HTC Sensation] TookeX:
is this 1.0.1 version of kernel support zram?
[HTC Sensation] SebastianFM:
In kernel 3.4.10 zRam driver has changed and it is only compatible with x86. I thinks zRam isn't good solution if you need swap because it reduces free RAM size. What do you think about Turbo Boost?
[HTC Sensation] Aca902:
No, it doesn't.

EDIT: didn't saw sebastian answered :) I also think that zram isnt a good solution, while using it you may still encounter lag... and i had same experinces with swap on sdcard, but now with swap on nand memory - no lag, very useful.
[HTC Sensation] TookeX:
i just tried turbo boost on my ViperS 3.1.1 with Multitasking Xtreme minfree setting

i noticed that in task manager there are much more process and app show in list

but when you touch some app icons or switch one from recent apps

it show blackscreen about seconds

i know that internal memory is less slower than ram so maybe turbo boost will slow down when data swap from internal memory to ram

so i wanna try Zram
[HTC Sensation] zooster:
[MENTION=2212152]SebastianFM[/MENTION]

I've taken another video about touchscreen issues. This time I've enabled touch highlight and position coordinates and trace in developer option. And it's clearly visible that at the bottom (I thought 5mm but it's actually more than 1cm) the trace stops bending upward a little bit. You can also see coordinates and pressure values in the top bar. Hope it can help somehow.

https://www.youtube.com/watch?v=ZhdCGr0ofck

If you cannot watch it in HD with android YouTube app use browser in desktop mode (adobe flash).
[HTC Sensation] TookeX:
which rom do you use ?

and what's your setting about oom values?
[HTC Sensation] farazejaz:
can i use this with elegancia rom? really excitted to tesr usb otg without external power :D

do viper and revelation 1.01 have this kernal compiled in them ? means flashing them will flash this kernal too? i want to use USB otg without external power so do i have to flash any of those two roms ?
[HTC Sensation] nikola016:
I think that this kernel won't boot sense 4.1 roms. So for now you can't.
[HTC Sensation] m.m.m:
I posted this in ViperS ROM topic but got no response, I think it's related to the kernel:

When I mount a usb storage using usb storage manager app it fails and then this messages appear:

Unlock

SD card encrypted

Usb storage damaged

Blank usb storage

Then it mounts the usb in storage /usb then after a minute this notification appears:

(I didn't encrypt anything)

http://xdaforums.com/attachment.php?attachmentid=2127760&d=1374237343

does anyone have the same problem?

also another thing about the drivers, I used silvercrest MTS2118 wireless keyboard and mouse (they used one receiver), and in usb host controller app it even recognizes the name of device but doesn't recognize that it is a mouse or keyboard and doesn't work. I have the drivers for windows, and also the CD from manufacturer, if you need it, I can attach that.

thanks a lot.
[HTC Sensation] Aca902:
I use Revelation 1.0.1, and i don't use swap with this rom. Because i like it as stock as possible. As for oom values, i haven't change anything - for the same reason... btw having great preformance and battery (stock settings, cpu [MENTION=1528666]151[/MENTION]2. :)
[HTC Sensation] Sherlocks:
Please try to my solution.

It help your issue to fix like magic.

Trust me
[HTC Sensation] hinxnz:
Swap or turbo boost is good at first until swap fills up and then phone basically hangs, AFAIK for apps to close properly to free swap, pages need to load back into RAM but from my experience this doesn't really happen which causes swap to full up but it would be great for us if it did act properly besides the amount of write cycles it does on our phones memory and sd card is to slow for swap and not so reliable/stable IMO

Sent from my HTC Sensation
[HTC Sensation] Sherlocks:
try to http://xdaforums.com/showthread.php?t=2246355

---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------

http://xdaforums.com/showthread.php?t=2083229

one s 3.4 kernel have a zram.
[HTC Sensation] m.m.m:
I wanted to add a keyboard driver to the phone's kernel, not to install an htc driver on my OS.
[HTC Sensation] Far_SighT:
One issue I would like to report:

When I set Max CPU to 1188/1566 MHz in venom tweaks. this seems to apply to only one core (Core0), the other core still goes upto the value set during kernel(rom) flash. What's wrong?
[HTC Sensation] Harbir:
its not a bug u should only use aroma to change the cpu freq ,and when i change my freq from viper tweaks my both cup freq changes ;)
[HTC Sensation] Mark376:
Bump! Because of this issue was sometimes the foreground killed by LMK

Like real racing

Will upload logcat soon
[HTC Sensation] Far_SighT:
Use Turbo Boost. It's really awesome.

Here.

Jam that THANKS button.
[HTC Sensation] Mark376:
Yes turbo boost use swap

we need to adjust the LMK because not everyone use swap for daily basis
[HTC Sensation] SebastianFM:
It's not issue. Amount of RAM is limited. If you want to have cool looking Sense 4+ which consumes a lot of memory, you must accept that when you use it some other apps in background may be killed.

I already adjusted lowmemorykiller settings. I used stock settings for Sensation, 4252,5416,6580,7946,13664,16854 (for One S was 7946,9953,11960,14008,16015,25108).