yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] dunstan92:
Snq, your kernel is still giving awesome speeds. Just want to ask why is USB toggle not appearing? It has been the same since v110923. I've tried other kernels, and the USB toggle is working fine. I flashed your kernel and the wifi n patch. After that the USB toggle doesn't work. The same goes to coolv3's rom, Aurora and runny. May I ask what is causing this??
[Desire Android Development] ivicask:
Just tested it, Tobi's way is not working

SNQ try your method, ill try it right away..
[Desire Android Development] anderl78:
Yep, can confirm its not working... The issue tobi reported, is still there.

@snq: I think, atm the freeze/reboot issue is our biggest Problem. Regardless, many thanks for your commitment!
[Desire Android Development] tobi01001:
You like it short, do you? :D Looks good... since I am an engineer with some focus on quality I usually tend to make things more "readable" and leave the optimization to the compiler. ;)

just created a github account... If we succeed here, I may dive a little deeper into kernel development... It's starting to be fun already.

Will flash the kernel now. May take some time to report back since I have some other stuff on the agenda.

Btw: using the 110918-lsmod1 for quite a while now without any freezes or other issues. Performance is great as well as battery. What I did in addition was to remove the script in init.d which were there to load kernel modules (not needed any longer and I doubt that it may cause trouble) and the script which sets the governor and frequencies at boot (I don't know what happens if you try to swicht to smartass if only smartassv2 is available).

further, I don't know how different roms implemented the module loading and governor setting. Would be best if developers remove it in updates. But for those testing the kernels already, it might be worth a try to remove that unnecessary stuff.
[Desire Android Development] tobi01001:
You guys are right. It's not quite working... But not bad for the first quick shot. Looks like we have the wrong enabled flag. I am not sure if it will ever work this way. May be something the kernel can do nothing for. But I'm not giving up yet...

Give me some time and I will have another look and proposal.
[Desire Android Development] Gr4bov5ky:
What do you mean under great battery performance?
[Desire Android Development] anderl78:
I guess, better battery live as with the closed source kernel... ;-)
[Desire Android Development] resadent:
snq-, does the new kernel have any changes apart from new tobi's fix?
[Desire Android Development] erklat:
You haven't bothered to read at least last 10 posts, have you?
[Desire Android Development] snq-:
tobi, how you like this:

--- a/drivers/input/misc/cm3602_lightsensor_microp.c
+++ b/drivers/input/misc/cm3602_lightsensor_microp.c
@@ -52,6 +52,9 @@ struct microp_ls_info {
int als_intr_enabled;
int is_suspend;
int old_intr_cmd;
+
+	uint8_t lsauto;
+	uint8_t spienab;
};

struct microp_ls_info *ls_info;
@@ -64,6 +67,8 @@ static DECLARE_DELAYED_WORK(enable_intr_work, enable_intr_do_work);
static void lightsensor_do_work(struct work_struct *w);
static DECLARE_WORK(lightsensor_work, lightsensor_do_work);

+static void read_spi_status(void);
+
void set_ls_kvalue(struct microp_ls_info *li)
{

@@ -125,7 +130,10 @@ static int get_ls_adc_level(uint8_t *data)
if (microp_read_adc(data))
return -1;

-	adc_value = data[0]<<8 | data[1];
+	read_spi_status();
+
+	adc_value = ls_info->lsauto ? (data[0]<<8 | data[1]) : 0x00;
+
if (adc_value > 0x3FF) {
printk(KERN_WARNING "%s: get wrong value: 0x%X\n",
__func__, adc_value);
@@ -388,14 +396,9 @@ static DEVICE_ATTR(ls_adc, 0664, ls_adc_show, NULL);
static ssize_t ls_enable_show(struct device *dev,
struct device_attribute *attr, char *buf)
{
-	uint8_t data[2] = {0, 0};
-	int ret;
-
-	microp_i2c_read(MICROP_I2C_RCMD_SPI_BL_STATUS, data, 2);
-	ret = sprintf(buf, "Light sensor Auto = %d, SPI enable = %d\n",
-	data[0], data[1]);
-
-	return ret;
+	read_spi_status();
+	return sprintf(buf, "Light sensor Auto = %d, SPI enable = %d\n",
+	ls_info->lsauto, ls_info->spienab);
}

static ssize_t ls_enable_store(struct device *dev,
@@ -502,6 +505,14 @@ static void light_sensor_resume(struct early_suspend *h)
}
#endif

+static void read_spi_status()
+{
+	uint8_t data[2] = {0, 0};
+	microp_i2c_read(MICROP_I2C_RCMD_SPI_BL_STATUS, data, 2);
+	ls_info->lsauto = data[0];
+	ls_info->spienab = data[1];
+}
+
static int lightsensor_probe(struct platform_device *pdev)
{
int ret, irq;
--

fastbootable zImage for testing
[Desire Android Development] Droidzone:
Thanks for the code, snq..
[Desire Android Development] resadent:
Yes I did and I read about snq- rebasing the kernel patch by patch but I wasn't sure if the new kernel had these new patches or if he was going to release it later, that's why I posted that.
[Desire Android Development] Droidzone:
Hmm..had partial success with this code.. It requires me to press the trackpad many times and there is a delay of several seconds before it unlocks.. I'll keep looking
[Desire Android Development] ivicask:
Nope, still doesn't work.

@Tobi and SNQ are you sure its Kernel problem and not some other stupid HTC stuff...
[Desire Android Development] t-pip:
snq- latest kernel no freezes but after disconnecting Bluetooth there is no sound from the handset. Had this in 110911 as well. Any ideas?

Thanks for all of your work.
[Desire Android Development] resadent:
You mean, no freezes at all? not even using stupid zombies? Really looking forward to try this kernel, will do it when I have a little bit of time :D
[Desire Android Development] tobi01001:
Yeah, looks good since it relies on lsauto - the flag I was looking for and originally thought it could be als_intr_enabled. But someone already mentioned that it wont work. Anyway, I am gonna flash and crate some screen brightness logs and report back.
[Desire Android Development] t-pip:
Sorry not a zombie player
[Desire Android Development] tobi01001:
@snq-: Thanks a lot. It works. At least somehow. And it brings us one step closer...

To sum up:

With this fix/hack or whatever we call it, we see no more crappy values from the ADC / SPI when the sensor is asleep. So what we get till the sensor is ready (ls_auto=1) are just beautifull zeroes all over the place :D

So this works quite well and helped me to find out the following: When you turn on the screen, it will be set to the value it was at when you turned it off.

So if you turn the screen off when you are in the brightest sun and the screen is at 255 it will turn on with 255 and then go doen to the level it actually reads.

If you turn it off while at level 1 and turn it back on in conditions for level 5, it will turn on with the value of level one and then change to the value of level 5. this works in most of the cases.

However, it somehow does not work, if you turn it off at level 0 and turn it back on in conditions for level 0. It will turn back on with the value for level 0 but after this change to the value of level 1. If it got turned on with the value of level 1 and there are conditions for level 0 it will not go down to the value of level 0.

I am not quite sure if this is still a kernel issue or rahter something the framework 7 android must handle.

On possibility could be, that changes in the levels somehow fire an event and it may be that such an event is missing for level 0. I don't know if its worth to look for a fix for that. A simple solution could be this one:

instead of keeping the values at level 0 while the sensor is not ready, we may keep them at e.g. level 3 (to be calculated with als_gadc and als_kadc). This way, it may trigger the whatever change as soon as the sensor is ready.

Second proposal:

What should work and what I would like to put into discussion here is the following:

We forget about my idea of enabling level 0 and "disable" it again.

Instead of enabling level 0, we just shift each array value one to the right (despite the left 3, they hafe to be adopted do that the last one is 3ff). So the resulting array would be something like 0x00, 0x04, 0x21, etc...

This way, we still have 9 sensor levels. Those sensor levels do no longer exactly represent what android reports as lux (not if it ever did) but represent levels from totally darkness to supernova. Developers and tweakers can adjust their frameworks accordingly.

Pros:

- fast, reliable and imho (still to be proved) working

Cons:

- on stock ROMs and/or ROMs without adjusted framework, the screen might be "a bit" (one step) to bright for the light conditions (as it always was?)

- Seems to be a bit of to much work for just a little screen on/off bug.

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

What do you guys think?

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

Damn: With so much ideas, I need to learn how to compile my own kernels... :D
[Desire Android Development] Carko:
Just want to say that this latest kernel is working great for me, there are no freezes YET, hope there won't be any :)
[Desire Android Development] osoelpeligroso:
Is it recommended to wipe battery stats after flashing a new kernel? Have the impression that batteryindication behaves strange after flashing a kernel...
[Desire Android Development] t-pip:
Bump

Padding
[Desire Android Development] Carko:
You can use Battery Calibration tool, just follow instructions...

You can also try charging your phone to 100% then turn it off and charge again until led is green, than power on and again turn it off and charge until LED is green. Your batt will have great life, and indicator will be showing right values.

You can make your UOT battery mod to show percentage on battery icon
[Desire Android Development] resadent:
I have been playing Stupid Zombies for more than an hour with the new kernel, no freezes for now, very very happy :D
[Desire Android Development] t-pip:
Sounds good, just this Bluetooth problem now.
[Desire Android Development] PeQuEsan:
I'm not using snq- kernels right now... but I've used them till 110923, and I connect my Desire to my Parrot mki9100 twice every day (using even A2DP profile to play music stored in my Desire). I haven't seen this issue you report lately. Sorry.
[Desire Android Development] t-pip:
The ones after 110911 and before 260911 haven't had the problem but they lock up. 110911 and 260911 both don't lock up but loose sound.
[Desire Android Development] thanito:
I dont have the bt problem either. I use my phone in parrot ck3000 evolution and in mki9200 as well without issues.

Which bt do you have?did you try updating the fw?
[Desire Android Development] anderl78:
I tried 260911 for some time now. I must say, its more stable then the last releases.

No freezes or reboots to see, even while playing stupid zombies. But today I used maps navigation and had a reboot...

Last_kmsg: http://db.tt/XP6Ez3YQ
[Desire Android Development] t-pip:
Looks like it's related to voice dial.
[Desire Android Development] erklat:
Does anyone else seem to notice that ringing is more subtle (quiet) than before?
[Desire Android Development] theGanymedes:
260911 is the snappiest ROM I've ever tried. Thanx SNQ..

Also, does anyone have a idea whether it's kernel problem or ROM: Sometimes, when I'm taking pictures continuously, the phone reboots. Alas, I don't have a log or whatsoever (I don't even know anything but logcat :) )
[Desire Android Development] resadent:
I know sense 2.x or 3.x based roms have problems with the camera, I don't know what problems but I know they do. Maybe if you tried a sense1.9-based ROM it would work better :P
[Desire Android Development] TomLeeDesire:
Hi snq-

Still there. Testing each one.

No zombies, but a lot of Gps, compass, 3G, WiFi, camera... (geocaching).

110926 is the first since some with no occasional big lag/freeze/reboot after two days of use.

Nice work ;-)
[Desire Android Development] erklat:
Disabling auto enhance usually helps with camera related reboots.
[Desire Android Development] thanito:
i dont use voice dial so i cant help you..I may try it though and see
[Desire Android Development] t-pip:
Seems to be since Call Recording was introduced see here. snq- could you produce a copy of 260911 without call recording to test?
[Desire Android Development] theGanymedes:
Where can I disable it?

