Hi guys,
i just installed the newest nightly CM10 (18.09.2012) on my galaxy tab 3110.
first i noticed that in navigation bar the back and multitask buttons are replaced.
second i noticed these buttons are smaller than bevor with nightly build 14.09.2012.
i figuered out how to replace the buttons again and saved the settings.
my problem is as followed:
since the new nightly update my navigation bar is not specific. everytime i have to touch the buttons a bit left and they work.
if i touch them in the center or a bit right there is no action and the buttons are not responding.
only the home-screen button is working well so far.
has anyone noticed this problem? can i solve it?
does this problem depend on the smaller navigation-bar buttons?
i hope you can help me.
thanks
Just try aokp rom it has a full control of navigation buttons (like cm10 but more customizable) and based also in jelly bean
Sent from Galaxy S2 or Galaxy Tab2
thanks for reply.
i dont want to change my rom. before the new nightly everything was ok and the navigation-bar was not customizable, so nothing was wrong and everytime i touched the buttons they responded 100%
does anybody have the same problems like me when touching the navigation-buttons they cant be touched in the center or a little bit to the right of them?
EDIT:
So it seems the problem is known by other users as well.
I would like to downgrade to an older nightly build. is this possible? can anybody tell me how to do it?
can i just put the older nightly .zip on internal sd-card and flash it like all the other "updates"?
thanks
EDIT:
So it seems the problem is known by other users as well.
I would like to downgrade to an older nightly build. is this possible? can anybody tell me how to do it?
can i just put the older nightly .zip on internal sd-card and flash it like all the other "updates"?
thanks
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 am running PA on my galaxy s4 I9505 International and everything is working fine... Only problem is that sometimes when I get a notification and Hover popes up my screen sometimes flashes black on and off. I believe this is a issue with the framework and that this may be fixed in a future update but in the meanwhile is there anything I can do to fix it? Or do I just have to wait to PA fixes it...
pcmaster44 said:
I am running PA on my galaxy s4 I9505 International and everything is working fine... Only problem is that sometimes when I get a notification and Hover popes up my screen sometimes flashes black on and off. I believe this is a issue with the framework and that this may be fixed in a future update but in the meanwhile is there anything I can do to fix it? Or do I just have to wait to PA fixes it...
Click to expand...
Click to collapse
I'm having exactly the same issue, I've been googling for a while, but found nothing so far! Do you have any new information by any chance?
i tried 4 or 5 roms lollipop but this issue seem happen with cm12 . Can anybody confirm ?
The issue is the navigation buttons does not turn off after screen turned off (you can check by turn on screen then turn off right immediately , the light still there)
hoangtu2410 said:
i tried 4 or 5 roms lollipop but this issue seem happen with cm12 . Can anybody confirm ?
The issue is the navigation buttons does not turn off after screen turned off (you can check by turn on screen then turn off right immediately , the light still there)
Click to expand...
Click to collapse
i am using AK.068.OPO.SKULL.CM12 Kernal with LiquidSmooth nightly, and this problem seems to be fixed most of the time. - still happens once a while. but much much better now.
I had this with older temasek but v3.3 seems to have it fixed now
Sent From Lollipopified Bacon Goodness!
I had my pre-owned SAMSUNG Galaxy Note Edge (SM-N915G)
running on Android OS 5.1.1 for almost a year.
The phablet was doing fine all along, until recently...
when the new OTA update Android 6.0.1 was made available
in my region my phablet start to show signs of malfunction
especially to the edge screen.
The edge screen's briefing panel always jam
& unable to load up whenever after a rebooting
of my phablet. The only lame-man method that I know
to solve my problem temporary, is to uncheck the panel...
confirm the setting & go back to re-check the panel...
re-confirm the setting again.
Anyone knows how to fix this problem permanently?
I've even tried full reset via [Vol. Up] + [Home] + [Power],
but it still didn't solve the problem.
Also, the update has been draining the battery like crazy.
Sent from my SAMSUNG-SM-N915A using XDA-Developers mobile app
I just haven't got time to downgrade the OS that's all
to see if it's the OS fault or not.
But funny... my the other Note Edge didn't have such issue.