Related
Hello everybody
I have a Sony Xperia T, and when I got tired of the stock ROM (JB 4.1.2), updated with PC Companion to 4.3, and everything started to go wrong. While daily use, the screen sometimes turned blue and afterwards the phone rebooted. This happened approximately once a week.
Less frequently, the phone shut down and I couldn't turn it on tipically by holding power button for few seconds. Otherwise, I had to press volume up + power keys until first vibration (I read this simulates battery removal) in order to start my phone.
I thought it might be due to the new ROM, so I flashed CM 10.2, but I had the same problem. Recently, I tried with PACMAN ROM (my current firmware), but it could not solve the problem neither.
Few weeks ago I read that this bug might be a kernel issue, but I'm not quite sure. Do you have any idea about what happens? Flashing a new kernel would end the problem? In that case, which one do you recommend? My phone is rooted, bootloader unlocked and CWM v 6.04.
Thanks you all for your time :fingers-crossed:
P.D.: I attach a screenshot with kernel, build, android version...
i dont know why someone would try out pac rom, a rom without a good forum thread support. a rom which seems dead for our phone?
about cyanogenmod, i not use it...so i just can guess: maybe they still not use the new sony 4.3 kernel source...that could be a reason for bluescreens (same pac rom)?
so you have this options:
omnirom official nightlies by tilal6991
omnirom homebuilds by scanno
latest paranoid android by tilal6991
plain AOSP by Rimmer1966
these use new kernel source, no bluescreens, good user experience, daily driver material.
try out and become happy...
you can find them in xperia T forum, just look around
edit:
why you have android version 4.2.2? is that a bug? build date 1.aug 2013?
we have already awesome kitkat (android 4.4.2) roms (list above)^^
immerblind said:
i dont know why someone would try out pac rom, a rom without a good forum thread support. a rom which seems dead for our phone?
about cyanogenmod, i not use it...so i just can guess: maybe they still not use the new sony 4.3 kernel source...that could be a reason for bluescreens (same pac rom)?
so you have this options:
omnirom official nightlies by tilal6991
omnirom homebuilds by scanno
latest paranoid android by tilal6991
plain AOSP by Rimmer1966
these use new kernel source, no bluescreens, good user experience, daily driver material.
try out and become happy...
you can find them in xperia T forum, just look around
edit:
why you have android version 4.2.2? is that a bug? build date 1.aug 2013?
we have already awesome kitkat (android 4.4.2) roms (list above)^^
Click to expand...
Click to collapse
First of all, thank you for your quick reply, I'll take it account
The reason why I tried with CM10.2 and Pacman ROM is that they are not nightlies. I don't totally rely on nightiles because of the many bugs ther're reported. Anyway, I'll try with some of the ROMs above.
Finally, I would like to know if I coud stay with my current ROM and solve my problem only by flashing a new kernel.
Thank you again ^^
you dont rely on nightlies? wrong decision regarding omnirom, all on my above list is daily driver material (even the nightlies)
easy Kernelchange and keep this outdated pac rom with 4.2.2? NO!
its that simple. there is no reason to use such an outdated custom rom, no reason!
Ok, I refused to change kernel, and flashed the third one of the list: "latest paranoid android by tilal6991" (I liked a review about it). However, the problem persists :crying: And that's a pity, because I love how the new ROM looks like
Take a look to the new screenshot of "About phone". The kernel version seems to be different to the one of the last cap. Any idea?
Thanks in advance!
hi evry bodey , i have an s3 mini smartphone and samsun was stopped the official update for this s3 mini
i have installedmany roms , i tried AOKP/CM10/CM11/PAC... all roms was instable...a have many problems with teh sim contacts i cant's show my sim contacts in all CM realises i don't know why and why this problem was not resolved
why maclaw and nova fusion can not realese one and only one stable and very stable version of CM bases roms and why i tried 20 realises from maclaw official site and all this roms were instable????...the can realise 5 roms per day and they can't realese one and only one stable??
i search a stability and perfermences ... where i can find a stable and fast versions or realiser for my s3 mini
where i can find an 4.4 KK rom stable for our s3 mini???
i'm tried virginity rom and DMOD roms are stable really and i like him but i want an 4.3 or 4.4 roms stable for dayly use??
any one can help me? i serach for stability and features and sorry for my bad english
Novafusion's KK variant rom and Gulden-guy's rom are the only KK rom available for our device. Most of them are under develompment by their own developers, so it's understand-able some problem may appear and the fitures isn't completed. Stay on stock based rom may the best choice for you and your needs but I and many other user here feels that all KK roms here is "fully-working" enough.
ztandroid said:
Novafusion's KK variant rom and Gulden-guy's rom are the only KK rom available for our device. Most of them are under develompment by their own developers, so it's understand-able some problem may appear and the fitures isn't completed. Stay on stock based rom may the best choice for you and your needs but I and many other user here feels that all KK roms here is "fully-working" enough.
Click to expand...
Click to collapse
All maclaw's ralises are not fully working .... All posts in forum are copy post from maclaw official site
All tis roms have problems with the sensors...our galaxy have 7sensors worked fully with stoc rom but with maclaw only 4 sensors works try with sensor kinetic app from google play you will see they are 4 sensors works good but the gyroscope for exemple they crash after secods and the acceleration linear sensor too
And the big problme with contacts sim i cant see or write any sim contact
And how can i know if it is stable or not stable?????
el portable said:
All maclaw's ralises are not fully working .... All posts in forum are copy post from maclaw official site
All tis roms have problems with the sensors...our galaxy have 7sensors worked fully with stoc rom but with maclaw only 4 sensors works try with sensor kinetic app from google play you will see they are 4 sensors works good but the gyroscope for exemple they crash after secods and the acceleration linear sensor too
And the big problme with contacts sim i cant see or write any sim contact
And how can i know if it is stable or not stable?????
Click to expand...
Click to collapse
You can check in rom's official website or blog, there's should be an announcement for rom's development stage or you can review their source code.
Sent from my GT-I8190 using Tapatalk
ztandroid said:
You can check in rom's official website or blog, there's should be an announcement for rom's development stage or you can review their source code.
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Maclaw don't post if they stable or not i don't know and there aren't a solution for the sim contacts problem?
el portable said:
Maclaw don't post if they stable or not i don't know and there aren't a solution for the sim contacts problem?
Click to expand...
Click to collapse
I meant official website or blog for each roms, not novafusion. Anyway, I just installed sensor kinetics app and all 7 sensors works fine (latest novafusion's CM11).
As I said, all ported KK roms here are under heavy development, needs time to get it complete, so you may found some inconviniance.
Sent from my GT-I8190 using Tapatalk
I also find the KK roms to be too unstable.
Maclaw has done some great work, but recently the nightlies have become increasingly buggy. I recommend using the 0225 build of CM10.2. It's only 4.3, but it's still much better than Touchwiz on 4.1 and it's very stable.
You can find it here: get.novafusion.pl/?id=732
Maclaw has also recently made the archive of all previous builds available for download. You can look around the forums to see which builds people recommend using.
The archive can be accessed here: get.novafusion.pl/archive
I know it sucks having to go through trial and error to find a suitable rom. But remember, these people do what they do for free. I've used official CM on a regular Galaxy S3 and I can promise you (even though it might not seem like it) that Maclaw's CM builds are top notch compared to many other custom roms out there.
Mod Edit
"Best" or "Recommend" ROM/kernel threads are not allowed on XDA.
Please test these things for yourself.
This is the only way you will get an unbiased opinion,and then, you can decide for yourself if it meets YOUR needs.
Don't forget to make a nandroid before you start.
Thread Closed
malybru
Forum Moderator
I just want to start this thread to consolidate the info...
First: zr/dogo (c5502/c5503) has a 2nd mic...
http://talk.sonymobile.com/t5/Xperi...ry-in-Config/m-p/699221/highlight/true#M41451
However, on all custom roms, it's not present/detected at all, it can be tested via recording video, then covering the main microphone. Normally, with stock rom, there'll still be sound, but on custom rom because 2nd mic is not working, there will be no sound.
The issue has been reported separately here:
https://code.google.com/p/freexperia/issues/detail?id=2286&q=ZR OR C5502 OR C5503
And here:
https://jira.cyanogenmod.org/browse/CYAN-4818
And mentioned numerous times in xda's zr forums.
The solution, currently, is to return to stock.
Note that this is not the same problem as troubled recording sound in stock roms, like this...
http://forum.xda-developers.com/showthread.php?t=2690192
I've reported it even on MoKee ROM bug tracker.
maybe we can try nagging the devs at http://webchat.freenode.net/?channels=#freexperia
I am also keeping away from custom ROMs only because of this 2nd mic issue.
Sent from my C5503 using XDA Free mobile app
I am also keeping away from custom ROMs only because of this 2nd mic issue.
Click to expand...
Click to collapse
+1
any idea on the next action??
nostupidthing said:
any idea on the next action??
Click to expand...
Click to collapse
- Sell the zr, and buy nexus. I think it is not so good phone, but has support.
- Learn programming and rewrite the zr's kernel.
Sorry, but no useful idea :banghead:
btw, please register an account and vote in the bugtrackers? see if it'd make a difference.
thx.
just reflashed stock again, video recording works.............................................................. FXP devs please help.
And I was thinking that "to hell with stock I am bored and CM 'L' here I come.."
Sent from my C5502 using XDA Free mobile app
Look for your friends, but do not trust to hope. It has forsaken these lands.
- Eomer, Lord of the Rings.
PUSH PUSH
nostupidthing said:
PUSH PUSH
Click to expand...
Click to collapse
wait that's a freexperia and cm bug right? then not all custom roms have that only freexperia and official cm, so you should tell them about this bug.
also did you used my omni too? it's based on AOSP but unfortunately freexperia kernel, so try that and see if second mic working?
and in that case the miui you mentioned ... it has working second mic try the latest one which is based on stock sony 4.2.2 for now.
EDIT: I see, there is bug reported for that but only 10.1 and 10.2 not bug reported for 11.
so if you want to get this solved or at least considered please download latest cm11 from Official cyanogenMod and fxp, get logcat while record a video and sound (use with adb "adb logcat > log.txt") , create new report with logcat in both fxp and cm bug reported and MENTION that this has logcat so nobody says it's just the dupplicate! also note that cyanogen won't accept bug report for nightlies you need to bug report for 10.2 stable one if for cm11 rejected ! with all this maybe they consider resolving dogo 2nd mic.
have fun.
https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-25441
they just say it's untaggabble bcs all fxp maintained devices don't get m-builds from cyanogenmod!!
nostupidthing said:
https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-25441
they just say it's untaggabble bcs all fxp maintained devices don't get m-builds from cyanogenmod!!
Click to expand...
Click to collapse
then do it on fxp, but I don't think they are building it using fxp as their builds are hell of a lot different! I know that because I merge things from official cm and fxp and Xperia Z aosp to make omni (It's pretty much pizza baking alright lol :laugh! so much different in libs and kernel in both builds! but still you can try it on fxp.
you mean this?
https://code.google.com/p/freexperia/issues/detail?id=2286
i would say the fxp-cm collaboration is currently damaging the development. the fxp team are so busy that they don't care about their bugtracker and small bugs (they'll fix it if the latest build is not bootable), otoh cm team is not working on xperia devices because it's the responsibility of the fxp team.
thx for the info, btw, i like using cm, it's a good balance of increased functionality (on top of aosp) and stable while not having too much customisation, imo. many custom roms makers are teenagers who incorporate too much cutting edge stuffs for my taste. but i don't want to go back to stock either...
cm bugtracker admin closed the original bug, it's been re-created.
https://jira.cyanogenmod.org/browse/CYAN-4818
new bug already quashed because "no official cm11 builds for dogo".
nostupidthing said:
new bug already quashed because "no official cm11 builds for dogo".
Click to expand...
Click to collapse
maybe you need to bug post in FXP not official cyanogen.
sijav said:
maybe you need to bug post in FXP not official cyanogen.
Click to expand...
Click to collapse
......................
nostupidthing said:
I just want to start this thread to consolidate the info...
First: zr/dogo (c5502/c5503) has a 2nd mic...
http://talk.sonymobile.com/t5/Xperi...ry-in-Config/m-p/699221/highlight/true#M41451
However, on all custom roms, it's not present/detected at all, it can be tested via recording video, then covering the main microphone. Normally, with stock rom, there'll still be sound, but on custom rom because 2nd mic is not working, there will be no sound.
The issue has been reported separately here:
https://code.google.com/p/freexperia/issues/detail?id=2286&q=ZR OR C5502 OR C5503
And here:
https://jira.cyanogenmod.org/browse/CYAN-4818
And mentioned numerous times in xda's zr forums.
The solution, currently, is to return to stock.
Note that this is not the same problem as troubled recording sound in stock roms, like this...
http://forum.xda-developers.com/showthread.php?t=2690192
Click to expand...
Click to collapse
Im running an mb886 using the CM11 and Carbon nightlys. ive been using the CM11 JBBL nightlys and was wondering if there is any reason to jump up to a KKBL. and if so is there a guide. alas the search feature did nothing for me.
disregard i found it.
disappointing that i cant move to the KKBL.
currently I have carbonrom on my phone. do the CM11 nightlys for JBBL mirror the other ones or are they behind?
oscar the grouch said:
currently I have carbonrom on my phone. do the CM11 nightlys for JBBL mirror the other ones or are they behind?
Click to expand...
Click to collapse
CM11 nightlies are based on the same build for both JBBL and KKBL bootloaders. The build server runs every night and uses the same code base for both of them.
p.s. If you're ever in doubt, you can always check the changelogs for both the JBBL and KKBL builds.
Thank you.
I tired the aospb build rom earlier. For some reason it kept giving me unfortunately blah blah quit. Apparently my itialian input method. (Not Italian) kept shutting off. And everything I tried from my titanium backup and the playstore crashed every time I opened it. Can't ask inthe rom thread so I sent back to carbon. Any thoughts
oscar the grouch said:
Thank you.
I tired the aospb build rom earlier. For some reason it kept giving me unfortunately blah blah quit. Apparently my itialian input method. (Not Italian) kept shutting off. And everything I tried from my titanium backup and the playstore crashed every time I opened it. Can't ask inthe rom thread so I sent back to carbon. Any thoughts
Click to expand...
Click to collapse
Sorry, but I have no idea what you're trying to say. I've used both Carbon and CM11 on my phone without issue (currently on CM11 nightly).
If I had to take a wild guess about your issue with Playstore crashing, you probably need a newer/more compatible version of the Google Apps installed. Not sure what you installed, but the PA Gapps are always up to date. Start with the Mini or Micro packages and work from there.
Or ask a new question in the Q&A forum.
I was using the pa micro. Still am. Something about the aospb rom didn't like me. I flashed it with out gapps and it still.crashed every non system app. It was better when not running the app data on a partition but still not good. Currentlyrunning the carbon nightly with zero issues
oscar the grouch said:
I was using the pa micro. Still am. Something about the aospb rom didn't like me. I flashed it with out gapps and it still.crashed every non system app. It was better when not running the app data on a partition but still not good. Currentlyrunning the carbon nightly with zero issues
Click to expand...
Click to collapse
With some ROMs, I was having an issue with the dialler whereby I would need to press the # key three times in a row to get the keypad to appear. Have you ever experienced this issue?
audit13 said:
With some ROMs, I was having an issue with the dialler whereby I would need to press the # key three times in a row to get the keypad to appear. Have you ever experienced this issue?
Click to expand...
Click to collapse
have not. that is weird. how do you get a #key with out a dial pad tho?
This is a compile done for a friend, as he found lp/mm roms to be unbearably laggy,especially when using social media/chatting apps. Just thought it could help some folks hoping to run an updated kitkat in their old(but great) galaxy s3. After some usage, his words were: this phone is part of my hand again .
This is a straight compile from cm11 sources for i9300, with the pac-rom source code(the best kitkat custom rom imo). Battery life, performance and stability are truly superb. Sources merged on 12-Oct-16, therefore having the latest stagefright and other security patches built-in. Wifi-fix for i9300 is also integrated. The rom is working fine with the latest boeffla-kernel(2.14) released for cm11, and thats the tested and recommended configuration. Some useless apps removed(like voicedialer, whisperpush,moviestudio,pacconsole and some more i can not remember) and i also removed pac console from the rom configuration settings framework as well. Have fun using it.
Link: https://mega.nz/#!Vl4nnYrK!N1PYfctzAnkOVDucMVsSCT5nnxUqY_oAZe2tsGDXkAo
All credits go to cyanogenmod and pac-rom team for both their amazing roms and sources for i9300 and many other phones we use and love!
Thanks you,!!
Screenshots?
Enviado desde mi SM-G935F mediante Tapatalk
Not having the phone means no screeshots . You can try it and put some up for everyone to see. You wont be disappointed.
What about gapps?? We have to dwnload it?
This is a clean rom, no gapps,xposed, or other mods included. use opengapps.
Really appreciate your efforts here... Great work on this rom... everything working fine... If possible can you put some time looking into Archidroid 4.4.4... IMO it was the best rom our s3 could ever have.... It has some wakeblock issues that might get resolved if we update the sources. Again thanks for your effort. S3 community owes you!
Hi uninstall theme auto reboot! Please to fix
sak0071 said:
Hi uninstall theme auto reboot! Please to fix
Click to expand...
Click to collapse
This problem persist with the latest snapshot of cm 11 also... nly install themes that you like... doesnt affect the functionality of the rom having themes installed.
Thanks for this great ROM. The only issue I have is I cant get 3G to work. Any suggestions? Would be much appreciated...
Its probably an APN problem, try inputting your carrier settings manually. 3g works fine on my friends' phone.
The rom is incredible but I need to restart my system with Wifi turned on so it can connect. If it disconnects (for any reason, disabling wifi, getting out of range etc), it only flashes "Connecting..." when connecting to the router again, but it doesn't connect
Try the fix in this thread: http://forum.xda-developers.com/galaxy-s3/help/wifi-fix-cm11-i9300-t2910872 . I already included the needed file in the rom, and it works fine here, but it couldnt hurt to try. Could it also be your router causing this?
pchatzop said:
Try the fix in this thread: http://forum.xda-developers.com/galaxy-s3/help/wifi-fix-cm11-i9300-t2910872 . I already included the needed file in the rom, and it works fine here, but it couldnt hurt to try. Could it also be your router causing this?
Click to expand...
Click to collapse
Will try! And it isn't the router, it worked with cm12.1 (no issues whatsoever) and cm13 (the issue on cm13 was random disconnects but it was rom related too).
Hey!
Switched to this rom recently and being very impressed, it having all the features one could ever want yet stable and battery friendly. Definitely better than MM roms on S3.
However do we need an kitkat bootloader or do we even have one available? Still on the official 4.3 bootloader and just wondering if could get more stability if upgrading it to kitkat.
Kitkat bootloaders dont exist for the i9300, since it never officially got kitkat. Last semi-stock kitkat rom for the i9300 were ported roms from n7100 and the korean variant of gs3, and they did not include a bootloader, because it would hard-brick the phone. Having installed 4.3 before this was the best you could do. Having this rom installed in 2 phones(my friend's and my sister's) i definitely recommend installing boeffla's last cm11 kernel, no stability,battery, or features problems with it. Actually, apart from the rebooting on uninstalling themes bug, no other bug has been reported to me from them, no even ones in the thread.
sak0071 said:
Hi uninstall theme auto reboot! Please to fix
Click to expand...
Click to collapse
Hold power, power menu come up, hold reboot, enter safemode, uninstall theme from app menu...that should work
Sent from my GT-I9300 using XDA-Developers mobile app
Hi. This rom next update? thank
jabyftw said:
The rom is incredible but I need to restart my system with Wifi turned on so it can connect. If it disconnects (for any reason, disabling wifi, getting out of range etc), it only flashes "Connecting..." when connecting to the router again, but it doesn't connect
Click to expand...
Click to collapse
I have the same problem. Is there a solution ?
wifi doesn't work ! any solution?
medsalah said:
wifi doesn't work ! any solution?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2910872
Sent from my GT-I9300 using XDA-Developers Legacy app