yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] paulk_:
Request sent 3!

... and approved! :P
[Nexus One Android Development] nurre:
Why would you do something like that...

Your doing a open source development model, and then requiring people to write android related tweets (and use twitter) in order to keep track of changes.

I've been an open source developer for about 15 years, I do it for a living. I've made android related apps as well, and they are open source. But I don't use twitter for anything but keeping up on a few android related posts. And I generally only keep attention to my own twitter rss feed, I don't use the application/service at all. And your effectivly locking me out of your service :/ (yes, not allowing people to check for updates/get changelogs etc is pretty much telling em to leave).
[Nexus One Android Development] intersectRaven:
Simply to weed out any spam bots. If you don't want to follow or use twitter, my updates are pretty much out there on my MediaFire folder for anyone to see. I'm just saying that if you want to be updated with "breaking news" updates I won't be posting here and instead will be announcing on my twitter account. Alternatively, you could just monitor my MediaFire folder for new uploads. It's just that I want this thread to have official updates to what I consider stable releases and not experimentals or minor updates. :)
[Nexus One Android Development] bewA:
which is...? :D
[Nexus One Android Development] intersectRaven:
I just updated the OP with the info. :)
[Nexus One Android Development] Gilg@mesh:
@intersectRaven

do you recommend using latest 2.6.35 kernel or stick with latest "stable" 2.6.34 until 2.6.35 becomes "final"? thanks
[Nexus One Android Development] watercool:
hm, any special thing to do for usb mounting? (.35 rc3 + modaco r20)

When plugging in nothing happens at my phone and my pc adds a new drive but nothing happens there too when clicking on it.

edit: uh, my bad.. NOT using the latest version i think :D currently downloading...

edit2: everything ok.. sorry :)
[Nexus One Android Development] intersectRaven:
I recommend sticking with the stable .34. The .35 is just for those people who, like me, are latest update freaks. :p
[Nexus One Android Development] Chahk:
I'll see you at the next LUF meeting ;)
[Nexus One Android Development] liem107:
sorry if t is an obvious question : if 800mv causes over consumption due to loss of signal and 925 only provides moderate gains, why not making a kernel around 850 mv? There should be a sweet spot combining good signal stability and battery savings? no? unless there is no intermediate step between 800 and 925 ? sorry if it was answered before.
[Nexus One Android Development] watercool:
Just reporting 2 perfect running n1 with the latest version .35. Anyone has issues with them?
[Nexus One Android Development] superg81:
can you be more specific which you are running.i see more than one on his folder uploaded today.
[Nexus One Android Development] intersectRaven:
Well, to answer your question, upon testing between different voltages, 800 and 925 offer the best values since there is a negligible difference in battery life with the voltages in between them. :)
[Nexus One Android Development] boesky:
In case anybody's wondering, this kernel is def better than stock.

Before: 7 - 8% drain per 40 minutes (music playback only, 3G off)

After: 5% per 40 minutes (same as above)

Also, 10% drain per 40 minutes of video playback. Didn't try it with the stock kernel, but it's just something to know.

An improvement, but I've a long way to go! :D
[Nexus One Android Development] intersectRaven:
Minor update!

20100701_09XX_.34:

- compiled from refreshed source

Here're the links:

20100701_09XX_.34:

BFS:

925mV -> http://www.mediafire.com/?zomzjm2mdqn

800mV -> http://www.mediafire.com/?zjgmtet0twt

CFS:

925mV -> http://www.mediafire.com/?j2jvj2tyjta

800mV -> http://www.mediafire.com/?mnzzj1ntdjn

***warning: didn't get to test this one since I'm busy at work so please backup before applying. :)
[Nexus One Android Development] adamgibbo:
Is anyone trying intersectRaven's Kernel on test0?...how is it?
[Nexus One Android Development] Micksta:
I would like to know if anyone has tried this with CM6-alpha1?

Thanks
[Nexus One Android Development] pzumk:
Someone already tried the newest kernel?
[Nexus One Android Development] mrandroid:
Hey I updated the site but I kept your Repo URL the same...

http://www.myhangoutonline.com/repositories/intersectraven/

