Related
apparently every time i install a jellybean stock rom for the uae my phone if not used (screen turned off for a while) when i open to use it again it wont open, and people call the phone normally but it doesnt give me a sound, the only way to use it again is to restart the phone, is there a fix for this? because ive had it with the march and april JB stock roms.
abdoabook said:
apparently every time i install a jellybean stock rom for the uae my phone if not used (screen turned off for a while) when i open to use it again it wont open, and people call the phone normally but it doesnt give me a sound, the only way to use it again is to restart the phone, is there a fix for this? Because ive had it with the march and april jb stock roms.
Click to expand...
Click to collapse
u need to format the phone and full wipe and reinstall...
Hello,
So far Holic's ROM seems to be the only one without in-call volume problems on my Vivid (Bell Canada) but there are two problems, one more annoying than the other
first, most annoying problem: after I install, the phone will upgrade to the latest apps like Hangouts. Everything works great, I can start hangouts and chat.
But after some time (5 to 10 minutes) of the phone just sitting there, or especially after a reboot, I will get the "google play services is not supported by your device" error. I have to remove update to google play store and resintall it, and then problem goes away temporarily and hangouts is usable again, and after the next reboot same problems reappear.
Does anyone have any fix for this?
second problem, less annoying:
On the phone dialer, there is a button at the bottom right which looks like a button for calling voicemail (has some funny symbols on it)
if I press this button I get error message "Android.process.acore has stopped unexpectedly". Does anyone else have this?
My phone is S-ON
I reinstalled the rom several times. I do the full system wipe before from recovery, flash the boot image, install rom with WCX recovery, re-flash the boot image from the SD card
same problem every time.
tudorvictor said:
Hello,
So far Holic's ROM seems to be the only one without in-call volume problems on my Vivid (Bell Canada) but there are two problems, one more annoying than the other
first, most annoying problem: after I install, the phone will upgrade to the latest apps like Hangouts. Everything works great, I can start hangouts and chat.
But after some time (5 to 10 minutes) of the phone just sitting there, or especially after a reboot, I will get the "google play services is not supported by your device" error. I have to remove update to google play store and resintall it, and then problem goes away temporarily and hangouts is usable again, and after the next reboot same problems reappear.
Does anyone have any fix for this?
second problem, less annoying:
On the phone dialer, there is a button at the bottom right which looks like a button for calling voicemail (has some funny symbols on it)
if I press this button I get error message "Android.process.acore has stopped unexpectedly". Does anyone else have this?
My phone is S-ON
I reinstalled the rom several times. I do the full system wipe before from recovery, flash the boot image, install rom with WCX recovery, re-flash the boot image from the SD card
same problem every time.
Click to expand...
Click to collapse
What Gapps are you installing? Have you tried different ones?
CM11 in call volume is pretty much gone since about the middle of January (if you read the thread, you'll see good feedback about it from about the 15th on). Only issue is sending/recieving MMS. Might want to give it another shot since this seem to be the only one getting worked on by the devs.
Yuskow said:
What Gapps are you installing? Have you tried different ones?
CM11 in call volume is pretty much gone since about the middle of January (if you read the thread, you'll see good feedback about it from about the 15th on). Only issue is sending/recieving MMS. Might want to give it another shot since this seem to be the only one getting worked on by the devs.
Click to expand...
Click to collapse
I'm not flashing any Gapps on this, the ROM already comes with them.
This is a ROM based on 4.0.3 ICS, not kitkat
I actually tried two versions of CM11, one was the latest unofficial nightly build from february 19, and the other was the albinoman release from january 15. both have the low volume problem.
I also tried the Borked ROM, based on 4.0.3, and it has the same low call volume problem, but no other issues like hangouts not working.
What GApps should I flash for a 4.0.3 based ROM?
You don't flash gapps on a stock based ROM ever
Sent from my Vivid 4G using XDA Premium 4 mobile app
Hello,
I need some help with install CyanogenMod 12 - Neo's Homebuilds
I have Sony Xperia T LT30p
Android ver: 4.3
Kernel ver: 3.4.0
Build number: 9.2.A.1.199
Phone is unlocked and rooted.
I have problem on next steps - recovery and flash
In instruction to install CyanogenMod12 doesn't write how recovery I shoud use. I read, most people use CWM, so I was looking for that recovery.
Unfortunatelly, from this post http://forum.xda-developers.com/showthread.php?t=2012738 when I tried run CWM v9 installer for JB, select my phone from list
I have only " deamon not running, starting it now on port 5037* deamon startded successfully" and nothing happens.
I flashed this one: http://forum.xda-developers.com/showthread.php?t=2677553 Installed correctly, I go to cwm recovery, I did a backup, but when I was tried
install rom, I have an error something like "You tried install rom for LT30, but your device is Hayabusa" and installation is aborted.
What recovery (and from where) I need, to correctly install this mod? Do I need install another kernel too? (All kernels what I seen, have older build number than I have on the phone)
Could someone help me to finish this process?
Best Regards
Same issue like here.
http://forum.xda-developers.com/showthread.php?t=3038250
Check this out. :good:
Hey WhiteNeo, thanks for response.
I read this post before, but in there, user has a Xperia V, and has a different Build number, and he has (a good?) recovery (I don't know if this has any significance) and aborts appears, in the middle of installation with different kind of error log.
I have abort message on the beginning, telling that the rom is ok but device is Hayabusa..:/
Could you tell me what recovery I should use? (Or maybe this what I have installed is correctly? I don't tried do this on the TRWP)
I need flash another kernel? or it's not necessary?
Still, the steps I mentioned are the same.. Either remove the first line in updater-script, or flash my kernel via fastboot before installing the rom.
The kernel does include a working recovery from where you may flash the rom itself.
Good news, I finished and it works
I flashed the kernel – boot.img from your rom zip package (maybe it worth add this info to the instruction on first page?)
Thanks very very! much for your hints. So now I join to the „tester” your great rom
For now (using only 1 hour) I found only 2 bugs.
First is a „!” symbol near gsm signal when we turn off cellular data.
Second is a unable to turn on the camera using dedicated button.
Thanks again.:good:
KOMODO404 said:
First is a „!” symbol near gsm signal when we turn off cellular data.
Click to expand...
Click to collapse
Funnily enough, that symbol shows that you don't have cellular data (internet connection); if you don't like the symbol, turn on cellular data or connect to a working WiFi network.
Antiga Prime said:
Funnily enough, that symbol shows that you don't have cellular data (internet connection); if you don't like the symbol, turn on cellular data or connect to a working WiFi network.
Click to expand...
Click to collapse
The "!" symbol, it's not funnily enough, on any kind of system or application.
It's little weird kind of notification about disabled internet connection. Many people save the battery or $ by
disabling cellular data (in stock system you don't have any icon to inform that status) and that should be
something "normal", "!" is unnecessary to inform that fact.
KOMODO404 said:
The "!" symbol, it's not funnily enough, on any kind of system or application.
It's little weird kind of notification about disabled internet connection. Many people save the battery or $ by
disabling cellular data (in stock system you don't have any icon to inform that status) and that should be
something "normal", "!" is unnecessary to inform that fact.
Click to expand...
Click to collapse
Then you should probably complain to Google and it's developers for creating that ugly and disgusting icon, instead of labeling it as a bug. Just because there is something about your phone that you don't like doesn't mean it's a bug; that's like saying my battery only lasting 18 hours is a bug, when in fact I leave my screen on for more than 3 hours.
Also, I didn't know there was an Official Android 5 Stock Rom for either the T/TX Sony phone, so I wouldn't know about how it behaves. Please do share the news.
http://www.androidpolice.com/2014/10/18/lollipop-feature-spotlight-android-now-defaults-to-mobile-data-when-wi-fi-has-no-internet-access-signal-icon-adds-a-for-no-connection/
Also custom ROMs don't always have the same features stock ROMs do, for instance, opening the camera app when clicking on the camera button (doesn't work on any of the custom ROMs I've used), but again, that doesn't mean it's a bug.
You can probably use Xposed + Xposed Additions to get that function.
Antiga Prime said:
Then you should probably complain to Google and it's developers for creating that ugly and disgusting icon, instead of labeling it as a bug. Just because there is something about your phone that you don't like doesn't mean it's a bug; that's like saying my battery only lasting 18 hours is a bug, when in fact I leave my screen on for more than 3 hours.
Also, I didn't know there was an Official Android 5 Stock Rom for either the T/TX Sony phone, so I wouldn't know about how it behaves. Please do share the news.
Also custom ROMs don't always have the same features stock ROMs do, for instance, opening the camera app when clicking on the camera button (doesn't work on any of the custom ROMs I've used), but again, that doesn't mean it's a bug.
You can probably use Xposed + Xposed Additions to get that function.
Click to expand...
Click to collapse
I didn't know that in the original android 5.x symbol "!" near gsm signal, is implemented - is changing, figure things out.
For me, its a little strange, "!" symbol should inform that something is wrong / something damaged but in this case
everything is ok but symbol is displayed. All right, this is only my opinion.
I didn't write nowhere about official android 5 for Xperia T, so I don't know what you mean.
About camera button, it's works, example on the Ultimate PureXT custom ROM, so it is possible to work on custom rom.
If it's designed for something, and now it's not working as it should....how do you call it if not a bug? fault? defect? mistake?
Fortunately, it's only a details and I'm grateful to the authors, for this custom rom and I keep my fingers crossed for next update
to improve this rom.
KOMODO404 said:
I didn't write nowhere about official android 5 for Xperia T, so I don't know what you mean.
About camera button, it's works, example on the Ultimate PureXT custom ROM, so it is possible to work on custom rom.
If it's designed for something, and now it's not working as it should....how do you call it if not a bug? fault? defect? mistake?
Fortunately, it's only a details and I'm grateful to the authors, for this custom rom and I keep my fingers crossed for next update
to improve this rom.
Click to expand...
Click to collapse
What I meant was that even on Stock ROMs, the icons change to show there is no connection to Google's servers (blue colored signal in 4.3 and below, and orange colored in QS in 4.4), so it shouldn't surprise you that the function is still there.
About the camera button... I would probably call that not having access to the entirety of Sony's source code, drivers, etc., in order to implement that function, and custom ROM developers probably just haven't simply figured that out yet; because, for your information, the Ultimate PureXT Rom is not a custom ROM.
Hello,
I have a motorola G6 that after bad root get stuck on bootloop.
I flash the phone with two roms but the phone after flash dont have sound during calls, the earpice dont work even in loudspeaker, but the phone rings when is receving calls.
anyone already have this problem?
tanks
This question is probably in the wrong section but anyway...I did. I never checked the phone prior to rooting so I'm not sure if a "bad root" was the cause or not. However, I experienced the exact same problem as you. I was originally on build OPS27.82-19-4 so I reflashed stock OPS27.82-19-4 as described here. But I still had the same problem. On a whim I randomly flashed build OPS27.82-19-4 following the same instructions. The phone has been working great ever since (I have it rooted, xposed. etc...). Not sure why there was a problem, or if reflashing the newer build "fixed" it or not...but as I said, all is good now. FWIW, when I check the sim status in settings>about phone, the network section is blank. It was blank when I had problems too.
Perhaps this will help you..
PS When I reflashed the firmware, the phone would boot into fastboot mode, then when I selected "Start" it would boot to the OS. If you run into that, here is how it was fixed. See posts 5, 6, 7, & 8.
Good luck!
I had a similar problem, I did the root, TWRP, I ended up giving up and flash again on the stock of the bike G6 Play (Brazil) available here in XDA, to my surprise, he made and received calls normally, the speaker for music and connections of other applications (Whatsapp, Messenger, Hangouts, etc.), but it did not work for the rom dialer.
I thought I had a problem, it was when a system update appeared, I installed it and it worked again.
I figured it was some rom bug I installed.
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Multiredes said:
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Click to expand...
Click to collapse
That's because a custom rom or GSI does not have all the necessary files. 99.9% of the time, flashing stock will fix a problem.
First of all, I'm running MSM Xtended v9 dirty flashed from v5 which was clean flashed after Havoc OS Pie rom some time ago.
Okay so here is the problem as specific as possible.
At first, after doing an online call using headphones (Either via Whatsapp, Messanger, Discord) the mic would suddenly stop working, no voice input would be detected whether its Voice Notes, regular calls, google assistant or any other app that detects voice input. This was back on MSM Xtended v5, which was Clean flashed. The problem then persisted and turned into the mic doing the same thing even without the headphones, then onto doing it again for regular calls too, not just the online ones (so that means I have to reboot after every call). I thought it was a problem with my android version so I upgraded to v9, dirty flashed. I wanted to opt for a clean flash but I had some data on apps that couldn't be backed up at the time. Problem still remained and now the mic suddenly stops working after reboot for no reason without making any calls.
Obviously, as every developer recommends I thought to clean flash the rom again, and prepared myself to backup everything and lose that which I can't back up. Then while looking for a different rom, I noticed multiple people having the same problem for different ROMs, though all were Android 10 ROMs.
So I wanted to ask, is there any solution to this problem? It makes the device basically unusable without any mic, and I do understand that not everyone has the same problem but when I saw others having it I realized it might not be specific to my unit.
Anyone trying other Android 10 ROMs without this problem? Should I downgrade to Pie? Any help would be appreciated, please.
If you recommend downgrading please tell me how, as I seem to have forgotten and can't find the method online (it may be there but I haven't seen, I apologize if that's the case).
Thank you in advance.
Known issue on Android 10, most probably it is Gapps issue, so try Weeb Gapps if you don't need 'Hey Google' thing. Downgrading is not that hard on OnePlus 3T, just download OOS 9.0.6, backup your data to PC or OTG, wipe all and format data and flash OOS, that's it.