Also; today my phone restarted and started to get into a Bootloop. When I checked the logcat, it was showing Java - Not available exception or something (I didn't copy the message, idiot me :) ) and the process was trying to get CpuTimes (Activity Manager) and it was repeating it over and over again.
[Desire Android Development] o$$!ram:
snq, can you please include the cpu freq table in you next releases please?
[Desire Android Development] littlej:
agreed with this, i rember i used to flash lee's rom with the kernel wich didnt had call recording.
[Desire Android Development] l3zawi:
all kernels comes after 110911 are laggy & unstable ... yesterday I flashed 260911 after clearing dalvik-cache ... the phone was too slow .. the best version is 110911 & I'll stay with it but it's recommended like they said to remove the 2 way call recording it's useless btw

snq- your kernel is the best ;)
[Desire Android Development] resadent:
I installed 260911 two days ago an had no problem with it, for me it is the stablest and fastest kernel since 110911.
[Desire Android Development] bgumble:
+1

bugfree @ Aurora v03 and best quadrant benchmark result
[Desire Android Development] merlin699:
too bad, just had a freeze while making a call. but other than that it works great and fast (110926)
[Desire Android Development] osoelpeligroso:
Very stable and snappy, absolutely no lags and freezes! But drains too fast...
[Desire Android Development] l3zawi:
Guys ... did you see this post :

