yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Komadyret:
Flashed 110916 yesterday, and after running full speed (performance, 1075MHz OC) with the old v5 kernel, I enabled smartass v2 on a 384-1075MHz range in setcpu. Phone was sluggish at times, had 5 freezes (several minutes long) while doing different things (using facbook app, loading pages or scrolling in DolphinHD browser, hitting home-button (loading sense homescreen) etc.) but only 2 times did I have to pull the battery, and mail and footmob-scores still updated with notifications and sound in background. Also I had sense and acore and 2-3 other apps FC on me during the same timeframe.

Went back to performance in in setcpu and all seems well again. Weird, as I thought smartass should be a good one. I used the old smartass back on the froyo ROM (Also LeeDroid) with very good results, and quite a few profiles for powersaving while on the go without much lag.

Gonna hold off doing more tweakiing until LeeDroid releases his next HD port, then I'll go over it all again. Just wanted to share my experience. Guess it's my phone having trouble with some of the voltages given in the scaling.

Other than this little annoyance, the kernel seems to do it's job well at this point. Good job and a thnakyou to snq- and his little helpers :D
[Desire Android Development] dorutec:
The sound remains routed through bluetooth output, if i reconnect headset i have sound in it.
[Desire Android Development] siedkins:
Pleased to see lots of new activity now the source has been released!

SNQ - loving your work as ever!

And also big ups to the rest of the community for continually tweaking stuff.
[Desire Android Development] ziggy1001:
@tobi01001

For me the problem is not too bright in low ambient light levels but outdoors on bright/sunny days i just can't see the screen it's not bright enough could this be addresed by the same method?
[Desire Android Development] angusc:
+1 must be getting old but that sunlight is a real killer.

Sent with Desire.
[Desire Android Development] BigMrB:
Just flashed 2.6.35.14 kernal... But I get splash boot loop..

Reflex 2.1.9 with cm7 r2

Wiped cache and dalvik...

Am I missing something lol? Is that the correct procedure?

I've read 10 pages back and seen someone else had issues with reflex.. but wasn't answered. I know people with reflex are using the same kernel ... Never had issues flashing before
[Desire Android Development] ivicask:
I think maximum brightness works just fine, only lowest settings didint work..its just our Desire sucks at direct sunlight..you cant do nothing about it.

Anways tomorow my desire comes from repair so im gona play with framework for some nicer auto brightness values..
[Desire Android Development] tobi01001:
At least I think so... Reason is, that level 7 already represents the brightest we get from the sensor / driver. The framework on the other hand works with all 10 possible levels. The max brightness is set at level 9... At least on stock framework.

So there are 2 ways to cope with that. Either we adjust the kernel so that the driver delivers 10 levels or we adjust the framework so that the screen brightness is at 100% on level 7...

I would prefer to mod the kernel, because this way we would have additional levels and even stock frameworks could benefit from this.

However, there are possible drawbacks... It could be that htc limited the number of levels by reason and it could further be, that the corresponding brightness is either to bright or to dark for the ambient light conditions.

The latter could be coped with modifying the framework accordingly...

I would give it a try... If snq- agrees :-) to compile the kernel. My last kernel compilation was on gentoo and was hardly more than "make all && make install" :-)

