Related
Just got my Galaxy S up and running on AT&T. It's the unbranded phone - not a captivate.
What is the best stable rom right now? I read about the official version codes, but I'm confused as to JR, JP, JM, etc.
At this point I just want something that's fast and works, so probably something 2.1 based. Later when I have more time I'll play with Froyo.
[Q] SGS South American Version will come whit DIGITAL TV reception
Guys, d u think there is gonna be a way to do it whit software changing, like flashing the SA firmware, or the phone needs a hardware part to receive the T signal ?
[Q] Laggy pinch-to-zoom
Hi everybody!
When i use the pinch-to-zoom function in my browser (the default browser on SGS), it's very slow. It is very laggy and not fast at all. Is there a fix for this or have I missed something?
please help!
Think you've answered your own question there.
If you want it on 2.1 install launcherpro or something.
Sent from my GT-I9000 using XDA App
[Q] Battery Drain on Mimocan Lag Fix
Hello all
I have noticed that my battry drain very fast after I applyed the Mimocan lag fix with a Sandisk 16 gb card Class 2 (all thanks to Mimocan for this lag fix. Apps run much smoother).
The main problem is when the phone goes in to standby. Last night it drained 22% even with all sync action diabled and all apps killed. Before the lag fix I did only see a 2-4% drop in battery over night.
To compare it drained more then a 15 min call I made before I went to sleep (35% vs 25% of total battery used. I pulled it out of the charger 5 min. before the call, so the data should be correct)
When the phone is activated, it seem like the battery drain is about normal.
I wonder if all/most ppl have this problem or is it just me?
My guess is that the SD card is activated all the time to acces apps data, and thus drain the battery.
Im on the m2 software, but I dont know if its the software or just a common issue when doing this lagfix?
Give a comment, Thx.
[Q] What drivers are needed for Odin?
Like other people, I'm having extreme difficulty connecting my SGS to PC with USB. I have tried just about everything mentioned in the forums, including:
-USB drivers from Kies and other sources (like the ATT Captivate drivers). Usually the Kies downloaded package installs all, but it cannot find the samsung modem driver when I plug in the phone. The Captivate drivers could not find "USB gadget". I tried installing both.
-Reformatting SD card (actually allows me to connect to 91 Panda PC Helper in -debug mode... but that's it)
-Erasing all references to Nokia and Motorola using Regedit. However I did not erase references to Samnsung or Windows Mobile)
-Praying to the creator
-Sacrifice of chicken
-Starting phone while connected to USB
-turning off antivirus.
I tried flashing phone using odin, in download mode, but it seemed that odin could not see my phone. Nothing happened.
Anyone have other ideas?
[Q] Lagging in ALL KINDS of music player after flashing samset1.9
I dont know if it is just an issue only to me, but I am having lags in any music player i tried after flashing samset 1.9.Generally the device runs other apps really fast but the sound and music lags all the time except when I leave the device be to just playing the music. I am using ext4 for a2sd fix. Dont know anyone is having the same problem
[Q] open img files from ClockworkMod Recovery?
Does anyone know a way to open the backup img files created by ClockworkMod Recovery?
[Q] Is the latest fix completely safe for device longterm?
Some people are wary of the stress caused by the latest fix, I am very very new to smartphone's in general and wanted the honest opinions of those who truly know android/device hardware.
There is a lot of well intentioned misinformed posters in any forum. But these things are important to get correct, I would much rather wreck my external 32GB card than the actual phone internal memory.
[Q] Busybox not installing
Hey all,
I am having a problem with busybox. According to the 1.18 installer, I have 1.15.3 installed. But the installer won't let me upgrade because 'the nand is not unlocked'. When I try the older 1.17 version, I suddenly have no busybox installed and have the same message with the failed instalation. What can I do....
Running jm5 with samset 1.9 (ext 3/4 fix not applied).
Alvast bedankt.
[Q] Wake the phone using Menu, Home or Back button?
Like the title says. Does anyone know if there's a way to wake the phone up using the Menu, Home or Back button like they've been able to do with the Desire and Nexus One?
Reference:
http://forum.xda-developers.com/showthread.php?t=696907&goto=newpost
Samsung placed the power button at an awkward place. I assume it wouldn't be too hard to accomplish this. Probably using an app or coded into custom ROMs?
EDIT: Don't have the phone yet but so I assumed it couldn't do it like the Desire. it seems you can wake the phone with Home and Power. I think the thread above details how to enable/disable the other buttons in waking the phone as well. Looks like a simple editing of the keyboard layout and then pushing it back. Thanks.
[Q] Still lag in Contacts and Phone even with Quadrant score 2106
I am now having Quadrant score of 2106 after using RyanZAEXT2Lagfix Alpha1. It is a huge increase. However, i still notice the annoying lag in CLOSING of application such as CONTACTS and PHONE. Opening of these application is also not as seemless as in Desire HTC sense which I previously own.
Can anyone tell me how to fix this?
[Q] No missed calls, sms, emails showing on icons
Last rom to work was a froyo rom, now any rom i put on dose not show a numeric sign to how many sms, emails or missed calls have not been read, please dose anyone know why?
[Q] ODIN questions
Hi there,
Could anyone tell me what will happen if I did the following:
I checked around but I don't think these minor questions have been covered in the big FAQ
Is it necessary to apply repartitioning when updating to a new firmware?
Will you corrupt data if you upgrade just 'modem' or 'csc' on ODIN?
Will you retain all your data if you don't go for repartition when updating to new firmware?
I've successfully flashed 2 new firmwares. One of them was Russian (jm5) and I was told a bit after than I can just apply the jm1 csc. Anyway, I got over it and just reflashed back to JM2 as it was stable enough.
Thanks
[Q] Headphones and micro issue
Hi,
I am the happy owner of HiDefDrum (+micro) - by atomic floyd - headphones I bought originally for my iPhone. It worked great with the iPhone 3G 16Go (sound, microphone and button).
Now I bought a Samsung Galaxy S last week, and I have problems with my headphones.
If I plug the headphones completely, the sound is weird when I listen to music (as if I heard only an echo of the sound, I don't even hear the voice of the singer) unless... I press the headphones button ! Then the sound is normal.
I can listen to a normal sound when I do not plug the headphones completely (leaving the last part of the plug outside).
And in any case, the microphone does not work.
I thought it was a hardware problem, until I saw that we can access many configuration settings using the code *#*#197328640#*#*
I guess the problem can be solved by modifying some settings in this menu, but I have no idea which !
Can anyone help ?
[Q] Question before drastic measures :) experts please
Hi Guys
I have tried all sorts of lag fixes on this forum, but after installing a couple of apps (10 to 15 in my case). The telephone is sluggish and laggy.
Yesterday i got fed up oflag fixes and firmware flashing hoping that the next version will be the solution so i put it on one of the online selling websites
I really like the way the phone looks and its amazing hardware but i am really not sure whether to keep it or sell it
Everyone keeps saying that the froyo 2.2 update will solve all the problems, so would you guys recommend holding on to the phone till end of september till the froyo is released, or should i sell it now and minimize my losses and try some other mobile phone
Is it true that 2.2 is gonna do its magic regarding lag and the time it takes to load an app, or am I having high expectations
[Q] Couple of newbie questions :)
Greetings fellow Friends from Galaxy
I just moved myself from the HTC Magic section to this one.. It was quite a jump, the Galaxy S Camera and 4inch screen are AWESOME =)
I have a few noob questions that I don't want to spread through many posts, so i've chosen to get them all here, without polution this forum section. Also they might come in handy for future Galaxy S buyers!
My phone is: 2.1-update1 @ I9000XXJF5
Question #1
Well at first glance everyone's trying to fix the "LAG PROBLEM"... I haven't noticed any lag!! What are we talking about? If its a fix.. i want it too
Question #2
The phone came with Android 2.1, but at samsung-firmwares.com and at this dev section of the forum, i saw the JP3 Froyo release. How stable is this? Is it already a daily driver or a total beta? As an Android lover, i'd love to have the latest
Question #3
I've used the One Click rooting solution and then the ROM Manager Clockwork to boot into clockwork rom and make a full-system backup. In my HTC Magic i had the recovery ROM (Amon_RA) flashed into the internal phone memory, so even if i didn't have a ROM installed, i was ALWAYS able to boot into recovery. That was a safety plus. How can i flash the Clockwork Recovery directly to my phone, without the ROM Manager? I'd feel more secure if i could count on recovery even if, for example, i flashed a non-working system ROM.
Question #4
So what is YOUR favourite ROM? My stock has some unwanted apps, and even worse, it's Eclair. I'd like to switch soon, but i don't know these Galaxy S ROMs Tell me what's the best ROM for you!
Thanks guys, XDA is indeed the #1 place for mobile stuff
Cheers
Phk
[Q] Galaxy S stops syncing corporate calender after upgrading it to firmware JG4
Anyone else having issue with syncing stock calender with corporate calender on exchange 2007??
[Q] Restoring File to /system/lib Without Root
I accidentally broke my phone by accidentally removing libgps.so now it won't boot.
I can get into recovery mode and see the device under devices, but I am unable to obtain root:
$ su
su
link_image[1728]: 2453 could not load needed library 'libandroid_runtime.so' fo
r 'su' (link_image[1728]: 2453 could not load needed library 'libui.so' for 'li
bandroid_runtime.so' (link_image[1728]: 2453 could not load needed library 'lib
pixelflinger.so' for 'libui.so' (link_image[1728]: 2453 could not load needed l
ibrary 'libhardware_legacy.so' for 'libpixelflinger.so' (link_image[1728]: 2453
could not load needed library 'libgps.so' for 'libhardware_legacy.so' (load_lib
rary[1058]: Library 'libgps.so' not found)))))CANNOT LINK EXECUTABLE
I can't cat the file, mv the file, remount /system.
Any wild and wacky work arounds in an emergency like this?
[Q] May I have the latest 2.1's official camera.apk
May I have the latest 2.1's official camera.apk
Just missing this file due to some unexpected problem.....
Could anyone help me a bit
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?
I broke the screen on my current phone and while it's being fixed I decided to give the ol' I9000 a spin. It was on Android 4.2.2, so I flashed the latest Cyanogenmod 11 snapshop and installed some apps. Both before and after the flashing I had some seemingly random performance problems. There were times when it performed reasonably well, scrolling and opening apps, while mere moments later it took minutes to open the default keyboard and write a few words. Is it something I can diagnose further or fix? Could it be some faulty component (like the built-in storage from example)?
I've attached the About information ...
My Original Post:
Phone runs hot. No deep sleep. High cpu usage from AndroidSystem app. Sometimes screen doesn't turn off after pressing power button. Phone runs slow.
All of this happen after any GPS data request from any app that can use device only gps data.
When GPS is off with a fresh boot, there is no problem.
When gps is turned on but not any data requested from it, there is no problem.
If you turn on device only gps and start using a gps app. CPU usage goes abnormally high and never falls down even after force closing the gps app and gps itself. Only a reboot turns the phone to normal.
Another thread I've found describing the same problem without solution:
http://forum.cyanogenmod.org/topic/94185-gps-bug-phone-unstable/
I've tested:
cm-11-20140916-SNAPSHOT-M10-p880
cm-11-20150517-NIGHTLY-p880
cm-11-20150524-NIGHTLY-p880
Euphoria-OS-1.1-p880-UNOFFICIAL-20150516
Euphoria-OS-1.1-p880-UNOFFICIAL-20150529
aosplp-20150423-p880
MK44.4-p880-150131-HISTORY (Mokee History)
LS-KK-v3.2-2014-10-14-p880 (Mourta Ed. with kernel 3.4)
LS-LP-v4.0-2015-03-27-liquid_p880 (Mourta Hybrid Kernel 3.4)
BeanStalk-4.4.4050-20140905-p880CMAD
Kernels:
Optimus_Prime_CM11-V3.0
iodakX3_v10_CM
WWJB_v009_anykernel-20140429
WWJB_v010_anykernel-2014-12-24_1303
I've tried listed roms and kernels with required wipe operations switching between them.
I've rebooted several times after installation and didn't give up in first boot.
I have CWM Official v6.0.4.5 as recovery.
Tried different governors and schedulers. No luck.
I'm using the phone with CM 10.1.3 Stable & WWJB_v009_anykernel-20140429 and I don't have this problem with it.
GPS apps never use high amount of CPU and when you turn off GPS apps, CPU usage falls to idle levels.
I've flashed same WWJB_v009_anykernel-20140429 kernel over a fresh CM11 M10 install and gps bug is still there.
I think this is not about kernel or rom but something different. I can't move forward from Jellybean.
Any idea what's causing this?
Any clues, ideas or suggestions are appreciated.
Click to expand...
Click to collapse
Update: I still have this annoying problem and I'm trying to solve this.
I need you to test this on your devices and tell me the result. Please.
How to reproduce the bug
1- Prepare your SD card with the custom Rom(Kitkat or later preferably with built-in file manager to install apks) to flash and apk files of F-Droid Satstat, CPU-Z for monitoring the cpu load.
2- Before flashing the rom, REMOVE your SIM card. The important thing is, do not let the phone go online after the fist boot. I will download the Agps data immediately and it may work without problem.
3- Flash X-cm12_1_1-20161131-ufoFILES-p880 or any other Rom which is 4.4+ or later. I've tried many and all of them have this problem.
4- After the first boot,(ignore the no "sim card inserted restart" notification just touch some where out of that box) install satstat and cpu-z.
5- Turn on your GPS if it is off.
6- Launch the GPS test app satstat. It will try to connect to GPS and Glonass satellites (if you have a v20 baseband) It is not important to keep the app running until you get a lock just wait for 15 seconds.
7- Close the gps app.
8- At this point you should be seeing a serious lag. Pushing the power button won't response. The phone won't go the sleep. If it does, it won't wake up easily. You will be pushing the power button several times to make it work. Battery will be drained fast.
7- Launch the CPUZ and watch the CPU load and frequency. One or two cores will spike up and down constantly and the cpu will stay at 1000-1500mhz forever.
8- There is nothing to do but restarting the phone. Sometimes my phone gets totally frozen before I'm able to restart it from the power menu. After the restart it will work normally. Provided if you keep the gps closed and not requesting info from it.
Could you test this please?
Problem solved. Temporary solution.
My description from CM11 Official thread:
Finally, I'm happy to clarify that both assisted and device only gps is working excellent!
After many sleepless nights, I've found what's causing the problem in my device. I've gone over 15+ custom roms and different kernels. I've changed baseband and custom recovery to only get despair.
The last thing I did before abandoning everything.... has worked.
Assisted GPS has to go on-line at least one time.
I'm not sure about the logic behind this but I can't believe how such a simple thing caused this trouble for me...
I don't have a data plan right now so no there is no data from cellular. I generally use device only gps outside. I've never used this rom with assisted gps when outside. I didn't get a chance.
When at home, I flashed roms with "device-only gps" testing in mind so I didn't bother connecting to wireless.
I tried this just with 20150524 and nothing else. (gapps, kernel etc.)
Enabled high accuracy mode on gps and connected to wifi.
Launched GPS Status & Toolbox app and at first, cpu usage was high but after the first fix, it's reduced to normal. I exited the app and cpu usage fell to idle as it should.
Switched off wireless and switched gps to device-only. Rebooted. Launched the GPS Status & Toolbox again and now it's working normally under device only mode. Other applications also working good.
Click to expand...
Click to collapse
Fused Location Provider, responsible for managing different data sources for providing geolocation data, manages the assisted or device-only gps itself. When you enable GPS, it switches the gps mode to high accuracy itself but if you hadn't gone online before with using assisted gps, gps is always stuck at device-only. I think that creates the high CPU usage.
THANK YOU THANK YOU THANK YOU!!!! I wanted to change custom ROM because of this, and you saved me from doing it! So, if I understood correctly, all I need is to enable High accuracy mode, launch "GPS status & toolbox" app (or can it be any other gps app?) and restart after the app gets a fix?
terirem said:
THANK YOU THANK YOU THANK YOU!!!! I wanted to change custom ROM because of this, and you saved me from doing it! So, if I understood correctly, all I need is to enable High accuracy mode, launch "GPS status & toolbox" app (or can it be any other gps app?) and restart after the app gets a fix?
Click to expand...
Click to collapse
You need to let the device to download A-GPS data from internet. GPS status & toolbox does this easily and you can see the "a-gps age" at the app screen as how old your data is.
Once you get a fresh a-gps data, the phone won't stuck at high cpu frequency when gps is enabled.
I 've found out that after "a-gps age" goes over 20+ days, something happens to the gps, and gps usage starts to cause high cpu usage and frequency stuck again. You have to re-download a-gps data to solve this.
I don't know why but gps in this device is not a true offline gps.
I've already described a temporary solution to my GPS bug.
I'm still trying to find a lasting solution.
Here is what I did in various posts:
http://forum.xda-developers.com/showthread.php?p=69893311#post69893311
http://forum.xda-developers.com/showthread.php?p=69970358#post69970358
http://forum.xda-developers.com/showthread.php?p=69988910#post69988910
http://forum.xda-developers.com/showthread.php?p=70066931#post70066931
http://forum.xda-developers.com/showthread.php?p=70067876#post70067876
http://forum.xda-developers.com/showthread.php?p=70068250#post70068250
http://forum.xda-developers.com/showthread.php?p=70071380#post70071380
http://forum.xda-developers.com/showthread.php?p=70084342#post70084342
I also tried
- replacing fusedlocation.apk from /priv-app folder with CM10.1.3 stable's fusedlocation.apk
- another fusedlocation.apk from Atrix 4g (wiped dalvik cache after priv-app change)
- μg v1.3.2 from >HERE<
New roms:
Near all versions after cm-11-20150524-NIGHTLY-p880 up to the FINAL cm-11-20160815-NIGHTLY-p880
omni-4.4.4-20150520-p880-FINAL
X-cm12_1_1-20161016-ufoFILES-p880
X-cm12_1_1-20161131-ufoFILES-p880
Kernels:
CyodakX3_v11_CM
cyospak12
Cyospak6-7
I also upgraded my V20D baseband to V20c-EUR-XXX-OCT-07-2014 and trying ROM/Kernel combinations with this.
So far I've only tried
cm-11-20160815-NIGHTLY-p880
omni-4.4.4-20150520-p880-FINAL
X-cm12_1_1-20161016-ufoFILES-p880
X-cm12_1_1-20161131-ufoFILES-p880
Nothing works for me so far.
Thanks to @oF2pks , I think this may be ril/baseband problem.
Here is another thing:
When I check the "Settings/AboutPhone baseband" it shows L6260_modem_sic_02.1233.00 but If I disable SIM PIN lock and restart the phone it shows LGP880AT-00-V20C-EUR-XXX-OCT-07-2014.
According to oF2pks, a healthy phone should always have only one baseband reading under Settings/AboutPhone baseband.
Sorry for the late answer. I didn't give up and still working on my issue.
For easy describing, lets say State X to the the high cpu state which is causing general slowdown, stuttering, lag and freezes for my device, which occurs after GPS usage, without any data connection after fresh rom install and that kicks in again any time if you are not online with the phone frequently.
After many flashes and tests I found some interesting things.
- In State X, the phone actually goes to deep sleep BUT you have to wait for the 1 minute screen timer and don't push the power button to send it to sleep. After waking it up, cpu is still stuck.
- p880-ota-eng.nmf26qz never displays L6260_modem_sic_02.1233.00 but still falling to the State X.
Only custom rom working without State X problem for me is the cm-10.1.3-p880 stable.
I tried:
Switching cm-11-20160815-NIGHTLY-p880's com.android.location.provider.jar with cm-10.1.3-p880 stable's. → Result: State X
Switching cm-11-20160815-NIGHTLY-p880's telephony-common.jar with cm-10.1.3-p880 stable's. → Result: Error at start-up
add line to getprop file: ro.ril.def.agps.mode = 0
→ Result: State X
Switching cm-11-20160815-NIGHTLY-p880's lge-ril.so with cm-10.1.3-p880 stable's. → Result: State X
oF2pks said:
So do you have right baseband v20C when you boot with sim-on, or still firmware number?
Click to expand...
Click to collapse
This is where the things are getting interesting...
- With CM10.1.3-stable, first boot after the rom flash(without sim card) baseband shows L6260_modem_sic_02.1233.00 but in the second boot with sim card, after the very first initialization with gsm tower, it shows LGP880AT-00-V20c-EUR-XXX-OCT-07-2014 and stays like this.
- With my current daily drive cm-11-20160424-NIGHTLY-p880 + WerewolfJB kernel V10
Without sim-> LGP880AT-00-V20c-EUR-XXX-OCT-07-2014
With sim-> LGP880AT-00-V20c-EUR-XXX-OCT-07-2014
Sim with sim pin lock-> L6260_modem_sic_02.1233.00
With different roms, sometimes baseband switches from LGP880AT-00-V20c-EUR-XXX-OCT-07-2014 to L6260_modem_sic_02.1233.00 after gsm initialization.
In one situation, after all the tampering, I flashed CM10.1.3-stable again and this time it was stuck with
L6260_modem_sic_02.1233.00 and never showed the LGP880AT-00-V20c-EUR-XXX-OCT-07-2014 but no State X
With my daily drive, I also checked both states with sibor's Getril. md5sums are the same.
I'm adding screenshots for them.
I think, maybe baseband display is irrelevant with my issue.
Also did format via recovery cleared your previous rom specific settings?
Click to expand...
Click to collapse
All settings clear but I'm not sure abut default gps switch behaviour. Maybe it's irrelevant too.
Somehow gps switch remembers it's old positions.
Today on single(/primary_multirom) rom I have same kdz designation v20D while booting airplane or sim-on.
But on 2nd/multirom I have the difference (due to primary fake transition via kexec ?), AND the gps is working fine : airplane boot (+FasterGps) + Satstat OK and deep sleep after OK.
Click to expand...
Click to collapse
My current daily drive does not have the State X rgiht now. It will stay like this for a while without internet connection, but after some time, something will trigger the State X again and there are two solutions:
1- Don't enable GPS
2- Connect to internet and update the A-GPS data.
Did you check CPU usage after GPS use?
Mine stays at 1000-1400mhz with one or two cores.
IMHO you should pm @Demetris about V20C because he was the one who did cover v20c-2014 :http://forum.xda-developers.com/show...postcount=2727 ; also he's OP for alternative http://forum.xda-developers.com/opti...grade-t2919195 (and many more...)
Click to expand...
Click to collapse
I did the CSE flash method of Demetris for the V20C 2014.
I'll ask him about this gps issue. Thanks for the suggestion.
I'm also adding my getprop result for you. From fresh CM10.1.3 stable.
The biggest deal breaker for me with this phone was the "temp_throttle_skin" (around 40°C) temp limit. It's a real pain to have and the main reason of general slowdown.
At least I can deal with this GPS issue from time to time when it needs correction.
My aim here is to create some consciousness about this elusive issue for the fellow O4X users, so some unexplained battery drain issues may be resolved or dealt with by the user.
I wish everyone a Merry Xmas and a happy new year.
@KSH2014 , can you check few more:
-is imei/software = printed imei under battery
-is GPS OK with cm10's original kernel
-is GPS OK with lg JB v20c
Within hidden menu in lg JB, I remember bunch of options (GPS ?), and you problem could be somewhere in it, maybe @RuedasLocas could help you to re-settle this hidden menu
http://www.lg-phones.org/lg-optimus-4x-hd-hidden-menu.html
oF2pks said:
@KSH2014 , can you check few more:
-is imei/software = printed imei under battery
-is GPS OK with cm10's original kernel
-is GPS OK with lg JB v20c
Within hidden menu in lg JB, I remember bunch of options (GPS ?), and you problem could be somewhere in it, maybe @RuedasLocas could help you to re-settle this hidden menu
http://www.lg-phones.org/lg-optimus-4x-hd-hidden-menu.html
Click to expand...
Click to collapse
I've been busy lately.
- imei matches.
- GPS is OK with CM 10.1.3 Stable release with it's own kernel.
- GPS was OK or I think so with JB V20. I have to check it again.
I'm planning to record and upload a video to show the problem.
Hi, I have a Redmi 4a with a custom android 11 ROM (tried a few).
Since a few days the microphone is not working on calls. If I record a video the audio recording is ok, so the mic itself does not have problems.
Hands-free calls work (loudspeaker), but still mic is muted or very low level.
Headset works correctly, with its own mic.
I think the microphone level is too low during calls, maybe some setting got messed up, but I do not know how.
I already tried doing factory reset, cache wipe, full wipe+ROM re-flashing, changing ROM (still keeping Android 11).
Only a few apps have microphone permission: Camera, FM Radio, Phone & now Phone Doctor Plus, which I installed to control the mic and the earphones plug (all working perfectly, all available microphones).
Google Assistant is disabled.
Bluetooth is off, nothing coupled at all.
Any Idea before I wipe again and try a ROM with Android 10 (or 9, or 8, ...)
Thanks, Leonardo
leodp said:
Hi, I have a Redmi 4a with a custom android 11 ROM (tried a few).
Since a few days the microphone is not working on calls. If I record a video the audio recording is ok, so the mic itself does not have problems.
Hands-free calls work (loudspeaker), but still mic is muted or very low level.
Headset works correctly, with its own mic.
I think the microphone level is too low during calls, maybe some setting got messed up, but I do not know how.
I already tried doing factory reset, cache wipe, full wipe+ROM re-flashing, changing ROM (still keeping Android 11).
Only a few apps have microphone permission: Camera, FM Radio, Phone & now Phone Doctor Plus, which I installed to control the mic and the earphones plug (all working perfectly, all available microphones).
Google Assistant is disabled.
Bluetooth is off, nothing coupled at all.
Any Idea before I wipe again and try a ROM with Android 10 (or 9, or 8, ...)
Thanks, Leonardo
Click to expand...
Click to collapse
Are you sure it is issue on your side? Did you try it out with several ppl? Might be some issue on the other side, just a guess.
First of all, I would recommend to check out telegram channels/official sites of mentioned ROMs for latest updates.
It looks to me as if you installed some outdated ROM, because i have not heard of mic issues for couple years.
Also join tg channel for our device, where you can request assistance.
Second suggestion would be check for phone caller app from other ROMs, from LineageOS for example is usual choice (you can find it on APK Mirror) or AOSP from AOSP-based ROMs.
If you have Magisk installed, check out for "NLSound for QCom Devices" module, it is a module that includes setting sensitivity of mic a lil bit higher as well as other sound enhancing options. (NLSound Tg Channel), or try to check out whatever module for that matter.
I changed a few other Android 11 ROMS, all with the same issue. Also AOSP.
Android 10 CRdroid works better, mic level is low, it's higher with free speaking.
It looks like a sensitivity issue, maybe I have to change some mixer.xml settings?
Now I'm back to Android 11, Nusantara (unified 4a & 5a), but still the problem persists.
Installed NLSound: not better.
Can I configure mic level on NLSound? Where (or with which app) should the mic level be exposed?
You cannot configure mic sensitivity with NLSound, but during installation you can choose option to increase it. Which i thought could resolve your issue.
I honestly ran out of ideas atm, maybe someone more expirienced will join the discussion.
But while we are at it, could you specify a little bit more, how your mic stopped work properly? Because it still doesnt looks like a ROM issue to me, all ROMs are generic and share same device tree, which already has optimised settings and rarely being updated.
Was it like you installed custom ROM and mic immidiately went bananas, or you installed custom ROM, mic worked for certain amount of time, and then issue appeared?
Maybe try to reflash persist.img and firmware.img from original MIUI ROM, or roll back on MIUI(but dont lock bootloader) and check if issue is still present.
2ley said:
You cannot configure mic sensitivity with NLSound, but during installation you can choose option to increase it. Which i thought could resolve your issue.
I honestly ran out of ideas atm, maybe someone more expirienced will join the discussion.
But while we are at it, could you specify a little bit more, how your mic stopped work properly? Because it still doesnt looks like a ROM issue to me, all ROMs are generic and share same device tree, which already has optimised settings and rarely being updated.
Was it like you installed custom ROM and mic immidiately went bananas, or you installed custom ROM, mic worked for certain amount of time, and then issue appeared?
Maybe try to reflash persist.img and firmware.img from original MIUI ROM, or roll back on MIUI(but dont lock bootloader) and check if issue is still present.
Click to expand...
Click to collapse
It stopped by itself, without me doing any specific install, as far as I can remember.
I reinstalled NLSound, with mic and volume optimizations. Still not ok.
One question: can I flash persist.img and firmware.img without losing the functionality of the ROM I have now, or should I then re-flash also the custom ROM afterwards?
Thanks for the hints.
leodp said:
It stopped by itself, without me doing any specific install, as far as I can remember.
I reinstalled NLSound, with mic and volume optimizations. Still not ok.
One question: can I flash persist.img and firmware.img without losing the functionality of the ROM I have now, or should I then re-flash also the custom ROM afterwards?
Thanks for the hints.
Click to expand...
Click to collapse
Yes, you can flash persist.img and firmware.img without any concerns about ROM.
It shouldnt affect ROM functionality, it is just a pre-caution step, in case any of previous ROM's you played with made some unnecessary changes.
2ley said:
Yes, you can flash persist.img and firmware.img without any concerns about ROM.
It shouldnt affect ROM functionality, it is just a pre-caution step, in case any of previous ROM's you played with made some unnecessary changes.
Click to expand...
Click to collapse
persist.img flashed, no change.
firmware.img: cannot find it in the stock MIUI I downloaded
rolling back to older MIUI: have not done it yet, as I do not know how to avoid relocking the recovery. I never did it before and I have run out of wife's patience in the meantime
leodp said:
rolling back to older MIUI: have not done it yet, as I do not know how to avoid relocking the recovery. I never did it
Click to expand...
Click to collapse
Gotta download Xiaomi official tools for this purposes. MiFlash PRO, or Mi Unlock or something like this, dont remember the name. The one you unlocked bootloader of a phone with, same tool can also flash stock MIUI back, if i remember correctly, According to MiUnlock FAQ bootloader wont lock, unless you choose special option "Clean All and lock"
I also found this instructions to deal with sound problems, check if it will fix your problems.
Spoiler: instructions
For non root users
Code:
Go to the following path
Setting > Google > search > voice > "ok google" detection and turn off both the options.
That's it.
For root users, edit audio_platform_info.xml and/or build.prop
Code:
Navigate to the root directory of the phone
Root/system/etc/
Then look for a file named "audio_platform_info.xml" with text editor of your choice .
Now go to the bottom of the file you will see </acdb_ids> , you need to add the below line before/above that </acdb_ids>
Click and add this line
<device name ="SND_DEVICE_IN_VOICE_DMIC" acdb_id = "100"/>
Now just save the file and exit the root browser
Reboot the device now. As soon as it boots up you may check thr mic quality if its better now or not
If you're still not satisfied with it then you may follow one more step. This will turn off the voice cancellation ( it could cause echo sometimes to the listener)
For this open root browser and navigate
Root > system > build.prop file
Open it with any text editor.
Look for following lines
persist.audio.fluence.voicecall= true
persist.audio.fluence.voicerec= false
As soon as you find these lines make true to false and it should look as follows
persist.audio.fluence.voicecall=false
persist.audio.fluence.voicerec=false
Save the file and exit.
Reboot the device and check if it's working or not.
As of your wife, there is only one common fix for that issue: switch from 'default charge' mode during night to 'super charge' one, and gotta charge longer in this mode, usually it helps them to switch from 'nagging mode' to 'silence mode' for a while. Apply this fix as often as she slips from 'silence mode', because there is no permanent fix for this issue.
End of the story:
I bought for a few € the miniboard with the USB connector and the microphone, replaced the old one and the phone is working again.
The not clear behavior of the microphone with the various Android installations was due to it starting to malfunction. The last days It was always completely silent.
Thanks to all for the help and the suggestions, I learned some new things.
leodp said:
End of the story:
I bought for a few € the miniboard with the USB connector and the microphone, replaced the old one and the phone is working again.
The not clear behavior of the microphone with the various Android installations was due to it starting to malfunction. The last days It was always completely silent.
Thanks to all for the help and the suggestions, I learned some new things.
Click to expand...
Click to collapse
Hi,
so does that mean, it was a hardware issue?
my dads Samsung Galaxy M21 has exact same problem
bushu16 said:
Hi,
so does that mean, it was a hardware issue?
my dads Samsung Galaxy M21 has exact same problem
Click to expand...
Click to collapse
Yes, hardware damage