I changed from joomla to wordpress for better performance.
[Nexus One Android Development] sir*mez:
yes new kernel works on cm6-t0.
[Nexus One Android Development] bewA:
I'm using the Latest 925mV CFS 2.6.35 Kernel on CM6 Alpha 1 with no problems!

bit early to comment on battery usage but its nice and stable :D
[Nexus One Android Development] fleebailey33:
i wish it was in Rom manager. *shrugs*
[Nexus One Android Development] boesky:
here's my experience -

Usage breakdown:

display 72%

cell standby 8%

phone idle 6%

android system 4%

mediaserver 4%

browser 3%

voice calls 3%

After 14H 35 min I had 9% left.

3G on and off - only when needed

Personally, it isn't spectacular. But considering I was surfing most of the morning and flashing roms all afternoon, pretty good.
[Nexus One Android Development] martin0285:
Hell ya!!!
[Nexus One Android Development] bigmike2424:
i need some help, im running cm6 and flash newest 925v kernel through recovery and went to set cpu but i still can not overclock it,so i re did the flash using adb and still no luck, in settings>about it shows the kernel but set cpu will not let it overclock
[Nexus One Android Development] watercool:
there is no overclock in this kernel, probably you are at the wrong thread and you search for pershoots oc kernel? Or Wilmonks HAVS OC Kernel?
[Nexus One Android Development] THATTON:
:eek::eek::eek::eek::rolleyes::rolleyes::D:D:D:D
[Nexus One Android Development] scalp42:
Quick question :

When I flash new kernels, how can I come back to the "original" one, lets say from FRF91 or whatever ?

Do I have to flash the original Google rom again ?

