Dear All,
The case of my phone is quite peculiar because there are several very serious problems, that combine together and make it impossible to use.
> The main problem is the lag. Still after i flashed the CM 13 and i am using the last Boeffla Kernel it lags so bad that i can't use it properly. Sometime to launch an app takes 5/6 seconds. This isn't changed even with different configuration for the Kernel.
The problem connected with the lag is that it takes ages to launch the apps, specially the gapps. It takes ages to launch chrome or maps or gmail. usually after are being launched they work, but apps like chrome are difficult to use on multiple tabs for instance. In general the multitasking is very slow.
>Another problem is that after the screen is locked it it takes at least 3 seconds to to being reactivated, same timing with every phisical button that wake the device up.
>The last problem is that the connection, either 3g or any other, sometimes is present sometimes is not, but it doesn't depend on the area, for instance sometimes works in my room sometimes not.
Is there someone who can help me to find a solution for these problems?
@Volkert Gage:
If everything run fine before CM13, do a clean flash without GCrap and custom kernel - perhaps you fished the wrong GApps.
If there were problems before, go back to firmware to repair.
rp158 said:
@Volkert Gage:
If everything run fine before CM13, do a clean flash without GCrap and custom kernel - perhaps you fished the wrong GApps.
If there were problems before, go back to firmware to repair.
Click to expand...
Click to collapse
thank you for your adivice rp158,
The fact is that these kind of problems (except for the connection) are not new for the phone, i always had it, even with the original firmware.
Before the upgrade to CM 13 i tryed to sort it with the original firmware but nothing worked.
Anyway, can i ask you what gapps pack do you reckon might work better on the phone?
@Volkert Gage: I recommend strongly to flash latest firmware +factory reset. You can't expect any stable LP or MM, if Sammy JB struggles.
@rp158 i'll try to do so then, thank you.
Related
Hello,
I'm going to describe the dialer lag bug and a possible clue how to fix it. In short the phone hangs when you try to dial (call) a number for up to 10 seconds (at least on my phone) and then the dialing begins.
As far as I've researched it is present in other phones as well. I'm running the latest CyanogenMod nighty (update-cm-9-20120511), but the same bug appears in all previous nighties and in the latest official Samsung 4.0.3 ROM I tried (XXLP7 I think). The logcat logs are from CM9, but I believe the reason is the same in the official Samsung ROM.
Full wipe (+sdcard if that matters), absolutely stock. Logged in Google account. Direct call shortcut on the main screen. WiFi should be turned off (very important). If the WiFi was turned on, restart the phone first for reliable reproduction. Leaving WiFi turned on for a longer period sometimes masks the bug.
1. Screen off
2. Wait 10 seconds, screen on, unlock
3. Tap on the direct dial shortcut
The phone hangs for ~ 10 seconds and then begins dialing. Exactly the same procedure with WiFi turned on results in no lag. The number is dialed immediately.
I suppose this bug is present in all ROMs, based on Samsung 4.0.3 XXLPQ+ (possibly previous ones as well).
I've attached logcat logs from point 1 (screen off) until the phone begins to dial and I hang up.
No WiFi (hangs): http://pastebin.com/GC01G2FR
WiFi (doesn't hang): http://pastebin.com/eJS9N6sz
Subtracting the noise, the last identical line between two versions is:
Code:
D/PhoneUtils( 2207): checkAndCopyPhoneProviderExtras: some or all extras are missing.
This is the line which appears when I start dialing the number. After that the difference are those lines, present only in No WiFi (hangs) version:
Code:
W/ActivityManager( 1985): Timeout of broadcast BroadcastRecord{410f0a90 android.intent.action.SCREEN_ON} - [email protected]40f159d0, started 10000ms ago
W/ActivityManager( 1985): Receiver during timeout: BroadcastFilter{40f15bd8 ReceiverList{40f15b60 1985 system/1000 local:40f159d0}}
I'm a developer outside of the Android ecosystem, but as far as I understand an intent broadcast SCREEN_ON is issued and its intent receiver timeouts in 10000ms (those 10 seconds during which the dialer hangs). Supposedly Android is waiting for some intent receiver to handle its onReceive() and during this period nothing happens.
Please note that in the log there is another timeout before this one with the same consequences, but with timeout for intent SCREEN_OFF, issued seconds earlier when I turned the display off. That's why I skipped it.
Interestingly with WiFi on this doesn't happen.
I searched many forums and some people report (but can't describe) the problem. Other don't have it. I suppose there are other variables I can't isolate. Can you please try to reproduce it and point me to the right direction (tools, approach) how to debug it? This is a showstopper bug IMHO.
This post is mirrored here: http://forum.cyanogenmod.com/topic/50279-dialing-lag-after-screen-on-with-logcatanalysis/
May I ask the administrators to transfer this thread in the section "Galaxy S II Original Android Development"? I think it will be more appropriate.
It happens to me only on stock ROM. cm9 never had that issue.
It actually started after I flashed the xwlp9 xen ROM, after that it haunted me for some time, until I went back to GB, deleted my contacts from gmail and resynced all again.
Wifi thing is interesting but I can't reproduce as it only happens once in a while. and doesn't reoccur the next time.
I'm on dxlp9 now and it happened just once in 4 days.
Yes, it is really frustrating. I didn't have the issue several days after I migrated to CM9. Now it happens even after full wipe. It is so annoying! This is basic functionality and I see people with Galaxy Nexus suffering the same issue. I think that I have enough knowledge to find the root cause, but I need somebody with a little Android debugging experience to help me start!
I have been having this problem as well with the stock (rooted) rom, and i recently flashed the Resurection Remix ICS rom (v2.0) just a few days ago and i still have this problem, almost without exception (ie easy to reproduce). I hadn't noticed the wifi part, for me it is about a 10sec lag with or w/o wifi, and actually i am now noticing a lag when turning on/off wifi... sigh.
I never got past "hello world" in perl so effectively have zero developer experince but if you have managed to figure out a fix for this I would love to hear it!
-Gaiko
After no one expressed any interest in this bug and I tried hard for a week, I gave up. Unfortunately IMHO Android 4.0.x is way unstable yet (I've experienced many issues with both stock and CM9 nighties). I reverted back to CM7 (currently 7.2.0RC3). It is Android 2.3.7 based, but I don't really miss anything from 4.0.x and I'm more than happy.
Thx for the reply. Its unforunate that its been so unstable, on my phone it seems like the longer i run it the less stable it is. I am going to try a newer stock rom and if that still gives me probs i will just go back to an older kernel and see if that does the trick.
Cheers,
-Gaiko
It's the first time I run into this issue and I had many stock and custom 403 and 404s.
For me, the delay is 5 sec and it ocurs randomly with or without wifi.
Now I run stock 4.0.3 xwlpg, jkay's fw, latest siyah kernel, go launcher.
I had this setup in the past and it didn't happened. Strange, ain't it?
Actually I don't care about this bug anymore. No one did anything to help and in Android 4.1 it is fixed. As I'm running on the latest nighties of CM10/4.1.2, I don't experience it anymore. Sometimes it's funny how fast technology goes forward.
I have this bug in android 4.2.1. Never used to have it, now I randomly do. Strangely, it cropped up at the same time as the multiple duplicate sms bug... I think they may be related. Any ideas?
My US Galaxy Player 5:
Model: YP-G70
ROM: Eryigit Rom 3.0 USA
Firmware: 2.3.6 Gingerbread
Launcher: ADW
Rooted: Yes
Sorry if this question has already been answered elsewhere, but I have scoured the forums and have seen no other people with an experience similar to mine.
I bought a refurbished galaxy player 5.0 US version on amazon about 6 months ago. Since about a week or two after I bought it, I have had nothing but problems with it:
-The player will randomly say the SD card has become unmounted (never on for more than 2 hours without the SD card being unmounted,) and the only way for it to recognize the SD card is a reboot
-The player will freeze when I am trying to open an app, and I am forced to hard reboot
-Occasionally starts randomly playing songs at full volume through the speakers, even though the player is on silent and is not being used (and there is no alarm on.)
I was originally using the stock ROM, and these problems gradually became worse and worse. After the freezing became so bad that I was literally forced to reboot (sometimes multiple times) any time I wanted to switch between apps, I decided to try using Cyanogen instead of Stock Gingerbread.
I loaded version CM7.2.0, and all of these problems completely disappeared (except for the SD card unmounting problem, but even this was way less frequent.) I used CM7 for a few weeks, and ran into the problem where flight mode was stuck on and I couldn't use my WIFI.
I tried to factory reset a few times, but still couldn't get it to work, so I tried flashing the Stock Gingerbread 2.3.6 back on, but got the boot loop error. I ignored the boot loop and used CWM to put CM7.2 back onto my player. I eventually got the WIFI to work through a third party app, and was able to use my player with no errors for about a week, until it went completely haywire and started crashing any time I tried to use any apps that WERE NOT third party apps. Also, none of the features like WIFI, bluetooth, camera, etc. were working. My app I use to study Chinese was still working, so I waited a few weeks before I tried to recover the player in case doing so made it unusable. I tried a hard reset, and this time I got a boot loop for Cyanogen as well. After a few weeks and about 40+ hours of flashing different ROMs onto the player and using different strategies to do so, I finally got past the a boot loop using Eryigit Rom 3.0 USA.
I was very happy to have use of my player back, but only a few days after flashing the stock ROM, the problems that plagued my player initially have returned.
Sorry for the novel, but I wanted to make sure I included a detailed history of my problems in case any lend some insight in to what is wrong with the device. Does anyone have any advice on what to do moving forward to fix any of these problems? Thanks in advanced.
Also, this probably isn't related, but I would like to note that my player stayed on without being charged for 10 straight days (with intermittent use over the period) when I had CM7 flashed and it was messed up. Wanted to point that out in case it signified that some specific critical process was not running, which led to buggy usage, but super long battery life.
Did you wipe the data partition and dalvik cache when you installed each new rom? If you didn't, I suspect that's causing a lot of your problems right there. To fix it, you'll need to use the "reset to factory" and 'wipe dalvik cache" options in CWM.
A couple of your problems are standard behavior. Specifically, the lack of bluetooth, camera, and hw acceleration are normal with CM9 or later on this device. Also bootloops will happen if you reboot your device while it's connected to a computer.
One possible solution for your sd-card issue is to unmount the drive (in the settings/control panel) then physically eject the card and reinsert it (making sure to push it in all the way, you'll feel it latch). That's what I did when I had a similar problem with my player and the sdcard.
Could be you did not wipe when you install rooms .. also try some 4.1 rom offcourse with wipe
Sent from my Galaxy Nexus using xda app-developers app
Hey everyone. I want to apologize in advance if I'm posting this in the wrong section (not permitted to in the development until I have more than 10 posts).
I have a Galaxy Note I717 and installed the latest AOKP rom running android 4.3.1. The phone runs relatively stable however after it was installed for about a day the bluetooth would beginning to flicker on and off every so often. Along with the bluetooth flickering on and off the keyboard to send a text, search, etc. would not stay open. It would open for a brief second and then close immediately.
There are many solutions to resolve this issue.
- reinstall the rom
- wipe dalvik cache
- wipe system/cache
After doing all these different procedures the phone is still having issues. The phone is occasionally reboot on its own and the keyboard keeps giving me the same issue. Sometimes I'm able to mess with the input method and the keyboard will stay open but then it begins to close immediately after thirty minutes or a few minutes.
Please if anyone can help it would be awesome to actually get this resolved. Each rom I've installed on my phone has had some kind of issue (bluetooth, speaker echo, constant phone reboots, sluggish performance after a day or so (this happened on Liquidsmooth 2.25), etc)
Thanks to anyone who has some insight on this.
I am using lg d605 for a while now. Everything worked fine before kitkat, but as soon as i upgradet, i started having an issue with messages. Sometimes (not always) i do not receive text messages and i never get them. It happens as rare as 1 in 30 messages, but it gets irritating if you are chatting with someone. At first i thought it is a problem with sim card. I've renewed it - nothing changed. After that i took my phone for a fix via phone warranty. They did not detect a problem and only rewrited the stock ROM. But... it did not solve my problem. As i have noticed afterwards, the problem was occuring if i had at least one app installed that is running as a background app. Like facebook, messanger and much more. As soon as i deleted facebook (it was the program causing issues back then, bet afterwards i learned that it was all aps that run in the background), the issue was gone, i have started to get all messages. How could I fix that? (I am not the only one in Lithuania facing this problem). I am open to any suggestions.
There are a lot of people having this problem in the Czech Republic. Currently, there is no known fix for this issue although some people had the signal receiver replaced (not sure if it helped, though). There seems to be suspiciously many software issues such as both background and foreground task being killed including the keyboard, hearing no sound during a phone call and other issues which can be temporarily solved by restarting the phone, i.e clearing the RAM.
My bet is the stock ROM (both JB and KK) which LG totally screwed up and aren't willing to admit it. If you don't mind messing with your phone a bit, I'd suggest trying either the CM or PA ROM which can be found on this forum.
Thank you for the replay
Alnydesr said:
There are a lot of people having this problem in the Czech Republic. Currently, there is no known fix for this issue although some people had the signal receiver replaced (not sure if it helped, though). There seems to be suspiciously many software issues such as both background and foreground task being killed including the keyboard, hearing no sound during a phone call and other issues which can be temporarily solved by restarting the phone, i.e clearing the RAM.
My bet is the stock ROM (both JB and KK) which LG totally screwed up and aren't willing to admit it. If you don't mind messing with your phone a bit, I'd suggest trying either the CM or PA ROM which can be found on this forum.
Click to expand...
Click to collapse
Oh, I see. Thank you for the replay.
Hello all,
Last week, I broke my oneplus one's screen so I decided to try and revive an old oneplus X.
A month ago, this device was still running the latest available OxygenOS but I played around with the device at the time and decided to install Lineage 14.1. I used the following versions of TWRP and LineageOS:
- LineageOS-14.1 20181110-nightly-onyx-signed (was no longer available on the official LineageOS site)
- TWRP version 3.3.1-0-onyx
After installing LineageOS 14.1, I noticed that there were some glitches when using the phone and the UI would lagg very hard sometimes. Since my Oneplus One was still working fine at the time, I decided to not troubleshoot this any further and put the device away.
Unfortunately, last week I dropped my Oneplus One and broke its screen, so I immediately tried to fix the Oneplus X again. I figured this might have been an issue with the LineageOS 14.1 ROM so I browsed this forum for an android 9 build and found the builds by YumeMichi and by psychem.
First, I booted into TWRP and performed an advanced wipe with every option selected.
Then, I installed Yume's build using the latest version of the ROM and Yume's version of TWRP: "twrp-3.2.3-20190127-onyx".
This booted fine and looked very promising at first, however the glitching/lagging returned after a few hours of use.
Then I cleared everything again and tried psychem's version (11.08.2019 build, without MicroG). I did not change the TWRP version (still using Yume's TWRP). This would not boot but I solved that by flashing Yume's build again and then dirty flashing psychem's build on top of it. That worked fine, untill after a few hours, the lagging and glitching returned.
The past week I've been playing with the power settings and trying to find someone with a similar issue on google. No luck, unfortunately.
The, on 22/08, I noticed psychem released a new build (22.08.2019). I installed that one and at the same time enabled the option "Force use of GPU for 2D rendering" in the developer options. That seemed to do the trick. I was able to use the device for 2 days without any issues, until the glitching happened again yesterday evening.
Today I installed the 23.08.2019 build but that did not solve the issue unfortunately.
To clarify what I mean by glitching/lagging: the phone seems to work fine for 90% of the time. Everything works, the device is performing smoothly and the battely lasts more than a day, awesome.
But sometimes, the screen starts glitching, the interface is extremely laggy and the phone might even randomly reboot. This phone will then be glitchy/laggy andis unusable for an hour. Rebooting does not help, clearing caches does not help, ... The wierd thing is, the same behaviour is also present within the TWRP interface at that moment (so not only once android has booted), as you can see in this video I made. It as also present during the boot phase. But, after a certain amount of time (usually 20-60 minutes), all is fine again and the phone works perfectly.
Is there any change this is not a hardware issue and I might be able to save this phone? The only reason why I think this might not be a hardware issue is because the phone runs fine 90% of the time.
Thanks in advance!
latest build is the 23.08 build.
Try this Nougat RR 5.8.5, works great for me, no lags at all.
https://androidfilehost.com/?fid=6006931924117938132
psychem said:
latest build is the 23.08 build.
Click to expand...
Click to collapse
Thank you. I installed this one, however that did not solve the issue.
I am inclined to believe this might not be related to the ROM at all, since all the LineageOS 14.1 ROM and Yume's ROM also had the same issue and also the issue is present in the TWRP interface and during the boot cycle too.
Is there any driver/firmware/software/... that might be causing this instead of a hardware issue?
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
BuzzBradA said:
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
Click to expand...
Click to collapse
Thanks for the suggestions! I do not have Chrome and Gboard installed so that should be fine, but I have disabled the double tap to sleep/double tap to wake option yesterday. Since then I've not experienced any more glitching/lagging. If it returns I will disable the HW buttons and use on-screen buttons and report back.
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
acidiz said:
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
Click to expand...
Click to collapse
To put your mind at ease, try OOS and see if it occurs. Then you'll know for sure.
Edit: just saw your video, never seen that before.