yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] hah2110:
Weird theory. Anyone notice a difference as to battery life when their phone is in their pocket vs not? SetCPU reports 35C when in my pocket (or as soon as I remove it) and about 27C when on a counter. I think it negatively affects battery. Does anyone else have the problem where they will have great battery life up until a certain point and then, out of no where, it starts dropping like nuts?
[Nexus One Android Development] cedricj:
Phone calls using all battery

Hello,

Was at 100 percent and after a 22 minutes call down to 45 :(:(

Will update to the newest kernel and see the difference! using the 1505 for now...

Best
[Nexus One Android Development] hah2110:
This is kind of standard I thought with the N1...
[Nexus One Android Development] Breece:
Ok def. something wrong here... cellphone froze twice... had to.pull the battery

Nexus one, cyanogen 5.0.6 newest .34 kernel
[Nexus One Android Development] jblazea50:
on .33 kernels of Raven's as well as Kmobs experiment kernels, i would lose about 10% during an hour of browsing so i doubt that's the standard
[Nexus One Android Development] jblazea50:
anyone interested in finding out the new features of .34 can find it here: What's new in .34 kernel

Raven, it says in the article that the new power saving technique is deactivated by default; is there anyway to activate it and run it on one of your kernels and test to see if there's any benefit of having that feature activated?

thanks
[Nexus One Android Development] Markdental:
Thanks for that article!
[Nexus One Android Development] intersectRaven:
Thanks for the article! Browsing through it, in my understanding, the new power saving technique seems applicable only to PCI devices so I don't think enabling it will do much on our phones. The file referred to in the git commit log in the article isn't even compiled when compiling for the N1. :)

Reading...reading...reading...hmmm...this article just gave me an idea for a .33 improvement... :D
[Nexus One Android Development] jblazea50:
ok, thanks; yeah i don't know much about these things so i figured i ask you and see if anything can be done

improve .33, well, looking forward to it
[Nexus One Android Development] mtw4991:
Maybe I missed it, but what is the difference between 2.6.33.4 925mV CFS 0514_1425 and 2.6.33.4 925mV CFS 0517_1015? I looked at the 1st page twice and can't tell, lol:confused:
[Nexus One Android Development] Buck Shot:
so I was using ur last 33.3 CFS800mV. I switched to the 925 becuase of the so called "myth" theories and I burned down to 71% in less than 2 hrs with some decent use as far as tweeting and facebook. I immediately switched back and charged up . awaiting for the complete stable .34

great work
[Nexus One Android Development] codington:
No luck making a VPN connection (L2TP)

Has anyone successfully made a VPN connection with any of these kernels? I am using 12vpn.com and trying to connect with L2TP (with IPSec PSK). I was able to connect with Enomther's 2.6.32.12 kernel under the 1.9.1 ROM. I have tried several different releases of the .34 kernels with no luck making a VPN connection - it just times out unable to connect. A forum search came up empty so I am posting for help. Cheers from China.
[Nexus One Android Development] mer6:
http://lifehacker.com/5375325/an-exhaustive-guide-to-saving-your-smartphones-battery

First tip ^_^

It's not weird, it's right. Your body constantly produces heat that's given off through the skin and thus diffused through your pockets.
[Nexus One Android Development] seanowns:
Took all day, but having many wakelock type problems with .34. I turn on screen and touchpad basically dead. Eventually i can use trackball to reboot, but happened 3rd time now.

The .34 is soooo smooth though. Pains me to go back!
[Nexus One Android Development] sovereignty68:
I tested 33.3 CFS 800mv so called ULV and burned down to 80% in an hour with twitter and facebook, so I switched back to 33.4 925mv. So 33.4 is stable to me.
[Nexus One Android Development] Buck Shot:
so how is the .34 ? Should I upgrade yet from .33?
[Nexus One Android Development] schahr01:
Doesn't sound like it yet. .33.4 = stability

After being on the Apr-29 800mv build until things quieted for awhile, I decided to try an updated kernel. So far so good results with .33.4 925mv CFS - Stable, comparable batt loss (~1%/hour idle, ~1% for every 3 minutes of 720x488 MP4 video :))
[Nexus One Android Development] schahr01:
Interesting. As far as I can remember, I never carried my phone in my pocket. Always sported the geek look - Always had a belt holster. Now I actually have 2, one on each side - Nexus One and a work Blackberry bold 9700.
[Nexus One Android Development] hah2110:
And how is your battery?
[Nexus One Android Development] mer6:
1%/hour idle? Jesus man I'm losing ~5%/hour
[Nexus One Android Development] jcky000:
I just flashed the 20100517_0731_.34 925mv and i cant connect to wifi access point that's has WEP with it, but open network works fine.

