Anyone else with 2.2.1 have fc's on sounds? - Epic 4G General

Hi, i installed this version of Froyo: http://forum.xda-developers.com/showthread.php?t=861220
All of a sudden my sounds don't play from anything with a notification including calls. If i go into any notification sound to choose a ringtone, it locks up, vibrates 3 times and fc's.
Anyone else have this issue?
This is the 2nd time i have experienced this flashing Froyo. Would a custom Froyo ROM correct this, or any other suggestions, or am i forced to go back to 2.1?
Thanks...

Have you removed the DRM apk's? if you have, this caused exactly what you described for me- and saw it was because I had removed them (after reading thru logcats). If so, push them back, or reflash the rom.
I still kill the process after start up, but keep them installed.
sent from my RAZR

I did, i'll try restoring them and report back.

If you copy/push em back, just make sure to fix the permissions as well to match those in the system/app folder.
sent from my RAZR

I didn't see your comment on permissions, so i ended up reflashing, but now it's working.
Thanks!

Please post questions in General Section.

Truedat- I started a thread on this topic in general a few weeks ago. I'll link it if this thread doesn't go bye bye before then
sent from my RAZR

Related

gapps/google talk/market/acore crashing/not working

Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App

[Q] SyndicateROM 2.2 frozen ROM issues

