Hi,
I recently upgraded to Android 4.4.2 and I have the latest CM 11 Nightly installed.... cm-11-20140217-NIGHTLY-d2att.zip
I installed pa_gapps-modular-full-4.4.2-20140531-signed
and installed the latest modem firmware modem_CWM_I747MUMUEND3
My problem is that the phone keeps randomly rebooting.... no idea why.... anyone else experience this issue?
Also the phone tends to freeze for about 3-6 seconds.... strange....
Other then the random reboots the phone seems to be working quite well. no issues at all.
Any help is appreciated!!! thanks!!
Could be a sensitive power button
Well that's why there called nightlies it might just be a bug....its weird that there hasn't been a stable build yet.....but you can try the monthly snapshot and see if that works
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Try an AOSP-based ROM or return to stock to see if it still happens.
Related
Ive noticed that flash does not work correctly on phone after the update. I can see where the flash on the page is then it shows a little blue block... any fixes besides uninstalling the update
Sent from my Super EVO running Sprint Lovers ROM!!
What rom are you running and have you tried installing the 10.2 version again. I've noticed alot of people are reporting the "blue block" problem with 10.3. Is it in the browser or an app?
dirkyd3rk said:
What rom are you running and have you tried installing the 10.2 version again. I've noticed alot of people are reporting the "blue block" problem with 10.3. Is it in the browser or an app?
Click to expand...
Click to collapse
I'm Running Sprint Lovers Latest ROM and I am now back on 10.2 and its working fine.. and I was having issues in the broswer...
jdawg0024 said:
I'm Running Sprint Lovers Latest ROM and I am now back on 10.2 and its working fine.. and I was having issues in the broswer...
Click to expand...
Click to collapse
I actually downgraded back to 10.2 myself man 10.3 crashes on me alot lol. It has weird issues man
Sent from my PC36100
where can i get 10.2 from,,, having same issues using fresh evo 2.2
im still using the original release of flash 10.1 (as far as i know) and im getting the blue block as well and cant install 10.3 for some odd reason, so where can 10.2 be acquired
using king cocoa II
I had the same problems with 10.3, it would buffer and rebuffer alot where as I go to the same site on 10.2 and the streaming is perfect no rebuffering every 20 secs.
i've been using 10.3 and things were fine when using the lastest FRESH rom. but I just switched to GingerAle and the browser FCs a lot when there is flash.
Hi,
I've purchased a a Samsung Galaxy 551 (I5510) (Middle east region) about a year ago and i was running android 2.2 fine for a while. When the Gingerbread 2.3 update came out i tried installing a European ROM because the ME ROMs weren't updated, it worked fine but had a weird glitch that if the screen was off (phone still working) for a while it would be very dark when turned on afterwards, it looked like this video:
http://www.youtube.com/watch?v=Kwll8ZfgaD0
P.S. I didn't make the video, just linking it because its the same issue
it would randomly work again after a couple of lock-screen off-unlock cycles, then happen again randomly when it's off
I tried a number of GB ROMs (mostly 2.3.4) but to no avail, then finally the latest EU ROMs (I5510XWKPJ) fixed the problem, nowhere to be seen anymore.
After that i tried installing Cyanogen mod for the phone and the problem came back with different degrees:
1. Cyanogen 7 - normal boot, screen gets dark after being off for a while.
2. Cyanogen 9,10 - show Samsung logo at start, screen gets dark as soon as the cyanogen logo appears and continues to be
Any help on what would be causing that especially on the newer CM builds? and why it doesn't happen at all in (I5510XWKPJ)
Thanks in advance,
use stock gb rom XEO-KPG from here...u find no bug in it....install as one pakage through odin...
http://galaxy551.wordpress.com/2011/12/20/new-stock-rom-xeo-kpg/
I will give it a try, though i have to clarify and say that on the current stock rom that i'm using (I5510XWKPJ) the problem doesn't happen. It only happens after i flash Cyanogenmod (any version) and persists till i reflash the Stock rom then it disappears again.
EDIT: Forgot to add that this isn't a CM specific bug as it happened also when i tried other roms too (Arkas, Miui,...)
You cannot say that this is a bug bcaz no other mamber of galaxy 551 and even me also not have this kind of problem....
So I think its problem of ur phone...
Sent from my GT-I5510 using xda premium
No change after installing (XEO-KPG) stock rom, the rom itself works fine with no problems, same as the (XWKPJ) I've been using. but as soon as i install CM the bug rears it's ugly head.
priyesh103 said:
You cannot say that this is a bug bcaz no other mamber of galaxy 551 and even me also not have this kind of problem....
So I think its problem of ur phone...
Sent from my GT-I5510 using xda premium
Click to expand...
Click to collapse
The reason i think it's a bug because it happens across lots of custom roms (which rules a rom being the cause) and it never happens when using the 2.3.6 stock roms. And on the custom roms it only happens after the screen has been off for a while, if i set the screen to never turn off for instance it never happens, but that butchers battery life.
IMO it might be a display driver issue, but since i have no experience with it i came here to get some help
Bump, any help would be appreciated.
I am running CyanogenMod 10 nightly 12/26 and for some reason lte is not working. I've looked all over the internet and Havant found anything to fix the solution. Any help would be aporeciated.
xoclutch said:
I am running CyanogenMod 10 nightly 12/26 and for some reason lte is not working. I've looked all over the internet and Havant found anything to fix the solution. Any help would be aporeciated.
Click to expand...
Click to collapse
Well maybe the fact your running a nightly explains it. Those are experimental builds which may have issues, go back to previous nightly or to a stable release I'm sure it will start working again.
Transmitted with a portable device using Xparent Blue Tapatalk 2
I've tried older builds including M1 and M2 and when I do my prl profile update fails giving a 602 error and I can't get online at all. I have updated the radio to FD02 several times after updating the ROM but it does nothing.
hi all just tried to update my cer iconia a700 with cyanogenmod cm 10.1 anyways download it to tablet installed clockwork recovery as well as downloading gapps clicke on mod file and it opened clockwork and i clicked install to install mod/update and now just boots to cyanogenmod on load screen and just sits ther for hours like its loading but nothing happening how to i get back to old rom or even carry on with update i was on 4.1 jb tried to update to 4.2 and yes its rooted sry i am a noob to this thanks in advance
Hello smedzz.
Your device only has experimental and nightlies for Cyanogenmod, with no RC or stable ROMs available. The problem you are experiencing sounds a lot like the problem I had with Cyanogenmod 9.0 for my Samsung Galaxy S i9000. It was a release Candidate (RC), and slightly unstable, and hung up on the boot graphic occasionally. The only way to fix it was to flash the phone again (my experience).
If that sounds like a pain, you could look for a different ROM in the Developer section of the forums for the a700. The "iconiaN 2.6" ROM, based on Jelly Bean 4.1.1, sounds good. At least it would get your tablet working again.
http://forum.xda-developers.com/showthread.php?t=1952124
Already solved?
Did you wipe?
Hello everyone,
I'm posting on here because I can't find any solution to my dilemma which I am sure that other people in the AOSPA legacy community have also experienced. I have been using Paranoid Android on my T989 since the 4.4.3 update and I have regularly updated my roms since then. Somehow ever since I updated my phone to 4.5 beta 3, something prevents me from being able to hear or be heard during regular phone calls around an hour after I restart my phone.
I have tried everything to try to make my phone back to normal, I have updated my versions of AOSPA, I have downgraded to stable versions, I have gone to a debloated stock rom (which worked perfectly fine but who likes touchwiz android 4.1.2?) and back to AOSPA, I tried the latest Carbon nightly rom and the problem persisted, I have wiped my internal memory, cache, davlik, etc. multiple times. I am at a total loss as to what I should do to fix this issue. I'm currently running it on 4.6 beta 1 and I still have the issue.
I really love my GS2 and I don't want to part with it or have it running stock. Please help me.
I really appreciate it,
Chris
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Playnhooky said:
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Click to expand...
Click to collapse
I am also getting this problem on Slim 7.8....must be an audio-caf issue....Can someone go back to an old KK rom (one from earlier months) and see if they experience the same issue? Preferably cyanogenmod
I flashed to stock rom via oden and spent the weekend with the phone and all was good , I flashed to the latest cm-11 with no addons , stock cm-11 kernal and after an hour or so I lost call audio again . We must have done something to the phone in a previous rom cause not many people are having this issue . Now I have flashed about 75 different roms with no issue , I hope someone finds the problem cause I'm not to keen on the stock rom !
I've seen posted that snapchat was the cause of the no call audio problem we are having , I flashed the latest liquid smooth rom last night , download all my apps that I usually do except snapchat and I've had no issues with the calling bug . All is working great .