Anyone have idea?:confused:
[Nexus One Android Development] Realtyem:
I have a question for everyone that has been having problems with unresponsive launcher process. Are you using setCpu with the Active widget? I found that uninstalling that app apparently fixed my lagging. My worst lag always seemed to occur after bringing the phone out of standby. Just wondering if anyone else noticed that correlation yet. :) Only reason I bring this up here is because I noticed it on this kernel first; I miss the snappy responsiveness it had too lol.
[Nexus One Android Development] Realtyem:
I don't seem to have any problems with my wifi on WEP. Maybe something else related?
[Nexus One Android Development] sir*mez:
Did you have a profile forwhen it slept or screen off? If so what was it?
[Nexus One Android Development] Realtyem:
I believe I did at one point, but while trying to get rid of my lag problem I disabled all profiles. The problem still existed then. I was so fed up with the lag that I was ready to be completely rid of whatever was causing the problem. I eventually had to go into terminal and use top to find out what user process was using 100% cpu for almost a full minute whenever I came out of standby or whenever backing out to the home screen. I suppose I could have just tried to use the old-school widget but I wasn't really in the mood to test out how far I could push the solution. I don't find I have a use for setCpu anyways since I almost always used ondemand. Just was curious if anyone else that had that lag problem had put those two ideas together. I must have tried a dozen of the last batch of kernels thinking it was an instability, I even went back to stock to see if i could duplicate it(without root though it wouldn't install so the problem didn't manifest). Stock CM5.0.6 didn't seem to have it either...at first.
[Nexus One Android Development] die-hard:
Can I install this kernel on modaco desire rom?

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] Docmjldds:
Works for me. Referring to latest .33.4. Works on Desire R22paul as well as NazTech Beta 11 I currently have installed. With Naz, I currently switched to termana's .34 since he is using wavelocks in his kernel, which plays nice with Desire, as well as having better battery. Again, Raven's latest .33.4 was rock solid on any Desire setup. I only mention Termana if you absolutely want to use the .34 updated kernel.
[Nexus One Android Development] ratson:
for best battery life what other settings you prefer? (i use Juicedefender to minimize my 3g online time while phone sleeps).

do you make any other steps? choosing a good kernel is one part, setting up the phone properly is also very important ;)

please share your experiences/ideas.

other question: how much is music player draining in background if phone is put to sleep?
[Nexus One Android Development] mikechw:
Re: [.33.4 & .34]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/17/2010 07:59am

My nexus hanged while using latest 925mV,.34 kernel,cyanogen 506, WiFi tethering 2.0 pre10

There were no problem with previous .33 kernel.

I have to take out the battery to reboot the phone

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] hah2110:
Hmm.... On 0503 1638 800 CFS, been 9 hours and still at 100%. WOW
[Nexus One Android Development] mtw4991:
Shutting your phone off doesn't count!:):p
[Nexus One Android Development] hah2110:
Haha... Nope. Phone wasn't off. It was sleeping. Received 15+ TD emails and had Klaxon running for an hour. Is there any way to check mAh from the phone without plugging it in and running a Logcat? The fact that this is still at 100% (I know sometimes on a new kernel it can stay at 100% for a long time, but not this long) either means the battery is more efficient at 100% OR there is a huge problem with the battery readings.
[Nexus One Android Development] m00moo:
Re: [.33.4 & .34]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/17/2010 07:59am

did u wipe the battery stats after flashing the kernel?
[Nexus One Android Development] hah2110:
Yes.......
[Nexus One Android Development] theloginwithnoname:
OS Monitor (from market) contains this in its Messages tab - you can filter on "batt" too, very useful.

If I were a betting man I'd put a *lot* on the latter being true...
[Nexus One Android Development] hah2110:
Here is the streamlined OS Monitor:

5/18/2010 10:15	-11 mA (-17 avg)	1411 mAh

