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
My camera opens fine (running the app Camera ICS, problem occurs with stock camera app, however) but often will go black or offer to force close/wait when switching from back to front facing.
Also, when this happens, my notification power widget bugs (wifi will turn itself back on after turning off, brightness resets when turning off screen, etc.)
Anyone have a similar problem or fix to this?
I've been working on the kernel for the MTDEV CM7 and have implemented a few fixes that may help you. Check out the post below from Androidforums. Been a member for months and still can't post a link.
What's up everybody?
I've been working on kernels lately and found some differences that may be able to help. I took MTDEV-KERNEL-CM7-master, and added a few things.
1. Added camera functions: need to see if this fixes the issues with FFC, both switching to, and autofocus click.
2. Updated the touch screen drivers: updated drivers this should also fix the lines in the screen on wake up that some phones experience.
3. Added filesystem support. (details in the config diff below)
4. Enabled a bunch of debugging, so hopefully we can get some more info to see what is happening in the kernel. I think I missed some debug flags this time around but all in due time.
This is a test and should be treated as such, I will continue work as things progress and we get some feedback.
This is a flashable zip, just boot to recovery and flash as normal.
BSydz-MTDEV-CM7-Kernel-Camera-Touch-test-1
Click to expand...
Click to collapse
Maybe if I get up to ten posts soon I can help other devs with other phones, that I have wanted to post solutions for.
I recently installed the JellyBelly ROM v.3 (CM10) on my EVO Shift. I really appreciate the work that the devs are doing on this ROM. I am posting some bugs I encountered after running the ROM for a day. I hope this info helps make the ROM more stable and polished for the entire community. This is my way of giving back right now. Thanks for all the hard work guys!
Green Box During Boot Screen Bug - During boot the HTC screen with white background is displayed for a few seconds, then the boot animation appears. During the transition between the HTC screen and boot animation you can see the HTC screen turns into a green box and fills the upper 30% of the display for a second or two prior to the boot animation starting. This is not a critical bug, yet it may point to a larger underlying video issue in the system. If nothing else, it could give a poor first impression about the ROM quality due to graphic glitches.
Random Screen Freeze/SOD Bug - For no apparent reason the device would lock up and refuse to respond to touch input or pressing the power button. I was forced to remove the battery several times in order to reboot the device. I was unable to establish exactly what caused the lock up, but I was curious if the CPU settings and clock settings might be to blame?
Camera Green Line Bug - After I took a couple pictures I reviewed them in the Gallery app. I immediately noticed that my pictures all had a green line down the left side. I thought that perhaps the stock Camera app was to blame so I installed CameraZoom, a third party camera app as a replacement to the stock Camera app. The result was that the entire upper half of the images taken with CameraZoom app were solid green. I'm not sure if the driver or the app is to blame for this experience.
Facebook App Crash Bug - The Facebook app refused to launch without crashing for me.
I want to run this ROM as my primary ROM, but these issues, except for the Boot Screen Bug, are show stoppers for me. Keep up the great work. I look forward to version 4!
The boot animation thing happens even when there is no boot animation... All the others I have fixed except Facebook, working on that at the moment. Once that is fixed v4 will be up... Facebook seems to be taking up way more RAM than it should The camera line is caused by the 4.2 camera, I took it out and replaced it with 4.1 camera. BTW I got your message, but was unable to respond to it.
Been running this since V2 came out and have seen your issues as well. When the screen locks up I just wait for a minute or so and the current app stops and doesn't require battery pull. Can't wait for those fixes.
bilgerryan said:
The boot animation thing happens even when there is no boot animation... All the others I have fixed except Facebook, working on that at the moment. Once that is fixed v4 will be up... Facebook seems to be taking up way more RAM than it should The camera line is caused by the 4.2 camera, I took it out and replaced it with 4.1 camera. BTW I got your message, but was unable to respond to it.
Click to expand...
Click to collapse
Thanks for the info. What was causing the phone to stop responding to input and how did you fix it? Also, do you have a complete list of outstanding bugs that have been reported so far?
adamthomas77 said:
Thanks for the info. What was causing the phone to stop responding to input and how did you fix it? Also, do you have a complete list of outstanding bugs that have been reported so far?
Click to expand...
Click to collapse
Actually you got all the bugs reported except Netflix... I got Facebook working, but now wifi won't turn on
The main issue with JB on the Shift IMO is RAM dispersion, which is mainly what I am working on.
Great info! Also meant to ask, why are there two flashlight applications installed? Why is Flipboard installed by default? Seems like Flipboard is kind of an odd default app.
Because it is a work in progress (I was testing them and forgot to remove one), and flipboard works better than Facebook
bilgerryan said:
Because it is a work in progress (I was testing them and forgot to remove one), and flipboard works better than Facebook
Click to expand...
Click to collapse
Yes, but you'll soon have those issues fixed I'm sure. Looking forward to v4.
adamthomas77 said:
Yes, but you'll soon have those issues fixed I'm sure. Looking forward to v4.
Click to expand...
Click to collapse
Got Facebook fixed, but I don't like how much performance I am having to give up to keep it from crashing... I'm hoping there is a perfect median, I just haven't found it yet. I have noticed quite a bit of difference between launchers also. This is my first dive into JB, so it's been a learning process. Got one more thing to try tonight.
I have had issues with the keyboard. on V3 Im not sure how it will work out with the V4. In most cases i would have to hold the . Shift button instead of just tapping it one to cap a letter. and then it resumes to lower case letters. ive also had to Hold FN to Create symbols instead of tapping just once. to make that symbol. over all it is a great rom i do have by far great expectations of it . i will re-flash once. some of those kinks are out such as the green line on the photos. as far as 4g goes i can careless about it considering the fact that i have no 4g in my local area .
As far as FB Goes i never use it ( Its a relationship killer ) xD
None the less keep up the great work on Deving the Rom .
I look forward to future updates. and maybe a keyboard fix. where it was like originally having it .
( Also random Closing of the browser . Ive had a few on V3 . But as i said im not sure what V4 will have in store for me. )
v4 is up and most of said bugs have been eliminated:sly:
You can post any v4 issues here if you change the title of the thread.
I can't seem to find any similar topics to this so I'll post it here..
My phone has been doing this for around 5-6 months now I think, I don't really remember when it properly started. At random times, my phone's flashlight would turn itself on and if I go on the flashlight app to turn it off, the flashlight would turn off for a splitsecond (resembling a flicker) and then turn itself back on, this would occur with changing the brightness of it too. I'm on the latest ViperOneS JB rom, and I don't know what I can do to fix this. Do any of you know whether this is software or hardware related? I'll be happy to give more details upon request.
eLiTeOneS said:
I can't seem to find any similar topics to this so I'll post it here..
My phone has been doing this for around 5-6 months now I think, I don't really remember when it properly started. At random times, my phone's flashlight would turn itself on and if I go on the flashlight app to turn it off, the flashlight would turn off for a splitsecond (resembling a flicker) and then turn itself back on, this would occur with changing the brightness of it too. I'm on the latest ViperOneS JB rom, and I don't know what I can do to fix this. Do any of you know whether this is software or hardware related? I'll be happy to give more details upon request.
Click to expand...
Click to collapse
A quick search revealed the solution in this thread.
http://forum.xda-developers.com/showthread.php?t=2277912
Seems to be a known issue with that ROM.:good:
I love my XZP, especially now that we have Android 10 custom roms. My problem started when I was on pie with eXistenZ. My flashlight stopped working and as a result the camera also. I was able to get it back with a reset but it then failed again after awhile. I tried a 3rd party flashlight app but it still wouldn't work. By this time I was trying the various "10" roms and noticed I had no GPS which is an issue with some of these roms but I also had no compass. In test settings and in compass apps, it shows "no sensor". I reverted back to stock pie and that didn't change anything, even went back to oreo but no help.
I'm guessing it's time to toss it in the bin of broken phones but before I do I thought i'd pick everybody's brains here first. I have the back off and the flashlight led is..well and led and is integrated into the board so I'm just guessing it's toast. I'm not sure where the compass is or what it would look like but guessing it's probably integrated also, as opposed to say the camera or a speaker. So... open to suggestions.