Related
Anyone here know if i can downgrade from jb to ics without wiping anything?
Sent from my GT-I9300 using xda premium
I wouldn't imagine so, mores to the point why would you want to do something as crazy as that, JB is much better all round that ICS.
jonny68 said:
I wouldn't imagine so, mores to the point why would you want to do something as crazy as that, JB is much better all round that ICS.
Click to expand...
Click to collapse
sorry delete post
Because jb have lag and problems not to much but some of my application are fc also
Sent from my GT-I9300 using xda premium
cris_ronel said:
Because jb have lag and problems
Click to expand...
Click to collapse
When are you experiencing lag? I found using a different launcher resolved all my lag problems, as loading the app drawer and flicking between home screens in Touchwizz was a bit crap for me. There are so many things you can do rather than take a step back to ICS......seems a bit extreme to me!
you can try it, but I reckon system data might cause conflicts....better to back up with titanium, do a clean install/reinstall apps and data/restore call logs and sms etc via .xml method and any other data(system) just restore 1 at a time to see if it causes any conflicts
I think youd have more force closes if you downgraded without wipe. Best way to flash any rom and avoid issues is with a full wipe. Even for rom updates
Sent from my GT-I9300 using xda premium
cris_ronel said:
Because jb have lag and problems not to much but some of my application are fc also
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Some apps FC? Did you wipe before you flash JB? So far there isn't any app FC due to Jelly Bean for me...
cris_ronel said:
Anyone here know if i can downgrade from jb to ics without wiping anything?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Always wipe, upgrade, downgrade, diarrhea, always wipe! :victory:
I recently bought an international GT-I9300 Galaxy s3. I am facing few problems. I get a 3-4 seconds lag when I open dialer contacts and messaging app but once i have opened them it seems like they stay in memory for some time and open instantly but after some time i get this horrible lag again. Is my phone normal? I searched the forums and some people are facing this while others not. Secondly whenever I charge my s3 through the AC adaptor, galaxy s3 shows as charging (USB). Then i unplug and plug again after few tries it shows charging (AC). Is my phone faulty or is this a software bugs? Any fixes to these problems? I am on everything stock and unrooted JB 4.1.1 I9300XXDLID. Thanks
Hello, first of all, did you buy it brand new? First, I trying turning of s voice as it is know to cause lags. Then I can developer options change the windows a d transition animation scale to 0.5. See if it gets better, it could just be that there are some bugs! I
Sent from my GT-I9300 using xda app-developers app
Yes brand new with official damsung warranty. I have changes the animations and transition to 0.5 and disabled s voice.. Still the lag is present. Any solution? Should I send it to Samsung?
Are there any other lags beside the dialer and the messaging app?
Sent from my GT-I9300 using xda app-developers app
saaj2000 said:
Are there any other lags beside the dialer and the messaging app?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
None. The lag is present only on dialer contacts and sometimes messaging.
Ok, I think that it's just a big with the jelly bean... It should be fixed soon!
Sent from my GT-I9300 using xda app-developers app
saaj2000 said:
Ok, I think that it's just a big with the jelly bean... It should be fixed soon!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I hope so. Thanks for your help
Charging problem fixed. Both the Samsung usb cables were crap.. Tried a new one and works well. Samsung should fix the dialer/contacts lag now or i will never buy a Samsung phone Again! Anyone knows how to submit this bug to Samsung?
just flash aokp or some stock AOSP jb rom
paintball23456 said:
just flash aokp or some stock AOSP jb rom
Click to expand...
Click to collapse
Sorry for being a noob but this is my first Android phone and I have heard rooting/flashing voids warranty so I don't wanna risk it. I prefer doing it the simple way. Samsung should fix this bug soon.
there are ways to reset the flash counter..search the forum for triangle away. I flashed my S3 with many different custom ROMs. My phone earphone jack had some problem. I used triangle away, flash to stock ROM and bring it to Samsung for warranty. No problem with that..or maybe they didn't check thoroughly..:highfive:
farrukh494 said:
Sorry for being a noob but this is my first Android phone and I have heard rooting/flashing voids warranty so I don't wanna risk it. I prefer doing it the simple way. Samsung should fix this bug soon.
Click to expand...
Click to collapse
oh ok, a different version of sammy Jb will probaly fix the problem.
paintball23456 said:
oh ok, a different version of sammy Jb will probaly fix the problem.
Click to expand...
Click to collapse
All problems fixed. There was a problem with ota update. I resolved it by reinstalling the firmware through KIES firmware upgrade and initialization option. No lags in dialer contacts so far and blue Samsung logo on boot has come back. Thanks everyone. This thread can be closed.
Update: dialer and contacts lag still present
Hi all
Anyone experienced the occasional dialer screen messed up after a call?
See attached screencapture.
rekenaar00 said:
Hi all
Anyone experienced the occasional dialer screen messed up after a call?
See attached screencapture.
Click to expand...
Click to collapse
Wow...never seen THAT before.
Sent from my GT-I9300 using xda app-developers app
Dafuq happened there. Sorry man, never seen that
Woah bro. I have no idea what's up with your dialer. Are you on stock firmware and kernel? No root? No mods?
It only happened 2 or three times and I cannot reproduce at will.
First time was on stock rom without root.
Last time (screencapture 18/12/2012), was on sotmax_Ultimate_stock_V10_XXELKC_Aroma, but it was not a clean flash. I kept apps and data when I converted to sotmax rom. So it must be something carried over.
But happening very seldom, so not a big issue where I would want to risk a clean factory wipe.
Just hoped someone seen it as well.
Happened to me aswell today but exiting and reentering the Dialer sorted it out.
I'm on a clean install of crDroid 8.2!
so I am not alone :laugh:
same, here, exit and reopen fixed it immediately.
This has happened to me on various Sammy based ROMs all JB but different versions.
I really wouldn't worry about it to much, killing the app and opening works again.
Must be something with the dialer. The only thing I will say is that I did have all the motion stuff turned on.
Sent from my GT-I9300 using xda premium
I've been using the nightly CM10.1 builds for a while now and it has always worked but lately when I tried to call someone I didn't hear the ringing before the call goes through and I can't hear them talking either but the speaker plays music and videos fine and I want to know how to fix this so I can call people normally again.
I have tried megawiping and reflashing, also going back to stock and starting again and other various methods like trying without gapps but I can't seem to get it to work and I really need it to cause its the only phone I can currently use but I found it was weird because this only occurs to my phone when running CM10.1 but calling works normally on stock and CM9.
LittleDoggy said:
I've been using the nightly CM10.1 builds for a while now and it has always worked but lately when I tried to call someone I didn't hear the ringing before the call goes through and I can't hear them talking either but the speaker plays music and videos fine and I want to know how to fix this so I can call people normally again.
I have tried megawiping and reflashing, also going back to stock and starting again and other various methods like trying without gapps but I can't seem to get it to work and I really need it to cause its the only phone I can currently use but I found it was weird because this only occurs to my phone when running CM10.1 but calling works normally on stock and CM9.
Click to expand...
Click to collapse
Could be your modem, try flashing a new one in CMW!
squ89r97 said:
Could be your modem, try flashing a new one in CMW!
Click to expand...
Click to collapse
I tried that and unfortunately that doesn't improve anything.
LittleDoggy said:
I tried that and unfortunately that doesn't improve anything.
Click to expand...
Click to collapse
Hmmmm, restore to your earlier backup, or try posting the question in the CM10.1 Q&A thread.
squ89r97 said:
Hmmmm, restore to your earlier backup, or try posting the question in the CM10.1 Q&A thread.
Click to expand...
Click to collapse
I tried that as well and if you mean the thread on xda then I have posted my problem in the discussion thread and I was planning on asking on the CM forums about this problem.
I have same problem, I tried everything, flash ROM , radio, modem, full wipe, everything I could possibly thing of, but the Fu.cking problem is, the front speaker works fine with Viber, but absolutely no sound during the phone call!
And at end I sent it to warranty... hope it would work out
Sent from my GT-I9300 using xda premium
qtwrk said:
I have same problem, I tried everything, flash ROM , radio, modem, full wipe, everything I could possibly thing of, but the Fu.cking problem is, the front speaker works fine with Viber, but absolutely no sound during the phone call!
And at end I sent it to warranty... hope it would work out
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The weird thing was I could get the phone/dialer working but it wouldn't work if I reboot my phone or change any of the settings like turning off animations.
qtwrk said:
I have same problem, I tried everything, flash ROM , radio, modem, full wipe, everything I could possibly thing of, but the Fu.cking problem is, the front speaker works fine with Viber, but absolutely no sound during the phone call!
And at end I sent it to warranty... hope it would work out
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I think it's more of a CM / 4.2.x Version issue rather than a service centre issue - Read a few issues and some say this solves the problem, some say it doesn't give it a try
Ok, i might found a solution:
Turning on the lockscreen sound in the sound setting and then reboot. I´ll try it and then tell my experience with this solution.
squ89r97 said:
I think it's more of a CM / 4.2.x Version issue rather than a service centre issue - Read a few issues and some say this solves the problem, some say it doesn't give it a try
Ok, i might found a solution:
Turning on the lockscreen sound in the sound setting and then reboot. I´ll try it and then tell my experience with this solution.
Click to expand...
Click to collapse
This seems to fix my issue for the time being but i'm still unsure if it is a permanent solution but thanks for helping
squ89r97 said:
I think it's more of a CM / 4.2.x Version issue rather than a service centre issue - Read a few issues and some say this solves the problem, some say it doesn't give it a try
Ok, i might found a solution:
Turning on the lockscreen sound in the sound setting and then reboot. I´ll try it and then tell my experience with this solution.
Click to expand...
Click to collapse
i flashed stock 4.0.4 , stock 4.1.2 , CM10, CM 10.1, every ROM i can think of ...not good at all
qtwrk said:
i flashed stock 4.0.4 , stock 4.1.2 , CM10, CM 10.1, every ROM i can think of ...not good at all
Click to expand...
Click to collapse
Reset counter, flash stock, service center it is!
Sent from my GT-I9300 using xda app-developers app
squ89r97 said:
Reset counter, flash stock, service center it is!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
really strange it is.
as Viber works , so i consider it not as a hardware problem but call just doesn't have any sound !!! nor otherside can hear me ...
maybe replace motherboard will fix it ...
cannot hear when calling
Anyone have the solution yet?
it just happened to me to with AOKP (the last version - JB-MR1 Milestone 1)
Everything works fine, in a middle of a call the phone restarted and now there is no sound
Edit:
After a few full wipes and refreshing all is working good now.
Possible solution
Check my post here
Thanks but I already solved it...
Sent from my GT-I9300 using Tapatalk 2
No sound while calling
itaysp said:
Thanks but I already solved it...
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Hey, can you please tell how were you able to solve it? I'm facing the same problem since yesterday.
Hello XDA. This ROM (rootbox 3.9.1) is supposed to be stable, but when I turn on flash or automatic flash and I touch to focus then shoot, the camera app lags and force closes (and doesn't take the picture). This is annoying in so many ways, and makes it virtually impossible for me to take pictures in low light. Please help me address this issue for it is killing me and I don't feel like downloading a whole new ROM, flashing it and reorganizing all my settings all over again just to fix this issue. I also had this issue with CM10.1 (but that was normal, cause it is a nightly).
Anybody else have this issue? And possibly a fix?
Thanks in advance.
Also: inb4 "search the official root box thread". I did, and nobody seems to have this issue.
Sent from my GT-I9300 using xda app-developers app
Marcellff said:
Hello XDA. This ROM (rootbox 3.9.1) is supposed to be stable, but when I turn on flash or automatic flash and I touch to focus then shoot, the camera app lags and force closes (and doesn't take the picture). This is annoying in so many ways, and makes it virtually impossible for me to take pictures in low light. Please help me address this issue for it is killing me and I don't feel like downloading a whole new ROM, flashing it and reorganizing all my settings all over again just to fix this issue. I also had this issue with CM10.1 (but that was normal, cause it is a nightly).
Anybody else have this issue? And possibly a fix?
Thanks in advance.
Also: inb4 "search the official root box thread". I did, and nobody seems to have this issue.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
As far as I know this issue was fixed a couple of days ago in the CM Nightlies so maybe the Vanilla Rootbox base hasn't been updated yet or you aren't using their latest update.
Scarface1991 said:
As far as I know this issue was fixed a couple of days ago in the CM Nightlies so maybe the Vanilla Rootbox base hasn't been updated yet or you aren't using their latest update.
Click to expand...
Click to collapse
3.9.1 is the latest as far as I know. I installed it a couple days ago.
Sent from my GT-I9300 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2179233&page=66
Top post works for me hope it helps
neilster2020 said:
http://forum.xda-developers.com/showthread.php?t=2179233&page=66
Top post works for me hope it helps
Click to expand...
Click to collapse
Didn't work. what version of this aosp camera are you using? And with what ROM? I got the latest version. And it still crashes.
Sent from my GT-I9300 using xda app-developers app
Actually I've found a way to bypass this problem. If I turn on the volume key to take pictures function, autofocus with flash on and take the picture with the volume key, it doesn't crash. I guess I'll just have to live with it like this for now, oh well.
OK now how do I close this thread? Or there's no such thing? Can any mod or janitor or whatever help me out here? I'm new here
Sent from my GT-I9300 using xda app-developers app