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
This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m
Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:
Updates and Notes
Reserved
Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.
@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here
Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:
@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel: