Related
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.
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
I have problem with rom cm 7.2. This rom is the best, but i have a problem with display usage battery, i have a 70% usage. Brightness i have a low level and still is this problem, and my battery drain a very fast with using. Help me please
bump
I have the same issue. I found that on stock Rom the main reason of battery drain so fast was dialer, now on cm7 display take about 50%
Try CM9... battery works for up to 2 days at normal use... Instead of the lopusy 12 hours on stock and cm7...
on cm9 i have this same
Since I am not allowed to post in development section (new user, 10 posts rule) this thread title is the closest one to my questions. I am currently on latest CM7 rom (thanks adlx.xda) and I am facing some issues.
First of all, the rom itself is great. It would be nice to update it with the latest sources. I tried all versions and in the last one there is a huge scrolling lag that was not present in the previous versions (one can see this in browser, opera mini etc. when scrolling down or up with physical keys). I think it has something to do with framework, but not sure. I ported another CM7 rom from various different phones, using adlx's as a base, and those didn't have that lag, but I couldn't remove the default on-screen keyboard because when I remove it the sym key when pressed keeps popping up to select input method.
Speaking of keyboard, when I use browser or any other browser (except opera) the key "enter" will not open the selected link. It will do nothing. This is only on CM7 and SuperOSR. It is working properly on stock, CM9 and CM10. This is very much needed since sometimes I am having trouble opening a link with my big fingers so I use the arrows to select a link and enter to open a link. I have tried to play with the keypad files but without much success.
The last issue I was having has something to do with the camera. I don't care about the front cam, I believe 90% of us doesn't care about it as well. But I was having issues with flash. It is out of sync most of the times. It works, but it is not in sync with the actual moment of taking the pictures so most of the times my pictures are dark and sometimes not visible at all. But I can live with that, just wanted to point it out.
Adlx, I hope you read the general section, and I would really appreciate if you could give me some pointers about keypad files and why enter button when I try to open a link with it is not working only in those two roms.
Best regards.
S
Little bump. Still need 2 more posts
Hi,
Just installed latest ROM - cm-12.1-20150518-NIGHTLY-bacon.zip .
Everything works well, I was hopping to fix the touchscreen issues (the phone is less sensitive than CM11), but feels the same as CM12S.
Anyway, if I am adding a new profile, and set it up based on my needs (for example to disable the look screen when I am home), after rebooting the screen is black, notification bar is running, I can expand it, but that's all I can do.
I cannot start any app, desktop is black.
Anybody having the same issue?
Thanks
paulserban said:
Hi,
Everything works well, I was hopping to fix the touchscreen issues (the phone is less sensitive than CM11), but feels the same as CM12S.
Thanks
Click to expand...
Click to collapse
CM reverted the change due to high battery drain, use an earlier nightly such as 20150515 (or a custom kernel like Boeffla beta15, ak246). Once it is fixed, it'll be re-added to the CM Repo.
As for the profiles part, I have not encountered that issue, however I am not on the CM's nightlies, but on temasek's custom forged.
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.1.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
bakmanhans said:
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.2.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
Click to expand...
Click to collapse
I've been tempted by the idea of jumping the MaximusHD rom ship for a while too. Are you happy with the camera performance? One of the reasons I'm reluctant to go the non-Sense rom way is the lack of the full hardware access to the camera on those roms.
I just jumped the ship three days ago. I didn't use the camera besides taking 3 pictures for test purposes. I'm a long time Camera ZOOM FX user so the app installed itself again. I replaced the CM12 camera app in the drawer with it.
I need more user experience time with the camera to tell you it lacks in any way.
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
bakmanhans said:
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
Click to expand...
Click to collapse
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
twotimer said:
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
Click to expand...
Click to collapse
I can't find slow motion video. I never saw it in the MaximusHD ROM either. ZOOM FX cam does have the HDR option, just like with MaximusHD. But seriously, it's nothing more than a gimmick. Do you ever use it?
twotimer said:
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
Click to expand...
Click to collapse
With stock CM camera I don't see these options. This cam app is really minimal. Some say you need to set resolution by entering the hamburger menu upper-left but I don't have the menu. App version is 2.0.002.
With ZOOM FX Premium all resolutions settings are there.
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
bakmanhans said:
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
Click to expand...
Click to collapse
It's not part of the ROM, it's rather a part of the bootloader itself. You can change it by flashing a modified bootloader version:
http://forum.xda-developers.com/showthread.php?p=38387544#post38387544
Just read the thread on how to do that and find the one that fits your HBOOT version.
Coming from MaximusHD my hboot is at version 2.16... I don't see any download for that.
I've been using 20151223 UNOFFICIAL for some time now without the camera/flashlight issue. I've been using the camera more than once during the holidays.
Only trouble I have is getting cellular (3G) back online after flight modus. It's not possible. I have to restart the device every time. Anybody else experiencing this?
No, working great here on 2015-12-23 Unofficial HBOOT 2.16 from Flyer. When going out of plane mode, it takes around 15 seconds to get H icon (for HSDPA, 3G if you prefer). It may be a problem with the SIM card or advanced operator settings.