5/18/2010 10:15	-5 mA (-23 avg)	1411 mAh

5/18/2010 10:15	-5 mA (-5 avg)	1411 mAh

5/18/2010 10:15	-5 mA (-5 avg)	1411 mAh

5/18/2010 10:15	-5 mA (-13 avg)	1411 mAh

5/18/2010 10:15	-5 mA (-5 avg)	1411 mAh

5/18/2010 10:15	-7 mA (-5 avg)	1411 mAh

5/18/2010 10:15	-5 mA (-6 avg)	1409 mAh

5/18/2010 10:15	-5 mA (-5 avg)	1409 mAh

5/18/2010 10:15	-115 mA (-28 avg)	1409 mAh

5/18/2010 10:15	-115 mA (-28 avg)	1409 mAh

5/18/2010 10:15	-9 mA (-16 avg)	1409 mAh

5/18/2010 10:16	-5 mA (-12 avg)	1409 mAh

5/18/2010 10:16	-6 mA (-5 avg)	1409 mAh

5/18/2010 10:16	-5 mA (-5 avg)	1409 mAh

5/18/2010 10:16	-6 mA (-5 avg)	1409 mAh

5/18/2010 10:16	-5 mA (-5 avg)	1409 mAh

5/18/2010 10:16	-5 mA (-5 avg)	1408 mAh

5/18/2010 10:16	-31 mA (-6 avg)	1408 mAh

5/18/2010 10:16	-39 mA (-12 avg)	1406 mAh

5/18/2010 10:17	-35 mA (-66 avg)	1406 mAh

5/18/2010 10:17	-5 mA (-7 avg)	1404 mAh

5/18/2010 10:17	-22 mA (-5 avg)	1404 mAh

5/18/2010 10:17	-5 mA (-5 avg)	1404 mAh

5/18/2010 10:17	-5 mA (-5 avg)	1404 mAh

5/18/2010 10:17	-5 mA (-5 avg)	1404 mAh

5/18/2010 10:17	-10 mA (-12 avg)	1403 mAh

5/18/2010 10:17	-5 mA (-24 avg)	1403 mAh

5/18/2010 10:17	-6 mA (-6 avg)	1403 mAh

5/18/2010 10:17	-5 mA (-6 avg)	1403 mAh

5/18/2010 10:17	-5 mA (-5 avg)	1403 mAh

5/18/2010 10:17	-7 mA (-6 avg)	1403 mAh

5/18/2010 10:18	-6 mA (-6 avg)	1401 mAh

5/18/2010 10:18	-32 mA (-197 avg)	1400 mAh

5/18/2010 10:18	-6 mA (-6 avg)	1400 mAh

5/18/2010 10:19	-83 mA (-63 avg)	1398 mAh

5/18/2010 10:19	-6 mA (-21 avg)	1398 mAh

5/18/2010 10:19	-5 mA (-6 avg)	1398 mAh

5/18/2010 10:20	-245 mA (-56 avg)	1396 mAh

5/18/2010 10:21	-243 mA (-233 avg)	1393 mA

5/18/2010 10:21	-7 mA (-161 avg)	1392 mAh

5/18/2010 10:22	-169 mA (-6 avg)	1390 mAh

5/18/2010 10:23	-134 mA (-249 avg)	1388 mA

5/18/2010 10:23	-128 mA (-161 avg)	1387 mA

5/18/2010 10:24	-8 mA (-20 avg)	1385 mAh

5/18/2010 10:24	-253 mA (-7 avg)	1384 mAh

5/18/2010 10:25	-302 mA (-137 avg)	1380 mA

5/18/2010 10:25	-6 mA (-178 avg)	1379 mAh

5/18/2010 10:26	-39 mA (-184 avg)	1377 mAh

5/18/2010 10:26	-5 mA (-20 avg)	1376 mAh

I just dropped to 99%. What does the center column mean?
[Nexus One Android Development] tsouza:
When you wipe, the battery needs to recalibrate. That's why it stays at 100% for a long time, when is being drained actually...
[Nexus One Android Development] schahr01:
Where is this information coming from? I wipe batt stats before flashing kernels and my readings never stay at 100% for more than 5 or 10 minutes after disconnecting and I start using the device.
[Nexus One Android Development] rjhay22:
Horah! Finally good battery life for you ... if I was smart like you I'd keep the kernel and be merry with it. Flashing another one would get you back to the same problem you have since day one of having your Nexie :-)
[Nexus One Android Development] hah2110:
Ya but I don't think the 0%/hour will stay lol
[Nexus One Android Development] sir*mez:
@intersectR: This is what pershoot's table looks like with the added frequencies. I hope this helps so you can add the frequencies so that when on conservative the CPU scales up thru more frequencies thus not alway reaching Max to save battle life:

struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, CCTL(CLK_TCXO, 1), SRC_RAW, 0, 0, 950 },
{ 128000, CCTL(CLK_TCXO, 1), SRC_AXI, 0, 0, 950 },
{ 245000, CCTL(CLK_MODEM_PLL, 1), SRC_RAW, 0, 0, 950 },
{ 256000, CCTL(CLK_GLOBAL_PLL, 3), SRC_RAW, 0, 0, 950 },
{ 384000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0A, 0, 975 },
{ 422400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0B, 0, 1000 },
{ 460800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0C, 0, 1025 },
{ 499200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0D, 0, 1050 },
{ 537600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0E, 0, 1050 },
{ 576000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0F, 0, 1075 },
{ 614400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x10, 0, 1100 },
{ 652800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x11, 0, 1125 },
{ 691200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x12, 0, 1150 },
{ 729600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x13, 0, 1175 },
{ 768000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x14, 0, 1200 },
{ 806400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x15, 0, 1225 },
{ 844800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x16, 0, 1225 },
{ 883200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x17, 0, 1250 },
{ 921600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x18, 0, 1275 },
{ 960000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x19, 0, 1275 },
{ 998400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1A, 0, 1275 },
{ 1036800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1B, 0, 1275 },
{ 1075200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1C, 0, 1275 },
{ 1113600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1D, 0, 1275 },
{ 0 },
};
[Nexus One Android Development] schahr01:
Aha... CLK_MODEM_PLL is the modem/radio voltage. Raven - In your table is the value different for 800mv and 925mv kernels? Looks like pershoot has the modem voltage at 950mv.
[Nexus One Android Development] hah2110:
So if I can duplicate the results of 9 hours at 100%, why wouldn't I just wipe batt stats every night? My mAh are still in line with current % reading. At 91% now and it dropped to 99% around 11am. Means 4 hours and 9% and I've used it. Not heavily, but I have.
[Nexus One Android Development] mrandroid:
Using 33.4 + Task Manager = 30% battery loss in 2 days! Awesome! (calls, texting, some gps usage and very minor web usage)

I set task manager to ignore 2 or 3 main apps and to kill all other apps 5 mins after screen turns off.

P.S. - If anyone is having trouble with mediafire i try to keep this page updated with kernels: intersectRaven Repository
[Nexus One Android Development] hah2110:
Okay... That blows mine out of the water. Do you have screenshots? Maybe a Battery Graph? I didn't think ANYONE was getting that kind of battery life on a .33.4. Which kernel is it exactly? Remember, there are also two schools of thought on whether or not a task killer helps.
[Nexus One Android Development] mrandroid:
Task killer definitely helps! I'm using the 925mV 33.4 latest release.

Honestly, task killer made all the difference, if it wasn't for that i wouldn't have had that type of battery life. As soon as i setup my task manager i noticed a HUGE improvement a few hours in... i'll work up some screen shots.
[Nexus One Android Development] schahr01:
Can you please indicate what specific application and the settings you use?
[Nexus One Android Development] joshualimjs:
hello there, wifi unable to start if i flash your kernel into MoDaCo Desire to nexus port R22. R21 works fine with your kernel but not R22. Any ideas? =)
[Nexus One Android Development] mtw4991:
+1 for specifics too. Also, are you using SetCPU? If so, settings?

Also, does 0517_1015 925mV have the USB unmounting issues?
[Nexus One Android Development] mrandroid:
Yes it has the unmount issue, but I just unplug the USB instead of clicking unmount. Also, I don't usually mount USB (I usually just push to SD Card with ADB). Plus, the speed/response is very much noticeable with the .34 kernel so the unmount issue doesn't bother me. Haven't found any other issues but that.

My Setup:

Rom: Cyanogenmod 5.0.6

Theme: NexTheme w/ Goodies (newest versions)

