CM7 Nightlies Topic [Nightly 28- 21/03/2011]

[Guest natash]

It is nokia hf310. When it is paired and connected, the screen will turn on, it is disconnecting. When I wake up the screen and check the bluetooth option I see. "Paired disconnected". Also when somebody is calling, the nokia hf310 did not ringing, just ZTE Blade.

UP.

[Guest Maringer]

Can't it be the smartass governor, as i use Overclock Widget i've noticed such behaviour when waking up: delay to speed up the cpu...

Not likely.

I encounter a similar delay on N28 and the governor was still set to "ondemand" as standard.

In fact, I've just changed the settings to use the smartass governor and, after a reboot, the screen seems to come back on more quickly than before! Not much in it but it seems to be a little quicker though it could just be placebo, I suppose.

[Guest Frankish]

I wonder if the screen freezes are fixed? On any nightly i couldn't play a game without getting at least 1 screen freeze. Just played a full game on n26 with not a single freeze at all. That includes a full game, extra time and penalties!

[Guest skyhacker]

I haven't got screen freezes on swype (used to get one on eatch sms) since n25, maybe the guys did something to solve the issue ...

[Guest Frankish]

I haven't got screen freezes on swype (used to get one on eatch sms) since n25, maybe the guys did something to solve the issue ...

Not seen any specific fixes but either way...yay. I'll test some more. If it's fixed then there must be just the reboot when charging issue left to fix. For major issues anyway :D

[Guest tomc123]

Hi,

my alarm went off for work this morning but only very briefly, luckily my old girl was still around to wake me up, when i looked at my phone the alarm screen was there but no sound ???

i have checked all settings and cannot find anything ???

BTW running N25... any ideas ?

[Guest samjam]

With N28 the battery performance is abysmal, I lose 4% per hour, true over a 4 hour period and true again after a charge.

[Guest Roo13]

Not likely.

I encounter a similar delay on N28 and the governor was still set to "ondemand" as standard.

In fact, I've just changed the settings to use the smartass governor and, after a reboot, the screen seems to come back on more quickly than before! Not much in it but it seems to be a little quicker though it could just be placebo, I suppose.

Ok, and what about using Overclock Widget is it double-use with CPU governors in general and the smartass one now on CM...? I keep using this app but don't really know if it's useful...

I wonder if the screen freezes are fixed? On any nightly i couldn't play a game without getting at least 1 screen freeze. Just played a full game on n26 with not a single freeze at all. That includes a full game, extra time and penalties!

Haven't experienced one on n26 since friday, got a serious one on n21 and none on RC2 as far as i remember...

[Guest forney27]

Not sure what happened last night, but was on N26 and phone turned off and took about 10 minutes for it to turn back on...lights were on, but nobody home.

[Guest skyhacker]

I don't know about u guys but on my phone the battery drain issue is back and with a vengeance, I lost about 10% in ten minutes in angry birds, when the phone is in sleep the loss is still minimum but when I'm messing with it the drain is huge

[Guest Victor von Zeppelin]

I don't know about u guys but on my phone the battery drain issue is back and with a vengeance, I lost about 10% in ten minutes in angry birds, when the phone is in sleep the loss is still minimum but when I'm messing with it the drain is huge

That's always always happened to me. But considering Angry Birds is probably the biggest CPU hog you can get, i'm not surprised.

[Guest Scoopading]

With regard to screen freezes - I've been on Nightly 25 for the last few days now and I haven't noticed any screen freezes of the type where you have to use the power on/off button to reset the screen. So (hopefully not speaking too soon) it seems like it's fixed, and it could've been related to the screwy ZTE sensor code which was fixed (now proximity works excellently!). There might still be some temporary screen freeze though (the sort which rectifies itself) but you'd need to test a while with something like Fruit Ninja to confirm that, and it's just as likely problems like that may be related to things other than the kernel itself.. (IE either the game code or background processes etc).

Pulling the Status Bars Notification menu back up seems a bit more reliable now too, although it still won't respond sometimes, so it's still not entirely fixed.

With regards to WIFI on Nightly 26 - Every version of the Blade has had screwed up WIFI. Some of the Froyo based roms have been modified to reconnect better after a screen sleep, but all of them have a broken sleep "never" function, so they all turn the WIFI off when the screen goes off, unless connected to a power source via USB. It's ironic that the new WIFI driver seems to do the exact opposite, but hopefully (when fixed) it'll mean the Blade will finally have a working "Never sleep" function, as well as more reliable reconnections.

With regards to power drain on nightly 26 - It might well be related to the WIFI, but (since the original battery drain issue actually stemmed from the CPU) I wouldn't rule out the new governor code either. I'd recommend people set the minimum speed down to 122Mhz in the Cyanogen settings, and try a different governor (the new smartass one) if they notice the drain, and set it to "on boot".

