yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] kecinzer:
That's absolutely nonsense.

UV can't affect signal strength.

If someone bring some evidence (like screenshots of monitoring signal strength) I don't believe it.

I'm on same place like with stock ROM - full signal on 2G and manualy set 2G, so the drain must be caused something else.
[Nexus S Android Development] steve.garon:
Don't use signal bar to determine if you have more or less signal. Use signal db..
[Nexus S Android Development] imperfection:
I'm looking at the previous versions because I'm on 2.3.3 with CM 7.0.3, and I'm just wondering if 1.1 is the only compatible version? It looks like it based on the file names, but I just want to double check.
[Nexus S Android Development] kecinzer:
When we can expect new version with BLD and touch wake fixes?
[Nexus S Android Development] reddv1:
None are compatible with 2.3.3, sorry. Just 2.3.4 and 2.3.5.
[Nexus S Android Development] reddv1:
Today hopefully :)
[Nexus S Android Development] rejanmanis:
how do u know i have weak signal on my room :confused:

r u sure stock voltage will save more battery ?

hmm... let me try and will let u know :D

oh yeah... 1 more thing,

i played together with 3 Gs, iphone 3 Gs load faster than mine, in 2 games GT Racing HD and Tom Clancy Rainbow Six

Do u think my ROM slow or the kernel ? im using MIUI 1.8.26 ? cannot OC since ur kernel runnin stock. i use Lucid 2.0.6 1100mhz.

How come 600mhz beats me ? What do u think ?
[Nexus S Android Development] kecinzer:
reddv1:

Thanks.

I found another thing. BLD is enabled by default. So if I recieve mail, my soft keys lighting.

I'm use to it control this feature by BLN control - Pro, and without this app keys have to be stay off. How can I do that?
[Nexus S Android Development] khartaras:
Just a question.

Do the colors affect the SCLCD version? Or just the AMOLED?
[Nexus S Android Development] zadnica:
Just for AMOLED
[Nexus S Android Development] rejanmanis:
yup just for amoled.

AMOLED uses RED GREEN BLUE bases colors.

absolutely.
[Nexus S Android Development] Igotsanevo4g:
^every display uses red green blue. Maybe a yellow on some hdtvs.

Its just LCDs aren't adjustable.
[Nexus S Android Development] reddv1:
Version 2.0

Update Kernel to version 2.0.

Changlog:

-Touch Wake proximity sensor bugfix

-BLD bugfix, fixed i9023 touchkeys not relighting up bug (please confirm, can't test)

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

New Lucid Experimental 2.0.11: http://goo.gl/PcuAo

-Lucid Blue

-1.1Ghz

-BLD enabled, 30 seconds

-Touch Wake enabled, 30 seconds

-SD card read ahead increased to 1024

-2.0 bugfixes
[Nexus S Android Development] Udaw:
My rom is 2.3.4 stock, Nexus 9020T - gsm.

After flashing version 2.0y instead of 1.8y, wifi have not work. When trying to turn it on, it writes error.

Return back to 1.8y - wifi works properly.
[Nexus S Android Development] :
I got this error very often when I flash a new kernel. You may flash it again, make a reboot, then reboot in recovery and wipe cache and dalvik cache. Should help...
[Nexus S Android Development] reddv1:
Fixed the Wifi on Lucid Nexus 2.0y stock NSGSM and NS4G.
[Nexus S Android Development] Udaw:
Thank you!

I can confirm, now everything is ok!
[Nexus S Android Development] isollo:
Love you work, could you make version for 2.3.6 stock
[Nexus S Android Development] dario3040:
I think all 2.3.4 and 2.3.5 kernels work on 2.3.6, it doesn't hurt to try, after all it there were just a few bug fixes, it should work.
[Nexus S Android Development] reapsor:
Now BLD is working perfectly on my i9023, thank you :)
[Nexus S Android Development] oleerik:
Touch keys still not relighting on i9023 on 2.0y:/

At the same time Id like to thank you for this awesome kernel.
[Nexus S Android Development] reapsor:
right, i've also noticed that relighting doesn't work :(
[Nexus S Android Development] Igotsanevo4g:
May I ask why you guys use the yellow version?
[Nexus S Android Development] reapsor:
I use the blue version, had never flashed the yellow one.
[Nexus S Android Development] Ezekeel:
Dammit!

1. Are the backlights re-enabled when you wake the device from lock?

2. Can you prevent the backlights from switching off by continuously pressing the touchkeys?

3. Disable Screen Dimmer and Touch Wake and only leave BLD enabled. Does this change anything?

4. With Touch Wake, can you wake the device from lock by pressing the touchkey (not touchscreen)?
[Nexus S Android Development] oleerik:
1. Yes, they are :)

2. No. I have tried all of the touchkeys, no matter which one I continously press the backlight is turned off.

3. Done. No change. I, in fact, never used Screen Dimmer or Touch Wake.

4. Not using touch wake.
[Nexus S Android Development] kecinzer:
Ezekeel:

1. YES

2. NO

3. NO - tested only BLD

4. not tested
[Nexus S Android Development] reapsor:
1. Yes

2. No

3. No (i have touch wake and screen dimmer disabled on my device, I don't use these features)

4. not tested
[Nexus S Android Development] Ezekeel:
Great. Thanks for your help.

Seems like on the i9023 a touchkey press is not properly recognized. Can you please try enabling Touch Wake and see if you can wake the device by touchkey press. If that also does not work, this would confirm that the problem is with the recognition of touchkey presses.
[Nexus S Android Development] kecinzer:
It seems, that Touch Wake not work at all.

When I put device into sleep (by power button), I can't wake up it by touch screen or keys.
[Nexus S Android Development] Ezekeel:
You have to wait for the screen to time out by itself. If you press the power button to lock, touch controls will be disabled right away.
[Nexus S Android Development] kecinzer:
No, even if I let phone turn off, then touch don't work.

Touch wake is set to 60 second, screen timeout is 15 second. Not working.

Can someone else with i9023 confirm this?
[Nexus S Android Development] oleerik:
I can awaken the device with touchkeys. The problem is that I have to press them two times before it works.
[Nexus S Android Development] chubb16:
Setting the voltage back to stock definitely increases the signal strength on this phone.
[Nexus S Android Development] kecinzer:
Ok, with Trinity TUV10 touch wake working well. I can wake device by touching screen or soft keys.
[Nexus S Android Development] Ezekeel:
Since I do not have a i9023 and cannot test it systematically, I can only guess what the problem might be.

This patch is my best guess: http://www.pastie.org/2482282

That is strange. With Trinity BLD is still not working correctly?
[Nexus S Android Development] chubb16:
Latest kernel is no good. I kept dim screen rebooting and just locking up and crashing whenever a text message came in. I am on the experimental 1.1ghz kernel thatyou posted a few pages back now with the stock voltages. So far so good. I like the stock voltages the phone isn't jumping the data connection around so much and the reception is a little better. Coverage is spotty and the extra voltage makes a difference.
[Nexus S Android Development] reddv1:
Can you guys test BLD on i9023, here's lucid blue with Ezekeel's latest patch

http://www.mediafire.com/?7t0b0l0052glx4c, Thank
[Nexus S Android Development] reapsor:
Is that patched version for cm7 only? cause i'm running the stock 2.3.4 rom.
[Nexus S Android Development] reddv1:
If you'reconing from a previous lucid kernel you can flash it on stock.

Sent from my Nexus S
[Nexus S Android Development] reapsor:
Great, i'm gonna try it later today.

reporting back if it works or not

Sent from my Nexus S
[Nexus S Android Development] opalhair:
I flash it on CM7,OpenVPN not work for me.
[Nexus S Android Development] kecinzer:
No, still not.

Tried latest Lucid test and still not working.
[Nexus S Android Development] oleerik:
Still no relighting backlights :(
[Nexus S Android Development] reapsor:
just flashed the new one but there are no changes, the reported problems with bld relighting still exist.

But anyways, not a real problem for me, i like that the touchkey backlight stays off the whole time.

as long as I use my device.

Sent from my Nexus S
[Nexus S Android Development] kecinzer:
I think, that will be neseccary to monitor each of soft keys, not all together. i9023 may have some cripled interface :))
[Nexus S Android Development] oleerik:
I agree. It is not a deal-breaker for me at all. I love that they turn off. Hate watching videoes in fullscreen and have those darn touchkeys lightened.

But, it would be nice if these awesome devs found an solution.

Please let me know if I can get any information of any sort from my device that would be of help, devs.
[Nexus S Android Development] Ezekeel:
Seems like the i9023 does not handle a touchkey press as a keypress (like the i9020 does), but instead simply reports them as a touchscreen input which the Android OS then interprets as a virtual key press.

So I change the implementation how touchkey presses are detected. This might need some fine tuning, but should do the trick.

Test patch (needs the code cleanup patch I released a few minutes ago): http://www.pastie.org/2488786
[Nexus S Android Development] oleerik:
Is it possible for me to apply this patch on my own? :D
[Nexus S Android Development] kecinzer:
I'm compiling analphabet, so waiting for latest Lucid test kernel :)
[Nexus S Android Development] reddv1:
I was going to wait till tomorrow, but I'll work on it just to be nice. Give me 30 minutes to an hour.

Sent from my Nexus S
[Nexus S Android Development] oleerik:
Awesome! Is there any way to donate to you for your great work?
[Nexus S Android Development] reddv1:
Here's the Lucid Blue test kernel for i9023 bld with the latest patches, hope it finally works. http://www.mediafire.com/file/0sllzjmqic00bj2/Lucid-nexus-2.1b-test-cm7-NS-2.3.5.zip

If you're flashing on a stock rom, make sure you're coming from a previous Lucid kernel.
[Nexus S Android Development] kecinzer:
Yeeeeehaaaa :). Now it works like a charm.

Super Trooper :D.

I get drunk tonight :DDD
[Nexus S Android Development] oleerik:
Working perfectly :-D
[Nexus S Android Development] fordmanck:
Anyone have issues on the NS4G not being able to UV? Every time I try to set my voltages with Proton it reboots immediately, otherwise I love this kernel. Aside from that I haven't had one random reboot and the battery life is incredible.
[Nexus S Android Development] Ezekeel:
Glad to hear that BLD is finally working on the i9023.

About the fine tuning I was talking about:

The i9020 has an array of physical touchkeys below the touchscreen. The i9023 on the other hand only has an array of simple LEDs and the digitizer (the thingy that records the touches) used for the touchscreen is extended to cover the touchkeys. The Android OS then interprets a digitizer input at the touchkey position as a virtual key press.

The way I implemented the detection of touchkey presses is that every digitizer input with a y-coordinate above 800 (0 is top of touchscreen) counts as a touchkey press. I guesstimated this value (center of virtual keys is located around 840) and it might need some fine tuning.

Thus, can you please test (by moving your finger from top down to the touchkeys) if the buttons light up a little too soon or too late.
[Nexus S Android Development] kenvan19:
Spoke too soon, seems I've lost wifi with another custom kernel on MIUI. Back to stock kernel.
[Nexus S Android Development] oleerik:
Way too soon :) I get my finger about 1cm away from the touchkeys when the touchkeys lighting u p.
[Nexus S Android Development] kecinzer:
I mentioned yesterday, that touchkeys sometimes wakes on screen press. Now I know, that I touched screen too bottom :).

But I don't care. It works well and I'm satisfied.
[Nexus S Android Development] reddv1:
I'm going to update the kernel soon and I'll include a fix for that too.

Sent from my Nexus S
[Nexus S Android Development] kecinzer:
endursa:

Good morning :)).

If you use Lucid 2.0, then you don't have latest fix in it, so BLD don't work properly on i9023.
[Nexus S Android Development] endursa:
oh :D i thought it should be fixed cause of the changelog!

just saw in the touch wake thread, that the problem was fixed only 4hours ago :D i hope lucid will release an update asap :) cause i love that feature!
[Nexus S Android Development] reddv1:
Version 2.1

Updated kernel to version 2.1,