Well with patched sources (cpu free governor's etc.) and a proper config and a hint on the toolchain I could give it a try...
[Desire Android Development] snq-:
bravo-2.6.35.14-snq-110918.zip

regulators/core: switch to vanilla

power: extend dpm watchdog timeout value

cpufreq: expose scaling_available_freqs to userland

+tobi's cm3602_lightsensor_microp: don't skip level0 from -110917

+mm-related mods from -110917

_optional_ wifi-n update: wifin_update-2.6.35.14-snq-110918.zip
[Desire Android Development] snq-:
any idea on the values?

0x0 0x71 0xE2 0x153 0x1C4 0x235 0x2A6 0x317 0x388 0x3FF?
[Desire Android Development] tobi01001:
Yes, already drawn a graph for it. Give me a minute.

/Edit: Here it comes:

I would suggest - from simply drawing a corresponding curve - the following values:

0x04 -> to have Level 0 already if there are very very low light conditions

0x21

0x4D

0xDC

0x134

0x18D

0x1E5

0x280

0x340

0x3FF

so finally:

.levels = { 0x04, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x280, 0x340, 0x3FF },

Actually, 0x3B2 was the max I got on my desire. Dunno if anyone is able to come closer to 0x3FF. But even 0x3B2 would lead to the highest level.

Looking forward to try it.

Thank you.
[Desire Android Development] anderl78:
Yep, my autobrightness mod on leedroid is using now even the lower values. To get the highest brightness-levels it would be necessary, to set highest on level 7. Possible, but better would be, to have all 10 levels...
[Desire Android Development] ZeGuitarist:
Forgive my noobishness, but what exactly is the difference? Does this mean undervolting becomes impossible again?
[Desire Android Development] snq-:
thanks!

d/l: tobi01001/bravo-2.6.35.14-snq-110918-lsmod1.zip

we could make all this tunable from userland (don't know if it would be worth the time invested though)
[Desire Android Development] snq-:
uv is still possible, i only removed some caf patches that were there in the htc code
[Desire Android Development] Zeljko1234:
Yes is worth to finally solve brightness control, especially at night.

Thank you :)
[Desire Android Development] anderl78:
Thanks! Will try with my modded framework...
[Desire Android Development] l3zawi:
first .. tnx for the great kernel .. :)

so this bravo-2.6.35.14-snq-110918.zip is stable & recommended to flash

& bravo-2.6.35.14-snq-110918-lsmod1.zip is on test and exp
[Desire Android Development] Alex-V:
I also think ext4 is not running...make my own version of 2.3.3 with data2ext ....and stuck on htc white screen...so i flash the latest leedroid (with modules in to check) and also stuck with ext4...!?!

maybe the module is running (if on ext3) and check with a terminal (have not test it)

with kind regards..Alex
[Desire Android Development] roalex:
its running really, i saw the modules loaded and i mounted with -t ext4 my ext, now you have to figure a way to make the a2sdext scripts work, thats another story. If you have system stuff on /sd-ext then its bad cause the mounting comes in to late. We could mount sd-ext in init.rc but then we would have to make a e2fsck service in it also, once is mounted we cant check for errors and not checking errors on it will kill the rom pretty fast.
[Desire Android Development] Alex-V:
OK...maybe (yes, think) you are right...mhhhh...ownhere´s script worked fine in every rom i tried (also with mine rom) but this was still with a ext4 supported kernel... i also tried it with copy e2fsck but no success at the moment (i did a set perm 755 on it)

with kind regards..Alex
[Desire Android Development] Droidzone:
I guess this issue will be fully solved only when a kernel with native ext4 support is built rather than one with loaded modules. With data2sd, there shouldn't be issues if insmod is done in ramdisk, since the script is in init.d. Isn't a2sd also loaded similarly?

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Desire Android Development] Benee:
added my tweaked conservative (from vorkKernel) + some tweaks for a init.d script if someone wants them ;)
[Desire Android Development] roalex:
Why don't we just make a proper ramdisk ?:p most of the tweaks should be in the init.bravo.rc (they are in another form in there now).
[Desire Android Development] Droidzone:
Definitely!

Swyped with my Starburst based Desire. Please ignore any typos
[Desire Android Development] Droidzone:
So init.rc or init.bravo.rc? Which one is a cleaner implementation? Also what exactly is the sequence of loading kernel ram disk scripts?

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Desire Android Development] roalex:
its just a different syntax, if you look, its not echo its write. Also we need to make sure we can actually write in those spots, like all the proc and such.
[Desire Android Development] coolexe:
Hi,

I've successfully edit the ramdisk...now ext4 modules activated at booting time but than
[Desire Android Development] Nitin985:
Neither can I but benee has made a edited Rom which has it built in :)

Now the Rom boots with my ext4 partition :)
[Desire Android Development] chihliouma:
Hi there, can you help to offer your related file that can really let us to boot ROBO's v07 ROM successfully with EXT4 ? Thanks.
[Desire Android Development] Benee:
added the insmod to system/bin/starta2sd (beginning) and system/etc/init.d/dta2sd (don't know how it is called correctly)(beginning) too.
[Desire Android Development] Muxeu:
1) Flash coolex zip;

2) rename /system/etc/init.d/dtapp to 04dtapp

2) make backup;

3) format ext3 to ext4

4) make restore

