Related
Hi, I've been searching high and low for others with this problem but here I am starting a thread...
First let me just thank all the devs who worked on this ROM. Your work is very much appreciated.
Is anyone having issues with SMS after flashing EE 2.0.1? I went straight to 2.0.1 no 2.0 first. Seems to be OK except somewhat buggy. Maybe this is why?
Here's the central issue for me so far:
When typing in an SMS text input box with Handcent, screen would go blank/black and just stay like that with no recovery. Could eventually get back to home but message input would be lost . It got so bad I uninstalled Handcent (crying shame, i loved it) and went back to stock SMS (hate it, booo!). Even with that I still have issues though not as frequent. While typing in text box, text box will disappear and I am left looking at the general text thread, but at least when I pull the box back up my message is still there and I can keep going. Happens CONSTANTLY. I am an avid texter and will have to try other ROMS to fix if I cannot resolve. I'm lazy and don't want to do that .
Should I wipe and flash 2.0, then 2.0.1? OR I guess if I'm going to do all that I might as well flash 3.0? Any more conservative suggestions ?
Thanks in advance !!!!!!!!!!!
danacorbin said:
Hi, I've been searching high and low for others with this problem but here I am starting a thread...
First let me just thank all the devs who worked on this ROM. Your work is very much appreciated.
Is anyone having issues with SMS after flashing EE 2.0.1? I went straight to 2.0.1 no 2.0 first. Seems to be OK except somewhat buggy. Maybe this is why?
Here's the central issue for me so far:
When typing in an SMS text input box with Handcent, screen would go blank/black and just stay like that with no recovery. Could eventually get back to home but message input would be lost . It got so bad I uninstalled Handcent (crying shame, i loved it) and went back to stock SMS (hate it, booo!). Even with that I still have issues though not as frequent. While typing in text box, text box will disappear and I am left looking at the general text thread, but at least when I pull the box back up my message is still there and I can keep going. Happens CONSTANTLY. I am an avid texter and will have to try other ROMS to fix if I cannot resolve. I'm lazy and don't want to do that .
Should I wipe and flash 2.0, then 2.0.1? OR I guess if I'm going to do all that I might as well flash 3.0? Any more conservative suggestions ?
Thanks in advance !!!!!!!!!!!
Click to expand...
Click to collapse
i'd suggest going to 3.0, never used it tho. do a nand back up first, and if you don't like it you could always restore back. the update of the rom might fix what ever is causing your issues. i read most of the EE thread, and don't ever recall anything like what you describe. maybe .... you could try uninstall handcent, then reinstall see if it helps any. just might be worth a try.
also you prolly should of posted this in the EE thread. some people around here get pissy when new threads are started.
Evil Eris 2.0.1 is only a flash update to 2.0 - you must have EE2.0 installed first. It also sounds like you didn't do a data wipe before flashing EE either. Personally, I would move to EE3.0 anyways. Framework is working on an update to 3.0 now that will finish the incomplete theme as well.
What g00gl3 said. Do a data wipe (backup first) and flash 3.0 anyways. There'll be a new version of 3.0 out very soon.
I did do a wipe... I'll try 3.0 and see what happens. That's a project for the weekend. BTW, I cannot find the EE thread. Can someone post a link to that? Search is limited in this forum (and I'm new here so maybe it's right in front of me). Thanks for the advice!
It's in the front now, I had a few FC's at first when I flashed it, but after a couple of days it was smooth sailing.
EE Link is in my sig.
Hungry Man said:
EE Link is in my sig.
Click to expand...
Click to collapse
Me too, lolz...
Thanks kindly everyone! Apologies to Mods for the new thread.
Flashed 3.0 yesterday and issue has been resolved, as it mostl likely would had i gone back and instead flashed 2.0 THEN 2.0.1. Anyhoo, LOVE 3,0!!! I especially dig the subtle blue theme (blue battery display, icon backgrounds turn blue when touched, etc). SWEET. Soft key backlights work, runs super smooth. Very nice!
Hey guys....I've had the Glacier for two weeks and I couldn't be happier. I got the OTA 2.2.1 and rooted it without any problems. Then, today I got a "android.process.acore has stopped unexpectedly" only when I go to the phone dialer or contacts. Everything else works perfectly. Earlier today I changed the boot animation and the splash screen...both work flawlessly. I changed the boot animation back to stock and see if that would fix it but no luck. I have rebooted and taken the battery out several times but no go. I checked around and no one else seems to have the same issue. Any suggestions would be greatly appreciated....Thanks in advance.
Edit...I just fixed the problem...I had downloaded a Tmobile voicemail app that was causing a conflict. I uninstalled it and I'm golden again. I appreciate the help. Thanks.
I've had this come up intermittently since rooting, and haven't been able to nail it down to one specific action or app, etc. It's happened since doing perma-root, and doesn't seem to matter if I'm running stock ROM or CM6.1 Alpha (which I flashed last night - had this pop up once or twice since).
It's annoying, but hasn't caused any real problems so far.
Would be nice to figure out why it's happening, and find a resolution.
What apps, if any, have either of you deleted since rooting?
Does it write any useful exception information in the log file?
Sent from my HTC Glacier using XDA App
XfooYen said:
What apps, if any, have either of you deleted since rooting?
Click to expand...
Click to collapse
I haven't deleted any apps...just hid them under general settings using Launcher Pro...the only other thing I did different today was unlock the SIM using the code Tmobile sent me but I can't imagine that has anything to do with it....Just can't access the Phone at all or the Contacts without a force close...I'm stumped...
Trying to figure out a good way to upload a log file...
I think it might have something to do with permissions..it said among other things...
W/dalvikvm*3381):Refusing to reopen boot DEX'/system/framework/com.htc.android.pimlib.jar
not sure what that means....
Please post questions in Q&A section.
Yep, I'm having the same issue. It does it when I'm using a few applications like Twidroid, even ChompSMS, and another one. I'm thinking it has less to do with what applications I'm using at that time (meaning it would do it no matter what application I had open) but those 2 I use 95% of my time on the phone.
& I as well have not deleted any applications only freezed them with Titanium Backup Pro.
I don't know if I'm the only one to notice this, but every. single. rom. after HKTW has been an asbolutely lag fest on when using your finger for 'slide to unlock'. When I first isntalled HKTW I was so satisfied and exclaimed "FINALLY, SMOOTH UNLOCK BAR GOODNESS".
Unfortunately this glee was not met with any custom roms based on source code since. I dunno what happened. I never noticed any improvements anywhere else in phone usability besides the lockscreen between these roms and I'm just hoping someone has an answer or knows what I'm talking about.
Alien rom - No dice
Cherry pi - no dice
CM7 - sad to say, no dice. However has the most utility out of all the other roms available which is amazing.
Widget locker doesn't help. Silly tricks from droid X2 (who has the same problems but managed to fix somehow..) don't help. Removing blur (CM7 does this right?) didn't do anything. I'm really confused what else can cause this dual core DUAL CORE PHONE to perform so horrendously on the basic basic of tasks: swipe to unlock.
I apologize if this sounded angry, I just want someone to feel my pain.
Novancaiel said:
I don't know if I'm the only one to notice this, but every. single. rom. after HKTW has been an asbolutely lag fest on when using your finger for 'slide to unlock'. When I first isntalled HKTW I was so satisfied and exclaimed "FINALLY, SMOOTH UNLOCK BAR GOODNESS".
Unfortunately this glee was not met with any custom roms based on source code since. I dunno what happened. I never noticed any improvements anywhere else in phone usability besides the lockscreen between these roms and I'm just hoping someone has an answer or knows what I'm talking about.
Alien rom - No dice
Cherry pi - no dice
CM7 - sad to say, no dice. However has the most utility out of all the other roms available which is amazing.
Widget locker doesn't help. Silly tricks from droid X2 (who has the same problems but managed to fix somehow..) don't help. Removing blur (CM7 does this right?) didn't do anything. I'm really confused what else can cause this dual core DUAL CORE PHONE to perform so horrendously on the basic basic of tasks: swipe to unlock.
I apologize if this sounded angry, I just want someone to feel my pain.
Click to expand...
Click to collapse
I don't feel your pain. My lock screen unlocks at a 1000fps. Almost too smooth, on Cyanogenmod!
I've rarely seen any lockscreen lag either..and when I did it was usually from SetCpu being too low for Screen Off. The only constant in your scenario (multiple ROM's) is your phone..which probably has something on it (app) interacting with it funny would be my guess..
This is EXCELLENT news then!
As far as I know there are no apps running that create this issue. (to my limited knowledge of course!) symptoms are felt on fresh wipe and install of any rom BUT HKTW.
Is there a deeper wipe I can use on the phone to ensure every byte of data is completely ERADICATED before installing cyanogenmod? I'm willing to try anything except taking her back to the store.
Apologies for my enthusiam.
Novancaiel said:
This is EXCELLENT news then!
As far as I know there are no apps running that create this issue. (to my limited knowledge of course!) symptoms are felt on fresh wipe and install of any rom BUT HKTW.
Is there a deeper wipe I can use on the phone to ensure every byte of data is completely ERADICATED before installing cyanogenmod? I'm willing to try anything except taking her back to the store.
Apologies for my enthusiam.
Click to expand...
Click to collapse
"fastboot erase system -w" I believe will do a much better wipe than just doing it thru CWM. Someone please correct me if i'm wrong though..
Here's a link with more info:
http://forum.xda-developers.com/showthread.php?t=619153
At work so fastboot isn't an option. I'll update when I get home though.
Thanks for help so far!
If cm7 rotary revamp isn't smooth, neither is the iPhones unlock slider. I have absolutely no lag on my end.
Sent from my MB860 using XDA Premium App
Rickroller said:
"fastboot erase system -w" I believe will do a much better wipe than just doing it thru CWM. Someone please correct me if i'm wrong though..
Here's a link with more info:
http://forum.xda-developers.com/showthread.php?t=619153
Click to expand...
Click to collapse
thanks for that....was unaware that this is a better way
Yea switch to cm7. No lag anywhere.
Sent from my cm7 Atrix
Update:
Fastboot wipe didn't help me at all. I installed Alien 4 today and no joy.
Went back to HKTW and everything is working the way I expect it to.
I have to be doing something wrong, no way this super duper beta software is more stable for me than all the other roms. I've been using Navalynt's HKTW rollup fix mod.
Is it kernel related possibly? I'm so curious I want to start developing just to see if there's a major difference..
I am using Pi-Cust and I too had lag with the stock lockscreen but with widget locker, I see no lag what so ever. I tried beta 1 of CM7 and I didn't see any lag in the lockscreen there either. It is definitely a blur thing. If you use Widget locker, make sure you disable the stock lockscreen though.
HKTW Gives no lag with stock lockscreen. All other roms show no difference between widget locker and stock lockscreen besides the utilitiy the app gives (widgets on lockscreen, custom slider etc). I'm sure blur can be an issue but I'm not experiencing any, I just installed HKTW and everything works perfectly. =\ I skipped blur setup as usual and have no problems..
Update:
Installed Faux123's kernel and it broke everything. I get the feeling I'm the only person interested in this (maybe not many people have tried HKTW?)
Incase anyone is.. Here is the rom I'm using.
http://forum.xda-developers.com/showthread.php?t=1142674
however it bootloops if you install it over CM7. I installed Alien 4 and then HKTW on top to stabilize. If you full wipe like usual and install HKTW it bootloops. =\
If it helps, when HKTW was first released I used the fastboot method of install. Not sure if that clues anyone into my issue or not.
my Iconia (always more often) flashes in the launcher, flickers and most of the times everything disappear apart the wallpaper...
i have used apex, nova, trebuchet, holo... all (before or later) start flickering and then die... only way out is to kill the launcher or start another one somehow.
my rom is reflexxx stryker rev 4.2 (but i also used cm9 and had some problem)
i have ics bootloader, but i can't say what version, sorry
i have seen some posts about this problem,
most common idea is that the problem is in the ics bootloader.
the only idea of a solution was to go back to honeycomb BL
but those posts i saw where almost 2 months old... so i wanted to ask:
are there any new solution about this? any new hints? any new ideas?
it is also difficult to search about this on the forum.. since i don't know exactly what to search
thanks anyone for any hint.
loth77 said:
my Iconia (always more often) flashes in the launcher, flickers and most of the times everything disappear apart the wallpaper...
i have used apex, nova, trebuchet, holo... all (before or later) start flickering and then die... only way out is to kill the launcher or start another one somehow.
my rom is reflexxx stryker rev 4.2 (but i also used cm9 and had some problem)
i have ics bootloader, but i can't say what version, sorry
i have seen some posts about this problem,
most common idea is that the problem is in the ics bootloader.
the only idea of a solution was to go back to honeycomb BL
but those posts i saw where almost 2 months old... so i wanted to ask:
are there any new solution about this? any new hints? any new ideas?
it is also difficult to search about this on the forum.. since i don't know exactly what to search
thanks anyone for any hint.
Click to expand...
Click to collapse
As far as I know there is no fix. I've tried many different roms and bootloaders as well as MANY launchers. The only way that I have been able to tone it down is to not use Google widgets. But even then when I play something that uses 3d graphics it may still trigger. I've taken logcats and it says something about some sort of video error, researched it a little and found nothing. I hope that someone has a solution.
JdgM3NT4L said:
As far as I know there is no fix. I've tried many different roms and bootloaders as well as MANY launchers. The only way that I have been able to tone it down is to not use Google widgets. But even then when I play something that uses 3d graphics it may still trigger. I've taken logcats and it says something about some sort of video error, researched it a little and found nothing. I hope that someone has a solution.
Click to expand...
Click to collapse
i tried to use less widgets... but doesn't really change much...
it is very random, but in my experience it appears more often when battery is low
do you feel the same?
i hope it can be fixed, i'm seriously thinking to sell it because of that (but who will buy it..?)
loth77 said:
i tried to use less widgets... but doesn't really change much...
it is very random, but in my experience it appears more often when battery is low
do you feel the same?
i hope it can be fixed, i'm seriously thinking to sell it because of that (but who will buy it..?)
Click to expand...
Click to collapse
Don't sell it, just flash stock. I tried them all and had problems. Stock for me run's with no problems and the fastest just give it a try and you won't look back.
shaun298 said:
Don't sell it, just flash stock. I tried them all and had problems. Stock for me run's with no problems and the fastest just give it a try and you won't look back.
Click to expand...
Click to collapse
I went stock for a while and it was noticeably less often, I still had the issue. Especially when playing Great Little War Game. So I just went back to an overclocked rom. I enjoy the performance more than I regret the flashing screen...
as i wrote to JdgM3NT4L in a pm:
my "solution" is to put a home switcher app shortcut in the lockscreen.
so that when it happens i can kill apex or switch to nova
i mirrored my settings in apex and nova (nova can import all apex settings automatically)
that's the way i survive this boring bug
if someone like the "solution" can try it
and maybe hit thanks button
JdgM3NT4L said:
I went stock for a while and it was noticeably less often, I still had the issue. Especially when playing Great Little War Game. So I just went back to an overclocked rom. I enjoy the performance more than I regret the flashing screen...
Click to expand...
Click to collapse
Did you go full stock no unlocked bootloader..? Not just run a stock rom.
shaun298 said:
Did you go full stock no unlocked bootloader..? Not just run a stock rom.
Click to expand...
Click to collapse
I actually did the rollback to 3.1, updated officially over the air all the way up. Complete stock. It was better, but the issue persisted.
Loth, I have not noticed if the charge had much effect, But one thing that I think that seems to trigger it is when there is a game/app going that is using 3d graphics, and then any sort of notification pops up as an overlay. There is one rom that I could get it to do this almost on command. I could have a game going and the check the notifications. 80% of the time that was enough to get the flashing started.
So perhaps what you've noticed could be triggered by the low battery popup?
I can say that the latest Flexreaper ShellSHOCK does this very rarely. Maybe three times in the last few weeks, and I play with the tablet a lot.
JdgM3NT4L said:
I actually did the rollback to 3.1, updated officially over the air all the way up. Complete stock. It was better, but the issue persisted.
Loth, I have not noticed if the charge had much effect, But one thing that I think that seems to trigger it is when there is a game/app going that is using 3d graphics, and then any sort of notification pops up as an overlay. There is one rom that I could get it to do this almost on command. I could have a game going and the check the notifications. 80% of the time that was enough to get the flashing started.
So perhaps what you've noticed could be triggered by the low battery popup?
I can say that the latest Flexreaper ShellSHOCK does this very rarely. Maybe three times in the last few weeks, and I play with the tablet a lot.
Click to expand...
Click to collapse
i installed latest shellshock, let's see
It happens to me all the time with all the launchers I 've tried. I am in unlocked ics bootloader and stock rom. The same happened with the locked bootloader. I tried the CM10 Rom same results. I removed all widgets from the homescreen with no luck.
If it's in the ICS Bootloader then all must have the same problem or not?
Any solution except going back to 3.2?
To fix it I had to go full stock to Honey Comb then reinstall CWM then install Thor cm v15 and no problems since. I think the problem is the ICS bootloader
After some good times with few troubles, now it is again a huge problem: i almost can't use the tablet it happens every day and more than once.
I think I'll go back to stock honeycomb
Sent from a GalaxyS2 far away with Amiga 1200
Hey, @houstonn! Everyone,
First, I've really wanted to thank you for the longest for all the work you've put in for for all LGG2 variants. I've been with you from the beginning, the quiet kid at the back of the class without the ten notches to do anything other than click Thanks! But it's been awesome. Even getting myself out of some sticky situations alone has tested my metal. It's a good thing I like to read.
K. More adulation later. Just have wanted to make note of something that I haven't ever seen throughout the PA thread concerning the d801 from the 12/24 build to present working 12/31. Don't wanna bring you more headaches after reading about v.01/03, but I'm hoping you or someone can verify an issue I've been experiencing on the three latest builds.
I can clean install PA using TWRP 2.6.3.4 Do so always as with the 2day 12/27 skin I was wearing until dirty flashing the 12/31 just now. Upon initial boot everything is spot on. I'll have already flashed my backup apps post gapps and be setting up, Google Now and offline voice recognition downloaed then set to auto update. Google Now will work hands free for a good while so I can't be exact about the interval between it working and losing the prompt in the Search box, which in turn leads to SMS fails in both stock messaging and Hangouts. I still receive SMS via both apps, but my sends fail every time after something 'breaks'.
I did notice something yesterday while running forensics. I switched Hangouts to batch MMS mode and texted to one party and pinged myself as well. So Hangouts/Messaging only works in MMS mode for me. I've yet to read this anywhere in the novel that is your thread and I do read, so correct me if this has been addressed. I checked App Ops and found the SMS send set to off in Stock Messaging but everything on in Hangouts, but figured that had to be the cause or Hangouts' doing by default since both apps must use the same broadcast intent, thus why both don't audibly run at once. It's really the only problem I have but it seemed strangely obscure enough to mention. I can't think of a possible cause or a way to track it other than running a log. Fall short of doing so cuz I have another phone running custom KK 4.4.2 and I have no problems messaging with it. As for Google Now and voice Recog, when I go back into language settings, my alternate languages will have disappeared until I toggle back and forth between 'when to update' and 'available to DL languages'. By then, English UK (US), French & Spanish have repopulated the downloaded field, yet hands free voice recog fails.
Otherwise, no other errors. I freakin love this ROM and with UV/OC, I'm maxing out some lengthy battery life upwards of 14 hours with screen on for 8 out of the whole! Yea, I'm on it feverishly but who can blame me. It's wicked smooth and you're awesome!!!
Thanks heaps!
tinydynamite00
--- Anyone else having experienced this, elaborations or recommended fixes welcome. Thx!
There is PA Q&A thread already..
Sent from my LG-D802 using xda app-developers app
Sean473 said:
There is PA Q&A thread already..
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, if it is a problem having my post here under the labeled Q&A thread for my device, I understand if you need to move it. As I really had a minute issue and was unable to post directly to the PA forum at the time, searched and evidently missed the thread you mentioned, I saw no problem in posting under the General device specific Q&A. Thanks for the correction. I'll be more thorough in searching next time.