The USB issues present on CM7 (which may cause a reboot, and doesn't detect USB properly on boot etc) don't seem like they'll be fixed so easily without a big overhaul, and Jacob has commented that he doesn't think some of the problems will be fixed until a move to a .35 kernel (Gingerbread expects 2.6.35+, but CM7 is currently using a .32 kernel for those who weren't aware.. )

If someone just wants a reliable Nightly, and doesn't want to test things, I can recommend Nightly 25. You can work around the WIFI reconnect issue easily by adding Blade WIFI fix from the market. If you want a working Never sleep function (albeit a kludge work around that will use more battery than it should) you can use Advanced WIFI lock free, although it'll autostart whether you use it or not, so you need an app like autostarts to stop it launching at boot time. I have noticed the GPS icon is a bit laggy setting on/off on nightly 25, but I haven't noticed any reboot issues related to GPS which some people mention.

[Guest Oyorf]

I don't know about u guys but on my phone the battery drain issue is back and with a vengeance, I lost about 10% in ten minutes in angry birds, when the phone is in sleep the loss is still minimum but when I'm messing with it the drain is huge

I get huge battery drain with Angry birds, also in 2.1 and 2.2 roms. So I guess it's more about problem in AB than in ROM.(or maybe not a problem at all, AB just use cpu a lot)

[Guest skyhacker]

I know angry birds use a lot of CPU but even with normal use a drainage is huge, angry bird was just an example

[Guest chimas]

I don't know about u guys but on my phone the battery drain issue is back and with a vengeance, I lost about 10% in ten minutes in angry birds, when the phone is in sleep the loss is still minimum but when I'm messing with it the drain is huge

I thought this was normal. while i lose little to no discharge in sleep mode, but as soon as i open up a browser or any app for that matter it's like a hole has been punched into my battery. Can someone else confirm this?

[Guest mELIANTE]

I thought this was normal. while i lose little to no discharge in sleep mode, but as soon as i open up a browser or any app for that matter it's like a hole has been punched into my battery. Can someone else confirm this?

I can. And I say that it punches a bigger hole than FroYo too.

[Guest Victor von Zeppelin]

S'up doods and doodlets (if there are any, of course...)

Now, I currently love http://cm-nightlies.appspot.com/?device=blade

I think it does an excellent job at surmising what's going on and what fixes are being made.

However, what I think would be most helpful is if it could be embedded into the first post. I've been playing with as many BB commands as I could find...and nothing would allow me to do what basically an iframe would.

So, I was wondering; is there a way? Or, as an alternative, a way to render the page as an image. I've seen the RSS images that have a ticker of updates, and I was wondering if that could be applied to the whole page.

(also, don't suggest using those, the RSS feed on that page is useless)

[Guest mvheuver]

I have noticed the GPS icon is a bit laggy setting on/off on nightly 25, but I haven't noticed any reboot issues related to GPS which some people mention.

For what it's worth, I just had my phone switch off on me after using GPS for a few minutes. That is on nightly 25, which I am staying on for the moment. It didn't reboot as seems to happen with other people, it just shut down somehow and it was only after 10 minutes or so that I realised. Guess I'd better start using Logcat as well.

[Guest muller37]

Hi,

my alarm went off for work this morning but only very briefly, luckily my old girl was still around to wake me up, when i looked at my phone the alarm screen was there but no sound ???

i have checked all settings and cannot find anything ???

BTW running N25... any ideas ?

i had exact same issue the other day. i was using the stock alarm clock from froyo roms at the time as i prefer it but as you say, it went off for half a second then just sat there saying dismiss. uninstalled it and used the supplied alarm in cm7 and has worked for me since. hope this helps.

[Guest brokebloke]

For what it's worth, I just had my phone switch off on me after using GPS for a few minutes. That is on nightly 25, which I am staying on for the moment. It didn't reboot as seems to happen with other people, it just shut down somehow and it was only after 10 minutes or so that I realised. Guess I'd better start using Logcat as well.

Had the exact same problem myself yesterday on nightly 25, tested the GPS then put the phone to sleep. 10 mins later it switched off. It's the first time i had tried the GPS been using the rom before that without any problems.

[Guest xzyk]

For what it's worth, I just had my phone switch off on me after using GPS for a few minutes. That is on nightly 25, which I am staying on for the moment. It didn't reboot as seems to happen with other people, it just shut down somehow and it was only after 10 minutes or so that I realised. Guess I'd better start using Logcat as well.

I've been trying to track this problem down on every nightly, since N19. Currently on N26 and it does the same thing. I can make it happen at will (few pages back I wrote what you need to do to re-produce the problem everytime). I did notice one thing though, if i have the phone in airplane mode, it doesn't reboot/shutdown. Obviusly this is neither a solution or a workaround, simply an observation.

[Guest chimas]

I can. And I say that it punches a bigger hole than FroYo too.

Yeah it really does.

and if you are crazy enough (like me) to play a high spec game like asphalt5 or read a book using aldiko, you battery will go quicker than a donut on a fat man's lap.

Edited March 21, 2011 by chimas

[Guest t0mm13b]

Am currently on nightly 28 now... and have noticed a few things....

Kernel has the fm radio chipset compiled in, but it is not Andorko's patched version..

<6>[01-01 00:00:01.290003] [1: swapper][FM][FYA@FM_SI4708]register fm_si4708 device successful!

USB OTG seems to be in place.... (makes me experimental kernel redundant... :()

Has anyone tested this as I do not have a adapter thingy for it.... :(

There seems to be a common issue.... have noticed this as far back as nightly 21...

<4>[01-01 00:00:00.450001] [1: swapper]------------[ cut here ]------------

<4>[01-01 00:00:00.450001] [1: swapper]WARNING: at drivers/gpio/gpiolib.c:101 gpio_ensure_requested+0x4c/0x19c()

<4>[01-01 00:00:00.450001] [1: swapper]autorequest GPIO-57

<4>[01-01 00:00:00.450001] [1: swapper]Modules linked in:

<4>[01-01 00:00:00.450001] [1: swapper][<c0037280>] (unwind_backtrace+0x0/0x154) from [<c00a01a4>] (warn_slowpath_common+0x48/0x60)

<4>[01-01 00:00:00.450001] [1: swapper][<c00a01a4>] (warn_slowpath_common+0x48/0x60) from [<c00a01f4>] (warn_slowpath_fmt+0x24/0x30)

<4>[01-01 00:00:00.450001] [1: swapper][<c00a01f4>] (warn_slowpath_fmt+0x24/0x30) from [<c024da40>] (gpio_ensure_requested+0x4c/0x19c)

<4>[01-01 00:00:00.450001] [1: swapper][<c024da40>] (gpio_ensure_requested+0x4c/0x19c) from [<c024dc18>] (gpio_direction_output+0x88/0x24c)

<4>[01-01 00:00:00.450001] [1: swapper][<c024dc18>] (gpio_direction_output+0x88/0x24c) from [<c02630b0>] (lcdc_set_bl+0xf4/0x280)

<4>[01-01 00:00:00.450001] [1: swapper][<c02630b0>] (lcdc_set_bl+0xf4/0x280) from [<c0254f30>] (msm_fb_set_backlight+0x68/0x7c)

<4>[01-01 00:00:00.450001] [1: swapper][<c0254f30>] (msm_fb_set_backlight+0x68/0x7c) from [<c025503c>] (msm_fb_blank_sub+0x90/0xe8)

<4>[01-01 00:00:00.450001] [1: swapper][<c025503c>] (msm_fb_blank_sub+0x90/0xe8) from [<c0255484>] (msm_fb_open+0x34/0x64)

<4>[01-01 00:00:00.450001] [1: swapper][<c0255484>] (msm_fb_open+0x34/0x64) from [<c024f5b8>] (register_framebuffer+0x2d4/0x310)

<4>[01-01 00:00:00.450001] [1: swapper][<c024f5b8>] (register_framebuffer+0x2d4/0x310) from [<c0256c44>] (msm_fb_probe+0x538/0x990)

<4>[01-01 00:00:00.450001] [1: swapper][<c0256c44>] (msm_fb_probe+0x538/0x990) from [<c02997d8>] (platform_drv_probe+0x18/0x1c)

<4>[01-01 00:00:00.450001] [1: swapper][<c02997d8>] (platform_drv_probe+0x18/0x1c) from [<c02984d0>] (driver_probe_device+0x140/0x2c0)

<4>[01-01 00:00:00.450001] [1: swapper][<c02984d0>] (driver_probe_device+0x140/0x2c0) from [<c0297774>] (bus_for_each_drv+0x48/0x84)

<4>[01-01 00:00:00.450001] [1: swapper][<c0297774>] (bus_for_each_drv+0x48/0x84) from [<c0298788>] (device_attach+0x50/0x68)

<4>[01-01 00:00:00.450001] [1: swapper][<c0298788>] (device_attach+0x50/0x68) from [<c0297558>] (bus_probe_device+0x24/0x44)

<4>[01-01 00:00:00.450001] [1: swapper][<c0297558>] (bus_probe_device+0x24/0x44) from [<c02957d0>] (device_add+0x36c/0x500)

<4>[01-01 00:00:00.450001] [1: swapper][<c02957d0>] (device_add+0x36c/0x500) from [<c0299de0>] (platform_device_add+0x138/0x1bc)

<4>[01-01 00:00:00.450001] [1: swapper][<c0299de0>] (platform_device_add+0x138/0x1bc) from [<c025751c>] (mdp_probe+0x3b0/0x474)

<4>[01-01 00:00:00.450001] [1: swapper][<c025751c>] (mdp_probe+0x3b0/0x474) from [<c02997d8>] (platform_drv_probe+0x18/0x1c)

<4>[01-01 00:00:00.450001] [1: swapper][<c02997d8>] (platform_drv_probe+0x18/0x1c) from [<c02984d0>] (driver_probe_device+0x140/0x2c0)

<4>[01-01 00:00:00.450001] [1: swapper][<c02984d0>] (driver_probe_device+0x140/0x2c0) from [<c0297774>] (bus_for_each_drv+0x48/0x84)

<4>[01-01 00:00:00.450001] [1: swapper][<c0297774>] (bus_for_each_drv+0x48/0x84) from [<c0298788>] (device_attach+0x50/0x68)

<4>[01-01 00:00:00.450001] [1: swapper][<c0298788>] (device_attach+0x50/0x68) from [<c0297558>] (bus_probe_device+0x24/0x44)

<4>[01-01 00:00:00.450001] [1: swapper][<c0297558>] (bus_probe_device+0x24/0x44) from [<c02957d0>] (device_add+0x36c/0x500)

<4>[01-01 00:00:00.450001] [1: swapper][<c02957d0>] (device_add+0x36c/0x500) from [<c0299de0>] (platform_device_add+0x138/0x1bc)

<4>[01-01 00:00:00.450001] [1: swapper][<c0299de0>] (platform_device_add+0x138/0x1bc) from [<c02610d0>] (lcdc_probe+0x128/0x178)

<4>[01-01 00:00:00.450001] [1: swapper][<c02610d0>] (lcdc_probe+0x128/0x178) from [<c02997d8>] (platform_drv_probe+0x18/0x1c)

<4>[01-01 00:00:00.450001] [1: swapper][<c02997d8>] (platform_drv_probe+0x18/0x1c) from [<c02984d0>] (driver_probe_device+0x140/0x2c0)

<4>[01-01 00:00:00.450001] [1: swapper][<c02984d0>] (driver_probe_device+0x140/0x2c0) from [<c0297774>] (bus_for_each_drv+0x48/0x84)

<4>[01-01 00:00:00.450001] [1: swapper][<c0297774>] (bus_for_each_drv+0x48/0x84) from [<c0298788>] (device_attach+0x50/0x68)

<4>[01-01 00:00:00.450001] [1: swapper][<c0298788>] (device_attach+0x50/0x68) from [<c0297558>] (bus_probe_device+0x24/0x44)

<4>[01-01 00:00:00.450001] [1: swapper][<c0297558>] (bus_probe_device+0x24/0x44) from [<c02957d0>] (device_add+0x36c/0x500)

<4>[01-01 00:00:00.450001] [1: swapper][<c02957d0>] (device_add+0x36c/0x500) from [<c0299de0>] (platform_device_add+0x138/0x1bc)

<4>[01-01 00:00:00.450001] [1: swapper][<c0299de0>] (platform_device_add+0x138/0x1bc) from [<c0255980>] (msm_fb_add_device+0xf4/0x140)

<4>[01-01 00:00:00.450001] [1: swapper][<c0255980>] (msm_fb_add_device+0xf4/0x140) from [<c001a494>] (lcdc_panel_probe+0x2c0/0x2f8)

<4>[01-01 00:00:00.450001] [1: swapper]unwind: Unknown symbol address c001a494

<4>[01-01 00:00:00.450001] [1: swapper]unwind: Index not found c001a494

<4>[01-01 00:00:00.450001] [1: swapper]---[ end trace da227214a82491b7 ]---

GPIO crashed somewhere unless why is the stack trace there....? :D

[Guest css771]

Am currently on nightly 28 now... and have noticed a few things....

Kernel has the fm radio chipset compiled in, but it is not Andorko's patched version..

USB OTG seems to be in place.... (makes me experimental kernel redundant... :()

Has anyone tested this as I do not have a adapter thingy for it.... :D

There seems to be a common issue.... have noticed this as far back as nightly 21...

GPIO crashed somewhere unless why is the stack trace there....? :D

When did the FM driver and USB OTG make it in? :( There haven't been any commits on TG's sources regarding that.

The GPIO thing is beyond me but I noticed that there have been no changes to the gpiolib.c file ever https://github.com/TomGiordano/kernel_zte_b.../gpio/gpiolib.c which was the file mentioned in the dmesg.

Edited March 21, 2011 by css771

[Guest jijijoujou1]

I have flashed N27 with wipe data and factory , and i have a problem with the accelorometer and the compass , i can't play deudly jump and speed 3dx , its seems that the sensor is broek , anyone else have this problem ?!