Develop Bugs

[TESTING] CONCLUDED! (For the time being...)

Hey all,
Nothing to test right now... Hopefully we'll have a new kernel to test, I will update when that happens.

Reserved...

Reserved...

1st run testing
I just tested this by replacing my existing zimage and modules on my att tilt 2 running xdandroid 09.16.10 reference with NRGY Rom and it loads into android ( I get to the lock screen)...then it vibrates and promptly shuts the phone down....I have to power it back up into windows. and it repeats.

Dropped it on over the 9/16 build and it crashed and rebooted on the first boot. Will continue trying.

same here.. getting to the initial lock screen and then it is shutting down automatically. Requires me to hit the power button and then it boots back into Windows.
I have tried to delete my data store, but that is about it. Any ideas?

doesnt sound like its working. I'll make some changes and have a re-release for this.
Thanks so far for the tests

I am seeing the same results as many others. I get to the android lock screen and then it vibrates and seems to lock up.
I have a rhod400 and I am using the 8/30 blazn release.

jeneric said:
I am seeing the same results as many others. I get to the android lock screen and then it vibrates and seems to lock up.
I have a rhod400 and I am using the 8/30 blazn release.
Click to expand...
Click to collapse
Same here, with the same hardware. Going to have to wait until I get an updated kernel, it sounds like a patch is in this kernel that isn't supposed to be in there
I'll update the first post when I get a new kernel.
So I seemed to get this kernel working on the NBH testing... at least I'm assuming it's using this kernel!

This is exciting, thanks a lot for the hard work devs, and looking forward to a new kernel to test

RHOD100, After boot animation - landscape lock screen and "no service". After unlock it - i had "rebooting".

Jabader said:
RHOD100, After boot animation - landscape lock screen and "no service". After unlock it - i had "rebooting".
Click to expand...
Click to collapse
Yes, read the big bold text on the first post
I will update when I get a new kernel... but I haven't gotten one yet!

arrrghhh said:
Yes, read the big bold text on the first post
I will update when I get a new kernel... but I haven't gotten one yet!
Click to expand...
Click to collapse
tell the devs that most of us are waiting patiently
and that we wait anxiously to test their work

noodles21o2 said:
tell the devs that most of us are waiting patiently
and that we wait anxiously to test their work
Click to expand...
Click to collapse
Haha no worries guys. I'm anxiously awaiting a new kernel for the public... in the meantime I've been testing some stuff for the button lights at the bottom of the phone & the ambient light sensor for the screen brightness... it's very promising!

Will the above light control maybe lead to a backlight keyboard? [fingers crossed!]

Serren said:
Will the above light control maybe lead to a backlight keyboard? [fingers crossed!]
Click to expand...
Click to collapse
I haven't heard that talked about yet, but it does seem like a natural progression... there's a guy who has some some coding with Qualcomm chips, seems to really know his stuff. I've been helping him test kernels on my RHOD400.

Same problem as other bootup to lockscreen then vibrate and restarts automatically back into windows.
Rhodium
Touch Pro 2
Energy Rom

Don't mean to necro, but I'm stoked for this fix any updates?

Working with the devs now... I think I'll have another kernel to test soon. Don't hold your breath tho

arrrghhh said:
Working with the devs now... I think I'll have another kernel to test soon. Don't hold your breath tho
Click to expand...
Click to collapse
You, sir, are a gentleman and a scholar for conveying this information lol
Ok sweet, sounds good to me!
Keep up the good work
Regards
Smith

BLN Support for SGS2 - With Example.

Hi Dev's
This is not my code, so credits to the owner 'creams'
I happened to stumble on some code yesterday from somebody who have attempted to integrate BLN to his kernel and done it successfully.
I thought the dev's might like to take a look at this one and implement this on their work.
blog : http://creamsnexus.blogspot.com/
git : git://github.com/creams/SGS2-SC02C-BLN-Kernel.git
His kernel was built for the Jap version of GS2.
Cheers!

AdamG has already implemented this into his AOSP ROM and it's working fantasticly, I know another Dev has already implemented it into a ROM just forgot his name. Thanks for pointing us to the source though!

hope that the devs give credit to the fix/implementation.

Ninpo also has putted it into his GIT so maybe they are already aware of it

oh i gave him a pm about it before i posted this.

samaral said:
oh i gave him a pm about it before i posted this.
Click to expand...
Click to collapse
July 31 in his GIT. You're ahead of him maybe.

I hope we will get it on MIUI and CM7 as well

vegetaleb said:
I hope we will get it on MIUI and CM7 as well
Click to expand...
Click to collapse
Don't know about MIUI but for sure on CM7. It's probably low on their to do list but BLN is something they will most definitely support just as they did with the 2X/G2X

mach0boi said:
July 31 in his GIT. You're ahead of him maybe.
Click to expand...
Click to collapse
im from the past
i didnt check his git commit date. thanks for the correction.

Do i also need to install any app from the market to enable it ?
Answer : Yes

Sorry if this is a noob question but what is BLN?

soupiejr said:
Sorry if this is a noob question but what is BLN?
Click to expand...
Click to collapse
Back Light Notification
using the led keys for notification.

Yay, my kernel will have BLN support to in the next version, just need to build all the seperate versions
(time to make a "one-for-all" kernel, that goes onto any (stock) ROM.... )

the only downside to this bln "version" is that it uses a kernel wakelock that will be hard on the battery

ogdobber said:
the only downside to this bln "version" is that it uses a kernel wakelock that will be hard on the battery
Click to expand...
Click to collapse
Yep, people are in for a treat when they realize their battery is being raped. We'll have to wait for CM7 to implement it into the framework like they did with the Optimus 2X/G2X

Nothing can beat the old good trackball lights on N1
It's a pitty all the brands stopped producing trackball,they could just reduce its size

ogdobber said:
the only downside to this bln "version" is that it uses a kernel wakelock that will be hard on the battery
Click to expand...
Click to collapse
jlevy73 said:
Yep, people are in for a treat when they realize their battery is being raped. We'll have to wait for CM7 to implement it into the framework like they did with the Optimus 2X/G2X
Click to expand...
Click to collapse
Yeah.... that is.... so not nice.... but well.... can't have everything.... :-/
// EDIT
Hm, for one, maybe some things can still be tweaked in the involved kernel code and for the other, how about disabling BLN when not needed? Does that release the wakelock? Haven't checked yet.... should check....
And does the drain/wakelock accour all the time while while activated or only when the lights are actually on - as far as I understood it so far the wakelock ist required to keep the powersupply up for the lights, but when no blinking is needed (due to no notification) the wakelock could/should be released....
Maybe that's something to tweak if that isn't already the case.
If the drain only accours when the lights are on, that's kinda OKish IMO, time to answer the damn phone *lol*

so creams put out an update that is supposed to release wakelock after the led cycle (pro app needed)
That would be an acceptable solution, I am testing to see
ps, btw jlevy he wasn't keen to your battery rape comment
HellcatDroid said:
Yeah.... that is.... so not nice.... but well.... can't have everything.... :-/
// EDIT
Hm, for one, maybe some things can still be tweaked in the involved kernel code and for the other, how about disabling BLN when not needed? Does that release the wakelock? Haven't checked yet.... should check....
And does the drain/wakelock accour all the time while while activated or only when the lights are actually on - as far as I understood it so far the wakelock ist required to keep the powersupply up for the lights, but when no blinking is needed (due to no notification) the wakelock could/should be released....
Maybe that's something to tweak if that isn't already the case.
If the drain only accours when the lights are on, that's kinda OKish IMO, time to answer the damn phone *lol*
Click to expand...
Click to collapse

ogdobber said:
so creams put out an update that is supposed to release wakelock after the led cycle (pro app needed)
That would be an acceptable solution, I am testing to see
Click to expand...
Click to collapse
NICE!
Compiler is already running

ogdobber said:
so creams put out an update that is supposed to release wakelock after the led cycle (pro app needed)
That would be an acceptable solution, I am testing to see
ps, btw jlevy he wasn't keen to your battery rape comment
Click to expand...
Click to collapse
It wasn't anything personally directed at him. I'm very grateful for his work in bringing BLN to our devices. I appreciate the update it looks like it will have a helpful impact on battery life.

Proximity sensor?

Searching on the proximity sensor I found these two parameters for the startup.txt:
board-htcrhodium-proximity.on=1 to enable the proximity device (default off)
board-htcrhodium-proximity.wake=1 to wake up the phone on proximity
http://xdandroid.com/wiki/Kernel_boot_command-line_parameters
But I can't get them to work.
Are they really available on FRX07 or NeoFroyo?
Thanks

Daved+ said:
Searching on the proximity sensor I found these two parameters for the startup.txt:
board-htcrhodium-proximity.on=1 to enable the proximity device (default off)
board-htcrhodium-proximity.wake=1 to wake up the phone on proximity
http://xdandroid.com/wiki/Kernel_boot_command-line_parameters
But I can't get them to work.
Are they really available on FRX07 or NeoFroyo?
Thanks
Click to expand...
Click to collapse
The prox sensor is not enabled on the hardware level (kernel). Perhaps they will be available soon tho, I think ACL was working on them.

arrrghhh said:
The prox sensor is not enabled on the hardware level (kernel). Perhaps they will be available soon tho, I think ACL was working on them.
Click to expand...
Click to collapse
Oh... good. Thanks for letting me know!
Would you mind if I ask you about using the PTT button?

