yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Zeljko1234:
Yes, current widget works with snq- kernel, problem is with gingercakes kernel.
[Desire Android Development] t-minik:
and UV seems to works well to :

GREAT WORK
[Desire Android Development] adogterom:
it looks like wifi doesn't auto reconnect anymore. i reflashed the kernel from 11-09 and that one does auto reconnect.
[Desire Android Development] ZeGuitarist:
I just checked, it does.
[Desire Android Development] adogterom:
might be the the type of encryption used? mine uses wpa2/psk
[Desire Android Development] ZeGuitarist:
Same here. ;)
[Desire Android Development] sjknight413:
Can't get it to boot on cool3d aceS.

Gets stuck on the first white HTC splash screen
[Desire Android Development] adogterom:
might be a leedroid thing then, for i'll stay at the 11-09 kernel.

it almost seems like an addiction of mine always wanting to flash the newest thing :)
[Desire Android Development] angusc:
I just flashed it to Coolexe 3d ace v1 all seems to be ok for now....did you wrote cache and delvik?

Sent with Desire.
[Desire Android Development] STONEMC:
The same here, but with the Reflex ROM. Wiped cache and davlik cache but stuck at the splashscreen.

Any ideas or solutions for this? Want to use tis kernel
[Desire Android Development] Muxeu:
Woks for me cool3d aceS on v1/2a. Wipe cache/dalvik not needed
[Desire Android Development] fragargon:
hi,

works fine on leedroid hd port, no wipe nedded

I switched to smartassV2 using OS monitor - rom scaling freq

thanks to all great job.
[Desire Android Development] Tendou:
Using CM7 latest nightly sep 01, flashed this kernel.

In camera, the preview screen is white no matter what. but still able to take pictures.

FM Radio does not work (Cannot enable bluetooth module).

Drain is about 80mA with 3G on.
[Desire Android Development] ny73r1d3r:
Err...this is a SENSE KERNEL, not AOSP/CM one, meaning it is never meant to be used in CM7.
[Desire Android Development] Tendou:
I'm sorry I promise I will not make that mistake again.

But I reflashed with gingercakes 0.5, wiped cache, wiped dalvik cache, and the problem is still there.
[Desire Android Development] ZeGuitarist:
So you just made that mistake again. -_-'

This kernel will not work with the ROM you're using. CM7 is an AOSP ROM. Use an AOSP kernel.
[Desire Android Development] STONEMC:
Can someone help me with this kernel in my Reflex Rom? I still gut stuck on splashscreen
[Desire Android Development] AndyBury:
Gingercakes 0.5 is a "Sence" rom too

Thats just to funny..
[Desire Android Development] Tendou:
Oh my god you're right, I'm blind, I just slapped myself a few times, I hope that serves as punishment.
[Desire Android Development] NeoEpsilon:
@snq-

Just want to confirm one thing...

Will this kernel boot @998Mhz or @1190Mhz..?

It is locked at 998Mhz when booting in v02, correct..?

How about the latest one..? :D
[Desire Android Development] snq-:
all releases including the last one are locked to 998 while booting
[Desire Android Development] teorouge:
Really thanks for all the recent efforts. Any chance we'll ever see a wifi N patch (something like this one by Myshkinbob)?
[Desire Android Development] schalmers:
Hi SNQ,

I see you have released an updated kernel for Badnew's IC Rom, any chance you can provide a flashable Zip so that we can use your kernel in other Roms? I tried your build from 1109 (on SGBS v2.7) but unfortunately I was getting freezes linked to the low voltage that I read you have corrected in the last release.

Thanks for all of your excellent work

EDIT: I found the link to your new kernel form today: (From IC download page)

http://dl.dropbox.com/u/13432479/bra...snq-110915.zip
[Desire Android Development] Andreas75k:
Something happened to your link, here it is in it's complete form.

bravo-2.6.35.14-snq-110915.zip

Here is where I found that link:

http://insertcoin-roms.org/archives/category/desire
[Desire Android Development] basher52:
It is possible to get an high OC Version with 1,3GHz? 1,152 ist rather too low for me :D
[Desire Android Development] t-minik:
1.3GHz ... do you fry eggs with your phone ? :D
[Desire Android Development] PlayPetepp:
No need for a bbq with that oc :)
[Desire Android Development] schalmers:
Just to mention I tested SNQ's latest kernel dated 110915 and unfortunately I still had my device freeze up and require a battery pull this morning while listening to music. I use sgbs_v27_oxy with setcpu no over clocking. Smartass v2 as governor.

Not sure if anyone else has had issues with this latest kernel?
[Desire Android Development] basher52:
Refering to this (old) topic, our desire can handle such OC.

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

I noticed that OC is going down since some month, from 1267MHz ( i used that, was stable for me), to 1113 MHz now.

Sometimes. ;)
[Desire Android Development] pavel54:
It would be very nice to break 1.2ghz for me too, ofc if it's possible huh :D

I'm using 1190mhz when charging as profile in setcpu ;)
[Desire Android Development] andQlimax:
now i understand why phone manufactures give so much attention to the cpu power and not to the battery life...because of the people like you guys! arghh :D

of course i want a fast phone, but reach 1 full day with very intense use is still a dream :(
[Desire Android Development] pavel54:
Exactly, unfortunately but it is a problem that can't be eliminated so and so we must love charging :D so why not get overclock :D

on my computer core 2 duo is running at 4ghz 1.24v, interesting when phones will reach for example 2 - 2.5ghz and with how battery life it will be :eek:
[Desire Android Development] ziggy1001:
CPU technology has improved radically, compare the Desire 1 GHz CPU to a Pentium 3 1Ghz processor of 10 years ago, batteries on the other hand given the tiny phones we use have extremely limited V and mA capacity

On my phone just going from 1152-1190 improves things:)
[Desire Android Development] basher52:
Which Kernel do you use? Iam atm on Miui 1.9.2 with Kernel 2.6.37.6-cyanogenmod-01494-g8dc02ffandroid@giulo-desktop # 19

Im looking forward flashing another kernel to get atleast 1190 MHz, 1113 is tooo slow...
[Desire Android Development] ziggy1001:
Well this is for Sense!

Doesn't [AOSP Kernel] 28/05/11 ManU 2.0 - 2.6.35 work on MIUI? with 1190
[Desire Android Development] BlueHawk:
Brand new kernel! :) Thanks snq! Works well with my LeeDrOiD ROM. No freezes or other issues.
[Desire Android Development] aeggedeler:
Hello! I just wanted to report my experiences with the new kernel. After a day with normal usage I have managed to freeze up after an ended phonecall. It seemed to occur when the dialer attempted to finish the call. This is the only freeze i have had so far.

Im using insertcoin 1.1.4, s-off cm7 hboot with the latest nocallrec kernel posted in this thread.

Unfortunately I am not at home, so couldn't pull a log. If I'm to come across another freeze, I'll get a log.

Thank you for all your work snq! And a good weekend to you all.

Carved in bread by aeggedeler

Edit: I forgot to add that a whole lot of freezes occurdd because my SDcard wasn't perfectly aligned. After a realignment, the only freeze encountered was on the kernel mentioned above.
[Desire Android Development] radiohitec:
@snq-

The new kernel works fine for me, I have a little question, is it possible to make a kernel with Wifi-N?

Can you make a ROM Package for Rom packing?
[Desire Android Development] mihai.onu94:
Awesome kernel. It's stable and very fast.

+1 for wifi-n
[Desire Android Development] punky.mtp:
+1 too faster. I only wait for that before flashing new kernel
[Desire Android Development] snq-:
bravo-2.6.35.14-snq-110916.zip (recent build)

wifin_update-2.6.35.14-snq-110916.zip (matching wifin-update)
[Desire Android Development] anderl78:
Hello snq! Thank you!

A change log would be nice... ;-)
[Desire Android Development] snq-:
soz, after all this lockups will be sorted out i'll start a separate thread with detailed features, proper changelogs, and cleaned up source tree

changes here
[Desire Android Development] crescal:
anything added in this build? thanks.

edit: seems i was late to ask the question:p
[Desire Android Development] Nightwing0815:
Thank you!

How can i make a complete boot.img including the new kernel, to put it in a rom.zip?

thanks in advance!

ToM
[Desire Android Development] Sebby:
Hello snq

could you add this scaling available frequencies in your kernel

sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

then i can use deamon controller with this kernel
[Desire Android Development] ZeGuitarist:
Hey snq-,

Would it be possible to add sibere's battery fix to your kernel? It's a pretty nice feature, would be great to have it.

What do you think?

Cheers!
[Desire Android Development] snq-:
looks like the function is already there, it's just not exposed to userland

should be no problem to add it
[Desire Android Development] snq-:
do you still experience that charge drop with gb kernels (stock / my binary-patched ones / builds based on the released htc sources)?
[Desire Android Development] ZeGuitarist:
I don't know how it was before, but here are my experiences.

On stock kernels and official patched builds (yours and bananacakes's), I disconnect my charger in the morning at 100%, and it will drop to 90-95% very quickly over the next half hour or so. After that, it'll go down at a pretty normal rate.

When I used sibere's "battfix" kernel, though, the battery stayed at 100% for a much longer time after disconnecting charger, and dropped at a normal, linear rate.

It just seems to me that official build kernels don't "really" charge to 100%, or something.
[Desire Android Development] snq-:
thanks.

back in the froyo-days i had a solution to that phemomenon: "Updated battery charging algorithm"

since i already have to refactor the bettery code because of a feature request (some kind of battery calibration support), i guess i could port that aswell
[Desire Android Development] ZeGuitarist:
Cheers, you're a champ mate! ;)
[Desire Android Development] tobi01001:
Lightsensor Driver / AutoBrightness fix

Hi snq-

Since the kernel source is finally available and you are already in business, I would like to suggest a mod/fix for the lightsensor driver....

I've been looking and searching quite a time to mod autobrighness settings in the framework-res of sense roms (based on a guide from Desire HD).

What I realized with the classic desire is, that the sensor driver (especially the levels the sensor manager uses) only uses/provides 7 Levels (out of possible 10).

What is really annoying if using autobrightness is that the minimal Level we get from the driver is still to bright.

The reason for this is that we never see Level 0 from the sensor driver. I am not quite sure if it's a bug or a feature. Nevertheless, having that additional level would give us the opportunity to lower autobrighness even more in dark conditions (as Level 0 should meant to be anyway).

So I already had a look into sources and found a possible solution:

First, the light-sensor values (levels) are defined in

arch\arm\mach-msm\board-bravo.c

static struct microp_function_config microp_lightsensor_function = {
.name = "light_sensor",
.category = MICROP_FUNCTION_LSENSOR,
.levels = { 0, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x3FF, 0x3FF, 0x3FF },
.channel = 6,
.int_pin = 1 << 9,
.golden_adc = 0xC0,
.ls_power = capella_cm3602_power,
};

You see that there are 10 Levels starting from 0 to 3FF. Since 3FF is there 3 Times, we only get 8 Levels and since we do not see Level 0, we see only 7 Levels in Android (sensor manager / framework).

The sensor-driver is in\drivers\input\misc\cm3602_lightsensor_microp.c

tatic int get_ls_adc_level(uint8_t *data)
{
struct microp_ls_info *li = ls_info;
uint8_t i, adc_level = 0;
uint16_t adc_value = 0;
...
...
for (i = 0; i < 10; i++) {
if (adc_value <=
li->ls_config->levels[i]) {
adc_level = i;
[B]if (li->ls_config->levels[i])
break;[/B]
}
}
printk(KERN_DEBUG "ALS value: 0x%X, level: %d #\n",
adc_value, adc_level);
data[2] = adc_level;
}
...
...
}

You see the marked if statement within the for loop which sets the level according to the sensor data.

Level 0 is unfortunately skipped, since we need a value <>0 for the if-statement. So even if we get zero from the sensor the for loop will iterate to level one.

My proposal would be to change the lightsensor values array to have a 1 instead of a zero at Level 0 (level[0]).

Therfore, we might have the additional very useful sensorlevel.

Changed:

static struct microp_function_config microp_lightsensor_function = {
.name = "light_sensor",
.category = MICROP_FUNCTION_LSENSOR,
.levels = { [B][I]0x01,[/I][/B] 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x3FF, 0x3FF, 0x3FF },
.channel = 6,
.int_pin = 1 << 9,
.golden_adc = 0xC0,
.ls_power = capella_cm3602_power,
};

Further: Don't know if it's possible, but maybe we could have an (accessible) interface for the values in the array (like frequencies / voltages). This would enable us to play around with different values and to adjust autobrightness on the fly (atm one has to mod framework-res.apk)

So, what do you think?
[Desire Android Development] ziggy1001:
Apologies for off topic but how many people who are asking for wifi-n have reliable 100 Mbps internet connection?
[Desire Android Development] beanbean50:
I'm losing about 1% battery per minute whilst browsing the web (10 minutes browsing = 10% battery drain) I wonder if this could be considered normal for a GB Sense ROM...?
[Desire Android Development] fragargon:
Hi snq,

do you think it would be possible to compile the tristan202's BFS cpu scheduler.

It ported to his working GB kernel, see post for available sources

http://xdaforums.com/showpost.php?p=17613848&postcount=266