http://xdaforums.com/showpost.php?p=17960386&postcount=571

I found that file on InsertCoin ROM 1.1.4
[Desire Android Development] snq-:
trevfee, just for you: bravo-2.6.35.14-snq-110928-no2wcr.zip
[Desire Android Development] snq-:
mon ami :D

much appreciated!

good to see you around

looks like the kernel crashes are gone, we still have occassional radio crashes
[Desire Android Development] snq-:
huh? .
[Desire Android Development] snq-:
the clockd phenomenon does not affect my releases
[Desire Android Development] snq-:
thanks, radio crash, i had this too
[Desire Android Development] snq-:
that was the one i hacked into the clsoed source kernel, and that is the one i still use in -1109xx; works for me
[Desire Android Development] snq-:
otoh, they were also compiled w/ 2wcr support
[Desire Android Development] bgumble:
hope that makes no difference cause 2wcr is really necassary 4 me :rolleyes:
[Desire Android Development] anderl78:
Hello! Latest kernel seems to be much more stable! Really good work! Thank you for that :-)

What can be done to prevent us from a radio crash?
[Desire Android Development] snq-:
that's exactly what i'm trying to find out :)

btw, which radio version do you have?
[Desire Android Development] t-pip:
Works great. Stable and voice dialling working without losing handset sound.

Thanks snq.
[Desire Android Development] anderl78:
Good as always ;) I'm on 5.17.05.08 if I could help with something... I'm available ...
[Desire Android Development] kekkle:
Using 260911 I found my phone unwilling to turn on when I woke up this morning. Had to remove battery and boot it up.

Thank god I woke up by myself, else I would have been late. But then again, stupid of me to install unstable stuff and rely on it!
[Desire Android Development] t-minik:
i'm testing 110926 on cool's BravoS v7.

phone just reboot because of empty battery but current widget shows 3.65V !

previously i was on 110923 with no problem.

anybody else ?

do i need to wipe battery stats ?

however all is working fine for me.
[Desire Android Development] WatsonDue:
I'm testing 110926. No issues so far, on 1-day usage with some calls (with bluetooth headset) and some games. Thanks snq-!:D
[Desire Android Development] TomLeeDesire:
I use it on HD V3.3.3 GB-R5 data++ with 5.17.05.23.

Still no crash I noticed since flashing.

:cool:

edit : damn, I've to update my sig :S
[Desire Android Development] resadent:
Same here, I also have this radio and had no problems at all with insertcoin 1.1.4. For me this kernel is perfectly stable and fully functional. I remember 5.17.05.08 was a radio extracted from a beta of gingerbread...
[Desire Android Development] anderl78:
Yes, that's possible... Till now I had no problems with it. Perhaps I should flash the newest...

Let's see what snq says to this ;-)
[Desire Android Development] kkiqq1208:
Just testing 20110928 no2wcr,at the sleep mode pressing the power button，phone shows the locksreen with a lagy about some seconds.I use the smartass V2 governor.

When i change the sleep governor to ondemand it has no lagy anymore but with reboot phone the lagy appear again..

Expect this it's very stable and snappy,thanks snq's hard work.

my rom is cool sense aces 1.1 full odexed.do you have any sulution？

Sorry for my poor english:p
[Desire Android Development] erklat:
I still have no problems with it. Mine passed 2hrs stability test with 100 mV undervolt at all frequencies last night :D

Gotta love SVS ;)

Have you checked apply to boot option? It probably restores smartassV2 upon reboot.
[Desire Android Development] kkiqq1208:
Thank for your reply.

I use deamoncontroller and the sleep governor is ondemand when phone is boot up.:eek:
[Desire Android Development] tomurbanowicz:
What values do You set in SmartassV2 and Ondemand?
[Desire Android Development] kkiqq1208:
I just tested snq-110923-kernel and had no lag with locksreen at all..

snq-, could you please check this ,because the 110928 execpt the problem that's very powerful and stable,and also have no 2 way call recorder,thanks a lot!!:cool:
[Desire Android Development] snq-:
if this happens, could you please check if your current cpu freq constraints match with those you previously set? (and it's not like setcpu shows "245 max 245 min" regardless of the state of the gauges)
[Desire Android Development] snq-:
for testers:

(found an axi related difference between v06 and -1109xx)

bravo-2.6.35.14-snq-110929.zip

bravo-2.6.35.14-snq-110929-no2wcr.zip (w/o callrec support)

optional wifi-n mods:

wifin_update-2.6.35.14-snq-110929.zip

wifin_update-2.6.35.14-snq-110929-no2wcr.zip
[Desire Android Development] VK7HSE:
Not sure if those having issues with the radio crash are using either earlier or later versions, but the radio that was contained within the gingerbread update was version bravo.5.11.05.14.zip

I'm using that version and so far no crashes for me...
[Desire Android Development] t-pip:
snq-

The build from yesterday has been working great for me (without Call Recording) as it allows me to use Voice Dial with my bluetooth without loosing Handset sound.

Many thanks for all of your hard work.

Edit: Installing new release now.
[Desire Android Development] anderl78:
Thanks again! Will try it and report back! For now I stay with my radio...
[Desire Android Development] nickislauw:
isnt it time to update the OP??

it still says v06..

its quite confusedfor some people!
[Desire Android Development] ZeGuitarist:
Thanks! Testing w/o callrec and w/o N-patch.

Yes, but snq- said he was going to post his new kernel in a seperate thread once it's final. It's still a work in progress atm, but as soon as it's done it belongs in a separate thread, since it's a whole new generation of kernels (based on official GB kernel source).
[Desire Android Development] VK7HSE:
Just flashed the latest, no wifi with either of the modules... Reverting back to the previous...
[Desire Android Development] ZeGuitarist:
Wifi is working just fine for me. 110929 w/o callrec and w/o N-patch.
[Desire Android Development] VK7HSE:
Hmm ok I'm using Supernova rom (not that should make any difference) as this is based on the release from 3 August.

I'm back on the build from the 26th and that's just fine... I'll give the no record to see if that is the same for me...
[Desire Android Development] t-pip:
+1 Works fine here.
[Desire Android Development] VK7HSE:
Ok just flashed the no record version (bravo-2.6.35.14-snq-110929.zip) and all is fine (wifi working)

Doesn't make sense to me! However I'm happy now :)
[Desire Android Development] resadent:
Flashed 29sept kernel just a while ago... just had a five-seconds or so lag with the browser and also with nofrills... gonna continue testing
[Desire Android Development] t-minik:
are you sure ?