-Fixed the problem of the touch controls misbehaving after the proximity sensor has blanked the screen during a call.

-Touch Wake time out changed from 45 seconds to 30 seconds.

-BLD: i9023, fix (this time for real) the touchkey backlights not being re-enabled on touchkey press

-BLD, SLD & TW: Code clean-up

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

New Lucid Experimental 2.1.11: http://goo.gl/idvJQ

-Lucid Blue

-1.1Ghz

-BLD enabled, 30 seconds

-Touch Wake enabled, 30 seconds

-SD card read ahead increased to 1024

-2.1 bugfixes
[Nexus S Android Development] nbeebe24:
Hey, I was wondering if you know of an alternate link to the Nexus S kernel source? git://android.git.kernel.org/kernel/samsung.git <------This link does not currently work
[Nexus S Android Development] reddv1:
Here's a clone of the Nexus S kernel source from my github, it's updated up to android 2.3.5. git://github.com/reddv1/nexus-s-source.git

Sent from my Nexus S
[Nexus S Android Development] nbeebe24:
Thank you very much sir
[Nexus S Android Development] Jibreil:
v2.1b works perfect on Brainmaster's MIUI. Smooth gaming with Angry Birds ;-)
[Nexus S Android Development] endursa:
Running 2.1 now on miui stock 1.9.9 runs perfectly so :-), bl dimmer works, the other two mods are disabled!

Sent from my Google Nexus S
[Nexus S Android Development] endursa:
Ok my system just froze on playing roboto :-( too bad, i guess back to 1ghz, my nexus just can't handle the 220 mhz bus speed...

Sent from my Google Nexus S
[Nexus S Android Development] axllent:
OpenVPN

I was wondering if you guys wouldn't mind adding the openvpn tun.ko module to the builds

please

? Thanks!
[Nexus S Android Development] endursa:
i just looked inside the zip file, the tun.ko file is included already
[Nexus S Android Development] reddv1:
It is? I didn't put it there.

Sent from my Nexus S
[Nexus S Android Development] axllent:
Could/would you please? It would be extremely handy to have, thanks!
[Nexus S Android Development] endursa:
damn my fault :D i thought is was in the wrong thread, i looked into the Trinitiy kernel zip file :( my bad!
[Nexus S Android Development] no_one_can:
When my screen is trun off, no any notification, and I press one of the softkey. The backlit will be turn on. Is this related to the BLD? I did not enable it and I think the default is disable.
[Nexus S Android Development] reddv1:
Try disabling than enabling BLN and see if that fixes the problem.

Sent from my Nexus S
[Nexus S Android Development] 5noc:
For some reason BLN only flashes 2 times and then turns off even in the settings it's set to flash until I wake up the phone. 1 sec. lit up, 500 ms. lit off and unlimited repeats.

I have all the other mods disabled and enabled BLN via Control BLN - Pro :confused:
[Nexus S Android Development] reddv1:
Do you have any task killers installed, that could be the reason. If not try disabling and enabling and rebooting.

Sent from my Nexus S
[Nexus S Android Development] 5noc:
Didn't work, I'm using MIUI 1.9.23 though it's been having this weird behaviour since a few versions ago :(
[Nexus S Android Development] madd0g:
A small question from a NS n00b. Got a i9023, running GRJ22 and KD1 radio. On SGS, you can flash custom kernel's to a Samsung stock ROM. How is it here ?

I unlocked the NS, installed CWM and rooted it (SU installed). I don't need anything extra from a custom ROM, just BLN and Voodoo sound. Is it possible to flash this (or any other custom) kernel, to use with the Google's stock ROM ?
[Nexus S Android Development] reddv1:
Yeah you can flash custom kernels on stock rom, you don't even have to be rooted.

Sent from my Nexus S
[Nexus S Android Development] mindwalkr:
Just installed this kernel. Giving it a spin since NetArchy 1.3.7 (first one I tried) was giving me jitter and stutter on recorded videos.

So far so good but only running it for the past 10 mins :)

I'm just curious though... you mention that this kernel runs at 1 Ghz and to not use SetCpu neither profiles. I checked the /sys partition using adb shell and found in /sys/devices/system/cpu/cpu0/cpufreq/ all that stuff about governors and clock frequencies and such.

Is there a technical reason why we shouldn't use SetCpu on this kernel ? As far as I understood it's using On Demand governor, max 1 ghz, min 100 Mhz.. this could be changed or not ?

Also when firing up Proton, it's not reading the voltages properly. But that's a very small detail. It's taking the 4 clock / voltage slots in the file and assigning them to the wrong frequencies in Proton. SetCpu loads them correctly though.
[Nexus S Android Development] reddv1:
It can be changed, but from users experience ondemand is the best governor for hummingbird CPU and setting min freq to more than 100 makes no sense to me. You can underclock to 800 to save battery but you might have performance issues. I guess you can use profiles but I think it runs as a background and it shouldn't be set under 800 because of waking up issues.

As for proton, press the suggested voltage button and only change the values of the five on the right, see if that works.

Sent from my Nexus S
[Nexus S Android Development] jorking:
Thanks for the great kernel. It's the best kernel for me so far, battery saving and stable(I use MIUI on my i9023).

Any update these days?

I saw some new ideas in this forum, such as Lazy governor, live oc, etc.
[Nexus S Android Development] reddv1:
Soon, I'm out of town now so that's the reason for the lack of updates.

Can you link me to the features you want such as live oc and others, the search on the xda app sucks.

Sent from my Nexus S
[Nexus S Android Development] IT4ALii3EN:
Hello,

It works in Android 2.3.7 Oxygen 2.3 NS I9023 ?!

Thx for your job :) ! +1
[Nexus S Android Development] M86:
surround sound?

Hey, awhile back I ran CM7 (2.3.3) on my nexus and whenever I used the bass amplifier with the "equalizer" app in the market, it made it feel as though I was in a movie room. I mean it was surround sound!

I've upgraded to MIUI and unfortunately I don't get that same sound output. The bass sounds sound smooth, rather it sounds like someone is banging the music playing.

I was wondering if there's anyway besides going back to CM7 and 2.3.3. that I could get that surround sound feeling back.

Thanks in advance
[Nexus S Android Development] jorking:
Live OC:

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

Lazy governor:

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

Thanks in advance. I am not sure if they are stable features or not, just in case.
[Nexus S Android Development] life2monkeys:
Hello,

Ive been trying to install this with the latest stable CM7 using the link in the OP for the CM version of lucid blue, and it can't seem to get past the "Google" screen both times that I've tried it. Any suggestions?

Many thanks!!
[Nexus S Android Development] reddv1:
I'm using it with cm7 and it's working fine, try deleting everything in the modules folder and unit.d folder then flash it.

Sent from my Nexus S
[Nexus S Android Development] jottosson:
Does lucid work with the latest oxygen rom? It says it's based on 2.3.7...
[Nexus S Android Development] IT4ALii3EN:
I asked to a french.

-> The kernels based for 2.3.4 & 2.3.5 are compatibily to 2.3.6 & 2.3.7 !

So, LucidKernel 2.1 is compatible with the lasted oxygen :)...

But, I wait reddv1 in order to be sure.
[Nexus S Android Development] reddv1:
Its compatible with 2.3.7, I'm using it right now on a 2.3.7 rom.

I wish I could update the kernel source to 2.3.7 but kernel.org is down so there's no way I can.

Sent from my Nexus S
[Nexus S Android Development] IT4ALii3EN:
Ok.

But, do you think that your future kernel will be based on 2.6.35.13 or 2.6.35.14 ?? And, so, All options will work -> BLN , BLD , ... ?
[Nexus S Android Development] reddv1:
No, I'm going to stick to 2.6.35.7. Google must have some reason for staying on that kernel version and I'm going for stability and reliability.

As for BLN, BLD and other mods they all work perfectly, if you want other mods included please suggest them. I'll update touchwake soon and I'm thinking of adding lazy governor.

Sent from my Nexus S
[Nexus S Android Development] IT4ALii3EN:
Ok :) ! Cool.

So, I think to put all work of Ezekeel will be a good idea ;) !

BLN / BLD / BLX / all the governor / etc.

And if possible, to add 1.44Ghz in max ... may be.

and update the source 2.3.7 on the kernel. Maybe update in LucidKernel 2.2...
[Nexus S Android Development] jottosson:
Flashed yellow universal and confirmed, thanks!
[Nexus S Android Development] oldblue910:
Very nice to see a kernel that supports pre-2.3.3 color drivers.
[Nexus S Android Development] Igotsanevo4g:
Any plans to update? I really enjoyed the colors and stability.
[Nexus S Android Development] kevlars9:
Yes wandering this as well
[Nexus S Android Development] reddv1:
Working on update, I'll post it later tonight.

Sent from my Nexus S
[Nexus S Android Development] reddv1:
2.2 update

Update kernel to 2.2

Changlog:

2.2

-Removed Screen Dimmer

-Raised FPS to 65

-Raised SDcard read-ahead to 1024

-Bugfixes for BLD and Touch Wake

-Fixed BLD for i9023 bottom screen calibration

-Added Lazy Governor

-TUN support

Lucid Nexus 2.3 Blue eXXperimental:

Blue: http://goo.gl/wpmgn

Yellow: http://goo.gl/rAzwe

-Everything in 2.2

-Deep Idle added and enabled by default

-BLD enabled at 30 seconds

-Touch Wake enabled at 30 seconds

-Runs at 1144Mhz
[Nexus S Android Development] IT4ALii3EN:
THANKS ! Big thx :D.

This is a good idea.

So, this kernel test in priority the mode DeepIdle & 1,14GHz.. I test.
[Nexus S Android Development] oldblue910:
2.2 blue seems to be working great on CM 7.1.0.1 for I9020T.
[Nexus S Android Development] lshking:
Used v2.1 for a long period of time. it's worked fine.

Updated to v2.3, screen off couldn't wake up also happened.

So back to v2.2, try again.
[Nexus S Android Development] reddv1:
I've gotten a couple of freezes on 2.3 too, I need to lower the speed a little cause I don't want to raise the voltage for battery life.

Sent from my Nexus S
[Nexus S Android Development] dman777:
Awesome kernels. Touchwake works great.

Can you add deepidle option to them?
[Nexus S Android Development] reddv1:
Yeah, I'll add it in soon.

Sent from my Nexus S
[Nexus S Android Development] lvnatic:
Does the kernel have the 100% charge tweak from latest nightlies?
[Nexus S Android Development] reddv1:
Nope, sorry. It doesn't really charge it to 100% so what's the point. Unless I'm missing something.

Sent from my Nexus S
[Nexus S Android Development] IT4ALii3EN:
* I installed the LucidKernel 2.3y and i had 2 freezes.

[When I use my phone with a lot of applications open, there is a big freeze, so I must do a hard reset or the phone reboot himself].

* The battery is at 25% while with the 2.1y, I was at 45% - 55%.. [But I listen to music 1h30 since the morning]. [Sound drivers of Supercurio work all the time, and not just when music is launching!!]

I keep the 2.3y for several tests.
[Nexus S Android Development] lvnatic:
The 1st post has a download link for 2.3.5 android versions, so does the kernel support 2.3.7 versions as well?
[Nexus S Android Development] IT4ALii3EN:
All kernels in 2.3.4 & 2.3.5 work in 2.3.6 & 2.3.7 :)

For the kernel 2.3y, there are any freezes when the battery is ~15% ! If you lock = freeze.

So, retourn in 2.2y. I think that the problem come with deep-idle! But the O/C in 1140Mhz is a good idea. The reactivity of the phone is better.
[Nexus S Android Development] lvnatic:
Thanks. Can interactive governer be included pls? I heard its the stock governer on some phones and it is even recommended by buglesspete, which's ROM is very AOSP-like and stable. I used interactive since quite some time and the phone felt very well.
[Nexus S Android Development] reddv1:
I'll include it in the next release.

Sent from my Nexus S
[Nexus S Android Development] lvnatic:
thank you for the quick reply!