Related
Hi all I am new to the xda forums (posting anyways) and I appreciate everyone who contributes on this site you guys are amazing. Anyways I am on a Motorola Droid RAZR M, rooted first with motochopper, unlocked boot loader with motopocalypse, and flashed the latest nightly from Cyanogenmod. I was ecstatic when it worked because tinkering with my old Droid 2 Global didnt go so well and I didn't want to mess up my phone, so I was elated that it worked. A couple days ago CM Updater popped up on my phone and it was CM10.2-20130815. When I saw the 10.2 I couldn't resist and I updated it. Everything was fine until the next day when I updated to CM10.2-20130816. Videos no longer played on my phone. The stock video player wasn't working. I searched and searched for a fix but I couldn't find one so I flashed back to CM10.1-20130813. Everything works now as it should but I keep researching it. Recently I found that the problem started in the first release of CM.10.2 for the xt907. I want Android 4.3 really badly but I can't live without the stock video player. MXPlayer is great but Vine, YouTube, Snapchat, etc. wouldn't work without the stock video player. Is there a fix for this or does anyone know if the newest nightly fixed this problem? Thank you in advance.
It will get better, nightlies are experimental and there are bugs and such
Sent from my XT907 using XDA Premium 4 mobile app
WillisD said:
It will get better, nightlies are experimental and there are bugs and such
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! Im thinking about trying Skrilax's CM10.2 ROMs. There are a lot more nightlies so maybe there will be less bugs but I dont know there could be even more. Do you have any experience with any of his ROMs? Ive heard good and bad about them.
It's still cm10.2 just unofficial, I've made a few nightlies myself I'm running the latest nightly now pretty smooth
Sent from my XT907 using XDA Premium 4 mobile app
WillisD said:
It's still cm10.2 just unofficial, I've made a few nightlies myself
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For the RAZR M? Was it hard to do?
Yes and no, but you have to be on Linux though and there are guides out there
Sent from my XT907 using XDA Premium 4 mobile app
taylorjared1996 said:
Thanks! Im thinking about trying Skrilax's CM10.2 ROMs. There are a lot more nightlies so maybe there will be less bugs but I dont know there could be even more. Do you have any experience with any of his ROMs? Ive heard good and bad about them.
Click to expand...
Click to collapse
I have used Skrilax's builds and have found them to be well built. Keep in mind if bugs exist in CM 10.2 it probably will be so across the board regardless of the dev.
Sent from my XT907 using Tapatalk 4
I dual boot Ubuntu and Windows 8 on both of my computers so maybe ill try it. It sounds kind of fun. And yeah I am coming to terms with the fact that i probably wont get 4.3 until a fix is made but its not a big deal. Having 4.2.2 is way better than being stuck on 4.1.2 with Motorola's skin on it. I knew the RAZR M had potential but I couldnt get it to perform well on Motorola's stock 4.1.2 ROM, but with CyanogenMod it runs like a dream. Battery life is better too!
is data working on the unofficial or skrillax's build?
undagullu said:
is data working on the unofficial or skrillax's build?
Click to expand...
Click to collapse
On the CM 4.2-20130824 Nightly the camera issue if fixed and has been since at least a couple nightlies back, so that isnt an issue anymore. I cant say about skrilax's or the unofficial but the official nightlies have all data working and LTE is especially fast, but i have not had any problems with any type of connection on LTE, 4g, 3g, HSPA+, & CDMA.
Is anyone else having the problem where if you turn off your phone and turn it back on it'll sometimes freeze at the Samsung logo. If you do a battery pull and turn the phone back on again, it'll boot like normal.
Firmware: MDL
ROM: Cyanogenmod 10.1 RC2
Recovery: TWRP
What twrp version?
xBeerdroiDx said:
What twrp version?
Click to expand...
Click to collapse
TWRP 2.5.0.2
I used your HOW-TO guide to complete everything
Loki+TWRP+Motochopper CASUAL
Wiping Device
Flashing ROM
How long has it been doing this/at what point did it start?
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
emckai said:
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
Click to expand...
Click to collapse
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
jd1639 said:
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
Click to expand...
Click to collapse
RC2 is a 4.2.2 build.
Last night I decided to just try and let it hang and see if it'll get past it but 2 minutes later it never did. So I just held the power button (10 seconds) to shut it down and restart.
Sorry, didn't read your whole post and missed the rc2.
jd1639 said:
Sorry, didn't read your whole post and missed the rc2.
Click to expand...
Click to collapse
No problem. Just wondering what is causing this issue, seems like some people in the Cyanogenmod thread is also having this issue.
It's happening on the cm10.2 roms too and seems to be related to the recovery used. See if twrp 2.6.3.0 works for you.
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
I switched custom recovery. TWRP to CWM and everything is booting just fine. (knock on wood) I'll turn off and on my phone a couple more times and see if it's actually the custom recovery.
cwm has had far fewer problems on the S4 than twrp. i've always rolled with cwm touch across my devices just out of preference. glad i havent had to deal with any of these twrp issues. glad you're sorted. cheers
Just rebooted my phone a couple of times (about 10 times) and it didn't hang at samsung logo anymore.
Thanks everyone!
emckai said:
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
Click to expand...
Click to collapse
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
CZ Eddie said:
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
Click to expand...
Click to collapse
x2 to all of the above. Known issue for S4s on 4.3 and 4.4 and although a couple of ROMs have claimed that they're "solving" it as of yesterday's nightlies it ain't fixed....
Just hold down power till the Samsung screen disappears then immediately let go. It'll try again. Repeat, repeat, repeat as necessary and eventually it will work.
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
CZ Eddie said:
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
Click to expand...
Click to collapse
I've been using the same kernel since yesterday afternoon and haven't hung once either. I've tried it with CWM and TWRP because my hangs used to occur when I rebooted system from recovery and both have worked just fine.
on the latest d802 4.4.2 custom roms and kernels i get a lot of freezes.
it will freeze in the middle of an animation and will take some seconds up to some minutes and then working normal again.
sometimes i have to hard-reboot to get out of freeze / lag.
on older 4.4.2 slimroms i never had this behavior, only since some weeks with new roms / kernels.
i`ve tried every rom / kernel combo but sooner or later i will get a freeze again.
could a revert to stock and re-rooting / flashing custom rom maybe a solution? i`m afraid to do this because of the long time to backup my 32gb data.
what are your experiences with the latest 4.4.2 roms and kernels? did you find a solution for this with any combo or fixes?
help would be appreciated.
push! no one else with same problems? maybe i got a hardware defect?
paratox said:
push! no one else with same problems? maybe i got a hardware defect?
Click to expand...
Click to collapse
The only thing I can say is I own the VS980 version of the device and i've tried every single 4.4 rom offered on this sight and have the same issue with all. Most of the time i'm using the device and it freezes, sometimes reboots, and sometimes comes out of it after a few minutes. Also not being able to wake the device only seeing a black screen and forced to hard reboot device. 4.3 seems to be a much better with these issues but not completely solved for me. I'm hoping the release of 4.4 source from lg will fix these issues but i'm unsure. So at least your not alone in these problems lol. I've tried multiple kernels and governors etc. Bumping up the min freq on the cpu seems to help and changing to interactive governor but doesn't eliminate the issue just help. I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
flyinj54 said:
I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
Click to expand...
Click to collapse
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
paratox said:
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
Click to expand...
Click to collapse
Yea unfortunately it seems very common among these devices so i'm pretty confident it's a software issue although i'm not 100% sure of that. I ran a flex rom for a few days on 4.2.2 and didn't have any of the same issues.
added a poll as a matter of interest.
omni-ROM, Mokee rom, vanir rom etc.freezing problem still continues.
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
lubirdy said:
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
Click to expand...
Click to collapse
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, stock cm kernel.
I'm thinking back now and it did freeze once when first signing into the Google account immediately after flashing the ROM, but nothing after that. So.. nearly spotless
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Best of luck! To be specific, I'm using the snapshot release of cm11... still don't trust the nightly releases
i did a lg flash tool stock restore, factory reset and OTA updates. now the freezes did not come back until now *knock on wood*.
when i did a backup of the sd there was one corrupt media file which was not able to transfer.
maybe the media scanner did go crazy and was the reason for the freezes.
using cm11 m3 on my d802... very little freezes compared to previous nightlies, fingers crossed
Hello,
I have been using Snapshot M8 for longest time and have quite enjoyed it.
For last day or so, i have been trying to update to M10 but i have been unsuccesful.
Im very technical savvy but when it comes to understanding some of lingo on this board, i am terrible.
So, ive tried updating to the KitKat firmware but after so much trouble ive decided to abandon it in favor of the JellyBean firmware. After bricking my phone over and over again, i finally got back to stock 4.4.2 with working modem's and the like. Also, ive reverted back stock recovery.
Ive read through quite a few threads but to no avail, can not understand how to upgrade or downgrade to M10.
Can anyone help me find what version of the firmware i have and advise me how to upgrade to M10? (jellybean, since i heard they're are problems)
I hate asking for help, i just cant understand what to do.
ALSO, THANK YOU DEVELOPERS for such a great port!
I believe you need the KK bootloader for M10.
So you'll need to flash this first (or just an official stock KitKat firmware), then a compatible recovery (e.g. CWM 6.0.4.9) and then CM M10.
lem22,
Thank you for your reply!
So its not a good idea to flash M10 using the jellybean firmware?
I can successfully flash CMW 6.0.4.9 using RSDLite. (ive become quite fluent after bricking my phone, haha.)
but when i tried to install M10 through CWM i get a status 7 error, i believe im flashing with 6.0.4.9 KitKat.
You must flash KitKat update first (http://sbf.droid-developers.org/phone.php?device=8), then compatible recovery and then CM11 M10.
I suggesting to use CM Nightly builds (mine is 9/27, which is more stable than snapshot builds.
UuN said:
I suggesting to use CM Nightly builds (mine is 9/27, which is more stable than snapshot builds.
Click to expand...
Click to collapse
Is wifi and bluetooth fixed in the latest nightly? KK BL?
Wifi & BT works fine, but gps kinda less acuration..
Yes, im using KK BL.
UuN said:
Wifi & BT works fine, but gps kinda less acuration..
Yes, im using KK BL.
Click to expand...
Click to collapse
Any major bugs with the new nightly that would be bad if your going to daily the phone?
Sent from my XT907 using Tapatalk
Any major bugs with the new nightly that would be bad if your going to daily the phone?
Click to expand...
Click to collapse
So far there is no major bug/issues i found in my daily use like phone calls, wifi, themes, games & apps running fine, and i do dirty flashing with last nightly build if there are a lot changes/fixed.
Hey, i just want to know your opinions about why is better CM11S or why is better the latest CM12 Bacon Nightly ( cm-12-20150128-NIGHTLY-bacon)
I'm not trying to be a spoiler, but seriously, when it's so easy to do a nandroid backup and flash CM12, why not just try it? The only slight hassle is having to flash the old firmware if you decide to go back, but even that's not hard if you know how to use fasboot / recovery / flash ROMs.
And to answer your question, it's better because it's Lollipop, a step forward.
Bottom line: there is only one way for you to know.
As the above post said try it but myself i went back to cm11 as i tried every cm12 rom plus different kernals and my device would still be awake in wakelock app went back to mahdi rom with ak kernal and all good. still early stages for cm12 and cant wait to go back but will wait for a while
pro4ever said:
As the above post said try it but myself i went back to cm11 as i tried every cm12 rom plus different kernals and my device would still be awake in wakelock app went back to mahdi rom with ak kernal and all good. still early stages for cm12 and cant wait to go back but will wait for a while
Click to expand...
Click to collapse
Your problems have nothing to do with the cm12 nightlies "early stage".
Using cm12 since unofficial builds in december. There were some problems,
but not the battery life. It is the same as on cm11 for me.
Thats good news for you but since going back to cm11 my device goes deep sleep im happy
AcmE85 said:
Your problems have nothing to do with the cm12 nightlies "early stage".
Using cm12 since unofficial builds in december. There were some problems,
but not the battery life. It is the same as on cm11 for me.
Click to expand...
Click to collapse
Agreed. I had some wakelock issues in a build back in December or early January, but none since.
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
pro4ever said:
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
Click to expand...
Click to collapse
I use official CM12 nightlies with stock kernel and no mods. I dirty flash, but clear cache / ART cache with every nightly.
pro4ever said:
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
Click to expand...
Click to collapse
Official CM12 Nightlies with stock kernel.
If you ask me ALL kernels are overrated in terms of battery life, but that is just my opinion (after some testing).
It is funny though how some users with custom kernels are undervolting and underclocking their
devices and yet never achieve the same battery life I get with all stock.
Some even claim that there device is more fluid than stock with kernel x or y. :laugh:
If you are into multirom or perhaps display color calibration then sure, a custom kernel is the way to go.
btw, I don't use greenify, I don't block play services wake permissions, I don't use the facebook app.
AcmE85 said:
Official CM12 Nightlies with stock kernel.
If you ask me ALL kernels are overrated in terms of battery life, but that is just my opinion (after some testing).
It is funny though how some users with custom kernels are undervolting and underclocking their
devices and yet never achieve the same battery life I get with all stock.
Some even claim that there device is more fluid than stock with kernel x or y. :laugh:
If you are into multirom or perhaps display color calibration then sure, a custom kernel is the way to go.
btw, I don't use greenify, I don't block play services wake permissions, I don't use the facebook app.
Click to expand...
Click to collapse
Tnx for both your replys I've always used cm 12 with custom kernels. Will try with stock and see how it goes
I reverted back to stock 44S after trying CM12 in Nov, was too unstable back then. Seems people are getting stable experience from CM12 now, think I am gonna flashing it later today
Thanks all!
I've gone from 11s to 12 to 11 again. Cm12 is stable but does have a few annoying bugs. The one that annoyed me the most was the audio buzzing bug. Many say enable the phone to always have 2 cores on, but that never fixed my issue. Buzzing always happened. Then there was the proximity issue which van be fixed by flashing a new firmware and modem but my phone doesn't take the modem. Lost lte and signal kept dropping every 3 minutes. Also had an issue when I was in a call, I often was a unable to hear the person. Only had to enable speaker and then Disable it again. That was the icing on the cake so I went back to cm11s. Now here I can say that battery life is almost identical. Just ever so slightly better on lollipop for me. The system is not as smooth specially with scrolling. I have scroll lag on instagram and Facebook again (minimal but noticeable) system, for a stock rom, isn't really too stable. Had the phone crash on me and when I turned it back on, it asked me to re set up the device but data was still in tac. So yeah. That's pretty much it.
Sent from my A0001 using Tapatalk
Have tried CM12 nightly, and back to 44s because one game that I like didn't run smooth . I think ART cause this, been trying on CM12 unofficial builds also, same result. Maybe the game hasn't updated for lollipop yet.