It works for me
[Desire Android Development] coolexe:
Hi,

just add...insmod

insmod /system/lib/modules/jbd2.ko
insmod /system/lib/modules/ext4.ko

on early-init category in init.bravo.rc file
[Desire Android Development] Muxeu:
Your solution is better ;)
[Desire Android Development] chihliouma:
Sorry to say but I don't find any init.bravo.rc file under system/etc/init.d directory. But there is "dtapp". Should I add the statement into that file or should I create another file ? Sorry for such a stupid question.
[Desire Android Development] KennyDumah:
Because it isn't under that directory.

It's just under the main folder.

Like when you open root explorer.

;)
[Desire Android Development] Muxeu:
init.bravo.rc is in the root path.

You should push jbd2.ko&ext4.ko to /system/lib/modules/ and add to init.bravo.rc

insmod /system/lib/modules/jbd2.ko
insmod /system/lib/modules/ext4.ko
[Desire Android Development] roalex:
still need to set permissions to the cpu stuff in init.rc
[Desire Android Development] snq-:
i mean, to be able to set the curve from cli
[Desire Android Development] Zeljko1234:
Yes, it's enough. Then someone could make application for it but I would be happy with cli :)
[Desire Android Development] ziggy1001:
Thanks i kinda get the impression when designing the phone it was only tested indoors under artificial light coz outside what good is a phone where you can't view the screen!
[Desire Android Development] anderl78:
Yep, just tried...

All 10 Brightness-levels accessable! I'm currently on Leedroid 3.3.3 with my autobrightness-modded framework.

Really good work snq and tobi!
[Desire Android Development] ZeGuitarist:
Flashed 119018 a few hours ago... Bad news, it still locks up.

Phone froze for 10min after which I pulled battery. I was streaming video from home LAN. I'm on IC 1.1.4 CM7.

Ugh :(
[Desire Android Development] tobi01001:
Nice... Will test it tomorrow but anderl78 already mentioned that all levels are accessible.

I also thought about making it accessible through sysfs or something like it. Could work. The problem I see is that the "table" is written to the sensor during driver initialization. So changing on the fly could lead to wrong values or the need to reinitialize the driver.

On the other hand, changed values which apply after a reboot for instance would be still better than the need to modify the framework.

Last but not least: I think now that there are 10 usable level for the whole range, there should be little need to modify the sensor values.

And as a last thought: if someone really liked to drive this further, it would be better to write an app that directly reads the sensor raw data and writes to the screen brightness in /sys... (autobrightness turned off in that case)

So thanks again for implementation. Will see how it works.
[Desire Android Development] tobi01001:
@anderl: care to share your framework over in the LD thread?
[Desire Android Development] theGanymedes:
lsmod1 kernel doesn't work with wifiN patch. Says "Error" on wifi settings page.
[Desire Android Development] galom:
I had a freeze today too. I was browsing with Dolphin this time.

Fyi you don't have to pull battery. Just press and hold trackpad. Volume down and power for 5 seconds (in that order. All at same time)
[Desire Android Development] live_0978:
Believe me, for that type of lock up the control-alt-del type method doesn't work, battery pull is the only option.
[Desire Android Development] galom:
OK, I must suffer from a different type of lockup. It works for me.
[Desire Android Development] galom:
Another lockup :(

It was at exact same point while loading page in dolphin. Site was on Lan (SickBeard)
[Desire Android Development] mistaliu:
I'm having an issue with battery and the kernel....I think. OK so I've been running LeeDroid HD 3.3.3. While running v6? of snq kernel, the last update of old kernel released with LeeDroid, I had great battery on 3g but wifi slayed it. Nothing could fix it, even Lee said just try not to use wifi. Now I have flashed the latest string of kernels since the HTC release, up to latest 110918 and now the opposite is happening. I'm getting great battery on wifi now but its 3g now that is killing my battery. I haven't changed anything with my phone since flashing the rom originally. Any ideas anyone?

Sent from my HTC Desire
[Desire Android Development] tobi01001:
Could you guy's with more or less random freezes provide the following information in addition:

- Kernel version

- which settings for the cpu (SetCPU profiles and such)

- on WiFi or mobile data

I did not have a single freeze. But I stopped overclocking and I do not use any SetCPU profiles. Just min and max frequency and the governor. (128 / 998 / smartass2)

Surfing on WiFi most of the time and having 3g disabled since I have very bad reception.
[Desire Android Development] Gr4bov5ky:
I flashed the latest kernel (-110918-lsmod1) yesterday, it's fast.No freezes, no lags yet. The only problem is, when I'm using wifi then it's eating up the battery very fast.

Didn't try the wifin update yet, in other post was mentioned that it doesn't works.

Any ideas to wifi's battery greed?

Btw. Great work snq ,tobi! :)
[Desire Android Development] anderl78:
Hello!

I have to report random freezes with the new kernels. Till now, I used them all since 110911. Atm I'm on 110918-lsmod1.

The freezes occur on all kernels, while playing (tried angry birds, stupid zombies, pig rush) and surfing on the web (android browser). Usually I have to pull the battery...

I set the Vdd-levels to stock, to be sure there is no uv-problem:

echo '128000 950' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '245000 950' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '384000 975' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '422400 975' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '460800 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '499200 1025' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '537600 1025' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '576000 1050' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '614400 1075' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '652800 1100' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '691200 1125' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '729600 1150' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '768000 1175' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '806400 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '844800 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '883200 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '921600 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '960000 1250' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '998400 1275' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1036800 1275' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1075200 1275' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1113600 1300' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1152000 1300' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1190400 1300' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels

In frojo-roms I undervolted to 900 mV without problems...

- SetCPU: 384 - 998 mhz @smartassV2, no screen off profile

- ROM: Leedroid 3.3.3 HD port
[Desire Android Development] tobi01001:
Strange.. Just played like 15 levels of angry birds with some Apps updating in the background. other than few slight lags there was no freeze. I have a fresh install of LeeDrOiD 3.3.3-R5:

Full wipe, flashed rom, flashed sense 3.0 addon, flashed kernel...

Maybe you can do a adb logcat while playing?
[Desire Android Development] anderl78:
It happens not always... Tried it yesterday a few times. Sometimes it freezes, sometimes not... Strange thing, I know...
[Desire Android Development] tomurbanowicz:
I have some freezes on Winamp and Android Browser.
[Desire Android Development] snq-:
do they also happen when you lock freq (and vdd) using the performance gov?
[Desire Android Development] tobi01001:
I currently have a app called stabilitytest running. It's a stress test and supports scaling as well. Runs for 40 minutes now without any freeze...
[Desire Android Development] anderl78:
Atm I'm on my "dark2 mod" http://xdaforums.com/showpost.php?p=15734822&postcount=397 (Leedroid 3.3.x - thread)

I already implemented all 10 levels in the modded frameworks. Seems to work well. I get all the brightness -values (30, 40, 50, 70, 105, 120, 145, 170, 200, 255) with it. Looks pretty well I think :-).

atm its very cloudy here, cause of this I can not try the values/behavior in direct sun. If I get the chance, I will see, if I perhaps have to set higher brightness earlier/on brighter conditions... (modify the autobrightnessLevels)
[Desire Android Development] anderl78:
Good point! I will try and report back!
[Desire Android Development] t-minik:
the same here ! with 110916 and BravoS V7

sometimes, for some hours, wifi is sucking up battery then it returns to default consumption.

this night current widget showed me 5/6 hours at 30 to 90 mA then returns to normal 3 to 8 mA.

EDIT // I forgot, it did the same saturday morning, i returned to V06 kernel and there was the same issue.

I thought hardware was faulty because i didn't found some infos, but now that happened to others desire user, I think it can be a software issue to...

perhaps a market problem
[Desire Android Development] b-george:
I also have lags and freezes not only with snq all kernel I have tried has same problem. Snqs v06 based on locked sources was very good with no problem!
[Desire Android Development] anderl78:
Here is a log with smartassV2, freeze during play with stupid zombies (of course only for testing :) )

Logcat: http://db.tt/yOllSAJ

Kernel log: http://db.tt/dW11n2x

Performance gov test is on the way...
[Desire Android Development] tobi01001:
Maybe would be good to upload the kernel log as well.. :-)

May you can adb shell and cat /proc/kmsg and then get again in business with your stupid zombies... :-)
[Desire Android Development] tomurbanowicz:
Do You mean: zImage-v06 or flashable v05-to-v06 kernel image+modules update package?
[Desire Android Development] anderl78:
Yes, you are right! Stupid zombies - stupid anderl ;-)

