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.
Related
Saved for later use....
Re: Droid Eris Issue/s!
I'm not too sure what this means of how I can figure out what or how to get a log file.
My phone has been doing a random slide all the way to the left. no matter what Rom I'm running. After a few hours my Eris, running 1.5 from jcase, and edited by k.
- Screen moves left
- fixs when I restart
- happened again after a few how's of phone on standby or playing.
- Also OS slow down.
- this has been on going for 3 days.
- wiped, everything.
-Flashed using same Rom, and 3 others. (Followed flash Rom steps.)
- Still same problem.
if anyone can it knows of any info or hoe I can make this more clear, I thank you.
sounds like a problem with the phone itself such as maybe a trackball issue. go to verizon and see what they say.
i discovered to 2 issues since i upgraded the newer 2.1. (i haven't flashed a custom rom)
one browser randomly closes while using it. my wife went to macy's website and it closed. no force close or anything.
two - google maps works, but if i i upgrade. every time i open the app a few seconds later it gives me a force close dialog box....
fKngFtd said:
I'm not too sure what this means of how I can figure out what or how to get a log file.
My phone has been doing a random slide all the way to the left. no matter what Rom I'm running. After a few hours my Eris, running 1.5 from jcase, and edited by k.
- Screen moves left
- fixs when I restart
- happened again after a few how's of phone on standby or playing.
- Also OS slow down.
- this has been on going for 3 days.
- wiped, everything.
-Flashed using same Rom, and 3 others. (Followed flash Rom steps.)
- Still same problem.
if anyone can it knows of any info or hoe I can make this more clear, I thank you.
Click to expand...
Click to collapse
Just to let you know my wife was having similar problems with screen going left. I have seen some people just have it while on a charger but we had another problem the phone would randomly die at various charge levels and sometimes not boot back up without plugging the charger in. We were able to get a warranty replacement on the battery and the issue with screen scroll to the left has ceased.
thank you everyone for the feedback. I'm going to see what happened with everything. I might just turn this into a project phone. I will try to clean the trackball, and use my other battery. I greatly appreciate the replies.
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
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?
Hi Folks,
This was the closet forum I could find for my phone. I actually have the GS2 HD LTE (i757) from Bell Mobility in Canada. Monday I finally received my Jelly Bean Update (4.1.2) I wish I could say I an excited however it has caused me so much stress, Ever since I installed it my phone has been terrible laggy. ICS gave me no troubles but after seeing the huge performance boost in my Wife's i9100m last month when it was available to hers I did not hesitate to update mine. Below I will list my symptoms, as well as the steps I have done to resolve this. I have search everywhere for an answer and have come up with nothing. Also to note, my Friend in the office has a Galaxy Note with a different provider (Telus) who received the update the same day, we can put our phones side by side and we both experience the exact same issue.
Setup:
i757 (S2 HD LTE)
Not Rooted
Symptoms:
Swiping to unlock is choppy
Opening Messaging to text takes three part (Loads the body, loads previous message and then keyboard loads in the middle of the screen and works its way down.
30-45 second pause to open the dialer
when clicking the power button to get to the lock screen it shows the desktop for a second, then god to my lock screen wallpaper then my lock screen icons appear. After this I can swipe.
loading apps
at startup RAM is 558MB/737MB. I hit clear memory right away it goes to 394MB/737MB. But open any app I am back up to to 550MB-600MB
Things I have tried:
Install install was Down with Kies as a regular update with all my Apps still installed.
I Wiped Cache and down a Factory Reset
Reloaded the Stock ROM with Odin3 v1.85
In developer options I disabled animation for Window, Transition and Animator
I disabled ripple effect for lock screen
I disabled Google Now
Tried to Wipe Cache then resume use without reloading OS
Tried Disabling GPS, Bluetooth, WiFi and sync.
Installed Android assistant to clean up startup
Did another Factory Reset/Cache Wipe then install OS from MSD
None of these options have made a difference. The phone worked flawlessly on ICS, I don't know what else I can do. Has anyone experienced this issue? and if so have they fixed it?
At this point I will try anything before I take out the hammer and fix it for good. Any assistance would be greatly appreciated.
- Boots!
Also my Current status is Factory Reset/Wipe Cache OS Installed from SD Card nothing install.
* * * COULD MOD PLEASE MOVE TO APPROPRIATE FORUM I MUST HAVE OVER LOOKED THE i757 FORUM * * *
Moved
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
windex23 said:
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
Click to expand...
Click to collapse
windex.
Please keep this thread in mind, Anything I can find I will post it here. If you could do that same that would be great. My S2-i9100 was amazing with the Official JB release also. I am surprised more people are not complain online about this as I know my friend with the Note on Telus is having same issue (Update was released the same time for him) I also called Bell and their Tech support said they were receiving alot of the same issues since the May JB update..
Damn Lag has got my phone!
AH! damn update lag has got my phone and my girlfriends too! We both have the samsung galaxy HD LTE I757M phone and have exactly the issues all of you guys have. From extremely slow response to flickering and its just a pain in the ass. My girlfriend tried a factory reset which worked for about a week with no lag or anything but then just started the same lag issues we all have. A lot of people apparently are reporting that a factory reset does the charm but its only a matter of time before the issues creep back to your phone. Right now I am going to try a custom rom for our phones and hope that it works. If it does Ill post the results for you guys to hopefully benefit from.
sean
I was having the same problem with my I757M. This phone is fine on ICS 4.0.4.
I don't know the real solution but, the phone is fine (for now)
Used Forever Gone app
Did a factory reset before upgrading to JB 4.2.1 (Maybe?)
Removed Ripple effect on Screen lock
Set the transitions to 0.5x
Power savings enabled (Screen only)
Disabled these system apps
100% HD Games
AllShare Play
Asphalt 6
Google Play Magazine
Google Play Movies
Google Play Music
Google+
GPS navigator
Let's Golf 3
Self-Service
Update software
Google Play Books (or Play Books)
Social Network
Ringtones and Applications
Sympatico.ca
Talk
Talkback
TV mobile (bell)
Y! Finance
Yahoo! Finance Daemon
Yahoo! News
I installed JB 4.1.2 today, saw some improvements, hope it is fixed for good !
The ram usage on boot (369MB / 737MB)
Sorry to post again !!
Okay, it started to lag as described by others. So I went back to 4.0.4... The battery life is better on Jelly Bean because it can reduce the screen's power (not just brightness)
I did this today, my last attempt with JB...
In Dial :: *2767*3855# (it formats everything, even sdcard, so backup your things before doing this !!!)
I configured ICS from the welcome screen (no gmail configuration, etc.)
Installed JB 4.1.2 from Kies.
I disabled the programs mentionned at my previous post...
There was still a lag when unlocking the phone. Tried Holo Locker and didn't do anything... still lags.
Then, I searched on the net :
http://forum.xda-developers.com/showthread.php?t=2224906
It seems TouchWiz has problems rendering Widgets on homescreen, so, I installed Nova Launcher to replace it.
For now, when receiving a SMS, after unlocking, the wallpaper can become black, but there is no lag like before. :good:
Same situation
My wife‘s i757m has the same situation. I wiped to factory and uninstall like "let's golf", google play music. Then it turned much better for about 1week and then be back lag lag lag again.
I have no idea why it is so ridiculous , cause my friend's I727(GS2HD rogers) is very good after he updated his in March.
Please help me SGH-1757M
I have the same Issues.
After upgrading the Phone to 4.1.2 bellow issues identified.
1) When Incoming call comes the Phone Frezes and Green and Red button on the screen does not work
2) Some times it works but when I get any call the Phone rings with black screen and after some time it comes with number and then caller id and then answer button
3) Every time when I went to Messaging it loads the messages with number and next updates the Caller ID and then body of the messages and text editor
4) Morning when alarm rings phone Freezes and does not allow me to stop the alaram and force restart the Phone.
I am having so amny problems like this .
Please suggest what we can do here to resolve these issues.
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.