Related
does anyone have the problem that the apn's dont save when entered on Szeso's 4.3 Rom? cuz it seems that every time i put it in and save it it disappears
matvey123 said:
does anyone have the problem that the apn's dont save when entered on Szeso's 4.3 Rom? cuz it seems that every time i put it in and save it it disappears
Click to expand...
Click to collapse
Well i dont have that issue you are saying. But try restoring your APN to default settings and use.
Make sure you save before exit. It should work then.
:good::good:
I check this also - no issue. Check the saving as meantioned above.
Incredibly Tapatalked!
idk i just went back to szeso's 4.2 because 4.3 has too many bugs and not everything works with it yet
root, WiFi and ringtone
matvey123 said:
idk i just went back to szeso's 4.2 because 4.3 has too many bugs and not everything works with it yet
Click to expand...
Click to collapse
Although with many bugs at present I like this rom, for me the top 3 problem that really have impact on daily usage is root, WiFi and ringtone.
Anyway, thanks Sezeso for his great job!:good:
dreamerforce said:
Although with many bugs at present I like this rom, for me the top 3 problem that really have impact on daily usage is root, WiFi and ringtone.
Anyway, thanks Sezeso for his great job!:good:
Click to expand...
Click to collapse
To gain root access you just need to flash SuperSu for 4.2 or 4.3. When I was using 4.3 I had no problems with Wifi.
Yea the wifi got fixed.
Press "thanks" if I helped you out!
root, WiFi solved!
matvey123 said:
To gain root access you just need to flash SuperSu for 4.2 or 4.3. When I was using 4.3 I had no problems with Wifi.
Click to expand...
Click to collapse
Yep, after flash the 2013.10.05 version ROM WiFi is OK now and as you suggested to flash SuperSu1.65 root also OK. Really great job for all you guys here! Thanks a lot!:good::good::good:
All bugs are fixed . Check this http://forum.xda-developers.com/showthread.php?t=2419875
wyhao109 said:
All bugs are fixed . Check this http://forum.xda-developers.com/showthread.php?t=2419875
Click to expand...
Click to collapse
and now look at second post and you'll see a full list of bugs present at latest build.
here they are:
# Capacitive buttons brightness bug: button's brightness is no longer changed when changing screen brightness - it always stays at max. Perhaps it's a side-effect of CM introducing new feature - controlling time-out of button's light
# Wi-fi on screen-off bug: when screen is turned off, wi-fi activity halts. I.e. if you download something through wi-fi and turn off display, then download will stop as well (actually it will continue through 3G, if available). Disregards setting about wi-fi mode with disabled screen. 3g continues to work with screen off without any issues. This bug was present in 10.1 as well and, perhaps, in 10.0 too.
# Flashlight bug: turns off, when screen is turned off.
# CRT-Off animation bug: screen turns off BEFORE playing CRT animation, while it should happen at the same time. Results in max brightness CRT-off animation.
# Green tint in camera bug: when taking photos through stock camera app in portrait mode, it will show green tint on "snap photo" animation. Actual photo is fine. Landscape mode works properly.
# Root access bug: It's not always possible to get Root access, even if all proper steps were taken.
# Failure to wake up from deep sleep bug: not really traceable. Happens randomly. Phone fails to wake up from deep sleep sometimes. It may happen when it's charging or just when it's idling on the desk, still, the bug appears regularly every few weeks. Might be caused by some voltage tweaks in kernel.
Click to expand...
Click to collapse
Shadowofagony said:
and now look at second post and you'll see a full list of bugs present at latest build.
here they are:
Click to expand...
Click to collapse
Maybe you forgot a sentence which is
Stable #3 bugz
and the latest build is #4
wyhao109 said:
Maybe you forgot a sentence which is
Stable #3 bugz
and the latest build is #4
Click to expand...
Click to collapse
Minor bugs were not fixed in Stable #4. Only the major ones were squished =)
For more information look here: http://forum.xda-developers.com/showpost.php?p=46347775&postcount=739
wyhao109 said:
Maybe you forgot a sentence which is
Stable #3 bugz
and the latest build is #4
Click to expand...
Click to collapse
yep, but these bugs are in stable 4 too, u can try it out. in stable 3 there was a few bus more.
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
Hey guys just looking for a definitive answer here. As 4.1.2 has no screen flickering bug, and on 4.3 it comes up automatically... I can assume its a software glitch rather then hardware .. then why isnt everyone having that issue? and why cant sony fix it.
I just updated to 12.1.A.1.201 and although the flicker has reduce, its still there in greys/blacks. Going back to 4.1.2 again.
magicali said:
Hey guys just looking for a definitive answer here. As 4.1.2 has no screen flickering bug, and on 4.3 it comes up automatically... I can assume its a software glitch rather then hardware .. then why isnt everyone having that issue? and why cant sony fix it.
I just updated to 12.1.A.1.201 and although the flicker has reduce, its still there in greys/blacks. Going back to 4.1.2 again.
Click to expand...
Click to collapse
cause sony sucks!! we said that.. they have your money they dont care any more i think a 20% at least have this flickering..
edit: check my thread and check the pictures http://forum.xda-developers.com/showthread.php?p=51553670
I have flickering bug on 4.1.2 with backlight turned off and auto brightness on
Sent from my C5303 using Tapatalk
I don't have any screen flickering things. Everything's normal with .266
hmm sound good to leave something here while watch what others feel about the new firmware before upgrading. Give some review guys
Just updated (only 9MB?!?!?). I'm on global generic firmware and still get the flickering screen with greys and blacks.
I don't think its as prominent as it was, and I definitely didn't get it with 4.1.2 software.
My screen is set to auto adjust its brightness and I think it's more noticeable when changing now.
That aside, its less laggy now!
The flicker issue was resolved by disabling adaptive brightness for me and some others but not for everyone.
Simple step...
Select wallpaper from album using google+ ( using scroll wallpaper)
Done
Hit the home icon 2 or 3 times
Problem solved.... Works for me.....
ArunThazhathuveetil said:
Simple step...
Select wallpaper from album using google+ ( using scroll wallpaper)
Done
Hit the home icon 2 or 3 times
Problem solved.... Works for me.....
Click to expand...
Click to collapse
That seems like an unnatural fix :S .. you have faced the screen flicker issue on 4.3 or 4.1.2?
magicali said:
That seems like an unnatural fix :S .. you have faced the screen flicker issue on 4.3 or 4.1.2?
Click to expand...
Click to collapse
Ha ha I will not even try it
ParaSense. said:
Ha ha I will not even try it
Click to expand...
Click to collapse
Neither will I
Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!
mrhnet said:
Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!
Click to expand...
Click to collapse
Doesn't work for me Thanks for the tip though
mrhnet said:
Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!
Click to expand...
Click to collapse
i have tried everything except pimp my rom... but i dont think it will solve this problem cause i have this flickering even in recovery (cwm,twrp) if 4.3 kernel is installed
ParaSense. said:
i have tried everything except pimp my rom... but i dont think it will solve this problem cause i have this flickering even in recovery (cwm,twrp) if 4.3 kernel is installed
Click to expand...
Click to collapse
Yes.. it looks like a issue at kernel level/gpu driver. But those workarounds worked for some. Maybe it could be another issue..
If you are still in 4.3, just type this in a terminal:
cat /d/clk/mdp_vsync_clk/enable
If it returns 0, type:
su
echo 1 > /d/clk/mdp_vsync_clk/enable
It fixed for some, but not sure whether it's the same "flickering" issue. Just a tip..
I have read this thread and (more other) and always wondering what are you people talking about??
Only flickering which I have seen on my sp was when I had auto brightnes on. But this is how auto brightness should work.
On 4.1 wasnt any flickering because auto brightnes didnt work on 4.1
On 4.3 work a little better, but not so good as for example in CM 11.
But when u turn off auto brightness there isnt any "flickering".
mrhnet said:
Yes.. it looks like a issue at kernel level/gpu driver. But those workarounds worked for some. Maybe it could be another issue..
If you are still in 4.3, just type this in a terminal:
cat /d/clk/mdp_vsync_clk/enable
If it returns 0, type:
su
echo 1 > /d/clk/mdp_vsync_clk/enable
It fixed for some, but not sure whether it's the same "flickering" issue. Just a tip..
Click to expand...
Click to collapse
I really dont want to install again 4.3 to try this (maybe it will work) not now at least.. but i will try it some time... thanks
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
That is happening on every 4.4 I think. It was on CM10.1, CM10.2 too.
Lag on calling screen
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
krazzykuldeep said:
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
Click to expand...
Click to collapse
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Klaas68 said:
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Click to expand...
Click to collapse
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
krazzykuldeep said:
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
Click to expand...
Click to collapse
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Klaas68 said:
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Click to expand...
Click to collapse
I installed the AOSP rom and it seems stable and maybe the call delay issue is better, still have to test it more.
I do however miss some nice functions which were present of the Carbon ROM:
- separate lockscreen background
- disabling the annoying Google Now bar on the homepages
- some fine tuning in icon colors
- kliing an app by long-press the back button
- defining hotkeys e.g. for the camera
and some more..
Is there maybe some package to install to add functions like this to the AOSP ?
Klaas68 said:
...
Click to expand...
Click to collapse
Use Xposed module for all what you need. Gravity Box or others module..
R_a_z_v_a_n said:
Use Xposed module for all what you need. Gravity Box or others module..
Click to expand...
Click to collapse
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Klaas68 said:
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Click to expand...
Click to collapse
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
shut_down said:
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
Click to expand...
Click to collapse
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Klaas68 said:
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Click to expand...
Click to collapse
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
shut_down said:
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
Click to expand...
Click to collapse
OK I did those 3 steps before flashing the new ROM. Sometimes I even had to do it twoce because the ROM did not install and raised a error 7 or so...
I think it was more a problem with the APN configuration and never before needed to do this manually...
Updating from 4.4.2 to 4.4.4
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
harsh3793 said:
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
Click to expand...
Click to collapse
If you dirty flash (just wipe cache/dalvik and install) the new version, you want loose your apps etc.
But I would recommend to do a clean flash (factory reset and format system), but before backup your apps with Titanium. After installing the new version you can restore your apps and data.
But anyway, before wiping/installing anything do a nandroid backup. So if anything went wrong, you can go back in just a minute.
solution ?
Klaas68 said:
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
Has anyone solved this problem ? I have this problem with every rom that i've tried. I'm losing patience with android phone.
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Wysłane z Light-fonika 1-2 ....
...
MikiGry said:
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Click to expand...
Click to collapse
I am stressed when receiving an incoming call and caller don't hear me. I wait from mobile phone calling without problems.
I just wanted to know if there is a ROM without this problem or if anyone have solution.:cyclops:
@ian2189
This is our phones problem. 99% of the users (me too) were expiring this since gingerbread 2.3.6 . So i think there isnt a solution. I now why it is happening but it is unfixnable.
Wysłane z mojego nexusowego tablecika.....
Yeah... I even bought another phone because of this...
I got my phone about a month ago. I updated the software to 4.4.2 kitkat released by sony. It's not rooted. This problem occured yesterday for the first time. When I call someone or someone calls me, the earphone doesn't work. I don' hear anything. When I run earphone test in Service tests, it works fine. The problem is fixed when I reboot the phone. But I can not reboot the phone everytime. It happened once yesterday and next time now. I am so pissed off. This is my first sony phone and so far I am very dissapointed. My audio jack flap is opening by its self and as I can see a lot of people complain about it. I hope this can be fixed
jankos98 said:
I got my phone about a month ago. I updated the software to 4.4.2 kitkat released by sony. It's not rooted. This problem occured yesterday for the first time. When I call someone or someone calls me, the earphone doesn't work. I don' hear anything. When I run earphone test in Service tests, it works fine. The problem is fixed when I reboot the phone. But I can not reboot the phone everytime. It happened once yesterday and next time now. I am so pissed off. This is my first sony phone and so far I am very dissapointed. My audio jack flap is opening by its self and as I can see a lot of people complain about it. I hope this can be fixed
Click to expand...
Click to collapse
Hi, is there any particular reason why you want to keep using stock firmware and not to root?
If not might I suggest rooting and using a custom firmware, because in my experience custom firmware is much more reliable than the stock.
Its really quite easy to do and the phone seems to benefit from doing a clean install getting rid of any junk thats built up over time.
Good Luck!
jankos98 said:
I got my phone about a month ago. I updated the software to 4.4.2 kitkat released by sony. It's not rooted. This problem occured yesterday for the first time. When I call someone or someone calls me, the earphone doesn't work. I don' hear anything. When I run earphone test in Service tests, it works fine. The problem is fixed when I reboot the phone. But I can not reboot the phone everytime. It happened once yesterday and next time now. I am so pissed off. This is my first sony phone and so far I am very dissapointed. My audio jack flap is opening by its self and as I can see a lot of people complain about it. I hope this can be fixed
Click to expand...
Click to collapse
I recommend you to use SUS or Sony PC companion to "reinstall" FW i am not sure if this can help you but its better than sending it to repair center without trying anything. Good luck and don't forget to backup you data, etc.
Same Earphone problem
Hello, i have the same issue too. Every rom (stock based) i install, that use 4.4.2 have the same issue.
Its very annoying, have someone can resolve this?
I have, UB and at moment ExistenZ Rom
I just opened the forum to make a thread about this, as I'm facing the same problem and it can get really annoying.
Sometimes my phone works normally for 3-4 days, and then it just suddenly happens. Someone calls me, and I can't hear them, but they can hear me...and after I reboot it usually works.
I flashed the 4.4.2 UK Generic a few days ago, and now I face two different problems regarding calls : first one is like this, I can't hear people that are calling me, and the other is that sometimes I don't hear them for a few seconds and then I hear them again, and then again I can't during the call. Don't know if this is firmware based, I guess it is. If I can remember correctly 4.3 worked perfectly, as I got the phone already on 4.3 firmware.
Also Cyanogenmod has the same issue, as well as PAC-man (some versions of these ROMs, the ones I tried LOL) so I'm wondering could it be a hardware issue...what are your experiences? If someone can confirm that it is a firmware issue and that 4.3 doesn't have these problems, I might actually switch back because its annoying and the phone seems to be working better on 4.3, even though I love the transparent interface of Kitkat =)
Have a nice day guys, hope we will fix this issue !
amar92 said:
I just opened the forum to make a thread about this, as I'm facing the same problem and it can get really annoying.
Sometimes my phone works normally for 3-4 days, and then it just suddenly happens. Someone calls me, and I can't hear them, but they can hear me...and after I reboot it usually works.
I flashed the 4.4.2 UK Generic a few days ago, and now I face two different problems regarding calls : first one is like this, I can't hear people that are calling me, and the other is that sometimes I don't hear them for a few seconds and then I hear them again, and then again I can't during the call. Don't know if this is firmware based, I guess it is. If I can remember correctly 4.3 worked perfectly, as I got the phone already on 4.3 firmware.
Also Cyanogenmod has the same issue, as well as PAC-man (some versions of these ROMs, the ones I tried LOL) so I'm wondering could it be a hardware issue...what are your experiences? If someone can confirm that it is a firmware issue and that 4.3 doesn't have these problems, I might actually switch back because its annoying and the phone seems to be working better on 4.3, even though I love the transparent interface of Kitkat =)
Have a nice day guys, hope we will fix this issue !
Click to expand...
Click to collapse
For me, only the stock based rom haver this issue, i haver tested omni rom and works normal
numero13 said:
For me, only the stock based rom haver this issue, i haver tested omni rom and works normal
Click to expand...
Click to collapse
Thanks for the info. Haven't tried Omni ROM yet, I might. Can you just tell me did you have this issue on 4.3 ?
amar92 said:
Thanks for the info. Haven't tried Omni ROM yet, I might. Can you just tell me did you have this issue on 4.3 ?
Click to expand...
Click to collapse
In 4.3 stock, the earphone seems work well, but i want 4.4, and for some time it worked
Hi there
I'm having exactly the same issue on 4.4 (existenz ultimate)
I can confirm once I had this issue on stock 4.3 rom as well (existenz 7). I installed Soundabout app and it fixed the issue somehow, and i never experienced the problem until yesterday (on 4.4) . I again installed soundabout, it worked for some time, but now earphone doesn't work again. It's really frustrating! According to service test it's not a hardware problem. But could sony engineers make the same mistake twice (both in 4.3 and 4.4)?
David.V said:
Hi there
I'm having exactly the same issue on 4.4 (existenz ultimate)
I can confirm once I had this issue on stock 4.3 rom as well (existenz 7). I installed Soundabout app and it fixed the issue somehow, and i never experienced the problem until yesterday (on 4.4) . I again installed soundabout, it worked for some time, but now earphone doesn't work again. It's really frustrating! According to service test it's not a hardware problem. But could sony engineers make the same mistake twice (both in 4.3 and 4.4)?
Click to expand...
Click to collapse
thats exactly same situatiom i have
So, are you positive its not a hardware issue? I sure hope that Sony is going to fix this and all the other Kitkat problems they've had with this new update that got certified (10.A.5.1.283)..Its probably going to be 4.4.4 and the last update for Xperia Z, as Android L is probably reserved for newer phones and Sony won't get anything from supporting the update for the original Z.
I really like Kitkat but if this earphone bug is related to Sony's Kitkat update and the next version doesn't fix it, I'm sure I'll get back to 4.3, as its really frustrating when you need to make an important call, or if you're in a hurry about something and your phone doesn't work...
If anyone knows the cause of this or is certain that it is related to specific firmwares please help us out and write it here.
Greetings from Bosnia
Lets hope it will be fixed on 4.4.4
maybe i will try another stock firmawares, based on 4.4.2, just for know if its region firmware related
numero13 said:
Lets hope it will be fixed on 4.4.4
maybe i will try another stock firmawares, based on 4.4.2, just for know if its region firmware related
Click to expand...
Click to collapse
i just flased the 4.4.4 and its the same problem again
---------- Post added 10th September 2014 at 12:07 AM ---------- Previous post was 9th September 2014 at 11:56 PM ----------
amar92 said:
So, are you positive its not a hardware issue? I sure hope that Sony is going to fix this and all the other Kitkat problems they've had with this new update that got certified (10.A.5.1.283)..Its probably going to be 4.4.4 and the last update for Xperia Z, as Android L is probably reserved for newer phones and Sony won't get anything from supporting the update for the original Z.
I really like Kitkat but if this earphone bug is related to Sony's Kitkat update and the next version doesn't fix it, I'm sure I'll get back to 4.3, as its really frustrating when you need to make an important call, or if you're in a hurry about something and your phone doesn't work...
If anyone knows the cause of this or is certain that it is related to specific firmwares please help us out and write it here.
Greetings from Bosnia
Click to expand...
Click to collapse
i try existenz v7 and have the same problem, but its based on 4.3, and stock 4.3 work fine to me, so i think maybe is something related to 4.4 sony framework
hello, i have tested lots off roms and the problem is ther on almost 4.4 rom. the Free Xperia rom, not have this problem.
i was thinking is there is some app that can manually disble the 3.5mm jack is on solution, but i not find that for 4.4
lets keep trying
I'm on stock .230 and never had this problem...
Sent from my C6603