Daved+ said:
Oh... good. Thanks for letting me know!
Would you mind if I ask you about using the PTT button?
Click to expand...
Click to collapse
What about it? Only the RHOD300 has it... No other RHOD has one.

arrrghhh said:
What about it? Only the RHOD300 has it... No other RHOD has one.
Click to expand...
Click to collapse
Yes and I have one of those. Any chance I can give it some use? I googled a lot and tried a couple things with no success. Thanks!

Daved+ said:
Yes and I have one of those. Any chance I can give it some use? I googled a lot and tried a couple things with no success. Thanks!
Click to expand...
Click to collapse
I think that if it's enabled kernel-side(I don't think so) you need to edit keymaps in rootfs to use it
But if it's not used kernel-side then you have to mess with the source

Daved+ said:
Yes and I have one of those. Any chance I can give it some use? I googled a lot and tried a couple things with no success. Thanks!
Click to expand...
Click to collapse
There's some hacking at the rootfs you'd have to do. F22's rootfs allowed you to remap the key to a few different things, but unfortunately he never made a merge request for his code... which wouldn't have been easy, he would've had to change the way he did certain things. His rootfs hasn't been updated in quite some time, so I would not recommend using it. I'm sure you can take his keymap stuff tho and put it into an updated rootfs - with a little bit of manual labor you'll be able to remap the PTT key to a few different things.
See F22's rootfs thread for more info on that.

i should have something to test for the prox sensor this week. Just finished the patch .. To be honest i have no idea when it's actually used or if our userland is ready for it.

[ACL] said:
i should have something to test for the prox sensor this week. Just finished the patch .. To be honest i have no idea when it's actually used or if our userland is ready for it.
Click to expand...
Click to collapse
I'll be happy to test it

kernel done but turns out we need some userland patches.

Wow you're really Johnny on the spot

i dunno if thats good or bad

I thought it was good, but sometimes when I try to make a reference it goes horribly awry.

Looks like this will be saved for gingerbread. Since userland changes need to be made, its not worth it to make em for froyo.
So next release of GB will have it

[ACL] said:
Looks like this will be saved for gingerbread. Since userland changes need to be made, its not worth it to make em for froyo.
So next release of GB will have it
Click to expand...
Click to collapse
One more reason to be eagerly awaiting a new GB drop.
Any ETA at all on that?

mbellot said:
One more reason to be eagerly awaiting a new GB drop.
Any ETA at all on that?
Click to expand...
Click to collapse
Never ask for eta.
It's better to have a nice surprise than a delayed build..

helicopter88 said:
Never ask for eta.
It's better to have a nice surprise than a delayed build..
Click to expand...
Click to collapse
Pretty much the first rule of any dev work - especially free/OSS - never ask for ETA.
Thanks!

actually prox is only tested on cdma and the gsm portion needs to be checked. Anyone have a recmodded rom ? or know how to pull dlls? PM me please since i need to double check on some stuff

[DEV/WIP] doubletap2wake & swipe2wake

Hello,
I'm currently implementing doubletap2wake and swipe2wake into the stock unsecured kernel.
If someone could help, that would be great. My C/C+ experience = 0%.
So if you guys have tips or source, help is always welcome!
Thanks,
Rinse

TheRinseM said:
Hello,
I'm currently implementing doubletap2wake and swipe2wake into the stock unsecured kernel.
If someone could help, that would be great. My C/C+ experience = 0%.
So if you guys have tips or source, help is always welcome!
Thanks,
Rinse
Click to expand...
Click to collapse
actually, the stock kernel has support for this,only with root, but sadly its a propitiatory app (i dont get it either) called PGM nexus which makes use of it and u can double tap to wake, slide to wake and touch to wake .
https://play.google.com/store/apps/details?id=net.ponury.pgm2&hl=en

shriom_manerker said:
actually, the stock kernel has support for this,only with root, but sadly its a propitiatory app (i dont get it either) called PGM nexus which makes use of it and u can double tap to wake, slide to wake and touch to wake .
https://play.google.com/store/apps/details?id=net.ponury.pgm2&hl=en
Click to expand...
Click to collapse
Thanks alot sir! I'll request to delete this thread.
Thanks!!
Rinse

TheRinseM said:
Thanks alot sir! I'll request to delete this thread.
Thanks!!
Rinse
Click to expand...
Click to collapse
hold on, never give your hopes up, This is only for the galaxy nexus and the nexus 4 if you can do this for other devices it would be great

shriom_manerker said:
hold on, never give your hopes up, This is only for the galaxy nexus and the nexus 4 if you can do this for other devices it would be great
Click to expand...
Click to collapse
And better if possible via kernel SysFS,not an app.A module like sweep2wake(the one from Showp1984) would be better!And not closed source like PGM is..sadly

