CM7 Q&A

cbizzle14

Member
Oct 28, 2011
25
3
0
Well the camera issue was addressed in both the nightly and the stable. Have you tried clearing data from the camera app? Nightlies aren't intended for everyday use. The stable version is better. What's in the nightlies is in the stable, but not everything in the stable is in the nightlies.
 

cption

Senior Member
Nov 4, 2011
61
17
0
Nevermind. False alarm. Im just being noob trying to focus on a white cup in the worst lighting. Fine focusing on my blue alarm now :)

Sent from my MB860 using XDA App
 

cbizzle14

Member
Oct 28, 2011
25
3
0
so is there just a massive difference in performance? I'm more interested in battery life so would the 1.0ghz kernel be best? what do you suggest?
Idk about the kernel, I'm trying to find out who has the best battery life so I can copy their settings. But Ba2tf is better than the nightlies if that's what you were asking.
 

fleurdelisxliv

Senior Member
Jan 19, 2011
4,300
292
0
Louisiana
Did your APN settings get modified somehow? Try checking those.
ok im trippin cant find apn settings lol tryin to work and do this :)

found apn settings but not sure what they are sup to be

edit: so after flashing the radio and rebooting nothing then rebooted again and bam got all sig and data back :confused:
 
Last edited:

cption

Senior Member
Nov 4, 2011
61
17
0
Another question. For contacts with 2 or more numbers under one name... the contact gets split into multiple contact with the same name? Is there an option to fix this?

Sent from my MB860 using XDA App
 

mohitgarg

Senior Member
Apr 9, 2009
56
12
0
Johannesburg
I'm using the mentioned kernel and faux123's 1Ghz Kernel (The latest version).

Both of theses are being used by many members so I don't think the issue lies there.

One member mentioned using the volume keys to wake phone.

Just saw the CM7 thread and now more users complaining about the wake up issue.
 

jerrygooch

Senior Member
Jul 9, 2011
266
21
0
Conway
www.jerrygooch.com
Idk about the kernel, I'm trying to find out who has the best battery life so I can copy their settings. But Ba2tf is better than the nightlies if that's what you were asking.
Im trying to figure out if the extra .45 ghz is worth the extra juice I'm assuming the processor would need. I will be under volting and setting up profiles. Basically is there such a drastic performance difference where it would be worth the drain or should I get the 1 ghz kernel and reap the benefits of a super awesome battery life? Thanks for the reply.
 

fischwrap

Senior Member
Jun 17, 2011
570
101
0
Man, I just updated to the latest stable, flashed faux's enhanced kernel, uv'd, and i'm getting horrible battery drain. Left it unplugged last night street a full charge and battery calibration, and it dropped 50% in 9 hours. Alarm manager had some wake locks, but it want that extreme... Anyone else experiencing this kind of drain on this release?

Sent from my MB860 using Tapatalk
 

cption

Senior Member
Nov 4, 2011
61
17
0
Again. My problem self sorted after digging around. Merged contacts on Google contact using browser sorted the issue

Sent from my MB860 using XDA App
 

2leaponover1

Senior Member
May 18, 2009
405
21
0
I have been having 4 issues with the CM7 releases (From Beta 2 to latest Ba2TF):
1. Reboot when USB is connected in storage mode.

2. Sometimes when I put my phone on standby, and then try to wake it, it doesn't work, I have to either call or connect headphones/charger to wake it up.

3. I get artifacts in Launcher Pro, specifically in the app drawer, rare, but it is there. Generally there is a abstract white icon in the top left corner where there should be the first app icon and once i touch the screen, it all becomes normal.

4. Data does not connect when I enable it, have to reboot to start it.

I am posting this here as the main CM7 thread is a mess. And wanted to know if I am the only facing such issues.
That problem you have (#2) is a problem at least me and some other person is having. If you go back a couple pages you'll see us talk about it. Funny how the next person to post after you says he hasn't seen any of these issues. WELL! They exist and it makes the phone unusable for me. Wish that there was a known fix for it. I would go to CM's Atrix developer page and list it but it says you have to be able to replicate the problem and it is random so I don't know how they expect you to do that.

---------- Post added at 10:51 PM ---------- Previous post was at 10:49 PM ----------

Ok im a new CM7 user and i havent yet figure out the right procedure to post a bug, but here is the traditional way: i have the same screen problem as you, but it only happens when i make a call. Rite after i press that dial button, the screen turns off and i can't seem to turn it back on. When i press the power button it will flash on then off immediately, so i can't do anything. After the call ends by itself, i can't turn the screen back on by a single press, but with a long press, so its really frustrating. I look everywhere for the settings, in Cyanogenmod settings, in call settings, in dialer settings, nothing. The best one i can find is Keep screen awake in calls settings, but it doesn't work. So i hope someone can find the solution to this bug. Thanks


Sent from my MB860 using XDA App
EXACTLY the same problem I am having, word for word.
 

ghost_og

Senior Member
Sep 7, 2011
492
182
0
Chula Vista, CA
They exist and it makes the phone unusable for me. Wish that there was a known fix for it. I would go to CM's Atrix developer page and list it but it says you have to be able to replicate the problem and it is random so I don't know how they expect you to do that.
Replicating it is important or else how would the dev team be able to figure out what's causing the problem, or more importantly how to fix it? You guys obviously have some idea of how to reproduce the issue on your end. Here are the steps to get a logcat:

1.Try to duplicate the bug.
2.Note the steps necessary to duplicate it on the phone.
3.If you can, get a logcat. "adb logcat > logcat.txt" (this will record the log into a text file)
4.While logcat is running, reproduce the bug.
5.Once bug is reproduced (allow couple of seconds), in command prompt, press Ctrl + C to stop the log recording.
6.Find logcat.txt saved on your computer & rename it to align with type of bug. (Example: bluetooth.txt)
7.Go to the Issue Tab on the site and create a New Issue
8.Write the problem and the steps clearly on your post. Use the below example to help construct your description.
9.Attach log using "Attach a file" link below the Description box.

Try calling a # that will allow you enough time to fiddle around and successfully reproduce the bug. It's not that people don't want to help, it's just there's only so much that can be done if others are unable to produce the same problem on their end, and no one else can provide a reliable log if it happening. I hope you can get this figured out.

P.S. I can speak from experience when saying that the team will definitely try to replicate most bugs people bring up (browse the tracker, you will definitely be facepalming after reading some "bugs"). It's just that without proof, they have more than enough verifiable issues to work on.
 
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone