Database Info

Green Screen/Artifacts - Hardware or Software problem?

Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!

boktai1000 said:
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
Click to expand...
Click to collapse
go to the main settings, cyanogenmod settings, display.. turn on the screen off animation. then go back to cyanogenmod settings, lockscreen, delay and timeout, turn both screen timeout delay and screen turned off delay to immediately. that should fix the green screen.

[Q] Samsung Infuse Call, SMS notification light issue

Hello Everyone,
I have Samsung infuse installed with CM10 JB 4.1.1 v. 8/23/12 ROM which is working good, I get fare battery life of 1.5 days with normal use.
But I am not getting any notification on screen when I get any call or SMS, I get ringtone alert but screen is blank.
Please let me know if all are facing this issue with Call or SMS notification light. Also tell me if there is any FIX available for this.
Thanks in Advance .

There is no notification light for the Infuse, and none of the ICS or JB ROMs have the built in "screen light up upon notification" ability that Gingerbread had. I believe this is because the post-Gingerbread ROMs for Infuse are built upon code for phones with notification lights.
But, your screen should still be lighting up when you receive a call. Mine certainly does. You might want to try a re-flash.

lukas_s said:
There is no notification light for the Infuse, and none of the ICS or JB ROMs have the built in "screen light up upon notification" ability that Gingerbread had. I believe this is because the post-Gingerbread ROMs for Infuse are built upon code for phones with notification lights.
But, your screen should still be lighting up when you receive a call. Mine certainly does. You might want to try a re-flash.
Click to expand...
Click to collapse
Hi Lukas, Thanks for reply. I did re flash but I m still not getting lighting up screen notification when I receive any SMS.
Actually is it possible for Dev team to glow up Menu, Home, Back and Search button lights up or blink when we miss any call or SMS ?
That will be really great, what you say

anichhatre said:
Hi Lukas, Thanks for reply. I did re flash but I m still not getting lighting up screen notification when I receive any SMS.
Actually is it possible for Dev team to glow up Menu, Home, Back and Search button lights up or blink when we miss any call or SMS ?
That will be really great, what you say
Click to expand...
Click to collapse
The screen won't light up for SMS outside of Gingerbread ROMs. As I said previously, I think this is because the ICS and JB ROMs that are built for the Infuse are being built off of code for phones which have notification lights. Phones with notification lights also don't light up the screen for SMS...they just light up the LED notification light.
I too wish that the screen would light up when I receive an SMS, as I'm completely deaf in one ear and don't always hear the notification sound. I've suggested it on at least one ICS ROM, but that suggestion never came to fruition.
I think it's just one of those things that most people don't care for. I enjoy the added functionality of JB, so I've just learned to live without it.
If it's a deal breaker for you, there are still some really awesome Gingerbread ROMs that you can flash that will still have the native SMS notification screen light up. Or, perhaps you can go into the Development subforum for whichever ROM you're running, and ask the developer if there is any way to add this functionality back into post-GB ROMs

Use GoSMS it has the features that you're looking for and it's FREE.

List of issues with AOSP rom's

There are a bunch of AOSP rom's for our phone, most of them share the same issues since it's the same code, with slight differences based on which commits they've added. I'm hoping we can list the common issues in one thread as a reference.
1. Data handoffs between 3g/4g - I believe this is now fixed in most of them after the RIL patches, right?
2. Call volume - This CM10 commit (http://review.cyanogenmod.com/#/c/24564/) should fix this. Not in most rom's yet
3. Bluetooth pairing, call connect, streaming - does this work fully in any AOSP rom?
4. Sleep of death
5. Wakelock caused after playing media (DirectTrack)
6. Camera issues, like save to sd. The JB mod camera hasn't been updated yet.
7. Misc battery life issues - are most of these due to #5?
8. Activation issues after a flash
9. Low video recording volume
10. Notification light problems
11. 160 char sms limit, MMS doesn't work
12. Problems waking up with home button
13. Screen redraw issues (these can be fixed by turning off hardware overlays, but that increases cpu consumption)
I think it would be very helpful if we could track which rom's had which fixes merged, since otherwise it's hard to tell without asking in each thread, doing a lot of searches, and trying out.

Slimbean:
-Wake lock issue still seams to be an issue, battery life is bad
-notification light not working when call/text/email etc come in. Will be patched on next release
-data seams stable enough (ril patch is active on most recent build)
-horrible battery life
-call volume will be patched on next release
-home button to wake up phone is hit or miss
-odd screen glitches every now and then (fully live withable)
-mms sending takes forever, needed several reboots to even get it to work
-if usb fast charge is available in your kernel, it has a toggle for it in the notification tray (awesome)
-did I mention the battery life is bad?
-soft key light options do not work
I'll report more as I find them. I like these threads, good call.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

Great idea for a thread!
Add low video recording in all AOSP Roms. As far as I know this has not been fixed yet.

Sticky?
Sent from my SCH-I535 using xda app-developers app

- continuous WiFi connectivity issues (none of the AOSP roms worked reliable for me)

annoyingduck said:
Slimbean:
-Wake lock issue still seams to be an issue, battery life is bad
-notification light not working when call/text/email etc come in. Will be patched on next release
-data seams stable enough (ril patch is active on most recent build)
-horrible battery life
-call volume will be patched on next release
-home button to wake up phone is hit or miss
-odd screen glitches every now and then (fully live withable)
-mms sending takes forever, needed several reboots to even get it to work
-if usb fast charge is available in your kernel, it has a toggle for it in the notification tray (awesome)
-did I mention the battery life is bad?
-soft key light options do not work
I'll report more as I find them. I like these threads, good call.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
I am using slimbean 2.5 and I am getting anywhere from 16 to 24 hours of battery life on a single charge (3-4 hours of screen) which is about normal for any AOSP/AOKP based rom.

I actually made a similar list, but deals with comparing TW quirks to AOSP quirks:
Touchwiz VS. AOSP
Touchwiz:
- No Bluetooth and Aux input simultaneously
- Wallpaper Cropping forced to non-scrolling
- No way to disable auto volume reduction upon headset plug-in
- God awful front end interface design (this is more of an opinion)
- Google Music will randomly stop working, requires screen to be turned on for it to start playing the next track
AOSP:
- Volume Quirks (upon reboot, media volume will play quiet regardless of where the slider is, if maxxed you must turn it down and then up again similar to the call volume issue)
- Call Volume at Max every call (wasn't this fixed recently?)
- Wrongly uses noise reduction mic for recording (thus quieter)
- Inferior Camera (features mainly)
- Worse battery life
- Sometimes drops data
- Not as buttery as ICS for some reason (recents excluded)
- Will frequently kill background apps, making 2GB of ram somewhat pointless
- Bluetooth streaming issues (This doesn't personally affect me but I thought I'd throw it in anyway)
Basically, the one with the shorter list wins. So, I'm on TW for now but I yearn for the AOSP list of quirks to shrink.

Div033 said:
- Wrongly uses noise reduction mic for recording (thus quieter)
Click to expand...
Click to collapse
I've been told this has been fixed, but I still experience it. Is there a workaround for this currently?

I believe that there is a big tracker which is linked to on the irc chat. I would link to it but I'm not at my pc.perhaps someone could do so?
#verizons3 on freenode
Sent from my Galaxy Nexus using Tapatalk 2

bobloblaw1 said:
I believe that there is a big tracker which is linked to on the irc chat. I would link to it but I'm not at my pc.perhaps someone could do so?
#verizons3 on freenode
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This 1? http://tinyw.in/25QW

Number 6 is not really a problem. It's all based on personal preference.
Number 1 was fixed. Sleep of death could be kernel and/or clock speed settings. Mms works fine. There is a fix somewhere for direct track. Battery issues? Umm mines been perfect. That could be contributed to people not knowing what's causing wake locks and not fixing it. Not sure how anybody is getting screen redraws I haven't disabled hardware overlay and mine is fine, using apex if that makes a difference.
Most if not all of those issues are non existent in liquid smooth.

Hope this is the right spot to post this question. I tried flashing 2 separate roms today (Slim Rom and Liquid Smooth) which I believe are both AOSP, but I could be wrong. On both occasions, it starts to boot and gets to the google account login screen and the screen on the phone just keeps flickering and goes black.
I am unlocked, obviously rooted, with CWM 6.0.1.1 and have flashed JB TW rom in the past with no problems but went back to TW ICS, which I am currently running now.
Anyone know or direct me to the right thread as to why the screen flickering happens after flashing these AOSP roms? I haven't tried CM10 yet because these other roms actually sound more stable than CM10 right now.
Any suggestions? Thanks in advance.

bales3795 said:
Hope this is the right spot to post this question. I tried flashing 2 separate roms today (Slim Rom and Liquid Smooth) which I believe are both AOSP, but I could be wrong. On both occasions, it starts to boot and gets to the google account login screen and the screen on the phone just keeps flickering and goes black.
I am unlocked, obviously rooted, with CWM 6.0.1.1 and have flashed JB TW rom in the past with no problems but went back to TW ICS, which I am currently running now.
Anyone know or direct me to the right thread as to why the screen flickering happens after flashing these AOSP roms? I haven't tried CM10 yet because these other roms actually sound more stable than CM10 right now.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Disable hardware overlay in developer options

Neverendingxsin said:
Disable hardware overlay in developer options
Click to expand...
Click to collapse
That might work, but I cannot even get into the OS to disable anything. It is completely unusable when I flash any of these roms.
Would there be something out there that I could flash in CWM to disable this in the rom pre-boot?

bales3795 said:
That might work, but I cannot even get into the OS to disable anything. It is completely unusable when I flash any of these roms.
Would there be something out there that I could flash in CWM to disable this in the rom pre-boot?
Click to expand...
Click to collapse
Nothing that I know of sorry.

One of the main reasons I don't use any AOSP roms is because of the bluetooth sync issue. In two of my cars, it will sync for the first time, but any other time I get in the car it won't pair up. I have to manually connect it every single time.

wifi errors, i get out of range and or wps failed on any aosp rom.

I find that signal is just not as strong as compared to Touchwiz roms.
Sent from my SCH-I535 using xda app-developers app

ROM: CM10 M2
Using Android Pro Widgets (the APW People widget in particular), it lags (the widget, not the ROM). Anyone run into this issue? Not a big problem, just curious.

Any word on when the call volume is going to be merged into the CM10 build for d2vzw

[Q] May be a BUG in Camera

First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad

prasad_m said:
First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad
Click to expand...
Click to collapse
First off, just for future refference, there are 2 threads for Albino's rom already.
One is in the development section and one specifically for troubleshooting like this post is in teh Q and A Section. In the future please search for an existing thread rather than create a new one. This helps keep XDA a little more organized.
Now onto your problem...
I agree with everything you said. The torch and the camera don't work at the same time. The camera needs access to the LED to work, and obviously so does the torch. When the torch is already on the camera doesn't have access to it. It's like trying to put 2 keys into the same lock at once.
So since the camera app reads the device to see if the hardware it needs is available, when it finds the LED isn't available it shuts down. Even though the torch itself has timed out and has gone off, the torch app is still running and it controls the LED hardware until the app stops. so even though the light is off, the camera still can't control the LED hardware.
This is an overly simplified explanation, but this is what's going on.
We discussed in the dev thread that the camera app can run the led constantly during video so this isn't being done on purpose to prevent a reboot due to extreme battery drain. Its just a conflict for hardware resources. But since the camera can keep the led on there is no reason to have the torch app keep the led on, so there is no reason to really fix this bug.
Again though, the camera still fc's after the led times out because the torch app is still in control of the led hardware. So you have to remember to turn off the torch. That's also why the notification bar says the torch is on, even though the led is off. The torch app is still running in the background, which is what the notification bar is rally indicating.

Thanks I thought I should mention here if it is a Bug, BTW I was not aware how to start a thread within the Albino's ROM.
I can see only option Reply to someones thread. I found new thread here and hence the confusion.
Anyways thanks.
Love and regards
Prasad

[Q] Samsung GT-N7105 Note 2 CM 10.2 stable update?

Hi. I am asking this here, since I don't have permissions yet to comment in the Note 2 thread.
I installed CM 10.1.3-stable on release day and there are obviously stuff missing compared to stock (like NFC and Beam icons (and the features too i think) in the pulldown menu, hand-over to wake from sleep, etc)
Trebuchet crashes sometimes too but not too often. (but i'd hardly call it stable )
But especially, I have problems with phone call sound quality and general buggyness when it comes to the phone part altogether.
I could not get CWM to install either (screen just flickers and continues boot, had to install some other recovery. (Pointing it out since the install instructions says to use CWM) I know the thread is for Nightlies, but i cant find a thread for Stable. And i dont have permissions anyway.
So i was wondering if anyone knows if there's any 10.2 nigthlies that are better than 10.1.3 Stable, and if it is, when will 10.2 be stable ?
Overall I've had a nice experience with CM 10.1.3 though. Not gonna uninstall. But i hope development will continue
Edit 1: Also, the meter for GSM signal strength also doesnt turn blue until you turn on wifi. But then both become blue if you enable WiFi.
And i dont think ive seen it deviate from 100% GSM strength. I used to have some variance in my house before i think. (but dont quote me on that one)