Develop Bugs

BLN port to cm7/miui kernel

Hi guys,
I'm trying to get BLN working on CM7/MIUI kernels but this is still somewhat over the top for me
the needed changes to completely revert led-notifications and add BLN
can be found in my repo in the following branch:
BLN04
the initial commit compiles fine but I'm not sure if it works (haven't tried it yet)
the 2 additional commits on top have changes from the Samsung kernel which most likely do NOT apply to our kernel
and the last one an update to the latest BLN version which doesn't compile since I get an error
I've only added those for completeness' sake
keep in mind we're using the cypress touchkey driver from the Nexus S - also: our touchkey driver has the firmware update-mechanism removed so those parts are missing in the driver
so the BLN patch from Samsung kernels doesn't work easily
some references to make it easier:
* led-notifications (BLN fork): LED notification support
* BLN on GB samsung kernel: initial bln for i9000 gingerbread (neldar's repo)
* initial BLN on morfic's Nexus S kernel (with other stuff in the commit): bln (equals the 1st commit of BLN in my repo)
* changes for BLN to newer version: finally BLN V4 commit can be done
many thanks in advance for your help and collaboration !
edit:
the error message in question is:
make
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC arch/arm/mach-s5pv210/mach-aries.o
arch/arm/mach-s5pv210/mach-aries.c:1232: error: unknown field 'touchkey_sleep_onoff' specified in initializer
arch/arm/mach-s5pv210/mach-aries.c:1232: warning: initialization from incompatible pointer type
make[1]: *** [arch/arm/mach-s5pv210/mach-aries.o] Error 1
make: *** [arch/arm/mach-s5pv210] Error 2
Click to expand...
Click to collapse
which amazes me since with that stuff in led-notifications it compiles fine
I must be missing something obvious ... :\

Posted a fix in my thread, but Ill do it here too.
touchkey_sleep_onoff isn't declared in touchkey_platform_data, you have to add it. include/linux/input/cypress-touchkey.h is where the struct definition is.

I was working on this and got some issues Thanks Zach !

TheEscapist said:
Posted a fix in my thread, but Ill do it here too.
touchkey_sleep_onoff isn't declared in touchkey_platform_data, you have to add it. include/linux/input/cypress-touchkey.h is where the struct definition is.
Click to expand...
Click to collapse
ah - ok,
thanks TheEscapist !
strangely that struct afaik also isn't included in led-notifications but it compiles fine ...
I'll add it & see whether it works after that
Tk-Glitch said:
I was working on this and got some issues Thanks Zach !
Click to expand...
Click to collapse
sure
it's also easier that way:
you can explicitely turn it off (uses less battery)
and I can safe time by only needing to compile 1 kernel for a model

zacharias.maladroit said:
ah - ok,
thanks TheEscapist !
strangely that struct afaik also isn't included in led-notifications but it compiles fine ...
I'll add it & see whether it works after that.
Click to expand...
Click to collapse
That is strange, but it makes sense in terms of the error you are getting. It was also the only major difference I saw between my bln code, and your git.
Let me know if it works, I didn't compile test it.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
That is strange, but it makes sense in terms of the error you are getting. It was also the only major difference I saw between my bln code, and your git.
Let me know if it works, I didn't compile test it.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
it doesn't seem to work correctly
the buttons are constantly on once they are touched (screen on) and turned off once the screen is off
notifications don't seem to work (according to testers)
I can't test it personally so every testing is a little delayed
attached is the patch on top of the kernel-tree where previously all led-notification-related changes were reverted
hope you can suggest what might be wrong
Thanks once again !

zacharias.maladroit said:
it doesn't seem to work correctly
the buttons are constantly on once they are touched (screen on) and turned off once the screen is off
notifications don't seem to work (according to testers)
I can't test it personally so every testing is a little delayed
attached is the patch on top of the kernel-tree where previously all led-notification-related changes were reverted
hope you can suggest what might be wrong
Thanks once again !
Click to expand...
Click to collapse
Buttons always being on while screen is on us by design. Add a timer to turn it off if you wish, but I prefer lights always on.
As for notifications, did you push the correct liblights? Check with the bln app to make sure that you have both a compatible kernel, and a compatible liblights.
I can't check the patch right now, as I'm at work, but if its not fixed in ~4 hours, ill take a look at it when I get home.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
Buttons always being on while screen is on us by design. Add a timer to turn it off if you wish, but I prefer lights always on.
As for notifications, did you push the correct liblights? Check with the bln app to make sure that you have both a compatible kernel, and a compatible liblights.
I can't check the patch right now, as I'm at work, but if its not fixed in ~4 hours, ill take a look at it when I get home.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
yeah - I pushed a file named lights.s5pc110.so
but that apparently wasn't the correct / needed on :\
I just had the chance to get on a wifi network and download the BLN test app
and that clearly says that BLN is supported by the kernel but the liblights is NOT the correct one ...
I thought the one for JVH / samsung roms was the correct one (i9000_jvh_BacklightNotification_v3.0.1_update.zip)
but apparently it isn't ...
searching for the right one now ...
thanks !

zacharias.maladroit said:
yeah - I pushed a file named lights.s5pc110.so
but that apparently wasn't the correct / needed on :\
I just had the chance to get on a wifi network and download the BLN test app
and that clearly says that BLN is supported by the kernel but the liblights is NOT the correct one ...
I thought the one for JVH / samsung roms was the correct one (i9000_jvh_BacklightNotification_v3.0.1_update.zip)
but apparently it isn't ...
searching for the right one now ...
thanks !
Click to expand...
Click to collapse
Grab lights.aries.so from one of my kernel packages, its the correct one.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
Grab lights.aries.so from one of my kernel packages, its the correct one.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
ok, it works now
AWESOME !
Thanks a ton TheEscapist !

TheEscapist said:
Buttons always being on while screen is on us by design. Add a timer to turn it off if you wish, but I prefer lights always on.
Click to expand...
Click to collapse
Can this be done without touching the kernel source? It bothers me to no end that the touch keys stays on while the screen is on :/

quaff said:
Can this be done without touching the kernel source? It bothers me to no end that the touch keys stays on while the screen is on :/
Click to expand...
Click to collapse
I was planning on reworking bln to be more compatible with cm anyway, adding in a userspace interface to control a timer probably wouldn't be too much trouble.
You'd have to ask your dev to incorporate it into the source though.
Oh, and Zach? I had an idea, ill pm you when I get home in an hour.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
I was planning on reworking bln to be more compatible with cm anyway, adding in a userspace interface to control a timer probably wouldn't be too much trouble.
You'd have to ask your dev to incorporate it into the source though.
Oh, and Zach? I had an idea, ill pm you when I get home in an hour.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Hi TheEscapist,
thanks !
you got a PM
TheEscapist said:
That is strange, but it makes sense in terms of the error you are getting. It was also the only major difference I saw between my bln code, and your git.
Let me know if it works, I didn't compile test it.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
ok, just went through the led-notifications patch again
and it's included so I must have overlooked it

I can't get it to work at all. The app will "work" with it happily, but the function is broken. Same for my testers :/
My tries to port it before were ending the same way so that's not new but I don't understand how some guys can get it to work with this patch.
EDIT : When a notification comes, the LEDs won't light up, but if I touch the softkeys, then they will light up and stay on until I read the sms/mail etc. (It doesn't happen if I don't have a notification waiting).

[ROM][ALPHA III] ICS AOSP Build

QUICK UPDATE:
Installing chainfire3d and using their "nvidia shader driver" fixes alot of games e.g. Angry Birds! (thanks to scottcom who sent me the tip via pm!)
This is a very simple ICS build using the Andromadus repo + Google AOSP code (rather than CM). This is just a quick update because we got the hw accel hack working
WORKING:
HW Accel (hack version i.e. not natively)
WiFi (TAKES TIME TOTURN ON)
Data
Calls
Superuser
Full Keyboard/Orientation
Audio
Basic ICS
Bluetooth
NOT WORKING:
GPS
Full Accel
etc.
NOT TESTED:
SD Card
FM Radio
most things
DOWNLOADS:
ROMS:
ALPHA II (by crowstar)
http://www.multiupload.com/5KGQH76YZN
ALPHA III CM (by Flinny)
http://www.multiupload.com/GESOB7P3JA
KERNEL:
http://www.mediafire.com/?2xbjvc1bk71xokx (OdiemanSAM's THANKS!)
!NEW! GAPPS:
http://www.multiupload.com/RQTF41Z1I2
THANKS:
To all involved! (Flinny, Ionic, guy who's name begins with an s who I forget)
I'll update the OP in the morning, need to go to bed
HOW TO BUILD ICS FOR YOURSELF!
Code:
mkdir android
cd android
repo init -u git://github.com/Andromadus/android.git
repo sync
then you can:
Code:
. build/envsetup.sh
lunch
5
make -j[NUM OF CORES x2] otapackage

I'll probably flash this ROM as a DD when it has 3G or real HW acceleration working, whichever comes first GJ so far though, I'll probably give it a whirl to see how it is later tonight, compare it to the port maybe in terms of speed and such

First off, here's how I flashed:
1. Superwipe
2. Flashed Rom
3. Flashed Odie kernel
4. Flashed gapps
5. fixed permissions
It booted really fast and looks absolutely clean. I immediately connected to data, but not wifi - even though the connection is strong here. My data says 3G, but could be HSPA, and I jumped on the browser just to double check. It worked.
Things I noticed:
Scrolling is choppy, but I know that's easily fixed.
The market would not download (as expected), so I ran the fix via adb. When I tried Market again, it froze the phone and I had to do a battery pull.
The home button is not working so well. Takes 3-4 pushes to get it to work, it's easier to just to use the back button.
Didn't get a chance to look at much else after the phone froze.
I really appreciate you posting this up. I know you've been working hard and probably waiting for something that can be played with, and you got that here. Thanks again, I 'll post more impressions in a bit.

enserio said:
First off, here's how I flashed:
1. Superwipe
2. Flashed Rom
3. Flashed Odie kernel
4. Flashed gapps
5. fixed permissions
It booted really fast and looks absolutely clean. I immediately connected to data, but not wifi - even though the connection is strong here. My data says 3G, but could be HSPA, and I jumped on the browser just to double check. It worked.
Things I noticed:
Scrolling is choppy, but I know that's easily fixed.
The market would not download (as expected), so I ran the fix via adb. When I tried Market again, it froze the phone and I had to do a battery pull.
The home button is not working so well. Takes 3-4 pushes to get it to work, it's easier to just to use the back button.
Didn't get a chance to look at much else after the phone froze.
I really appreciate you posting this up. I know you've been working hard and probably waiting for something that can be played with, and you got that here. Thanks again, I 'll post more impressions in a bit.
Click to expand...
Click to collapse
I'd suggest installing setCPU or something similar to check those lockups, as there was a known(ish) issue in the port with Odie's kernel clocking too low (at 122 mhz) so if you could bump that up and also see what the upper end is? I'll probably do it myself eventually, and since I'm super lazy ill just pack the apks for titanium and setCPU into the app folder of the ROM itself and give it a whirl haha

My wifi works but the icon doesn't show up so its as if I have no connection. My home button is also bugged.
Edit: Also the gallery apo doesn't work and the messaging app seems to be missing
Sent from my HTC Vision using XDA App

Is the camera working in this build? Its the last fix I'm looking for before going back to ics xD

ohshootrawr said:
Is the camera working in this build? Its the last fix I'm looking for before going back to ics xD
Click to expand...
Click to collapse
no it doesn't, that requires a new kernel which will be updated in the DHD section very soon

crowstar said:
no it doesn't, that requires a new kernel which will be updated in the DHD section very soon
Click to expand...
Click to collapse
Wewt, good news at last! Thanks for the reply

Rom runs good for an alpha
- The Homebutton ( i know this is known ) but it seems like its reacting like a back buttons sometimes.
- I often get a red border when tapping next in a menu or install in the market.
- SDcard works but no mass storage on pc
Edit 2: the : and ; are not located at the fn button but at the shift button.
So far i already like this better then de Desire S port
Edit: I have no messaging app, anybody else who hasn't?
Edit 3: I tried buttonremapper to try and remap the home button but no luck

johrie said:
Rom runs good for an alpha
- The Homebutton ( i know this is known ) but it seems like its reacting like a back buttons sometimes.
- I often get a red border when tapping next in a menu or install in the market.
- SDcard works but no mass storage on pc
Edit 2: the : and ; are not located at the fn button but at the shift button.
So far i already like this better then de Desire S port
Edit: I have no messaging app, anybody else who hasn't?
Edit 3: I tried buttonremapper to try and remap the home button but no luck
Click to expand...
Click to collapse
Your home button was acting like a back button? Mine was just being unresponsive until about the third press. Interesting.
aside from that, did you notice if your handset got warm while running this rom? Mine did, and I forgot to mention it in my post.

Hey the key layout and keychar file have move_home wrong
Sent from my HTC Vision using XDA App

I ran this rom for about 45 mins and had two lockups where I had to battery pull, first was upon signing into google and it goes to the wifi screen...locked up...rebooted signed in fine and played around for a bit...yea no messaging app and then I noticed it syncd emails and upon c hecking gmail from the notification bar it locked up in gmail..I then restored to cm7...data worked though tmobile usa
Sent from my HTC Vision using XDA App

enserio said:
Your home button was acting like a back button? Mine was just being unresponsive until about the third press. Interesting.
aside from that, did you notice if your handset got warm while running this rom? Mine did, and I forgot to mention it in my post.
Click to expand...
Click to collapse
No not having problems with it being to warm. Running it now since my post and still no problems except the usuals.
And about the homebutton, it also looks app related. For example in whatsapp it just does nothing, but in the browser it reacts as a back button.
Seems like someone in the desire s port thread fixed the home button. But i found something new with the hw kayboard. Capital d doesn't work.
Sent from my HTC Vision using XDA App

What particular files fix the software keyboard, allow hardware keyboard to rotate it and manage the keyboard lights??? Thanks
Sent from my HTC Vision using XDA App

Headphones not working properly: (

xT4Z1N4TRx said:
What particular files fix the software keyboard, allow hardware keyboard to rotate it and manage the keyboard lights??? Thanks
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
the IDCs I think. But I'm not having these issues, try out some of the kernels by odiemanSAM. See which one works best

johrie said:
Headphones not working properly: (
Click to expand...
Click to collapse
That's to be expected. It's an alpha after all

bogdan5844 said:
That's to be expected. It's an alpha after all
Click to expand...
Click to collapse
I know but in Odies last kernel they worked perfectly.
Let me be more precise.
When i plug the headphones in they wil connect and work. Then i tried to skip a song and they dont work anymore and the phone speaker takes over.
Sent from my HTC Vision using XDA App

crowstar said:
This is a very simple ICS build using the Andromadus repo + Google AOSP code (rather than CM)...
Click to expand...
Click to collapse
Could you please write a short "how-to: compile ics for htc vision"?
I would like to build it on my machine but I don't know how...
Thank you!

g4rb4g3 said:
Could you please write a short "how-to: compile ics for htc vision"?
I would like to build it on my machine but I don't know how...
Thank you!
Click to expand...
Click to collapse
done! 10charcahrcahralsdfja;lsiht

[FIX][UPDATED 5/28/2012]VivoW AOSP Capacitive Buttons Backlight Fix

Hey everyone,
With some edits of cm9 source i managed to get softkeys backlight working.
I have only tested it on cm9 but it should work on MIUI and maybe AOKP.
Download: (Updated 5/28/2012)
attached to thread
Credits:
Aeroevan
Litetaker
Me
Thanks

Excited to test it out

alright attached fix to the thread. sorry it took so long as i felt that the button-light-doesn't-turn-off-after-screen-turns-off bug is pretty major and i cant release it until thats fixed.
well that took a lot longer than expected but i think its fixed. It might take up to 5+ seconds for the light to switch but if it take longer than that please tell me.
Thanks

kevdliu said:
alright attached fix to the thread. sorry it took so long as i felt that the button-light-doesn't-turn-off-after-screen-turns-off bug is pretty major and i cant release it until thats fixed.
well that took a lot longer than expected but i think its fixed. It might take up to 5+ seconds for the light to switch but if it take longer than that please tell me.
Thanks
Click to expand...
Click to collapse
Flash able or extract and run script? Thanks for this btw
Sent from my Amazon Kindle Fire using Tapatalk 2

jamminjon82 said:
Flash able or extract and run script? Thanks for this btw
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
just flash it in recovery

Confirmed to work on AOKP nice job!

kevdliu said:
Hey everyone,
After modifying a light script in Aeroevan's cm9 build I managed to get the buttons backlight semi-working (at least more working than before).
It should work on cm9, AOKP, CNA, and maybe MIUI.
Bugs:
- Sometimes there will be a few seconds lag between screen on/off and buttons backlight on/off
- (Fixed, I think. Need more testing) Sometimes the backlight won't turn off after screen is off. If that happens just turn the screen on and off again and that should fix it.
I based my editing on Aeroevan's script so credit goes to him.
This is just an initial fix and I will try to improve this later on.
Download:
attached to thread
Thanks
Click to expand...
Click to collapse
Great job, still needs some tweaking but its better than having to adjust the brightness all the time
Sent from my Incredible 2 using Tapatalk 2 Beta-5

kevdliu said:
Hey everyone,
After modifying a light script in Aeroevan's cm9 build I managed to get the buttons backlight semi-working (at least more working than before).
It should work on cm9, AOKP, CNA, and maybe MIUI.
Bugs:
- Sometimes there will be a few seconds lag between screen on/off and buttons backlight on/off
- (Fixed, I think. Need more testing) Sometimes the backlight won't turn off after screen is off. If that happens just turn the screen on and off again and that should fix it.
I based my editing on Aeroevan's script so credit goes to him.
This is just an initial fix and I will try to improve this later on.
Download:
attached to thread
Thanks
Click to expand...
Click to collapse
I didn't try the fix yet but I see that you are modifying the /sys/class/leds/button-backlight-landscape/brightness files. I was trying to come up with a script to do this a while back, but didn't know how. Now I see that this is how it is done! So, are scripts in /system/etc/ run continuously by the OS?

litetaker said:
I didn't try the fix yet but I see that you are modifying the /sys/class/leds/button-backlight-landscape/brightness files. I was trying to come up with a script to do this a while back, but didn't know how. Now I see that this is how it is done! So, are scripts in /system/etc/ run continuously by the OS?
Click to expand...
Click to collapse
probably not all scripts in /system/etc but rotating_lights.sh is ran by the system every few seconds.

ok so with help and suggestions from litetaker i updated the fix which should fix (how ironic ) the backlight staying on after screen is turned off problem. however there is still sometimes the few seconds lag

kevdliu said:
ok so with help and suggestions from litetaker i updated the fix which should fix (how ironic ) the backlight staying on after screen is turned off problem. however there is still sometimes the few seconds lag
Click to expand...
Click to collapse
Thanks for your work and the shout out! Actually seeing how you fixed the backlight thing with these scripts made me learn a lot about scripting... I am still very new to all of this. By the way, I think there is a slight error in your bklights0.sh script. The file has the following lines:
Code:
echo 0 > /sys/class/leds/button-backlight-portrait/brightness
echo 0 > /sys/class/leds/button-backlight-portrait/brightness
which should instead be:
Code:
echo 0 > /sys/class/leds/button-backlight-portrait/brightness
echo 0 > /sys/class/leds/button-backlight-landscape/brightness
Apart for that, this is A+ work!

Been running this fix on cm9 for a couple days now and haven't had any issues yet. Great work my man!
Sent from my Incredible 2 using Tapatalk

It's been working great for me aside from the buttons sometimes being lit when the screen is off. I am loving that I can actually see them now though

phillibl said:
It's been working great for me aside from the buttons sometimes being lit when the screen is off. I am loving that I can actually see them now though
Click to expand...
Click to collapse
even after the 5/2/2012 update?

kevdliu said:
even after the 5/2/2012 update?
Click to expand...
Click to collapse
I didn't know there was an update I'll try it in a few hours thanks

This might be off-topic, but in aeroevan's CM 7.2 he ported a fix for the rotating keys but apparently there are some issues with it. Would this fix that too?

ma70ent said:
This might be off-topic, but in aeroevan's CM 7.2 he ported a fix for the rotating keys but apparently there are some issues with it. Would this fix that too?
Click to expand...
Click to collapse
yes i think so
Sent from my Incredible 2 using Tapatalk 2

Confirmed. This fix worked for Aerovans new CM 7.2 ROM. Usually, when you switch from camera to video mode, the lights go out. After the fix, the buttons behaves as expected. Thank you kevdliu!
kevdliu said:
yes i think so
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse

findthisfunny said:
Confirmed. This fix worked for Aerovans new CM 7.2 ROM. Usually, when you switch from camera to video mode, the lights go out. After the fix, the buttons behaves as expected. Thank you kevdliu!
Click to expand...
Click to collapse
Another newbie question, if I'm running CM 7.2 RC1 (non-Aeroevan, just the official one) will this allow my keys to rotate? Basically, is this an actual edit of his Script/Code or a standalone script of its own?

Na, I don't believe that feature is in the official release and this is only a fix for that feature.
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
findthisfunny said:
Confirmed. This fix worked for Aerovans new CM 7.2 ROM. Usually, when you switch from camera to video mode, the lights go out. After the fix, the buttons behaves as expected. Thank you kevdliu!
Click to expand...
Click to collapse
How is that ROM after this fix?

Unresponsive lock screen

I have 2.3.4 and sense 2.1. Everything works fine except the lock screen is very unresponsive. I literally have to punch the screen with my finger a few times before it wakes up. I was wondering if the newer versions of sense fix the lock screen?

I have the same problem from time to time. Restarting my phone normally sorts it out.

I wish that was my answer but Its not. At least not for me.

Others have found this post useful and it seems it is similar to your issue. ;-)

I've tried that several times. Infact it helped me calibrate my touch screen after I broke the original. I've honestly had the same issue even with the original screen.

Cataulin said:
I have 2.3.4 and sense 2.1. Everything works fine except the lock screen is very unresponsive. I literally have to punch the screen with my finger a few times before it wakes up. I was wondering if the newer versions of sense fix the lock screen?
Click to expand...
Click to collapse
If you aren't adamant about Sense, you could try flashing a Sense-less ROM. In my experience, it improves much on performance.

When i bought my WildfireS i had the same problem , stock came with 2.3.3 . But when i updated to the official 2.3.5 problem solved. U Can try different rom also .
Sent from my Wildfire S using XDA

sorry for taking so long to get back to you guys.
I've got a VM Wildfire S thats CDMA and well.....None of the other roms seem to work. I;ve tried Wildchild but its not picking up my service. Simonsense3.5 seems to be okay but things like music crash every now and again. I do still have the unresponsive screen issue but its not as bad with simonsense. I do seem to have a deadzone on my screen for the I key. Specificly the I key. if I switch into that horrible swipe the screen does not track any inputs exactly on or bordering that specific letter. Anyway I can fix that?
Also what else should I be doing now that i've been able to get this phone in a better rom?

Set the minimum overclock limit in No frills to something lieke 245 Mhz or above until it solves.
It worked for me when I used sense roms.
Hope it helped..

Try editing your build.prop
With the touch responsive tweak.
It worked for me
Sent from my HTC_A510c using XDA

cpie20 said:
Try editing your build.prop
With the touch responsive tweak.
It worked for me
Sent from my HTC_A510c using XDA
Click to expand...
Click to collapse
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.

spit_fire said:
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
Click to expand...
Click to collapse
This worked for me.
#Helps Scrolling Responsiveness windowsmgr. .performance.tuning=1 Video.accelerate.hw=1
Sent from my HTC_A510c using XDA

spit_fire said:
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
Click to expand...
Click to collapse
Did you try turning off Settings -> Sound -> Quiet ring on pickup & Pocket mode & Flip for speaker?
As cpie20 also stated you can try doing the following to your build.prop to help speed things up.
CHANGE:
Code:
view.touch_slop = 2
ADD:
Code:
# Force Launcher into Memory
ro.HOME_APP_ADJ = 1
# Enable Graphic Processor Unit
debug.sf.hw = 1
# Improve Overall Touch Responsiveness
debug.performance.tuning = 1
video.accelerate.hw = 1
# Improve Scrolling Responsiveness
windowsmgr.max_events_per_sec = 150

Thanks for that. I did switch off the Sound settings as you mentioned earlier. Apart from that, I noticed that most of the tweaks were already present on the build.prop I'm currently running on. Just changed the following:
Code:
view.touch_slop = 2 [COLOR="Red"](Was 15)[/COLOR]
# Force Launcher into Memory
ro.HOME_APP_ADJ = 1 [COLOR="red"](Wasn't there)[/COLOR]
# Improve Scrolling Responsiveness
windowsmgr.max_events_per_sec = 150 [COLOR="red"](Was set on 120)[/COLOR]
So yeah, will see how that helps and report back later.
EDIT: Seems to work great upto now. The build.prop tweaks seem to have finally fixed it. Will report back if I head into any issues but seem quite unlikely.

help
Sorry but I didn't know where to add the other code
so I have to add them at the end ... or after the code:
view.touch_slop = 2
& with thanks and respect

[DEV][BETA-2.4] CyanogenMod 10.1 - A77R builds

Hi everybody!
You might already know me. I develop CM for the SGR. Here I give you my builds of CyanogenMod 10.1 (based on Android 4.2.1 Jelly Bean) for the Samsung Captivate Glide (SGH-I927).
As I do not own the device, I need some testers first to confirm! Do have a backup!
For general discussion and Q&A: head to this thread.
What works:
Mobile network (2G/3G switch and network selection as well)
Data connection
Data usage statistics
Audio
Wi-Fi
Wi-Fi Direct (P2P)
Bluetooth
Video player
Accelerometer, orientation, magnetic field, light, proximity, battery temperature sensors, gyroscope
BLN feature (you need either the free or the paid version of BLN Control from Play Store)
Auto brightness
USB On-The-Go
Moving apps to SD card
Camera (single and panorama pictures)
Video recording (480p SD and 720p HD as well)
Full HW acceleration with Nvidia and Samsung codecs
Wireless tethering
Keyboard rotation and key fixes (thx thegreatergood)
What doesn't work:
USB Mass Storage only works manually
Stock sound recorder app (use an external, like MIUI Sound Recorder instead)
Maybe bluetooth A2DP (I couldn't test)
Maybe bluetooth tethering (I couldn't test)
A more detailed bug list and possible solutions can be found here. There may be other bugs, feel free to report them.
Link: Not available.
Get Google apps here: http://goo.im/gapps/gapps-jb-20121212-signed.zip
Installation method:
Flash CM.
Flash this kernel to fix vibration issue.
Flash Google apps. (It is not optional anymore!)
Do 'Wipe data/factory reset' in recovery.
Reboot & enjoy.
Every custom modification to devices have risks. Flash this at your own risk!
Have fun and enjoy!

Thread cleaned
The bickering ends now. There is room for creativity from many members. Continuation of the deleted discussion will result in an infraction against the user's account.

Thanks MOD. Love ur presence here.
Sent from my GT-I9103 using Tapatalk 2

don't know what happend but if staring from scratch why not building 4.2.1 instead?

He has to understand your device first, once it is stable he will release for 10.1... He already release for Galaxy R and it is Beta...
So don't worry guys, Please download, test and provide the logcat for him... he will fix as earliest..

I noticed that the bugs from dman's build aren't the same ones listed. Does that mean the keyboard works now?
Sent from my myTouch_4G_Slide using Tapatalk 2

gtmaster303 said:
I noticed that the bugs from dman's build aren't the same ones listed. Does that mean the keyboard works now?
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
He doesn't have the phone that's why we he wants us to test it

i cannot install it. cwmr says: installation aborted.. I thought it might be a result of a bad downloading, so I downloaded it again, but the result is the same

soadzoor said:
i cannot install it. cwmr says: installation aborted.. I thought it might be a result of a bad downloading, so I downloaded it again, but the result is the same
Click to expand...
Click to collapse
Does it say anything more?

well, I made a picture of it, dont know if it makes anything clear..

this is error

This is assertion error. Just wondering if dman has opened all of his zips and removed these lines. Will post a new zip tomorrow with the assertion check removed then will examine your CWM builds.

Adam77Root said:
This is assertion error. Just wondering if dman has opened all of his zips and removed these lines. Will post a new zip tomorrow with the assertion check removed then will examine your CWM builds.
Click to expand...
Click to collapse
so i have a paper weight until tomorrow

smutta said:
so i have a paper weight until tomorrow
Click to expand...
Click to collapse
Should be able to mount USB and transfer a working ROM to the phone for flashing.

smutta said:
so i have a paper weight until tomorrow
Click to expand...
Click to collapse
Dude you chose to test this, he clearly said to make a backup so,

Adam77Root said:
This is assertion error. Just wondering if dman has opened all of his zips and removed these lines. Will post a new zip tomorrow with the assertion check removed then will examine your CWM builds.
Click to expand...
Click to collapse
Should be assert i927, SGH-I927, SGH-I927R, SGHI927,SGHI927R, n1. That's what all my updaters run....
Sent from my SGH-I927 using xda premium

And this will fix keyboard lights in lights.c
char const*const BUTTON_FILE="/sys/class/sec/sec_stempe_bl/backlight"
But you probably already knew that..
Sent from my SGH-I927 using xda premium

dman3285 said:
And this will fix keyboard lights in lights.c
char const*const BUTTON_FILE="/sys/class/sec/sec_stempe_bl/backlight"
But you probably already knew that..
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Thanks !!!

dman3285 said:
And this will fix keyboard lights in lights.c
char const*const BUTTON_FILE="/sys/class/sec/sec_stempe_bl/backlight"
But you probably already knew that..
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I end up getting char: not found...

Has anyone else noticed that the Home button doesn't actually function as a home button (the capacitive button, not the keyboard one.)
Installed by edited installer script.