this would greatly improved cpu tuning.

thanks
[Desire Android Development] ziggy1001:
Just spent 20+mins of painfully slow 2G-3G surfing for 10% drop
[Desire Android Development] rayiskon:
hey snq- i noticed something on ur 13.9 build (haven't had time to try the 16.9) , when the phone stays a relatively long time on standby (~1h or more ) and u wake it up the battery current shows a lil higher drain value, usually it is between -3 to -5 mA , in this case it is showing around -9mA (sometimes more, i've seen ~ -30mA on wake ), i tried with sleep governors and freqs and without them,but it was the same, i have no special apps running in background that could cause that drain (especially if the phone has been on standby for 4-5 hours). not sure really what's the cause for that drain. p.s. current was monitored using elixir battery current widget on homescreen :)
[Desire Android Development] kuroneko007:
Can see WiFi networks but cant get an IP address, using WiFi N and also normal version. Using Cool Sense 3D AceS v2a. Anyone having the same problem?
[Desire Android Development] snq-:
the marked statement does not set the level

it's just there to break the loop, so we don't unneccessarily iterate the array in case we already got the matching (value read <= value for current level) level
[Desire Android Development] snq-:
how come?

.
[Desire Android Development] punky.mtp:
It's really usefull on LAN :cool:
[Desire Android Development] anonymous2183:
Did you flash GingerCakes0.6a before? for me,this would cause same problem.
[Desire Android Development] kuroneko007:
Yes! Because WiFi wasn't working with gingercakes I tried this kernel. What did you do to solve it?
[Desire Android Development] anonymous2183:
restore from my backup,then flash snq's kernel,cause GingerCake0.6a is a img file,there must something in config not play well our desire.
[Desire Android Development] tobi01001:
I know it just breaks the loop. That's exactly the problem for the first iteration. Since we have a 0 at first in the array, we do one unnecessary iteration and end up in level one instead of level 0. And therefore all sensor apps see/show 40 as the lowest brightness. This applies for the framework as well. So the assigned brightness for level 0 will never be set...

BTW: if the statement wouldn't be there, we would always have level 10 (9)...

Maybe you could give it a try...
[Desire Android Development] snq-:
oh youre right

so the workaround would be changing the first element to !0 and the fix would be changing "if (li->ls_config->levels) break;" to a single "break;" (since the condition was reduntand anyway)
[Desire Android Development] tobi01001:
Should work. Even only changing the first element to 0x01 should do the trick. Using only the break statement could be even better. I do not know if that would break the driver for other devices but we are on desire development anyway...

If that works like I expect it and "cat /sys/devices/i2c-0/0-0066/ls_adc" gives me level 0 and "cat /sys/class/leds/lcd-backlight/brightness" gives the corresponding screen brightness then we could go one step further and adjust the array so that we have all levels (0 to 9) because the framework uses 10 levels but gets only at the moment....

Finally to try this, I first have to switch back to Sense. :-D Will do so this evening.
[Desire Android Development] ivicask:
Good thing someone working on this, i also noticed Desire never switches to lowest brightness values, and i was trying to tweak framework, but it was just ignoring last 1-2 lower values...so it must be kernel prob.

Hoping for positive results so we can finally have some costom brightness levels for sense roms, and save our batterys and our eyes at night :)
[Desire Android Development] Zeljko1234:
I also tried to tweak framework without success, so I used Brightness Profile widget to switch it to low at night.
[Desire Android Development] ivicask:
I think WifiN has apsolutley minimun or none perfomance impact on our phones, as it cant even process more than 54mbit of data in any way.

If you copy files any way you still wont reach 54mbit as its limited by speed of your SD card or nand, and also i doubt even if you have more than 54mbit internet that desires processor can proces data so fast...If you watch movie directly over Wifi..also..Desire cant process movies not even near that bitrate...

Just my thought's
[Desire Android Development] teorouge:
Thanks, flashed both zips in a row and getting connection, bandwith is 65MBmbps so it should be N then. I'm happy because upstairs I get decent connection, now. :)
[Desire Android Development] Nightwing0815:
Seems, i can answer myself the question. (shall i hit thank you on my own posting? :p )

Added the folder kernel in rom.zip, the new module in /system/lib/modules and changed the code from updater-script to:

