• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM 10.1 Nightlies Discussion

Neph81 said:
After looking at that patch, I don't believe it's going to help what you are looking at. They are in a spot where the camera is not even starting up. Ours starts, but the qdoverlay is acting up causing only a 3 line preview to be shown. At this point, I suppose it wouldn't hurt to try it out, but I have a feeling it's all going to come down to the video fixes that RMCC pushed 2 months back.
Click to expand...

You're provably right on the patch. I can say that I am no longer having the issue since I switched to the slide lock.
 
Neph81 said:
After looking at that patch, I don't believe it's going to help what you are looking at. They are in a spot where the camera is not even starting up. Ours starts, but the qdoverlay is acting up causing only a 3 line preview to be shown. At this point, I suppose it wouldn't hurt to try it out, but I have a feeling it's all going to come down to the video fixes that RMCC pushed 2 months back.
Click to expand...


If I'm not mistaken, CM swapped over to some portion of the CAF q-com a/v tree. Sorry I I don't remember the exact name off the top of my head. I believe that's what prompted RMCC's kernel side changes to begin with. Perhaps the problem is somehow tied to that?
 
Yoinx : Yeah, that was when the whole issue started with Carcasonne. I remember staying on RC3 because of that and then when it became a stable release, I just put up with the issue. Now that I know it's system related, it's got my attention a bit more. I'm going to start digging through commits on Monday to see if I can figure out which one would be a probable culprit.
 
Neph81 said:
Yoinx : Yeah, that was when the whole issue started with Carcasonne. I remember staying on RC3 because of that and then when it became a stable release, I just put up with the issue. Now that I know it's system related, it's got my attention a bit more. I'm going to start digging through commits on Monday to see if I can figure out which one would be a probable culprit.
Click to expand...


The commits for what? The kernel?

The ones in the kernel were just the two about pipes. One was commited when people first started getting teh black screen on boot. Then they changed something, and that patch needed to be reverted, then it needed to be unreverted or something (why the kernel I compile was still working for people for awhile while the one in the nightlies wouldnt). Then they re-fixed the official kernel.

It might be hard to track down since there was so much flip flopping.

Though, I'm willing to bet you understand it more than I do ;)


What I've noticed though from looking other device trees while I pick & pull things is that it seems like the graphics drivers in the kernel source are kinda bastardized anyway. It's like all the adreno stuff got pulled over and just tossed in /drivers/gpu/msm and hacked up a bit. I was trying to merge some changes the other day locally, and couldn't even wrap my head on how to clean it up to start merging things. But *shrug* some things just aren't meant to be.


*edit*

Btw, oddly enough what you described doesn't happen to me. I don't normally bother with security, so I set a 3x3 pattern and rebooted. Before unlocking the phone, I swiped right to the camera. Works fine.

This is running the pac build from 29jun and my kernel though. Might be a place to compare from if nothing else.
 
I understand the basics, but not much else. The one thing I am good at though is looking through code/logs and find the one piece that doesn't belong. I've noticed that there is an IOCTL error calling MSMFB_OVERLAY_SET. That's probably going to be my first step. You are correct about the drivers being bastardized. I'm hoping TDM is making some good progress on 3.4. We're going to need that new source if we ever plan on making it off of JB when KLP finally comes out.
 
Neph81 said:
I understand the basics, but not much else. The one thing I am good at though is looking through code/logs and find the one piece that doesn't belong. I've noticed that there is an IOCTL error calling MSMFB_OVERLAY_SET. That's probably going to be my first step. You are correct about the drivers being bastardized. I'm hoping TDM is making some good progress on 3.4. We're going to need that new source if we ever plan on making it off of JB when KLP finally comes out.
Click to expand...

Yeah. Hey sorry I edited my previous post after trying to reproduce. Not sure it helps much... but I can't reproduce what you're getting on my setup

Sent from my VS920 4G using Tapatalk 2
 
I just flashed stable 10.1
Its telling me there's updates available. Should I get the updates? (Shows 10.1.1 and 10.1.2) Whats been changed/improved with them updates?
 
Security updates for the master key exploit. I would suggest upgrading, especially if you sideload any apps from "suspicious" places.
 
So I just updated to the latest stable release 10.1.2. What I'm noticing on this and the previous stable release is that my 4g signal is awful especially at home, where it used to be fine. Network mode is set to LTE/CDMA/EVDO.

Any suggestions for things to try and improve signal?
 
Staticaxe said:
So I just updated to the latest stable release 10.1.2. What I'm noticing on this and the previous stable release is that my 4g signal is awful especially at home, where it used to be fine. Network mode is set to LTE/CDMA/EVDO.

Any suggestions for things to try and improve signal?
Click to expand...
What baseband are you on? I've found V7 to be the best for me, but others are saying v8 gives them better results.
 
DSP Manager built into CM. You won't get much of an increase, but it's about the same as you'd get from any other app.
 
I've been using these ROMs for a bit on this phone. I've also used a few others.

I figure I might as well ask about some of the issues I've had and see if anyone has experienced them as well and/or has solutions for them.

  • Apps will randomly close out. Not in the force close sort of way, but as if I had just pressed the back button (no, I'm not accidentally hitting it). This normally happens when I try to scroll before everything has loaded. Some apps more than others.
  • Bluetooth won't work for any devices that use a pin number (Ex. My car)
  • That video bug where the entire screen turns to barred lines and the only way to fix it is to pull the battery. It doesn't happen often though.
  • When I take a picture the exif data is always 12/08/2002.
 
oceania said:
I've been using these ROMs for a bit on this phone. I've also used a few others.

I figure I might as well ask about some of the issues I've had and see if anyone has experienced them as well and/or has solutions for them.

  • Apps will randomly close out. Not in the force close sort of way, but as if I had just pressed the back button (no, I'm not accidentally hitting it). This normally happens when I try to scroll before everything has loaded. Some apps more than others.
  • That video bug where the entire screen turns to barred lines and the only way to fix it is to pull the battery. It doesn't happen often though.
  • When I take a picture the exif data is always 12/08/2002.
Click to expand...

I experienced these too. Mostly on the most recent 'stable' build. I had to go back to beta4. These happened less often, if at all there.
The picture naming is still annoying however.
 
azoller1 said:
OK, but I'm wondering why it only happens on jb when i get the messages and on ICS I dont get them
Click to expand...

On the VZW site, go under Change Features or something like that. Backup Assistant Plus and Contact Sync or Contact Management, something like that, both cause those obnoxious texts, so disable 'em (does anyone actually use Verizon's Backup Assistant?).
 
You must log in or register to reply here.
Back
Top Bottom