[10/10/13]neXusKERNEL v4.0 with Sweep2Wake ALPHA [JB]

[CurtisMJ]

you havent switched to the correct tree (https://github.com/ProtoU/neXusKERNEL/tree/s2w). I always keep my github updated with local changes.

Thanks, my github skills are a little rusty. :laugh:

Been testing alpha build in meantime, woke up from deep sleep this morning with a swipe (two actually). Wonder if I'm gonna be another perfect tester.

Edit: BTW, for live kmsg,

adb shell cat /proc/kmsg

Sorry if it was already figured out. Just realized my successful wake this morning may have been bugged. Haven't used s2w since then, so it should be easy to spot the flags in last_kmsg.

 

[-Johan]

Noob question incoming.. How would I install this? Installing it with the toolkit doesn't work. Thanks in advance.

 

[GtrCraft]

Noob question incoming.. How would I install this? Installing it with the toolkit doesn't work. Thanks in advance.

In fastboot do ''fastboot flash boot kernelname.img'' with cmd

 

[Tresox]

Noob question incoming.. How would I install this? Installing it with the toolkit doesn't work. Thanks in advance.

Just boot into bootloader and choose fastboot.
Make sure that the kernel is named boot.img NOT boot1.img or boot.img(1) .
Then connect your phone on your PC with a usb.
Open your toolkit and select install kernel, it's gonna say phone not detected.
So close that window and another one will popup and then it's done

 

[-Johan]

In fastboot do ''fastboot flash boot kernelname.img'' with cmd

Just boot into bootloader and choose fastboot.
Make sure that the kernel is named boot.img NOT boot1.img or boot.img(1) .
Then connect your phone on your PC with a usb.
Open your toolkit and select install kernel, it's gonna say phone not detected.
So close that window and another one will popup and then it's done

So I did the right thing before, how long is the 'waiting for device' window meant to be there though? It doesn't seem to be closing.
Thanks for the replies!

 

[CurtisMJ]

So I did the right thing before, how long is the 'waiting for device' window meant to be there though? It doesn't seem to be closing.
Thanks for the replies!

It should close as soon as you connect the device via cable. Do you happen to be working on Windows 8? If so, you'll need to do this on an older box or from the terminal in a linux distro until HTC updates the drivers to be Windows 8 compatible. Even if you don't have windows 8, try on a different machine anyway, low-level drivers tend to be weird. If you happen to have an android tablet with a usb port, there are arm builds of fastboot as well.

 

[-Johan]

It should close as soon as you connect the device via cable. Do you happen to be working on Windows 8? If so, you'll need to do this on an older box or from the terminal in a linux distro until HTC updates the drivers to be Windows 8 compatible. Even if you don't have windows 8, try on a different machine anyway, low-level drivers tend to be weird. If you happen to have an android tablet with a usb port, there are arm builds of fastboot as well.

Well yeah, I have Windows 8. I'll try it on another computer when I can get my hands on one, thanks!


Edit: Well, now it doesn't automaticly reboot to the bootloader and says 'can't find path 'C\users\pcname''. It does open a reboot CMD after exiting the 'can't find path' one now, though.

 

[McGrady]

i hate my new Desire X for the PowerButton before i use your Sweep2Wake feature now its no problem to wake up the phone... Thank You !
But there are there any chances of success for a solution to the display problem? I know the problem is known. The funny thing is sometimes it works without reboot.

When I turn on the screen, I sometimes can not pull the lockscreen ring. Screen on and off after press the power-button. But can not do anything.
Press Screen off.... wait a little ... then sometimes goes again. Sometimes wait a little longer

can i help ... More information, logcat or something else?

 

[neXus PRIME]

Thanks for testing.... Yes, there are buggy wakeup by sweep sometimes which cause hangup.... Known issue, but I will try to fix it when I find some free time from office....

Sent from my C5303 using Tapatalk

 

[kostovdean]

Thanks for testing.... Yes, there are buggy wakeup by sweep sometimes which cause hangup.... Known issue, but I will try to fix it when I find some free time from office....

Sent from my C5303 using Tapatalk

Why don't you make several kernels for testing so we can report back?

Sent from my HTC Desire X using Xparent Cyan Tapatalk 2

 

[neXus PRIME]

Why don't you make several kernels for testing so we can report back?

Sent from my HTC Desire X using Xparent Cyan Tapatalk 2

As i said, i cant find time... if you guys wanna help me here, find some patterns, do this...
Any compiler out there, please make a boot.img using my tree
https://github.com/ProtoU/neXusKERNEL/tree/s2w


After you have forked it, go in below file:
https://github.com/ProtoU/neXusKERN...4cfe63/drivers/input/touchscreen/himax8526a.c


Put some flags in suspend, resume, earlysuspend, and early resume functions.... compile it... and post the boot.img here


THen people flash it, use the s2w a lot of times, copy the kmsg from device, and post here.... reading that kmsg, and the flag sequnce when a freeze occurs, we can find the culprit and go on debugging it.

So anyone up for it?

 

[hell_lock]

Can someone actually describe me how the freezes were? I am asking it in the point of view of a user and not a developer.

 

[filipcar]

Can someone actually describe me how the freezes were? I am asking it in the point of view of a user and not a developer.

For me the freezes were happening when you unlock your phone (button or swipe) you cant do anything the screen is not responding .You can still unlock and lock your phone with swipe2wake and the only solution i to wait(hour or something ) or just reboot .Maybe it wont freeze if you disable lockscreen , maybe the lock screen freezes i dont know i forgot to test it im on V3 and its awesome and it is great for the battery.
Hope this helped.

 

[neXus PRIME]

Can someone actually describe me how the freezes were? I am asking it in the point of view of a user and not a developer.

The resume function to wake screen called by a Swype sometimes remained incomplete... Causing the touch screen to be disabled.... However display lights up.... If you wait a couple of minutes, the kernel sorts out the bug, recovers, and then swipes work again....

Just the temporary screen disable caused by some buggy swipes is the issue.... Otherwise it work ok 90% of the time

Sent from my C5303 using Tapatalk

 

[alkox]

any idea when desire x will get complete s2w...
I will have to rely on it as my power button is almost dead..

Sent from my HTC Desire X using XDA Premium 4 mobile app

 

[McGrady]

When I turn on the screen, I sometimes can not pull the lockscreen ring. Screen on and off after press the power-button. But can not do anything.
Press Screen off.... wait a little ... then sometimes goes again. Sometimes wait a little longer, than goes again or i must restart the DX.
When the Screen is on without Touchscreen working i test the vol + and vol - keys and this works! But it probably seems to be a pure touchscreen problem.
After i Install no-frills cpi with 1008 ghz, 245 mhz smartass V2 and bfq I have a feeling that the problem is not so common. But just a feeling

it would be awesome if S2W would run stable! :good:

 

[neXus PRIME]

Omg... You guys really rub in the issue....
Screen not responding is a known bug

Sent from my C5303 using Tapatalk

 

[McGrady]

i know... but InfinityShooter ask if a user can describe the error. or have I misunderstood?

 

[neXus PRIME]

i know... but InfinityShooter ask if a user can describe the error. or have I misunderstood?

Oh... Ok.

Sent from my C5303 using Tapatalk

 

[CurtisMJ]

Debug Build

Here you go, debug build as requested by nexus PRIME (Sorry for being late, I was too busy with school to do big stuff)

Instructions for testers:
Make sure you have USB debugging enabled in developer settings!
1. Test till the screen freezes.
2. Once you get it to freeze, hold down the power button till your phone reboots (It should display a message saying "Your phone is rebooting in [x] seconds" or something similar)
3. Once rebooted, connect your phone to your PC and type the following command in a command prompt.

adb pull /proc/last_kmsg KernelLog.txt

This will generate a file called "KernelLog.txt" in the working directory.
Post KernelLog.txt to this thread with any other information you can provide about the circumstances!
Thanks in advance to all testers.