This is the third or fourth time downgrading. Unfortunately I've encountered bugs, performance issues and force closes in various system applications.
Last night, I tried AGAIN to move forward and update. The latest update was 4.3. Unfortunately 4.4 has not yet been released and even if it was it is likely to come with bugs until an update or two rectifies any issues.
Now, these are some problems/bugs experienced with 4.3:
1 - Camera is now laggy whereas on 4.2 is was silky smooth. Only improvements I see on the latest update is a decrease in both noise/iso sensitivity as well as many other various camera effects.
Focusing takes far longer than before.
2 - Sound Settings keeps force closing in the 4.3 update. I'm not able to access or change the xLoud setting. I've cleared data, cache and even re-flashed. Keeps crashing. Downgrading to 4.2 solved this issue. Sound is LOUDER and xLoud works as it should.
3 - Screen - There is a slight delay when finishing from a call. It takes a few seconds for the proximity sensor to wake the screen to end the call. On 4.2 it is instant.
4 - Performance issue. 4.2 was smooth, fluid and instant. 4.3 feels heavier and not as quick as it previously was.
Therefore, with the above issues, I've had no choice but to downgrade. There were more advantages in 4.2 than in 4.3 which had issues, unfortunately.
I hope these problems are solved in the upcoming 4.4 Kitkat. Could other users share any problems caused by the latest updates? Was the stock 4.2 rom any better?
Sorry, pal, I am on 4.3 .136 and the only thing I have observed is the laggy proximity sensor, which was fixed after some calibration (search for Hammdog's post). No traces at all of the other problems you mention. Camera shots are far better, and overall performance is excellent. Is it possible that you experience some sort of software incompatibility due to the apps you use?
Sent from my C6833 using XDA Premium 4 mobile app
stopa10 said:
Sorry, pal, I am on 4.3 .136 and the only thing I have observed is the laggy proximity sensor, which was fixed after some calibration (search for Hammdog's post). No traces at all of the other problems you mention. Camera shots are far better, and overall performance is excellent. Is it possible that you experience some sort of software incompatibility due to the apps you use?
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ahh, so the laggy proximity sensor was a problem for others, not only me.
In 4.3 .136, the camera is better as you said but I'm experiencing lag, it's slow and takes 3-5 seconds to focus should the light be poor.
4.2 camera was substantially faster. Any reason why my sound settings keep crashing on 4.3?
so it crashes even after a CLEAN re-flash or factory reset?
clean as in no app data restored, just pure stock naked rom
Saikyo_San said:
so it crashes even after a CLEAN re-flash or factory reset?
clean as in no app data restored, just pure stock naked rom
Click to expand...
Click to collapse
Yes. The ONLY thing crashing is when attempting to open the sound settings and enable the xLoud option. Force closes even after flashing, factory reset, etc.
my humble opinion is that in the same situation i'd either stay on 4.2 or just root, get recovery and flash a stock based custom ROM or some AOKP, PA goodness or maybe GPe ROM
i have not encountered this issue before nor have I heard of it
Saikyo_San said:
my humble opinion is that in the same situation i'd either stay on 4.2 or just root, get recovery and flash a stock based custom ROM or some AOKP, PA goodness or maybe GPe ROM
i have not encountered this issue before nor have I heard of it
Click to expand...
Click to collapse
GPe Rom sound like a nice idea.
However, I'm thinking to patiently wait for the highly anticipated KitKat to be officially released.
That said, staying on the current 532 Android 4.2 will make rooting easier before upgrading to 4.4.
No issues (incl proximity sensor or cam lag) for me on any 4.3 rom. If we were all having xloud fc there would be many threads about it - so it's not a Sony 4.3 issue, it's a @kanej2006 issue (not having a go at you, just saying your problems can't be automatically assumed to be problems for all and therefore flaws in 4.3)
Sent from my C6833 using Tapatalk
iBuzman said:
No issues (incl proximity sensor or cam lag) for me on any 4.3 rom. If we were all having xloud fc there would be many threads about it - so it's not a Sony 4.3 issue, it's a @kanej2006 issue (not having a go at you, just saying your problems can't be automatically assumed to be problems for all and therefore flaws in 4.3)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Very strange as I only had these problems when upgrading to 4.3. Hopefully, these issues will be resolved in the future when upgrading to Kitkat.
Related
If I am currently on jokersax beta 0.6.9.2, can I just flash the updated rom over my current version? Or do I have to wipe data and cache in order to flash it? Because I've been thinking about getting around to updating but would rather not lose anything. My other question is if the update to 0.7.0.0 would be worth it. Is there large fixes or just small bug fixes? Thanks ahead of time for your help.
guitaristjoel said:
If I am currently on jokersax beta 0.6.9.2, can I just flash the updated rom over my current version? Or do I have to wipe data and cache in order to flash it? Because I've been thinking about getting around to updating but would rather not lose anything. My other question is if the update to 0.7.0.0 would be worth it. Is there large fixes or just small bug fixes? Thanks ahead of time for your help.
Click to expand...
Click to collapse
I would not recommend it. Version 7 was made primarily as a base for a Jellybean port that Joker was working on, and appears to use a different GPU driver that fixes browser rotation but also lowers performance. You're better off waiting for the next version.
OK. I've been considering just waiting until a stable release anyway. So, now I think I will. Thanks.
Sent from my MB860 using xda app-developers app
There are two different ROMs:
0.7 - Normal
0.7 - Special
Flash normal one, and everything will be fine.
I saw that. But will that be incrementally better than 0.6.9.2? Or lots of fixes?
Sent from my MB860 using xda app-developers app
guitaristjoel said:
I saw that. But will that be incrementally better than 0.6.9.2? Or lots of fixes?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
As my experiences in these CM9s, the 0.6.9.3 is most stable. But like any other CM9, the camera issue is really big to have been preventing me to install. Additionally, the FingerPrint scanner has never worked, either.
Let's keep waiting till the official ICS will be realeased by Moto
guitaristjoel said:
If I am currently on jokersax beta 0.6.9.2, can I just flash the updated rom over my current version? Or do I have to wipe data and cache in order to flash it? Because I've been thinking about getting around to updating but would rather not lose anything. My other question is if the update to 0.7.0.0 would be worth it. Is there large fixes or just small bug fixes? Thanks ahead of time for your help.
Click to expand...
Click to collapse
No need to wipe anything. Just install the zip for updates. And yes, it is better.
There are two different roms:
0.7.0.0 is the update
0.7.0.0 Special has Jelly Bean elements. It is a work in progress.
So, once the atrix gets an official ICS update from Motorola, and we get a stable build of CM9, will we have to wait until the official 4.1 update to get a stable release of CM10?
guitaristjoel said:
So, once the atrix gets an official ICS update from Motorola, and we get a stable build of CM9, will we have to wait until the official 4.1 update to get a stable release of CM10?
Click to expand...
Click to collapse
There is no guarantee of an official 4.1. But we will get CM10 in some form.
Will it be stable though if we don't have the 4.1 drivers?
guitaristjoel said:
Will it be stable though if we don't have the 4.1 drivers?
Click to expand...
Click to collapse
You are confusing stable with compatible. Stable means all of the bugs have been worked out. We will not know if ICS drivers are compatible with JB until they are released.
If ICS drivers are not compatible with JB, major aspects of JB can still be ported to ICS (though it will probably not be the same as pure JB).
OK, thanks! That's just the explanation I needed.
0.7.0.0 issues
I installed from 6.9.1 to 0.7.0.0 last night and would like to report my findings. Let me start by saying I am new to the whole changing ROMs and kernels etc. so I am sure I haven't checked everything just yet. The problems I have found so far are as follows:
1. When using the ICS or ICS+ browser it seems to randomly decide to reset itself back to the initial google page. Iknow I read a post somewhere that reported Opera browser was not working either. Anyone know of a working browser for this release?
2. There is an issue with watching online video. I can watch streams from CNN, YouTube, Fox News just fine. When trying to watch anything on Netflix I only get audio with a black video screen.
3. Battery so far seems to be lasting about the same as 6.9.1 but I probably need more time to make a better evaluation.
4. Camera is working fine. Of course the Video camera is not working.
I am using Apex launcher with Jelly Bean theme and no issues. The only reason I am posting here instead of in the development thread is because I do not have enough posts yet.
does the biometric reader work on the ICS roms for the Atrix?
JayMax03 said:
does the biometric reader work on the ICS roms for the Atrix?
Click to expand...
Click to collapse
Not yet
Follows are outstanding issues over ICS roms which are still in waiting for resolving:
1. Camcoder (video recoder)
2. FingerPrint scanner
3. 2D renderer
4. Some browser problem relating to flash player
5. Crystal Talk (call noise canceller)
Hi guys,
I've been searching for a fully stable flashable .zip for the JB 4.2 camera&gallery app with Photosphere. I have tried "4CamNex2.zip" & "4.2Camera_t04.zip" apps. The latter with slightly improved stability, (photosphere, panorama etc. working) however main issue/bug is: in standard photo taking mode, if you tap the screen to focus (or pre focus) and then take the picture, camera and gallery crash - Quite frustrating.
I've wiped cache&dalvik and re-flashed zip etc. (this helped as the first time I flashed the zip, photosphere was not working - solved by clearning cache & re-flashing)
Running:
Liquidsmooth v2.1 - 4.2.2
Siyah kernel 1.9.1
Thanks for any input!
Questions Welcomed also
UPDATE:
The crashing only occurs when the flash comes on. Forcing flash off or when there is enough ambient light you can pre-focus on a spot then take the pic.
I think currently there is no camera stable for 4.2.
I'm very interested in this as well (who wouldn't be?). I wonder if anyone is even working on it, and where we could perhaps track the progress. I don't see anything in the log tracker but I could have missed it.
LudicrousPeed said:
I'm very interested in this as well (who wouldn't be?). I wonder if anyone is even working on it, and where we could perhaps track the progress. I don't see anything in the log tracker but I could have missed it.
Click to expand...
Click to collapse
when Cm10.1 nightly builds reach stable stage youll be able to use this camera with photosphere normally, now its just expérimental..
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
they never will. CM said it will be stable only if Samsung release the sources, which will not happen
how to i delete this...
you have a completely different device
Dont know why but jb+ camera works perfect on aosp roms. No touch to focus issues, front camera working perfect.Only persisting issue is that sometimes sound on recorded videos is very low. After hundreds of hours testing and trying to reproduce the bug i thing it is related to notifications or sound volume adjusting. For example:when i recieve some notification immediately after booting my phone and then i want to grab some video-recorded sound is too low..... Can someone tell me if its kernel, rom or what? Why touch to focus works perfectly on jb+ camera without samsung exynos4 sources but this bug is still present. I just cant sleep.......
Glebun said:
you have a completely different device
Click to expand...
Click to collapse
Sorry, wasn't paying attention.
Can anyone provide a download link to the standard jellybean (4.2.+) camera apk/zip?
I did find this camera worked quite well (stock samsung one that is), with the exception of no photosphere (which is only really usefully for showing off to be honest)
I'm having an issue with every rom except the stock rom with the phone automatically rebooting itself while doing simple tasks and showing a green screen. I tried enabling force gpu rendering etc but still getting this. Though with any stock roms (default rogers rom + the jb 4.1.2 for att etc) i dont occur this issue. What could be the problem?
Yeah this happens wayyy to often on 4.2.2 roms a little bit less on 4.1.x roms.
arberthebarber said:
I'm having an issue with every rom except the stock rom with the phone automatically rebooting itself while doing simple tasks and showing a green screen. I tried enabling force gpu rendering etc but still getting this. Though with any stock roms (default rogers rom + the jb 4.1.2 for att etc) i dont occur this issue. What could be the problem?
Yeah this happens wayyy to often on 4.2.2 roms a little bit less on 4.1.x roms.
Click to expand...
Click to collapse
This is usual since we do not have the kernel source to make ROMS stable and not reboot. 4.2.2 ROMs are more stable then 4.1.2 so idk what you did there.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Rebooting on 4.2 ROMS
I'm having the same problem as OP with my i717 It happens bad on all of the 4.2 ROM's I've tried, and I know it's not the ROM. So far I've tried: Slim, Supernexus, CM10.1,ReVolt all of which I love! I really want to fix this. I start a game or other app and get a wildly flashing green, blue or sometimes black screen and then she reboots. Usually when opening a game or instagram, but not limited to those apps. It's hard for me to replicate the symptoms. Anyone else struggling with these symptoms on 4.2 roms? It seems less often on 4.1.2 ROM. When I restore a Blackstar ICS setup from twrp the phone runs beautifully. I've used darkside super-wipe hoping that would help. I've also tried changing recovery. Now I'm running out of things to try. I feel like somethings not being cleaned properly before install but I'm new so I don't really know.
Should I try using ODIN to flash a stock jelly bean firmware in order to sort of "start over fresh"?
I wish I could explain to everyone better my problem.
DollarStrawz said:
I'm having the same problem as OP with my i717 It happens bad on all of the 4.2 ROM's I've tried, and I know it's not the ROM. So far I've tried: Slim, Supernexus, CM10.1,ReVolt all of which I love! I really want to fix this. I start a game or other app and get a wildly flashing green, blue or sometimes black screen and then she reboots. Usually when opening a game or instagram, but not limited to those apps. It's hard for me to replicate the symptoms. Anyone else struggling with these symptoms on 4.2 roms? It seems less often on 4.1.2 ROM. When I restore a Blackstar ICS setup from twrp the phone runs beautifully. I've used darkside super-wipe hoping that would help. I've also tried changing recovery. Now I'm running out of things to try. I feel like somethings not being cleaned properly before install but I'm new so I don't really know.
Should I try using ODIN to flash a stock jelly bean firmware in order to sort of "start over fresh"?
I wish I could explain to everyone better my problem.
Click to expand...
Click to collapse
1) AOSP is unofficial so these is going to happen. 2) Is your screen flickering? 3) if so check HW overlays in dev options.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
It happens to PACman ROMs too, try listening to music while attempting to cause the crash.. .There will be a loud beeping sound, followed by the greenish-blue screen, then the device will shut off, and reboot
I got the crash on trying to wake the device to unlock, and grabbed a logcat using Catlog.
I had camera problems on liquid smooth 4.2.2 v2.4 kernel soap 3.0.76 so I was told that it was probably a hardware issue and i should probably revert back to 4.1.2 dont think so...Considering no camera app from gplay would work. So I would think it would had been a hardware issue also. So I wiped data dalvic and cach then flashed this ROM sons of android 4.2.2 kernel 3.0.70 soapKernel_05 then gapps rebooted and waited opened the camera and it works. Can't understand why the camera wouldn't work before.
The camera on the AOSP rom is a little dodgy for some people. If it shows the camera is disconnected, I can't remember the message it pops up, a battery pull will fix it usually. It is just am issue with the flash on 4.2 roms, if you touch to focus before taking the picture it will keep that from happening.
Sent from my SCH-I605 using XDA Premium HD app
webb7735 said:
I had camera problems on liquid smooth 4.2.2 v2.4 kernel soap 3.0.76 so I was told that it was probably a hardware issue and i should probably revert back to 4.1.2 dont think so...Considering no camera app from gplay would work. So I would think it would had been a hardware issue also. So I wiped data dalvic and cach then flashed this ROM sons of android 4.2.2 kernel 3.0.70 soapKernel_05 then gapps rebooted and waited opened the camera and it works. Can't understand why the camera wouldn't work before.
Click to expand...
Click to collapse
Well looks as if it wasn't a hardware issue after, which reverting back to 4.1.2 would have given you the same results. AOSP ROMs don't always play nicely with different types of hardware and the only way to rule hardware out as the culprit is to use the original software. Glad to see you got it working though.
https://dl.google.com/dl/android/aosp/mantaray-lmy47d-factory-63eade7f.tgz
Have fun!
Hm, it's been sitting on "sending bootloader" for a while now. Should I be worried?
So far feeling very good and fast, nice update
Rand Brittain said:
Hm, it's been sitting on "sending bootloader" for a while now. Should I be worried?
Click to expand...
Click to collapse
Welp, doing it over on a different port and cable seems to have handled it.
Flashed it.
Might be placebo but it seems much smoother.
Also the recent bug is fixed and the toggles in the Account Sync have been changed.
Images flashed......"optimizing app 98 of 154" so first 5.1 boot should be soon.
Anybody tested this bug?
http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672
tylerdurden83 said:
Flashed it.
Might be placebo but it seems much smoother.
Also the recent bug is fixed and the toggles in the Account Sync have been changed.
Click to expand...
Click to collapse
What about wifi performance and the audio bug wile/straight after charging/docked?
I don't understand what the bug is. I never experienced it before, but I can try to replicate it in 5.1 if you explain what I am supposed to do clearly.
isarebe said:
I don't understand what the bug is. I never experienced it before, but I can try to replicate it in 5.1 if you explain what I am supposed to do clearly.
Click to expand...
Click to collapse
What I got is, sometimes when starting the N10 while charging, there is no sound at all, and I have to reboot the N10 without charging to get the sound back.
I tried with 5.1 and so far, 5-6 times, no bug, but as I said is only happening sometimes before...
Audio Bug Squashed?
It looks like 5.1 has fixed the audio bug. It has for me at least.
Anyone experience lag when pulling the notification tray on the home screen?
matejilic said:
Anyone experience lag when pulling the notification tray on the home screen?
Click to expand...
Click to collapse
Using the default Launcher3, not really. The Google Launcher lags when pulling down the tray, and lags all other animations for that matter. It always has since 4.4, but I put up with it because I like the GEL. It doesn't lag anywhere else thankfully, so it's your call.
On March 10th I did a factory image update to 5.1 but did not wipe user data on both my Nexus 10 and 5.. At least for me, this is the best version of Lollipop I've experienced.
My Nexus 10 was more stable than my Nexus 5 on any 5.0.x release but it seems that all the issues I'd been experiencing are resolved. On 5.0.x my Nexus 5 experienced the memory leak causing UI slow downs, odd reboots, total freezes needing power cycles and frequent disconnects of both WiFi and my cell network.
Android 5.1.0 did break the K9 email reader but that was fixed this morning and Jota+ SMB support currently is not functioning. On the Nexus 10 my battery stats still does not update always showing 100% charge even when its been off the charger for hours. Its been like that for a long time including with KitKat.
I am rooted and use a number of app beta versions including Nova Launcher, GMD Gesture Control and GMD Auto Hide Software keys, Viper4Android and they all worked before and after the OS update. That is a little surprising as previous Lollipop 5.0.x updates had broken more apps when they were first released. For the first time in a long time MX Player Pro still worked after an OS upgrade.
This was what the Lollipop release should have been. I'm happy especially as my Nexus 5 is as reliable as it was with KitKat.
That's great. Smooth
My 5.02 Nexus got an OTA to 5.1 last night (I'm in the UK). Everything seems fine and I am really happy that I have a tablet that is still supported.
Alan
Is anyone getting a screen freeze? Basically the screen just freezes but the unit seems OK ie it's not a system crash. It needs resetting to work again.
Sent from my Nexus 10 using XDA Free mobile app
Warren_Orange said:
Is anyone getting a screen freeze? Basically the screen just freezes but the unit seems OK ie it's not a system crash. It needs resetting to work again.
Click to expand...
Click to collapse
Sometimes, but always related with Chrome playing videos.
Hi.
I have narrowed it down to when i bring up google search with the swipe up gesture. Once on google search the screen becomes unresponsive. But a can reboot by pressing the power button and choosing 'reboot now'. I may try and reinstall it.
This only started happening with 5.1.
Sent from my Nexus 10 using XDA Free mobile app
Warren_Orange said:
I have narrowed it down to when i bring up google search with the swipe up gesture.
Click to expand...
Click to collapse
In my case I have that feature replaced by a more useful one: a handy launcher:
https://play.google.com/store/apps/...store&pcampaignid=APPU_1_cw0YVbWgJ8XTU_77gYgP
It never freezes.