Helix Launcher2 (that came w/goodies) - I only use 3 screens

Kernel: Using intersectRaven's newest release of .34

GPS: Enabled (disable if you don't use, will save a ton of battery)

Stock Weather Widget set to zipcode instead of location (saves on GPS usage)

I don't use SetCPU

Task Manager 2.0.8 (the little green android one)

Task Manager Settings:

- Ignore List: Clock, TaskManager & HelixLauncher2

Auto Startup - check

Notification Bar - uncheck (I use the widget)

Enable Auto-Kill - check

Auto-Kill Delay - 5 mins (you can use 3 mins also)

Auto-Kill notification - uncheck

Also, when you install the .34 kernel, wipe your cache, dalvik-cache & battery stats. Then leave your phone to charge to full. This will give you optimal results.

Also, I like old school, i never use the update.zip method. I unpack the zImage & flash through fastboot.
[Nexus One Android Development] mtw4991:
Thanks for the info...are you using 33.4 or .34?? I was asking if 33.4 had the unmount issue. I know .34 does. Thanks!
[Nexus One Android Development] mrandroid:
oh sorry, i never had any mounting issues with the 33.4 kernels... I'm using .34 right now.
[Nexus One Android Development] D200P13:
2.6.34_AVS-925mV_CFS_20100517_1023 <-- is that the latest beta or something for the nexus one? what i am trying to say if its recommended and ok to use on my cyan nexus one or if its for another phone model.
[Nexus One Android Development] mrandroid:
Yes, it's better, newer.

Just get the update.zip from the first page (get the 925mV version) and flash it like you would a rom. place it on your sdcard, boot into your recovery and select/install it. reboot and you're done.

When you update to a new CM release it'll overwrite this kernel, so you'll need to reinstall it after any ROM updates.
[Nexus One Android Development] mrandroid:
yes it's ok. flash it, love it!
[Nexus One Android Development] D200P13:
ah im guessing that it should work fine correct? the file name is just 2.6.34_AVS-925mV_CFS_20100517[DATE]_1023[TIME] and is 3 hours newer then the "stable" one posted on first post. i thought they was some special version or something that are specific to something.
[Nexus One Android Development] hah2110:
Anyone have clues as to this whole 100% for 9 hours deal?
[Nexus One Android Development] schahr01:
Maybe an important piece of information was left out? Was it still plugged into the charger or USB port? ;)

Seriously, there's no other way - Faulty hardware (battery sensor)? Faulty software (battery status wedged)?
[Nexus One Android Development] hah2110:
No... Obviously not plugged in. I could provide screenshots to prove that. It isn't faulty anything if you look at the OSMonitor. It is actually reporting over 1400mAh and it slowly decreases as needed. Many people have reported being stuck at 100 for a while (just not that long). I think there is something here that no one is capitalizing on. All software items are reporting the same results (ie., about phone, osmonitor, juice plotter, etc.
[Nexus One Android Development] Pochemuchka1977:
The devices stays in boot loop on the first boot screen (the one with a lock) for 5 minutes now ....
[Nexus One Android Development] wildmonks:
I tried it too, just for fun. :rolleyes: I get the same thing.
[Nexus One Android Development] intersectRaven:
Whoops! I forgot to return minimum values to 1000 uV instead of 800. Will upload a fixed one. :eek:

Here's the correct one:

http://www.mediafire.com/?oc3neim4jez
[Nexus One Android Development] Pochemuchka1977:
Same :(

<6>[ 104.157165] do_imprecise_ext: ADFSR = 0x00000004

<6>[ 104.157348] do_imprecise_ext: DFSR = 0x00000436

<6>[ 104.157440] do_imprecise_ext: ACTLR = 0x000c0037

<6>[ 104.157623] do_imprecise_ext: EFSR = 0x00000004

<6>[ 104.157714] do_imprecise_ext: L2SR = 0x00010000

<6>[ 104.157806] do_imprecise_ext: L2CR0 = 0xc0050f0f

<6>[ 104.157958] do_imprecise_ext: L2CPUESR = 0x00001020

<6>[ 104.158050] do_imprecise_ext: L2CPUCR = 0x000000e0

<6>[ 104.158233] do_imprecise_ext: SPESR = 0x00000000

<6>[ 104.158325] do_imprecise_ext: SPCR = 0x0000000f

<6>[ 104.158508] do_imprecise_ext: DMACHSR = 0x00000001

<6>[ 104.158599] do_imprecise_ext: DMACHESR = 0x00000000

<6>[ 104.158691] do_imprecise_ext: DMACHCR = 0x0000000f

<6>[ 104.158843] do_imprecise_ext: TCSR_SPARE2 = 0x0000a037

<1>[ 104.158935] Unhandled fault: imprecise external abort (0x436) at 0x423259d

e

<6>[ 170.908447] do_imprecise_ext: ADFSR = 0x00000004

<6>[ 170.908630] do_imprecise_ext: DFSR = 0x00000416

<6>[ 170.908752] do_imprecise_ext: ACTLR = 0x000c0037

<6>[ 170.908843] do_imprecise_ext: EFSR = 0x00000004

<6>[ 170.909027] do_imprecise_ext: L2SR = 0x00010000

<6>[ 170.909118] do_imprecise_ext: L2CR0 = 0xc0050f0f

<6>[ 170.909301] do_imprecise_ext: L2CPUESR = 0x00001020

<6>[ 170.909393] do_imprecise_ext: L2CPUCR = 0x000000e0

<6>[ 170.909484] do_imprecise_ext: SPESR = 0x00000000

<6>[ 170.909576] do_imprecise_ext: SPCR = 0x0000000f

<6>[ 170.909667] do_imprecise_ext: DMACHSR = 0x00000001

<6>[ 170.909851] do_imprecise_ext: DMACHESR = 0x00000000

<6>[ 170.909942] do_imprecise_ext: DMACHCR = 0x0000000f

<6>[ 170.910095] do_imprecise_ext: TCSR_SPARE2 = 0x0000a037

<1>[ 170.910186] Unhandled fault: imprecise external abort (0x416) at 0x0049525

4

<6>[ 188.851562] do_imprecise_ext: ADFSR = 0x00000004

<6>[ 188.851745] do_imprecise_ext: DFSR = 0x00000436

<6>[ 188.851837] do_imprecise_ext: ACTLR = 0x000c0037

<6>[ 188.851928] do_imprecise_ext: EFSR = 0x00000004

<6>[ 188.852081] do_imprecise_ext: L2SR = 0x00010000

<6>[ 188.852172] do_imprecise_ext: L2CR0 = 0xc0050f0f

<6>[ 188.852355] do_imprecise_ext: L2CPUESR = 0x00001020

<6>[ 188.852447] do_imprecise_ext: L2CPUCR = 0x000000e0

<6>[ 188.852539] do_imprecise_ext: SPESR = 0x00000000

<6>[ 188.852722] do_imprecise_ext: SPCR = 0x0000000f

<6>[ 188.852813] do_imprecise_ext: DMACHSR = 0x00000001

<6>[ 188.852996] do_imprecise_ext: DMACHESR = 0x00000000

<6>[ 188.853088] do_imprecise_ext: DMACHCR = 0x0000000f

<6>[ 188.853240] do_imprecise_ext: TCSR_SPARE2 = 0x0000a037

<1>[ 188.853332] Unhandled fault: imprecise external abort (0x436) at 0xaf723f8

8

I have much more like these, these are examples. Part of the errors happen when ROM is loading, even before I see the home screen for the first time
[Nexus One Android Development] intersectRaven:
Hmmm...I can rule out the optimization then...must be some deviation between our code modifications then...when do you encounter the errors by the way? Is there a specific program or something?
[Nexus One Android Development] wildmonks:
Re: [Kernel - .33]intersectRaven's Kernel (with several tweaks) 04/10/2010 11:56pm

This one works for me, no bootloop. But I still have that strange wi-fi issue hah.
[Nexus One Android Development] Pochemuchka1977:
This happens during boot of the device - i did not manage even to see the home screen. On other reboot the home screen was frozen. It happens regardless of which program I am running

The last version I was managed to run properly was 20100403_0849
[Nexus One Android Development] intersectRaven:
Hmmm...does the non-AVS version work for you? I'm thinking of redoing the AVS version from it if ever that works.
[Nexus One Android Development] Pochemuchka1977:
Yes, without any problem

The latest Ivan's AVS runs good as well
[Nexus One Android Development] rori~:
Tried this one...just opened the Market app, phone freezes :(