ui_print(" Installing Kernel ... ");
unmount("/boot");
format("MTD", "boot");
#assert(package_extract_file("boot.img", "/tmp/boot.img"),
# write_raw_image("/tmp/boot.img", "boot"),
# delete("/tmp/boot.img"));
package_extract_dir("kernel", "/tmp");
set_perm(0, 0, 0777, "/tmp/dump_image");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
run_program("/tmp/dump_image", "boot", "/tmp/boot.img");
run_program("/tmp/unpackbootimg", "/tmp/boot.img", "/tmp/");
run_program("/tmp/mkbootimg.sh");
write_raw_image("/tmp/newboot.img", "boot");

Should work. Flashing tomorrow...

ToM
[Desire Android Development] theGanymedes:
Last "write_raw_image" line is unnecessary, if you're not planning to write it right away... All you need will be "newboot.img" from /tmp folder.
[Desire Android Development] Nightwing0815:
Just copied the updater-script syntax from snq-'s zipfile here.

Only commented out the 3 lines from the ROM updater-script and replaced it with the new entry.

ToM
[Desire Android Development] theGanymedes:
Got that :) However, there is something bugging me.. There is a format boot partition line above your commented lines. Shouldn't it erase boot, so dumping boot image would be blank? So all lines you need should be those:

set_perm(0, 0, 0777, "/tmp/dump_image");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
run_program("/tmp/dump_image", "boot", "/tmp/boot.img");
run_program("/tmp/unpackbootimg", "/tmp/boot.img", "/tmp/");
run_program("/tmp/mkbootimg.sh");
[Desire Android Development] Nightwing0815:
WOW, good hint! Overseen that totally, you're right.

Changed it immediately:

ui_print(" Installing Kernel ... ");
#unmount("/boot");
#format("MTD", "boot");
#assert(package_extract_file("boot.img", "/tmp/boot.img"),
# write_raw_image("/tmp/boot.img", "boot"),
# delete("/tmp/boot.img"));
package_extract_dir("kernel", "/tmp");
set_perm(0, 0, 0777, "/tmp/dump_image");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
run_program("/tmp/dump_image", "boot", "/tmp/boot.img");
run_program("/tmp/unpackbootimg", "/tmp/boot.img", "/tmp/");
run_program("/tmp/mkbootimg.sh");
write_raw_image("/tmp/newboot.img", "boot");

The line unmount("/boot"); is unnecessary too, i think.

In case, i need this code for future use, i only commend it out. Better than use google, when i need them again.

Thanks for your hint!

ToM
[Desire Android Development] dorutec:
This kernel has same old problem: after bluetooth headset is disconnected the phone has absolutely no sound.
[Desire Android Development] theGanymedes:
No problem here (using Plantronics Backbeat 903)
[Desire Android Development] snq-:
@tobi01001: in case you wanted to test your mod:

bravo-2.6.35.14-snq-110917.zip

(build contains also mm-related changes, but they don't interfere with your stuff)
[Desire Android Development] tobi01001:
Big thanks...

Just flashed Leedroid HD 3.3.3 - R5 and the previous kernel.

So I will adb shell into the phone and report back...

/Edit:

OK, in short: It works... yippieh... another job well done :-D

Here is what I got before the mod:

ADC[0x003] => level 1
ADC[0x003] => level 1
ADC[0x004] => level 1
ADC[0x003] => level 1
ADC[0x001] => level 1
ADC[0x003] => level 1
ADC[0x001] => level 1
ADC[0x003] => level 1
ADC[0x001] => level 1
ADC[0x003] => level 1
ADC[0x001] => level 1
[B]ADC[0x000] => level 1
ADC[0x000] => level 1[/B]

and here what is shown with the mod:

ADC[0x00D] => level 1
ADC[0x00D] => level 1
ADC[0x00D] => level 1
ADC[0x00D] => level 1
ADC[0x00D] => level 1
ADC[0x00F] => level 1
ADC[0x00D] => level 1
ADC[0x00D] => level 1
ADC[0x00D] => level 1
ADC[0x00F] => level 1
ADC[0x00D] => level 1
ADC[0x00D] => level 1
[B]ADC[0x000] => level 0
ADC[0x000] => level 0
ADC[0x000] => level 0[/B]
ADC[0x006] => level 1
ADC[0x009] => level 1
ADC[0x006] => level 1
ADC[0x006] => level 1
ADC[0x006] => level 1
ADC[0x006] => level 1

And a sensor app shows 10 instead of 40 for level 0... So yes it works like I expected and finally like it should be.

I don't know if we should tweak those values a bit more. I would say yes.

If we move the array to the driver itself, would it then be possible to compile it as a module and change the array values only in the module?

Thanks again, time to go to sleep.