Just installed this ROM and as before, all previous Syndicate roms were amazing! But this one has a few issues id like to question. Biggest problem is when i turn my Epic off, it wont charge. It stalls at the battery loading screen. It just shows the "working icon" and doesn't go away. I have to pull the battery. Perhaps this isn't the rom, but i've never had this issue until now.
Second thing, a FC for "gapps" keeps coming up. Dunno why, never did before, perhaps a re-flash of the ROM would fix it. It's just a pain setting everything up over and over.
If anyone could help, I couldn't post this to the ROMs Specific thread because i'm a noob and havent posted 10 times yet, so here i am. Thank you in advance for all your help and knowledge.
-Cman
cman1084 said:
Just installed this ROM and as before, all previous Syndicate roms were amazing! But this one has a few issues id like to question. Biggest problem is when i turn my Epic off, it wont charge. It stalls at the battery loading screen. It just shows the "working icon" and doesn't go away. I have to pull the battery. Perhaps this isn't the rom, but i've never had this issue until now.
Second thing, a FC for "gapps" keeps coming up. Dunno why, never did before, perhaps a re-flash of the ROM would fix it. It's just a pain setting everything up over and over.
If anyone could help, I couldn't post this to the ROMs Specific thread because i'm a noob and havent posted 10 times yet, so here i am. Thank you in advance for all your help and knowledge.
-Cman
Click to expand...
Click to collapse
The battery issue is an issue with CWM3.0.6... so i was told. So it isn't rom related. As for the gapps, I don't think they have made a gapps yet for this rom...
I'm sure you would find better support for your questions in the ACS thread
Sent from my SPH-D700 using XDA App
Roam Control
I have Flashed this ROM from supernova didn't like the battery drain so I wiped and went back to where I was before with my nandroid back up but Kernal was still stuck on twilight. I then reflashed this rom after using the samsung odin to get back to stock then the one click root from AC where you can keep data phone frooze on samsung re-odined from the ROM's OP to get CW3 and ext4. wiped 3x and flashed got a bad flash rewiped and flashed and it's finally working kind of.
I am in a place where we have no sprint 3G which is fine as @home in on wifi. Android market doesn't work unless on wifi. when off wifi it always says it looses connection or needs a connection (this never happened on any other rom I've ran before) it is way slower if I ever do get to download anything. Also other apps such as world war say I have no connection half the time as well. I used to use Roam Control from the market to get better service as I get zero in the office with sprint but now I can't even get that to work everytime I try and hit roam in the app it says to purchase from the market when I already have.
As i previously mentioned wasn't happy with the battery drain. so I have tried re downloading the zip for ROM and the new twilight fix. still losing a percent or 2 every 15-20 min seems pretty big drain compared to the supernova I was running and the midnight 4.1 before that. any help would be awesome. I wish I could put this in the ROM's thread but this is only my first post on xda. not a fan of that rule.
Re-download and reflash. Be sure to wipe 3x before doing so!
They are offering live support in their IRC.
irc.droid-life.com #acs-users
Gapps is baked in the rom, and I'm gonna try and reinstall everything. Ill post again with my experience.
Sent from my SPH-D700 using XDA App
If you are having issues, then I would suggest doing EB13 + EXT4 with ODIN and then doing a fresh install. The rom has been nothing but stable for me. And if you use titanium backup or some other type of app restoration then I would suggest only restoring apps with data in only the apps you really need. Otherwise you are going to run into trouble.
stormglove said:
I have Flashed this ROM from supernova didn't like the battery drain so I wiped and went back to where I was before with my nandroid back up but Kernal was still stuck on twilight. I then reflashed this rom after using the samsung odin to get back to stock then the one click root from AC where you can keep data phone frooze on samsung re-odined from the ROM's OP to get CW3 and ext4. wiped 3x and flashed got a bad flash rewiped and flashed and it's finally working kind of.
I am in a place where we have no sprint 3G which is fine as @home in on wifi. Android market doesn't work unless on wifi. when off wifi it always says it looses connection or needs a connection (this never happened on any other rom I've ran before) it is way slower if I ever do get to download anything. Also other apps such as world war say I have no connection half the time as well. I used to use Roam Control from the market to get better service as I get zero in the office with sprint but now I can't even get that to work everytime I try and hit roam in the app it says to purchase from the market when I already have.
As i previously mentioned wasn't happy with the battery drain. so I have tried re downloading the zip for ROM and the new twilight fix. still losing a percent or 2 every 15-20 min seems pretty big drain compared to the supernova I was running and the midnight 4.1 before that. any help would be awesome. I wish I could put this in the ROM's thread but this is only my first post on xda. not a fan of that rule.
Click to expand...
Click to collapse
Can you try a fresh uninstall and re-install of Roam Control through the market? Then just make sure you have a signal the first time you change the roaming mode. Send me an email at roamcontrol (at) gmail (dot) com with any questions. Thanks!
Ok so, using CWM, I just wiped and cleared the cache a bunch of times. Not all gapps were there. Just market and contacts. I had to install gmail, search and others. I'm not getting ANY FC's. Its smooth as butter now. Now to fix the battery lock up problem. Is there a EB13 tar with the EXT4 CWM included? I'm sure someone has done it by now. Plus, this is the first version of the 2.2 rom. It can only get better. Thanks for your help fellas.
Sent from my Futuristic Device That You Don't Have
xxmastermindxx said:
They are offering live support in their IRC.
irc.droid-life.com #acs-users
Click to expand...
Click to collapse
Thanks for the info on that chat help. I talked to them a bit consensus is another odin, wipe, and flash . I've tried so many times already i'm starting to get frustrated, oh well, all part of the experience right. I just got home so we'll see with new downloads of all files I can get this baby running.
Hi guys thanks for the awesome ROM
I just wanted to mention I am having the same email issue with my IMPAP AOL account, at first I was using IMAP SSL 993, I deleted the account and readded standard IMAP 143 and I am having same problem. I know you guys are aware of the email issue, I just wanted to share this info with you.
Before I installed this ROM I used ES File Explorer to copy my Angry Birds highscores.lua file to SD card and then to my computer. After installing this ROM I installed Angry Birds and it was working fine, then I installed ES File Explorer. I copied back my highscores.lua file back to the correct directory. Angry Birds started crashing after this whenever I cleared a level. It turns out the file I copied back was not writeable, so I installed Terminal Emulator and did a chmod to the highscores.lua to make it writeable, and now it works fine.
When I was on stock EBE13 my TWS was 51% I was able to fix this by changing my Mobile network from Automatic to Sprint Only and then it went to 2%. I am using this on Boost Mobile so I dont think I can Roam anyway. On this ROM my TWS is 50%, changing to Sprint Only has no affect on this, and I tried toggeling Airplane Mode on and off and it did not seem to help.
Once again thanks for this superfast ROM
cman1084 said:
Ok so, using CWM, I just wiped and cleared the cache a bunch of times. Not all gapps were there. Just market and contacts. I had to install gmail, search and others. I'm not getting ANY FC's. Its smooth as butter now. Now to fix the battery lock up problem. Is there a EB13 tar with the EXT4 CWM included? I'm sure someone has done it by now. Plus, this is the first version of the 2.2 rom. It can only get better. Thanks for your help fellas.
Sent from my Futuristic Device That You Don't Have
Click to expand...
Click to collapse
it was answered in post #2, the battery lockup is an issue with CWM 3.x.x. It was also posted numerous times in the Syndicate ROM thread. I'm getting tired of reading about it.
cavrac said:
Hi guys thanks for the awesome ROM
I just wanted to mention I am having the same email issue with my IMPAP AOL account, at first I was using IMAP SSL 993, I deleted the account and readded standard IMAP 143 and I am having same problem. I know you guys are aware of the email issue, I just wanted to share this info with you.
Before I installed this ROM I used ES File Explorer to copy my Angry Birds highscores.lua file to SD card and then to my computer. After installing this ROM I installed Angry Birds and it was working fine, then I installed ES File Explorer. I copied back my highscores.lua file back to the correct directory. Angry Birds started crashing after this whenever I cleared a level. It turns out the file I copied back was not writeable, so I installed Terminal Emulator and did a chmod to the highscores.lua to make it writeable, and now it works fine.
When I was on stock EBE13 my TWS was 51% I was able to fix this by changing my Mobile network from Automatic to Sprint Only and then it went to 2%. I am using this on Boost Mobile so I dont think I can Roam anyway. On this ROM my TWS is 50%, changing to Sprint Only has no affect on this, and I tried toggeling Airplane Mode on and off and it did not seem to help.
Once again thanks for this superfast ROM
Click to expand...
Click to collapse
They know about the email issue and are working on it.
Not sure about the angry birds issue sorry.
for the TWS issue I still do the airplane mode toggle to fix that. unfortunately I think that will be necessary forever, I see you've tried it already but try from a fresh reboot right away and see if that works and also I've heard of some having to toggle a couple times before it working. after a reboot I just toggle 3 times just to be safe. I have not found a rom that solves this issue. That's weird that changing to sprint only helped I have never tried that nor heard of anyone who has. I'd give it a shot but I use roam control at work so maybe i'll see if it works this weekend when I'm not at work.
I hope it works out for you, I don't know too much but hope i helped somewhat. have a good one.
I was able to fix Echange email issue by replacing Email.apk with the file from this thread.
http://forum.xda-developers.com/showthread.php?t=775007
Is anyone else having an issue with call volume? I just made my first phone call since flashing this ROM and I could barely hear the person on the other end despite having the volume up as loud as it would go.
Is there a fix for this? If so, can someone point me to it?