sert00 said:
And better if possible via kernel SysFS,not an app.A module like sweep2wake(the one from Showp1984) would be better!And not closed source like PGM is..sadly
Click to expand...
Click to collapse
yes ! exactly ! open source is the way to go besides pgm no longer supports newer kernels for 4.3 (only stock no trace and trace methods are supported ) which i guess some kernel developers dont use. anyways please make it open source if possible

shriom_manerker said:
yes ! exactly ! open source is the way to go besides pgm no longer supports newer kernels for 4.3 (only stock no trace and trace methods are supported ) which i guess some kernel developers dont use. anyways please make it open source if possible
Click to expand...
Click to collapse
Sadly my C\C++ skills are very limited,i would have been happy to help you out

TheRinseM said:
Hello,
I'm currently implementing doubletap2wake and swipe2wake into the stock unsecured kernel.
If someone could help, that would be great. My C/C+ experience = 0%.
So if you guys have tips or source, help is always welcome!
Thanks,
Rinse
Click to expand...
Click to collapse
How far have you come?
I can imagine, with 0% C/C++ experience, it is somewhat of an uphill.
sert00 said:
Sadly my C\C++ skills are very limited,i would have been happy to help you out
Click to expand...
Click to collapse
Here is an implementation for Nexus7 (2013)
https://github.com/flar2/flo/tree/ElementalX
Something to work with perhaps?
Cheers,
/J

I'd check @faux123 git. He's done this for a few devices with settings to turn on and off in his app.

Anybody still working on? Got a few thoughts.
A good place to start would be to look up the "gpm hack" and "gpm mouse" in duckduckgo. I think there is a lot of good stuff you'll find. Another thing to get familiar with is parsing the output of /dev/input/event* and the builtin touch screen emulation with android's "input" command line function, "input touchscreen" to be more exact.

Shameless bump, but is someone still interested in this?

I Am!

thewisenerd said:
Shameless bump, but is someone still interested in this?
Click to expand...
Click to collapse
I am lol

[8.1] [Magisk Module] Multi-Touch Fix for 8.1 Devices

Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
It seems devices with oos on 8.1 ( op5/t) cannot use this mod.
AOSP and LOS roms should be okay.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07

@calebcabob
 @Myself5
 @BDogg718
 @sixohtew
 @nitin.chobhe
 @auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.

This causes a bootloop on P DP1.

iaTa said:
This causes a bootloop on P DP1.
Click to expand...
Click to collapse
Thanks for the report.
can anyone confirm this?
In the meantime i removed the p tag from the thread title.
Could be That there are additional changes in p that make this libs unusable and only workable on 8.1.
Unfortunately there is afaik no complete source for p yet. So I can’t compile them specifically for p.

Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!

jbarcus81 said:
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
Click to expand...
Click to collapse
Same with me on google fotos!
Glad it’s fixed for you.

Freak07 said:
Same with me on google fotos!
Glad it’s fixed for you.
Click to expand...
Click to collapse
Also fixed for me, thanks for solving this problem!

I can't replicate this problem, but good to know that there's a fix if I ever experience it.

I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks

I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch

Prey521 said:
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
Click to expand...
Click to collapse
sixohtew said:
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Click to expand...
Click to collapse
I also thought at first I didn’t have this issue at all.
But once I triggered it accidentally I experienced it many times. Maybe I just learnt what to look for.
Another fun thing is. A friend of mine also got the pixel XL 2 and I could reproduce it right away on his locked phone which is stock 8.1.
I can also trigger it on my pixel C tablet.

ReapinDevil said:
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
Click to expand...
Click to collapse
Either try flashing it in recovery or use the latest magisk?

Freak07 said:
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
 @auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
Click to expand...
Click to collapse
The mention for the last dev didn't work for some reason, so:
@auras76

mistermojorizin said:
The mention for the last dev didn't work for some reason, so:
@auras76
Click to expand...
Click to collapse
Thanks in the quote from your post of my post it worked tough

Freak07 said:
Thanks in the quote from your post of my post it worked tough
Click to expand...
Click to collapse
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the quote.

Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !

What app did you use for that test?

I've experienced lack of touch response quite often. It's weird and seemingly random. I just flashed this on 8.1 with magisk. I don't have any results yet, but based on what everyone else is saying, this is a solid fix. Thanks for your work!
Do we have to worry about removing this in the future if google updates fix the issue too? Will this being on the system cause conflicts and issues?

mistermojorizin said:
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the Autor.
Click to expand...
Click to collapse
That’s just xda bring xda.
I had this problem a few times when updating the OP for a new release. Sometimes the OP won’t update at all...

otonieru said:
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
Click to expand...
Click to collapse
Glad it works out for you!
Enjoy your phone