i thought gb update radio was 5.17.05.23.

with 110926 sleeping power consumption is awesome for me !

3/4 mA wifi + 3g on with BravoS V7 ondemand.

wake is prety good to.

great great work snq- !
[Desire Android Development] tobi01001:
Can someone please check / confirm : it looks like the compass isn't working any longer. I remember this was the case with the first gb leak....
[Desire Android Development] t-minik:
compass works perfectly for me ;)
[Desire Android Development] t-pip:
Seems OK here
[Desire Android Development] NeoEpsilon:
Compass works fine here...
[Desire Android Development] kkiqq1208:
Thank you snq-,i will check for a while.:cool:
[Desire Android Development] tobi01001:
Well yeah, thank you guys. Just another proof that I've been to stupid.

Compass working fine here as well.
[Desire Android Development] erklat:
I use smartassV2 only.
[Desire Android Development] rayiskon:
wifi is not reconnecting for me with the last kernel , sleep policy set to never , and ofcourse wiped cache and dalvik before flash..

ow and still getting -25 / -30mA current during standby when wifi is on , ya ya i know no 1 else got this,but i'm mentioning it coz i don't have a clue what is causing it
[Desire Android Development] resadent:
Just had a bat pull freeze with my phome when playing stupid zombies. I managed to lock my phone but the it did nothing... pulled the battery and reinstalled 260911. For me, this kernel works noticeably better than the newest one and has no freezes at all.
[Desire Android Development] darkpain:
I just had my second freeze!

The first was when i connected to wifi and open android market!

The second when i opened internet browser!

I had to pull the battery!

I had 290911 without call recording with 23.05.17.5 radio!
[Desire Android Development] alidsd:
All those who are having freezes please try to change your governor from 'smartassv2' to 'ondemand'.

I think this governor has some problems.

Sent from Hell using XDA App
[Desire Android Development] erklat:
I had one too. The phone wasn't accessible for about a minute, it didn't freeze completely. Everything stock.

Tried more than a week ago. It is not the governor.
[Desire Android Development] anderl78:
Hello!

Freeze for a few minutes on 110929 during a phonecall. No battery pull needed. Still reproducable reboots if I use maps navigation. As written, I'm still on 5.17.05.08 radio.

110926 gives me the reboots too, but had no freezes...

Last_kmsg: http://db.tt/bQM5R9QR
[Desire Android Development] Musko:
Same here ...
[Desire Android Development] darkpain:
same here!!!

The 110911 is the most stable(i installed it again with no problems so far) but the 110926 and 110923 are faster, i think, but gives me reboots too!!
[Desire Android Development] ZeGuitarist:
Just had a freeze too, using 110929 w/o callrec and w/o n-patch, on IC 1.1.4 CM7. Battery pulled, so no kmsg...

Reverting to 110926, that seemed more stable. No freezing problems there.

EDIT: I reverted to 110928 (no callrec or wifi-n) instead, I'll see how that goes first. If that fails, it's going to be 110926 instead.
[Desire Android Development] TomLeeDesire:
Had 2 freezes on 110929 (pull out needed after waiting 2min, no last_kmsg, just last_radio_log).

2 times were using gscript. 1st checking vdd levels (first execution ok, second one freeze). 2nd trying to mount my share rw with cifs.

Edit : just tried cifs again after reboot, it's running fine (mount, copy from pc to phone, unmount).
[Desire Android Development] jasisoft:
freezes on 110929 too, mainly after calls. flashed back 110926 and everything works fine...

using InsertCoin 1.1.4 on S-LCD Desire... :confused:
[Desire Android Development] l3zawi:
As I said before ... the best is 110911 no lags at all ... when I use the newest ones I had freezes in opera browser or when playing some games ...