Too many issues so few roms

3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?

Gingerbread 2.3 problems.

Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Frosty1148 said:
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Click to expand...
Click to collapse
Maybe it's a bug in the ROM
Try different rom and see if this problem still persists, if yes, maybe a hardware problem related issue
Cheers
There are a few roms with 100% support for the official extended batteries(s). Your best bet is to go with one of them.
Sent from my HD2 using XDA App

[Q] (Q) Screen stays on when I miss phone call or msg

Hello.
I posted the question in the Q & A thread but I fear my question got lost in between the many that are asked.
I own a rooted S4 from Rogers Canada, which used to be on Alpha Infamous rom, an old version like the 5.0 from at least 6 months ago. Everything runned fine until recently. The phone started giving me some trouble. After missing a phone call while I didn't had the phone on me, the screen stayed on showing missed call until I happened to see the phone and pressing power to close it. The same started happening with message at about the same time.
Since I thought I might have installed a dumb apk on gplay that messed something in the settings, I went to get a new Rom. Alpha having no development for a long time, I thought I'd try something else.
I have tried both omega v25 and [23/03][4.4.2][XXUFNBH]< Echoe v18 > [07/02][4.3][NA4]< Echoe v12.1 "The Final Bean">, the latest which I run at the moment. Both gave me the same trouble with the screen staying powered after missing a msg or a phone call.
Since I don't know how to fix it, I was wondering if anyone could help me out ?
I'm no pro at rooting/flashing but I did the wipe dalvik, cache and everything before flashing both of the new rom. I didn't update the bootloader as I didn't remember clearly how or if it was necessary but the rom in general runs great so I figured out it was ok this way. The only trouble I have is with the screen as previously stated. I didn't flashed the modem either as I seem to have great download speed (without testing, simply feeling it).
So as of now, I'm running Echoe V18 with most of the bloatware disabled in aroma installer.
What can I do to fix this? I've tried googling but nothing close to my trouble came as result. Neither could I find an answer here, there's so many result I might have simply missed it.
Thanks for the help!
Laethageal
Anyone's able to help out ? My question is getting phased out but still has no answer. Please ?

Categories

Resources