Thank you in advance ;)
[Nexus One Android Development] intersectRaven:
You can either do that or extract the boot.img and necessary modules from the ROM and use fastboot and adb to put them into your device. Personally, I think flashing the ROM is faster. OR you could just perform a nandroid backup before and restore it afterwards which is THE safest way. :)
[Nexus One Android Development] brian6685:
Using the newest .35 rc3 with kang-o-rama froyo final, and its working great!. Linpack is actually getting faster speeds then the .34 kernels. Great work!
[Nexus One Android Development] lorloff:
Hey IR. For some reason the wifi sleep policy doesn't work correctly for me on .34 with froyo roms. My wifi will disconnect(policy is set to never disconnect) and then the only way to reconnect is to toggle wifi off and on. Let me know what you need from me to help troubleshoot.
[Nexus One Android Development] ibegary:
I'm having this issue as well but I think its with froyo not the kernel. Dunno for sure.
[Nexus One Android Development] Kolyk:
Ребят помогите, только что обнаружил что после установки 2.6.35_AVS-800mV_CFS_20100702_0948 в Kang-o-rama 0.9 Final SP2 у меня перестал работать WiFi, откаты не помогают ((, уже пробовал устанавливать предыдущие радио froyo-radio-32.36.00.28U_4.06.00.02_2, не помогло (((, может кто знает как моей беде помочь ?
[Nexus One Android Development] apnoia:
По русски тут вряд ли прочтут. English please. Just try to search . WiFi issue discussed already here.
[Nexus One Android Development] Kolyk:
After kernel setting 2.6.35_AVS-800mV_CFS_20100702_0948 WiFi does not work, rollbacks do not help that to me to do?
[Nexus One Android Development] intersectRaven:
What ROM are you using?
[Nexus One Android Development] knightnz:
Running .35 on CM6-a1 here and it's good as gold, no WiFi issues. 925mV BFS.
[Nexus One Android Development] Kolyk:
When stitched a new kernel stood Kang-o-rama 0.9 Final SP2, then tried CM6 alfa, FRF91 Stock, but all without changes does not work wifi (((
[Nexus One Android Development] intersectRaven:
Try to push the bcm4329.ko file manually to /system/lib/modules. I recently experienced a scenario where the module isn't pushed by the update.zip. :)
[Nexus One Android Development] Kolyk:
I badly understand English language, Try to push the bcm4329.ko file manually to/system/lib/modules, means to rewrite the given file from your kernel? I re-recorded but the same result, at pushing wifi the error writes.
[Nexus One Android Development] intersectRaven:
So there was an error when you tried adb push? What error was it? :(
[Nexus One Android Development] Kolyk:
Error when in adjustments I include wifi, process com.android.settings does not answer
[Nexus One Android Development] intersectRaven:
I'm having difficulty understanding you (no offense meant). Can you just post a screenshot of the error when using adb push? :confused:
[Nexus One Android Development] apnoia:
Kolyk, have you tried to wipe dalvik, cache and/or full wipe?

Напишите мне по русски в private
[Nexus One Android Development] elnoxvie:
I am using .35 on kang-o-rama SP2.

So far the battery life has far exceeded my expectation.
[Nexus One Android Development] bewA:
I'm not getting great battery life on CM6-A1 but this is more down to CM6 being alpha I think.
[Nexus One Android Development] vegetaleb:
Yeah CM 6 is nice but alpha is alpha and I will install Paul's r21 prebake once it's out.

CM roms always used more juice than other roms anyway
[Nexus One Android Development] Rafase282:
What is the difference between CFS and BFS?
[Nexus One Android Development] mtw4991:
FACEPALM....is your search button broken?
[Nexus One Android Development] chobie:
my wifi shows error after flashing :(
[Nexus One Android Development] Chahk:
I'm staying om MCR r21 until CM6 incorporates Apps2SD.

With that said, IR's .33.5 kernels have been very stable, and the CFS 925mV combo yields the best battery life on my N1.

I'm not seeing this on 2.6.35_AVS-925mV_CFS_20100705_2204 version. How exactly are you flashing it? A few posts back IR said that sometimes bcm4329.ko wifi module fails to apply via update.zip. Try pushing it manually.
[Nexus One Android Development] Kolyk:
I was stitched 2.6.35_AVS-800mV_CFS_20100702_0948 by a kernel then for me have refused to work wifi, adb push bcm4329.ko/system/lib/modules I did errors was not, but wifi and does not work
[Nexus One Android Development] Chahk:
Так значит не выдает никакой ошибки когда ты делаешь "adb push"? Попробуй еще раз. Вытащи bcm4329.ko из архива и положи в корень C:\ драйва. Теперь открй командную строку и дай следующие команды:

cd c:\Android SDK\Tools\ (или где там у тебя ADB установлен)
adb remount
adb push c:\bcm4329.ko /system/lib/modules/bcm4329.ko
adb shell reboot

После того как телефон перезагрузится попробуй включить WiFi.
[Nexus One Android Development] Kolyk:
Сделал все четко по пунктам, после перезагрузки девайса при включении WiFi пишеться следующие -Приложение Настройки (в процессе com.android.settings) не отвечает. WiFi по прежнему не работает (((
[Nexus One Android Development] Chahk:
Очень странно. А в журнале отладки что-то интересное есть? Подключи телефон к компу через USB, в командной строке запусти команду "adb logcat", потом попробуй включить WiFi, когда выкинет ошибку - остонови вывод (Ctrl + C) и скопируй где-то 20-30 последних строк сюда.
[Nexus One Android Development] Kolyk:
m.android.internal.view.IInputMethodClient$Stub$Proxy@452736b8

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): Intent Received

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): state == idle | sc

anning | failed

D/WifiService( 423): ACTION_BATTERY_CHANGED pluggedType: 2

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): Intent Received

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): state == idle | sc

anning | failed

I/wpa_supplicant( 1257): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00

:00:00

E/wpa_supplicant( 1257): Failed to disable WPA in the driver.

D/dalvikvm( 818): GC_EXPLICIT freed 255 objects / 16000 bytes in 53ms

D/WifiStateTracker( 423): Reset connections and stopping DHCP

D/WifiStateTracker( 423): Disabling interface

E/WifiHW ( 423): Supplicant not running, cannot connect

D/dalvikvm( 805): GC_EXPLICIT freed 58 objects / 2904 bytes in 53ms

E/WifiHW ( 423): Supplicant not running, cannot connect

I/ActivityManager( 423): Starting activity: Intent { act=android.intent.action.

MAIN cmp=com.android.settings/.wifi.WifiSettings }

I/ActivityManager( 423): Displayed activity com.android.settings/.wifi.WifiSett

ings: 340 ms (total 340 ms)

E/WifiHW ( 423): Supplicant not running, cannot connect

V/WifiStateTracker( 423): Supplicant died unexpectedly

D/WifiStateTracker( 423): Reset connections and stopping DHCP

D/WifiStateTracker( 423): Disabling interface

D/NetworkStateTracker( 423): setDetailed state, old =DISCONNECTED and new state

=DISCONNECTED

D/WifiStateTracker( 423): Reset connections and stopping DHCP

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): Intent Received

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): removing disconnec

ted wifi notification

D/WifiStateTracker( 423): Disabling interface

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): Intent Received

I/com.schwimmer.android.wifistatus.WifiStatusReceiver( 818): removing disconnec

ted wifi notification

^C

C:\Users\Основной>

Тут ошибку не выкинуло просто WiFi отключился, если нужно с ошибкой могу другой сделать но думаю и в этом логе есть на что обратить внимание
[Nexus One Android Development] chobie:
I flashed thru recovery. Regular flashing =p

I tried monks' kernel but still wifi says error and wont turn on.

Last resort was to reflash my rom that included the kernel (Kang-o-rama)

And why is everyone chatting in russian? LOL
[Nexus One Android Development] knightnz:
Didn't you hear? They're using internet forums for their plans now!

AVS-X?
[Nexus One Android Development] zombiess:
just reporting that I'm getting about fifteen percent better battery life on the july 1 925mv cfs kernel than the one previous to it. phone use is identical to previous.
[Nexus One Android Development] Chahk:
Sorry, we'll stop passing encrypted spy messages now :p

Just wanted to help a guy out quickly, but apparently the problem he's experiencing is something that someone more qualified than I should try to resolve. I'm not seeing anything obvious in the logs.
[Nexus One Android Development] intersectRaven:
Please don't use the AVS-X versions. They're test versions which I upload just in case I need to download them away from my PC. :)
[Nexus One Android Development] Kolyk:
And how to me to be? What to do with my problem?
[Nexus One Android Development] Chahk:
I'll send you a PM.
[Nexus One Android Development] decayed.cell:
2.6.35_AVS-925mV_BFS_20100703_1834 is giving me major crashing problems on FR91. Also USB mounting seems to be broken. On the positive side, my boot up time has sped up ENORMOUSLY lol
[Nexus One Android Development] knightnz:
Whoops :) On the upside, it seems to work ok. I'll go back to a non-X version just in case though.
[Nexus One Android Development] boesky:
Lol just use CFS then? Technically, it is more stable :cool:
[Nexus One Android Development] hah2110:
Lol I tried too. Battery was great overnight, lost 1.2%/hour. Then I went to a meeting, didn't touch the phone for 3 hours and lost 67% LOL
[Nexus One Android Development] intersectRaven:
.34 and .35 kernels updated! They can be found on my MediaFire folder. (too busy to post links...) :p
[Nexus One Android Development] Kolyk:
Prompt that still it is possible to try to undertake what has earned WiFi, after an unsuccessful insertion of a kernel.
[Nexus One Android Development] intersectRaven:
Btw, what ROM are you using? The wifi drivers of .34 and .35 are reliant on an updated wpa_supplicant so maybe the ROM you're using has an outdated one. :confused:
[Nexus One Android Development] Kolyk:
Has now put FRF91 STOCK, without Root etc. How to check up updatings wpa_supplicant?
[Nexus One Android Development] intersectRaven:
Try using my kernel now. It should work with the built-in wpa_supplicant of FroYo. :)
[Nexus One Android Development] Zenoran:
does anyone know how this kernel compares to the new OC'd kernel in CM6 nightly builds?
[Nexus One Android Development] limouren:
Using stock FRF91 (not rooted), when applying update.zip through recovery, it showed "E: signature verification failed". Tried with both

2.6.34_AVS-800mV_BFS_20100708_1042.zip, and

2.6.35_AVS-800mV_BFS_20100708_1010.zip

but no luck.

I guess I'm doing it right? Just renamed the ZIPs to update.zip. Sorry for disturbing.
[Nexus One Android Development] hjlow:
You need root for one thing
[Nexus One Android Development] limouren:
Oops, sorry for fooling around... :o
[Nexus One Android Development] hah2110:
These aren't OCed...
[Nexus One Android Development] carblanco:
I think these are OC but you have to go to setCPU, check it.
[Nexus One Android Development] hah2110:
No. Raven does NOT do OC.
[Nexus One Android Development] pzumk:
No.

Check the first post (I'm not sure if it's there) and search for "Overclock" and "OC" in the thread.
[Nexus One Android Development] Kolyk:
LeoFroYo BETA 7, 2.6.35_AVS-925mV_CFS_20100708_0955 - and has not earned WiFi (((, what it is possible to try to undertake for this purpose what has earned WiFi?
[Nexus One Android Development] dessanct:
If the you used the update.zip method and the WiFi doesn't work, try the manual method.

Instructions for zImage and bcm4329.ko driver extracted from the update.zip(from command line):

1.) adb remount

2.) adb push bcm4329.ko /system/lib/modules

3.) adb reboot bootloader

4.) fastboot flash zimage zImage

5.) fastboot reboot
[Nexus One Android Development] Kolyk:
Has made all under the instruction of problems was not, but the same result ((does not work WiFi
[Nexus One Android Development] christiankk:
Then I am afraid no-one can help you.:(
[Nexus One Android Development] erikiksaz:
Hah, woops! I tried one out accidentally--I was wondering why my phone was running so slow. Plus, I was running 3g and wifi at the same time!
[Nexus One Android Development] carblanco:
Ok, sorry, I was talking about CM6 kernel :rolleyes:
[Nexus One Android Development] brian6685:
Anyone use this kernel with the desire rom? If so, which version do you use? I'm using 33.5 cfs and it seems to make it faster and a lot better battery life. Am I able to use .34 kernel with it? Figure I would ask before I take the time to try them all out.
[Nexus One Android Development] THATTON:
Then why did you post this in IntersectRaven's kernel thread? I'm a little confused?
[Nexus One Android Development] carblanco:
because

Anyway, sorry again.
[Nexus One Android Development] Pochemuchka1977:
Battery drain

I have tried both latest versions .34 and .35 from your mediafire folder

The .34 was 2.6.34_AVS-925mV_CFS_20100708_1028.zip and the .35 was

2.6.35_AVS-925mV_CFS_20100710_0036.zip. I am running CM 5.0.8

When the phone is idle, i have checked the the kmsg to see the battery use

The .35 kernel gave me the following results:

<6>[ 2602.049713] batt: 100%, 4133 mV, -3 mA (-5 avg), 31.3 C, 1356 mAh

<6>[ 2602.353118] batt: 100%, 4133 mV, -3 mA (-4 avg), 31.1 C, 1356 mAh

<6>[ 2603.038513] batt: 100%, 4123 mV, -3 mA (-11 avg), 31.0 C, 1356 mAh

<6>[ 2603.765716] batt: 100%, 4133 mV, -4 mA (-4 avg), 30.8 C, 1355 mAh

<6>[ 2973.096221] batt: 98%, 4118 mV, -9 mA (-13 avg), 29.8 C, 1340 mAh

<6>[ 2973.767242] batt: 98%, 4109 mV, -4 mA (-5 avg), 29.6 C, 1340 mAh

<6>[ 2974.191070] batt: 98%, 4114 mV, -5 mA (-5 avg), 29.6 C, 1340 mAh

<6>[ 2974.895172] batt: 98%, 4109 mV, -15 mA (-6 avg), 29.3 C, 1340 mAh

<6>[ 2984.932189] batt: 98%, 4118 mV, -45 mA (-10 avg), 29.3 C, 1340 mAh

<6>[ 3002.341613] batt: 98%, 4123 mV, -4 mA (-9 avg), 29.3 C, 1339 mAh

<6>[ 3003.137298] batt: 98%, 4123 mV, -4 mA (-5 avg), 29.3 C, 1339 mAh

<6>[ 3003.380310] batt: 98%, 4123 mV, -4 mA (-6 avg), 29.3 C, 1339 mAh

<6>[ 3004.200805] batt: 98%, 4118 mV, -8 mA (-7 avg), 29.3 C, 1339 mAh

<6>[ 3004.426147] batt: 98%, 4123 mV, -5 mA (-5 avg), 29.3 C, 1339 mAh

<6>[ 3005.480926] batt: 98%, 4123 mV, -5 mA (-6 avg), 29.6 C, 1339 mAh

<6>[ 3005.671051] batt: 98%, 4118 mV, -8 mA (-6 avg), 29.6 C, 1339 mAh

<6>[ 3010.106689] batt: 98%, 4123 mV, -32 mA (-10 avg), 29.6 C, 1339 mAh

<6>[ 3011.133728] batt: 98%, 4109 mV, -34 mA (-7 avg), 29.6 C, 1339 mAh

<6>[ 3021.575164] batt: 98%, 4118 mV, -5 mA (-7 avg), 29.7 C, 1339 mAh

<6>[ 3024.888092] batt: 98%, 4118 mV, -5 mA (-4 avg), 29.8 C, 1339 mAh

<6>[ 3025.571624] batt: 98%, 4109 mV, -4 mA (-5 avg), 29.8 C, 1337 mAh

<6>[ 3025.740234] batt: 98%, 4118 mV, -6 mA (-5 avg), 29.8 C, 1337 mAh

<6>[ 3025.993713] batt: 98%, 4123 mV, -4 mA (-5 avg), 30.0 C, 1339 mAh

<6>[ 3026.233398] batt: 98%, 4123 mV, -4 mA (-6 avg), 30.1 C, 1339 mAh

<6>[ 3028.206024] batt: 98%, 4118 mV, -9 mA (-8 avg), 30.1 C, 1339 mAh

<6>[ 3031.627410] batt: 98%, 4118 mV, -4 mA (-5 avg), 30.1 C, 1339 mAh

and the .34 kernel gave me -44 mA in the average.

The phone was with the same configuration and same programs running. The WiFi was on and connected (with sleep policy Never). The bluetooth was off

I am wondering what might be the reason for such different behavior between these two kernels
[Nexus One Android Development] chattyducky:
How did you get this? not trying to disturb the chain but really noob with this.
[Nexus One Android Development] Pochemuchka1977:
Install Android SDK and drivers on your PC.

Connect the phone to the PC and make sure the PC sees it (by running command adb devices)

After this run the command adb shell "cat /proc/kmsg |grep 'batt:'" and you will get it
[Nexus One Android Development] mindfrost82:
Your kernels have been the best for battery life, but within the last 2 months, everytime I install it I seem to get a touchscreen issue where I can't unlock the phone. I know a few others reported it too, but nobody else seems to be mentioning it anymore.

I've always been using the 925 CFS version, and I was using the .34 kernel, but I've tried your last two .35 versions with the same results.

When it happens, I go to turn the screen on and can't slide to unlock it. If I press the power button again, the screen just dims and doesn't actually shut off. Pressing it again will light it back up, but I still can't do anything. Eventually I can get the screen to shut off but then it usually doesn't turn back on. The only fix is a battery pull.

I've been running Paul's r21 Froyo ROM, but I've had this issue with every Froyo ROM I've tried.

I usually have WiFi on and never sleeping, and usually when I notice this problem, its when I go to a store or somewhere that doesn't have WiFi. It'll still be on but not connected. So far its never happened at home or at work where I have WiFi.

After this happens, I've been flashing pershoot's kernels (.34 and .35) and its never happened on his. I also don't run any apps to overclock his. I just prefer your's for the better battery life.
[Nexus One Android Development] Gilg@mesh:
@mindfrost82

Thats happens to me too! very annoying! :)
[Nexus One Android Development] Pochemuchka1977:
This happens to me too, I thought it's CM problem, but it happens both on 5.0.8 and 6.0.0 rc1 running .34 and .35 kernels. I have managed to get the logs from the phone AFTER this happened. I had both BT and wifi on but not connected. With wifi only it never happened.

logcat - http://pastebin.com/EwgWpiQz

kmsg - http://pastebin.com/0nbH47pr

BTW, it's possible to reboot the phone by pressing trackball + volume down + power buttons.
[Nexus One Android Development] mindfrost82:
Hopefully we can get it fixed! I hardly ever have BT on and I know BT wasn't on when its happened to me in the past.