This has been an issue for me in 4.3 or any 4.3 ROM with the AOSP messaging app. I'm getting extremely tired of it freezing up my whole phone for 10 seconds at a time. Is there seriously no way to fix this awful issue?
BravoMotorola said:
This has been an issue for me in 4.3 or any 4.3 ROM with the AOSP messaging app. I'm getting extremely tired of it freezing up my whole phone for 10 seconds at a time. Is there seriously no way to fix this awful issue?
Click to expand...
Click to collapse
My recent cm 10.2 builds are doing this since last week.. Hopefully its something they are aware of .. getting annoying. At first I thought it was my Swype but it happens on other keyboards as well..
Thank God i am not the only one that experience this. I have had that freeze three times already. Twice last week and once yesterday. This morning my phone rebooted by itself for the first time since running any CM10.X. I hope this is a bug that will be crushed in the next few builds.
cenwesi said:
Thank God i am not the only one that experience this. I have had that freeze three times already. Twice last week and once yesterday. This morning my phone rebooted by itself for the first time since running any CM10.X. I hope this is a bug that will be crushed in the next few builds.
Click to expand...
Click to collapse
I've had it for so long, I'm not sure if anyones on it to fix the problem or not. I'm actually thinking its a general 4.3 bug not just a CM10.2 bug.
You are right. It's a deadlock on all JSS builds used in cm 10.2
Sent from my Nexus 4 using xda app-developers app
seriousneo said:
You are right. It's a deadlock on all JSS builds used in cm 10.2
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
So do you why this happens? Should it really be that hard of a fix?
BravoMotorola said:
So do you why this happens? Should it really be that hard of a fix?
Click to expand...
Click to collapse
The problem is in the AOSP source. The fix has to come from Google. We won't see it soon, as Google is working on 4.4 now.
Until then, try JWR/JSS hybrids. They don't have deadlocks.
Related
Hey I got a nexus s a week ago and noticed it was a little stuttery at times going in and out of apps,so I got an exchange ..new one does same thing,went to 3 different bestbuys all there demo phones did the same...my question? Who else notice this lag or stuttering opening and closing apps,note launcher and home screen is smooth...
Sent from my Nexus S using XDA App
Yeah I notice a stutter on mine especially when loading and closing apps, but compared to my old hero this thing flies.
Sent from my Nexus S using XDA App
Mine does all of the above and sometimes freezes in between a home screen, like 5o 5o% and the apps from the app free drawer never come up
~Sent from my Nexus S with Swype~
Highly recommend if you're rooted to use CM7 nightly very smooth all around over stock and any other custom ROM out now for NS
Yea am thinking about just rooting it,was gonna wait and see what updates Google was going to release, but I'm not very patient
Sent from my Nexus S using XDA App
Raver27 said:
Yea am thinking about just rooting it,was gonna wait and see what updates Google was going to release, but I'm not very patient
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
2.4 should be out in couple months but i think next update we are getting just resolves issues when making phone calls. But yea CM7 nightly is very good i dont usually advertise what rom i like best but if you noticed i have it on my SIG...IMO its that good not to mention you get a rom update every night and no need to wipe after every update they just update over each other so very convenient
And you can always unroot and relock your boot loader if you have to return your phone for any reason Ive returned 2 phones with no problems.
Welcome to Gingerbread, home of the glitch-train. Population: us.
Hey I got a nexus s a week ago and noticed it was a little stuttery at times going in and out of apps,so I got an exchange ..new one does same thing,went to 3 different bestbuys all there demo phones did the same...my question? Who else notice this lag or stuttering opening and closing apps,note launcher and home screen is smooth...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
This is just the beginning... welcome to the GB beta testers club.
Sent from my Nexus S using XDA App
Well this thing would eat my old hero for lunch when it comes to speed. So I'm not really complaining.
There is only a little bit of stuttering every now and again.
I've had it for about a week now and it has been flawless on stock. I've had one random restart.
This is seriously the best android phone I have ever owned. Im so ****ing satisfied with my purchase.
Sent from my Nexus S using XDA App
Zardos66 said:
I've had it for about a week now and it has been flawless on stock. I've had one random restart.
This is seriously the best android phone I have ever owned. Im so ****ing satisfied with my purchase.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yes, I had it about three days and did not have any random reboot or lags. I'm on stock OS too. I just had one 3G disconnection but that's pretty much about it. I had to reboot and it was back to normal.
It's very smooth and I feel glad that I switched from WM 6.5!
Install the app "OS Monitor" from the Market and check if the "init" process is using a constant 100% cpu.
This is a known bug that affects some Android devices. The fix is to enable the USB Debugging mode in Options -> Application -> Developer.
I have been on the cm7 RC for about a month now. However its really not running optimally. I getting tired of the naggs. So I nandroid restored to my backup to cm6. Man what a difference. It's so much smoother. I know cm7 is not complete yet but froyo is still runs very well. Any of you guys feel the samek? Who is still rocking froyo?
Sent from my Nexus One using XDA App
Nope. Not here. Still on rc2 and I'd say its stable enough. I didn't think cyanogen would even go this far on rc.
Edit: I've found one unstable thing on my n1. The sense preview lags and choppy.
Sent from my Nexus One using XDA App
Yes froyo is miles smoother than cm7 and ginger bread stock. Scrolling apps, lists, webpages, everything is by far smoother on froyo. Makes a tough decision which ROM I want to run:-(
Cm7 rc4 has been as smooth as any 2.2 rom I've tried...now only if battery life was better than 10 hours I'd say it was perfect.
Sent from my Nexus One using XDA Premium App
TheSneakerWhore said:
Cm7 rc4 has been as smooth as any 2.2 rom I've tried...now only if battery life was better than 10 hours I'd say it was perfect.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
whorelando florida hahahaha! sorry but i just had to laugh at this because it is so true...
I'm going to Disneyworld!
Seriously, I have stayed of CM7 for now, since they haven't resolved the call wonkiness issue. I'll wait for CM7 final, or even 7.1. 6.1 is rock solid and by far the best ROM I have used in a loooong time. NO gingerbread for me yet. Stability first.
mr_raider said:
I'm going to Disneyworld!
Seriously, I have stayed of CM7 for now, since they haven't resolved the call wonkiness issue. I'll wait for CM7 final, or even 7.1. 6.1 is rock solid and by far the best ROM I have used in a loooong time. NO gingerbread for me yet. Stability first.
Click to expand...
Click to collapse
RC4 fixed my wonk issue but even on RC2, Dewonkificator solved the issue anyways.
JHaste said:
whorelando florida hahahaha! sorry but i just had to laugh at this because it is so true...
Click to expand...
Click to collapse
Pretty much sums it up.
TheSneakerWhore said:
Cm7 rc4 has been as smooth as any 2.2 rom I've tried...now only if battery life was better than 10 hours I'd say it was perfect.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
i find cm7 RC4 to be extremely good on battery. i can go 12 hours and still be at 60% rather easily. but i just find RC4 laggy and choppy. try loading a tapatalk thread with 30 posts, and scroll that sucker. now try it on froyo, its like a totally different phone, one's smooth, one's chunky as hell.
Battery life sux. But loading huge threads and fora is not a problem at all for me. Everything is snappy and awesome.
Sent from my Nexus One using XDA Premium App
I'm on cm 6.1.1. It's the best rom I've ever seen. I tried cm7, but with a lot of wonks, it was unusable...
Sent from my Nexus One using XDA App
People face choppy scrolling because they don't wipe properly when coming to a new rom. Its a know fact that when you switch a rom, you've to wipe atleast 3 times before flashing the new .zip.
This is simply because, 80% of the first wipe doesn't wipe at all. ( both Amon_RA and CWR)
Always wipe 3-4 times and you'll never face the choppiness issue on any CM Roms.
Sent from my Nexus One using XDA Premium App
Got tired of plain Android and CM7 wonks and other CM7/GB bugs, and tried Sense-based Froyo. What a difference. Going to stay there until (hopefully) a fully functional Sense GB port will be out.
What's the most stable Sense UI ROM?
eViL's NXSense 1.26. It's the only fully functional Sense ROM, unfortunately.
If you don't mind not having native hotspot capabilities - you can also install Desire HD ports (MM SuperHybrid 1.7 and eViL's 1.1beta).
siddharthsai said:
People face choppy scrolling because they don't wipe properly when coming to a new rom. Its a know fact that when you switch a rom, you've to wipe atleast 3 times before flashing the new .zip.
This is simply because, 80% of the first wipe doesn't wipe at all. ( both Amon_RA and CWR)
Always wipe 3-4 times and you'll never face the choppiness issue on any CM Roms.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
but i have wiped 3 times...i just dont know what else to do. cm6 is smooth as butter, cm7 is chunky and choppy.
RogerPodacter said:
but i have wiped 3 times...i just dont know what else to do. cm6 is smooth as butter, cm7 is chunky and choppy.
Click to expand...
Click to collapse
I've always experienced lag when using adw launcher that comes with CM. Try giving launcher pro a go if you haven't. It made a difference for me.
Mokurex said:
I've always experienced lag when using adw launcher that comes with CM. Try giving launcher pro a go if you haven't. It made a difference for me.
Click to expand...
Click to collapse
i use launcher pro exclusively for the last 10 months or so...paid version. it is smoother for sure. but my scroll issues are ont necessarily home screen related. load any tapatalk thread, and it scrolls in chunks. handcent text items in a long list scrolls in chunks.
another bug in cm7, if you have battery text shown in the status bar, once you plug in to charge, after 20 minutes the homescreens become super laggy and skip. this continues until charge is complete, or you unplug. or if you turn off the percent text, scroll returns to normal smooth. i looked at the source code, and this new implementation is different than cm6 battery percent text version. seems using broadcast receivers, etc, or possibly the animation speed, is causing this issue.
i may edit the source to turn off batt percent when plugged in, since that's how cm6 functioned, and see if that fixes it. but i've been lazy pulling down the source.
Latest nightly fixes battery issue.
Sent from my Nexus One using XDA Premium App
>Latest nightly fixes battery issue.
interesting - what was it?, is there a thread that discusses the fixed issue? would be worth rooting for, i'm on stock gb and was thinking of going back to froyo cuz of battery issues.
Running CM7 nightly 41 with dalingrin's 418c kernel. Every time I attempt to view a profile, the Facebook app will crash. I've tried to reinstall and fix permissions / reboot, but to no avail. Anyone else having this problem?
Happened on my Galaxy S too, so I think the release is bad. A clear of Facebook cache and reboot seems to have fixed it.
Sent from my SAMSUNG-SGH-I897 using XDA App
jpeg42 said:
Happened on my Galaxy S too, so I think the release is bad. A clear of Facebook cache and reboot seems to have fixed it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Gave it a shot, and no luck. I still FC every time I try and view a profile.
i have cyanogen 7 final release and facebook 1.5.3 keeps crashing when i click on a profile.
yes i've got the same problem on my wildfire (cm7 #41) -.-
Same here on HTC Desire GSM (Bravo) with CM7 installed
Same problem. On CM6 and Froyo tho...
works fine BN 1.1
With autonooter 3.0
My Nexus One and Nook Color, both with CM7, experience this crash every time. I had to roll back to 1.5.2. So it seems to happen in general with CM7. If anyone has a non-CM7 Gingerbread ROM on their phone maybe they can try it too?
So yeah it's Facebook's fault
Definitely leading towards a bad release by FB.
I Am Marino said:
Definitely leading towards a bad release by FB.
Click to expand...
Click to collapse
Indeed. Is happening to me to. I also did downgrade of kernel to LorDmod V4.1 2.6.32.28 and still doing it. This is a FB issue and not the CM rom or kernel.
I get a:
process com.facebook.katana error
Same thing happening for me. I sideloaded 1.5.2 and the crashes have gone
found it at http://software2tech.com/tag/facebook-for-android-1-5-2-apk-download/ if anyone else needs it
Yeah I was lucky enough to have 1.5.2 in a Titanium Backup so I restored it from there; then copied the apk to my phone and placed it there too. I also used TB to remove the Market link so that it won't auto-update for now.
Happens on both my HTC Hero and my Nook.
same here with CM7 #50... tried everything till I realised it was really the app that cause the problem... hope they will fix this soon
A copy of the prior stable version is posted here:
http://forum.xda-developers.com/showpost.php?p=13135172&postcount=27
Finally a solution!
Thanks guys!
going back to the previous version fixed the problem
Nexus One running CM7
I'm just using the new browser FB for now.
Sent from my Incredible with the XDA Premium App.
I have the same issue on CM7 but I think going back to the previous version is not the best solution...it is a solution thou. Makes me think Facebook doesn't have much about testing their apps before releasing...like they don't have enough money to hire some QA people
Switch to 1.52 and it's running flawlessly!!!
Sent from my PC36100 using XDA Premium App
Hello the popular messenger whatsapp takes ages to open up on my defy, be it any ROM, GB,ICS,JB after first few weeks or months the application lags like hell! is there any solution? i tried keeping app in memory, but still there ain't any significant change! is it only me or anyone else facing the problem?
Also after the holo redesign the app has started to lag otherwise it was fine with old UI, fast as light !
also i searched in forum for this issue but there is no such thread that's y asked here... hope you may enlighten me !!
any ideas?
vedhasd said:
any ideas?
Click to expand...
Click to collapse
I updated it and it seems faster now
hotdog125 said:
I updated it and it seems faster now
Click to expand...
Click to collapse
Same here, till now its good but let's see after a week..
Sent from my MB526 using xda premium
Here are the rules!
This is an UNOFFICIAL build
This thread is only temporary until CM will make the move to CM10.2 official
This has nothing to do with any official CM build
DONT EVER BOTHER Entropy512 or the other CM guys by posting anything about this in the official CM thread
This is for bug reports only!
No discusions
No small talk
No feature discussions
No "thank you" posts
Bug reports ONLY with logcat and/or kernel log
kernel
https://github.com/maxwen/android_kernel_oppo_find5 - branch jb-mr2
device
https://github.com/maxwen/android_device_oppo_find5 - branch cm-10.2
vendor
https://github.com/maxwen/proprietary_vendor_oppo - branch cm-10.2
Downloads:
4.3 gapps:
http://goo.im/gapps/gapps-jb-20130813-signed.zip
ROM
http://cyano-rob.tuennerhoff-edv.de/Maxwen/cm-10.2-20130908-UNOFFICIAL-find5.zip
Tp flash hangs when its done. Needed to force reboot to get it booting. Not able to make logs of to flash and aosp camera is missing res
Sent from my Find 5 using XDA Premium HD app
anders3408 said:
Tp flash hangs when its done. Needed to force reboot to get it booting. Not able to make logs of to flash and aosp camera is missing res
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
second one is know and fixed in next build. First one I never had so far maybe because I use the patched TWRP
Sent from my Find 5 using xda app-developers app
maxwen said:
second one is know and fixed in next build. First one I never had so far maybe because I use the patched TWRP
Sent from my Find 5 using xda app-developers app
Click to expand...
Click to collapse
I did use the old tp version, if that helps.
Sent from my Find 5 using XDA Premium HD app
I cant change the lockscreen shortcuts.
Had no problem with flashing im on the patched version
Sent from my Find 5 using Tapatalk 4
anders3408 said:
I did use the old tp version, if that helps.
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I will try a full tp flash cycle tonight
but actually I have not changed anything in kernel there
Sent from my Find 5 using xda app-developers app
michiil said:
I cant change the lockscreen shortcuts.
Had no problem with flashing im on the patched version
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
please don't report any CM 10.2 bugs
there are a lot of them
I will not start to fix CM bugs cause I will not stay on CM. So I will just sync whatever CM has changed
so this is mostly to find device specific issues cause those will happen on all custom roms
Sent from my Find 5 using xda app-developers app
maxwen said:
please don't report any CM 10.2 bugs
there are a lot of them
I will not start to fix CM bugs cause I will not stay on CM
so this is mostly to find device specific issues cause those will happen on all custom roms
Sent from my Find 5 using xda app-developers app
Click to expand...
Click to collapse
Ok sorry
Cant wait till your aokp 4.3 release
Sent from my Find 5 using Tapatalk 4
michiil said:
Ok sorry
Cant wait till your aokp 4.3 release
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
me too
for me those builds are actually a testbed for my 4.3 kernel
Sent from my Find 5 using xda app-developers app
maxwen said:
me too
for me those builds are actually a testbed for my 4.3 kernel
Sent from my Find 5 using xda app-developers app
Click to expand...
Click to collapse
And its working pretty good so i guess it wont take much longer?
maxwen said:
So I will just sync whatever CM has changed
Click to expand...
Click to collapse
you should consider these builds equal to nightlies
Sent from my Find 5 using xda app-developers app
First of all, congrats on the build. It's running much better than I could have hoped for, and I haven't seen a bug so far.
I'd like to let you know that the application I mentioned in the official CM thread a couple of days back runs properly on this build. I haven't had time to compile a proper test app for you, so I'll just throw the APK in here if you'd still like to test it. I'm suspecting it's an issue on 4.2, but I haven't had access to another 4.2 device so far. If you'd prefer I post this in the official thread instead, just let me know.
Anyway, the APK can be found here. The included fade animations turned out to have no effect on performance, so don't worry about that. The mere presence of the two backgrounds causes the application to grind to a halt, I noticed it in another app as well.
https://docs.google.com/file/d/0B8_H23V1zt69NE1qYmx4eUZjVms/edit?usp=sharing
Quipeace said:
First of all, congrats on the build. It's running much better than I could have hoped for, and I haven't seen a bug so far.
I'd like to let you know that the application I mentioned in the official CM thread a couple of days back runs properly on this build. I haven't had time to compile a proper test app for you, so I'll just throw the APK in here if you'd still like to test it. I'm suspecting it's an issue on 4.2, but I haven't had access to another 4.2 device so far. If you'd prefer I post this in the official thread instead, just let me know.
Anyway, the APK can be found here. The included fade animations turned out to have no effect on performance, so don't worry about that. The mere presence of the two backgrounds causes the application to grind to a halt, I noticed it in another app as well.
https://docs.google.com/file/d/0B8_H23V1zt69NE1qYmx4eUZjVms/edit?usp=sharing
Click to expand...
Click to collapse
oh - thats nice to hear
will give it a try later
I have the feeling the battery drains pretty fast, also battery graph says WiFi always on which it isn't. Went from 80 to 30 % in 6 hours and 32 minutes. Screen on time around 45 minutes, pretty light use.
Sent from my Find 5 using XDA Premium HD app
I did not had any TP fw flash hanging. Im on stock unpatched twrp 2.6 fyi
Sent from my Find 5 using Tapatalk 4
Psych0_D0g said:
I did not had any TP fw flash hanging. Im on stock unpatched twrp 2.6 fyi
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
I just tried it too - but I had reports in the past of such hangs
so it might be only happening random - which doesnt make it better
anders3408 said:
I have the feeling the battery drains pretty fast, also battery graph says WiFi always on which it isn't. Went from 80 to 30 % in 6 hours and 32 minutes. Screen on time around 45 minutes, pretty light use.
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I cant confirm that after using it for 2 days now
A rather minor bug, but the hardware key LEDs don't dim with the screen like they would on CM10.1. I must say they're quite bright in a dark room.
Quipeace said:
A rather minor bug, but the hardware key LEDs don't dim with the screen like they would on CM10.1. I must say they're quite bright in a dark room.
Click to expand...
Click to collapse
oh thanks - thats because I still use the liblights from my AOKP rom
which supports separate settings for screen and keys
and that doesnt play nice with CM which only supports settings
both to the same value
fixed in next build