I added a kernel log to my post above... Both with smartassv2
[Desire Android Development] PeQuEsan:
First of all, I want to thank snq- for his work. I've been using his kernels from first cooked ROM I used (Leedroid Froyo) till now (running AceSMod007 GB).

Talking about autobrightness, I post my current values for config_autoBrightnessLevels and config_autoBrightnessLcdBacklightValues, after some testing under my conditions...

<integer-array name="config_autoBrightnessLevels">
<item>41</item>
<item>100</item>
<item>150</item>
<item>195</item>
<item>226</item>
<item>321</item>
<item>641</item>
<item>1281</item>
<item>2601</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>30</item>
<item>45</item>
<item>60</item>
<item>70</item>
<item>100</item>
<item>155</item>
<item>180</item>
<item>255</item>
<item>255</item>
<item>255</item>
</integer-array>

My tests say that sensor is not going under 41, even in totally absence of light. On the other hand, as you can see, I don't want to have any problem watching my display under sunlight conditions... :P

BTW... What are values "config_autoBrightnessLcdBacklightValuesUp" and "config_autoBrightnessLcdBacklightValuesDown" for? I'm setting same levels as "config_autoBrightnessLcdBacklightValues", but I asume these values have a "reason to be there", which I don't know. Some kind of hysteresi?.

Thanks a lot for you work!
[Desire Android Development] P0MM3S:
stupid zombies seems to be a god way to reproduce those freezes, i also got 3 of them while playing it!
[Desire Android Development] tomurbanowicz:
How to flash from the newest kernet to V06? On the first page there is ony patch for "V05 to V06" of kernel.
[Desire Android Development] ZeGuitarist:
So, snq-, you heard the man... lol ^^
[Desire Android Development] tobi01001:
Well, with the latest kernel (lsmod) you'll have all level - even below 41..

Up and down are for hysteresis. Don't know exactly how or if it works but should lead to smoother brightness changes. Imo those values should represent the brightness between the current and the next step. Either for going down or for going up. But that's something to better ask in the adjust autobrightness thread since the kernel can do nothing about.
[Desire Android Development] zedmarcus:
Top of page 58, comment #571.

I believe that's the most recent kernel from snq.
[Desire Android Development] anderl78:
And a kernel log with performance gov @ 998 mhz:

http://db.tt/6buE3ga
[Desire Android Development] anderl78:
Yep, stupid freezes :D
[Desire Android Development] tobi01001:
Could you maybe pull /proc/last_kmsg after a freeze and after reboot?

Just played stupid zombies (of course for testing only :-)). How long will I have to play in order to get a freeze?
[Desire Android Development] P0MM3S:
of course! :D hm, thats quiet different, sometimes around 5 -10 minutes, sometimes it gets stuck @ the loading screen, right after choosing a level!

(can't post a kmsg right now, i'm @ work )
[Desire Android Development] anderl78:
The file I attached is the ksmg log after a freeze.

Don't know, how long you have to play. Sometimes there is a freeze after a few minutes, then after a longer time (maybe 30 min) and perhaps there is even no freeze...
[Desire Android Development] snq-:
thanks but those incomplete logs only show that your adb session ended
[Desire Android Development] PeQuEsan:
Are you talking about this thread?

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

I learned there how to play with autobrightness levels...

BTW, When I finish doing more stability tests under AceSMod007, I'll test this modified kernel. Thanks a lot.
[Desire Android Development] anderl78:
Hmm, seems to be a problem with my pc here at work... Just noticed he ends the usb-connection from time to time... Pulled the last_kmsg from the phone. Just freezes again with stupid zombies... http://db.tt/K3x2QL2
[Desire Android Development] teorouge:
Massive battery drain here, too. 110918 (

not

lsmod) + Wifi N patch, 9 hours to go 100%-->shutdown. Couldn't see what ate my battery the most before phone turned off, drain was accettable with older kernels... :(
[Desire Android Development] ziggy1001:
I have had random high drain on wifi with the "N" patch in the past
[Desire Android Development] elliottg61:
have you tried changing cpu governors? when mine was on ondemand i used to only get about 8-9 hours, but i changed it to smartass v2 and can now easily get 2 days:eek: