Related
You can get it here: http://get.cm/?device=quincytmo&type=RC
Seems stable. Everything working so far.
I guess I need to go check it out. I'm still on the latest monthly.
As far as I can tell, it is caught up with the nightlies as far as features go: Camera timer, stylus gestures, whatever else is new. Everything I've tested so far works, wifi tether, bluetooth etc,
Yeah, so far so good. It seems pretty stable and fluid. Haven't checked battery life. I noticed on the last nightly that it took longer to charge the battery.
Battery life here seems very good. Very smooth, not getting lagginess that was in a couple of nightlies.
Had a couple of instabilities with a couple of apps. Reinstalling them seems to have fixed the problem. Time will tell.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Going back to M3. Having too many instabilities, random reboots, lock ups.
srpanadero said:
Going back to M3. Having too many instabilities, random reboots, lock ups.
Click to expand...
Click to collapse
I was about to say that I haven't seen any bugs with this latest release, but then I thought for a second and remembered that I had a weird screen issue where my screen was flickering, and then went black until I restarted the phone. It only happened once, so I didn't think much of it. I expect a few bugs with any ROM no matter how stable/baked it is.
Here is a bug report for graphical issues. Now is the time to report any bugs that you see.
https://jira.cyanogenmod.org/browse/CYAN-1057
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Now there's an RC2. Trying it now.
fraughtsigewulf said:
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Click to expand...
Click to collapse
So then could you and anyone else who've seen the issue sign up and vote on the bug report here: https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-1125
Either that or add your own comment and log if you have. Hopefully the devs will then see and fix the problem.
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
hogasswild said:
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
Click to expand...
Click to collapse
Now i'm getting freezes and reboots 5-6 times a day. Today I could hardly use my phone. And that was even after doing a full wipe this morning and reinstalling the latest nightly and Gapps. I think i'm gonna roll back to a version from a couple of months ago if I can find one and see if that helps.
I did go to that dev page that was suggested earlier in the thread and signed up and voted up this issue. I hope it gets the ball rolling.
I'm kinda disappointed. I know these are nightlies and aren't supported, but i'm really used to Cyanogenmod putting out solid builds, even for their nightlies. A few bugs I can deal with, but this is unusable.
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
error when installing
when I try to install the zip file I get this error "assert failed: getprop("ro.product.device)...." this is just the beginning the type is small and its hard to read- any suggestions? Some searches I've done say this error shows when the ROM is for the wrong phone, but don't see how that can be. I have the T-Mobile Galaxy Note for sure. Thanks for any help that I can get. Since it seems like T-Mobil is never going to upgrade OTA to Jelly Bean I really would like to get this ROM.
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod. Here is the links. http://get.cm/?device=quincytmo&type=snapshot
srpanadero said:
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod.
I was using Clockwork MOD. I will admit I'm a bit of a Newb with this custom recovery stuff. I went to install Goomanager on my phone, but when I reboot it reboots it into Clockwork MOD. So do I need to uninstall clockwork MOD somehow? I will try the other ROM you mentioned, but I think I had tried that one as well and got the same error. Of course this was using clockwork MOD.
Thanks,
John
Click to expand...
Click to collapse
This is the twrp page for this phone.
http://teamw.in/project/twrp2/113
It lists several ways to install it. Try them all, one will work.
srpanadero said:
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
Click to expand...
Click to collapse
So M3 is stable enough to use? I couldn't remember whether it was M2 or M3.
Yes M2 and M3 are stable enough for daily use. Actually any nightly from that time is good too. It wasn't until after M3 that things took a dive, and didn't get any better with RC1 and 2.
Only problem I'm aware of is a bug with the Bluetooth on off toggle that affects some. If it happens reboot or force close Bluetooth share.
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.
using CandyRom 5.0.2
I never faced any touch freezes issue
@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?
im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english
Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.
I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.
1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)
I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.
Okay. . .so here's a little background on my issue. So, I have been running CM13 nightlies for almost a year without issue. The phone is encrypted (by choice) and I went to install the latest nightly (072216) and the install went great. As it boots up, it requests a password to be entered before it will boot. (Normal behavior, so far). But when I go to enter the password now, the keyboard is all messed up. Certain keys can be pressed and others cannot. Instead, when I press certain keys, it is as if the notification bar tries to come down. . .again, the phone is still encrypted and NOT booted up at this point. It only happens on the last 2 nightlies. . . .(072216 and 072316). Because the keyboard is acting strangely, I am unable to log in. The only way to boot it is to boot into recovery, reinstall the previous version and then all is well.
Any thoughts?
Don't use the newest nightlies until it's fixed? Or even better, drop cm and use a better ROM?
Kreateablaze said:
Don't use the newest nightlies until it's fixed? Or even better, drop cm and use a better ROM?
Click to expand...
Click to collapse
Ha! Actually, rather enjoy using the standard CM13 Rom. That said, I noticed something else. It isn't the keyboard that is the issue, but the lock screen icon is actually covering up the bottom line of the keyboard and not letting me get to it.
That's why you should use another ROM. The Cyanogenmod crew simply don't test the things they throw into the ROM anymore, leading to incidents like this one.
Hi all, lurker here.
I've been having an issue with my OP3T that hasn't really phased me until now. From time to time my phone would lock up and crash (phone shuts down unexpectedly). I would have to manually reboot the phone by holding the power down button.
I am running on OOS Beta 10, rooted with Magisk 13, EX Kernel and whatnot. This has happened prior to being on beta channel and root as well. I've read somewhere that this is a hardware issue that arises from SD821 clocking up to max Freq which causes the crash but I think even with the custom kernel and underclocking I am still experiencing lock ups.
If there is a log I can provide for you guys I can post it, just don't know which one.
Thanks.
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch ?
pitrus- said:
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch
Click to expand...
Click to collapse
I don't have Substratum installed
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
shivagajavelli said:
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
Click to expand...
Click to collapse
Damnn, i've got the same problem.. blank screen with white light notif then off, when 3T not get random shutdown they give me random restart every 2-3mins, aarrgggghhh really annoying!
same problem with my devices
And then whats the solution for these problem? Arrggghhh
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
Anyway which kernel?
I have the same with stock and beta OOS, stock and bluspark kernel. Never rooted. I though that maybe i just press power button in my pocket but then it happend on the desk as well.
Similar issue, sometimes black screen with unresponsive buttons (they do vibrate), sometimes I can unlock it via fingerprint to the home screen but touch is unresponsive, only appswitch via recents button works but can't exit the app with home button, sometimes it just reboots.
Never had these issues from dirty flashing from open betas but now when I started clean these things began lol. Seems more laggy too.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
I just clean flashed all stock, pure without UBL, root but still same. Then tried to UBL, MAGISK + Franco Kernel, and still the same condition...
Ahhh i hate this phone! Really sucks
Hmm yeah I've had another crash but this just happened during boot.
Still have no idea what the possible cause is. Not aure why it's just us few that are experiencing this.
Maybe faulty hardware? Who knows
I used to have this problem when running the open betas for the 3t, I moved over to RR and there hasn't been any problems especially after the latest update
Edit. Also when turning on the phone the bootanimation (the two dots spinning around the thingy) it would freeze constantly, also fixed after moving to RR
My phone was crashed few times when using cameraMX application. I do not know reason, maybe last update fault? I have simple question, why we have beta version? Where is stable
Yeh I've had it freeze on multiple accounts while booting up. It would crash while the two dots are spinning and would need a hard reset.
Many times it would crash when entering my PIN for smart lock or lock screen as well..
Issue seems to have popped up again., after flashing OOS OB 14.
Most frequent symptom is after entering pin or unlocking device, at random times it would lock up Android and crash (shut down, not reboot). So I have to boot my device again by holding down power button.